OEE Calculator

Overall Equipment Effectiveness = Availability × Performance × Quality. Deterministic, 100% client-side, nothing uploaded.

Inputs
Results
Availability
Performance
Quality
Run time
Downtime loss
Speed loss
Quality loss

Benchmark: ~85% is world-class, ~60% is typical for discrete manufacturing. Performance is capped at 100% (check cycle time if it exceeds).

About the OEE Calculator (Availability x Performance x Quality)

Measuring manufacturing productivity requires tracking equipment availability, performance, and output quality. An OEE calculator simplifies this by multiplying these three factors to reveal true production efficiency. Operations managers and continuous improvement teams use this metric to identify bottlenecks, reduce downtime, and systematically address the six big losses affecting production line profitability.

How it works

  1. Enter the total planned production time and any planned downtime.
  2. Input the operating time and actual run rate.
  3. Record the total number of parts produced and the number of defective parts.
  4. Review your final OEE percentage alongside the TEEP breakdown.

Frequently asked questions

What is a good benchmark score for OEE?

World-class manufacturing operations typically target an Overall Equipment Effectiveness score of 85%. However, many standard manufacturing plants operate closer to 60%.

How do the six big losses factor into this calculation?

The six big losses—breakdowns, setup/adjustments, small stops, reduced speed, startup rejects, and production rejects—are categorized into availability, performance, and quality losses.

What is the difference between OEE and TEEP?

OEE measures efficiency during planned production time, while Total Effective Equipment Performance (TEEP) measures efficiency against all calendar hours, including unscheduled time.

Why did my performance score exceed 100%?

A performance score over 100% usually means the ideal cycle time entered is slower than the machine's actual capability, or there was a data entry error in the run rate.

References