E•ENGINEERING
DESK TOOLS
All guides
Maintenance5 min readUpdated 5 October 2026

OEE calculation: check availability, performance and quality

Prepare consistent production-time and count data, calculate the three OEE factors and investigate results above 100 percent.

What OEE measures

Overall equipment effectiveness (OEE) expresses how much of the planned production time produced good product at the ideal rate. It multiplies three factors: availability (was the machine running), performance (was it running at the ideal speed) and quality (was the output good). Because they are multiplied, three factors that each look acceptable can still produce a modest total, and any loss counted twice or omitted corrupts every later conclusion. The method works only if time and counts are defined before the first shift is recorded.

The standard factor definitions also assume a clear planned production time. Time with no production planned, such as no orders or a scheduled holiday, is normally excluded from that denominator; if it is included instead, the figure is better described as a utilisation measure and should not be compared with OEE from other sites.

The three factors and the formula

  • Availability = run time ÷ planned production time
  • Performance = (ideal cycle time × total count) ÷ run time
  • Quality = good count ÷ total count
  • OEE = Availability × Performance × Quality

Run time is planned production time minus stop time. The OEE calculator multiplies the three percentages you enter; it does not derive them from raw counts, so calculate each factor first. Its inputs are limited to 0–100 %, which means a performance figure above 100 % cannot be entered. That is intentional, because it signals a data problem, not a good shift. A useful identity: OEE equals ideal cycle time × good count ÷ planned production time.

Worked example 1: one shift

A packaging line has 480 min of planned production time. Recorded stops (breakdowns, changeover and jams) total 47 min, so run time is 433 min. The ideal cycle time is 0.5 min per unit. The line counts 760 units, of which 722 pass inspection.

FactorCalculationResult
Availability433 ÷ 48090.21 %
Performance0.5 × 760 ÷ 43387.76 %
Quality722 ÷ 76095.00 %
OEE0.9021 × 0.8776 × 0.9575.21 %

The check identity agrees: 0.5 × 722 ÷ 480 = 75.21 %. Rounding matters slightly. Entering 90.2, 87.8 and 95 into the calculator gives 75.24 %, so carry full precision from a spreadsheet when possible.

Where the losses went: 47 min of stops cost 9.79 points of availability, running below the ideal rate cost further time, and 38 rejected units removed 5 percent of output. Each can be assigned to an action owner.

Worked example 2: a second line, and performance above 100 percent

A second line has 450 min planned, 396 min run, an ideal cycle time of 0.8 min, 460 units counted and 437 good. Availability = 396 ÷ 450 = 88.00 %. Performance = 0.8 × 460 ÷ 396 = 92.93 %. Quality = 437 ÷ 460 = 95.00 %. OEE = 77.69 %.

Now return to the first line and suppose the count were 900 units instead of 760: performance = 0.5 × 900 ÷ 433 = 103.93 %. That cannot happen if the ideal cycle time is truly the fastest sustained rate and the count belongs to the same run time. Likely causes are an ideal cycle time that is too slow, a count that includes rework or units from another period, stop time that was over-recorded, or a unit mismatch such as pieces versus cartons. Do not cap it at 100 %. Find the cause.

Keep time and counting units aligned

Use one time unit throughout; minutes and hours mixed in one calculation is a classic error. State the ideal cycle time as time per counted unit, not units per hour, or convert deliberately: 120 units per hour is 0.5 min per unit, while a wrongly assumed 100 units per hour (0.6 min) would raise the first line's performance from 87.76 % to 105.31 %. Count at a consistent point, and use the same unit for total and good count. Decide whether reworked units count as good (most definitions say only first-pass good units do) and whether planned stops such as scheduled breaks sit outside planned production time. Write both decisions on the sheet.

Common mistakes

  • Using calendar time as the denominator when the plan is only one shift.
  • Choosing the ideal cycle time from average demonstrated speed, which hides speed loss.
  • Counting start-up scrap or reworked units as good.
  • Counting a micro-stop as run time in one report and as a stop in another.
  • Averaging OEE percentages across lines with different planned time instead of summing time and counts.
  • Comparing OEE across products or sites with different ideal-rate rules.
  • Using the total as the only number, so the losses are not visible.

Read the three factors alongside the total

The product can be identical for different problems. An OEE of 75 % made of 90 / 88 / 95 points to speed and scrap as much as downtime. Review each factor against its loss category: availability against breakdowns, setup and waiting; performance against slow cycles and minor stops; quality against scrap and rework. Pairing the availability factor with an MTBF and MTTR view from the breakdown log guide shows whether the lost time comes from frequent short stops or a few long ones.

FAQ

What is a good OEE?

It depends on process, product mix and definitions. Trend your own line using stable definitions rather than comparing with an outside figure.

Should planned maintenance count as a loss?

That is a policy choice. Document it, because it changes availability.

Why does quality use units, not time?

Quality is a ratio of counts. Time is only converted through the ideal cycle time.

Can I calculate OEE for a whole plant?

Sum planned time, run time and counts across lines before dividing, and keep the line detail beside it.

Checks before you trust the result, and recording the data

Checks. Planned time minus stop time must equal run time. Good count must not exceed total count. Performance should not exceed 100 %. Recompute with the identity above. Confirm the same shift window was used for time, stops and counts.

Records. For each shift keep the line, product, planned time, each stop with start, end and reason, ideal cycle time with its source, total count and reject count. The free breakdown log template on the site can hold the stop events, and its totals by reason give the availability losses directly.

Try it with the calculators

Free Excel templateBreakdown & downtime log: blank records, dropdowns and a live dashboard.
Download .xlsx

Browse all Excel templates and dashboard previews

References