OEE Guide

Line OEE vs Machine OEE
The Line Is Not the Average

Every machine on the line reports OEE in the high 80s, and the line reports something in the 50s. Nobody has made a mistake. OEE calculated for a machine and OEE calculated for a line are different quantities, and the gap between them is set by how the machines are connected.

OEE calculation, defined properly

Overall Equipment Effectiveness is three ratios multiplied together, each measured against planned production time:

The OEE formula

FactorCalculationWhat it charges
Availabilityrun time ÷ planned production timebreakdowns, setups and changeovers
Performance(ideal cycle time × total count) ÷ run timeminor stops and running below rated speed
Qualitygood count ÷ total countscrap, rework, startup rejects
OEEA × P × Q= good count × ideal cycle time ÷ planned time

The last row is the useful check. Multiply the three factors and run time and total count cancel, leaving the good units made, expressed as a share of what an ideal machine would have made in the planned time. If your A, P and Q don’t multiply back to that figure, one of them is using a different denominator.

Illustrative arithmetic, not plant data

A machine rated at 60 units per minute is planned for 480 minutes. It is down for 60, so it runs for 420: Availability 87.5%. In those 420 minutes it makes 23,000 units against an ideal 25,200: Performance 91.3%. Of the 23,000, 22,540 are good: Quality 98.0%. OEE is 0.875 × 0.913 × 0.980 = 78.3%, and the check agrees: 22,540 good units at an ideal 60 per minute is 375.7 minutes of fully productive time out of 480.

Two decisions change the number without changing the machine. The first is the rate used as “ideal”: a nameplate speed nobody runs, or a speed set per product. The second is the denominator. OEE excludes time that was never scheduled, so cutting a shift can raise it while the asset makes no more. TEEP measures against the full calendar instead; Asset Efficiency vs OEE reconciles the two.

Machine OEE and line OEE measure different things

Machine OEE is the formula above applied to one machine’s run time, count and rejects. Line OEE is the same formula applied at the end of the line: good units out, against the line’s rated speed and planned time.

The two part company because a machine on a line can stand still for reasons that are not its own. When the machine feeding it stops, it is starved. When the machine after it stops, it is blocked. Depending on how your monitoring system codes those states, that time is either charged to the machine or excluded as an external loss. Either way, the line pays for it. So the line number collects every machine’s losses plus the losses that pass from one machine to the next.

Why line OEE is not the average of machine OEEs

Averaging machine OEEs is the most common shortcut and the most misleading one. An average treats the machines as alternatives, as if product could reach the end of the line through whichever machine happens to be running. On a series line, every unit passes through every machine. If one machine is down and nothing sits between it and its neighbors, the whole line is down.

Take five machines, each at 85% OEE. Their average is 85%. With no buffering between them, the line runs only when all five run, and the losses multiply: 0.85544%. The average overstates the line by more than 40 points. Is 85% OEE achievable on your line? works through what that does to the world-class benchmark.

Series topology: when every loss propagates

The multiplication is exact only under specific conditions, and it pays to know which factor behaves how on a close-coupled line (no storage between machines):

Real lines are rarely close-coupled throughout. On a five-machine bottling line whose machine availabilities multiply out to 46.7%, the line runs at 54.3% (see OEE simulation). The multiplication assumed every stoppage reached the whole line. Buffers meant many didn’t.

Line OEE calculator

Enter availability, performance and quality for up to six machines in series. The calculator shows each machine’s OEE and the line figures that arithmetic can give: the misleading average, the ceiling set by the weakest machine, and the close-coupled estimate. The example values are illustrative.

Machines in series

M1
M2
M3
M4
M5
Average of machine OEEs — not a line figure
Weakest machine — the ceiling no buffering can beat
Close-coupled, if all performance loss is slow running rather than stops
Close-coupled line estimate (every loss propagates)

Line availability · line performance · line quality (each the product across machines)

Arithmetic, not simulation — assumes no buffers and failures on a wall-clock basis; a buffered line does better, and only a simulation says how much. It also assumes every machine is rated at the line’s speed.

How OEE simulation gets the real number →

With the example values, every machine sits between 85% and 93%, the average is near 88%, and the close-coupled estimate is about 52%. None of those three figures is the line’s actual OEE. Where a buffered line lands between the close-coupled estimate and the weakest machine is the part arithmetic cannot supply.

Buffers decouple, so the arithmetic overstates losses

A buffer lets the downstream machine keep running while the upstream one is stopped. That is all it does, and it is enough to break the multiplication: a stoppage that would have halted the line becomes a local event. The close-coupled product charges every machine’s every stop to the whole line, so on a line with storage it overstates the losses and understates line OEE.

How much it overstates depends on the buffers and the stops together. A full buffer covers a stop only until it runs dry, so short stops are absorbed and long ones mostly pass through. A buffer drained by the last stop protects nothing against the next one. That is why buffer size has a knee, and why the distribution of stop lengths, not the average, decides where it falls.

The opposite shortcut fails in the other direction. Assume buffers decouple completely, use each machine’s average rate and availability, and take the minimum, and you get a figure that is predictably too high. Averaging removes exactly the variability that makes a real line fall short. Spreadsheet, AI, or simulation? explains why that bias always runs the same way.

Two bounds, both wrong in known directions

EstimateAssumesError on a buffered line
Average of machine OEEsmachines are alternatives, not a seriestoo high, often by a wide margin
Weakest machineinfinite buffers, perfect decouplingtoo high: a ceiling, not a forecast
Product of machine OEEsno buffers, every loss propagatestoo low: a floor
Simulationthe line as built, stop by stopvalidated against measured OEE

Getting the real line number

The floor and the ceiling are still useful. If measured line OEE sits near the close-coupled product, the buffers are doing little: they are too small for the stops, or they are empty when stops arrive. If it sits near the weakest machine, the line is well decoupled and the lever is that machine. Anywhere between, the question is which machine’s losses are actually reaching the end of the line.

Answering that means playing the line forward through time, with each machine’s rate, each failure mode’s time-to-failure and time-to-repair distributions, and the buffers between them. That is OEE simulation. A model built from per-failure-mode interrupt data, fitted properly and validated against the line’s own history can match measured OEE within 1%. The published proof point: the Fischel & Lange (WSC 2020) food-plant model was rebuilt in ReliaSim and independently validated by Tom Lange within 1% of both the plant’s measured OEE and the original ExtendSim model. It ran the same one-year simulation 1,200× faster on the same laptop (Within 1% of measured OEE).

Once the model reproduces the line, the calculator’s gap closes into a single number, and every change you are considering can be tested against it before you spend.

Frequently asked questions

How do you calculate OEE?

Multiply Availability (run time ÷ planned production time), Performance (ideal cycle time × total count ÷ run time) and Quality (good count ÷ total count). The result equals good count × ideal cycle time ÷ planned production time, which is a useful check that all three factors use the same denominator.

How do you calculate line OEE?

Apply the same formula at the end of the line: good units out, the line’s rated speed, and the line’s planned production time. Estimating it from machine figures needs assumptions about buffering, which is where arithmetic runs out.

Is line OEE the average of machine OEEs?

No. An average treats machines as alternatives, but on a series line every unit passes through every machine. Five machines at 85% average 85%, while the same five with no buffering give a line near 44%.

Why is my line OEE lower than every machine’s OEE?

Because losses pass from machine to machine. When one machine stops, its neighbors are starved or blocked, and that time reaches the end of the line even if the monitoring system excludes it from each machine’s own OEE.

Do buffers improve line OEE?

They can. A buffer lets the next machine keep running while the previous one is stopped, so line OEE rises above the close-coupled product of machine OEEs. It can never exceed the weakest machine, and how far it rises depends on buffer size against the length and frequency of stops.

Is the calculator on this page a simulation?

No. It is arithmetic that assumes no buffers, independent failures on a wall-clock basis and every machine rated at line speed. It gives a floor and a ceiling; a validated simulation of the line gives the number in between.

See a buffered line beat its arithmetic

The ReliaSim Sandbox runs a five-machine bottling line in your browser. Stop a machine, change a buffer, and watch line efficiency move. No signup.

Open the sandbox → OEE simulation

Want to see it on a real line first? Read the case study — or schedule a call.