Production worked example

OEE with planned production time of 1,200 min: a worked example

This scenario runs the oee calculation on the strong side: planned production time of 1,200 min, with every other input held at its documented default. Use when a machine or line needs a reliable effectiveness score.

The inputs for this scenario

  • Planned production time: 1,200 min (raised for this scenario; the documented default is 480)
  • Downtime: 55 min (unchanged)
  • Ideal cycle time: 20 sec / unit (unchanged)
  • Total count: 1,180 units (unchanged)
  • Good count: 1,125 units (unchanged)

Working through the calculation

  • Applying the documented formula (Availability = run time รท planned time) to the inputs above produces each figure below.
  • At this operating point the engine returns 31.25 % for oee, the number this scenario is built around.
  • At this operating point the engine returns 95.42 % for availability.
  • At this operating point the engine returns 34.35 % for performance.
  • At this operating point the engine returns 95.34 % for quality.

How this compares with the baseline

  • Against the tool's baseline example, where planned production time sits at 480 min and the headline result is 78.12 %, this scenario comes in 60% below the baseline at 31.25 %.
  • Use it at the end of a shift, run, or day to score how much of your scheduled time produced good parts and to isolate which loss bucket is hurting most. Treat this as a target state: the delta against the baseline quantifies what the improvement is worth before you commit to chasing it.

Results at a glance

  • OEE: 31.25 % (headline result)
  • Availability: 95.42 %
  • Performance: 34.35 %
  • Quality: 95.34 %

Run it with your numbers

  • Every input above is editable in the live OEE calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.