Short-notice changes and re-planning

Machine breakdown, rush order, missing material: how the same planning logic produces a new, robust plan within a short time.

Written by Matthäus Niedermeier · · updated · 2 min read

The short answer: When a machine breaks down, a rush order arrives or material is missing, the engine re-creates the plan using the same planning logic – not just for the affected machine, but across the whole planning horizon. A new, robust plan is ready in less than 30 minutes. Re-planning can be triggered on demand or run on a fixed cycle.

Disruption is the norm

No plan survives the day unchanged. Typical triggers include:

  • machine breakdowns and unplanned maintenance,
  • sickness or short-notice staff absence,
  • rush orders and changed delivery dates,
  • missing or late material,
  • data corrections and new call-offs.

In conventional planning, each of these changes means coordination, phone calls and manual reshuffling – often under time pressure. Experts call this planning nervousness: constant changes that unsettle the whole process.

Why reshuffling is not enough

If only the affected order is moved to another machine after a breakdown, knock-on problems follow: the alternative machine was intended for other orders, set-up sequences no longer fit, and staff with the right qualification are not available. A change in one place ripples across several production stages.

DeepSynergy.AI Production Planning therefore re-creates the plan for the whole horizon – with the same rules, objectives and weightings as the original plan. The result is not an emergency plan but another optimised plan.

An example: a machine goes down

Suppose a machine fails one morning. The engine receives the new availability and re-plans:

  1. Record the disruption: the machine is marked as unavailable for the affected period.
  2. Re-plan: orders are reassigned to suitable machines – taking capabilities, set-up sequences, material and qualifications into account.
  3. Assess the result: the KPIs show which delivery dates hold and where things get tight. The planner decides whether to adopt the new plan.

An animation on the product page shows this process.

Building in robustness from the start

Re-planning is the reactive side. The proactive side is a plan that copes better with disruption – for example through targeted buffers before critical steps. At ams OSRAM, the last relevant process step must be completed at least 48 hours before the delivery date. How much weight robustness carries relative to efficiency is part of the jointly agreed objective system (see Planning problems and trade-offs).

On demand or on a cycle

In day-to-day operation there are two kinds of re-planning, which can be combined:

  • On demand: the planner triggers re-planning as soon as something changes.
  • Cyclical: the plan is re-created at fixed intervals, such as every shift or every day.

What changes in practice

At ams OSRAM, new call-offs, data corrections or missing pre-material no longer cause immediate disruption. In laser cutting at a metal-processing company, new or changed orders do not trigger manual re-planning but a consistent update of the plan. Fewer short-notice interventions free up time for forward-looking planning.

How much potential is there in your planning?

In the free potential check (45 minutes), we talk about your current planning and assess together whether and where DeepSynergy.AI Production Planning can help.

Free potential check(opens booking calendar in a new tab)