OEE Production Loss Breakdown

How to use OEE Production Loss Breakdown

Availability uses run time over planned minutes, performance uses ideal production seconds over run seconds, and quality uses good over total units. Their product is checked through fully productive time, with inconsistent faster-than-ideal input refused.

1. Enter model json (schema and units below).
2. Choose the stated convention and check the units and supported model.
3. Calculate, inspect the result, then copy or download it.

Good to know

• Plain decimal JSON numbers or strings, at most six fractional places, magnitude at most 1,000,000,000; raw numeric spellings and duplicate object members are checked. Exact rational arithmetic is capped at 8,192 bits. Text is at most 30,000 characters; a local JSON download preserves exact fractions or full stored approximate numbers. Planned/run minutes and ideal cycle seconds must be positive; stop time is lower than planned time. Whole total count 1–1,000,000,000 and good count 0–total. One consistent production run only; no benchmark, bottleneck diagnosis or operating recommendation.
• Local calculation only; no input persistence or external lookup. Text/JSON is limited to 30000 characters and output to 1000000 characters. Numeric model inputs and precision/work limits are stated on this page. Approximate JSON numbers retain full stored values; exact arithmetic outputs retain decimal or fraction strings. Unsupported states fail explicitly.
• Educational user-assumption arithmetic only. No live prices, laws, tax rules, quotes or financial advice.