35. Resource calendars, finite dispatch loading and operation cost evidence
Prevent Flow 28 dispatch overbooking and give every Flow 27 execution an immutable actual-minute cost snapshot without acquiring maintenance, machine, payroll, accounting, valuation, stock or custody authority.
Purpose
Prevent Flow 28 dispatch overbooking and give every Flow 27 execution an immutable actual-minute cost snapshot without acquiring maintenance, machine, payroll, accounting, valuation, stock or custody authority.
Manufacturing Engineer, different Production Manager, Production Planner, different Production Supervisor, exact named Production Operator and read-only Auditor
CELL-01 calendar v1 capacity 3 + TOOL-01 calendar v1 capacity 1 + INR-STD rate v1 → MDP-… two planned loads → supervisor RESERVED → operator CONSUMED → INR labour/work-centre/tooling/total evidence.
Before you begin
- Flow 28 exact resource versions are active and approved
- One same-site CLEAN controlled evidence version exists
- Calendar and rate author differs from Production Manager approver
- Planner and supervisor remain separate
- Dispatch window fits wholly within one local approved interval
Finite-load and financial-authority boundaries
Freezes exact resource, IANA timezone, validity, weekly local intervals, closed/overtime exceptions and capacity. Overnight work is split into separately governed local-day intervals.
An exact TOOL or EQUIPMENT calendar is always capacity one. A WORK_CENTER may define bounded parallel units. The calendar never starts, stops or maintains the physical resource.
Supervisor approval locks exact resource-version rows, rechecks the approved window and counts every overlapping RESERVED load before atomically reserving all dispatch resources.
Rejection or cancellation marks planned/reserved loads CANCELLED. Execution requires all exact loads RESERVED and marks them CONSUMED in the same transaction as operation evidence.
Freezes site, currency, validity and labour/work-centre/tooling per-minute rates. Dispatch must cite one exact ACTIVE APPROVED effective version.
Actual minutes derive the three components and total, with balanced WIP, rate snapshot and SHA-256 fingerprint. One execution has exactly one immutable record.
The evidence does not create timecards, payroll, invoices, payments, journal entries, inventory valuation, stock movements or Assembly custody transactions.
Procedure
- 1
Create, submit and independently approve exact-resource calendar versions and one site/currency evidence-rate version.
- 2
In Production readiness, plan each dispatch with exact resource, calendar, competency, operator and cost-rate versions.
- 3
Release as a separate supervisor and prove an overlapping capacity-one tool is rejected atomically.
- 4
Reject/cancel a dispatch and confirm all of its loads are CANCELLED before a fresh non-overlapping replacement is planned.
- 5
Execute as the exact named operator and reconcile CONSUMED loads plus one actual-minute immutable cost record.
- 6
As Auditor, verify rate/calendar history and unchanged maintenance, machine, payroll, accounting, valuation, stock, ledger, custody and identity sources.
Expected result
- Calendar/rate lifecycles retain rejected immutable versions and controlled replacements
- Exact tool/equipment capacity cannot exceed one
- Dispatch outside validity/local intervals or within CLOSED exceptions is rejected
- Concurrent supervisor releases cannot exceed finite overlapping capacity
- Rejected/cancelled dispatches release load and completed dispatches consume it
- Each execution has one cost record with total = labour + work centre + tooling
- Rate retirement fails future planning/execution closed
- No maintenance, machine, financial, inventory valuation, stock, ledger, custody or identity source is mutated