Production Planning vs Control: Follow a Delayed Job

Production planning sets the quantity, sequence, resources and intended timing of work. Production control compares execution with that plan, investigates deviations and coordinates the authorised response. The resulting evidence improves the next plan.

Planning and control continue to interact after release. A changed customer order needs a planning decision, while an operator’s progress update supplies the evidence for that decision. Keep the original plan and the revised commitment distinguishable.

Separate the planned decision from the observed event

A material requirement or schedule is not proof that execution occurred. Frappe's work-order documentation provides a primary reference for connecting planned operations with manufacturing records.

Follow one delayed job

Illustrative case: job B is planned to start at 09:00, and its material is ready then. The preceding job A occupies the machine until 10:00. Job B then needs a 15-minute changeover, giving a revised start of 10:15.

The start delay is 75 minutes. The evidence identifies a preceding-job and changeover constraint, not a material shortage. Do not calculate a revised completion date from the start alone; include the remaining setup, run quantity, inspection and downstream operations.

1. The supervisor records when job A finishes and what remains before job B can run.
2. The planner checks the remaining machine load, skilled worker and material readiness.
3. The authorised owner chooses a revised sequence or another feasible resource.
4. Sales receives the effect on the accepted-output and delivery commitment.
5. The revised decision retains its reason, owner and update time.

Use machine signals with job context

Machine runtime and downtime help establish when a resource was operating. They do not explain every reason a particular order was waiting. Add the job, setup, material, inspection and operator context before assigning a cause.

Optiwise industrial IoT connects machine signals with OEE, runtime, downtime and performance views. OptiEdge collects machine data, while the wider device range covers power, state and vibration monitoring. Supervisors can review these signals alongside the process entries used for production work.

Feed the evidence into the next plan

If the preceding job repeatedly takes longer than its estimate, review that product’s time basis. If the 15-minute changeover was omitted from the original sequence, include it explicitly next time. Retain individual causes so one late shift does not become an unsupported blanket assumption about the whole factory.

In Optiwise, Smart Suggest connects BOM demand with stock and existing supply. Routing, machine calendars, worker allocation and process entries connect planned work with execution. Our AI agents retrieve production records and perform permitted actions, helping the responsible user move from a question to the relevant workflow.

Use the capacity sanity check before release. Use this timeline after a deviation to record what changed and who owns the response.

Questions from manufacturing teams

Does planning stop when a work order is released?

No. New evidence can require an authorised change to quantity, sequence or timing. Preserve the released plan and the reason for the revision.

Can IoT explain every production delay?

No. Machine signals need job and operator context. A material hold or pending inspection may delay the order even when the machine is available.

Who should change the production sequence?

Use the authority defined by your operation. The supervisor provides current execution facts; the planner or designated owner reviews constraints and approves the revised sequence.

Follow a production delay in Optiwise from the machine and job records to the revised action.