AI for CAD Tools
What SolidWorks PDM actually does: how the vault, check-in/check-out, and workflows work, and how Standard, Professional, and SolidWorks Manage differ.
·
⏱
7 min read
Michelle Ben-David
Michelle Ben-David is a mechanical engineer and Technion graduate. She served in an IDF elite technology and intelligence unit, where she developed multidisciplinary systems integrating mechanics, electronics, and advanced algorithms. Her engineering background spans robotics, medical devices, and automotive systems.
BOTTOM LINE
SolidWorks PDM is a vault-based data management system built into Windows Explorer that controls who can edit a file and tracks every version of it, using check-out and check-in rather than shared-drive folders. Workflows route files through approval states like Work in Progress, Under Review, and Released, and revisions typically bump when a workflow transition fires. PDM Standard, bundled free with SolidWorks Professional and Premium seats, covers a single workflow and a handful of concurrent users; PDM Professional is a separate purchase built for multiple workflows, larger teams, browser access, and ERP integration. SolidWorks Manage extends a PDM Professional vault with project management and advanced BOM tools rather than replacing it. The right tier depends on how many workflows and concurrent users a team actually runs, not how the two are marketed.
Ask five engineers what SolidWorks PDM does and the answers rarely agree. Some call it a fancy shared drive. Others call it version control for CAD files. Both are true in the narrowest sense, and both miss what actually changes once a team turns it on.
SolidWorks PDM is Dassault Systemes’ data management add-on for SolidWorks, and it answers a question a shared folder cannot: which copy of this file is the real one, and who is allowed to touch it right now. That sounds small until a team has lived without it, tracking revisions in filenames and finding out too late that two engineers edited the same assembly at once. This piece lays out what SolidWorks PDM actually does day to day, how its vault, check-in and check-out, and workflows fit together, what separates PDM Standard from PDM Professional and where SolidWorks Manage fits in, and how to tell which tier a team actually needs.
What SolidWorks PDM Actually Is
SolidWorks PDM lives inside Windows Explorer rather than as a separate application, which is part of why teams underestimate it before they use it. Every managed file, CAD models, drawings, spreadsheets, and any other document a team chooses to include, sits in a vault: a centralized, server-based repository that every user’s PDM client connects to. What appears on an engineer’s own machine is a local view, a working copy synced from that vault rather than the file itself.
That structure solves a problem a shared network drive cannot. A folder of files has no memory of who changed what or when, no way to stop two people from overwriting each other’s work, and no reliable record of which version actually shipped. A vault handles all three: it tracks every version of every file, it enforces who can edit a file at a given moment, and it keeps the full history, including old revisions, available to pull back if a change needs to be undone. None of that requires a separate database an engineering team manages by hand. It runs quietly behind the file browser they already use.
IN PRACTICE
It integrates directly with PLM and existing workflows, making past designs, standards, and calculations instantly available. The result is fewer errors, faster decision-making, and a more consistent process across teams.
- Sergey G., Board Member
How Files Move Through the Vault: Check-Out, Check-In, and Versioning
The mechanic that makes a vault different from a folder is check-out and check-in. Checking out a file copies it from the vault to an engineer’s local view and gives that engineer exclusive editing rights until it comes back in. Everyone else can still open the file to view or reference it, but PDM blocks a second person from saving conflicting changes over the top.
Checking a file back in copies the edited version back to the server. If the content actually changed, PDM creates a new version rather than overwriting the old one, so the prior version is never lost. Saving a file locally, without checking it back in, only updates the copy on that one machine. The vault does not see the change until check-in happens, which is the detail that trips up teams new to PDM: a file can look finished on someone’s desktop and still be several versions behind for everyone else.
Every check-in can carry a comment describing what changed, and PDM keeps that comment attached to the version permanently. Combined with the version history, that turns a vault into a searchable record of a part’s design history, not just its current state, which is the piece a shared drive with version numbers in filenames can never replicate reliably.
Workflows and Revisions: How Approval Actually Happens
Checking a file in and out controls editing. Getting a design released for manufacturing or handed to a supplier is a separate problem, and that is what PDM workflows solve. A workflow defines the states a file can pass through, for example Work in Progress, Under Review, and Released, along with the transitions allowed between them and who has permission to approve each move.
Moving a file to its next state, typically done with a right-click Change State action, can require the file to be checked in first, can notify specific reviewers automatically, and can trigger actions like generating a PDF or updating a property. None of that depends on a spreadsheet of approvals or an email thread someone forgets to close, and none of it relies on an engineer remembering to tell manufacturing that a part changed.
Revisions sit on top of workflows rather than replacing them. A workflow transition, most often the move into a Released state, is usually what triggers a revision bump, and PDM can generate the next revision label automatically according to whatever scheme a company uses: letters, numbers, or a mixed scheme tied to major and minor changes. The result is a revision history that reflects actual approvals, not whatever an engineer typed into a title block before saving.
SolidWorks PDM Standard vs Professional (and Where SolidWorks Manage Fits)
SolidWorks PDM ships in two tiers, and the gap between them is bigger than a feature checkbox suggests. PDM Standard runs on Microsoft SQL Server Express, caps out around a 10 GB database, and is realistically built for three to five concurrent users before performance becomes a problem. It supports exactly one workflow with up to ten states, offers basic revision control, and is accessed only through the desktop client.
PDM Professional runs on the full Microsoft SQL Server Standard edition, scales to far larger vaults and user counts, and supports multiple workflows with unlimited states and transitions, which matters the moment more than one department needs its own approval path. It adds automatic serial and part number generation, a browser-based Web2 client for suppliers or reviewers who do not need full CAD access, basic bill of materials management, task automation, and an API for connecting to an ERP or MRP system. Our PDM vs PLM comparison covers where PDM’s job ends and a full PLM system’s begins, which is a separate question from Standard versus Professional.
SolidWorks Manage is a distinct product that connects to a PDM Professional vault rather than replacing it. It adds project management with Gantt-style scheduling, advanced BOM variants, process management for engineering change orders, and real-time dashboards, aimed at teams that need PDM’s file control plus visibility into the broader product development process. A team cannot run Manage on top of PDM Standard; the underlying vault has to be Professional. Our comparison of PDM software options looks at how these tiers stack up against alternatives outside the SolidWorks ecosystem.
Licensing and Who Actually Needs It
PDM Standard is not sold on its own. It comes bundled with every SolidWorks Professional and SolidWorks Premium seat, which is why many teams already own it without realizing it. PDM Professional is a separate purchase, licensed through Editor, Contributor, and Viewer seats, or through Universal Licensing packs of 25, 50, 100, or 200 units that let an organization reassign license types across CAD users, non-CAD contributors, and view-only stakeholders as needs shift.
The honest answer to which tier a team needs comes down to how many people touch the vault and how many approval paths a company actually runs. A small team on one workflow, one product line, and under five concurrent users can live on Standard for a long time. The moment a company needs a second workflow for a different department, more concurrent users than Standard’s SQL Express database handles well, or supplier access through a browser instead of a full CAD seat, Professional stops being optional.
None of this changes what a vault cannot do on its own: help someone find a part that already exists, or explain why a tolerance was set a particular way five revisions ago. Leo sits as an intelligence layer on top of PDM systems including SolidWorks PDM, searching across a vault’s structured data and connected files rather than replacing the vault itself, so a workflow that already enforces who can edit and approve a file also becomes one where past decisions stay findable instead of disappearing into old revisions. Our look at why PDM search breaks down, our framework for evaluating AI tools on PDM, and our SolidWorks PDM-specific criteria all dig into that gap in more depth.
FAQ
Bring AI Search to Your PDM Vault
Find parts and past decisions already sitting in your vault.
Leo connects to SolidWorks PDM and other PDM and PLM systems to search across your vault's files, standards, and past designs in plain language.
Schedule a Demo →
#1 New AI Software Globally - G2 2026
Enterprise-grade security
Trusted by world-class engineering teams
