Line efficiency is the ratio of a line's actual output to the output a perfectly balanced line could achieve, expressed as a percent. It measures how evenly work is spread across stations. A line is 100% efficient only when every station has the same cycle time; any station that finishes early and waits is idle time that drags the number down.
Line efficiency answers a narrow, useful question: is this line balanced, or is one station forcing the others to wait? That is a different question from the one OEE answers, which is why a line can post a strong efficiency number and a weak OEE at the same time. This guide defines line efficiency, shows the calculation, and, most importantly, maps exactly where it and OEE disagree, so you know which number to trust for which problem.
What Is Line Efficiency?
Line efficiency measures balance: how close each station's workload is to every other station's. On a balanced line, work flows without any station sitting idle waiting for the slowest one. On an unbalanced line, faster stations finish early and wait on the bottleneck, and that waiting is wasted capacity you paid for. Line efficiency puts a number on that waste, the closer to 100%, the less idle time built into the line's design.
The key phrase is balanced output. Line efficiency compares what the line actually produces against what it could produce if the total work were spread perfectly evenly across stations, all running at the pace of the slowest one. It is fundamentally a design-and-layout metric: it tells you whether the work content is distributed well, not whether the machines ran without breaking down or whether the parts came out good. Those last two belong to OEE.
How Do You Calculate Line Efficiency?
You calculate line efficiency by dividing the total work content by the capacity the bottleneck implies across all stations. The standard formula is: line efficiency = (sum of all station cycle times) ÷ (number of stations × the bottleneck station's cycle time) × 100. The steps:
- Measure each station's cycle time. Time every station at the same product and conditions. Pull the numbers from machine data where you can, so you capture real variation rather than one clean cycle.
- Sum the station cycle times. This is the total work content of one unit across the whole line, the numerator.
- Find the bottleneck cycle time. The slowest station sets the line's pace; every other station can only cycle as often as the bottleneck releases work.
- Multiply the bottleneck time by the number of stations. This is what the line would produce in work-content terms if every station took as long as the slowest, the denominator.
- Divide and multiply by 100. The result is the percent of paid station time that is actually doing work rather than waiting on the bottleneck.
- Read the gap as idle time. A 78% line efficiency means 22% of your station capacity is idle by design, waiting on the slow station. That gap is the target for line balancing.
A worked example: a five-station line with cycle times of 48, 52, 66, 44, and 50 seconds. The sum is 260 seconds. The bottleneck is 66 seconds. Line efficiency is 260 ÷ (5 × 66) × 100 = 260 ÷ 330 × 100 = 78.8%. Roughly a fifth of the line's station-time is idle, waiting on the 66-second station. Rebalance the work so the stations sit closer to 52 seconds each and efficiency climbs toward the 90s, without buying a single machine.
One caution on the formula: it uses cycle times, so it inherits whatever error is in your cycle-time data. If you time the bottleneck on a good cycle and miss its frequent long ones, you will overstate line efficiency and wonder why the real output never matches the number. Measure each station across many consecutive cycles, keep the variation, and use the typical bottleneck cycle rather than its best-case one. A line-efficiency figure built on cherry-picked cycles is a flattering fiction; one built on honest, continuous cycle-time data is a work list.
How Is Line Efficiency Different from OEE?
Line efficiency measures how evenly work is distributed; OEE measures how well equipment converts planned time into good output. They are not two versions of the same number, they measure different losses, and a line can score high on one while failing the other. OEE multiplies availability, performance, and quality, so it captures downtime, speed loss, and defects. Line efficiency captures none of those; it only sees the idle time created by imbalance. A perfectly balanced line that breaks down constantly is 100% efficient and has terrible OEE.
This is exactly where the two disagree, and the disagreement is the point. A line can run at 95% line efficiency, beautifully balanced, while its OEE sits at 60% because of frequent unplanned stops and a quality problem that balance metrics simply cannot see. Report line efficiency alone and the line looks excellent; report OEE and you find the real losses. The reverse also happens: a line with strong OEE can hide a balance problem if the bottleneck station is also the one with the best uptime. You need both lenses.
The practical rule is to let each metric drive the decision it is built for. When you are designing a line, adding a station, or moving work between operations, line efficiency is the number to optimize, it tells you whether the layout wastes capacity. When you are running the line day to day, OEE is the number to watch, because it catches the breakdowns, slow cycles, and scrap that erode output after the layout is fixed. Confusing the two leads to the classic wasted improvement: a team spends a week rebalancing a line to lift efficiency from 88% to 94%, gains almost nothing in real output, and only later discovers the line's actual problem was a bottleneck machine down a quarter of every shift. Line efficiency was never going to show them that.
| Line efficiency | OEE | |
|---|---|---|
| Core question | Is the work balanced across stations? | Is planned time becoming good output at speed? |
| Losses it sees | Idle time from imbalance | Downtime, speed loss, defects |
| Losses it misses | Breakdowns, slow cycles, scrap | Poor work distribution between stations |
| Formula | Σ station times ÷ (stations × bottleneck time) | Availability × Performance × Quality |
| Fix it with | Line balancing re-sequencing work | Maintenance, changeover, quality control |
| Best used for | Line design and layout decisions | Day-to-day equipment loss tracking |
Line efficiency vs. OEE: the reference numbers
The two metrics rest on distinct, well-established formulas:
- Line efficiency = (sum of station cycle times) ÷ (number of stations × bottleneck cycle time) × 100 reaching 100% only when the line is perfectly balanced, the standard line-balancing definition.
- OEE = Availability × Performance × Quality with the world-class benchmark of 85% built from roughly 90% availability, 95% performance, and 99.9% quality (OEE.com, World-Class OEE). Because it is multiplicative, OEE penalizes losses line efficiency never sees.
- U.S. manufacturing ran near 75.7–76.3% capacity utilization through 2025 per the Federal Reserve's G.17 release (Federal Reserve, Industrial Production and Capacity Utilization), a reminder that idle capacity, some of it from imbalance, is common across the sector.
What Is a Good Line Efficiency, and How Do You Improve It?
A well-balanced line generally runs above 85% line efficiency, and world-class balancing pushes into the 90s; below about 70% you have significant idle time worth attacking. But the target depends on the line, a high-mix line that changes products often will show lower efficiency than a dedicated single-product line, because each product balances differently and the compromise layout cannot be perfect for all of them.
You improve line efficiency by moving work content off the bottleneck station and onto the stations that finish early, so every station's cycle time converges toward the same value. That is the whole discipline of line balancing: shift tasks, re-sequence steps, split or combine stations, and sometimes add a parallel station at the constraint. A yamazumi chart stacking each station's task times against takt makes the imbalance visible and shows exactly which tasks to move. Watch the interaction with the real constraint, though, if the bottleneck is also your least reliable station, rebalancing the work without fixing its downtime just moves idle time around, which is the argument for reading line efficiency and OEE together, and the reason our line OEE vs. cell OEE guide matters for where you measure.
Both numbers get more useful when they come from the same live data instead of two separate studies. When station cycle times, downtime, and quality counts are captured from machine signals and the floor's own tablets, line efficiency and OEE are computed from one source, so you can see at a glance whether a low number is a balance problem or an equipment problem. That is the approach Harmony takes when it connects the floor into one operational layer with no rip-and-replace of the equipment; the plant in our CLS case study reads balance and OEE off the same picture, which stops teams from rebalancing a line whose real problem was uptime all along.