Blog / Downtime
Downtime · Guide

Machine Downtime Categories for OEE Reporting

OL By OEE Lab Editorial |Updated 2 November 2026 |5 min read
Short answer

A clear OEE report sorts machine time into five downtime categories: excluded time, planned stops, induced stops, unplanned downtime and short stops. Excluded time sits outside OEE. Planned, induced and unplanned stops lower availability, and short stops under your threshold fall into performance.

Why one downtime bucket is not enough

A single "downtime" number tells you the line lost time. It does not say who can win it back.

A late pallet of cartons and a burnt-out motor can each cost 40 minutes. One belongs to logistics and the other to the technicians, so they need different categories.

Categories sit one level above the causes. The cause says "labeller web break", and the category says "unplanned, technical".

To build the cause list itself, use the guide to downtime reason codes.

The five categories at a glance

CategoryExamplesUsual ownerOEE effect
Excluded timeNo orders, holiday, shutdown set well aheadPlanningOutside OEE, shows in TEEP
Planned stopChangeover, scheduled clean, standard testProductionAvailability
Induced stopNo material, no crew, blocked, starvedLogistics, planningAvailability
Unplanned downtimeFailure, wrong setup, bad batch stops the lineTechnicians, production, qualityAvailability
Short stopJam cleared under your stop thresholdLine teamPerformance
Only excluded time leaves OEE. The other four all cost output.

This five-way split is a reporting convention, and plants name the groups in different ways. Unplanned downtime can then be split once more into technical, operational and quality.

That three-way split matters because the fixes differ. A bearing failure is technical, a wrong recipe is operational, and an out-of-spec batch is quality.

How this maps to the six big losses

You may already report Nakajima's six big losses. The two views fit together.

  • Breakdowns are unplanned technical downtime.
  • Setup and adjustment covers most planned stops, such as changeovers.
  • Idling and minor stops are your short stops. They also include some induced waiting if it stays under the threshold.
  • Reduced speed, defects and yield loss are not downtime. The machine is running, so they are measured from counts.

The six losses leave one gap: they do not name induced stops. Waiting for material or a crew has its own owner, so give it its own line.

See waiting for material and blocked and starved.

Worked example: one shift, every minute in a category

Example: a bottling line runs an 8-hour shift of 480 minutes. A 30-minute break with no relief crew is not planned for production, so it is excluded.

Shift length480 min
Excluded: break, no relief30 min
Planned production time450 min
Planned stop: changeover35 min
Induced stop: no cartons25 min
Unplanned, technical40 min
Unplanned, operational10 min
Unplanned, quality10 min
Run time330 min
Each bar starts where the last one ended. Bar widths are shares of the 480 minute shift.

The stops add up to 35 + 25 + 40 + 10 + 10 = 120 minutes. Run time is 450 - 120 = 330 minutes, so availability is 330 / 450 = 73.3%.

Now the report can say more than "we lost 120 minutes". Technical faults took 40 minutes, which is one third of the stops, and two thirds belong to someone else.

The category you pick moves the numbers

Take the same shift and change only the rule. Assume performance of 90% and quality of 98% in the base case.

RuleAvail.Perf.Qual.OEE
Base case: break excluded73.3%90.0%98.0%64.7%
Break counted as a planned stop68.8%90.0%98.0%60.6%
10 min of jams fall under the threshold75.6%87.4%98.0%64.7%
Moving time out of planned production changes OEE. Moving it between availability and performance does not.

In row 2, planned time grows to 480 minutes, and 330 / 480 = 68.8%. OEE falls because the denominator grew.

In row 3, run time rises to 340 minutes, but the same output now counts as slower running. Net run time stays 330 x 0.90 = 297 minutes, and 297 / 340 = 87.4%, so OEE does not move.

So the choice that matters most is the excluded rule. Write it down once, and use it on every line you plan to compare.

Gray areas you will meet on the floor

  • Breaks. Practice varies. If a relief crew could keep the line running, many plants count the break as a loss. See how to count breaks in OEE.
  • Changeovers. They are planned, and they still cost availability. See how to count changeovers.
  • Maintenance in a production window. It stays a planned stop unless the time was taken out of the schedule well ahead. See does maintenance count in OEE.
  • A planned stop that runs over. Count the planned length as planned and the extra as unplanned.
  • Stops of a minute or two. The stop threshold decides, so pick it once. See how to set a stop threshold.

Set the categories up in four steps

1
Write the excluded rule
List what leaves planned production time, and who may approve it.
2
Write the stop threshold
Below it, a stop is a short stop. Above it, the stop gets a category and a cause.
3
Add one category per stop
Keep the category beside the cause in the log, so totals never need rework.
4
Report by category each week
Show minutes per category and name one owner per bar.
Do this before you build charts, or last month will not compare with this month.

A stop log with both fields feeds the OEE loss tree and a downtime Pareto chart. To collect the stops, start from how to track downtime.

Mistakes that blur the categories

  • Letting planners mark a bad week as "no orders" after the fact.
  • Putting waiting for material inside "breakdowns", which hides it from the people who can fix it.
  • Adding speed loss to downtime. A slow machine is running, so it belongs in performance.
  • Using a different category list on each line, which makes the plant total meaningless.
See it live in Fabrico

Categories only help if each stop has one. Operators tag the cause at the line in Fabrico, against stops taken live from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal. See how Fabrico tracks stops by line.

What people ask next

What are the main categories of machine downtime?

Excluded time, planned stops, induced stops, unplanned downtime and short stops. Only excluded time sits outside OEE. For the causes under each one, see machine downtime reasons.

Which downtime categories count against OEE availability?

Planned stops, induced stops and unplanned downtime all lower availability. Short stops under your threshold show up as performance loss instead. See availability, performance and quality.

Is waiting for material planned or unplanned downtime?

It is unplanned, since nobody scheduled it, but it did not come from the machine. Many plants report it as an induced stop, so logistics owns the bar. See waiting for material downtime.

How many downtime categories should a plant use?

Keep the top level small, about five or six, and use the same list on every line. Machine-specific detail belongs in the causes under each category. The reason codes guide shows how to build them.

Is no-order time downtime?

Not for OEE, because the line was not planned to run. It is still lost capacity, so it shows in TEEP. See OEE with no orders.

See OEE per line and shift on your own machines

Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.

Book a Fabrico demo

← More OEE Lab guides · Machine downtime reasons →

OEE essentials: OEE calculator · What is OEE · Six big losses · Availability · TEEP · Cost of downtime · OEE benchmark · Free OEE tracker · Free OEE software · How to track downtime · How to implement OEE · Light MES vs full MES