The Real Cost of Poor Version Control
Every experienced mechanical designer has encountered the consequences of inadequate drawing version control: a machinist who manufactured to an old drawing, a supplier who quoted from a superseded BOM, a field technician who installed the wrong revision of a critical component. These are not administrative failures — they are engineering failures with real cost consequences.
Effective version control is not primarily about documentation discipline. It is about ensuring that everyone who needs a drawing has the correct revision, that the history of changes is traceable, and that superseded revisions are clearly identified and inaccessible to users who might act on them. This article covers the practical systems and habits that achieve those outcomes in real engineering environments.
Revision Numbering Systems
Before managing revisions, you need a consistent system for numbering them. The two most common systems are alphabetic and numeric, each with established conventions.
Alphabetic Revision System
Revisions are designated A, B, C, D… with pre-release revisions typically using a dash prefix (- or a number) to indicate unreleased design iterations. This system is common in North American manufacturing and aligns with ASME Y14.35 practices. Pre-release revisions (dash numbers: -01, -02) cover design development phases; alpha revisions (A, B, C) are formal releases. The letters I, O, Q, S, X, and Z are often skipped to avoid confusion with numbers and other characters.
Numeric Revision System
Revisions are designated 01, 02, 03… This system is common in European manufacturing environments and aligns with ISO standards. It is unambiguous and eliminates the confusion between similar-looking letters and numbers. The trade-off is that there is no natural distinction between pre-release and formal release revisions without adding a status designation field.
The critical rule, regardless of system: never go backward. A revision is permanent once issued. If a released drawing revision is found to have an error, the correction is made in the next revision. Overwriting or correcting a released revision creates a version control integrity failure — the change is not visible in the revision history.
The Revision Block: What It Must Contain
Every engineering drawing should have a revision history table — typically called the revision block — that records the complete history of all issued revisions. The revision block is a permanent part of the drawing and is never deleted or shortened.
| Revision Block Column | Content | Required? |
|---|---|---|
| Revision | Revision letter or number | Yes |
| Date | Date revision was issued | Yes |
| Description | Brief description of what changed | Yes |
| Approved by | Approving engineer or manager | Yes |
| Drawn by | Engineer who made the change | Recommended |
| ECO/ECR number | Engineering change order reference | Recommended for released drawings |
The change description must be specific enough to be useful. "Per ECO 1247: updated bore diameter on Pos. 4 from Ø32H7 to Ø35H7 to accommodate new bearing selection." is useful. "Drawing update" is not. The revision block is a communication tool, not a formality.
File and Folder Management for Drawing Control
Even in organizations without a formal PDM or PLM system, disciplined file management prevents the most common version control failures. The core principle is simple: there is one place to get the current drawing, and it is clearly distinguished from all other locations.
Controlled vs. Working Directories
Maintain a strict separation between the controlled release folder and the working/in-progress folder:
- Released drawings folder: Contains only current, formally issued revisions. Access is controlled — ideally, only the drawing administrator can write to this folder. Users can read and print from it but cannot overwrite files.
- Working drawings folder: Contains in-progress design work. Files here are clearly marked as not released (e.g., file name suffix "_WIP" or "_DRAFT"). Files are promoted to the released folder only after formal review and approval.
- Archive folder: Superseded revisions are moved here when a new revision is released. Files are renamed to include the revision designation (e.g., "part-12345_RevA.pdf") and never deleted.
File Naming Conventions
File names should encode the drawing number and revision at minimum. A consistent naming convention that can be sorted and searched programmatically saves significant time in a large drawing library. Example convention: [PROJECT]-[DRAW_NUMBER]_[REVISION].[EXT] → PRJ001-12345_RevC.pdf. Native CAD files (SLDPRT, PRT, STEP) should follow the same convention. Avoid spaces and special characters in file names — they cause problems in automated systems and some operating environments.
Change Control Process
For drawings in production use, changes must follow a formal process. The process exists to ensure that changes are reviewed before implementation, that affected parties are notified, and that the change history is documented. A minimal change control process for a small engineering team has four steps:
- Change request: Anyone can initiate a change request. The request identifies the drawing, the proposed change, and the reason. Verbal change requests are not valid — they leave no trail.
- Technical review: The responsible engineer reviews the proposed change for technical correctness, impact on adjacent parts and assemblies, and compliance with applicable standards. This is where downstream effects (supplier parts, field inventory, assembly instructions) are identified.
- Approval: An authorized approver signs off on the change. For production drawings, this should require a second engineer in addition to the originator.
- Release and notification: The revised drawing is released to the controlled folder, superseded revisions are archived, and affected stakeholders (manufacturing, purchasing, quality) are notified.
FAQ
Q: What is the minimum viable drawing control system for a small team without PLM software?
A controlled network folder with write access restricted to a single administrator, a consistent file naming convention, a revision block on every drawing, and a simple shared log (spreadsheet or shared document) of all released revisions. This is not ideal, but it prevents the most damaging failures: manufacturing to old revisions and losing the history of what changed. Add a formal ECO process as soon as workload permits.
Q: How should I handle a situation where a drawing was changed without going through the revision process?
Treat it as a nonconformance. Issue a corrected revision through the formal process, documenting both the actual change and the fact that it was made without proper change control. Do not silently absorb the unauthorized change into the next legitimate revision — the change history must be accurate and complete even when the process was not followed correctly.
Q: At what point does a project need PDM or PLM software instead of manual file management?
When any of the following occur: drawing library exceeds several hundred documents, multiple designers are working on the same assembly simultaneously, supplier data management is required, or product releases require formal configuration control audits. PDM systems solve the multi-user concurrency and access control problems that manual file management cannot reliably handle at scale.
コメント