22. First article plan, report and acceptance
Prove one first article against an exact approved configuration through versioned plans and reports with five-person authority separation, complete characteristic coverage and controlled evidence.
Purpose
Prove one first article against an exact approved configuration through versioned plans and reports with five-person authority separation, complete characteristic coverage and controlled evidence.
Product Engineer, different Configuration Manager, separate Quality Inspector, separate Quality Engineer, different QA Head, Supplier Quality/Auditor read-only
FAI-E2E-001 for E2E-ACT-001 rev B / released BOM B / baseline PB-E2E-001 v1 → plan v1 rejected → plan v2 approved → report v1 rejected → passing report v2 accepted.
Before you begin
- The item is ACTIVE and APPROVED at the exact current revision
- Any selected BOM is RELEASED for that item; any selected product baseline is RELEASED at the same site and snapshots the exact hardware revision and BOM
- Any selected product unit is assigned to that baseline and site; any selected supplier is registered and AVL approved
- Five separate eligible test users exist for Product, Configuration, Inspection, Quality review and QA acceptance
- At least one ACTIVE, CLEAN controlled evidence version exists at the same site
FAI authority and configuration boundaries
The plan snapshots approved item revision, optional released BOM, optional released product baseline hardware configuration item, optional product unit and supplier. A mismatched or draft source is rejected.
Scope, drawing/specification/process references, characteristics, source snapshot and evidence are fixed. Configuration rejection leaves the version intact and permits a separately recorded next version.
The report must contain exactly one PASS or FAIL result for every characteristic in the approved current plan. Duplicate, missing or foreign characteristic IDs are rejected.
Every failed result must link an open NCR for the same site and item at or below the FAI classification. A passing result cannot carry a failure NCR.
A Quality Engineer different from the plan author, Configuration approver and inspector decides report completeness. Rejection retains the report and returns the FAI for a new immutable report version.
A fifth named user may accept only a passing, independently reviewed report. If external acceptance is required, a reference must be captured first; Moduvio does not send the external message.
FAI acceptance updates no stock, ledger, item, BOM, baseline, product unit or supplier approval. It does not authorize shipment or customer delivery.
Supplier Quality Engineer and Auditor can reconcile the chain but cannot author, configure, inspect, review or accept an FAI.
Procedure
- 1
Create and submit plan v1 as Product Engineer.
- 2
Reject v1 as a different Configuration Manager; create/submit immutable v2 and approve it.
- 3
Submit complete report v1 as a separate Quality Inspector and reject it as a separate Quality Engineer.
- 4
Submit passing immutable report v2 and have Quality Engineering accept completeness.
- 5
As a fifth QA Head, record final acceptance with required evidence and any external reference.
- 6
As read-only stakeholder, verify source snapshot, version history, characteristic results, actor separation, evidence/audit/outbox and zero inventory/baseline-release side effects.
Expected result
- Lifecycle follows DRAFT → CONFIGURATION_REVIEW → READY_FOR_INSPECTION → REPORT_REVIEW → ACCEPTANCE_PENDING → ACCEPTED or REJECTED
- Product author, Configuration approver, Inspector, Quality reviewer and QA acceptor are five different user IDs
- Rejected plans and reports remain immutable while current version numbers advance
- Every approved characteristic has exactly one result and every failure has a valid matching NCR
- Every plan, configuration decision, report, Quality review and QA acceptance links exact CLEAN evidence
- A failed report and an acceptance missing a required external reference are blocked
- Supplier Quality and Auditor mutation attempts are rejected
- Every transition is attributable in audit and durable outbox history
- FAI routes never change current_stock, stock_ledger, product baseline state or customer delivery state