How to Reschedule Production After a Machine Breakdown

Home » Resources » How to Reschedule Production After a Machine Breakdown

Estimated reading time: 8 minutes

To reschedule production after a machine breakdown, record when the machine is unavailable, confirm the state of the affected work, and recalculate the remaining schedule against the capacity you can actually use. Then check the downstream operations before giving the floor its next work sequence.

The task is bigger than moving the broken machine’s queue to tomorrow. Other machines may be waiting for its output, while a possible replacement is already busy with another customer’s order. You need a sequence that works across those connections.

SkyPlanner APS handles that connected scheduling calculation. You record the unavailable period and set the priorities; its scheduling AI, Arcturus, recalculates schedulable work, and the Gantt shows the result. That saves you from rebuilding interdependent queues by hand while maintenance works on the fault.

Recover the route, not just the machine queue

Imagine a sheet-metal manufacturer whose main press brake stops during a batch of enclosure panels. Some panels are already bent, the current bending job is interrupted, and more batches are waiting. Welding needs a complete set of panels before it can assemble each enclosure.

There is another press brake, but it cannot handle every panel size and already has work assigned. Simply moving everything there could displace an order that was not affected by the breakdown at all. Simply pushing bending later could leave welding expecting parts that will not arrive.

The useful recovery decision is therefore not “where can I put this bar?” It is “what should each affected resource do next, given what has really changed?” Work through the following decisions in that order.

1. Put the unavailable period into the capacity plan

Ask maintenance for the current expected return-to-service time, not just the estimated time to replace a component. The machine needs to be ready for production, including any required checks, before you count its capacity again.

If the estimate is uncertain, use an explicit planning assumption and agree when it will be reviewed. Leaving the old capacity available makes the plan look achievable while the machine is still down. Treating the resource as unavailable indefinitely can hide useful work after its expected return.

In SkyPlanner, represent the interruption with a workstation exception on the affected resource. Give it a description and the unavailable time range, then save it. The capacity display on the Gantt marks that period as unavailable. The important change is not the color: Arcturus now has a capacity restriction to schedule around.

For the press-brake example, block the main brake’s unavailable period rather than changing the whole department’s normal shifts. The second brake and welding retain their own capacity. You are describing the actual loss, not spreading it to resources that can still work.

When maintenance revises the return time, update that assumption and recalculate again. You do not need a perfect repair forecast to make a useful recovery plan; you need a visible, current one.

2. Separate interrupted work from work that has not started

Before rescheduling, reconcile the affected jobs with the floor. Confirm what is complete, what has started and stopped, and what is still waiting. Check the remaining quantity and work rather than assuming that everything originally planned is still ahead of you.

In the example, cutting the panels again would add work that has already been done. Treating all panels as ready for welding would make the opposite mistake. The planner needs the actual state of the batch, including any pieces awaiting a quality decision.

There is also an important SkyPlanner distinction: a job that has started and been paused remains in progress and locked in its Gantt position. Arcturus does not move it simply because you run a recalculation. Not-yet-started jobs can be rescheduled unless another rule protects them.

That means you should settle the interrupted bending job’s restart separately from the waiting batches. If it will resume on the repaired press, agree that restart with the supervisor. If the remaining work must move elsewhere, resolve how that work will be represented before relying on the new schedule. Do not assume that pressing Pause releases it for automatic reassignment.

This check keeps the recovery plan grounded in production, rather than turning a stopped operation into an apparently free scheduling choice.

3. Make the alternatives and priorities real

An idle machine is not necessarily a usable replacement. Confirm which operations it can perform, the tooling and setup required, and whether the right operator is available. If the alternative runs more slowly, the plan must reflect that too.

SkyPlanner’s process steps define eligible workstations, durations and dependencies. Workstations and shifts define the available capacity. Keeping those inputs accurate lets Arcturus calculate an alternative sequence instead of asking you to manually fit each waiting operation into a gap.

For the enclosure batches, the smaller press brake may be suitable for some panels but not the largest ones. Represent that eligibility accurately. Do not make every operation eligible just to clear the broken machine’s queue on screen.

Then decide which commitments take precedence. Marking every affected order urgent does not restore lost capacity or tell the scheduler which customer matters most. Keep your normal priorities where they still make sense, and change the exceptions deliberately. SkyPlanner lets you steer Arcturus through priorities and rules rather than surrendering those decisions to the AI.

If moving a waiting batch to the second brake delays its existing work, that consequence belongs in the decision. The point is to recover the best usable sequence, not to make one troubled queue look empty.

4. Recalculate, then follow the work downstream

With the exception saved and the relevant inputs current, press SkyPlanner’s King Button to update the schedule. Arcturus recalculates schedulable work around the unavailable capacity, using the configured resources, dependencies, priorities and rules. The Gantt shows the resulting assignments and sequence.

This is where connected scheduling earns its place. You are no longer moving bending jobs and then separately repairing every welding and assembly queue affected by those moves.

Review the result along the affected route:

• On the failed resource: does the waiting work now fit around the recorded unavailable period? Is the interrupted job’s restart still an explicit decision?
• On alternative resources: what work has moved there, and which existing jobs now run later?
• At the next operations: will the required parts be ready when welding or assembly is scheduled to use them?
• At completion: which committed orders still fit their dates, and which need action?

In the example, getting one panel batch through the second press earlier only helps welding if the other required panels are ready too. Likewise, an attractive bending finish is not enough if welding’s next usable slot has already gone.

If an important order still runs late, choose a real change: a suitable alternative resource, approved extra capacity, a justified priority change or a revised commitment. Record that change and recalculate. Moving a due date or dragging an operation into occupied time does not, by itself, give production the capacity to do it.

5. Give the floor one current sequence

Before handing over the recovery plan, confirm that the supervisor can answer three practical questions: what starts next, where does it run, and what is waiting for the repaired machine or another decision?

Make sure the revised sequence reaches the people doing the work. A corrected planning screen is not enough if operators continue from an earlier queue. Also tell the customer-facing team which existing commitments are now at risk, so they can act on the same plan.

UTU, a Finnish manufacturer of electrical switchboards and switchgear, illustrates why this handoff matters. Before SkyPlanner, changes in its ERP production sequence did not always reach the shop floor through its manually updated departmental spreadsheets. With SkyPlanner connecting its lines and departments, UTU reports that an updated work queue reaches installers on the line in seconds. The benefit is a changed sequence people can use, not another document the planner has to keep aligned.

Keep the recovery plan current as the repair progresses. If the machine returns earlier or later than assumed, update its availability and the job state, recalculate and communicate the changed sequence. That is far less work when the connections are already in the scheduling system.

Make the next breakdown easier to manage

The reason to choose SkyPlanner is not that a breakdown stops being disruptive. It is that lost capacity becomes an input to a connected schedule, rather than the start of another round of manual queue reconstruction. You keep control of priorities and production decisions; Arcturus handles the scheduling calculation, and the Gantt makes its consequences visible.

SkyPlanner integrates with any ERP or MES through its open REST API, so you can connect your existing order and production data to that scheduling process.

Book a SkyPlanner demo around a recent interruption. Bring the affected route, the machine’s unavailable period and an example of work already in progress. See how the capacity exception changes the waiting queues, which downstream operations move, and how your team would handle the interrupted job. That is a useful test of whether the system will save you work when the next machine stops.

If you prefer to explore first, try SkyPlanner with demo data and see how a capacity change reshapes the schedule.