On this page

BOM vs PDM vs PLM vs ERP for Robotics

A BOM records the selected product structure, parts, revisions, quantities and units. PDM manages design and engineering data. PLM supports the wider product lifecycle and change process. ERP supports business execution such as purchasing, inventory and financial transactions. For a robot build, the useful boundary is the person authorised to write each controlled field and the receiving check that preserves its meaning across a handoff.

These categories overlap. Autodesk describes PDM revision, change-order and BOM functions alongside the broader processes associated with PLM. Oracle describes procurement, manufacturing and supply-chain activities within ERP scope. Verify the chosen product and workflow rather than assigning authority from its category name. Autodesk PDM definitions and Oracle ERP definition

This guide supplies a field-owner contract and a rejected purchasing handoff. Arc's existing robotics PLM guide covers the adoption decision and general team responsibilities. Its SOLIDWORKS PDM comparison covers the CAD-vault evaluation. Robotics PLM guide and SOLIDWORKS PDM comparison

Treat the BOM as controlled information

A BOM can live in a controlled spreadsheet, CAD/PDM system, PLM platform, ERP or dedicated BOM tool. A BOM tool is an optional software category. Decide which accepted view defines the build and how downstream views retain the selected release, quantities and revisions.

The engineering BOM describes design structure. A manufacturing BOM may reorganise that structure around assembly work and add controlled manufacturing items. Manufacturing engineering owns that transformation in the example below. Its authoritative authoring system depends on the team's architecture. It could be a manufacturing workspace in PLM, ERP or another controlled record. Identify one writer for the accepted manufacturing fields and a clear release boundary.

Keep native design authoring with the responsible design team. Keep purchase orders and physical stock transactions with their operational owners. A release workflow can collect the evidence and approvals without taking over every source record. NASA's configuration-management method connects identification, change control, status records and verification of implementation. The handoff contract here applies those concepts to a fictional pilot, without importing NASA programme obligations. NASA configuration-management guidance

Assign one authoritative writer per field

Start with the fields that can alter what the buyer orders or builder installs. Name the owner, authoritative location and value transferred. Downstream users can report a conflict, propose a change or record a local transaction. The original controlled design and release fields change through their assigned owners.

Controlled field Authoritative writer Source to nominate Exact handoff content Receiving check
Harness design and drawing revision Harness design owner Released CAD/drawing record, controlled through the chosen PDM workflow DW-HR-300 B and its stable released file reference Drawing opens and its identity and revision match the manifest.
Item identity, selected revision, quantity and unit Product-data owner Accepted BOM register or nominated product-record system HR-300 B, quantity 3, unit ea, from BOM-R01 B Imported fields match the source and retain a resolvable release reference.
Approved configuration and effectivity Engineering release authority Release and change register CFG-R01-B, serials 003–005, ECO-017 and the release approval Every planned serial has a selected configuration and attributable approval.
Manufacturing operations and added consumables Manufacturing engineer Nominated MBOM and instruction authoring record Accepted manufacturing view and its source-BOM relationship Manufacturing additions and quantities have their own accepted scope.
Supplier quotation and purchase-order terms Buyer Purchasing record, often in ERP Quote reference, item/revision, ordered quantity, price, currency and exceptions Commercial values are supported and the order preserves the authorised technical scope.
Receipts, accepted stock and allocation Materials lead Physical inventory and receipt record Actual item/revision, quantity, inspection status and allocation Material selected for issue matches the build's approved revision.
Installation instruction Manufacturing engineer Released work-instruction record Applicable instruction revision and serial range Builder resolves the selected harness and drawing from the instruction.
Installed identity Assembly record owner Serial-specific build record Actual HR-300 revision installed on each robot Actual installation reconciles with the plan or links to an authorised exception.

The table is a proposed ownership arrangement. The same person may hold several roles in a small team. Record which authority they exercised. Review permission and read access can span several systems while the accepted field has one authoritative editing path.

Follow ECO-017 into an exact outbound package

R-01 is the fictional indoor inspection robot used in Arc's BOM series. CFG-R01-A with BOM-R01 A selects HR-300 A and DW-HR-300 A for serials 001–002. ECO-017 approves a harness strain-relief manufacturing improvement. CFG-R01-B with BOM-R01 B selects HR-300 B and DW-HR-300 B for 003–005. The change retains the installation interfaces and acceptance requirements. Both select DW-R01 A, ECAD CB-200 A and firmware 1.2.0, with no automatic retrofit of 001–002. R-01 configuration matrix

The harness design owner controls the changed drawing. The product-data owner prepares the B BOM selection. The release authority accepts its effectivity and reviewed scope. Manufacturing engineering then prepares the B-build instructions. Approval and implementation records identify their exact sources, including the unchanged references.

For this guide, HND-R01-B-01 is a fictional outbound handoff derived from the accepted B release. The package contains the following inspectable content.

  • Handoff identity HND-R01-B-01, source BOM-R01 B and configuration CFG-R01-B.
  • ECO-017 and the attributable B-release approval reference.
  • One HR-300 B per robot for 003–005, giving three gross harnesses in ea.
  • Released DW-HR-300 B, with DW-R01 A, ECAD CB-200 A and firmware 1.2.0 retained in the configuration manifest.
  • Accepted manufacturing-view and instruction references for the relevant operations.
  • Explicit retention of the A selection for 001–002 and an exception rule for proposed substitutions.

The A handoff separately requires two HR-300 A harnesses. The pilot therefore has five gross harnesses across the two revision groups. Purchasing still reconciles accepted stock, open orders and supplier terms before placing an order. Firmware is an installation reference in this example and carries no stocked harness quantity. R-01 gross purchasing quantities

Reject a conflicting purchasing line

In the fictional recovery exercise, the buyer's candidate purchasing line maps HND-R01-B-01 to HR-300 A, quantity three, for 003–005. Its attached drawing is DW-HR-300 B. The receiving check finds a mixed revision selection before a purchase order or material issue is authorised.

Mark the candidate Rejected and record the mismatched fields with the source handoff. Hold purchase and issue for that B-build line. Revision A remains valid for its original 001–002 scope. It is obsolete as the selected value on this candidate B line.

Handoff state Evidence retained Owner action Permitted next action
Sent for receiver check HND-R01-B-01 with source and intended values Product-data owner identifies the exact released source. Inspect the candidate mapping.
Rejected Candidate shows A with drawing B for 003–005 Buyer records the mismatch and holds the candidate. Trace the conflict to its authoritative field.
Corrected candidate Purchasing line now shows HR-300 B, DW-HR-300 B, 3 ea, 003–005 Buyer repairs the local mapping after confirming the source is correct. Repeat the receiving checks.
Acknowledged Receiver records the checked handoff and corrected candidate identity Buyer confirms selected fields and manufacturing owner confirms the applicable instruction. Continue the separately authorised purchasing and build process.

The source comparison in this scenario shows that BOM-R01 B was already correct. The buyer therefore repairs the purchasing mapping. The product-data owner preserves the accepted source. If the source itself were wrong, its owner would correct it through review and issue a replacement handoff before purchasing adopted the new values.

An acknowledgment confirms that the receiving record matches the identified handoff. It provides no supplier availability evidence, material inspection result or permission to disregard a later discrepancy. Retain those decisions with their own records.

Test the contract before automating it

Run one representative handoff using the team's actual files and systems. Have a receiver recover serial 002's A selection and serial 003's B selection. Deliberately introduce a conflicting revision into a safe candidate record, then check whether it is held, assigned and repaired without changing the wrong source.

Record manual steps as manual. If the team proposes an integration, verify its revision mapping, error reporting, retry behaviour and rejection handling in the intended setup. This guide specifies the required result and makes no integration capability claim for Arc or another product.

BOM, PDM, PLM and ERP questions

Is a BOM the same kind of thing as PDM or ERP?

A BOM is controlled product information. PDM, PLM and ERP describe software and process categories that can hold or use that information. A dedicated BOM tool is one possible place to manage it.

Must the MBOM be authored in ERP?

Its authoring location depends on the architecture. Assign manufacturing engineering responsibility for the accepted transformation and nominate the system that owns those fields. Receiving systems must preserve the source and accepted scope.

Can purchasing change a selected revision when a supplier offers a newer one?

Purchasing can record the offer and request engineering disposition. The selected revision changes through the authorised change or exception process before it becomes an order or issue instruction.

Does a successful import mean the handoff is accepted?

Successful parsing shows that data entered a system. Acceptance needs the receiving checks for identity, revision, quantity, unit, effectivity, documents and approval scope, with the receiver's decision recorded.

Do small teams need four separate tools?

Choose tools around the records and decisions the team must preserve. A controlled spreadsheet and stable source files may support an early pilot. Test the ownership and handoff contract before deciding which additional system is justified.

Continue the ownership review

Use the robotics PLM guide for adoption decisions and the SOLIDWORKS PDM comparison for design-file control. Use the revision and configuration matrix to check the release selected for each serial.

Use the whole-robot release manifest to assemble the exact outbound package that the receiver checks.

Move faster without compromising engineering rigour.

Bring one engineering-to-purchasing handoff and its field-owner map to a demo.