OEE Calculator
Enter the five raw inputs and get availability, performance, quality, and OEE — the same arithmetic as the worked example in the OEE guide. Nothing is sent anywhere; the math runs in your browser.
Sanity check (good units × ideal cycle ÷ planned time): — — should equal OEE. If it doesn't, an input is wrong.
Reading the Result
A number below expectations is not a verdict, it is a map: read the factors, not just the product. Availability losses point at breakdowns and changeovers; performance losses at micro-stops and slow cycles; quality losses at the process. The benchmarks guide explains why comparing yourself to a textbook 85% misleads, and what to do instead.
One convention worth keeping: any minute the machine is not producing for a known reason is downtime and leaves run time. Performance only measures how fast the machine ran while it was running. Mixing the two double-counts the same loss.
Frequently Asked Questions
Is this the same OEE Voltrus MES computes?
Same formula, same cap on performance. The difference is where the inputs come from: here you type them; in Voltrus they are ingested from machine states and confirmed counts at the station terminal, rolled up hourly per station and line, with downtime reasons attached. See why to measure OEE before buying a MES.
Why is performance capped at 100%?
If the raw calculation exceeds 100%, the ideal cycle time is wrong (too slow) or the counter double-counts. Capping keeps the displayed number trustworthy while the warning above tells you to fix the input. An OEE that can exceed 100% loses the room in one meeting.
Does planned maintenance count as downtime?
No. Planned stops come out of planned production time before the calculation. If maintenance happens outside the planned schedule, it is downtime. Pick one convention per line and keep it.
OEE Every Hour, Not Every Spreadsheet Session
Voltrus MES ingests machine states over keyed SCADA connections and rolls OEE up per station and line, hourly, with downtime reasons.
See Voltrus MES