As a SolidWorks project grows, keeping track of parts, assemblies, and drawings can become difficult. Files may be saved in different folders, teammates may work from outdated copies, and it can be hard to tell which version is ready to use.
SolidWorks Product Data Management (PDM) helps teams organize and control those files. This guide covers the basics: what PDM does, how its workflow works, and a few habits that make it easier to use.
What is SolidWorks PDM?
SolidWorks PDM is a system for storing and managing design files in a shared vault. A vault is a controlled location for parts, assemblies, drawings, and related documents.
PDM helps a team:
- Find design files in one organized place
- Track changes and previous versions
- See who has a file checked out
- Keep references between parts, assemblies, and drawings together
- Route files through review and approval steps
PDM manages files and their history. SolidWorks remains the tool used to create and edit the models.
How a PDM vault works
A PDM vault is not just a shared folder. It also stores information about files, their versions, and their workflow status.
You usually access vault files through a local view on your computer. This view lets you browse the vault in File Explorer and work with files using SolidWorks. PDM keeps track of file operations such as checking out, checking in, and changing a file’s state.
The vault’s setup can vary by company. Folder structure, permissions, revision labels, and approval steps are typically configured to match the team’s process.
The basic PDM workflow
1. Get the latest version
Before editing a file, get the latest version from the vault. This helps ensure you are working with the current approved or shared copy.
If your work involves an assembly, check that the referenced parts and subassemblies are also available in the versions you need.
2. Check out the file
Checking out a file tells PDM that you are working on it. Depending on the vault’s settings, other users may still be able to view the file, but they generally cannot check out the same file for editing at the same time.
Check out only the files you need to change. For an assembly edit, consider which components actually need modifications.
3. Make and save your changes
Open the file from the vault view and make your changes in SolidWorks. Save as you normally would.
When assemblies reference other files, use PDM-aware actions where possible so that references remain connected to the correct vault files.
4. Check in the file
When you check in a file, PDM saves your changes to the vault and creates a new version. Add a clear comment describing what changed, such as “Updated mounting hole spacing” or “Added drawing dimensions.”
A useful comment makes the file history easier for teammates to understand.
5. Change the file’s state when needed
Many vaults use workflow states such as Work in Progress, For Review, and Approved. A state change can move a file to the next step in the team’s review process.
The exact state names and permissions depend on how the administrator configured the vault.
Versions and revisions are different
PDM often tracks both versions and revisions:
- A version records each check-in of a file. It helps track ongoing edits.
- A revision identifies a formal release or milestone, often using labels such as A, B, or C.
For example, a file may have several internal versions while it is being developed, then receive a new revision after approval. The labels and rules vary by organization, so follow your team’s process.
Good habits for a clean vault
- Check that you have the latest files before editing. This reduces the chance of making changes based on old data.
- Use clear file names and folder locations. Follow the team’s naming conventions rather than inventing your own.
- Write useful check-in comments. Describe the change, not just “updated.”
- Check in completed work promptly. This makes your changes available to others and keeps the vault history current.
- Be careful when renaming or moving files. Use PDM tools so references can be updated correctly.
- Avoid keeping project files outside the vault without a reason. Local copies can become disconnected from the tracked version.
- Ask before changing shared or released files. Your team may have a specific process for revising approved designs.
Common beginner mistakes
Editing a file without checking it outYou may be working on a local copy without reserving the file for editing. Check the file’s status in PDM before making changes.
Renaming files outside PDMRenaming a part directly in File Explorer can break references in assemblies or drawings. Use the vault’s rename or move tools when available.
Using “Save As” carelesslySaving a copy under a new name can create duplicate files or leave an assembly pointing to the old part. Follow your team’s process for creating new designs and replacing components.
Checking in without a commentA blank or vague comment makes it harder for others to understand why a new version exists. Include a short description of the change.
Assuming a checked-in file is approvedChecking in saves a version to the vault, but it may not mean the file has completed review. Check the file’s workflow state before using it as a released design.
Start with a simple routine
For everyday work, remember this sequence:
PDM can feel unfamiliar at first, especially when a vault has custom rules. Once you understand how your team handles checkouts, versions, and approvals, it becomes much easier to find the right files and work confidently with others.
SOLIDWORKS Mastery Pack – 11 Courses in 1 | Complete Beginner-to-Industry Training
This all-in-one SOLIDWORKS Mastery Pack combines 3 comprehensive video courses with 8 project-based eBooks, providing a structured learning path from SOLIDWORKS fundamentals to advanced mechanical design, sheet metal, assemblies, engineering drawings, and practical project-based learning.
- Master SOLIDWORKS from Scratch
- Design Real-World Projects
- Master Industry-Ready Sheet Metal
- Build a Job-Ready CAD Portfolio