Flow 30 — Exact operation evidence to reviewed build variance
Freeze every cost-evidenced operation attempt into deterministic build-level planned-versus-actual WIP/minute/cost lines, retain rejected explanations and independently approve an unchanged source fingerprint.
Overview
Flow 30 is an operational evidence rollup only. Summed WIP is clearly labelled attempt evidence—not stock on hand—and cost totals never create payroll, budget, invoice, ledger, payment or inventory-valuation records.
Production Planner rollup author → different Production Manager variance reviewer → Project / Contract Manager and Auditor read-only
Process
- 1Complete evidence
Require every released operation to have a passing attempt and every attempt to have Flow 29 cost evidence.
Exact source only - 2Derive lines
Compare plan minutes/rate baseline with all actual attempts and sum explicit operation-evidence WIP.
No stock projection - 3Classify
Derive favourable, within-tolerance or unfavourable variance against the declared threshold.
No financial posting - 4Explain/version
Planner retains attributable explanation and controlled evidence; rejected versions stay immutable.
Versioned evidence - 5ReviewREAD ONLY
Different Production Manager recalculates the exact fingerprint before approval or rejection.
Approved evidence only
Role handoff
Production Planner rollup author → different Production Manager variance reviewer → Project / Contract Manager and Auditor read-only
Detailed reference chapters
Detailed steps
- 1
Complete every Flow 27 routing operation through exact Flow 28/29 dispatch, load, WIP/labour and cost evidence. The build must have reached AS_BUILT_CAPTURE or later.
- 2
As Production Planner, open Manufacturing → WIP & cost variance, select the exact build, choose the percent tolerance and enter an attributable explanation. Unfavourable build or operation variance requires detailed context and controlled evidence.
- 3
Confirm planned cost uses released estimated minutes and the earliest exact attempt rate baseline per operation, while actual minutes/WIP/cost include every retained failed and passing attempt. All rates must use one currency.
- 4
Submit v1. As a different Production Manager, reject it and confirm its source, lines and explanation remain immutable. Create replacement v2 for the same build, submit and independently approve only after server-side fingerprint recalculation.
- 5
As Project / Contract Manager or Auditor, reconcile every operation execution/dispatch/cost fingerprint and confirm build totals equal the line sum without creating financial or inventory records.
Field-by-field practice data
Freeze one cost-evidence rollup for a completed training build and explain its variance. The page shows sample set A; the workbook includes independent A, B and C values.
Field names match the current application labels. Select existing approved records where shown, leave optional values blank unless they genuinely apply, and never copy fictitious TRAIN values into live work.
Create the rollup
Select the exact completed-operation build and derive the rollup from pinned plan/rate/execution evidence.
| Exact field name | Requirement | Sample value A | How to use it |
|---|---|---|---|
| Exact completed-operation build | Select existing | TRAIN-A-WO-ASM-001 | Select a build whose operations are complete. |
| Variance threshold % | Required | 10 | Use the approved review threshold. |
| Attributable explanation | Required | Actual labour exceeded plan because operation 20 required one controlled rework attempt. | Explain material variances using authoritative evidence. |
| Controlled rollup evidence | Select existing | TRAIN-A-COST-EVID-001 | Select CLEAN controlled evidence. |
Expected result: A different Production Manager reviews the evidence; no accounting or inventory posting is created.
End state
One approved immutable build rollup retains exact planned/actual operation evidence, deterministic variance classification and separate review while stock, custody, payroll, budget, accounting and valuation remain unchanged.