Work-Centre Capacity

Three independent permissions control this area: View work-centre schedules, Assign and schedule production capacity, and Manage work centres and calendars. Policy changes still require Manufacturing settings permission, not general business settings access.

1. Open Work-centre capacity, then Work centres. Save a centre's simultaneous units and checked weekly working intervals. Times use the business's saved timezone. An unchecked day has no working hours. Multiple intervals allow breaks; split overnight shifts at midnight, using 24:00 for an interval ending at midnight. Record maintenance as downtime and release it explicitly when no longer applicable.
2. On a new recipe version, mark only operations that require capacity scheduling, assign their centre and simultaneous units, and save normally. Recipe approval remains independent. Preset templates do not enable capacity, approve recipes or set operation durations.
3. For an older retained order, open Capacity schedule and record a retained-version assignment with a reason. This makes that specific stable step required without altering the old recipe definition or switching the order's version. Assignments can be corrected before production starts; earlier assignment records remain visible.
4. Enter each operation's local start/end, then Preview schedule. Day, Week and List views use real links; every scheduling action is also available through standard keyboard-operable forms. There is no drag-only flow or automatic optimizer.
5. In Block mode, resolve missing assignments, unscheduled required operations, inactive centres, nonworking times, downtime and over-capacity conflicts before reserving or starting. Unmarked legacy operations remain compatible. In Warn mode, explicitly acknowledge the listed warnings and enter a reason. The acknowledgement is bound to the current schedule, assignments, timezone and overlapping capacity facts; changed facts require another preview and acknowledgement. Off mode does not gate production starts, although previews still show scheduling issues.
6. Reserve schedule to record a new operation reference. Exact retries return the same result; a reused reference with different data is refused. Rescheduling retains released reservations and creates new records. On already started orders, only future operations can be replaced; past and active slots stay unchanged. Finished and cancelled schedules are read only.

New starts recheck the current policy after recipe-governance checks. Already started production is not retroactively blocked. Scheduled timestamps are reservations, not a requirement that the Start production button be pressed at that exact wall-clock time. Cancellation releases future slots and retains past/active slots and all history. It uses the existing production cancellation rules for stock/cost effects; capacity scheduling itself adds none.

Reservations are stored in UTC and displayed in the business timezone. A missing or repeated local timestamp at a daylight-saving transition is refused instead of silently choosing an offset. Choose an unambiguous timestamp. End must be after start and no more than 31 days later. Adjacent slots may share a boundary without overlapping.