Blog / Losses
Losses · Guide

The OEE Loss Tree: Classify Every Minute of Time

OL By OEE Lab Editorial |Updated 1 November 2026 |6 min read
Short answer

The loss tree puts every minute of the clock in one box: excluded time, stop time, downtime, speed loss, waste or good output. The boxes below scheduled time are the losses. OEE plus all the losses equals 100% of scheduled time, so nothing is left unexplained.

The tree

The tree below is the one in Overall Equipment Effectiveness (R. C. Hansen, 2001). Its idea is simple: every minute of the clock belongs to exactly one box.

Calendar time
Every minute of the clock
Excluded time
Planned, and not scheduled for production
Scheduled time (loading time)
What OEE is measured against
Stop time (ST)
Operational: planned, part of normal running. Induced: outside the machine
Downtime (DT)
Unplanned. Technical, Operational or Quality
Operating time (runtime)
The machine is making product
Speed loss
Running below the ideal rate
Waste
Time spent on units that are not good
Theoretical run time = OEE
Good units ÷ ideal rate
Hansen's classification of time. Everything under scheduled time is either a loss or good output.

OEE is the last box: the minutes you would have needed to make the good units at the ideal rate. Everything else under scheduled time is a loss. Their sum is 100%.

What goes in each box

BoxWhat it isExamples
ExcludedPlanned, not scheduled for productionShutdown planned at least a week ahead, no product scheduled, planned meetings or training, time freed by finishing early
ST OperationalPlanned stops that are part of normal runningChangeovers, size changes, standard tests, planned material loading
ST InducedUnplanned, caused outside the machineNo material, no people, no information, waiting for upstream or downstream
DT TechnicalEquipment failureBreakdowns, utilities, maintenance errors, contamination caused by the equipment
DT OperationalPeople or procedureOperator error, wrong material loaded, not following procedure
DT QualityMaterial or process qualityOut-of-spec raw material, process-control problems, unplanned testing
Speed lossRunning below the ideal rateHalf speed because of a raw material problem
WasteUnits that are not goodStructural, incident, testing and recall waste

Hansen's loss codes are STO, STI, DTT, DTO, DTQ, W (waste) and S (speed). They are short enough to write on a shop-floor sheet.

Five questions to classify an event

  1. Was it planned as not for production (scheduled at least a week ahead, headroom, an experiment whose product will not be sold, finished early)? Then it is excluded time.
  2. Is it a planned, normal part of running orders such as a changeover or standard test? Then it is ST Operational.
  3. Is the line stopped by something outside the machine such as no material, people or information? Then it is ST Induced.
  4. Is it unplanned? Equipment caused it: DT Technical. People or procedure: DT Operational. Material or process quality: DT Quality.
  5. Is the machine running? If it is slow, it is speed loss. If the units are not good, it is waste, counted in units, not as downtime.

The last rule is a favourite trap. Hansen's example: 40 minutes of contaminated production is waste, not technical downtime, because the machine was running.

Worked example: Hansen's 40-hour run

The book follows a run of 2,400 calendar minutes with an ideal rate of 4 units a minute. Excluded time is 570 minutes (shift start, planned lunches, a planned two-hour shutdown, no product scheduled, a meeting and an experiment). That leaves 1,830 scheduled minutes.

The stops and downtime are: ST Operational 170 minutes, ST Induced 60, DT Technical 150, DT Operational 30 and DT Quality 80. Together they are 490 minutes, so runtime is 1,830 − 490 = 1,340 minutes. The line runs 1,000 minutes at full rate and 340 minutes at half rate, so it makes 4,680 units. Of those, 4,362 are good.

LossCalculationMinutesShare of 1,830
Waste(4,680 − 4,362) ÷ 479.54.3%
Speed loss1,340 − 4,680 ÷ 4170.09.3%
ST Operationalfrom the log170.09.3%
ST Inducedfrom the log60.03.3%
Downtime150 + 30 + 80260.014.2%
Good output (OEE)4,362 ÷ 41,090.559.6%
Total1,830.0100.0%
Good output (OEE)59.6%
Downtime14.2%
ST Operational9.3%
Speed loss9.3%
Waste4.3%
ST Induced3.3%
The 1,830 scheduled minutes of Hansen's example. The losses add to 40.4% and OEE is 59.6%.

Check it three ways. Availability 1,340 ÷ 1,830 = 73.2%, speed 0.873, quality 4,362 ÷ 4,680 = 0.932, and 0.732 × 0.873 × 0.932 = 59.6%. Method 3 gives 1,090.5 ÷ 1,830 = 59.6%. The losses 40.4% plus OEE 59.6% make 100%.

Over the full 2,400 minutes, the same good output is 1,090.5 ÷ 2,400 = 45.4%. That is TEEP. See OEE vs TEEP.

How to start with a one-page sheet

You do not need software to begin. A one-page sheet per run is enough: scheduled time, a row for each event with start, end and loss code, the total units, the good units and the ideal rate.

At the end of the run, add the minutes by code. Add the waste and speed loss from the unit counts. The total must equal the scheduled time. If it does not, ask what is missing before you file the sheet.

Keep the code list short, so that people use it. Hansen warns against too much detail: enough to focus priorities, not so much that people drown in data.

What the tree tells you to do

In the example, downtime is the biggest loss at 14.2%, but the two stop boxes together (12.6%) are nearly as big. ST Operational (changeovers, standard tests, planned loading) is 9.3% on its own. If most of it is changeovers, that points to SMED, not to repairs.

Unplanned boxes are the worst for the business. Hansen ranks induced stops and downtime below planned downtime in value, and he says reactive repairs cost three to five times more than planned ones. That is why the split between planned and unplanned matters.

Hansen also asks you to record how often events happen, not only how long they last. A box with many short events is a different problem from one with a few long ones. Start with the Pareto: rank the minutes by category, then inside the top category by cause. See the downtime Pareto chart.

For the six-loss view that many plants already use, see six big losses and the six big losses calculator. For the formula itself, go to how to calculate OEE.

See it live in Fabrico

A loss tree only works if each stop gets a category. In Fabrico, stops come live from the machine and operators tag the cause at the line, so every minute lands in a loss box while it is fresh. See how Fabrico tags stop causes.

Book a Fabrico demo

What people ask next

What is the difference between stop time and downtime?

In Hansen's tree, stop time is planned or caused outside the machine: changeovers, standard tests, waiting for material or people. Downtime is unplanned and caused by the equipment, people or procedures, or material quality. See planned vs unplanned downtime.

How does the loss tree relate to the six big losses?

The six big losses are Nakajima's list. Hansen's tree is a finer version for scheduling and cause work. Roughly, breakdowns map to technical downtime, setup to operational stops, minor stops to short downtime events (or speed loss if nobody logs them), reduced speed to speed loss, and defects and start-up yield to waste. Waiting for material or people, which the six losses do not name, is Hansen's induced stop time. See the six big losses.

Where do micro-stops go?

If you log them, they are stops and belong in availability. If you do not, they stay in run time and appear as speed loss. Logging them gives them a cause. See micro-stops.

Should I use a category called "other"?

No. Hansen says to categorise every minute and never use "miscellaneous" or "other". If an event does not fit, add a category or split the event. See downtime reason codes.

Do I need all the categories to start?

No. Start with excluded, stops, downtime, speed and waste, and add detail when a category becomes big. Hansen warns against too much detail: enough to focus priorities, not so much that people drown in data. A downtime Pareto chart shows where to split next.

Related guides: Does Planned Maintenance Count in OEE or TEEP? · OEE vs Technical Availability: The Key Gap · Machine Downtime Categories for OEE Reporting

← More OEE Lab guides · Open the OEE calculator → · Try the loss tree simulator →

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