Blog · Finance metrics and formulas · Manufacturing
Calculate overall operations effectiveness using an explicit operating-time denominator. Reconcile scheduled exclusions, production losses and good output, then compare OOE with OEE on the same records.
Overall operations effectiveness (OOE) measures good output at the ideal production speed against a defined operating-time window. It includes unscheduled time inside that window, whereas OEE measures performance against planned production time. The calculation is useful only when the report states exactly which hours, breaks and planned downtime belong in each denominator.
OOE = Good units × Ideal cycle minutes per unit / Operating-window minutes
Equivalent form: Operating availability × Performance × Quality
Operating availability = Run minutes / Operating-window minutes
Performance remains ideal cycle time multiplied by total units, divided by run time. Quality remains good units divided by total units. The broader availability denominator is what changes.
An explanation of OEE, OOE and TEEP distinguishes OOE's total operations time from OEE's scheduled time and TEEP's all-time denominator. Covirage is not affiliated with MachineMetrics.
Because the words operating time can also mean actual run time in a local report, write operating window and run time as separate columns. Dividing by actual run time would remove downtime from the denominator and answer a different question.
For the narrower equipment calculation, see overall equipment effectiveness. Keep that measure intact instead of relabeling an OOE result as OEE.
Consider a US components plant on October 22, 2026. Management defines the line's open operating window as 480 minutes. Its OOE policy retains temporary breaks, no-order intervals and maintenance inside that window. Hours outside the open window are excluded; this is a stated reporting convention, not a claim that every plant uses identical exclusions.
The production schedule excludes several intervals from planned production. Once production is planned, however, interruptions such as changeovers stay within that planned time. The OEE calculation method includes planned stops such as changeovers among the stops that reduce run time.
| Schedule or downtime record | Minutes | Treatment |
|---|---|---|
| Open operating window | 480 | OOE denominator |
| Scheduled break | 30 | Inside operating window; outside planned production |
| No orders scheduled | 60 | Inside operating window; outside planned production |
| Scheduled maintenance | 30 | Inside operating window; outside planned production |
| Planned production | 360 | 480 − 30 − 60 − 30 |
| Breakdown during planned production | 30 | Stop within planned production |
| Changeover during planned production | 20 | Stop within planned production |
| Material wait during planned production | 10 | Stop within planned production |
| Run time | 300 | 360 − 30 − 20 − 10 |
These are mutually exclusive intervals. A breakdown that overlaps maintenance must not be subtracted twice. The planner owns the approved schedule; the production supervisor owns the stop log; the analyst checks timestamps and boundaries before calculating percentages.
The production file adds the following inputs for that exact window:
| Production input | Value |
|---|---|
| Ideal cycle minutes per unit | 0.50 |
| Total completed units | 540 |
| Good units | 513 |
| Rejected units: total − good | 27 |
| Fully productive minutes: good × ideal cycle | 256.50 |
Keep the product code and standard revision with the ideal cycle time. For different products, compute ideal minutes on each product row and then sum them. Raw counts from products with different speeds cannot safely share one cycle standard.
Calculations use unrounded inputs. Percentages are displayed to two decimal places.
| Factor | OEE calculation | OEE basis | OOE calculation | OOE basis |
|---|---|---|---|---|
| Availability | 300 / 360 | 83.33% | 300 / 480 | 62.50% |
| Performance | 540 × 0.50 / 300 | 90.00% | Same production rows | 90.00% |
| Quality | 513 / 540 | 95.00% | Same quality rows | 95.00% |
| Combined result | Availability × performance × quality | 71.25% | Availability × performance × quality | 53.44% |
| Direct check | 256.50 / 360 | 71.25% | 256.50 / 480 | 53.44% |
The line converted 256.50 minutes of the operating window into good production at ideal speed. OOE is therefore 53.44%. The higher OEE does not describe another line or more output; it uses the smaller scheduled-production denominator.
The identity is:
OOE = OEE × Planned production minutes / Operating-window minutes
Here, 71.25% × (360 / 480) = 71.25% × 75.00% = 53.44% after rounding. If that identity fails, investigate mismatched time windows, cycle standards or quality counts.
For a connected line, make sure output is counted once at the final inspection boundary. Overall line efficiency explains why station counts and the line's bottleneck standard require their own boundary rules.
An operations review needs to explain the gap, not just present a percentage. Convert each production loss to ideal minutes:
| Operating-window bucket | Calculation | Minutes |
|---|---|---|
| Outside planned production | 30 + 60 + 30 | 120.00 |
| Stops within planned production | 30 + 20 + 10 | 60.00 |
| Speed losses | 300 − 540 × 0.50 | 30.00 |
| Quality losses | 27 × 0.50 | 13.50 |
| Fully productive time | 513 × 0.50 | 256.50 |
| Total operating window | Sum of the five buckets | 480.00 |
The sum proves that no time disappeared between the schedule and the result. A downtime review can then break the stop bucket into causes, while the planner separately investigates why available operating time was left outside the production plan.
That distinction changes the decision. No-order time calls for demand and scheduling review. Breakdown time calls for maintenance evidence. Rejects call for quality investigation. The combined percentage alone cannot tell management whether additional equipment is justified.
Suppose the planner reclassifies the same 60-minute no-order interval as scheduled production, with no additional run time or output. This is a reporting variation, not an improvement scenario.
| Measure | Original classification | Revised classification |
|---|---|---|
| Operating-window minutes | 480 | 480 |
| Planned production minutes | 360 | 420 |
| Fully productive minutes | 256.50 | 256.50 |
| OEE | 71.25% | 61.07% |
| OOE | 53.44% | 53.44% |
OOE stays constant because its numerator and denominator did not change. OEE falls because the same output is compared with a larger production plan. Preserve the approved classification and explain any restatement before interpreting a trend.
Bring the operating calendar, shift schedule, downtime export and accepted production counts with their cycle standards. Covirage maps the columns, and its tools compute OOE and OEE and check the time reconciliation; the external AI model explains the result with every figure traced to its rows. Create a free Covirage account in about a minute, then set up your business and bring a sample of your own data.
See how those comparisons support capacity planning.
OEE uses planned production time. OOE uses a broader defined operating window that includes unscheduled time within it. Both use the same good output and ideal cycle standard, so their different percentages can reflect scheduling exclusions rather than different machine performance.
No. Its denominator is the documented operating window, such as the hours a plant is open for operations. Total effective equipment performance uses all calendar time instead. A report must state the operating calendar rather than leaving the reader to assume it.
Maintenance inside the defined operating window remains in the OOE denominator under the policy used here, even if production was not scheduled for that interval. Maintenance outside that window does not. Keep the calendar policy consistent and disclose it beside the result.