BOM management software should tell your robotics team what goes into each robot variant and which release the manufacturer should use. Test a candidate by asking a colleague to reconstruct one approved build package, including nested assemblies, selected revisions, permitted substitutions and firmware instructions. A spreadsheet can serve that job when the team maintains its relationships, approvals and release copies.
For a documented software shortlist, start with OpenBOM when BOM data must flow into quotation and purchasing, Bild when the immediate handoff starts in mechanical design files, Duro Design when mechanical and electrical BOMs need a shared revision review, and Altium 365 BOM Portal when the main task is electronics component sourcing. The evidence and limits for these conditional choices appear below.
A bill of materials (BOM) here describes physical robot parts and assemblies. Firmware belongs in the build package as a controlled installation reference.
What must a robotics BOM preserve?
Keep the product structure and the build selection together. An item record says what a part is. A BOM relationship says which parent uses it and in what quantity. A release says which revisions and references are accepted for a particular configuration. Combining those into a single description column makes later checks harder.
Record the internal item number, revision, parent, quantity per parent and unit. Keep the manufacturer's part number and supplier catalogue number in their own fields. Add the make-or-buy decision, controlled drawing or specification, selected product variant and any approved substitution rule. Link the release decision and specify which builds it covers.
An engineering bill of materials (EBOM) describes the designed product. A manufacturing bill of materials (MBOM) describes the assembly stages and materials used to make it. A manufacturer may reorganise the structure into kits or operations. Keep each physical input traceable to the accepted design. Robotics EBOM-to-MBOM guide
Worked example with two grippers on one warehouse robot
WP-200 is a fictional warehouse picking robot. Its orderable items are WP-200-J for a jaw gripper and WP-200-V for a vacuum gripper. Each robot uses one CH-110 A chassis and one CTL-310 B controller bought as a complete assembly. Grippers are assembled from their inputs, with no prebuilt grippers in stock.
The original release, REL-WP-01, was approved on 30 October 2026. Five jaw robots, WP-001–WP-005, were built on 6 November using BOM-JAW A and CFG-JAW A. VAC A was qualified in that original package, although its first use is in the planned batch below.
Actuator availability prompts engineering change order ECO-027, approved on 18 November. REL-WP-02 is issued on 19 November for batch B-2412. It covers twelve jaw robots, WP-006–WP-017, and eight vacuum robots, WP-018–WP-025. Material issue is planned for 14 December. Earlier serials retain their as-built release, with no retrofit.
Table 1 gives the selected relationships in this deliberately small teaching BOM. Quantity is per parent, in pieces. The two common rows are included once in each robot's selected BOM. Only one gripper is selected for each orderable variant.
| Parent and selected BOM | Child item | Revision | Quantity per parent | Variant or release use |
|---|---|---|---|---|
| WP-200-J or WP-200-V, in each selected BOM | CH-110 chassis | A | 1 | Common to JAW A, JAW B and VAC A |
| WP-200-J or WP-200-V, in each selected BOM | CTL-310 complete controller | B | 1 | Common to JAW A, JAW B and VAC A |
| WP-200-J, BOM-JAW A | GR-J210 jaw gripper | A | 1 | CFG-JAW A, original jaw build |
| GR-J210 A, within BOM-JAW A | ACT-410 bought actuator | A | 1 | Original jaw stack only |
| GR-J210 A, within BOM-JAW A | ENC-510 encoder | A | 1 | Original jaw stack only |
| WP-200-J, BOM-JAW B | GR-J210 jaw gripper | B | 1 | CFG-JAW B, twelve planned jaw robots |
| GR-J210 B, within BOM-JAW B | ACT-420 bought actuator | A | 1 | Approved replacement jaw stack |
| GR-J210 B, within BOM-JAW B | ENC-520 encoder | A | 1 | Approved replacement jaw stack |
| WP-200-V, BOM-VAC A | GR-V220 vacuum gripper | A | 1 | CFG-VAC A, eight planned vacuum robots |
| GR-V220 A, within BOM-VAC A | PMP-430 bought vacuum pump | A | 1 | VAC A only |
Firmware FW-310 1.4.0 is selected on CTL-310 B for JAW A and VAC A. JAW B selects FW-310 1.5.0 for the exact ACT-420 A and ENC-520 A stack. VAC has no jaw encoder. A correct hardware count does not prove that these installation choices are correct.
How does a multi-level BOM roll up?
Multiply quantity along each parent-child path, then sum matching item-and-revision uses across the selected variants. For the new jaw actuator, the path is one GR-J210 B per jaw robot multiplied by one ACT-420 A per gripper. Twelve jaw robots therefore require 12 × 1 × 1 = 12 actuators.
The shared controller rolls up across both variants. The calculation is 12 × 1 + 8 × 1 = 20.
Table 2 is the gross physical requirement for B-2412 under REL-WP-02. Other approved physical inputs are assumed sufficient in this illustration. These totals establish what the batch consumes, before any stock or due-order calculation.
| Item and revision | Twelve JAW B robots | Eight VAC A robots | Gross batch requirement | Supply treatment |
|---|---|---|---|---|
| CH-110 A | 12 | 8 | 20 | Physical chassis input |
| CTL-310 B | 12 | 8 | 20 | Buy complete controller once per robot |
| GR-J210 B | 12 | 0 | 12 | Assemble grippers from the selected children |
| ACT-420 A | 12 | 0 | 12 | Bought actuator input |
| ENC-520 A | 12 | 0 | 12 | Selected encoder input |
| GR-V220 A | 0 | 8 | 8 | Assemble vacuum grippers from the selected child |
| PMP-430 A | 0 | 8 | 8 | Bought pump input |
| ACT-410 A and ENC-510 A | 0 | 0 | 0 | Retained in the earlier jaw release |
Show gripper assemblies in the manufacturing view and their bought children in the purchasing view. Purchase the CTL-310 B controller as one complete unit per robot. Its supplier's electronics BOM can support a separate component risk review.
The install sheet calls for twelve installations of FW-310 1.5.0 and eight of FW-310 1.4.0. Neither is a physical stock requirement. To decide what to buy and when, carry these accepted quantities into the MRP guide for the twenty-robot batch. Material requirements planning (MRP) then reconciles usable stock, scheduled receipts and lead times.
When is a substitute actually approved?
A supplier's alternative suggestion identifies a candidate. Engineering approval must say where that candidate can be used. In WP-200, ACT-420 A requires ENC-520 A and FW-310 1.5.0 within JAW B. Listing ACT-410 and ACT-420 as freely interchangeable would erase the decision that makes the replacement acceptable.
Table 3 records where each combination can be used. TV-027 is fictional verification evidence for the exact JAW B combination. It covers fit, encoder counts and direction, and the response to an encoder fault.
| Selected configuration | Actuator or pump | Encoder | Firmware on CTL-310 B | Substitution and build rule |
|---|---|---|---|---|
| CFG-JAW A / BOM-JAW A | ACT-410 A | ENC-510 A | FW-310 1.4.0 | Keep for WP-001–WP-005 under REL-WP-01. No blanket permission to fit ACT-420 |
| CFG-JAW B / BOM-JAW B | ACT-420 A | ENC-520 A | FW-310 1.5.0 | ECO-027 approves this stack for B-2412, WP-006–WP-017, with DW-GR-J210 B and TV-027 |
| CFG-VAC A / BOM-VAC A | PMP-430 A | No jaw encoder | FW-310 1.4.0 | Carry unchanged for WP-018–WP-025. Jaw compatibility evidence does not apply |
Record the approval reference, selected drawing, configuration and applicability beside any alternative relationship in the software. If its substitute field grants permission to consume either item, use separate released structures until the conditional rule is represented and tested. The PLM change-control guide follows the reviewers, approval and earlier-release reconstruction behind this handoff.
What should the contract manufacturer receive?
Send a named package with a readable manifest and machine-readable BOM data. The manifest lets the manufacturer check that the files and rows belong to the same release. A comma-separated values (CSV) file may contain correct quantities and still omit drawing selection, firmware or applicability.
For B-2412, include the following release checklist. These are expected package contents for the fictional exercise, not files produced in a software trial.
| Package element | Information the recipient must be able to check |
|---|---|
| Release manifest | REL-WP-02, issued 19 November 2026, ECO-027 approval reference, batch B-2412 and planned 14 December material issue |
| Variant split | WP-200-J with BOM-JAW B and CFG-JAW B for WP-006–WP-017. WP-200-V with BOM-VAC A and CFG-VAC A for WP-018–WP-025 |
| Structured BOM | Parent, child item, revision, quantity per parent, unit, supply treatment and applicable variant |
| Derived physical requirement | Twenty controllers, twelve ACT-420 A actuators, twelve ENC-520 A encoders and eight pumps, traceable to the structure |
| Controlled design references | DW-GR-J210 B for JAW B, plus the exact selected mechanical, electrical and supplier references required by the real build |
| Installation and acceptance instructions | Firmware split, exact jaw compatibility rule, TV-027 reference and the build's acceptance instructions |
| Substitution and deviation route | Which alternatives are accepted, where they apply and who decides when delivered identity differs |
| Receipt and as-built record | Space to record actual installed identities and link them to each serial and the package used |
Retain REL-WP-01 and DW-GR-J210 A for service and reconstruction of WP-001–WP-005. A link that always opens the newest drawing is insufficient for that job. Ask the recipient to resolve WP-005 and WP-006 from the package references before accepting the handoff.
When does a spreadsheet still work?
A workbook can work when one owner maintains the item and relationship tables, formulas are reviewed, and the team records an attributable release decision. Store quantities as numbers, identities and revisions as text, and units separately. Derive the flat totals from the selected structure. Keep released copies and the source references they select.
Use the existing robotics BOM spreadsheet template for the relationship format. Its separate teaching example does not replace WP-200's release selections. The workbook-versus-tool guide covers version history and approval as different controls.
Evaluate dedicated software when parallel edits repeatedly overwrite accepted data, a second variant inherits the wrong change, sourcing edits lose their approval conditions, or a supplier gets a package the team cannot reconstruct. Record an actual failure, then test whether the proposed tool resolves it.
Compare a shortlist by the handoff you need
This comparison is for technical founders, mechanical and electrical leads, and manufacturing engineers moving from prototypes into low-volume robot production. Four candidates from the existing guide cover different documented handoffs.
Computer-aided design (CAD) and electronic computer-aided design (ECAD) author mechanical and electronic design data. Product data management (PDM) controls their engineering files. Product lifecycle management (PLM) can coordinate BOM and release records across disciplines.
Each trial should check selected structure and revisions, variant isolation, CAD and electronics mapping, conditional substitutions, and a reproducible manufacturer package. Primary vendor pages were inspected on 20 November 2026. Product descriptions establish documented scope. The proposed trial tasks are editorial judgements. Check exact plan entitlements, connector versions and configured enforcement in the evaluation. Arc publishes software and has a commercial interest in software evaluations. Buyer-guide methodology for recording evidence and unknowns
| Candidate and scope reviewed | Documented reason to consider it | WP-200 task to request | Decision-changing question still to resolve |
|---|---|---|---|
| OpenBOM, current workspace product description | Flat and multi-level BOMs, revisions and engineering changes, plus requests for quotation and purchase orders. OpenBOM product page | Send twelve JAW B and eight VAC A requirements into a sourcing handoff with REL-WP-02 retained | Which subscribed modules and export fields preserve the exact revisions, approval conditions and manufacturer package? |
| Bild, current cloud PDM/PLM product description | BOMs from its design vault, parent-child updates, change orders and supplier collaboration. Bild product page | Start from selected mechanical files and deliver DW-GR-J210 B with the applicable jaw BOM | How are electrical and firmware references selected, and can a recipient retrieve the earlier A package? |
| Duro Design PLM, current product description | Mechanical/electrical BOM consolidation, revision comparison, where-used and tailored change orders. Duro Design product page | Compare GR-J210 A/B, retain CTL-310 B and show the separate VAC selection | How do the configured approval and downstream export represent the exact actuator/encoder/firmware rule? |
| Altium 365 BOM Portal, current technical documentation | Electronics manufacturer/supplier data, alternative suggestions and managed BOM releases. BOM Portal documentation | Review component sourcing for the complete controller without adding its internal components to robot purchases | Which licensed features cover the task, and what separate process owns the whole-robot mechanical and firmware release? |
For Altium, an alternative electronic component suggestion does not establish approval to substitute the complete robot controller or the jaw actuator. For every candidate, a successful task in one discipline leaves the remaining handoffs to be assigned explicitly.
If source access and self-hosting are buying constraints, compare licences, deployment and export fields in the InvenTree and Part-DB open-source BOM guide.
Test your workbook and software against one release
Give each candidate the same WP-200 relationship rows, A/B drawings and a synthetic release manifest. Begin with REL-WP-01, then apply ECO-027 only to the intended JAW B batch. A useful evaluation records the evidence for each step instead of accepting a general demonstration.
| Buyer check | Expected result to demonstrate |
|---|---|
| Identity and quantity | One common CTL-310 B item appears once per robot. ACT-420 A rolls up only through JAW B |
| Variant isolation | VAC A keeps PMP-430 A and FW-310 1.4.0, with no jaw encoder |
| CAD and electronics mapping | Source file, version/configuration, internal item and revision are reconciled. Unmodelled inputs and supplier controller detail are handled explicitly |
| Approval rule | An operator cannot treat ACT-410 A as an accepted input to the JAW B stack merely because stock exists |
| Manufacturer export | Parent-child rows, selected revisions, gross totals and the accompanying release references survive delivery |
| Earlier package | A second engineer retrieves WP-005's A drawing, original jaw inputs and firmware while WP-006 resolves to B |
| Receipt discrepancy | The receiving team records and holds a wrong revision for disposition by a named owner |
For CAD imports, reconcile the source counts, electronics identities, bought-complete boundaries and firmware selection. Onshape CSV guide · SOLIDWORKS Excel guide
Arc's current robotics product page describes starting from BOM source exports with agreed mapping, linking CAD, ECAD and firmware references, and reviewing proposed part and configuration changes. If that review handoff is the buying problem, request the same WP-200 package exercise in the intended setup. That public description does not establish an executed WP-200 import or a material-planning result.
Record the tool, edition or modules, version where available, permissions, operator, date and outputs. Keep documented capabilities separate from demonstrated results and unresolved questions.
Keep the workbook if it passes the repeatable handoff with sustainable ownership. Evaluate a tool where it closes a recorded control gap. In either case, make the manufacturer's ability to select and reconstruct the right robot the acceptance criterion.