On this page

BOM revision vs product configuration, tracking robot versions and build applicability

BOM revision control identifies the selected parts and quantities in an approved structure. Record serial effectivity, meaning where a change applies, beside that revision and the complete product configuration. In this R-01 example, serial 002 selects HR-300 A and DW-HR-300 A, while serial 003 selects HR-300 B and DW-HR-300 B.

The product configuration also identifies the mechanical drawing, electronics and firmware selected for that build. Keep those references visible even when they stay unchanged. A release called “latest” leaves the approved selection for earlier serials unresolved.

R-01 is a fictional indoor inspection robot with five pilot serials, 001–005. ECO-017 approves a harness strain-relief manufacturing improvement from serial 003. It retains the controlled installation interfaces and acceptance requirements. The change does not automatically retrofit serials 001–002.

Record what changed and what stayed selected

Configuration field Original release Changed release
Product R-01 indoor inspection variant R-01 indoor inspection variant
Configuration ID CFG-R01-A CFG-R01-B
BOM identity BOM-R01 A BOM-R01 B
Harness selection HR-300 A HR-300 B
Harness drawing DW-HR-300 A DW-HR-300 B
Mechanical assembly reference DW-R01 A DW-R01 A
Electronics reference ECAD CB-200 A ECAD CB-200 A
Firmware 1.2.0 1.2.0
Serial applicability 001–002 003–005
Approval basis Recorded original release approval ECO-017 and recorded B-release approval

Keep the real approver and approval date in the release record. They are not invented for this fixture. Identify the change approval and the resulting baseline acceptance separately if the team's process uses different decisions.

Unchanged firmware and electronics references still belong in the matrix. Their presence makes the intended scope inspectable. It does not claim new test results or automatically prove that historical evidence covers the changed harness.

Define serial effectivity before a buyer or builder acts

Effectivity states where a change applies. In this example it is a serial boundary, from 003 in the five-unit pilot. Other products might use a date, lot, variant or defined combination. Choose a basis that purchasing and manufacturing can resolve without guessing.

Serial Planned configuration BOM Harness and drawing Release decision to confirm
001 CFG-R01-A BOM-R01 A HR-300 A, DW-HR-300 A Original A-release approval
002 CFG-R01-A BOM-R01 A HR-300 A, DW-HR-300 A Original A-release approval
003 CFG-R01-B BOM-R01 B HR-300 B, DW-HR-300 B ECO-017 and B-release approval
004 CFG-R01-B BOM-R01 B HR-300 B, DW-HR-300 B ECO-017 and B-release approval
005 CFG-R01-B BOM-R01 B HR-300 B, DW-HR-300 B ECO-017 and B-release approval

Add release status, approval references and dates, source locations and any authorised exception to a real matrix. Define how overlapping or missing applicability will be resolved before release. A proposed B row must remain distinguishable from an accepted B baseline.

The ECR, ECO and ECN guide explains the different change records. An engineering change authorisation should identify the implementation scope. A notification communicates the authorised decision to the people who must act on it.

Reconcile planned, received and installed identity

Purchasing derives two HR-300 A and three HR-300 B harnesses for the pilot. Stock and order records should preserve those revision groups. A receipt of five B harnesses would differ from the stated requirement, even though B is the newer revision.

Record the delivered identity and revision, related drawing or supplier documentation, quantity and intended allocation. If a receipt differs, keep it out of automatic allocation until the responsible engineering and purchasing owners disposition it.

During assembly, record what was actually installed against each serial. If a builder proposes harness A for serial 003 because B is unavailable, raise the exception before installation. The team's authorised engineering authority must decide whether a deviation is acceptable for that serial and under what checks. Record the decision, scope, evidence and expiry or closure conditions.

Do not edit CFG-R01-B to make an exception appear to have been the original plan. Preserve the approved configuration and link the deviation and as-built record to it. The as-designed, as-built and as-tested guide explains how these states relate.

Review evidence against the configuration it supports

The strain-relief improvement leaves the declared acceptance requirements unchanged. Engineering still needs to assess which manufacturing and verification records are affected, and whether earlier evidence can be reused with a justified applicability argument.

The robotics change-impact review shows how to keep an inspected proposal, owner findings and evidence actions connected. Arc's public capability record describes attributable review decisions and configuration-specific requirements and evidence. When evaluating a BOM workflow, ask to see how those approved change practices apply to the exact part and serial matrix.

Try the matrix on your next release before changing an order. Ask a buyer and a builder independently to select the harness for serial 002 and serial 003. Then verify their selections against the approved references and the pilot quantity table. Preserve any disagreement as a release-record correction to resolve.

Move faster without compromising engineering rigour.

Review one product release, its change decisions and supporting evidence with Arc.