2028 Vehicle MCAD Organization

📁 Folder Structure Overview

LHRS YY-YY
└── System
    └── Subsystem
        └── Subassembly
            └── (Nested Subassemblies as needed)

⚙️ Naming Convention

General Format

Assemblies:

##-XXX-###_##-R# (name)
season-system-subsystem and/or subassembly_nested/secondary subassembly (optional)-revision # (human-readable name)

Parts:

##-XXX-###_##-##-R# (name)
season-system-subsystem and/or subassembly_nested/secondary subassembly (optional)-part #-revision # (human-readable name)

Notes

Secondary Assemblies:
- Do not get their own folder.
- Use preexisting parts from the main assembly hierarchy.
- May or may not be used in another assembly.
- Serve as subassemblies to make the main assembly cleaner, or as supplemental assemblies for interference checks, testing, or visualization purposes.
Nested Assemblies:
- Do get their own folder.
- Are fully part of the assembly/part hierarchy.
- Follow the standard _subassembly-R# naming and folder structure.
System-specific Folder Splitting:
- Some systems may choose not to split folders by subsystem.
- For example, Ergonomics (ERG) and Aeroshell (AER) may be better organized by projects from the start rather than by subsystem.
- Folder structure should remain logical and easy to navigate, prioritizing the natural workflow of the system or project.

Examples by Level

Level	Example	Notes

Level	Example	Notes
System	26-PTN	Powertrain system
Subsystem	26-PTN-100 (Battery)	Major subsystem
Subassembly	26-PTN-101 (BPS Subassembly)	Within Battery subsystem
Nested Subassembly	26-PTN-101_01 (Connector Subassembly)	Nested or secondary assemblies
Part	26-PTN-101_01-01-R1 (Connector Housing)	Individual components

Note: Secondary/nested assemblies are optional and indicated by _01, _02, etc.

🧩 SolidWorks Assembly Naming

Assemblies should start with an underscore (_) to appear at the top of the file explorer.

Level	Example	Notes

Level	Example	Notes
System Assembly	_26-PTN.sldasm	No revision or name needed
Subsystem Assembly	_26-PTN-100 (Battery).sldasm	Human-readable name required
Subassembly	_26-PTN-101-R1 (BPS Subassembly).sldasm	Revision begins at subassembly level
Nested Subassembly	_26-PTN-101_01-R1 (Connector Subassembly).sldasm	Nested assemblies also get R#
Secondary Assembly	26-PTN-100_01 (Secondary Battery Assembly).sldasm	Optional grouping inside subsystem

🧱 Parts Naming Convention

Parts must include revision number R# and a human-readable name.

26-PTN-101_01-01-R1 (Connector Housing).sldprt
26-PTN-101_01-02-R1 (Lock Tab).sldprt
26-PTN-101-01-R1 (Fuse Mount).sldprt
26-PTN-101-02-R1 (Mounting Plate).sldprt

🧮 Reference Sketches & Equations

Reference sketches do not include revision numbers or human-readable names.

26-PTN-100-REF.sldprt
26-PTN-100-REF-equations.txt

🗂 Subassembly Subfolders

Each subassembly folder must contain four standardized folders:

Folder	Purpose

Folder	Purpose
_concept	Early sketches, test parts, ideas, R&D
_fab	CNC/3DP G-code, DXFs, fixtures, jigs, Engineering Drawings (DWGs) - anything required for in-house manufacturing or outsourcing
_archive	Old/deprecated designs or revisions
_sim	Design study and simulation files

✅ Full Example Directory

26-PTN
├── _26-PTN.sldasm
├── 26-PTN-100 (Battery)
│   ├── _26-PTN-100-R1 (Battery).sldasm
│   ├── 26-PTN-100-REF.sldprt
│   ├── 26-PTN-100-REF-equations.txt
│   ├── 26-PTN-101 (BPS Subassembly)
│   │   ├── _26-PTN-101-R1 (BPS Subassembly).sldasm
│   │   ├── 26-PTN-101_01 (Connector Subassembly)
│   │   │   ├── _26-PTN-101_01-R1 (Connector Subassembly).sldasm
│   │   │   ├── 26-PTN-101_01-01-R1 (Connector Housing).sldprt
│   │   │   └── 26-PTN-101_01-02-R1 (Lock Tab).sldprt
│   │   ├── 26-PTN-101-01-R1 (Fuse Mount).sldprt
│   │   └── 26-PTN-101-02-R1 (Mounting Plate).sldprt
│   ├── _concept
│   ├── _fab
│   └── _archive