Production planning starts before the first slot is placed on a schedule. A feasible production schedule must connect confirmed orders and due dates with operations, available resources, materials and work already committed. If any of those inputs is missing or out of date, the plan may look orderly but the shop floor will not be able to follow it.
A production schedule answers practical operating questions: which order should start first, at which work centre, in which sequence, with which material and in which realistic time window. That is why a schedule cannot be created simply by sorting orders by delivery date.
The customer due date is an important input, but it is not the only one. An order with the closest due date may be waiting for material, require tooling that is occupied, or need to pass through a bottleneck with no remaining capacity. An order with a later due date may make sense to start earlier if it uses an available resource, prevents idle time or prepares the next critical operation.
Capacity management should therefore be considered alongside material planning and the sequence of operations. Separate views often create a false sense of control: sales sees a due date, purchasing sees ordered material, production sees a queue at a machine, and no one sees the whole picture.
Before creating a production schedule, it is useful to check how the following data sets connect.
Each order needs a clear product, quantity, requested date, confirmed date and order status. Firm customer commitments should be distinguished from forecasts, blanket orders and internal capacity reservations.
A change in quantity or due date needs to reach the planner quickly. Otherwise, the schedule may continue to protect a priority that no longer exists while a new urgent request remains outside the plan.
It is also useful to record the consequence of delay, without turning every order into an emergency. Different customer types, contractual commitments, service parts and work orders for a key delivery may have different business priorities. The priority rule needs to be visible and applicable, not left to individual interpretation on the shop floor.
An order is more than a product quantity. Realistic production planning requires a routing: which operations follow, in what sequence, at which work centres and how much time they require.
An operation should include at least planned setup time, processing time, any waiting or cooling time, and the required resource. If a batch can be split, that rule should be clear as well. If it cannot move before quality control, the schedule needs to respect that condition.
Alternative resources deserve particular attention. The option to perform an operation on several machines or with several teams can reduce disruption risk, but only where they are genuinely comparable in capability, tooling, quality and operator availability. Formal substitutability without an operational check often only moves the problem to a later stage.
Capacity management requires more than a machine's nominal hours. Available capacity depends on shifts, maintenance, non-working days, absences, operator qualifications, tooling constraints and the actual condition of the work centre.
An eight-hour plan does not mean eight hours of production time. Setup, tool changes, cleaning, inspection, internal transport or an approved stoppage may use part of the day. An organisation does not need to model every minute from day one, but it should deliberately choose its level of detail. A model that is too coarse hides overload. A model that is too detailed creates an administrative burden that is not maintained.
As a starting point, it is often useful to track bottlenecks separately. Their hours, availability and order sequence have more influence on due dates than resources with average loading.
An order is not ready merely because production capacity exists. Materials and components need to be available in the right quantity, at the right location and in a status suitable for use.
The planner should distinguish material in stock, reserved material, material in transit, material under inspection and material with a known delay risk. Material also needs to be linked to its point of consumption in the process. Some components need to be available at the start of an order, while others enter only in the final operation.
Starting an order early without a key component may make sense only where there is a controlled intermediate step and the partly completed product will not block space, cash or capacity. Otherwise, work in progress accumulates and makes priorities harder to see.
A new schedule needs to start from reality, not from an empty calendar. This includes orders in progress, orders already released, planned tool changes, reserved resources and backlogs from previous days.
Statuses need a clear operational meaning. The difference between "planned", "released", "in progress", "completed" and "blocked" must be understood by everyone who enters or uses data. If an operation is recorded as completed in the system while it is physically still waiting for the next step, the schedule receives an inaccurate picture of free capacity and available material.
Updates do not need to be perfect or immediate in every part of the process. The organisation needs an agreement on who updates each event, when they update it and at what level of accuracy. Without that rule, production planning rests on outdated assumptions.
The most important questions are often managerial rather than technical: what takes precedence when two orders require the same resource? Is the first criterion the customer due date, release date, order value, disruption risk, material availability or the needs of the bottleneck?
There is no universal rule for every type of manufacturing. What matters is defining a limited set of rules, setting their order of application and stating who can approve an exception. Without this, the planner and production manager resolve the same conflicts again every day.
A simple framework may look like this:
Imagine two orders for the same machine. Order A is due on Wednesday, but its key component arrives on Tuesday afternoon. Order B is due on Thursday, all of its material is available, and its first operation releases semi-finished goods for the next bottleneck.
A simple "earliest due date first" rule would put A at the front of the queue. A feasible schedule may prioritise B until A's component arrives, provided this sequence does not put Wednesday at risk. The planner needs to see setup duration, processing time, the machine's free window, material status and the next operations for both orders.
This example does not prescribe one solution. It shows why a production schedule needs to show constraints and decision consequences, not merely provide a list of dates.
A good plan is not one that predicts every disruption. Its value lies in a fast, consistent response when disruption occurs. Machine failures, employee absences, changes in customer priority and supplier delays will still happen.
It is therefore useful to distinguish longer-term capacity planning from the daily operational schedule. The longer-term view reveals where demand will exceed available hours. The daily schedule decides what to do in the next shift or day. Mixing these levels can produce an unstable plan in which everything keeps changing.
Change discipline is also necessary. Frequent reshuffling of orders may protect an individual urgent request, but it increases setups, makes material purchasing harder and reduces trust in the schedule. The organisation should define a time window within which the schedule changes only for a justified reason, and record urgent interventions separately.
Before introducing a new tool or more complex automation, it is useful to follow the actual path of one order from receipt to delivery. Check where data on due dates, operations, materials and work status is created, who changes it and when a change becomes visible in the schedule.
Then select one bottleneck or one production line and check whether the schedule for the next week can clearly answer four questions: what is done first, what blocks an order, which capacity is missing, and who approves a priority change.
ORKA's approach to manufacturing processes includes connecting operational data with the decisions that make a schedule feasible. Find further context at ORKA for manufacturing . To review processes, data and rules before larger changes, consider ERP and process screening .