Line balancing

Line balancing is assigning work to stations so every station carries a roughly equal share of the total cycle — no station drowning while the next one idles. A balanced line wastes less capacity, needs fewer operators for the same output, and exposes its true bottleneck instead of hiding it behind uneven loading.

Takt time vs cycle time

Two numbers govern every balancing decision:

• Takt time = available production time ÷ customer demand. It is the rhythm the market sets: one unit every N seconds.
• Cycle time is how long a station actually takes to do its assigned work.

The balancing rule is simple to state and hard to maintain: every station's cycle time must sit at or below takt. The station with the highest cycle time is the bottleneck, and it — not the average — sets the line's real output.

Why lines drift out of balance

Products change, task times drift as operators learn, a new fixture speeds one station and strands another. Most plants re-balance with spreadsheets and stopwatch studies, or lean on ERP capacity-planning modules that see work centers but not individual task assignments. The result: re-balancing happens rarely, and the line runs unbalanced between studies.

How the Factory Agent does it

• Cycle-time rollups per station across the whole line, computed from the same task and process data the layout and work instructions use
• Balance against takt: the agent assigns tasks to stations and shows exactly which station binds and by how much
• Discrete-event throughput simulation validates the balance under real conditions — utilization, buffers, and bottlenecks per station, not just static arithmetic
• Re-balance by prompting: change the takt, add a station, move a task — the rollups and simulation re-run, so a demand change is a 30-minute exercise instead of a new study
• A readiness gate states plainly what still blocks the target rate, and why

Common questions

What's a good line balance rate? Divide the sum of all station cycle times by (number of stations × the slowest station's cycle time). Above ~85% is generally considered well balanced; the agent reports this per variant.

Does this replace our ERP? No — it layers on top. ERP capacity planning sees aggregate hours; balancing needs task-level assignment, which is what the agent adds.

Related: factory layout planning · shift scheduling

Book a demo to see your line balanced from one prompt.