Operations

Schedule — plan of record

ScheduleRevision / ScheduleInterval. One board, configured per operation.

Preassembly & staging — Staging is sequenced against what the next operation needs, so the run window is the subject and changeover is not a concept here. This is where fork-truck observations arrive.

Window

FiltersApplied server-side; the query narrows, not the render

Intervals shown

Assets

Planned hours

0.0

Unscheduled (excluded)

0.0

Intervals6 columns, declared for Preassembly & staging

⏳

Reading the plan

Querying ScheduleInterval

Deviations — not yet availableS2 · authorised by Amendment H-1, not yet built

Cycle-time updates and fork-truck observations are deviations against the plan in force, not edits to it. A published plan that silently becomes whatever happened makes attainment-against-plan meaningless — the same failure as a standard refreshed to the last actual. No deviation grain exists yet, so this board is read-only by construction and there is no control here to suggest otherwise.

Preassembly & staging gains under H-1: material readiness · fork-truck deviation · staged-for run

This is the published plan. Production Schedule is a finite-scheduling simulation over synthetic batch history and reads no database. The work queue is the same plan at real-time grain (D4). Two subjects one word apart — flagged under R1, not resolved here.