The Hidden Cost of Bad File Management
Bad CAD file management does not announce itself with an error message. It accumulates quietly. Files named “bracket_final_v2_FINAL_USE_THIS.SLDPRT” multiply. Assembly references break when someone moves a folder. A machinist gets the wrong revision because two files have nearly identical names. A drawing revision gets issued without including the latest part model because no one knew which version was current.
I have seen a costly tooling order placed from a superseded drawing revision because the project folder had three files with similar names and no clear indication of which was current. The tooling was wrong. The cost was significant. The root cause was file management, not engineering.
This guide covers naming conventions, folder structure, and revision control approaches that work in practice — from individual engineers to small teams without a full PDM system.
Why Uncontrolled Folders Lead to Disasters
The failure mode is always the same. A project starts with good intentions. Parts have clear names, one folder, one engineer. Then the project grows. Multiple engineers contribute files. Revisions happen. Someone needs a slightly modified version “just for this customer.” A copy gets made “to be safe.” The original and the copy both get updated independently. No one knows which is the master.
Assemblies reference the wrong part silently. SolidWorks opens a file, resolves references to whichever version it finds first in the search path, and never tells you it chose the wrong one. The assembly looks correct. The drawing is based on it. The drawing is wrong.
Naming Conventions That Work
The best naming convention is one that is simple enough to follow consistently. Elaborate schemes with many fields get abandoned under time pressure.
Part files
Recommended format: [ProjectCode]-[Sequence]-[Description]
Example: PRJ001-0010-MOUNT_BRACKET.SLDPRT
- ProjectCode: 3-6 character project identifier
- Sequence: 4-digit number for ordering in file listings
- Description: short noun phrase, underscores instead of spaces
Rules: no version number in the filename. Revision is tracked by the revision field in the drawing title block and in the file metadata, not by the filename. A file named “bracket_v3” means nothing six months later — was v3 the released version? Is v4 in someone else’s folder?
Drawing files
Same project code and sequence as the referenced part: PRJ001-0010-MOUNT_BRACKET.SLDDRW. One drawing per part. If the part is updated, the drawing is updated — same filename, revision tracked in the title block.
Assembly files
Use a higher-level sequence to distinguish assemblies from parts: PRJ001-1000-MAIN_ASSEMBLY.SLDASM. Assemblies in the 1000-1999 range, sub-assemblies in 1100-1199, etc.
Folder Structure Principles
Keep folder structure shallow. Three levels deep is a practical maximum before navigation becomes slow and paths become excessively long (Windows path length limits have caused real problems with deep CAD folder structures).
Suggested structure:
- ProjectCode\ — top level for all project files
- ProjectCode\CAD\ — all SolidWorks parts, assemblies, drawings
- ProjectCode\Release\ — approved released drawings (PDF and DXF)
- ProjectCode\Supplier\ — files received from suppliers
- ProjectCode\Reference\ — customer specs, standards, technical references
The CAD folder contains working files. The Release folder contains frozen, approved output files (PDF drawings, STEP exports). Never overwrite a released file — add a revision letter to the released filename: PRJ001-0010_RevB.PDF.
Revision Letters vs. Revision Numbers
Two common approaches:
- Letter-based (A, B, C…): standard in many industries. Pre-release revisions sometimes use numbers (Rev 01, 02) internally, then switch to letters (Rev A) for the first released version. Letters clearly distinguish design revisions from pre-release drafts.
- Number-based (1, 2, 3…): simpler, avoids confusion between letter “O” and zero, or “I” and one. Used in some industries where letter-based revision is not mandated by a standard.
Use whatever your industry standard or customer specifies. If there is no external requirement, pick one and use it consistently. Never mix letter and number revisions on the same project.
Lightweight PDM for Small Teams
Full PDM systems (SolidWorks PDM, Vault) have significant setup and licensing costs. For small teams (2-5 engineers), simpler approaches can provide most of the benefit:
Shared folder with access controls
Network share with one master CAD folder. Access control: all engineers read/write, but only the project lead can write to the Release folder. This prevents accidental overwriting of released files. Works for up to 5-10 engineers if naming conventions are followed.
Git LFS for version control
Git with Large File Storage (LFS) can version-control binary CAD files. SolidWorks files are binary, but Git LFS stores them on a server and tracks them with pointers in the Git repository. You get full history, rollback capability, and branch support. The workflow is unfamiliar to engineers who have not used Git, but the payback in version history is significant.
SolidWorks PDM Standard
Included with SolidWorks Professional, PDM Standard provides basic check-in/check-out, revision control, and a SQL-based vault. It is not as full-featured as PDM Professional, but it handles the essential requirement: one file, one current version, change history tracked.
Lessons From Real Mistakes
Mistake 1: Assembly file moved to a new folder without updating references. SolidWorks could not find the part files on next open, prompted for each missing file. The engineer clicked through the prompts quickly, pointing to the wrong folder. The assembly rebuilt silently with wrong part versions. The drawing based on it was issued. Parts were ordered. Wrong.
Lesson: never move CAD files manually. Use the SolidWorks Explorer or PDM to move files so references are updated automatically.
Mistake 2: Two engineers working on the same part simultaneously (no check-out system). Both saved their changes. The one who saved last overwrote the other’s work. One set of changes was lost permanently.
Lesson: even without a PDM system, establish a simple check-out protocol — a shared spreadsheet where engineers log which files they are actively editing. Low-tech, effective.
Key Takeaways
- Revision in the filename is a trap. Use consistent part numbers in filenames and track revision in the drawing title block and metadata.
- Keep folder structure to three levels or less. Deep hierarchies create navigation friction and path-length errors.
- The Release folder is read-only except for the project lead. Released files never get overwritten.
- Never move CAD files using Windows Explorer. Use SolidWorks Explorer or PDM to maintain reference integrity.
- For small teams without PDM: a simple check-out log (shared spreadsheet) prevents simultaneous editing conflicts. It is not elegant, but it works.
コメント