What should a machine shop complete before implementing SOLIDWORKS PDM?
Complete the business rules before the server work. Name an accountable owner, inventory the files and references, define revision and release workflows, map permissions, prepare the infrastructure, test a representative pilot, rehearse cutover and rollback, then train users on their actual jobs. A technically functioning vault is not the same thing as a production-ready system.
Engineering managers, CAD administrators, manufacturing engineers, IT owners, and machine-shop leaders planning a first PDM Standard or PDM Professional vault.
Exact server sizing, SQL configuration, authentication, backups, integrations, and licensing must be reviewed for the selected release and environment with qualified IT and your SOLIDWORKS reseller.
Start with ownership, not folders
A PDM project crosses engineering, programming, quality, purchasing, and IT. If every decision belongs to a committee, small questions about revisions or permissions sit unanswered while configuration continues around them. Name one executive sponsor, one day-to-day vault owner, one technical administrator, and a process owner for each workflow that will approve released data.
Write the success criteria in operational terms. “Install PDM” is not measurable. “A programmer can open the released model and drawing for job 4382, identify the current revision, see who approved it, and avoid an obsolete copy” is measurable. Add response-time expectations, backup recovery objectives, and the few reports or searches the team must use on day one.
Decide which business problems are inside the first release. Revision control, engineering release, controlled PDFs, and search may belong in phase one. Automated ERP exchange, complex dispatch scripts, or every historical file may be later phases. A smaller vault with enforced rules is more valuable than a broad vault whose rules are still changing.
| Role | Decision it owns | Evidence before build |
|---|---|---|
| Executive sponsor | Scope, priority, conflict resolution, and go-live authority | Signed scope and success criteria |
| Vault owner | Daily administration, user requests, and standards | Named primary and backup administrator |
| Process owner | States, transitions, approvals, and exceptions | Approved workflow map |
| IT owner | Servers, SQL, identity, security, backup, and monitoring | Supported architecture and recovery plan |
| Pilot users | Real-job testing across roles | Representative files, tasks, and acceptance steps |
Inventory the data that has to behave correctly
Do not begin with a blind copy of the shared drive. Scan file types, sizes, duplicate names, duplicate content, broken references, external references, toolbox and library locations, templates, macros, PDFs, NC files, inspection documents, and files that belong to customers or suppliers. Separate active production data from reference libraries and archive material.
SOLIDWORKS assemblies expose weak data hygiene quickly. The same fastener may exist under three names, a drawing may point into a programmer’s desktop, or two customers may use the same part number. These are business decisions, not copy errors. Decide what becomes authoritative, what gets renamed, what remains read-only, and what stays outside the vault before import rules are written.
Build a migration register with source path, destination path, owner, file count, size, reference result, duplicate decision, and validation status. That register becomes the cutover control sheet and prevents “everything was moved” from replacing actual evidence.
- Freeze new folder structures and naming experiments during discovery.
- Identify files owned by CNC programmers, quality, and the shop floor, not only engineering.
- Record software versions needed to open or convert legacy files.
- Choose whether released deliverables such as PDF, DXF, STEP, and neutral manufacturing files are generated, stored, or both.
- Define handling for personal work, obsolete files, customer-controlled data, and records with retention requirements.
Configure the minimum system that enforces the process
The official installation guidance separates the SQL database, archive server, database server, license manager, and optional web components because they perform different jobs. The vault design should also keep concerns separate: folders express broad organization, data cards hold searchable metadata, workflows control maturity, and permissions limit what roles can see or change.
Use the smallest number of states and transitions that still reflects how work is released. SOLIDWORKS 2026 Help limits PDM Standard to one workflow with no more than ten states, while PDM Professional supports multiple workflows and additional automation, integration, and administration capabilities. An implementation plan that assumes Professional-only behavior can fail before configuration begins if the quoted edition is Standard.
Test permissions as the actual role, not only as Admin. A programmer should be able to retrieve the released manufacturing package without accidentally editing it. A reviewer should see the information required for approval. A contractor or viewer should not inherit broad rights through an unexpected group. Record the expected result for every role and test case.
The first vault is a production system
Treat configuration exports, archive settings, SQL data, physical archives, service accounts, and license dependencies as controlled assets. The backup design and an isolated restore rehearsal belong in the implementation plan, not in a later maintenance list.
Pilot complete jobs, including the awkward ones
Choose a pilot set that includes a normal assembly, a drawing revision, a purchased component, a library part, a file with an external reference, and one job that crosses engineering and manufacturing. Add a negative case such as a rejected approval, missing metadata, duplicate filename, or broken reference. The pilot should expose process edges while the cost of correction is still low.
Run the work as users will run it after launch. Check files out, edit them, update references, submit for approval, create the released deliverable, retrieve the right version from another workstation, and search by the fields the team says it needs. Time the steps that matter, but prioritize correct data and unambiguous status over a fast demonstration.
A useful acceptance record includes the test job, PDM edition, user role, client and server version, expected result, actual result, evidence file, issue owner, and retest result. Close severe issues before cutover. Put lower-risk requests into a visible backlog so they do not quietly become go-live assumptions.
Build a representative job set
Include normal work, exceptions, cross-department handoffs, and at least one intentionally bad input.
Test with real roles
Use engineering, manufacturing, quality, viewer, and administrator accounts with their intended permissions.
Prove references and outputs
Open assemblies and drawings, revise a model, generate controlled deliverables, and retrieve them on another workstation.
Close and retest defects
Do not accept a verbal workaround for an issue that can release the wrong file or stop production.
Record each pilot result by edition, role, and evidence
The downloadable matrix ties one test to the PDM edition, release, role, workstation, job, precondition, expected and actual result, evidence, defect owner, retest, and approval.
Rehearse cutover, rollback, and the first week
Write the cutover like a machine changeover: prerequisites, stop point, owner, task order, expected duration, inspection step, release authority, and rollback trigger. Define when the shared drive becomes read-only, how late engineering changes are handled, which data batches move, how counts and references are verified, and who decides that users can begin work.
Training should use the shop’s workflow and files. A generic tour will not answer whether a designer checks out the assembly or a subcomponent, how a programmer identifies released data, or what quality does when a customer drawing changes. Give each role a short job-based exercise and require it to be completed before access is considered ready.
For the first week, establish a single support channel, daily issue review, severity rules, and a change freeze for nonessential configuration. Watch rejected transitions, permission failures, slow searches, missing card values, reference errors, and users who continue saving outside the vault. The objective is not zero questions. It is fast separation of training questions from defects and process gaps.
| Go-live gate | Pass evidence | Stop condition |
|---|---|---|
| Migration | Counts reconcile and representative references open | Missing, duplicated, or misdirected production files |
| Workflow | Release and rejection paths pass by role | Users can bypass required authority |
| Recovery | Current backup set and documented restore test | No recoverable synchronized vault state |
| Clients | Supported versions and required add-ins confirmed | Client/server mismatch or incomplete deployment |
| People | Role exercises complete and support owners scheduled | Critical role cannot perform its day-one job |
Measure control and adoption after launch
Track a small set of operating signals: files still created outside the vault, approval cycle exceptions, failed automated tasks, restore-test status, duplicate-name events, support requests by category, and the percentage of active users completing the expected workflow. These measures show whether the process is becoming routine or merely being worked around.
Schedule a thirty-day review with the sponsor, vault owner, IT, and pilot users. Confirm that the original business problems improved, close temporary permissions, review open risks, and decide which backlog items deserve the next controlled release. PDM stays healthy when configuration changes follow the same ownership and evidence rules used during implementation.
Frequently asked questions
How long does a SOLIDWORKS PDM implementation take?
The duration depends on file volume, reference quality, workflow complexity, integrations, infrastructure, and user availability. Estimate from a completed discovery and pilot, not from user count alone. A limited first release can often reduce risk compared with moving every historical file and automation at once.
Should every file on the shared drive move into PDM?
No. Separate active controlled product data from personal files, duplicates, temporary exports, archives, and records owned by another system. Every included class should have an owner, destination, retention rule, and validation method.
What makes a PDM pilot representative?
A representative pilot uses real assemblies, drawings, revisions, deliverables, user roles, and at least one exception. It proves references, permissions, workflows, search, output, and recovery-related procedures rather than showing only a clean demo file.
Who should own SOLIDWORKS PDM after go-live?
Name a business-facing vault owner and a technical backup. Process owners should approve workflow changes, while IT owns infrastructure, security, monitoring, and backup operations. The exact split should be written before launch.
Vendor references and method
- SOLIDWORKS 2026 Installation Help: PDM server components, official architecture and component roles
- SOLIDWORKS 2026 Installation Help: installing a PDM server, official installation sequence and product differences
- SOLIDWORKS PDM training course guide, official planning and administration curriculum
- SOLIDWORKS 2026 PDM overview, current product/version context
- SOLIDWORKS 2026 Help: PDM Standard and Professional differences, official edition boundaries for workflows, states, automation, integrations, SQL, replication, and administration
- Checklists, sequencing, and decision gates on this page are Morphos 3D implementation guidance. Adapt them to the exact software release, infrastructure, machine, controller, quality system, and approved company procedures.
Turn the checklist into a scoped vault plan
Bring the current folder structure, user roles, release process, and representative assemblies. The next useful output is a bounded phase-one design and pilot plan.