[{"data":1,"prerenderedAt":4},["ShallowReactive",2],{"article-body-the-schedule-is-obsolete-by-the-morning-meeting":3},"\nThe overnight scheduling run delivers an optimised sequence, and by\nthe 8am meeting reality has already amended it. A truck is late, a\nmachine failed its start-up checks, two operators called in absent.\nThe supervisors repair the plan by hand, and the optimised sequence\nspends the rest of its day as a reference document.\n\nThis is not a failure of effort, and smarter software does not fix\nit. A schedule is a forecast about a physical system, and physical\nsystems disagree with forecasts hourly. The question was never how\nto compute a perfect schedule but how to live with the fact that\nnone survives the shift.\n\n## The rescheduling trap\n\nThe instinctive answer is to reschedule at every disruption, from\nscratch. Planners call the result nervousness, and it is worse than\nthe ailment. A from-scratch rebuild may reshuffle everything to\nharvest minutes, and the costs of that churn are mostly invisible\nto the software. Materials get staged for\na sequence that no longer exists. Changeovers begin for jobs that\njust moved. Teams learn, correctly, that the plan is not worth\nreading.\n\nA plan that changes completely twice a day is not twice as\nresponsive. It is a plan nobody follows, which returns the plant to\nmanual scheduling with extra steps.\n\n## Triage, not recomputation\n\nA mature operation triages disruptions and saves recomputation for\nthe events that earn it.\n\n1. **Absorb silently where buffers exist.** Most disruptions\n   threaten nothing. The late truck arrives inside the slack, and\n   the short stoppage fits the buffer. The correct response is no\n   response.\n2. **Repair minimally where commitments are threatened.** When an\n   event does endanger a due date, the objective becomes the\n   smallest stable change that protects the commitment. Swap two\n   jobs, shift a batch, hold the rest intact.\n3. **Rebuild rarely, and knowingly.** Some events genuinely\n   invalidate the plan (e.g. a line down for days, or a material out\n   for a week). Then a full rebuild is right, taken as a visible\n   decision, cost acknowledged.\n\nTwo disciplines keep the triage honest. The warnings carry odds,\nworked out from how deliveries and processing times have actually\nvaried, not yes-or-no flags. And the triage is checked afterwards.\nWhich ignored events should have triggered repairs, and which\nrepairs proved unnecessary, so the thresholds learn from the plant.\n\n## What the morning meeting becomes\n\nRun this way, the morning meeting reviews a handful of genuine\ndecisions, each with options and odds attached. The schedule keeps\nthe one property that makes any plan valuable. The people executing\nit believe it will still be true after lunch.\n\nFor a week, count how many of the overnight\nschedule's first ten jobs actually ran in sequence. That number is\nyour plan's real credibility, and raising it is what\n[the Prophesee Supply Chain Suite](/solutions/supply-chain/manufacturing)\nis for. [See what your schedule churn is costing](/contact).\n",1786984937789]