Editorial draft available to read. Factual and language review is pending. Examples are illustrative.
Decision and scope
Version calendars by site, production line and effective date. Record exceptions without rewriting historical shifts. Each change should identify affected orders, the approving owner and the people who need to know. Separate a proposed calendar adjustment from an approved schedule that other planning calculations may use.
Illustrative example
Illustrative example: a Friday changes from two shifts to one because of planned maintenance. The planner sees which orders lose available capacity and reviews a rescheduling proposal with production. Completed shift records retain the calendar that applied when the work occurred, while future calculations use the newly approved version.
Acceptance check
Test overnight shifts, time zones and days with a different clock duration. Check that notifications refer to the approved version. Accept the change when planning and actual records use identifiable calendars and unresolved capacity impacts remain visible.
Key takeaways
- Accept the change when planning and actual records use identifiable calendars and unresolved capacity impacts remain visible.