45. Job, contract and programme operational cost insight
Read explainable actual-versus-baseline operation evidence by exact job and released product baseline, with deterministic customer/contract context, without acquiring cost-allocation, financial-posting or source-edit authority.
Purpose
Read explainable actual-versus-baseline operation evidence by exact job and released product baseline, with deterministic customer/contract context, without acquiring cost-allocation, financial-posting or source-edit authority.
Project / Contract Manager, Accountable Executive, Production Manager, Production Planner and read-only Auditor
AWO-… / MBL-… → MCV-… approved v1 → INR 1000 baseline / 1125 actual → unique DEM-… customer/project/contract context, or an explicit AMBIGUOUS / NO MATCH result.
Before you begin
- The Manufacturing plan pins one exact RELEASED product baseline
- The build has immutable Flow 29 cost evidence for every attempt
- A different Production Manager has approved the current Flow 30 rollup version
- The reader has programme_cost:read plus assigned-site and classification clearance
- For customer/contract context, a visible Flow 40 demand line uses the same site, project reference and exact product baseline
Evidence lineage, deterministic context and financial boundaries
The surface reads only the current APPROVED Flow 30 rollup version. Draft, submitted and rejected versions cannot be presented as programme insight.
Build number, Assembly work-order number, external reference, project reference, manufacturing-plan version and released product-baseline UUID/version remain separately visible.
Customer and contract appear as a unique association only when exactly one visible, non-cancelled demand line matches assigned site + case-insensitive project reference + exact product-baseline UUID.
More than one matching demand line remains AMBIGUOUS. Candidate references are visible for human reconciliation, but Moduvio does not divide, duplicate or allocate the build cost.
The Manufacturing cost evidence remains valid without a demand match. No customer/contract is guessed from mutable names, similar part numbers or a different revision/baseline.
Planned cost is the immutable Flow 30 baseline derived from planned minutes and the exact operation rate evidence; actual cost sums all retained execution attempts. Currency summaries never combine unlike currencies.
Every displayed rollup UUID/version and SHA-256 source fingerprint drills to ordered operation rows and their execution, dispatch, exact rate-version and cost fingerprints.
programme_cost:read is granted to bounded Programme/Production/audit roles. A user without it is denied; assigned-site and clearance filters apply before any demand context is resolved.
The view cannot allocate cost, write Item Master values, post payroll, budget, GL, AP/AR, tax, payment or inventory valuation, or change demand, Manufacturing evidence, current stock, stock ledger, custody or identities.
Procedure
- 1
Open the independently approved build rollup in Manufacturing and record its version, build, plan, baseline and source fingerprint.
- 2
Open Programme → Job & contract cost insight and apply exact filters. Confirm a user without programme_cost:read is denied rather than shown partial financial context.
- 3
Read the job/build/product baseline and actual-versus-baseline summary. Never combine different currencies or interpret operation-evidence WIP as stock on hand.
- 4
Inspect the demand association: use customer/contract only for EXACT UNIQUE MATCH; review but do not allocate AMBIGUOUS candidates; accept NO MATCH as an honest boundary.
- 5
Expand every operation and reconcile its attempts, minutes, cost, execution/dispatch/rate-version IDs and fingerprints to Flow 29/30 source evidence.
- 6
As Auditor, prove hidden-site and above-clearance records are absent and compare zero-side-effect witnesses. A classified-read audit fact is expected; source/outbox/stock/ledger/custody/demand/finance counts must otherwise remain unchanged.
Expected result
- Only current approved rollup versions appear
- Every row identifies the exact job, build, released plan and product baseline
- Customer/contract context is unique only under the declared deterministic rule
- Ambiguous demand never duplicates or allocates build cost
- No match never invents a customer or contract
- Operation lineage retains immutable attempt/execution/dispatch/rate-version fingerprints
- Currency totals remain separate
- Permission, tenant, site, clearance and classification filters apply before association
- Classified reads are audited without outbox or domain mutation
- Manufacturing sources, demand, item identity, current stock, stock ledger, custody, valuation, payroll, budget and accounting remain unchanged