Evaluate product lifecycle management (PLM) software when your robotics team cannot reliably keep a change proposal, its engineering approval and the released hardware and firmware configuration together. The first useful adoption test is whether someone outside the design team can reconstruct an earlier build and prepare the next one from its approved records.
A small team can do that with a controlled spreadsheet, stable design references and a release register. Dedicated PLM becomes worth evaluating when parallel changes, two gripper variants or a supplier replacement repeatedly force engineers to reconcile those records by hand. Team size alone does not decide the answer.
Start with the next release you need to issue. Agree what it must contain, then evaluate software against that task. If self-hosting or source-code access is a buying constraint, the open-source PLM comparison adds edition, licence and operating responsibilities to this exercise.
What should CAD, PDM, inventory and PLM each own?
Computer-aided design (CAD) tools author the geometry, drawings and design configurations. Product data management (PDM) controls design files, versions and, in some products, release approval. PLM coordinates the wider product record and change process. Parts inventory owns physical quantities and stock transactions. Their capabilities overlap, so define authority at the record level.
Onshape documents approval workflows and immutable versions containing released objects. A CAD/PDM workflow can therefore provide release control. Check whether your setup also preserves the electronics, firmware, evidence and build applicability required for the robot. Source note
Table 1. Responsibilities to assign to the people on a small robotics team.
| Record or activity | Accountable owner | Boundary to agree before buying software |
|---|---|---|
| Native CAD, selected model configuration and drawing | Mechanical lead | Identify the authoritative design revision and a stable released reference. Keep design authoring in the CAD environment. |
| Electronics design and bought controller identity | Electrical lead | Distinguish the selected controller revision from any editable electronics design behind it. A controller bought complete is one purchasing item. |
| Firmware source and installable release | Firmware lead | Retain the source tag or commit, installation artifact and supported hardware stack. A branch called main is a moving reference. |
| Item identity, revision and assembly structure | Product-data owner | Decide which register issues identifiers and which accepted bill of materials (BOM) drives the build package. |
| Engineering change and product release | Engineering release authority | Record the difference, reviewed evidence, decision and applicable configurations or serials. |
| Verification evidence | Verification owner | Identify the exact hardware, firmware and conditions covered by each result. |
| Available stock, reservations, purchase orders and receipts | Operations lead | Maintain the physical and purchasing records. Reconcile their item and revision identity with the engineering release. |
A derived BOM export is useful when it carries its source release and someone accepts the handoff. If both systems can independently edit the same approved structure, the team needs an explicit reconciliation rule. The BOM management guide covers the structure and manufacturer package. The MRP selection guide covers material requirements planning (MRP) after engineering has authorised what to build. The open-source MRP comparison adds Community edition and operating checks at that planning handoff.
A robot change that crosses mechanical, electrical and firmware work
WP-200 is an illustrative warehouse picking robot. Every identifier, date, quantity, approval and verification outcome below is fictional. This is a teaching fixture and proposed software evaluation, with no customer or completed product trial.
The orderable robot items are WP-200-J with a jaw gripper, called JAW, and WP-200-V with a vacuum gripper, called VAC. Both use one CH-110 A chassis and one bought complete CTL-310 B controller. The selected physical components each have quantity one per robot. Firmware is an installation reference on the controller, with no stocked quantity.
The original product pack, REL-WP-01, was approved on 30 October 2026. Five JAW robots, WP-001 to WP-005, were built from it on 6 November. VAC A was also qualified in that original pack and is first used in the planned batch.
Actuator availability prompts engineering change order ECO-027. The proposed JAW design uses a different actuator and encoder, so it also needs a compatible firmware release. Engineering must approve the full combination before purchasing can adopt it.
Table 2. Selected configuration records used in the release decision.
| Controlled selection | Earlier JAW build | JAW after ECO-027 | VAC retained for the next batch |
|---|---|---|---|
| Orderable robot item | WP-200-J |
WP-200-J |
WP-200-V |
| BOM and configuration | BOM-JAW A, CFG-JAW A |
BOM-JAW B, CFG-JAW B |
BOM-VAC A, CFG-VAC A |
| Gripper assembly | One GR-J210 A |
One GR-J210 B |
One GR-V220 A |
| Bought actuator inside the jaw gripper | One ACT-410 A |
One ACT-420 A |
No jaw actuator |
| Encoder inside the jaw gripper | One ENC-510 A |
One ENC-520 A |
No jaw encoder |
| Pump inside the vacuum gripper | None in this variant | None in this variant | One bought PMP-430 A nested under GR-V220 A |
| Common physical selections | One CH-110 A, one complete CTL-310 B |
One CH-110 A, one complete CTL-310 B |
One CH-110 A, one complete CTL-310 B |
| Firmware installed on CTL-310 B | FW-310 1.4.0 for the JAW A stack |
FW-310 1.5.0 for this exact JAW B stack |
FW-310 1.4.0 for VAC A |
| Controlled jaw drawing | DW-GR-J210 A |
DW-GR-J210 B |
Jaw drawing does not apply |
| Product release and applicability | REL-WP-01, built serials WP-001 to WP-005 |
REL-WP-02, batch B-2412, planned serials WP-006 to WP-017 |
REL-WP-02 retains VAC A, batch B-2412, planned serials WP-018 to WP-025 |
ECO-027 is approved on 18 November and REL-WP-02 is issued on 19 November 2026. The planning snapshot is 20 November. Batch B-2412 contains 12 JAW B and 8 VAC A robots, with material issue planned for 14 December. There are no prebuilt grippers in this scenario. The first five robots retain their original as-built release, with no retrofit authorised.
The unchanged controller revision does not establish firmware interchangeability. FW-310 1.5.0 is accepted for the ACT-420 A and ENC-520 A stack in JAW B. This example supplies no approval to transfer it to JAW A or VAC A.
The existing BOM revision and product configuration guide explains why a changed assembly revision and a selected complete product configuration need separate records.
Follow the change from proposal to release
Use the following procedure as the minimum viable change-control workflow. A team can apply it to its current records before choosing PLM software. The required result is an attributable release whose exact selections remain recoverable after later changes.
1. Open a proposal against the approved source release — Identify REL-WP-01 as the starting point for ECO-027. Record the availability trigger, old and proposed component identities, responsible engineer and intended build applicability. Preserve the existing release while the proposal is being prepared.
Propose ACT-420 A and ENC-520 A for the JAW gripper, release GR-J210 B and its drawing, and select FW-310 1.5.0 for that configuration. Retain the VAC A selection.
2. Review the affected records and engineering questions — Run a where-used check from the actuator and encoder through the gripper to the JAW robot configuration. Include related drawings, software install references, verification records and applicable manufacturing instructions. Inspect retained selections too. The same controller may need different firmware behaviour for the changed encoder.
Table 3. The review record to prepare for ECO-027.
| Review subject | Owner to assign | Evidence needed for this fictional change |
|---|---|---|
| Gripper fit and actuator mounting | Mechanical lead | GR-J210 B and DW-GR-J210 B, with the change from A visible and fit evidence identified. |
| Encoder compatibility | Electrical lead | The selected ENC-520 A, its interface and the required counts and direction behaviour. |
| Firmware selection and fault response | Firmware lead | FW-310 1.5.0 tied to CTL-310 B, ACT-420 A and ENC-520 A, with the encoder fault response checked. |
| Verification applicability | Verification owner | TV-027, the approved fictional reference for fit, encoder counts and direction, and encoder fault response on the exact JAW B stack. |
| Product applicability | Release authority | BOM-JAW B, CFG-JAW B and serials WP-006 to WP-017, with VAC A and earlier serials retained explicitly. |
| Manufacturer handoff | Manufacturing lead | The released structure, drawing and firmware instructions needed to assemble JAW B, while VAC A remains a distinct selection. |
TV-027 covers the stated checks for this fictional JAW B stack. Preserve the original pack's evidence with its original applicability. Use the supplier-change evidence guide to decide whether earlier evidence can support another selection.
3. Approve the exact material reviewed — Nominate an engineering release authority. Mechanical, electrical and firmware owners provide their technical dispositions. The verification owner confirms what the evidence covers. The manufacturing lead checks that the approved design can be expressed in an unambiguous build package.
In a small team, one person may cover several responsibilities. Record which decisions they made and use a second competent reviewer where the agreed process requires one. A list of names or a status called Approved does not show what each person accepted.
Each approval should identify the change, reviewed revision or snapshot, decision, actor and timestamp. If the proposal changes after review, retain the earlier decision and obtain acceptance of the changed material. Ask a software demonstrator to show what happens to approvals when an encoder or firmware reference changes during review.
4. Issue a product release and communicate its applicability — After approval, issue REL-WP-02 with a manifest identifying ECO-027, the selected BOMs, configurations, drawing and firmware references, and evidence locations. Store copies or stable version references where a link could otherwise resolve to current work.
Attach the batch and serial allocation shown in Table 2. Record JAW B for the 12 new JAW robots and retained VAC A for the eight vacuum robots. Earlier serials continue to resolve to REL-WP-01. Later release dates must not silently rewrite their as-built identity.
Give the contract manufacturer the accepted package and obtain confirmation of the release received. The BOM handoff checklist defines its structure and quantities. Operations then performs the stock, receipt and purchasing exercise in the MRP guide. Approval of JAW B establishes the authorised configuration. It does not establish that its actuator stock arrives in time.
5. Reconstruct the earlier release without relying on its author — Give a buyer or manufacturing engineer the identity WP-003. They should recover REL-WP-01, CFG-JAW A, BOM-JAW A, DW-GR-J210 A, ACT-410 A, ENC-510 A and FW-310 1.4.0, plus the approval and evidence references in that original pack.
Then give them planned serial WP-010. They should recover the JAW B selections, ECO-027 and REL-WP-02. Planned serial WP-020 should recover VAC A with FW-310 1.4.0, without inheriting the JAW encoder or firmware change. These last two are planned configurations at the 20 November snapshot. Their actual as-built records will be created and reconciled during manufacturing.
Repeat the lookup from an exported archive. A screenshot of the current BOM is insufficient when another engineer needs the selected files, release decision and historical evidence references. Record every manual step necessary to recover the package.
Arc adapted NASA's configuration identification, change control and status-accounting principles for the WP-200 exercise. Source note
Which software should enter the evaluation?
Select candidates around the unresolved responsibility. If your existing CAD/PDM tool can release its design files well, evaluate the missing cross-discipline release record. If the problem is an unreliable material count, assess the inventory and planning workflow with its engineering handoff.
Comparison methodology and commercial interest — This guide is for technical founders and engineering, manufacturing and operations leads moving from prototypes into low-volume robot builds. It compares workflows for approving a first controlled hardware and firmware change and recovering a release later.
The examples cover three buying routes using first-party sources reviewed on 20 November 2026. Check identity and BOM structure, stable source references, proposal isolation, attributable approval, configuration and serial applicability, release recovery, export and operating responsibility. The vendor sources describe their published scope. WP-200 is a fictional exercise for a future evaluation. Leave any unsupported field unresolved until you can verify it.
Arc publishes this guide and sells engineering software, so it has a commercial interest in the outcome. Agree the robot release's acceptance conditions before evaluation. Use Arc's existing approach to recording comparable evidence. Buyer-guide methodology
Table 4. Documented buying routes and the next question to verify. Product names are examples for evaluation, with no implied ranking. Source note
| Candidate route | Relevant documented scope and source | Decision-changing WP-200 question |
|---|---|---|
| Extend the current CAD/PDM workflow, for example Onshape PDM | Onshape release management covers released parts, assemblies, drawings and imported files. Approval policy is configured, and Enterprise supports custom workflows. | Can the edition you use preserve the selected firmware and evidence references and the three historical or planned configurations, with a clear owner for records outside CAD? |
| Evaluate hardware PLM, for example Duro Design | Duro Design's PLM page documents mechanical and electrical BOM consolidation, revision comparison, where-used and change-order workflows. | Show ECO-027 with the exact firmware stack and applicable serials, then reconstruct REL-WP-01 and export its release evidence. Confirm the plan and integrations needed for the demonstrated workflow. |
| Evaluate a wider lifecycle platform, for example Teamcenter or Teamcenter X | Siemens' Teamcenter page describes multidisciplinary product information and lifecycle processes, with customer-operated and Siemens-operated deployment options. | Specify the modules, deployment, configuration effort and support required for this release exercise. Confirm whether that scope is justified by your established CAD environment, customers and future product complexity. |
When source ownership is a requirement, start with the pinned editions and module checks in the open-source PLM guide. The open-source BOM guide addresses parts, stock and assembly records, whose presence alone does not demonstrate approval of this product change.
Start small, then add control where the workflow needs it
Table 5. Decisions and acceptance conditions as the release workflow grows.
| Current situation | Smallest useful adoption scope | Acceptance condition before expanding |
|---|---|---|
| Repeated prototypes with one maintained structure | Keep a controlled BOM, stable design links and an explicit release register. | Another engineer reconstructs the released configuration and its decision using the records alone. |
| JAW and VAC variants with the first cross-discipline supplier change | Evaluate a controlled change record and a frozen product manifest. | ECO-027 is reviewed against exact selections and all three WP-200 lookups resolve correctly. |
| More suppliers, variants and concurrent changes | Add maintained where-used relationships, review permissions, conflict handling and applicability rules. | Two proposals can remain distinct, and review of one does not authorise the other's unreviewed content. |
| Manufacturing handoffs need repeated reconciliation | Define the engineering-to-manufacturing mapping and automate only the agreed handoff. | The receiving system records the source release and preserves accepted quantities, revisions and firmware instructions. |
| Exit or upgrade risk becomes material | Test an export archive and a recovery exercise for the actual setup. | An independent reviewer can recover records, files, relationships, decisions and applicability after the transition. |
For migration, begin with one released assembly. Map item identities, revision representation, relationship keys and source references. Reconcile the imported structure and the approved configuration against the original. A matching row count is only one check.
Budget for duplicate identifiers, missing source files, approval history, permission configuration and training. Obtain an exit sample before purchase. Have an independent reader open the release archive and separately test recovery from a database backup. Confirm the cost of users, editions, support and integration work with dated quotations.
Choose a cutover boundary after the representative release passes acceptance. Keep its original records available through reconciliation and name the owner who closes the superseded editing path.
Arc's robotics homepage describes assembly BOMs, selected CAD and electronic computer-aided design (ECAD) references, firmware versions, branches and review of product-record changes. For ECO-027, ask to see the import, review permissions, historical recovery and manufacturer export in the intended setup. Page reviewed on 20 November 2026. Arc robotics product page
Use your WP-200-style release as the decision aid. Keep the current process while it gives buyers and builders an unambiguous answer at an acceptable maintenance cost. Adopt PLM when the demonstrated workflow preserves that answer through the changes your team actually makes.