OEE Calculator
Calculate Overall Equipment Effectiveness as Availability × Performance × Quality. Enter one production period to see the factors separately—and check the data before drawing conclusions.
How is OEE calculated?
Multiply the three unrounded ratios. This calculator keeps minutes and seconds explicit, and displays the resulting percentages to one decimal place.
- 1. Runtime
- planned production minutes − downtime minutes
- 2. Availability
- runtime minutes ÷ planned production minutes
- 3. Performance
- (ideal cycle seconds/unit × total units) ÷ (runtime minutes × 60)
- The × 60 converts runtime to seconds. A value above 100% triggers a data-check warning; it is not silently capped.
- 4. Quality
- good units ÷ total units
- For zero output, this tool displays 0 by convention rather than treating the ratio as a measured yield.
- 5. Overall Equipment Effectiveness
- Availability × Performance × Quality
- Use ratios, not the already rounded displayed percentages. Multiply by 100 to express the result as a percentage.
- Cross-check when runtime and output are positive
- (ideal cycle seconds/unit × good units) ÷ (planned production minutes × 60)
- This gives the same OEE ratio but does not expose the three factors separately.
Definition reference: Vorne’s OEE calculation guide ↗. Calculator-specific zero-output and validation rules are stated on this page.
What do the example inputs produce?
480 planned production minutes, 60 downtime minutes, a 1.2-second ideal cycle, 12,000 total units and 11,500 first-pass good units.
The 480 minutes are already planned production time—not a shift length from which breaks still need to be subtracted. This example is not a performance benchmark.
| Runtime | 480 − 60 = 420 minutes |
|---|---|
| Availability | 420 ÷ 480 = 87.5% |
| Performance | (1.2 × 12,000) ÷ (420 × 60) = 57.1% |
| Quality | 11,500 ÷ 12,000 = 95.8% |
| OEE | Unrounded A × P × Q = 47.9% |
| Direct cross-check | (1.2 × 11,500) ÷ (480 × 60) = 47.9% |
The displayed ratios are rounded for readability; multiplication uses their full precision.
Assumptions & limitations
The tool measures the period and process you define. It does not verify your production records, choose an ideal cycle or establish an improvement business case.
- One period, one compatible cycle basis. Time, counts and cycle reference must describe the same operation. Different product cycle times need a suitable product-specific or weighted model; this tool has one cycle-time input.
- No silent count or time correction. Good count above total count, downtime above planned time, and positive output with zero runtime are rejected. The previous estimate remains visible with an explicit warning until corrected.
- Above 100% means check the data. Review unit conversion, counts and the ideal-cycle reference. The calculated value remains visible; do not use it as an efficiency claim.
- No-output Quality is not measured. With zero output, Performance, Quality and OEE display 0 by convention. Availability still follows the entered time, and the page avoids a misleading quality-loss recommendation.
- Lowest factor is not guaranteed fastest payback. It does not rank lost minutes, financial impact or project feasibility. Investigate the underlying causes and operational constraint before choosing an improvement.
- No universal target is applied. Defaults are illustrative. Compare periods only when the input boundaries and counting rules are compatible.
Further definitions: Vorne’s OEE FAQ ↗, including planned-time boundaries and first-pass quality.
OEE calculator FAQs
Check the definitions before comparing shifts, products or machines.
How is OEE calculated?
OEE is Availability × Performance × Quality. This tool uses runtime divided by planned production time, ideal cycle seconds multiplied by total units divided by runtime seconds, and good units divided by total units. It multiplies the unrounded ratios and displays percentages to one decimal place.
What belongs in planned production time and downtime?
Use the period intended for production, excluding time when production was not scheduled. Enter stops that occurred inside that period, including changeovers if production was intended. Do not exclude a stop from planned time and subtract it again as downtime. Apply one consistent boundary to all inputs.
What counts as a good unit?
For the OEE quality factor, count units accepted on their first pass, without rework. Total count includes all produced units for the same period and process. Do not mix first-pass good counts with eventual acceptance after rework or counts from another shift.
Why can Performance exceed 100%?
The entered ideal cycle time, unit counts or time basis may be inconsistent. This tool shows the calculated value and a warning instead of hiding the issue by capping it. Check seconds versus minutes, parts per cycle, product mix and the cycle-time reference before interpreting the OEE result.
What happens when no units were produced?
With total count and good count both zero, this tool displays Performance, Quality and OEE as 0.0% by convention. Quality has no measured denominator in that case; it does not mean every unit was rejected. Availability is still calculated from the entered time. Positive output with zero runtime is rejected.
Does the lowest factor tell me the best improvement project?
No. The lowest factor is a prompt to investigate its underlying losses, not a cost, payback or constraint-based priority ranking. Use stop reasons, cycle data and defects alongside throughput, delivery risk and practical improvement options. Example inputs and results are not industry benchmarks.