A robotics pilot-build readiness checklist should identify the exact build scope, assign an owner to every gate and show the evidence required to proceed. Hold an affected operation when its parts, instructions or release references disagree. Restart it only after the responsible owners correct the discrepancy, approve the replacement material and confirm that the builder received it.
This guide prepares a team to begin a controlled pilot build. The decision covers specified serials and operations. Product acceptance, production ramp and permission to operate the finished robot require their own evidence and decisions.
R-01 is the fictional indoor inspection robot used in Arc's BOM series. The five-unit pilot needs two HR-300 A harnesses for serials 001–002 and three HR-300 B harnesses for serials 003–005. Every instruction identifier, gate record and disposition added below is a fictional extension for teaching. There is no executed customer build behind the example. Robotics BOM template
Define the release that the checklist covers
Name the product, serial range, location, operations and release before reviewing readiness. A decision to begin chassis preparation has a different scope from a decision to kit harnesses or energise a completed robot. Give each permitted scope an identifiable work package so builders can tell where authorisation ends.
For R-01, CFG-R01-A and BOM-R01 A select HR-300 A with DW-HR-300 A for 001–002. ECO-017 approves a strain-relief manufacturing improvement. CFG-R01-B and BOM-R01 B select HR-300 B with DW-HR-300 B for 003–005. The installation interfaces and acceptance requirements remain unchanged. Both configurations select DW-R01 A, ECAD CB-200 A and firmware 1.2.0. Earlier serials have no automatic retrofit instruction. Revision and configuration matrix
Record approval of the change and acceptance of the resulting build package where your process treats them as separate decisions. NASA's configuration-management guidance distinguishes identifying a baseline, controlling changes and verifying implementation. These concepts support the record discipline here. They do not assign NASA lifecycle gates to this robot pilot. NASA configuration-management guidance
Use a gate record with a restart condition
For each gate, record its scope, accountable owner, evidence reference, decision and unresolved action. A green cell without a recoverable document leaves the reviewer unable to explain what passed. A hold should identify the affected operation and the exact condition that will clear it.
Use the following table as a starting record. Its evidence column describes what the R-01 owners would need to inspect. It supplies no actual approval, inspection or test result.
| Readiness gate | Accountable owner | Evidence to inspect | Go or hold rule | Restart condition after a hold |
|---|---|---|---|---|
| Defined build scope | Pilot-build lead | Serial allocation, operations, work-package ID and named release authority | Go when every planned serial and operation resolves to one authorised package. Hold ambiguous scope. | Issue the corrected scope and have affected owners accept it. |
| Configuration and effectivity | Product-data owner | BOM-R01 A/B, CFG-R01-A/B and ECO-017 implementation scope | Go when 001–002 select A and 003–005 select B, with common references visible. Hold missing or overlapping selection. | Correct the authoritative selection, obtain release approval and replace affected handoffs. |
| Materials ready for issue | Materials lead | Revision-specific requirements, receipts, allocation and required inspection records | Go when accepted material covers the operation's quantity and revision. Hold unidentified, short or unaccepted material. | Reconcile the receipt or shortage and approve the revised allocation before issue. |
| Build instructions agree | Manufacturing engineer | Released instructions and their part, drawing and serial references | Go when the instructions reproduce the selected configuration. Hold any conflicting instruction. | Correct and reapprove the instruction, withdraw its affected predecessor and obtain builder readback. |
| Tools and process ready | Manufacturing lead | Required fixtures, settings, inspection equipment and operator preparation | Go when the specified operation can use its controlled method. Hold missing equipment or unresolved process limits. | Supply the evidence required by that method and confirm the operation can proceed. |
| Programming and checks prepared | Firmware and verification owners | Installable 1.2.0 artifact, programming instruction and approved checks with limits | Go when the package identifies the selected firmware and executable checks. Hold missing references or undefined criteria. | Release the missing material and review its applicability to the planned configuration. |
| Operating boundary and final permission | Build release authority | Relevant hazard controls, work boundaries, open-action dispositions and gate evidence | Go only for the stated operations whose prerequisites are accepted. Hold affected operations with unresolved prerequisites. | Review closure evidence and issue a new bounded permission to proceed. |
Several people may share evidence, but each gate needs one accountable owner. A small team can assign several roles to one engineer. Keep technical acceptance, material allocation and final build permission individually attributable even when the same person performs them.
Work a wrong-revision instruction through the hold
The fictional B-build candidate contains WI-HR-INSTALL 04. Its applicability names serials 003–005, but its installation step calls for HR-300 A and DW-HR-300 A. A reviewer checking serial 003 therefore finds a direct conflict with CFG-R01-B.
The manufacturing engineer marks that instruction gate Hold. The pilot-build lead holds harness kitting and installation for 003–005, together with operations that depend on that installation. The reason is recorded against the candidate instruction and B-build package. The team can assess independently scoped work against its own prerequisites, with explicit permission for any work that proceeds.
The correction changes the instruction. It does not require rewriting the already approved B configuration to agree with the erroneous step. The manufacturing engineer authors WI-HR-INSTALL 05 and the designated release authority reviews its exact content.
| Instruction field | Held WI-HR-INSTALL 04 | Corrected WI-HR-INSTALL 05 |
|---|---|---|
| Applicable robot serials | 003–005 | 003–005 |
| Source configuration and BOM | CFG-R01-B, BOM-R01 B | CFG-R01-B, BOM-R01 B |
| Harness installation step | Select one HR-300 A using DW-HR-300 A | Select one HR-300 B using DW-HR-300 B |
| Other selected build references | DW-R01 A, ECAD CB-200 A, firmware 1.2.0 | DW-R01 A, ECAD CB-200 A, firmware 1.2.0 |
| Approval state for this scope | Held before issue to the B build | Reapproved for the stated B-build operation |
| Earlier serials | Outside this instruction's applicability | 001–002 remain governed by their A-build package |
The corrected instruction also tells the builder to confirm the harness identity and record the installed revision against each serial. If the identified material differs, the operation returns to hold for owner disposition. A changed label alone cannot establish that the physical harness conforms to the selected drawing.
Make the restart decision concrete
In this fictional disposition, the manufacturing engineer records the difference between 04 and 05. The release authority's approval record identifies WI-HR-INSTALL 05 and its B-build applicability. The document owner marks 04 unavailable for use in that scope while retaining it as discrepancy evidence. The builder confirms receipt of 05 and independently selects HR-300 B for serial 003 from the package.
The materials lead separately confirms that the allocated B harnesses have the required identification and acceptance records. The verification owner reviews which manufacturing and check documents ECO-017 affects. Unchanged acceptance requirements still need an applicability assessment for the changed manufacturing revision.
The final readiness disposition permits harness kitting and installation for 003–005 under WI-HR-INSTALL 05 once those prerequisites are accepted. It preserves the A allocation for 001–002. It leaves product acceptance and powered operation to their specified later decisions. In a real record, retain the actual actor, timestamp and reviewed evidence for each approval and acknowledgment.
Use these checks at the restart review.
- Confirm the held instruction and every affected copy have an explicit disposition.
- Trace serial 003 to CFG-R01-B, BOM-R01 B, HR-300 B and DW-HR-300 B.
- Confirm the same instruction applies to 004–005 and preserves the common selected references.
- Have the builder locate the replacement instruction and explain the revision selection.
- Record the operations allowed to restart and any operations still held.
Keep unresolved actions visible after permission to build
A readiness record remains useful after work begins because it explains the authorised starting point. Retain the accepted package, gate evidence and hold history with the build record. Record any later change or exception against that starting point.
Give an open action an owner, affected scope, decision needed and closure evidence. If it has no bearing on a permitted operation, record that assessment. If its effect is unknown, the relevant gate remains unresolved. Avoid a percentage-complete score that lets several completed administrative tasks obscure one missing installation instruction.
Robotics pilot-build readiness questions
Does a working prototype make a five-unit pilot ready?
A prototype supplies useful evidence, but the pilot still needs an unambiguous release, repeatable instructions, revision-specific material and prepared checks. Review those prerequisites for the intended build operations before issuing permission.
Can we start part of the build while one gate is held?
An independently scoped operation can proceed when its prerequisites and boundaries are accepted by the responsible authority. Record that permission. Work that depends on the held harness installation remains held.
Who clears a wrong-revision instruction?
The instruction's authoring owner corrects it, the designated authority approves the replacement and the receiving builder confirms the revised package. Material allocation and any technical exception need their own responsible-owner decisions.
Does ECO-017 require retrofitting serials 001–002?
The R-01 teaching fixture applies B to 003–005 and contains no automatic retrofit authorisation. Any proposed change to earlier serials needs a separately reviewed scope and implementation instruction.
Is this checklist a product acceptance test?
It is a preparation record for permission to perform defined build work. The resulting robot needs the acceptance evidence and operating permissions specified for its actual configuration and application.
Continue the release preparation
Prepare the underlying quantities with the robotics BOM template. Check the selected references and serial boundaries in the BOM revision and product configuration guide.
Collect the approved package with the whole-robot release manifest. Prepare the serial-specific installation and exception records with the robot build-record guide.