Sometimes. The 85% figure is a world-class mark for discrete and batch processes, from R. C. Hansen's book building on Nakajima's TPM figures. Hansen sets higher bars for dedicated discrete and continuous processes. Whether 85% is realistic for your line depends on process type, changeovers and how honestly OEE is measured.
Where the 85% comes from
The 85% figure is old and well known. It goes back to the TPM work of Seiichi Nakajima. Overall Equipment Effectiveness (R. C. Hansen, 2001) builds on that work and sets the world-class bar by process type.
| Process type | World-class bar (Hansen, building on Nakajima) |
|---|---|
| Discrete and batch | 85% or more |
| Dedicated discrete, and non-dedicated continuous | 90% or more |
| Dedicated continuous (on-stream) | 95% or more |
So in Hansen's scheme, which builds on Nakajima, 85% is the lowest of the three world-class bars, not the top. For a dedicated continuous process, 85% is still short of the bar.
Note that the bar is for OEE as a whole. How the 85% splits between availability, performance and quality depends on where your line loses time, as the example further down shows.
How Hansen rates your own number
Hansen also gives plain ratings for key processes, which are a better test of "how are we doing" than a single bar.
He adds that the gap between your OEE and world class is your first look at the hidden factory. And a gap of the same size matters more when you start low, because large losses are easier to find.
What 85% asks for, in minutes
OEE is a share of scheduled time. So 85% means that 15% of scheduled time is allowed to go to every loss together.
Example: a 480-minute shift. The line has to make 408 minutes of good output at the ideal rate. One way to split the 72 minutes of loss:
The stops budget is 38.4 minutes for a whole shift. Everything counts: breakdowns, changeovers, waiting for material, short breaks you did not exclude. That is what "85%" really asks.
Why it is hard on some lines
Batch and high-mix lines lose time to changeovers by design. Example: a line runs three changeovers of 30 minutes in a 480-minute shift. That is 90 minutes, so availability can be at most 390 ÷ 480 = 81.25%, even with no breakdown, full speed and perfect quality.
That line cannot reach 85% until the changeovers get shorter. At 15 minutes each, the stops are 45 minutes, and availability can reach 90.6%. See SMED changeover reduction and OEE for batch processes.
Hansen's bars are higher for continuous work. Our reading is that a line that runs for days without a changeover has less built-in loss, so it can be held to more.
Why it can also be too easy
An 85% on paper can be a poor result. Three common causes:
- Too much excluded time. Hansen allows excluded time only for things planned as not for production, such as shutdowns planned at least a week ahead. Moving real losses into excluded time lifts OEE and changes nothing in the plant.
- An ideal rate set low. If the ideal is last month's average, performance reads near 100%. See ideal cycle time.
- Rework counted as good. Quality then reads near 100%. See how to calculate OEE quality.
Hansen's test is that OEE must track actual output. If OEE is high and output is not, the measure is lying. The list of errors is in OEE calculation mistakes.
What the plants that get there do differently
Hansen describes two kinds of plant. A reactive plant typically sits below 70% OEE, with more than 15% of its work unplanned. A proactive plant sits at 80% or more. It is run on data, uses condition-based maintenance, statistical process control and designed experiments, and manages change well.
The point is that the number follows the way of working. A plant does not reach a high OEE by asking for one. It gets there by removing the same stops, one cause at a time, and by keeping the data honest enough to see them.
Hansen also says the cost of a program like this is mostly training and time, with little capital. That is why he compares it with buying new capacity, and why a lower number is not a verdict. It is a place to start.
A five-question test of your own number
Before you compare your OEE with any bar, check how it was made.
- Is excluded time really planned? Shutdowns set at least a week ahead, headroom, no product scheduled. Not "quiet periods" that happened.
- Is the ideal rate accredited? Not last month's average.
- Is rework out of good units? A unit fixed later was not good the first time.
- Does OEE follow output? In Hansen's case study, online OEE tracked actual output with a correlation above 0.9. If your OEE goes up and output does not, something is missing.
- Do the losses add up? OEE plus every loss must equal 100% of scheduled time. If two ways of computing OEE disagree, Hansen says to trust the lower one.
If you can answer yes five times, your number is honest, and the comparison with the bar means something. If not, fix the measure first. A higher number built on a soft measure is worse than a lower one you trust.
How to use the 85% number
- Measure honestly first. Use the same rules every week, and reconcile the losses to 100%.
- Pick the right bar. Discrete or batch, dedicated or not, continuous or not. The bar for your process type is the one to compare.
- Turn the gap into minutes. Example: a line at 73.5% loses 26.5% of a 480-minute shift. To reach 85% it must remove 11.5 points, which is 43% of its losses (11.5 ÷ 26.5).
- Attack the biggest loss first. Not the biggest number on the dashboard.
The step from "a gap" to "a target" is in how to set OEE targets. For a wider view of published benchmarks, see the OEE benchmark report. For what OEE means at all, start with what is OEE.
A target only helps if you can see the gap every shift. Fabrico shows OEE per line and shift, with stop causes tagged by operators at the line, so the gap to your own target is split into named losses. See OEE per line and shift in Fabrico.
What people ask next
Is 85% OEE good?
For a discrete or batch process, 85% matches the world-class bar in Hansen's book, which builds on Nakajima's TPM figures. In Hansen's own ratings for key processes, 75% to 85% is "pretty good", so a plant at 80% is not failing. Read the loss data before you judge a single number.
Is 100% OEE possible?
It is the theoretical maximum: no stops, ideal speed, every unit good. In practice no line holds it. Hansen cites 98% sustained for two years at one olefin plant, which shows how far a continuous process can go, but that is the exception.
Is an OEE of 60% bad?
Hansen rates a key process below 65% as unacceptable and says hidden money is slipping away. But the number alone does not say why. A low start also means big losses are easy to find. See how to improve OEE.
Should every machine in the plant aim for 85%?
No. Hansen says to apply OEE to bottlenecks first, then to critical or high-cost areas. A machine that is not a bottleneck gains the plant little. See bottleneck analysis and line OEE vs machine OEE.
How does TEEP compare with 85%?
TEEP uses all calendar time, so it is never higher than OEE for the same line. Do not hold a TEEP figure against the 85% mark, which Hansen, building on Nakajima, sets for OEE on scheduled time. The two are compared in OEE vs TEEP.
Related guides: OEE for Continuous Processes: How to Measure It · History of OEE: From Nakajima to Hansen and ISO · OEE for Process Manufacturing: A Plant Guide · OEE values reported in published studies