Your line, one average shift
Use minutes and counts for the same shift. The defaults are the worked example below.
The loss tree for one shift
What if you fix part of it?
Move a slider to win back part of one loss. The rest of the line stays as it is today.
All four together can add more than the four bars, because recovered minutes also run faster and with less scrap. Extra units earn margin only if you can sell them.
Want a second look at this result?
Leave your work email if you would like the OEE Lab team to get in touch about your numbers. To keep the result, use Copy link or Print above.
No newsletter, no spam.
A simulator only knows the minutes you type in.
Short stops nobody logs hide inside the speed branch of the tree. Fabrico tracks downtime live from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal and, where cameras are fitted, can stream video of a stop on request next to its machine data, so the line actually runs at the pace it's capable of.
Request a demo Contact usWhat the OEE loss tree simulator does
It takes one average shift of your line and splits the planned production time into the three OEE losses: downtime, speed loss and quality loss. What is left at the bottom is fully productive time, the minutes spent making good units at the ideal rate.
Then it lets you test fixes. Move a slider to win back part of a loss, and the simulator shows the new OEE, the extra good units a year and the extra margin a year.
The OEE calculator gives you the score. This page shows where the minutes went and which loss is worth attacking first.
The formulas: Hansen's time model
The simulator follows the time model in Overall Equipment Effectiveness (R. C. Hansen, 2001). Each level of the tree is the level above it minus one loss.
OEE = Availability × Performance × Quality
- Run time = planned production time - unplanned stops - changeovers. Availability = run time ÷ planned production time.
- Net run time = total count × ideal cycle time. Performance = net run time ÷ run time, and the gap between them is speed loss.
- Fully productive time = good count × ideal cycle time (Hansen calls it theoretical run time).Quality = good count ÷ total count, and the gap is quality loss.
- OEE = fully productive time ÷ planned production time. It is the same number as A × P × Q.
Hansen's full tree splits the losses more finely, into stop time, downtime, speed and waste. The OEE loss tree guide shows that version and how to code each event.
Worked example: the default numbers
Example: a packing line plans 450 minutes a shift and runs 10 shifts a week for 48 weeks. In an average shift it loses 50 minutes to unplanned stops and 40 minutes to changeovers.
Its ideal cycle time is 3 seconds a unit. It makes 5,760 units a shift, 5,472 of them good, and each good unit carries a margin of 0.50.
| Level | Calculation | Minutes | Ratio |
|---|---|---|---|
| Planned production time | given | 450 | 100% |
| Downtime | 50 + 40 | 90 | 20.0% lost |
| Run time | 450 - 90 | 360 | A = 80.0% |
| Net run time | 5,760 × 3 s ÷ 60 | 288 | P = 80.0% |
| Speed loss | 360 - 288 | 72 | 16.0% lost |
| Fully productive time | 5,472 × 3 s ÷ 60 | 273.6 | Q = 95.0% |
| Quality loss | 288 - 273.6 | 14.4 | 3.2% lost |
| OEE | 273.6 ÷ 450 | 60.8% |
Over a year that is 480 shifts, 2,626,560 good units and 1,313,280 of margin.
With every slider at 25%, each lever on its own gives this:
| Lever at 25% | Minutes back a shift | Extra good units a year | Extra margin a year |
|---|---|---|---|
| Changeovers | 10 | 72,960 | 36,480 |
| Unplanned stops | 12.5 | 91,200 | 45,600 |
| Speed gap | 18 | 164,160 | 82,080 |
| Scrap | 3.6 | 34,560 | 17,280 |
All four together lift OEE from 60.8% to 69.5%, worth 377,595 extra good units and 188,798 of margin a year.
The speed gap wins, even though stops look bigger on the log. A minute won back from a stop still runs at 80% performance and 95% quality, so it is worth only 0.76 of a good minute, while a minute won back from speed loss is worth 0.95.
How to read the tree
Read it from the top down. Each loss bar sits exactly where it comes off the bar above it, so the widths always add up to the planned time.
Find the widest loss bar first. It is the biggest pool of minutes, but not always the cheapest one to drain.
Speed loss is often the surprise, because it has no reason code and hides inside run time as slow cycles and short stops. The speed losses guide and the hidden factory calculator help you size it.
The six big losses fit the same branches. Breakdowns and setups sit in downtime, minor stops and reduced speed in speed loss, and defects and start-up rejects in quality loss; see the six big losses.
Common mistakes
- Taking changeovers out of planned time. They are planned, but the line is scheduled and not making product, so they belong in availability loss. See how to count changeovers in OEE.
- Using the average cycle time as the ideal. The average already contains the slow running, so the speed lever looks worthless. Use the fastest proven cycle for the product.
- Counting short stops twice. If you log them as unplanned stops, they must not also sit in the speed gap. Each lost minute goes in one branch only.
- Reading extra units as extra money. They earn margin only if you can sell them. With fixed demand, the gain shows up as fewer hours instead.
- Ranking levers on the percent alone. 25% of changeover time and 25% of the speed gap are different jobs with different costs. Use the verdict to rank the payoff, then price the work.
If performance comes out above 100%, the simulator caps it and says so. That always points to a wrong input, most often the ideal cycle time; see performance over 100%.
Turn the biggest lever into a plan
Pick one lever, give it a target and measure it every shift. The guide on how to set OEE targets shows how to turn a gap like this into a target per factor.
For teams turning the biggest lever into a plan, Fabrico has a guide to building an OEE improvement strategy.
Loss tree simulator FAQ
What is an OEE loss tree?
It splits planned production time into run time, net run time and fully productive time, with one loss between each level: downtime, speed loss and quality loss. Fully productive time divided by planned production time is the OEE.
What is fully productive time?
It is good count times ideal cycle time: the minutes you would have needed to make only the good units at the ideal rate. In the default example it is 5,472 × 3 seconds = 273.6 minutes, and 273.6 ÷ 450 gives an OEE of 60.8%.
Which OEE loss should I fix first?
Start with the lever that returns the most good units for the effort, not the biggest number on the stop log. A minute won back from a stop still carries the line's speed and quality losses, so a minute of speed gained is worth more.
Why does the simulator cap performance at 100%?
Performance above 100% means the line made more units than its ideal cycle time allows, so an input is wrong. The simulator caps it so the tree still adds up, and shows a note. See performance over 100%.
Is 85% OEE the right target?
85% is the world-class figure usually traced to Seiichi Nakajima's Introduction to TPM (1988). Set your own target from your baseline and the lever you will work on. See how to set OEE targets.
Do extra good units always mean extra money?
No. They earn margin only if you can sell them. If demand is fixed, the same gain shows up as fewer hours, less overtime or a free shift instead.