Skip to content

Main content

OEE Availability Performance Quality One Factor Tool

OEE factorization with explicit ideal cycle time; performance above one remains visible if the supplied ideal cycle is inconsistent.

Loading tool…

Description

Compute availability = run/planned minutes, performance = idealCycleMinutes × totalUnits/runMinutes, and quality = goodUnits/totalUnits.

Production yields distinguish first-pass output, accepted rework, and final good units. Expected fractions, observed counts, and reporting bases should remain explicit.

Compute availability = run/planned minutes, performance = idealCycleMinutes × totalUnits/runMinutes, and quality = goodUnits/totalUnits.

When to use this tool

Use OEE Availability Performance Quality One Factor when you need one supplied yield, rework, or effectiveness component.

How to use the tool and how it works

  1. Enter plannedMinutes, runMinutes, totalUnits, goodUnits, idealCycleMinutes. Use the units and conventions below.
  2. Run the tool. Correct any format, range, or cross-field input error before interpreting the output.
  3. Read availability, performance, quality, oee. Use the output convention below.

Compute availability = run/planned minutes, performance = idealCycleMinutes × totalUnits/runMinutes, and quality = goodUnits/totalUnits. Return idealCycleMinutes × goodUnits/plannedMinutes as oee.1

Input fieldMeaning and unitsAccepted input
plannedMinutesPlanned MinutesRequired. Finite number; strictly above 0.
runMinutesRun MinutesRequired. Finite number; strictly above 0.
totalUnitsTotal UnitsRequired. Safe integer; minimum 1.
goodUnitsGood UnitsRequired. Safe integer; minimum 0.
idealCycleMinutesIdeal Cycle MinutesRequired. Finite number; minimum 0.
Output fieldInterpretationReturned shape
availabilityAvailabilityRequired. Finite number.
performancePerformanceRequired. Finite number.
qualityQualityRequired. Finite number.
oeeIdeal-cycle good-unit time divided by planned time; not capped at one.Required. Finite number.
json
{
  "input": {
    "plannedMinutes": 480,
    "runMinutes": 400,
    "totalUnits": 1000,
    "goodUnits": 950,
    "idealCycleMinutes": 0.3
  },
  "output": {
    "availability": 0.8333333333333334,
    "performance": 0.75,
    "quality": 0.95,
    "oee": 0.59375
  }
}

Limitations and assumptions

  • Performance and OEE are not capped at one; the time and ideal-cycle conventions are supplied and no industry reporting or equipment safety standard is validated.
  • Inputs must satisfy both the field types and the cross-field conditions above. Invalid input causes an error; a successful false flag or documented placeholder is a different result.
  • Numeric calculations use binary floating point unless exact decimal-integer arithmetic is explicitly stated. No hidden measurement tolerance or decimal rounding is added; nonfinite or out-of-contract results are rejected. Numeric signed-zero results are exported as zero.

Alternative or Complementary methods

Review process records and the relevant quality and time-accounting definitions before comparing production performance.

References

  1. Calculation and input contract: industrial-engineering/oee-availability-performance-quality-one-factor — tool.io

Similar or alternative tools