What Is a Downtime Event in Production Scheduling?

A downtime event is a defined period when a single work center is unavailable, whether from planned maintenance, a changeover, or an unexpected breakdown. It removes capacity from that one machine for the window, so the engine will not place any job on it during that time. Unlike a holiday, which closes work by the calendar, downtime attaches a reason and a specific window to one resource.

One practical note up front, because the term implies a record you create: EDGEBIC's engine honors downtime, but the current release has no downtime screen. A machine's unavailable hours are entered as a per-day capacity override on that work center, shift, and date. The concept below is real and the capacity effect is real; the entry point is the override dialog.

How it works

Downtime splits naturally into two cases, and the difference is when you find out rather than which box you tick. Planned downtime is known in advance: a monthly press calibration, a coolant change, a preventive-maintenance slot. Because you know it ahead of time, you take the hours out of capacity before the plan is built and the schedule simply never offers them. Unplanned downtime is the surprise: a spindle bearing that fails mid-shift, a hydraulic leak. You record the lost hours after the fact, then reschedule so the plan catches up to reality.

Either way, the effect on capacity is the same. During the downtime window, the affected work center has fewer available hours or none at all. When the engine schedules, it treats those hours as gone and walks forward to the next opening, exactly as it does when a machine is simply fully booked. If the step has alternate work centers, the engine can also move the work onto a substitute rather than waiting for the original machine to come back.

Because downtime targets one work center for one window, it is more surgical than a holiday. You can block just the six hours a repair takes, on just the machine involved, without touching any other resource or the rest of the day.

How you enter it today

This is the part worth being precise about, because the term "downtime event" suggests a record you go and create.

The scheduling engine understands standalone downtime records, including ones that recur on a weekday, and it honors them. The current release has no screen for creating them. There is no downtime editor, no recurrence picker, and no scheduled-versus-unscheduled type field to stamp on an event.

So a machine's unavailable time reaches the calendar one of two ways:

• A per-day capacity override on that work center, shift, and date. Type the hours the machine can actually work, or zero if it is out entirely, and add a reason. This is the answer for a specific maintenance day or a repair that already happened.
• Shorter shift hours on that machine's own calendar, when the loss is standing and predictable. A press that gives up an hour every week can simply have a shorter day, which never needs maintaining.

Note what is missing from both: recurrence. There is no weekly repeat anywhere in the calendar, and the plant holiday's recurring flag matches the same month and day each year rather than a weekday. A standing weekly window belongs in the shift definition; anything dated belongs in an override.

A concrete example

Picture the machine log the way a garage tracks a lift. A garage might block one lift on Saturday from eight in the morning until two in the afternoon for a hydraulic repair. That single lift is out; the other bays keep taking cars. That is a downtime event: one resource, one window, a reason attached.

If instead the whole garage closed for a public holiday, no bay would run at all. That is the calendar closing work, not downtime. And if the garage knew in advance that the lift needed an inspection, it would pencil that in ahead of time rather than discovering it when a car was already up in the air. Planned versus unplanned downtime is exactly that difference: one is on the calendar before the fact, the other is recorded after the breakdown.

In the plant, "CNC number three offline Saturday eight to two for spindle replacement" is downtime. The machine loses those hours, the rest of the plant runs, and any operation that was sitting in that window moves forward on the next reschedule.

How EDGEBIC uses it

Downtime is expressed as reduced capacity on the affected work center for the affected dates. The step-by-step is in how to block a machine for a maintenance day, which walks the per-day capacity dialog, and the broader picture of how closed time flows into the plan is covered in how a schedule accounts for holidays and downtime.

Once entered, those hours feed the same capacity math as shifts and holidays, so the reduction appears wherever capacity does: no bars on the machine during the outage, and reduced hours in the capacity views. The anomaly report's off-calendar check watches for bookings that landed inside a window that should have been closed, which catches a block entered after a plan was already built.

Downtime narrows to one machine; the companion term plant holiday closes the whole site by the calendar, and a partial plant holiday blocks a window across every shift that overlaps it. Knowing which lever to pull keeps your capacity honest. For the wider vocabulary, see the manufacturing glossary, and to see downtime inside a live plan, explore EDGEBIC.