30. Reusable inspection/test plans and assurance analytics
Reuse one independently approved exact-item characteristic plan and create deterministic period assurance evidence without duplicating or mutating inspection, FAI or NCR authority.
Purpose
Reuse one independently approved exact-item characteristic plan and create deterministic period assurance evidence without duplicating or mutating inspection, FAI or NCR authority.
Quality Engineer, two different QA Head users, Quality Audit Manager, Quality Inspector, Product Engineer, Quality Management Representative and Auditor read-only
QAP-… rejected v1 → approved v2 with C-01/C-02 → QAA-… exact inspection/FAI/NCR sources → 99.000 ASSURED → separate QA approval.
Before you begin
- The site and one item revision already exist; the item is APPROVED and ACTIVE
- An optional supplier is ACTIVE and AVL APPROVED
- At least one same-site ACTIVE, CLEAN evidence version exists
- Plan author, plan QA approver, Quality Audit Manager and analytics QA reviewer are four different named users
- At least one matching disposed receipt inspection, final FAI decision or item NCR exists in the analysis period
Reusable immutable planning and deterministic analytics
Every version snapshots the site, current approved item revision and optional approved supplier. QA approval recalculates the SHA-256 subject fingerprint; changed revision/approval facts require a fresh immutable version.
Choose all-units, fixed sample, AQL or risk-based sampling. Fixed sampling requires an exact sample size; AQL requires its approved level. The acceptance rule remains explicit rather than hidden in UI defaults.
Each version retains unique numbered dimensional, material, functional, visual, software, documentation, environmental or other characteristics with criticality, source requirement, acceptance criteria, method, recording type, unit and evidence requirement.
Rejected plan versions remain immutable. A later approved version becomes active and a replaced approved version is marked superseded; analyses remain bound to their exact approved version.
QUALITY_ASSURANCE_V1 selects every matching disposed receipt inspection, final FAI decision and item NCR for the approved plan scope and period. The UI offers no manual source selection or substitution.
A different QA Head recalculates the complete source population. Approval is blocked when any authoritative outcome or source membership changed after analysis creation.
Flow 24 creates zero notification deliveries and never changes items, suppliers, receipts, inspection disposition, FAI, NCR, current_stock or stock_ledger records.
Procedure
- 1
Create and submit plan v1 as Quality Engineer; reject it as the first QA Head.
- 2
Create immutable v2 and approve the unchanged site/item/supplier subject as a different QA Head.
- 3
Generate the exact-source period analysis as a different Quality Audit Manager and inspect its metrics/source register.
- 4
Approve or reject the unchanged fingerprint as a second QA Head who is different from author, plan approver and analyst.
- 5
Reconcile immutable versions, characteristics, sources, decisions, evidence and zero source/custody/message side effects as Auditor.
Expected result
- Plan lifecycle supports DRAFT → PLAN_REVIEW → ACTIVE with immutable rejected and superseded versions
- The four different named users separate plan authorship, plan approval, analysis preparation and analytics review
- Plan version author and QA approver are different user IDs
- Analytics author differs from plan author and approver
- Analytics QA reviewer differs from plan author, plan approver and analyst
- The approved active plan retains exact item revision and optional supplier snapshots
- Every characteristic is unique and complete
- No manual analytics source selection or substitution exists
- Stale subject and analysis fingerprints are rejected
- Flow 24 creates zero notification deliveries and never changes item, supplier, inspection, FAI, NCR, inventory or ledger records
- Auditor mutation attempts are rejected