On this page

Robot Build Records: Serial Numbers, Substitutions and Field Retrofits

A robot build record should identify one physical robot and preserve the events that changed its installed configuration. Record the old and new component identities, the authorising decision, the time and location of the change, applicable evidence and acceptance state. Physical state changes at the actual installation. Update its recorded snapshot when that event is captured and checked, retaining both times if capture occurs later. Record acceptance separately when the required checks and review are complete.

An approved BOM states the selected design. A serial-specific record states what was installed, including an authorised departure or later replacement. Keep both recoverable so a later engineer can explain how the physical unit relates to its starting release. As-designed, as-built and as-tested guide

Use a unit header and an event log

Give the record a stable robot serial and model identity. Record the source configuration, accepted release package and installed firmware reference. Keep location and custodian at the level needed to find the unit and its records. The example uses fictional work areas, without customer names or personal details.

NASA's configuration-status accounting method preserves current and historical documentation, change states and discrepancy dispositions. This event log applies that record principle to one robot. It is a proposed working format and supplies no assurance approval or NASA programme requirement. NASA configuration-management guidance

Unit-header field Value to enter
Robot serial and model/variant
Record ID and current revision
Original configuration, BOM and package references
Current physical configuration snapshot reference
Last accepted configuration and acceptance reference
Installed firmware artefact and version
Current location and responsible record owner
Open replacement, discrepancy or acceptance actions

Keep events appendable. A correction should identify the earlier entry and its corrected fact, preserving the reason and actor. A changed physical configuration should receive a new snapshot reference. Replacing the entire row with the newest part can erase the evidence needed to interpret an earlier inspection.

Event ID, occurrence time and capture time Robot location Position and event Old item/revision, serial or lot New item/revision, serial or lot Authorising record Work and evidence references Acceptance state and current-state effect

Where a component is tracked by lot, record the lot and quantity installed. Where it has a unique serial, retain that serial with the item and revision. Identify its position so two identical sensors or drive modules remain distinguishable.

Reconstruct serial 003's original build

R-01 is the fictional indoor inspection robot from Arc's BOM series. Serial 003 selects CFG-R01-B, BOM-R01 B, HR-300 B and DW-HR-300 B after ECO-017. The original mechanical drawing is DW-R01 A, electronics reference ECAD CB-200 A and firmware selection 1.2.0. Serials 001–002 retain A while 003–005 select B. R-01 configuration matrix

The filled history below is a later teaching snapshot, B0. It assumes serial 003 was built from an accepted B package after the separate manifest candidate hold had been resolved. All dates, serials, lots, record IDs, installation events and acceptance states are fictional. They illustrate completed-record fields and make no claim about an actual build, test or maintenance visit.

The unit header identifies record BR-R01-003 01. Its original package is MAN-R01-B-AC01, a hypothetical accepted distribution package. The firmware install record identifies ART-FW-R01-120-01, version 1.2.0, on CB-200 A. Snapshot ASB-003-01 records the initial physical unit. Original acceptance decision ACC-003-01 references that snapshot and its scoped evidence.

The initial installations below use None, initial installation in the blank template's old-item field. Their displayed times are event-occurrence times. In this fictional history, each event is captured and checked at the same time, so the capture-time field matches. A real late entry should retain its later capture time separately.

Event ID and time Location and position Installed identity Authorising record Evidence in the fictional history State after event
E01, 2027-01-18 at 10.00 UTC Build area BA-01, harness position H1 HR-300 B, serial H-B-003, lot HB-L01, quantity 1 ea MAN-R01-B-AC01 and applicable installation instruction Receipt REC-HB-01 and inspection INSP-HR-003 01, with DW-HR-300 B identified Harness installation recorded in ASB-003-01
E02, 2027-01-18 at 11.00 UTC BA-01, sensor position S1 SN-400 A, serial S-A-003, lot SA-L01, quantity 1 ea MAN-R01-B-AC01 and sensor installation instruction Installation record INST-S-003-01, calibration-context record CAL-S-003-01 and unit check RPT-003-01 Initial unit accepted under ACC-003-01, scoped to ASB-003-01

A real inspector would retrieve those actual receipt, installation and report records. They would check that each applies to the identified component and snapshot. The log stores their references and decision, with numerical results and underlying evidence retained in the appropriate source records.

At B0, the unit has H-B-003 and S-A-003 installed. A later reader asking about an observation from that time should recover ASB-003-01, the sensor serial and its calibration context. A later replacement must preserve that earlier association. Robot sensor-calibration evidence guide

Separate three kinds of departure

A preapproved substitution is an option already authorised for the specified build and conditions. Record the exact alternate, its authority and actual installation. An unapproved mismatch is an observed disagreement that needs disposition. A later retrofit or replacement is an individually scoped modification to an already built unit.

Situation Record decision Effect on the unit and baseline
Preapproved alternate selected during build Confirm the alternate's approval and applicability before issue, then record its actual identity Unit record shows the approved alternate selected for that build.
Harness A offered for serial 003 with no scoped approval Raise a discrepancy and hold the affected issue or installation CFG-R01-B continues to select B. A proposed exception remains pending until authorised.
Later authorised sensor replacement on serial 003 Open an individual work authorisation, preserve old/new identities and define required checks Physical history changes when the replacement is installed. Acceptance follows its own decision.

The earlier A/B harness split remains the pilot's design selection. A maintenance event on one serial does not rewrite that selection for every robot. A planned substitute also cannot become an installed fact merely because it appears in a purchase order.

Log the later sensor replacement without hiding the hold

Snapshot B1 follows the initial build by several weeks. A fictional maintenance proposal replaces S-A-003 with another SN-400 A sensor, serial S-A-103 from lot SA-L02. It is a like-for-like item and revision replacement, with a different physical sensor identity.

MWA-003-01 authorises that one replacement at position S1 on robot 003. The sensor owner defines the required installation, calibration-context and unit checks in RV-003-01. The designated acceptance authority must review the resulting evidence before accepting the maintained unit. This scope leaves H-B-003, CB-200 A and firmware 1.2.0 selected and gives no authority to modify other serials.

Event ID and time Location and event Old identity New identity Authority and work Evidence and acceptance state
E03, 2027-03-03 at 14.00 UTC Maintenance area MA-01, authorise replacement SN-400 A, S-A-003, SA-L01 Proposed SN-400 A, S-A-103, SA-L02 MWA-003-01, checks defined in RV-003-01 Authorisation recorded. Physical snapshot remains ASB-003-01.
E04, 2027-03-04 at 09.00 UTC MA-01, remove old sensor and install new at S1 SN-400 A, S-A-003, SA-L01 Installed SN-400 A, S-A-103, SA-L02 MWA-003-01 and replacement record REPL-003-01 Physical snapshot becomes ASB-003-02. Required checks and maintained-unit acceptance are pending.
E05, 2027-03-04 at 09.15 UTC MA-01, review open check actions S-A-003 retained in removal history S-A-103 remains installed RV-003-01 with sensor owner and acceptance authority assigned CAL-S-003-02 and RPT-003-02 are pending. No new acceptance decision is recorded.

At B1, the current location is MA-01 and the current physical sensor is S-A-103. The record owner is the maintenance record owner. The recorded physical snapshot is ASB-003-02, and the current disposition is Hold maintained-unit acceptance pending RV-003-01 checks. ACC-003-01 remains the last accepted historical decision for ASB-003-01. It does not accept ASB-003-02. Show both facts in the header and keep the maintained-unit acceptance state Pending.

If the checks pass and their review is accepted, append a new decision referencing ASB-003-02 and the actual evidence. If a check fails or remains incomplete, preserve the installed configuration and the unresolved disposition. The verification-evidence guide explains the resulting applicability review.

Check the two directions of the trace

From robot 003, retrieve its installed harness, original sensor, replacement sensor and the events that changed state. From sensor S-A-103 or lot SA-L02, retrieve robot 003, position S1, installation time, work authorisation and current acceptance hold. Keep the removed S-A-003 entry so an earlier report still resolves to the right component.

Before accepting the record, ask another reader to reconstruct B0 and B1 independently. They should identify the physical change at E04, the pending checks at E05 and the unchanged design baseline. Missing identity or evidence is an open record action with an owner and affected scope.

Robot build-record questions

When does the current physical configuration change?

It changes at the actual installation time. Capture and check that occurrence in the record, preserving a separate capture time where entry is delayed. In this example E04 creates the recorded snapshot ASB-003-02 and acceptance remains pending.

Does a like-for-like replacement preserve the old calibration evidence?

Keep the earlier evidence with its original sensor and conditions. The responsible owner must determine what the new serial and installation need before a new observation or acceptance decision can use the replacement.

Should an approved substitute alter the original BOM?

Follow the project's change policy. An individual authorised departure can remain linked to the unit, while a revised design baseline needs a separate controlled change. Preserve the original selected plan and actual installation.

What if the replacement is authorised but has not been fitted?

Record it as proposed or authorised work. The physical snapshot continues to show the installed old component until an actual installation event is recorded.

Continue the serial review

Use the whole-robot manifest to recover the selected starting package. Use the as-designed/as-built/as-tested guide and sensor-calibration guide for the associated evidence decisions.

Move faster without compromising engineering rigour.

Bring one robot serial and a proposed replacement event to a demo.