OEE measures how well you run during scheduled production time. OOE (overall operations effectiveness) uses a wider time base, such as the staffed window or the whole calendar. The name has no single standard definition, so always check which time base a report uses before you compare numbers.
OEE and OOE in one minute
OEE is defined on scheduled time, the time you planned to make product. In Overall Equipment Effectiveness (R. C. Hansen, 2001): OEE = good units ÷ ideal rate ÷ scheduled time.
OOE is a newer name, and it is less settled. Hansen's book is built on three other measures: OEE (scheduled time), TEEP (calendar time) and asset utilization (running time over calendar time).
Different sources define OOE differently. All of them divide by a time base that is wider than OEE's. They do not agree on how wide.
What the sources say
- Whole calendar. Tractian, a maintenance-software vendor, defines OOE in its vendor glossary (Tractian) as OEE × utilization, with utilization measured against the full calendar. That is the same idea as TEEP.
- Operating time. Teeptrak, an OEE-software vendor, puts OOE between the two on its vendor comparison page (Teeptrak): wider than OEE, narrower than TEEP. It uses operating time and leaves out time that was left unscheduled on purpose.
- Name. Shoplogix, a production-monitoring vendor, notes in its vendor guide (Shoplogix) that the acronym is spelled out in more than one way.
These are vendors' own definitions, not standards, and we cite them only to show that the definitions differ. The lesson is simple: a number called OOE is meaningless until you know its denominator.
Same output, three time bases
Example: a plant runs two 8-hour shifts a day. Of the 1,440 minutes in the day, the staffed window is 960 minutes. Planned breaks and meetings are 60 minutes, which leaves 900 minutes of scheduled production time. The line makes good units worth 630 minutes at its ideal rate.
| Time base | Minutes | Calculation | Result |
|---|---|---|---|
| Scheduled time (OEE) | 900 | 630 ÷ 900 | 70.0% |
| Staffed window (one OOE reading) | 960 | 630 ÷ 960 | 65.6% |
| Whole calendar (TEEP, or OOE on all time) | 1,440 | 630 ÷ 1,440 | 43.8% |
Check the calendar row another way. OEE 70% × (900 ÷ 1,440 = 62.5%) = 43.75%, which rounds to 43.8%. That is the "OEE × utilization" form.
Nothing about the line changed between the rows. Only the denominator moved. This is why a plant that switches from OEE to OOE sees its score "fall" overnight.
Where the 900 minutes go inside OEE
OEE is more than one number. It also shows the losses inside the scheduled time. For the same example, the 900 scheduled minutes split like this:
| Part of the 900 scheduled minutes | Minutes | Share |
|---|---|---|
| Good output at the ideal rate (OEE) | 630 | 70.0% |
| Stops | 135 | 15.0% |
| Slow running | 90 | 10.0% |
| Bad units | 45 | 5.0% |
| Total | 900 | 100.0% |
Hansen's rule is that OEE plus all loss percentages equals 100% of scheduled time. A wider time base such as OOE or TEEP adds the unscheduled minutes on top, but the loss inside the schedule stays the same. This is why the loss breakdown, not the headline number, is what you work on.
Why the choice matters when the schedule changes
Take the same plant and add a third shift. The new shift is scheduled for 450 minutes and runs at the same 70% OEE, so it adds 315 minutes of good output.
OEE did not move, because the line runs the same way. The calendar-based figure jumped from 43.8% to 65.6%, because more of the clock is now used. A staffed-window OOE would stay at 65.6%, because the staffed window grows with the shift. So the three numbers answer three questions.
If a manager asks "did we improve?" and the answer depends on which of these you report, you need to say which one you mean. OEE tells you about running. TEEP tells you about using the clock.
Which one answers which question
| Question | Use |
|---|---|
| How well do we run when we plan to run? | OEE, on scheduled time |
| Where do the minutes go inside the shift? | OEE with its loss breakdown |
| How much of the asset's total potential do we use? | TEEP, on calendar time |
| Do we need a new line or more shifts? | TEEP first, then OEE of the bottleneck |
Hansen's own line is that OEE ignores planned downtime, and that TEEP brings the planned activities into focus: shutdowns, preventive maintenance, training, staffing gaps and headroom. If your OOE is meant to do that job, call it TEEP, or write its time base next to it.
Mix-ups to watch for
- Calling OEE "OOE" by habit. Some teams use the two names for the same number. Ask for the formula, not the label.
- Treating a lower OOE as a worse line. It may only be a wider time base, as in the example above.
- Using OOE to excuse planned time. Planned stops are not free. Hansen ranks planned downtime below effective runtime in value, because it sustains the status quo and makes no product. Excluding it from OEE is a rule, not a reason to stop looking at it.
- Comparing plants. Two sites with different shift patterns will show very different calendar-based numbers for the same line performance.
How to label it so nobody is confused
- Put the denominator in the title. "OOE, staffed hours" or "OEE, scheduled time".
- Never mix bases in one trend line. If the definition changes, mark the change on the chart.
- Keep OEE as the improvement number. It is the one that moves when you remove a stop or a slow cycle. OOE and TEEP also move when you change the schedule.
- Do not compare your OOE with an OEE benchmark. The bar for OEE is set on scheduled time.
For the data behind scheduled time and what may be excluded, see how to calculate OEE and OEE calculation mistakes. To calculate the calendar version yourself, use the TEEP calculator or how to calculate TEEP.
The 85% world-class bar for discrete and batch processes comes from Overall Equipment Effectiveness (R. C. Hansen, 2001), building on Nakajima's TPM figures, and it is set on scheduled time. Do not hold an OOE figure against it. To judge your own number, read is 85% OEE realistic.
For more context on comparing plants, see the OEE benchmark report.
Whatever name your reports use, the time base must be clear. Fabrico shows OEE per line and shift, so the scheduled time behind each number is visible next to it. See OEE per line and shift in Fabrico.
What people ask next
What does OOE stand for?
Overall Operations Effectiveness in most sources. Some write Overall Operational Effectiveness or Overall Operations Efficiency. The acronym is not standardised, which is why the definition matters more than the name.
Is OOE the same as TEEP?
Only if OOE is defined on all calendar time. Then it matches TEEP: good output at the ideal rate divided by the full calendar. If your OOE uses staffed hours instead, it sits between OEE and TEEP. Read OEE vs TEEP.
Which one should I report?
Use OEE to improve how you run when you plan to run. Use TEEP when you decide about capacity or new equipment. If your company reports OOE, label the time base in the title of the chart.
Does OOE include planned downtime?
Usually yes. A wider time base brings time planned as not for production, such as maintenance shutdowns planned ahead and unscheduled shifts, into the denominator. Changeovers are different: in Hansen's method they are already a loss inside OEE. See planned vs unplanned downtime.
Why is my OOE lower than my OEE?
Because the same good output is divided by more time. The line did not run worse. See the worked example above, and utilization vs OEE for the same effect from another side.
Related guides: OEE vs OPE: Why the Two Numbers Disagree · Manufacturing KPI Formulas: A Full Cheat Sheet