Revision control is where the hours actually go
Ask an engineering team where their week disappears and nobody says "modelling". They say: finding the right file, working out which drawing the shop floor is holding, and redoing a change because someone edited a part that was supposed to be frozen.
Those are not discipline problems. They are configuration problems — and every one of them is solvable inside SOLIDWORKS PDM. Get revision control set up properly once, and the time you stop losing every single week is substantial.
First, separate version from revision
This is the root of most confusion, so it is worth stating plainly:
- Version — every check-in creates one automatically. Version 1, 2, 3, 4… It is a safety net. It is invisible to the shop floor and nobody should ever quote it.
- Revision — a deliberate, human-meaningful milestone. A, B, C or 1, 2, 3. It means "this was approved and released". It goes on the drawing and into the ERP.
PDM gives you versions for free. Revisions are a decision you make — and that decision lives in your workflow, not in your folder structure.
Practice 1: Decide the revision scheme before you build anything
Two questions, answered on paper, before a vault exists:
- Letters or numbers? Most discrete-manufacturing teams use letters (A, B, C) for released revisions and reserve numbers for pre-release iterations. Regulated industries often need a numeric scheme to match a customer or auditor's expectation.
- Does your customer or quality system dictate it? If your drawings are scrutinised in an aerospace, medical or automotive PPAP audit, the scheme is not yours to choose freely. Find that out now, not after 8,000 files are at revision C.
Changing a revision scheme after go-live is possible but painful: every historical file has to be reconciled. Thirty minutes of planning at the start saves days later.
Practice 2: Increment the revision on the transition that means something
The single biggest design decision in a PDM workflow: when does the revision increment?
There are two schools of thought, and both work — as long as you pick one and apply it consistently:
- Increment on approval. The file sits at its old revision while under modification, then jumps to the next revision on the transition into Released or Approved. This is how PDM is designed to work out of the box, and it keeps the data card and the drawing title block in sync at all times.
- Increment on change start. As soon as a released part is pulled into rework, it becomes revision B immediately, so everyone knows a change is underway. Some teams prefer this because the revision on the data card reflects "what is being worked on". The trade-off is that the title block can then disagree with the physical file until approval, so you must add the workflow state to the data card next to the revision to avoid ambiguity.
What definitely does not work: incrementing on some transitions and not others, or leaving it to engineers to change the revision property by hand. That is how you get two revision Bs with different geometry.
Practice 3: Drive the drawing title block from the vault, never from typing
If an engineer types the revision into a title block, it will eventually be wrong. Map the revision variable to the title block once, so the drawing reads it from the PDM data card automatically.
The chain to get right, in order:
- Create the revision number in the vault (Administration tool → Revision numbers).
- Attach it to the target state — Released, Approved — in the workflow's Revisions tab.
- On the incoming transition, set the increment value, and add the two actions in the correct order: Increment Revision first, then Set Revision. Reverse the order and your data card variable will land on the wrong value.
- Link the data card variable to the SOLIDWORKS custom property that the title block reads.
Then test it: push one part through the full cycle three times and confirm that the revision increments on the file, the data card, the drawing and the History tab all agree. Ten minutes of testing here prevents months of "the drawing says C but the vault says D".
Practice 4: Keep the workflow short enough that people actually follow it
A workflow with fifteen states looks thorough and behaves like a maze. Aim for five to seven states that map to real, distinguishable stages: In Work, In Review, Released, In Change, Obsolete. If two states have never required a different action or a different approver, merge them.
Every state should answer one question: who can touch this file right now? If the answer is "everyone", the state is not doing any work.
Practice 5: Make Released genuinely immutable
Revision control only holds if Released is a locked door. Permission the state so that editing requires either a checkout by a named owner or a transition into In Change. A released file that anyone can quietly modify is a released file you cannot trust — and trust is the entire point.
Pair this with a mandatory comment on the change transition. Two fields on one dialog box gives you an audit trail that costs seconds to create and answers the auditor's question months later: who changed it, when, and why.
Practice 6: One part number, one file, generated not chosen
Free-text part numbers produce BRACKET-01, bracket 1, BRACKET_REV2_final and three copies of the same geometry. Configure a serial-number generator in the data card so the number is issued by the vault. Then no naming convention argument can go wrong, and where-used will actually work.
For teams on PDM Standard the fixed workflow limits how far you can go here — a starter vault is the right comparison, and this is usually the first thing customers want changed.
Practice 7: Publish the derivative files as part of the release, not after it
If PDFs go to the shop floor and DXF goes to the laser cutter, those exports are revision-controlled data too — and a PDF that does not match its release is exactly how a wrong part gets made.
In PDM Professional you can attach PDF/DXF publishing to the release transition, so the neutral file is generated from the approved model at the same instant the revision increments. That single automation typically removes a recurring hour or two a week per project for a busy design office, and removes the "which PDF is current?" conversation entirely.
Practice 8: Review the vault like a process, not a project
Revision control decays quietly. Once a quarter, check:
- Files released without a transition — signs someone bypassed the workflow
- Overlaps: more than one file at the same part number and revision
- Stale checkouts held for weeks
- Obsolete files still being referenced by live assemblies
Most PDM setups ship reports that make this a fifteen-minute job. It is much cheaper than discovering the problem during an audit or, worse, during assembly.
Standard or Professional — what revision control actually needs
Both tiers do check-in/check-out, versioning and basic workflow, and PDM Standard is included with active SOLIDWORKS subscription up to ten CAD-Editor seats, which makes it the natural first step off the shared drive.
The revision-control features that typically force an upgrade to PDM Professional:
- Custom workflows with branching and parallel approvals — needed for a real ECO process where mechanical, electrical and quality sign off independently
- Serial-number generators and configurable data cards for part numbering
- Automated PDF/DXF publishing on release
- Full-text search and Web2 access for people outside engineering
- Multi-site replication, if drawings are being released from more than one office
An honest rule of thumb: if the requirement is "stop losing files and know which revision is current", Standard is enough. Once there is a formal change board, a second site, or an audit that expects signatures, it is Professional.
The checklist
- Revision scheme chosen and documented — letters, numbers, or customer-mandated
- Revision increments on one clearly defined transition, consistently
- Title block variable mapped to the data card — nobody types a revision
- Workflow five to seven states, each with a clear permission set
- Released state locked; changes require a transition and a comment
- Part numbers issued by a serial-number generator
- PDFs and neutral formats published automatically at release
- Quarterly vault review on the calendar
None of this is complicated. It is just the difference between a vault that is a storage location and a vault that is a controlled process — and that difference is measured in hours.
Running SOLIDWORKS PDM already and not sure your revision scheme is doing its job? Our team can review your workflow and tell you where the leaks are.