Sumivo · Manufacturing

OEE Calculator

Calculate Overall Equipment Effectiveness from availability, performance, and quality.

01 / inputs

%
%
%

02 / result

OVERALL EQUIPMENT EFFECTIVENESS

84.645%

OEE
84.645%
Input factors
Availability × performance × quality

Calculation trace

  1. (90 ÷ 100) × (95 ÷ 100) × (99 ÷ 100) × 100 = 84.645%
    84.645 %
    Overall equipment effectiveness

Maintained by Jack Shi

§

How it works

Combine three already-calculated factors into Overall Equipment Effectiveness (OEE). Enter availability, performance and quality as percentages. OEE (%) = (availability ÷ 100) × (performance ÷ 100) × (quality ÷ 100) × 100. The tool multiplies the fractions; it does not average the percentages.

Assumptions & limits

  • Each factor must be a finite percentage from 0 to 100 inclusive; decimal percentages are accepted. Enter 90 for 90%, not 0.90. Empty fields are rejected rather than treated as a zero factor.
  • Use factors for the same equipment, measurement period and counting basis. This page takes the factors as inputs; it does not calculate them from downtime, ideal cycle time, output counts or rejects.
  • The result is between 0% and 100%. A performance input above 100% is rejected rather than capped. The tool does not assign a benchmark, grade or improvement target.

Verified runs

Synthetic examples executed at build revision 24533ff on . Cards round decimal results to 6 significant figures; matching uses full precision and the tolerance below. Matches cover the displayed fields, not every possible input or clinical or engineering validation.

  • Inputs: Availability: 90 %; Performance: 95 %; Quality: 99 %

    Result: OEE: 84.645 % (expected OEE: 84.645 %) ✓

  • Inputs: Availability: 0 %; Performance: 100 %; Quality: 100 %

    Result: OEE: 0 % (expected OEE: 0 %) ✓

  • Inputs: Availability: 80 %; Performance: 90 %; Quality: 95 %

    Result: OEE: 68.4 % (expected OEE: 68.4 %) ✓

How these runs were checked

Method: oee@1.0.0. Expectations come from the listed test fixtures or hand arithmetic; they are not copied from these executions. Omitted optional inputs use the method defaults. Run dates record execution, not expert review or fresh measurements.

Download all verified runs (JSON) — full inputs, returned values, expectations, timestamps and buildRevision.

  • normal: . Absolute tolerance: 0.0005. Text and booleans match exactly. Full-precision result: OEE: 84.645 %. Expected: OEE: 84.645 %. Expectation: packages/calculator-core/tests/oee.test.ts
  • boundary: . Absolute tolerance: 1e-10. Text and booleans match exactly. Full-precision result: OEE: 0 %. Expected: OEE: 0 %. Expectation: packages/calculator-core/tests/oee.test.ts
  • sensitivity: . Absolute tolerance: 1e-10. Text and booleans match exactly. Full-precision result: OEE: 68.4 %. Expected: OEE: 68.4 %. Expectation: packages/calculator-core/tests/oee.test.ts

Reproduce from the source checkout with pnpm --filter @sumivo/web gen:verified-runs. A rebuild changes execution times; the revision identifies its Git starting point, including any uncommitted changes made for that build.

§

Synthetic example

Availability 80%, performance 90% and quality 95%.

  1. Convert percentages to fractions: 80 ÷ 100 = 0.8, 90 ÷ 100 = 0.9, and 95 ÷ 100 = 0.95.
  2. Multiply: 0.8 × 0.9 = 0.72; 0.72 × 0.95 = 0.684.
  3. Convert back to a percentage: 0.684 × 100 = 68.4%.

OEE = 68.4%. The arithmetic average of the three inputs is not this result.

§

Boundary case

Availability 0%, performance 90% and quality 95% give a valid 0% OEE: any zero factor makes the product zero. Performance 101% instead gives an error and no result. Exactly 100% is accepted for every factor.

§

How to read the result

The result is the combined fraction represented by all three factors. In the example, that fraction is 0.684. Multiplying fractions means OEE cannot exceed the smallest entered percentage. Use the individual factors to see what you supplied; OEE alone does not identify the cause of a loss or say whether performance meets your own target.

§

Sources and what they support

Input ranges, the absence of raw production-data inputs and the absence of benchmark grading describe this implementation. Keep the measurement basis consistent when supplying factors; this tool does not check that basis.

§

FAQ

Why is the result below all three inputs?
Each percentage is converted to a fraction no larger than 1. Multiplication by the other two fractions can only keep or reduce that fraction, so the combined percentage is no larger than the smallest factor.
§

Related calculators

§

SOURCES