On this page

SOLIDWORKS PDM vs Arc: CAD Revisions, BOMs and Product Releases

SOLIDWORKS PDM and Arc address overlapping parts of an engineering release from different starting points. SOLIDWORKS PDM centres on controlled CAD files and documents. Arc centres on connected robotics product records, selected build references and engineering review. Compare them by releasing one complete robot configuration, with an explicit owner for each record and handoff.

Begin by naming the PDM edition. Standard and Professional have different documented scope. Also decide whether you are choosing a CAD vault, a broader product record system, or a combination. Complete the build record with selected firmware, approved sources and applicable evidence alongside the CAD revision.

Comparison method and product boundaries

This is an Arc-authored, documented-source assessment for robotics teams with SOLIDWORKS CAD and additional electrical, software and verification records. It selects PDM Standard and Professional because those edition differences change the evaluation. It uses the same questions for each candidate: identity, revisions, BOM view, release approval, configuration continuity, interchange and operating responsibility.

Use the existing buyer-guide criteria for traceability, review, operating responsibility and migration questions, then add the CAD and BOM checks here. Official pages were inspected on 20 November 2026. The scope is a documentation review, with installation and integration behaviour left for the witness exercise. Arc sells engineering software and has a commercial interest in this comparison. Documented capabilities, proposed exercises and unresolved package details are kept separate. There are no numerical scores or overall winner.

What Standard and Professional document

The SOLIDWORKS PDM product page describes a central file vault, version control and check-out locking. It positions Standard for smaller single-site companies. Professional adds capabilities including browser access, BOM support and multi-CAD support. Those are documented product statements. The robot exercise below supplies the separate acceptance evidence.

CandidateDocumented starting pointQuestion for the selected implementation
PDM StandardSingle-site file management, change tracking and workflow notificationsCan the chosen workflow issue the required CAD and document release with the assigned reviewers?
PDM ProfessionalStandard scope plus browser access, BOM and multi-CAD capabilitiesWhich BOM views, external-user permissions and downstream handoffs are configured and licensed?
ArcRobotics product records with build references and engineering reviewHow will controlled CAD files, part structures and purchasing records connect to that context?

SOLIDWORKS also describes Manage as a records-based product with item and process management. Keep Manage's scope tied to that offered product. Require direct evidence before assigning CAD vault or native procurement duties to Arc. Ask each vendor to identify the edition, modules and configured workflow that supply the proposed solution.

Separate a file version from a product release

Use four distinct identifiers in the evaluation: the CAD file version, the part's engineering revision, the selected assembly/BOM view and the complete robot configuration. Record how they relate. A file may change several times while a proposed engineering revision is under review. The released product may continue to use the previously approved revision.

For PDM, demonstrate which saved file versions a released assembly resolves to and what happens when a child receives a later revision. For BOM handling, ask the implementer to show the actual supported view and its lifecycle. Check whether an export can reproduce the accepted quantity, configuration and child revision selection. Witness named-BOM behaviour in the selected installation.

Arc's documented review workflow provides a reason to evaluate linked engineering context. Define the proposed mapping before importing data. Record a CAD reference as a controlled file reference unless the selected integration has been demonstrated. Synchronisation, CAD dependency resolution and manufacturing release need their own demonstrated handoffs.

Use the SOLIDWORKS BOM preparation guide for the export task. This article owns the separate decision about who controls the wider release. The configuration matrix supplies a common record format for the exercise.

Run a robot release witness exercise

In this fictional scenario, R-01 has motor bracket BR-120 A, controller CB-200 A, firmware reference FW-1.4 and configuration CFG-R01-A for serials 001–002. A proposed change creates bracket B and requires a new alignment check. The team intends to apply the change from serial 003. Nothing in this scenario represents an executed customer build.

ExerciseWitness evidence to retainAcceptance question
Retrieve the A releaseSelected CAD files, versions, drawing, BOM rows and configuration recordCan another reviewer reproduce the accepted A design?
Propose bracket BChanged files, item identity, reason and affected interfacesIs the proposed change distinct from the released A baseline?
Review alignment evidenceTest setup, tested revision, result and decisionDoes the evidence actually apply to bracket B in the proposed assembly?
Release serial 003 onwardApproved configuration, effectivity and manufacturing handoffDo later builds use B while the A release remains reproducible?

Execute the same steps in the proposed PDM solution and Arc workflow. Record manual steps as manual. For a combined solution, interrupt a synchronisation or deliberately reject a mapping in a controlled trial. Check who notices, how the discrepancy is held and how recovery avoids issuing a mixed release.

A purchasing export should identify the relevant release and selected revisions. Use the multilevel BOM example to check quantities. Require the responsible team's approval and a tested connection before using a file state transition to authorise a purchase order.

Compare adoption and operating responsibility

Request a scope breakdown for software, implementation, migration, training, ongoing administration and support. State the number of authors, reviewers and external users and the sites they access. Ask who operates storage, backups, permissions and upgrades in the offered deployment. Avoid estimating a total from a licence price while leaving essential work uncosted.

Inventory the records that must transfer: file versions, identifiers, references, approvals, attachments and applicable configurations. Reconcile a sample release before cutover. Preserve the original evidence until the team has accepted the replacement record. Agree the mapping and reconcile required records and relationships before accepting the migration.

Keep PDM when controlled CAD is already doing its job and assess whether another system needs to own cross-domain decisions. Evaluate a broader PLM if product structure, manufacturing or supplier release scope requires it. The Teamcenter comparison examines that broader scope. Choose a coherent ownership map that the robot team can operate.

SOLIDWORKS PDM comparison questions

Does PDM Professional have BOM management?

The official product page lists BOM support for Professional. Verify the precise view, revision behaviour and release workflow in the offered installation. Assess ERP and purchasing integration as separate offered and demonstrated capabilities.

Can Arc replace a SOLIDWORKS CAD vault?

That replacement needs a CAD-specific evaluation. Require a demonstration of CAD references, file versioning, locking and release resolution before assigning those responsibilities to another system. A combined workflow may leave the vault as the CAD owner.

What should count as a successful evaluation?

Another engineer can retrieve the accepted configuration, identify every controlled revision, follow the approval decision and find applicable evidence. The purchasing and manufacturing teams can identify their authorised handoff without resolving undocumented conflicts.

Move faster without compromising engineering rigour.

Use one CAD revision and robot release pack to evaluate Arc alongside your SOLIDWORKS PDM workflow.