What is SOLIDWORKS PDM? Modules, integrations and alternatives
SOLIDWORKS PDM is Dassault Systemes' product data management system for controlling CAD files and related engineering documents in a secured vault. It adds check-in/check-out, revision control, lifecycle workflows and bill of materials views to teams that design in SOLIDWORKS and other CAD tools. It is offered in Standard and Professional editions that differ mainly in scale and capability.
Also known as: SOLIDWORKS Product Data Management, SolidWorks PDM Professional, SolidWorks PDM Standard, SWPDM, EPDM, Enterprise PDM
SOLIDWORKS PDM replaces shared network folders and manual file naming with a controlled vault. Engineers check files out to a local cache, edit them, and check them back in as new versions. The system tracks who changed what, keeps references between assemblies, parts and drawings intact, and prevents two people from overwriting each other's work.
Beyond version control, the product models how engineering data matures. Files carry variables stored on data cards, such as part number, description, material and revision. Workflows define states like In Work, Pending Approval and Released, with transitions that require specific users or groups to approve. A released drawing can be locked read-only and a new revision can be started in a controlled way.
In a manufacturing stack, SOLIDWORKS PDM sits between engineering and the rest of the business. The ERP usually owns the item master, costing and purchasing, while PDM owns the CAD files and the engineering view of the bill of materials. Many shops push released part and BOM data from PDM into the ERP through the PDM API, exported files or a middleware layer, and pull back ERP-assigned numbers. How automated that handoff is varies widely by implementation.
Modules and capabilities
File vault
A server-side archive with a database that stores versions of CAD files and documents, presented to users as a vault view in Windows Explorer.
Check-in, check-out and versioning
Controls who can edit a file, keeps every saved version, and maintains the links between parent and child files.
Workflows and states
Configurable lifecycle states and transitions with permissions, notifications and automated actions on state change.
Data cards and variables
Forms that capture metadata on files and map it to CAD custom properties and BOM columns.
Bill of materials
Computed and saved BOM views from assemblies, with configurable columns and export for downstream systems.
Search and where-used
Search by metadata and content, plus where-used and contains views to understand the impact of changing a part.
Web access and viewers
Browser-based access and lightweight viewing for people who do not run CAD, depending on edition and configuration.
Tasks and automation
Add-ins and task tools for conversion to PDF or neutral formats, printing and other batch actions triggered by workflow.
Integrations and data access
SOLIDWORKS and CAD
Deep integration with SOLIDWORKS through an add-in that handles file references, custom properties and configurations. Other CAD formats can be stored as files but with less intelligent reference handling.
PDM API
A programmable API lets developers automate vault operations, read variables and BOMs and build custom add-ins, commonly used to feed ERP item and BOM interfaces.
ERP and BOM export
BOMs can be exported to files such as XML or CSV, or pushed by integration code or middleware into ERP systems such as SAP, NetSuite, Infor and others, with the mapping designed per project.
SQL database
Metadata lives in a Microsoft SQL Server database. Direct reporting against the database is possible but should respect vendor guidance and be read-only.
Neutral formats
Tasks can generate PDF, STEP, DXF or similar outputs on release so downstream teams and suppliers receive controlled copies.
Strengths
- Tight fit with SOLIDWORKS, so reference handling and custom property mapping work with little friction.
- Familiar file-system style experience that engineers tend to adopt quickly.
- Flexible workflows and data cards that can be shaped to local release procedures.
- A documented API that supports custom ERP and manufacturing integrations.
- Scales from a small team to multi-site use depending on edition and architecture.
Limitations
- Strongest for SOLIDWORKS-centred data; mixed multi-CAD environments need more design effort.
- It is a PDM, so formal change management, supplier collaboration and multi-BOM lifecycles may call for a fuller PLM product.
- Server, database and replication planning for multi-site use needs real administration skill.
- ERP integration is not automatic and is usually a project in its own right.
Where AI helps SOLIDWORKS PDM users
- - Natural-language search across vault metadata, such as finding released assemblies that use a given material or fastener.
- - Summarizing revision and workflow history on a part to speed engineering change reviews.
- - Checking that BOM data pushed to the ERP matches released PDM data and flagging mismatches for a human to resolve.
- - Drafting ERP item-creation records from data card values for engineer approval before anything is written.
- - Answering where-used questions in plain language to assess the impact of a proposed change.
Evaluating SOLIDWORKS PDM? Check these
- Confirm which edition fits your user count, sites and need for replication before sizing hardware.
- Decide early which system owns the part number and how it is generated, PDM or ERP.
- Define the release workflow on paper first, including who approves and what gets exported on release.
- Plan the ERP interface scope: item master only, full BOM, or documents too, and who maintains the mapping.
- Test with a realistic set of assemblies, including configurations and legacy files, during migration.
- Check your reseller's experience with your ERP, not only with SOLIDWORKS.
Common alternatives: Autodesk Vault, PTC Windchill, Siemens Teamcenter, Aras Innovator, Arena PLM, Onshape (built-in data management).
Frequently asked questions
What is SOLIDWORKS PDM used for?
It stores and controls engineering files in a secured vault, tracks versions and revisions, and manages release through approval workflows. Teams use it to avoid overwritten files, find the right revision quickly, and give manufacturing a trusted source of released drawings and bills of materials.
What is the difference between SOLIDWORKS PDM Standard and Professional?
Standard targets smaller, usually single-site teams and uses a lighter database engine, while Professional supports larger deployments with more scale, replication options and extra capabilities. Exact feature sets and limits change over time, so check current vendor documentation or ask a reseller before deciding.
Can SOLIDWORKS PDM integrate with an ERP system?
Yes, but through configuration and development rather than a single built-in connector. Common approaches use the PDM API, exported BOM files, or middleware to send released items and structures to the ERP. The ERP typically keeps costing and purchasing, while PDM remains the source for CAD files.
Is SOLIDWORKS PDM the same as PLM?
Not exactly. PDM focuses on controlling CAD files, revisions and release. PLM covers a wider lifecycle, including formal change management, supplier collaboration and requirements. Some companies start with PDM and add PLM later; others find PDM with disciplined processes is enough.
Does it only work with SOLIDWORKS files?
No, it can store any file type, including other CAD formats and office documents. However, the richest behavior, such as automatic reference tracking and property mapping, is for SOLIDWORKS. Other CAD systems may be handled with less automation or through separate integrations.
Running SOLIDWORKS PDM?
We add AI, chat, automation and integrations to the systems manufacturers already run, on-prem if needed.
Get a free assessment