OEE calculation explained
OEE calculation explained in one line: overall equipment effectiveness equals Availability (run time divided by planned production time) times Performance (ideal cycle time times total count, divided by run time) times Quality (good count divided by total count). The shortcut is good count times ideal cycle time, divided by planned production time. The score is only as honest as those inputs.
Picture a board at the end of a line that reads 82% OEE. That is within sight of the 85% figure everyone calls world-class. Yet the plant cannot take an extra order next month without scheduling overtime. The arithmetic on the board is fine. The framing is not. Three choices made before anyone touches the formula decide what the score says: what counts as planned production time, which cycle time you divide by, and how you roll machines up into a plant number. In many plants all three lean the same way.
This guide walks through the formula, the three leaks, and a worked example on one hypothetical line (not a plant we visited). On that line a reported OEE of 82.1% falls to 55.2% when calculated to the standard definitions, and roughly 73% of the weekly capacity gap is invisible in the reported version.
The formula and the six losses behind it
The standard definitions published by OEE.com (Vorne) are compact:
-
Availability = Run Time / Planned Production Time
-
Performance = (Ideal Cycle Time × Total Count) / Run Time
-
Quality = Good Count / Total Count
-
OEE = Availability × Performance × Quality, which simplifies to (Good Count × Ideal Cycle Time) / Planned Production Time
Planned Production Time, in that framework, is shift length minus breaks. The only time excluded is time when there is no intent to produce.
Each factor absorbs specific losses. OEE.com's Six Big Losses map them this way:
| OEE factor | Losses it captures | | --- | --- | | Availability | Equipment failure; setup and adjustments (changeovers) | | Performance | Idling and minor stops; reduced speed | | Quality | Process defects; reduced yield (startup scrap) |
That mapping matters because each of the leaks below works by quietly moving a loss out of the factor where it belongs and into nowhere.
Leak 1: the shrinking denominator
The most common adjustment is to classify changeovers, preventive maintenance, startup and sometimes shift meetings as "planned downtime" and remove them from planned production time. Availability then looks excellent, because the hours that hurt it are no longer in the calculation.
The standard guidance says otherwise. The OEE.com FAQ is direct: "Changeover time should be included in OEE (specifically, it should be included in Availability)." Preventive maintenance that takes away time that could otherwise be used for production belongs there too. A changeover is setup and adjustment, one of the six big losses. Scheduling it in advance does not make it free.
The operational cost of the shortcut is that the changeover study never gets funded. If eight hours a week of changeover sit outside the denominator, SMED work cannot move the OEE number, so it loses the argument for engineering time against projects that can.
The fix: planned production time = shift length minus breaks. If a line is scheduled to run, every minute it is not producing a good part at ideal rate shows up in one of the three factors.
Leak 2: the padded ideal cycle time
The second leak sits in Performance. Many plants divide by the routing standard or the budget cycle time, which usually has allowances built in for older equipment, material variation or operator pace. Performance then lands in the 90s without much effort.

OEE.com defines ideal cycle time as "the theoretical maximum throughput of the machine or process," meaning the nameplate rate or the fastest rate demonstrated in a time study. It "should generally NOT be lowered due to factors such as machine age or material quality," and using a standard cycle time will "artificially raise your OEE score, while hiding loss and slowing improvement."
There is a built-in tell. According to the same FAQ, if Availability, Performance or Quality ever exceeds 100%, "something is incorrectly defined or measured." It is almost always Performance, caused by an ideal cycle time set too high, meaning too slow. As a simple illustration: a line with a 50-second standard that runs a clean hour at 45 seconds a part reports Performance of about 111%. That is not a great hour. It is a bad ideal.
A padded ideal also erases two of the six losses. Minor stops and slow cycles are exactly what Performance is supposed to catch, and they vanish into the allowance.
The fix: set ideal cycle time from nameplate or a time study of the demonstrated best rate, per part family if the line runs a mix, and lock it. Do not re-baseline it downward when a machine ages. That drift is loss you want to see.
Leak 3: averaging lines as if they were the same size
The third leak happens at roll-up. A plant report takes each line's OEE and averages the percentages. A small line that runs well gets the same vote as a large one that struggles.
OEE.com recommends a weighted average for plant or multi-machine OEE, weighting by planned production time, or by value for high-impact assets. MPDV gives a quantity-weighted example: unit 1 at 65% OEE on 1,300 parts and unit 2 at 80% on 1,800 parts gives 2,285 / 3,100 = 73.7%.
MPDV adds a caveat that operators should take seriously. Weighting only applies to parallel or independent machines. For linked machines in series, per-station losses compound, so station OEEs multiply and the line figure drops. In practice that means you should measure line OEE at line output or at the constraint, not by averaging the stations on the line.
An illustrative plant with three lines shows how much the method matters:
| Line | OEE | Planned production time (h/week) | | --- | --- | --- | | Line A | 55.2% | 75 | | Line B | 85.0% | 20 | | Line C | 80.0% | 40 | | Simple average | 73.4% | | | Weighted by planned production time | 66.9% | 135 |
The weighted figure is 9,037.75 / 135 = 66.9%. The 20-hour line props up the simple average by more than six points, while the line carrying most of the schedule is the one that needs attention.
A worked example: one line, two OEE numbers
The following is a hypothetical line built to show the mechanics. It is not a plant we visited or measured.
The week: 10 shifts of 8 hours is 80 hours. Breaks take 5 hours, leaving 75 hours of planned production time. Changeovers take 8 hours, preventive maintenance 4 hours and unplanned stops 6 hours, so run time is 57 hours. The line makes 3,800 parts, of which 3,724 are good (98.0%). The routing standard is 50 seconds a part. The nameplate and demonstrated best rate is 40 seconds a part.
| | Reported version | Recalculated version | | --- | --- | --- | | Planned production time | 63 h (changeovers and PM removed) | 75 h (shift minus breaks) | | Cycle time used | 50 s routing standard | 40 s ideal | | Availability | 57 / 63 = 90.5% | 57 / 75 = 76.0% | | Performance | 3,800 × 50 s / 205,200 s = 92.6% | 3,800 × 40 s / 205,200 s = 74.1% | | Quality | 98.0% | 98.0% | | OEE | 82.1% | 55.2% | | Check (simplified formula) | 3,724 × 50 / 226,800 s | 3,724 × 40 / 270,000 s = 55.17% |
Same line, same week, same parts. Quality did not change at all. The entire 27-point difference comes from the denominator and the cycle time.
Turn the percentages into parts
Percentages invite debate. Parts do not. At the true ideal, 75 hours at 40 seconds a part is a theoretical 6,750 parts. The line shipped 3,724 good ones, a gap of 3,026 good parts a week.
The reported framing implies a theoretical output of 63 hours at 50 seconds, or 4,536 parts, and a gap of only 812. About 2,214 of the 3,026 lost parts, roughly 73%, do not exist in the reported number.
| Where the gap goes (parts/week) | Reported version | Recalculated version | | --- | --- | --- | | Availability loss | 432 (6 h unplanned at 50 s) | 1,620 (18 h at 40 s) | | Performance loss | 304 | 1,330 | | Quality loss | 76 | 76 | | Total gap | 812 | 3,026 |
Read the recalculated column as a work list. Changeovers and PM account for 12 of the 18 lost availability hours, which is a changeover and maintenance-planning problem, not a breakdown problem. Performance loss of 1,330 parts points at minor stops and slow cycles that the 50-second standard was absorbing. Scrap, the thing most quality meetings focus on, is the smallest bucket on this line.
To put a dollar figure on recovered hours, use the ManufacturingMag downtime cost calculator. It takes stopped hours per incident, saleable units per hour, contribution per unit, the share of output not recovered, incremental recovery cost and incidents per month, and it separates lost contribution from recovery cost such as overtime or expediting. On the example line the ideal rate is 90 parts an hour; plug in your own contribution margin rather than borrowing a number.
Zoom out to TEEP before you ask for capex
OEE measures how well you use the time you scheduled. It says nothing about the time you did not schedule. For that, OEE.com uses TEEP: TEEP = OEE × Utilization, where Utilization = Planned Production Time / All Time. In its own example, 80 scheduled hours out of 168 is 47.62% utilization, and 65% OEE times that gives 30.95% TEEP.

For the example line, utilization is 75 / 168 = 44.6%, and TEEP is 148,960 productive seconds out of 604,800 in the week, or 24.6%. Three-quarters of the calendar capacity on that asset is unused.
That changes the capex conversation. Before a request for a second machine, the questions run in order: is this line actually the constraint; how much of the 3,026-part gap can changeover and minor-stop work recover inside existing shifts; and what would an added shift, at its labor cost, do against a machine at its capital cost? Plant-average OEE answers none of those. Line-level TEEP at the constraint answers the first and frames the rest.
One caution on terms. The Federal Reserve's G.17 release of August 18, 2026 put manufacturing capacity utilization at 76.0% in July 2026, 2.2 points below its 1972 to 2025 average. That is a sector-wide economic estimate, not OEE or TEEP, and it should not be used as a benchmark for a single line.
Benchmarks without the myth
The 85% "world-class" target traces to Seiichi Nakajima's 1984 book Introduction to TPM (English edition 1988, Productivity Press). The commonly cited components are 90% availability, 95% performance and 99.9% quality, which multiply to about 85.4%. OEE.com's world-class OEE page calls 85% "a convenient, compelling and completely artificial benchmark." It says most manufacturers, even today, have OEE closer to 60%, and that it sees more companies below 45% than above 85%.
Machine-connected data points the same way. Evocon, which sells OEE monitoring software, analyzed more than 3,500 machines in over 50 countries using data from mid-2023 to mid-2024. Average OEE clustered around 55% to 60%. About 6% of organizations reported 85% or higher, and Evocon estimates the real share is closer to 3% after correcting calculation errors. It also notes that 90% on each of the three factors produces only 73% OEE.
The practical reading: a recalculated 55% is not a crisis. It is normal. An 82% built on a shrunken denominator is the number to worry about, because it tells the plant it has little left to find. Set targets as improvement against your own honest baseline, factor by factor.
A note on standards
ISO 22400-2:2014 standardizes key performance indicators for manufacturing operations management, including OEE (expressed as Availability × Effectiveness × Quality Ratio). A revision, ISO/DIS 22400-2, is in progress. Even the standard is not a settled reference: Schiraldi and Varisco, writing in Computers and Industrial Engineering (vol. 145, 2020), found that ISO 22400 versions diverge from each other and from Nakajima's original TPM formulation.
The lesson is not to wait for a perfect standard. Write your plant's definitions down, in one document, and lock them: what counts as planned production time, how ideal cycle time is set per part family, where scrap is counted, and how lines roll up. Comparisons between plants or across years only mean something when those rules hold still.
What to do on Monday
-
Audit the denominator. List every category currently treated as planned downtime. Anything other than breaks and time with no intent to produce, including changeovers, PM that displaces production and startup, goes back into planned production time.
-
Re-baseline ideal cycle times. Replace routing standards with nameplate or time-studied best rates. Flag any shift where Performance exceeded 100% as evidence the ideal is wrong.
-
Report the three factors separately. A single OEE percentage hides whether the problem is changeovers, minor stops or scrap. Show Availability, Performance and Quality alongside the lost parts in each.
-
Weight the roll-up. Use planned production time weighting for parallel lines. For linked stations, measure at line output or the constraint instead of averaging.
-
Convert the gap to parts, then to money. Translate each factor's loss into good parts a week, and price recovered hours with the downtime cost calculator, keeping lost contribution and recovery cost apart.
-
Add TEEP to every capex review. No request for new equipment should go forward without utilization and TEEP on the constraint asset.
-
Expect the number to fall, and say so in advance. Tell leadership before the recalculated figures appear. And be wary of tying OEE targets to pay or bonuses before the definitions are locked, since the three leaks above are also the easiest ways to game the score.
Related reading
-
If Boeing Engineers Strike, Who Signs Off on Supplier Deviations?
-
What Tier-3 Foundries Should Expect From the GE Castings Deal
Sources
-
OEE Calculation: Definitions, Formulas, and Examples, OEE.com (Vorne)
-
OEE FAQ, OEE.com (Vorne)
-
OEE Six Big Losses, OEE.com
-
World-Class OEE: Industry Benchmarks From 50+ Countries, Evocon (vendor data)
-
ISO 22400-2:2014, KPIs for manufacturing operations management, Part 2, ISO
-
G.17 Industrial Production and Capacity Utilization, Federal Reserve
-
Manufacturing Downtime Cost Calculator, ManufacturingMag
