The overnight scheduling run delivers an optimised sequence, and by the 8am meeting reality has already amended it. A truck is late, a machine failed its start-up checks, two operators called in absent. The supervisors repair the plan by hand, and the optimised sequence spends the rest of its day as a reference document.
This is not a failure of effort, and smarter software does not fix it. A schedule is a forecast about a physical system, and physical systems disagree with forecasts hourly. The question was never how to compute a perfect schedule but how to live with the fact that none survives the shift.
The rescheduling trap
The instinctive answer is to reschedule at every disruption, from scratch. Planners call the result nervousness, and it is worse than the ailment. A from-scratch rebuild may reshuffle everything to harvest minutes, and the costs of that churn are mostly invisible to the software. Materials get staged for a sequence that no longer exists. Changeovers begin for jobs that just moved. Teams learn, correctly, that the plan is not worth reading.
A plan that changes completely twice a day is not twice as responsive. It is a plan nobody follows, which returns the plant to manual scheduling with extra steps.
Triage, not recomputation
A mature operation triages disruptions and saves recomputation for the events that earn it.
- Absorb silently where buffers exist. Most disruptions threaten nothing. The late truck arrives inside the slack, and the short stoppage fits the buffer. The correct response is no response.
- Repair minimally where commitments are threatened. When an event does endanger a due date, the objective becomes the smallest stable change that protects the commitment. Swap two jobs, shift a batch, hold the rest intact.
- Rebuild rarely, and knowingly. Some events genuinely invalidate the plan (e.g. a line down for days, or a material out for a week). Then a full rebuild is right, taken as a visible decision, cost acknowledged.
Two disciplines keep the triage honest. The warnings carry odds, worked out from how deliveries and processing times have actually varied, not yes-or-no flags. And the triage is checked afterwards. Which ignored events should have triggered repairs, and which repairs proved unnecessary, so the thresholds learn from the plant.
What the morning meeting becomes
Run this way, the morning meeting reviews a handful of genuine decisions, each with options and odds attached. The schedule keeps the one property that makes any plan valuable. The people executing it believe it will still be true after lunch.
For a week, count how many of the overnight schedule's first ten jobs actually ran in sequence. That number is your plan's real credibility, and raising it is what the Prophesee Supply Chain Suite is for. See what your schedule churn is costing.