2.5  Project Folder Structure

2.5.1 General

Maintaining consistent file naming and structure is critical for referenced (linked) files to function properly across project teams and for end users such as facilities managers, to be able to retrieve files quickly once the project is complete.  For this reason, LACCD has developed a filing structure to organize BIM Files and other deliverables for the duration of the project.

Sample Folder Structure 

The root location (drive letter) of the Project folders may differ from office to office.  However, all LACCD project data should be independent of the root drive letter to allow sharing between differing office server structures.  The Root project Directory (LACCD) must reside directly below the Drive letter:

a. Campus Codes 

Campus Codes (Table 1) shall be used to organize all projects by a consultant at a particular college.  Folders consist of the 3 character Campus code, and shall be placed directly below the LACCD Project Directory as shown above.  Campus Name can follow campus code if desired.

b. Project Number 

Prior to commencing work, project teams shall be assigned an LACCD Project Number by the College Project Manager.  This number shall be used for organizing the project files, and should include the common name on the file name project.

●        (Example:  Mission College CPM assigns the East Complex project a project number of 04M-418.    Therefore project folder shall be named 04M-418 East Complex)

c. Discipline Folders

Each discipline shall be assigned a folder corresponding to a Discipline Designator as listed in Table 2.  All project files received and referenced from each discipline shall be organized in this folder.  As a project progresses, the contents within these discipline folders will expand, and each deliverable should be clearly organized in its own folder. 

d. BIM Folder 

BIM Files shall be sorted by model files and sheet files.

Model Files - Original files from other disciplines should be linked from their discipline folder location and relative path to models.  Model file names shall follow file naming convention outlined in Section 3.1 Model file Naming of this document

Sheet Files - PDF and .dwg (.dgn) formats of the most current sheets shall be maintained in this folder and organized with sheet file naming outlined in File Naming Section 3.2 Sheet Naming and Numbering of LACCD CAD Standards.

e. Support Files - Standard items needed for the project, such as a project specific symbols, applications (lisp, script, etc.), logos and graphics.  Project Specific Model Content can also be placed here.

f. Coordination Files – Files for Construction coordination (clash detection) shall be managed by the Virtual Design and Construction Manager or Builder, and organized by date as the project progresses.  

g. Other Folders -  Renderings, analyses, LEED, etc., will have their own folders which will be populated as the project progresses.

2.5.2 Variant Folder Tree

For projects that require multiple buildings:

Create building folders below the discipline directories as required for the project.

2.5.3 Archiving Milestone Submittals

All documentation pertaining to Milestone Submittals shall be archived and stored within the project file structure with a heading corresponding to the submittal type (i.e. 100% Construction Documents).  A sample file structure is shown below: