Everything Your Team Needs To Know About SOLIDWORKS PDM
If your engineering team is storing SOLIDWORKS files on a network drive, a local hard drive, or a general-purpose cloud storage service like OneDrive or Dropbox, you are managing product data in a way that was not designed for CAD. It works until it does not. And when it stops working, the cost shows up in lost data, broken assemblies, and time spent tracking down which version of a file is the right one.
SOLIDWORKS PDM was built to solve exactly that problem. This post explains what it is, whether your team needs it, what implementation actually looks like, and how to choose between Standard and Professional.
What Does SOLIDWORKS PDM Actually Do?
PDM stands for Product Data Management. In the SOLIDWORKS context, it is a secure, structured vault for your CAD files. Every part, assembly, drawing, and related document lives in that vault, and the system manages how people access, edit, and track changes to those files.
Four things distinguish PDM from saving files to a shared drive.
Version and revision control
Every time someone saves a change to a file, PDM records it. You can retrieve any previous state of a design. When a file is approved for production, it can be locked so no one can edit it without creating a formal new revision. That history does not disappear. Six months later, if a customer asks what the product looked like when it shipped, you can pull that exact version in seconds.
Check-in and check-out
When an engineer opens a file to edit it, PDM checks it out and reserves it. Other people can still view it, but only one person has edit control at a time. When they are done, they check it back in and the updated version is available to the team. This eliminates the scenario where two engineers unknowingly work on the same part simultaneously and one of them loses their work.
Reference management
SOLIDWORKS files reference each other. A drawing references a part. An assembly references dozens of parts. If someone moves or renames a file outside of PDM, those references break. PDM handles file moves and renames properly so references stay intact across the entire data set.
Access control and approval workflows
You decide who can view, edit, and approve files. Shop floor employees can be set up as viewers so they always have access to the current released drawing without being able to modify anything. Approval routes can require sign-off from the right people before a design is released to production.
Why Your Current Setup Is Riskier Than You Think
Engineering managers often push back on PDM with a version of the same question: we have been doing it this way for years and it has mostly worked. Here is what each of the most common storage approaches actually exposes you to.
Local hard drive
Best performance, highest risk. If the drive fails or the laptop is lost, the data is gone. No version history, no backup structure.
Network drive
Better than local, but still problematic for CAD. Saving and opening large assemblies over a network connection is slower than local storage. If the connection drops mid-save, file corruption is a real risk. VPN access slows this down further for remote engineers.
OneDrive, Dropbox, Google Drive
These tools work reasonably well for a single person. As soon as you add a second engineer, problems emerge. SOLIDWORKS stores files with references that point to specific file paths. Different users have different local cache paths, which means the same file on OneDrive lives at a different path on each machine. References break. Additionally, the constant background syncing these platforms do can conflict with SOLIDWORKS file operations and increase the chance of corruption.
PDM combines the best of both approaches: you work on a local copy for fast read-write performance, and when you check in your changes, they are pushed to the server with a full backup and version record.
A Real-World Example
A small product development company came to us struggling with a problem that sounds minor until it is not: duplicate file names. They had been building products for years, and their file structure had accumulated multiple versions of the same part number in different folders. A quarter-inch socket head cap screw in passivated stainless and the same part in black oxide steel had the same file name in different directories. There was no way to know at a glance which was which.
Implementation of PDM resolved the duplication problem immediately because the system checks for duplicate file names across the entire vault, not just within a folder. What had been invisible before became obvious and fixable. They had the system up and running with users trained within a week, and they now have a structure that prevents new duplicates from being created.
How Implementation Works
Implementation has a few moving parts that are worth understanding before you commit to a timeline.
Server infrastructure
Traditional SOLIDWORKS PDM runs on a server that you host on-premise. There are two components: the database server (which runs SQL) and the archive server (which stores the actual files). For smaller teams, these can run on the same machine. Larger deployments with more users and data often benefit from separating them. PDM Standard uses SQL Express, which is free. PDM Professional requires a paid SQL Server license.
Data migration
Before moving files into the vault, it is worth assessing what you have. The main issues to look for are broken references and duplicate file names. Broken references are assemblies that point to parts that have been moved or renamed outside of SOLIDWORKS. Duplicate file names will cause problems on import. Both can be identified and resolved before migration. SWYFT works through this process with customers as part of implementation, running checks and cleaning up data before it enters the vault.
You do not have to migrate everything at once. Some teams migrate active projects first and pull in legacy data as they need it.
Access configuration
Before the system goes live, you define who gets what level of access. The three types are CAD editors (engineers actively working in SOLIDWORKS), contributors (non-SOLIDWORKS users who need to edit properties or manage non-CAD documents), and viewers (shop floor or procurement staff who need to see current released drawings but not edit anything). Viewers come in at a lower license cost, which matters when you are adding access across a manufacturing floor.
PDM Standard vs. PDM Professional
PDM Standard is included with SOLIDWORKS Professional and Premium licenses under standalone and network licensing. PDM Professional is a separate purchase that is not bundled with any SOLIDWORKS license.
Standard covers the core functionality: check-in and check-out, revision control, basic workflow, and SOLIDWORKS file management. For a smaller team that primarily needs version control and wants to avoid broken references, Standard is often sufficient.
Professional adds several capabilities that matter as teams and complexity grow.
• More sophisticated approval workflows with multiple stages and conditions
• Automatic part numbering
• Broader file type support so you can manage PDFs, Word documents, and Excel files in the same vault alongside your CAD data
• Web portal access for reviewing data without installing the PDM client
• More extensive API access for custom automation
One important note: if your team is on named user licensing (SOLIDWORKS Design subscriptions rather than standalone perpetual licenses), PDM Standard is not included. In that scenario, all subscription license tiers do include SOLIDWORKS Cloud PLM, which delivers similar core capabilities in a fully cloud-hosted environment with no server infrastructure required. It is worth understanding which licensing model you are on before planning your data management strategy.
The Most Common Implementation Mistakes
Two mistakes come up consistently when teams try to set up PDM without experienced help.
The first is not configuring backups. The server stores your vault data, and if that server is not being backed up properly, you have recreated the same risk you were trying to escape. Backup configuration is not complicated but it is easy to overlook if you are working through an install guide for the first time.
The second is file naming collisions during migration. If you have duplicate file names in your current structure and you do not address them before importing, the migration process will surface those conflicts in a way that takes time to untangle after the fact. Dealing with them beforehand is much cleaner.
Both of these are non-issues when you go through implementation with a partner who has done it dozens of times. SWYFT handles the server setup, backup configuration, data integrity checks, and user training as part of the implementation process.
Is PDM Right for Your Team?
If you have more than one person working in SOLIDWORKS and you are producing products that matter, PDM is worth it. The version control, reference protection, and access structure it provides are not features that add overhead. They are risk management for your engineering data.
If you are a single engineer and your file structure is clean, you may be fine without it for now. But as you add engineers or move from prototype to production, PDM becomes the right infrastructure to have in place before the problems it prevents start showing up.
Questions about whether your setup is the right fit for PDM Standard or Professional? Reach out to the SWYFT Solutions team. We will walk through your file structure, team size, and workflow to give you an honest recommendation.