32. Repair, replacement, supplier RMA, warranty and reinspection assurance
Prove restoration or replacement against exact authoritative work/custody/receipt evidence and independent reinspection without duplicating or mutating any source-domain transaction.
Purpose
Prove restoration or replacement against exact authoritative work/custody/receipt evidence and independent reinspection without duplicating or mutating any source-domain transaction.
Quality Engineer, Product Engineer, Stores Supervisor, Supplier Quality Engineer, Quality Inspector, three different QA Head authorities, QMR / Project or Contract Manager / Auditor read-only
QRA-… rejected v1 → approved v2 → Product Engineering → reconciled original serial return → failed reinspection → PASS v2 → separate-QA CLOSED.
Before you begin
- An active serialized NCR has a current APPROVED REWORK/REJECT investigation
- The linked MRB disposition is APPROVED/CLOSED and EXECUTED against the exact identity and quantity
- The owning module already contains the required maintenance, subcontractor custody or accepted replacement receipt record
- At least one same-site ACTIVE, CLEAN evidence version exists
- Author, scope QA, Product Engineer, coordinator, Inspector, reinspection QA and closer are separate named authorities
Exact route, identity and source-authority controls
Scope requires one active serialized NCR, its current approved investigation and exact executed MRB disposition. Mode and disposition must agree, and QA/Product Engineering block stale SHA-256 fingerprints.
Stores Supervisor coordinates INTERNAL_REPAIR. Supplier Quality Engineer coordinates EXTERNAL_REPAIR, SUPPLIER_RMA, WARRANTY or REPLACEMENT. Permission alone cannot cross that route boundary.
Internal repair requires an exact completed PASS maintenance work order. External repair/RMA/warranty requires a same-site, same-supplier, same-item/serial reconciled subcontractor return with sufficient returned quantity.
A replacement is a different active physical instance of the same item, from the coordinated supplier when declared, tied to a receipt whose authoritative inspection disposition is ACCEPT or ACCEPT_UNDER_DEVIATION. It never overwrites the rejected serial.
The Quality Inspector cites the exact repaired original or replacement serial. Unique numbered checks derive PASS only when every result passes; failed versions remain immutable and can be replaced after additional authoritative work.
QA reinspection review requires an unchanged fulfillment fingerprint and cannot accept FAIL. Closure requires another QA Head, one accepted PASS reinspection and still-unchanged authoritative fulfillment evidence.
Flow 26 creates zero notification deliveries and never changes NCR/investigation/MRB, maintenance, subcontractor custody, SCAR, vendor, receipt, inspection, physical instance, current_stock or stock_ledger records.
Procedure
- 1
Create and submit exact-source scope v1 as Quality Engineer; reject it as a different QA Head.
- 2
Create immutable v2, approve an unchanged fingerprint as QA and approve technical basis as a separate Product Engineer.
- 3
Coordinate the mode through the route-specific Stores or Supplier Quality authority and cite existing owning-module records.
- 4
Record exact authoritative fulfillment without changing it; then retain a failed reinspection and record a later PASS version as Quality Inspector.
- 5
Accept the unchanged PASS as a separate QA Head, close as another QA Head and reconcile all source, custody, stock, ledger and delivery witnesses as Auditor.
Expected result
- Lifecycle follows DRAFT → SCOPE_REVIEW → TECHNICAL_REVIEW → COORDINATION → FULFILMENT → REINSPECTION → REINSPECTION_REVIEW → CLOSURE_REVIEW → CLOSED
- Rejected scope and reinspection versions remain immutable
- QA and Product Engineering reject stale exact-source fingerprints
- Internal and external coordination roles cannot cross routes
- A repaired original retains the exact rejected serial; a replacement is a separate accepted physical identity
- FAIL cannot be accepted and checklist results derive the declared outcome
- Author, scope reviewer, Product Engineer, coordinator, Inspector, reinspection reviewer and closer remain separately attributable
- Flow 26 creates zero notification deliveries and never changes Quality source, maintenance, custody, supplier, receipt, inspection, physical identity, inventory or ledger records
- Auditor mutation attempts are rejected