Planned vs Unplanned Downtime: Why the Difference Defines Your Maintenance Maturity

Key takeaways

• Planned downtime = scheduled stoppage. Operator and maintenance know in advance.
• Unplanned downtime = unscheduled stoppage. Equipment fails or material runs out without warning.
• The planned/unplanned ratio is the strongest single signal of maintenance maturity. Mature plants: 80% planned. Firefighting plants: 30% planned or less.
• OEE treats planned and unplanned downtime differently: planned production time excludes planned breaks; unplanned downtime is the Availability loss.
• Misclassifying unplanned as planned to flatter the OEE number is a common but corrosive error.

Short answer: Planned downtime is on the schedule — known in advance, prepared for, recovery is fast. Unplanned downtime happens without warning — breakdowns, material starvation, surprise issues. The planned/unplanned ratio is one of the most telling indicators of maintenance maturity. Mature plants run 80%+ planned; firefighting plants run 30% or less. OEE separates them so the ratio is visible. See also Downtime Reason Code Design.

What planned downtime is

Planned downtime is a scheduled stop. Examples:

• Scheduled preventive maintenance.
• Planned changeover between SKUs.
• Operator breaks built into the shift schedule.
• Scheduled cleaning, sanitation, CIP.
• Scheduled meetings, training, turnover.

The defining feature is foreknowledge. Everyone knew it was coming. Resources are prepared. Recovery is predictable.

What unplanned downtime is

Unplanned downtime is an unscheduled stop. Examples:

• Equipment breakdown.
• Material starvation (upstream supply failure).
• Quality excursion forcing a halt.
• Safety event.
• IT or utility outage.

The defining feature is surprise. Resources are not pre-positioned. Recovery is reactive.

How OEE treats each

OEE separates them in the time-state model:

• Planned breaks (lunch, shift change, scheduled cleaning) are excluded from planned production time. They do not affect OEE.
• Planned maintenance and scheduled changeover are typically within planned production time and become Availability loss.
• Unplanned downtime is always Availability loss.

Definitions vary by plant. The important thing is consistency — same definition every shift, every line.

The planned/unplanned ratio as a maturity signal

The ratio of planned downtime to total downtime tells a clear maturity story:

• 80%+ planned: mature reliability program. PMs are effective; breakdowns are rare; the team works to a schedule.
• 50-80% planned: developing. PMs exist but are not yet preventing the majority of breakdowns.
• Under 50% planned: firefighting. Equipment fails faster than the team can plan; reactive work dominates.
• Under 30% planned: reliability crisis. Reactive work consumes the maintenance day; PMs slip; failures accelerate.

Moving the ratio from 30% to 80% planned over 12-24 months is the single highest-leverage maintenance program. It does not require new equipment; it requires PM discipline and reliability engineering.

The misclassification temptation

When OEE reporting incentivizes high Availability, there is a temptation to:

• Reclassify breakdowns as "planned PM" because someone happened to be near the equipment.
• Bucket changeover overruns as "planned changeover" even though they exceeded the allotted time.
• Excuse unplanned starvation as "planned material switch."

This flatters the number while destroying the maturity signal. The ratio becomes useless.

What to do with the ratio

1. Measure honestly. Misclassification corrupts both OEE and the maturity signal.
2. Track per asset and per shift. Aggregate ratios hide assets dragging the average.
3. Set improvement targets for the ratio. Not just for OEE — the ratio drives long-term reliability.
4. Tie unplanned events to root cause work. Every unplanned event should produce learning that prevents the next one.

Why mature plants minimize unplanned even at cost

An hour of unplanned downtime usually costs more than an hour of planned downtime because:

• Resources are not pre-positioned. Technicians and parts have to be located.
• Diagnosis adds time.
• Production loss compounds (downstream starvation, upstream blockage).
• Quality scrap at restart adds Quality loss.
• Stress and rework increase the chance of another failure soon.

Trading planned downtime for unplanned (deferring PMs) usually loses on net. The math favors planned.

Common mistakes

1. Treating all downtime as one number. Loses the maturity signal.

2. Excluding planned downtime from reporting. Plant looks better than it is. Cannot improve what is invisible.

3. Misclassifying unplanned as planned. Flatters the metric and corrupts the analytics.

4. Deferring PMs to "save" downtime. Trades a planned hour for two unplanned hours later.

How a modern OEE platform tracks this

A modern OEE platform tags every downtime event as planned or unplanned, with reason codes for both, and reports the ratio per line, per shift, per asset. The ratio is trendable so the maturity arc is visible.

Fabrico's OEE module separates planned and unplanned downtime explicitly with reason codes for each, reports the ratio with trend, and ties unplanned events to CMMS work orders for root-cause follow-up.

See how Fabrico captures this automatically — explore OEE for manufacturing or book a demo.

Related reading

• Downtime Reason Code Design

Frequently asked questions

Is changeover planned or unplanned downtime?

Planned if it was on the schedule. The overrun (if it exceeded the planned time) is sometimes tracked separately as unplanned.

Should planned breaks count in OEE?

No. Planned breaks (lunch, shift change) are typically excluded from planned production time and do not affect OEE.

Is a PM that took longer than planned still planned?

The planned portion is planned. The overrun is unplanned. Tracking them separately preserves the maturity signal.

What is a good planned/unplanned ratio?

80%+ planned for mature operations. Most plants start much lower and improve over years.

Should I optimize for planned or for less total downtime?

Both. Less total is the goal; more planned within total is the maturity arc. They typically move together as reliability improves.