The problem with OEE as a KPI
OEE is a ratio. It measures Availability × Performance × Quality. In theory, it gives you a single number that reflects how well you're running your equipment. In practice, the formula is usually right and the data and methods behind it are not.
The common mistake is treating OEE as a report card rather than a diagnostic tool. A plant hits 72% OEE and either celebrates or panics, and rarely asks the more useful question: which of the three components is driving that number, and why? Answering that on demand is the whole point of OEE tracking built on live machine data.
The three components are not equal
Availability, Performance, and Quality each tell a different story about your operation. Collapsing them into a single number hides that story.
Availability: the honest one
Availability measures how much of your planned production time the equipment was actually running. It's the most honest of the three because downtime is hard to hide. If the line was down, it was down. The challenge is that planned downtime — scheduled maintenance, changeovers, breaks — is almost always excluded from the denominator, which means a plant can game its availability number by converting unplanned downtime into planned time after the fact.
Performance: the slippery one
Performance is speed loss — the ratio of actual output rate to the theoretical maximum. This is where the most distortion happens. If your theoretical maximum rate is set too low (too conservatively), your performance score looks great even when the line is crawling. We've seen plants running at 60% of true capacity reporting "95% performance" because someone set the ideal cycle time to a number the line can always hit.
Base your ideal cycle time on the best rate the line has sustained over a long run, rather than the nameplate speed or a number picked to make the metrics look good.
Quality: the one everyone forgets to close
Quality is the ratio of good parts to total parts produced. The trouble is that scrap and rework often go on paper first and get entered into a system hours or days later. By the time the quality loss shows up in OEE, the production run is over and the root cause has gone cold.
OEE is only useful when the data feeding it is captured in real time, at the source, by someone with a stake in the accuracy of the number.
Five ways plants corrupt their OEE data
- Converting unplanned downtime to planned after the fact. The line goes down unexpectedly. Someone calls it a scheduled changeover in the system. Availability climbs. The problem never gets investigated.
- Setting conservative ideal cycle times. If the "ideal" is already 80% of actual maximum throughput, your performance metric is meaningless. Ideal means ideal — the rate you can sustain when everything is running right.
- Capturing quality losses at shift end rather than real time. End-of-shift quality reconciliation produces estimates. It also makes it impossible to tie a defect to the conditions on the line when it was made.
- Including time the line wasn't scheduled to run. Some systems calculate OEE against calendar time rather than planned production time. That rewards a plant for adding shifts, whether or not they run well.
- Aggregating OEE across machines to get a line number. A line OEE hides which asset is the bottleneck. Report OEE at the machine level first, then roll up.
What good OEE measurement looks like
Good OEE data starts with two things: automated cycle counting and real-time operator entry. Cycle counts come from the machine — a sensor, a PLC signal, or a proximity switch — so the system always knows how many parts were produced and at what rate. Downtime and quality losses come from operators entering them in the moment, with a structured reason code list that's short enough to use but granular enough to be useful.
With both in place, the weekly meeting can use OEE to pick what to fix next instead of debating whether the number is right.
Why 85% isn't the target
World-class OEE is often cited as 85%. That benchmark means little for a discrete manufacturer. The 85% number is not an empirical statistic; it is the mathematical product of three component targets Nakajima proposed in 1988. What matters is what's holding your own plant back, and working through those losses one at a time.
A plant with an honest 68% OEE and a clear improvement roadmap is in far better shape than a plant with a massaged 81% and no idea where its losses are.
Doing the arithmetic right
Two calculation mistakes distort OEE even when the data underneath is good.
Averaging percentages across machines. Machine A runs at 80% OEE over 450 planned minutes; machine B runs at 40% over 90 minutes. The simple average says 60%. Weighted by planned time it's (0.80 × 450 + 0.40 × 90) ÷ 540 = 73.3%. The simple average gives a machine that barely ran as much say as one that ran all shift. Roll up by weighting with planned time, or add up good-part time across machines and divide by total planned time.
One ideal rate for every product. If a machine runs parts with different cycle times, a single ideal rate makes Performance swing with the product mix instead of with how well the line ran. Measure earned time per product (parts made × that product's ideal cycle) and divide the total by run time.