OEE calculator

Your OEE calculator, with the awkward number left in.

Five figures off one shift and you have an OEE. The arithmetic is not the hard part — availability × performance × quality has not changed in forty years. What decides whether the answer means anything is the standard cycle time you feed it, and almost nobody checks that.

So this one shows performance twice: what your numbers actually say, and the capped version everyone reports. When those two disagree, the gap is the finding.

One machine, one shift

Five numbers from a single window.

Take one machine over one shift or one day — not a whole factory averaged together, which is how an OEE figure stops meaning anything. Everything updates as you type, nothing is sent anywhere, and there is no email box on this page.

Your shift

How long the machine was scheduled to run. Planned maintenance and unmanned breaks come out before this number, not after it. Of that, how long it was actually producing. Loading time minus every unplanned stop. The ideal or nameplate cycle — the rate the part is supposed to run at. This is the input that quietly breaks most OEE figures. Everything that came off the machine in the window, good and bad together. Scrap plus anything reworked. A part that needed a second operation was not right first time.

Overall equipment effectiveness

83.0% Availability × performance × quality, using the capped performance figure — which is the convention, and is the one your customer means when they ask.

The three components

Availability 85.0% Run time ÷ loading time. Losing 15.0 points here.
Performance capped 100.0% Losing 0.0 points here.
Quality 97.6% Good parts ÷ total parts. Losing 2.4 points here.

Performance, uncapped

What your numbers actually say 106.2% Standard cycle × parts made ÷ run time. Your floor averaged 49.0s a part against a standard of 52s.

Performance above 100% is not a fast machine. It means the standard cycle you entered is slower than what the machine is really doing, so every OEE figure built on it is flattering you. Fix the standard before you report the number — and note that capping it, which is what almost every system does silently, hides exactly this.

Where it is going

Availability is costing you the most — the machine is not running when it is scheduled to. Stops, changeovers and waiting — not speed, and not scrap.

One machine, one window, five numbers you typed. It is the same arithmetic a production system runs continuously across every machine — the difference is that it does not depend on anyone remembering to write the stops down, and it keeps the standard cycle honest because it can see the actual one. That is live monitoring and honest OEE.

Bring us the figure you do not believe.

If your OEE looks too good, or moved ten points for no reason anybody can explain, send us the numbers you put in here. An engineer will tell you which input is doing it. That conversation costs nothing and usually takes one call.