Production scheduling: dates that respect available capacity

How many minutes can you actually use?

Start with resource calendars, shifts and unavailable periods. An eight-hour shift is not always eight hours of manufacturing. Identify setup, cleaning, breaks, maintenance and prior reservations without deducting a period twice when already excluded from the calendar. Distinguish machine duration from operator attendance: one shared person may constrain two seemingly available machines.

Microsoft documents finite capacity that considers reservations and moves work when capacity is insufficient. It requires enabled plans and resources, a defined horizon and attention to model limitations. Finite capacity. Do not assume a configuration models every variable shift; demonstrate how it represents your calendars and which constraints it leaves out.

Example: two full orders cannot fit on Monday

Completing both needs sixty more minutes. In this exercise A goes first, B may split and its setup carries into Tuesday without extra time. A uses 270, leaving 120. Setting up B uses twenty and making fifty uses one hundred: Monday completes A and fifty B units. The remaining thirty need sixty minutes Tuesday. If restarting B requires another setup, Tuesday needs that time as well; recalculate the load and planned finish against Tuesday’s calendar. Do not hide that assumption inside a Gantt bar.

Does an available machine mean an order is ready?

Check eligible material, the preceding operation, tools and people qualified for the task. A promised purchase order is not received material. For sequential operations, define whether the entire lot must finish before the next starts or partial transfer is allowed. Avoid multiplying machines by hours if they all wait for the same mold or operator. The effective recipe and routing must explain quantities and duration.

SkyPlanner publishes APS scheduling using orders, capacity and materials alongside planner controls. Production scheduling. This is vendor-declared coverage; its case figures and speed are neither Nightly results nor evidence for your factory. An algorithm can propose a plan, but its input constraints and priorities still need review.

What happens when the resource breaks down?

Retain the published plan and create a new proposal using actual unavailability. Show affected orders, changed dates and reservations released or reassigned. If one person edits priority while another schedules, compare against the base revision and resolve the conflict before publication. Changing the planned date does not establish customer notification or acceptance of a new delivery; those decisions need their own evidence.

What should a capacity test demonstrate?

• Normal: CP01 shows 390 usable minutes and explains 270 for A plus 120 for Monday's part of B.
• Exception: unavailable material or tools hold work under the defined rule; work cannot consume production capacity as if already started.
• Change: a breakdown creates a revised proposal with visible affected orders and an owner for accepting new priority.
• Retry: repeated P01 publication keeps one published revision and one reservation per operation.
• Assumption: prohibiting a B split or requiring Tuesday setup changes the result; the system cannot preserve an impossible date to appear compliant.

What data should you bring to a diagnosis?

Complete the minutes and constraints worksheet for one bottleneck. The production guide covers progress; equipment maintenance explains unavailability and closure. To scope production control, bring two orders competing for the same resource and their setup assumptions. You need not invent timings to begin: unknown durations can remain items for measurement.