Standard Work · Program & Workflow

CAD File Management and Naming Convention

Mandatory procedure for organising, naming, and versioning all CAD files across engineering and manufacturing. Eliminates duplicate files, ensures traceability, and supports lean document control.

Review Cycle
Semi‑Annual
Department
Engineering & Design
Compliance
Mandatory
Version
2.1
Free download — no sign‑up, no email.Standardize your internal operations and training documentation.
Program Overview

This program establishes a single source of truth for all CAD files (SolidWorks, Fusion 360, AutoCAD, Inventor, etc.) used in production and design. It mandates a consistent naming structure, versioning protocol, and automated check-in/check-out to prevent overwrites and ensure audit trails. Every file must comply with the five‑field naming schema: Project‑PartNumber‑Revision‑ComponentType‑Description. Non‑compliant files are rejected at gate review.

Scope & Applicability

Applies to all engineers, designers, CAD technicians, and any personnel who create, modify, or archive CAD files at the facility. Includes native part/assembly files, drawings, STEP/IGES exports, and simulation files. Excludes temporary scratch files or reference PDFs stored locally. The procedure covers the centralised network drive (\\server\cad_lib\) and any cloud‑synced directory under the company PDM system.

Core Directives & Workflow Rules
  • NAMMandatory naming format: [PROJECT]_[PN]_[REV]_[TYPE]_[DESC].SLDPRT. Example: MACH3_0750_R02_FRAME_BASE.SLDPRT. No spaces or special characters except underscore.
  • REVRevision control: Each revision increments the tag (R01 → R02 …). Major releases change the project version. Revisions must align with the ECO (Engineering Change Order) number.
  • CHKCheck in/out: Before editing any file, the user must “Check Out” via the PDM or a formal locker system. No simultaneous writes to the same file. Check in with a comment referencing the ECO or task ID.
  • ARCArchive policy: Obsolete revisions are moved to _Archive folder with a date stamp, never deleted. Active project folders contain only the current revision plus a _Ref subfolder for imported geometry.
  • EXPExport naming: Neutral formats (STEP, IGES, PDF) inherit the source file name with a suffix: _STEP, _IGES, _DWG. Never rename exports arbitrarily.
Roles & Responsibilities
  • Design Engineers / CAD Technicians – Ensure all files created or modified follow the naming convention and revision rules. Perform check‑in/check‑out procedures and update the change log.
  • Engineering Manager / Lead Designer – Conduct weekly file audits (random sample of 10% of modified files). Enforce compliance and escalate repeated violations.
  • Document Control Clerk – Maintain the archive directory, purge temporary local copies, and generate monthly compliance reports.
  • IT / PDM Administrator – Manage user permissions, automate naming validation scripts, and backup the CAD library nightly.

Standardize Your Shop Floor

Your processes are only as good as your ability to sustain them. ShopDocs gives you a centralized, digital library for all your SOPs, 5S audits, and training materials. Keep your team accountable and your shop lean.

Try ShopDocs →
Implementation & Tracking
1 Audit existing files. Inventory all active CAD files on the shared drive. Flag files that do not match the naming schema. Use a script to auto‑detect violations (e.g., spaces, missing revision tags).
2 Migrate to compliant structure. Rename files in batches using a change‑log tool (or manual rename with ECO approval). Update all assembly references before moving.
3 Train all users. Deliver a 30‑minute hands‑on session covering naming rules, check‑in/out, and the archive folder. Provide a quick‑reference card (laminated) at each workstation.
4 Activate validation gates. Configure the PDM or a simple script to read the file name upon save and reject any non‑conforming name. Issue a warning log for the user.
5 Monthly compliance review. Engineering Manager runs a report of all modified files from the past 30 days. Score compliance percentage. Any score below 95% triggers a targeted retraining session.

Software that works like your best tools.

This SOP library is maintained by Ryxen — focused software tools that solve specific operational friction points for Canadian small businesses. No ERP bloat, no per-user pricing, no demo calls.

SwitchDesk · Call Tracking SiteQueue · Install Tracking ServiceGrid · CMMS SupplyGrid · Material Orders SafeDesk · Safety Compliance ShopDocs · Visual SOPs