Cycle Time vs Takt Line Balance Planner
Find which of four line stations is the real bottleneck against takt time, not just the average cycle time.
The average cycle time (4.38 min/unit) is under takt and would look fine on its own, it hides Station 4's real 7-min/unit bottleneck.
Continue Analysis
Based on your results, these related decisions are available.
How this works
Takt time is available time divided by demand, the pace a line must sustain. A line with several stations in series is only as fast as its single slowest station, not the average cycle time across all of them. Averaging can make a line look fine when one station is genuinely a bottleneck, this engine reports both figures side by side so that gap is visible rather than silently smoothed over.
Key terms
- Takt time: available time divided by demand, the pace the line must sustain to meet demand.
- Bottleneck station: the station with the highest cycle time, the one that actually governs the line's throughput.
- Stations needed: how many parallel stations/operators a given station needs to keep pace with takt,
ceil(cycle time / takt time).
Assumptions
- Four stations in series, one line, one takt time
- Stations run in series, so the slowest one sets the line's real pace
Limitations
- Fixed four-station shape, not an open-ended N-station line balancer
- Does not model changeover time between products or station-to-station buffer effects
- Distinct from Production Capacity Planner, which handles a single cycle time, not a multi-station line
Sources
Rother and Shook, Learning to See, and Groover, Work Systems and the Methods, Measurement, and Management of Work, standard line-balancing and takt-time treatment.
Worked example
At 100 units/day demand and 480 available minutes, takt time is 4.8 min/unit. Four stations run at 3, 3.5, 4, and 7 minutes per unit. The average, 4.375 min/unit, is under takt and would read as fine on its own. But the 7-minute station is the real bottleneck, the line's actual throughput is only 480/7, about 68.6 units/day, a 31.4-unit/day shortfall the average completely hides. That station needs two parallel operators to close the gap.
Common use cases
- Finding which station on a line is actually limiting throughput, not assuming it from an average
- Sizing how many parallel operators a bottleneck station needs to hit takt
- Continuing from Production Capacity Planner's single-station takt check into a multi-station line view
- Feeding a confirmed capacity gap into Bottleneck Capacity Analyzer's constraint analysis
Frequently asked
- Why isn't the average cycle time the bottleneck indicator?
- A line runs only as fast as its slowest station; the average across four stations can look fine while one specific station exceeds takt time and constrains total output.
- What is takt time exactly?
- Takt time is available production time divided by customer demand, the pace the line needs to sustain to meet demand exactly, not a measured speed but a required one.
- What if every station is below takt time?
- Then the line has slack relative to demand at every station; the result should say so rather than manufacturing a bottleneck that does not exist.
- Does balancing to takt time guarantee on-time delivery?
- It confirms the line's capacity can match demand pace; it does not account for downtime, changeovers, or upstream material availability, which can still cause misses even at a balanced line.