What is OEE (Overall Equipment Effectiveness)?
Overall Equipment Effectiveness (OEE) measures how effectively a machine, line, or plant turns scheduled production time into saleable output. It combines availability, performance speed, and first-pass quality into a single percentage that links shop-floor losses directly to asset productivity, unit cost, and value creation.
Formula
Equivalently, when you combine the three components:
Example
A line is scheduled for 480 minutes with 60 minutes of unplanned downtime, so operating time is 420 minutes. The ideal cycle time is 45 seconds per unit, the line produces 540 units in total, and 525 of them are good.
Availability:
Performance:
Quality:
Overall Equipment Effectiveness:
An OEE of ~82% signals a strong but improvable asset: most planned time is productive, yet downtime and speed losses still represent hidden cost-of-capacity that depresses throughput, margins, and ultimately the firm’s return on invested capital.
How to Use the OEE Calculator
Enter your shift or batch data into the fields at the top, then use the results panel to see OEE, availability, performance, quality, and where you’re losing time, speed, or yield.
Gather your production data
- From your production report, collect planned production time (scheduled running minutes), unplanned downtime minutes, ideal cycle time per unit (seconds), total units produced, and good units that met spec.
Enter time-related fields
- Type the total scheduled running time for the period into Planned production time (min) and the sum of all unplanned stoppages into Unplanned downtime (min). Planned breaks or maintenance that are not meant to run should already be excluded from the planned time.
Add units and review the OEE calculation
- Fill Ideal cycle time per unit (seconds), Total units produced, and Good units; the calculator then computes availability, performance, quality, and overall OEE using and displays both the percentage and an “OEE level” band for quick interpretation.OEE = Availability × Performance × Quality
Interpret the loss breakdown
- Use the results table to look at operating time, ideal output at runtime, speed loss units, and scrap/rework units so you can see whether downtime, slow running, or quality is driving most of the loss.
Test improvement scenarios
- Adjust inputs like unplanned downtime, ideal cycle time, or scrap to simulate improvement ideas (e.g., faster changeovers, better process stability) and see how much each change would move OEE before you commit resources on the shop floor.
Frequently Asked Questions
What inputs do I need to use the OEE Calculator correctly?
Enter the planned production time in minutes for the shift, the unplanned downtime in minutes (breakdowns, changeovers, stoppages), the ideal cycle time per unit in seconds (best-case speed), total units produced, and good units that passed quality on the first try. The calculator uses these to derive availability, performance, quality, and overall OEE.
How does this calculator actually compute OEE from my data?
It first finds operating time as
, then availability as
, performance from speed losses, and quality as
; finally it multiplies these factors to get
and shows the result as a percentage.
What is a “good” OEE score and how should I read the result?
Many factories sit in the 60–80% range, while scores around 85% are often treated as “world-class”, though realistic targets depend heavily on your industry and asset base.: Use the OEE level label (e.g., Typical, Excellent) as a rough benchmark and focus on improving your own trend over time rather than chasing a single magic number.
Why do I sometimes see performance above 100% or an OEE that feels unrealistic?
That usually means one or more inputs are off—most often the ideal cycle time is set too slow, planned production time includes breaks where the line is not supposed to run, or “good units” includes reworked product. Tighten your definitions (true best-case cycle time, shift time the line is expected to run, only first-pass good units) so the calculator reflects real losses instead of data noise.
Sources & Methodology