Robot component supplier change management should end in a traceable acceptance decision for the installed system, with each supplier claim tied to the evidence and configuration that supports it. Identify the old and candidate component, declared changes and effectivity, compare report scope with the robot’s requirements and interfaces, then record retained, revised, rejected or unresolved evidence uses. A supplier report labelled pass does not automatically accept the replacement.
For a hardware, systems or supplier-quality manager, the trigger is often ordinary procurement: a replacement gripper, sensor or controller arrives with reports for another revision or narrower conditions. The useful deliverable is a claim-to-installed-system evidence acceptance record, with owners and bounded closure actions.
Ask which claim the supplied evidence actually supports
A supplier’s test can be valid and useful without covering your installed configuration. Its component revision, firmware, mode, fixture, load and environment may differ. Its report may assess one property while the acceptance requirement concerns the behaviour of the complete robot.
NASA’s product-verification guidance applies the conformance question to products that are built, coded, bought or reused. It identifies the product, requirements baseline, verification plan and enabling products as process inputs, and calls for examining data validity and discrepancies. Those principles help a receiving team examine purchased evidence without treating NASA’s flight acceptance programme as a universal robot procurement rule.
Maintain two decisions. The engineering review asks whether the candidate can meet the installed requirements. The evidence review asks which supplied and internal records support that argument. Neither should collapse into an unqualified “supplier approved” flag.
A fictional replacement gripper with conditional reports
GRIP-25 is an invented supervised robot cell moving marked test blocks. Approved teaching configuration CELL-A25 declares gripper GRP-25 rev A, serial G25-011, firmware GF-25 v1.8, jaw set JAW-25A, mounting ADAPT-25 rev A and controller GC-25 v1. Proposed CELL-B25 replaces the gripper with rev B, serial G25-104, firmware v2.0 and jaw set JAW-25B while initially retaining the mounting and controller.
SCN-25 is the fictional supplier change notice. It declares a jaw geometry and firmware change and identifies candidate shipment lot LOT-B25. It does not establish unchanged power behaviour, command semantics or loaded retention. All records, limits and reports here are teaching inputs, with no real supplier, completed test or customer acceptance.
The selected installed obligations are GRP-PWR-250 v1, peak input demand ≤45 W at IF-PWR-25 under LOAD-25 v1, and GRP-RET-251 v1, retention of the specified 0.8 kg test block through MOVE-25 v1. IF-CMD-25 v1 separately defines the controller/gripper command and status meanings. The limits and motion profile are invented and do not establish safe lifting or use around people.
The candidate dossier names SUP-PWR-25, a hypothetical report for rev B at nominal supply during unloaded closing, and SUP-RET-25, a hypothetical report for rev A with JAW-25A under a different static load case. Report values, raw data and actual review outcomes are not supplied. The exercise is to determine which evidence each installed claim still needs.
Identify old, candidate and installed effectivity
NASA’s configuration-management guidance calls for unique product and configuration-document identifiers and consistency between the product and its information. A receiving record should therefore distinguish the intended replacement from what was actually installed and what each report assessed.
| Identity field | Old teaching state | Candidate declaration and receiving check |
|---|---|---|
| Component and effectivity | GRP-25 rev A, G25-011 in CELL-A25. | GRP-25 rev B, G25-104 from LOT-B25 proposed for CELL-B25. Record supplier and internal effectivity separately. |
| Firmware and settings | GF-25 v1.8, settings set SET-G25A. | GF-25 v2.0, SET-G25B to identify and inspect. A version label alone does not establish loaded settings. |
| Jaws and accessories | JAW-25A and the declared fastener/accessory set. | JAW-25B with its geometry and accessory identities. Receiving inspection reconciles actual items with the declaration. |
| Installation interfaces | ADAPT-25 rev A, IF-PWR-25 and IF-CMD-25 v1. | Initially retained, with fit, clearance, power and command compatibility unresolved. |
| Reports and reference state | Historical evidence for CELL-A25 retains its original scope. | SUP-PWR-25 identifies rev B/unloaded closing. SUP-RET-25 identifies rev A/JAW-25A/static case. Neither is relabelled as installed CELL-B25 evidence. |
| Decision scope | Teaching historical baseline CELL-A25. | SCN-25 review for the identified candidate only, with covered variants, units and conditions to be stated by authority. |
Keep declared sameness separate from verified sameness. A supplier statement that the flange remains unchanged is evidence to inspect, with its exact scope. It does not answer jaw clearance during MOVE-25 or controller interpretation of a status code. Missing declarations stay unknown and go to a named owner.
Use a claim-to-installed-system evidence record
The record should make the proposed evidence use explicit. “Report received” records possession. “Reviewed” records inspection. “Accepted for claim X in configuration Y” records a bounded judgement. The table gives proposed dispositions for this unexecuted example.
| Installed claim | Supplied scope | Proposed disposition and gap | Owner and closure evidence |
|---|---|---|---|
| GRP-PWR-250: loaded peak demand ≤45 W | SUP-PWR-25: rev B at nominal supply during unloaded closing. | Retain as supporting information for its assessed mode. Installed loaded peak claim remains unresolved. | Electrical/verification owners assess loaded cycle, supply and settings. Obtain applicable report, supplement or internal evidence. |
| GRP-RET-251: specified block retained through MOVE-25 | SUP-RET-25: rev A with JAW-25A in a different static case. | Reject proposed direct closure for rev B/JAW-25B and dynamic profile. Preserve the original report. | Mechanical/verification owners require a justified transfer argument or evidence for candidate jaws, block and motion. |
| Mounting and clearance | SCN-25 declares unchanged mounting flange, with changed jaws. | Retain the declaration as input. Installed fit/clearance evidence and accessory reconciliation remain open. | Mechanical/integration owners compare controlled geometry and actual installed configuration. |
| IF-CMD-25 command/status semantics | GF-25 v2.0 is declared, but its change details are absent. | Unresolved compatibility. Shared connector and field names do not establish semantics. | Controller/supplier interface owners obtain revision notes and both endpoint definitions, then plan compatibility cases. |
| Candidate configuration/effectivity | SCN-25 names rev B and LOT-B25. | Revise receiving record when actual serial, firmware, settings and accessories are known. No blanket variant acceptance. | Configuration and supplier-quality owners reconcile the candidate and record covered units/variants. |
“Rejected” in the retention row describes the proposed direct use of that report. It is not a measured failure of rev B. A stronger applicability argument could be reviewed later, with its supporting facts retained. Unknown evidence is neither proof of failure nor permission to accept.
Do not weaken GRP-PWR-250 to accommodate a narrower supplier report. If the installed obligation must change, the requirements authority must assess and approve that revision. Evidence sufficiency is then evaluated against the revised claim. Procurement convenience does not silently revise engineering intent.
Review report provenance and limitations before reuse
Inspect the report revision, assessed serial or representative article, firmware/settings, method, equipment, conditions, result definition, anomalies and reviewer identity. Resolve whether the supplier used an applicable configuration and whether the data support the stated comparison. A cover-page pass without its conditions cannot close the acceptance record.
Ask for enough supporting information to judge the claim under the programme’s data agreement. Raw data may be important for some decisions, while a controlled report can be sufficient for others. Record access and scope limitations rather than promising universal access to a supplier’s internal records.
NASA’s technical-data guidance describes data identification, metadata, access, responsibilities and distribution limits. The transferable question here is whether the receiving reviewer can retrieve and interpret the authoritative evidence needed for its decision. A broken link or unavailable appendix is an evidence gap with a responsible owner.
Use the robotics evidence ledger for the full report-level applicability record. This checklist owns the supplier-to-installed-system acceptance bridge and receiving effectivity, with only the fields needed to expose those gaps.
Preserve the acceptance decision and installed release conditions
ACC-REV-25 is the proposed review record. Its present teaching disposition is hold candidate acceptance: power coverage is incomplete, retention evidence does not directly cover the candidate, clearance and command compatibility are unresolved, and actual receiving configuration is unconfirmed. No component defect, test outcome or real authority decision has been established.
Each owner should return a finding, inspected source revisions, applicable scope and closure evidence. Retained evidence stays attached to the claim it supports. Revised records preserve the change from the supplier declaration to the actual installed state. Rejected evidence uses retain their rationale. A later approval records the exact candidate, effectivity and conditions accepted.
Keep component acceptance, permission to install for investigation, evidence acceptance and robot release distinct in the project’s authority model. A candidate may be authorised for a controlled integration assessment while operational release is still pending. The configuration-state guide explains the shared record definitions.
For a wider dependency sweep after the replacement proposal, use the engineering change-impact guide. The robotics model-change dossier remains the owner for its M1-to-M2 case. GRIP-25 does not recreate that model-change example or the payload power evaluation.
Evaluate Arc with a conditional supplier report
Arc’s connected programme records can relate supplier evidence references to requirements, systems and interfaces. Its configuration capability represents applicability and baselines, while controlled change and attributable reviews preserve the proposed acceptance and owner decisions.
For a demo, create the old/candidate identities and installed requirements, then attach a clearly synthetic report for unloaded rev B behaviour and a historical rev A retention report. Ask the reviewers to retain the narrow power evidence, reject direct candidate-retention closure and keep installation acceptance held. Inspect how the configured record shows effectivity, limitations and the remaining evidence actions.
Arc supports the engineering context and review history. Its public capability reference does not establish supplier-portal delivery, purchasing execution, manufacturing genealogy or automatic component acceptance. Agree authoritative procurement, quality, design and test systems before connecting their records.
Questions for supplier-change acceptance
Does a supplier’s passing component report accept the installed robot?
It supports the claim and conditions actually assessed in that report. The installed system still needs an applicability argument for its component revision, settings, interfaces, loads and operating conditions, plus evidence for any system obligations the supplier report does not cover.
Can evidence for an older component revision be retained?
Yes, for its original claim and any justified candidate use. Identify the assessed revision and property, inspect the changed dependencies and record the reviewer’s applicability rationale. A shared part name or form-fit label does not by itself establish equivalence.
Is an unsupported supplier claim a failed capability?
No. Mark the claim or proposed evidence use as unresolved or unsupported for the stated acceptance decision. Request the missing scope, report or applicability argument. A rejected evidence-use argument is different from a component test failure.
What should the change notice include beyond the new part number?
Identify old and candidate revisions, serial or lot effectivity, firmware, settings, accessories, mounting, declared changes and remaining unknowns. Link the affected requirements, interfaces, evidence and owners. The notice must let the receiving team determine which installed configurations it actually covers.
Can a conditionally accepted component enter every robot variant?
Only within the authorised scope and conditions. Record covered variants, settings, loads, effectivity and exclusions, with open actions for unsupported configurations. A conditional disposition should not become a blanket accepted status.