OpenBOM is a candidate when a robotics team needs connected item catalogues, collaborative BOMs, sourcing and purchase planning. Arc is a candidate for connected robotics product structures, selected hardware/software build references and engineering review. Compare them on one released assembly, then follow its quantities and revisions into the proposed purchasing workflow.
The selection depends on which duties the team is assigning. A BOM revision defines design content. An order uses that content together with a quantity, current inventory and purchasing decisions. A build configuration also identifies the selected mechanical, electrical and firmware references. Evaluate the continuity between those records explicitly.
Comparison method and documented boundaries
This is an Arc-authored assessment for civilian industrial robotics teams coordinating design and pilot purchasing. OpenBOM is included for its documented item, BOM and procurement scope. Arc is assessed against its documented robotics record workflow. The common dimensions are item identity, structure, release context, quantity reconciliation, selected sources, build references and contributor handoffs.
Use the existing buyer-guide criteria for review, traceability, evidence and adoption discipline. The exercise here adds purchasing-specific acceptance questions and imports no numerical vendor scores. Official pages were inspected on 20 November 2026. Arc has a commercial interest in the comparison. No customer account, product trial, purchase order or integration was executed.
Compare item, BOM and order responsibilities
| Duty | OpenBOM documented scope | Arc evaluation scope |
|---|---|---|
| Item identity | Items organised in catalogues with part numbers and properties | Review selected part numbers, revisions and design references in the robotics record |
| Product structure | Multi-level BOM and revision capabilities | Demonstrate the assembly/part quantities and revisions needed for the build |
| Source and order | Vendor, sourcing and purchase-order workflow | Review source documents and draft handoffs, then test connection to the order owner |
| Build context | Witness the selected package's release and configuration workflow | Selected BOM, CAD, ECAD and firmware build references |
OpenBOM's documented model connects reusable items with BOM and sourcing information. Ask which subscription and permissions supply your required order functions. Arc's public robotics page describes reviewable supplier handoffs. Native ordering, inventory movement and receiving behaviour need separate evidence before those responsibilities are assigned to Arc.
Use the part-numbering guide to preserve internal IDs separately from MPNs and supplier SKUs. Apply the same identity and unit rules in both candidate workflows. A duplicate created to represent another vendor can otherwise split the same component's demand or obscure its approved source relationship.
Check how a released BOM becomes an order
OpenBOM's February 2026 release update says Orders can be invoked from a BOM revision and calculated from that revision's content. It also says quantity on hand is taken from current inventory. The current revision-control page documents released-revision Order BOM creation.
There is a documentation inconsistency to resolve during evaluation. The planning training page still contains wording that describes Orders from Latest only. Treat the dated update and current product page as the documented revision-based option, then have the vendor show your exact tenant workflow. Retain the order's source revision field and test it after a later design revision exists.
For either candidate, distinguish frozen design content from live inventory inputs. The team should be able to explain why an order quantity changed while the selected design revision stayed the same. Record inventory timing, any approved stock exclusions, packs, minimum quantities and open-order treatment. Verify those calculations in the offered workflow.
Run a five-robot purchasing exercise
This fictional R-01 pack uses two drive modules per robot. Each module needs one motor and four screws. The top-level robot needs another two screws. Five robots therefore require 5 × 2 = 10 motors and 5 × (2 × 4 + 2) = 50 screws. Reproduce the relationship rows using the multilevel BOM template.
BOM-R01 A selects harness A for serials 001–002. BOM-R01 B selects harness B for serials 003–005. The gross harness demand is two A and three B. The fixture has three accepted motors in stock and two on an open order due before the build. With those assumed quantities available, net new motor demand is 10 − 3 − 2 = 5. Record gross demand, accepted stock, open orders and net demand as separate fields.
| Exercise | Expected record in the fictional pack | Witness evidence |
|---|---|---|
| Roll up the BOM | 10 motors, 50 screws, two harness A and three harness B | Source relationships, selected revisions and calculation |
| Reconcile motors | Five new motors under the stated stock/order assumptions | Stock eligibility, open-order timing and demand basis |
| Select purchasing sources | Approved manufacturer and seller per item | MPN, quote, packaging, delivery and authorisation check |
| Issue an order handoff | Selected design release and purchasing inputs | Source revision field, approval and receiving-system result |
| Create a later design revision | Prior order remains traceable to its accepted source | Reopened order view and historical release retrieval |
These values are test inputs and expected arithmetic, with no observed software result. Run the same exercise in OpenBOM and the proposed Arc/purchasing solution. Keep manual calculation, configured behaviour and integration assistance recorded. Include a rejected source substitution and a partial receipt so the team can examine the exception path.
The distributor guide supplies part-specific authorisation and delivery checks. The costed BOM example separates design cost from pack-rounded expenditure. Source approval and a vendor price remain distinct decisions.
Keep build references and compatibility evidence connected
Add CAD drawing, ECAD and firmware references to the witness pack. Record which robot serials select each combination. If firmware remains unchanged after a harness revision, ask the reviewer to locate the compatibility decision and evidence that justify it. Use the configuration matrix to state those selected references independently of the purchasing quantity.
For OpenBOM, demonstrate the data model and selected package that keep those references with the release. For Arc, demonstrate the proposed build record and change review alongside the purchasing handoff. Require stable IDs and an explicit authoritative source for each exchanged value. Check a failed synchronisation before relying on the combined workflow.
Select by the witnessed workflow and its ownership
Choose OpenBOM when its demonstrated item-to-order process meets the purchasing requirements and the team can govern its release and inventory decisions. Evaluate Arc when its robotics build-reference and review workflow fits the engineering need, with an agreed and tested order handoff. A combined solution needs its own ownership map, integration scope and exception handling.
Request comparable offers naming subscriptions, user roles, implementation, migration, training, integrations and support. Reconcile a representative release and its history before cutover. Retain the exact version, package, source revision and evidence from the witness exercise. Those records make the final decision inspectable.
OpenBOM vs Arc questions
Can OpenBOM create an order from a released BOM revision?
The February 2026 update and current product documentation describe that option. One training page retains different wording. Verify the operation in the offered tenant and retain the source revision reference in the resulting order.
Does selecting a BOM revision freeze stock quantities?
The cited update says quantity on hand comes from current inventory. Preserve the chosen design revision separately from the timestamped inventory and purchasing inputs used to calculate an order.
Does Arc execute procurement in this comparison?
The documented scope here is its robotics product record and reviewed supplier handoff. Require direct evidence for the selected order, inventory and receiving workflow, including any external purchasing system or integration.