Key takeaways
- OEE = Availability × Performance × Quality. Three factors at 90% give 72.9%, not 90%.
- The decomposition matters more than the headline percentage — it tells you which factor to fix.
- Most gaming happens in planned production time: exclude enough and any line looks excellent.
- Compare a line against itself over time. OEE across different lines is rarely meaningful.
Overall Equipment Effectiveness (OEE) is a single percentage that combines three things: how much of the planned time a machine was available, how fast it ran while available, and how much of what it made was good. Multiply the three and you get one number that answers “how much useful output did we get compared with the theoretical maximum?”
It is genuinely useful, and it is also one of the most commonly gamed metrics in manufacturing. Both facts are worth understanding before you put it on a screen.
The calculation
OEE is the product of three factors, each a percentage:
- Availability = Run Time ÷ Planned Production Time
- Performance = (Ideal Cycle Time × Total Count) ÷ Run Time
- Quality = Good Count ÷ Total Count
OEE = Availability × Performance × Quality
Because the three multiply rather than average, OEE falls away quickly. Three respectable-looking factors of 90% each give an OEE of 72.9%, not 90%. That compounding is the point: it stops one strong factor from hiding two weak ones.
A worked example
A line is scheduled for an 8-hour shift, so planned production time is 480 minutes. It stops for 45 minutes across a changeover and a jam, so run time is 435 minutes.
The ideal cycle time is 0.5 minutes per unit. In those 435 minutes it produced 780 units, of which 760 were good.
- Availability = 435 ÷ 480 = 90.6%
- Performance = (0.5 × 780) ÷ 435 = 390 ÷ 435 = 89.7%
- Quality = 760 ÷ 780 = 97.4%
OEE = 0.906 × 0.897 × 0.974 = 79.2%
Note what that tells you that a single output figure would not: the biggest losses are availability and speed, roughly equally, and quality is comparatively healthy. That is a different improvement plan from a line with 98% availability and 85% quality.
Three factors at 90% do not give you 90%. They give you 72.9% — which is exactly why OEE is worth calculating.
The traps
Planned production time is where the gaming happens
Availability is a fraction of planned time, so anything excluded from the denominator improves OEE without improving anything real. Exclude changeovers, breaks, planned maintenance and “unschedulable” periods and you can produce a very impressive number for a line that is not producing much. Decide what counts as planned time, write it down, and do not change it because the number looks bad.
Ideal cycle time drifts optimistic — or pessimistic
Performance depends entirely on the ideal cycle time you compare against. If it was set generously years ago, Performance will sit near 100% forever and tell you nothing. If it was set to a best-ever run nobody can repeat, it will look permanently broken.
Rework counts as bad
A unit that failed and was reworked into a good unit is not a good first-pass unit. Counting it as good hides exactly the quality signal you built the metric to see.
Watch out for
OEE compared between different lines is usually meaningless. A 65% on a complex line with frequent changeovers may be a far better operation than an 85% on a long-run dedicated line. Compare a line against itself over time — that is the comparison the number is honest about.
What OEE is good for — and what it is not
It is good for trend. Watching one line’s OEE over months, with the three factors shown separately, tells you whether interventions worked and which factor is degrading.
It is good for diagnosis, precisely because it decomposes. The headline percentage is the least interesting part; Availability, Performance and Quality side by side are where the decisions live.
It is bad as a target handed down without context, because every one of the traps above is easier to exploit than the underlying problem is to fix. If OEE becomes something people are judged on rather than something they use, it will improve on the report and not on the floor.
Try this
Before publishing OEE anywhere, calculate it by hand for one shift on one line using your existing records. If you cannot source run time, total count and good count without asking three people, the metric is not ready — and that gap is the real first project.
Getting the inputs without a clipboard
OEE needs three data streams: stop duration, unit counts, and quality outcomes. All three are things a shop-floor system should be capturing anyway.
Machine data gives you accurate run time and total count without transcription. Operator entry gives the reason for each stop, which is what turns Availability from a number into an action. Quality checks recorded against the same work order give you Good Count without a separate reconciliation.
Capitán MES reads machine data directly and holds work orders, quality control and waste management in the same record, so the OEE inputs come from production as it runs rather than from a month-end rebuild. If you want to see what that looks like against your own lines, talk to our team.
The short version
OEE = Availability × Performance × Quality. The multiplication is the feature. Define planned time honestly, keep ideal cycle time current, count reworked units as bad, and compare a line only against itself.