Design Organization Standards
In order for our CAD and other design files to be easy to navigate and use, we must follow a standardized naming convention and file structure. A consistent system ensures that files can be quickly located, understood, and updated by anyone on the team. This organization not only speeds up design work but also reduces errors, prevents duplication, and makes design reviews more efficient. By maintaining clear and consistent file management, we enable smoother collaboration and long-term usability of our designs.
MCAD Organization
Project Structure
The folder structure is as such:
LHRS 24-26 → System → Subsystem → Subassembly
Systems
24-SYS
Ex: 24-DYN
Subsystems
24-SYS-X000 (Name)
Ex: 24-DYN-1000 (Suspension)
Ex: 24-BDY-2000 (Ergonomics)
Subassemblies
Each subassembly within a subsystem should be given its own subassembly folder that contains the assembly itself as well as its constituent parts
24-SYS-XY00 (Assembly)
Ex: 24-DYN-1100 (Control Arms)
Ex: 24-BDY-2100 (Pedal Box)
The actual SolidWorks assembly files should be prefixed with a _ in order to place them at the top of the file explorer. This applies at any level of the file system.
Ex: _24-000 ← Should be within the LHRS (24-26) folder
Ex: _24-DYN ← Should be within the dynamics system folder
Ex: _24-DYN-1000 (Suspension Assembly) ← Should be within the suspension subsystem folder
Ex: _24-DYN-1100 (Control Arm Assembly) ← Should be within the control arms subassembly folder
Parts
All parts will be contained in the subassembly folder to which they belong.
24-SYS-XY##-R# (Name)
Ex: 24-DYN-1101-R1 (Control Arm Apex)
R# stands for revision number. Revision numbers should be used when a part or assembly is completely redesigned from scratch, not for minor edits or updates. In this case, the old version should be moved to the _archive folder within its subassembly folder, and the new design should be saved with the next available revision number. This makes it clear that the design has undergone a full revision rather than a simple modification.
Note: Reference sketches:
Reference sketches should be included at the system and subsystem level. The word REF should come after the level designation.
Ex: 24-BDY-REF
Ex: 24-BDY-1000-REF (Tab Sketch)
Note: Manufacturing subfolders
Every subassembly should contain four folders
_concept - folder for sketches, practice parts, and other concept work related to the subassembly or parts
_dwg - folder for all formal engineering drawings for components to be machined
_fab - folder for everything related to manufacturing including CNC or 3DP gcode, waterjetting DXFs, tooling, machining fixtures, or jigging files
_archive - folder for old versions of parts or assemblies
Design Library
The “Design Library” will serve as a central repository for all standardized hardware and commonly used components. By keeping these parts in one organized location, we can ensure consistency across designs, reduce duplicate files, and make it easier for team members to find and reuse existing components. All items in the library will follow a clear naming convention to maintain order and usability
DL-####-VEN (Desc.)
#### = Vendor part number
VEN = Vendor
(Desc.) = Hardware component name or description. These should be named according to standard engineering convention, and go in order of specificity
Ex: DL-92620A564-McMaster (0.25-28x1 HH) → 1/4”-28 1” Long Hex Head Bolt
Ex: DL-63195K61-McMaster (0.25 ID 0.65625 OD Swivel Joint) → 1/4” ID 21/32” OD Spherical Bearing
Information to include: Sizing, Thread, Thread-Direction if multiple, etc. There are too many types of hardware components for me to give a guide on how to name every type. Use your best judgement and be consistent with what already exists. Make sure it makes sense.
Ex: HH - hex head, SCH - socket cap head, RH - rounded head, FH - flat head