Inputs
Example data table
This sample mirrors what the calculator expects. You can load it into the form using the "Load example" button.
| Shift (min) | Breaks (min) | Planned DT (min) | Unplanned DT (min) | Stations | Units Produced | Demand (optional) | Station Times (min/unit) |
|---|---|---|---|---|---|---|---|
| 480 | 30 | 20 | 15 | 6 | 100 | 160 | 1.8, 2.4, 2.1, 2.7, 1.9, 2.6 |
Formula used
- Effective Time = Shift - Breaks - Planned Downtime
- Net Time = Effective Time - Unplanned Downtime
- Output-Based Cycle = Net Time / Units Produced
- Station Average = mean(station times)
- Bottleneck = max(station times)
- Observed Line Cycle = Bottleneck
- Capacity = floor(Net Time / Bottleneck)
- Line Efficiency = sum(station times) / (Stations * Bottleneck)
- Balance Delay = 1 - Line Efficiency
How to use this calculator
- Enter shift length and all time losses in minutes.
- Type the number of units produced for the same shift.
- Set station count for your current assembly line layout.
- Add measured station times (minutes per unit) in the table.
- Optionally enter demand units to compute takt time.
- Click Calculate cycle time to view results above.
- Use Download CSV or Download PDF for reporting.
Cycle time as a controllable constraint
Assembly cycle time is the practical pace of a line: the minutes required to complete one finished unit at steady flow. In most lines, the slowest station defines that pace, so small delays at the constraint station create large output losses across a shift. Tracking the bottleneck prevents local optimizations that raise activity but not throughput.
Net available time improves planning accuracy
Shift length alone is misleading. Breaks, planned changeovers, and unplanned stops reduce usable production minutes. This calculator converts scheduled time into net time, then compares net time with station observations to show whether achieved output matches the capacity implied by the bottleneck. Output-based cycle time is a reality check when measurements and production differ.
Station time spread reveals balance opportunities
When station times vary widely, operators experience waiting at fast stations and overload at slow ones. The station list and Plotly chart visualize the spread, making it easier to spot candidates for work sharing, fixture redesign, kitting, or standardized work updates. A narrow spread indicates stable methods; a wide spread often signals mixed work content, training gaps, or material access issues.
Line efficiency and balance delay quantify waste
Line efficiency is calculated as the sum of station times divided by stations multiplied by the bottleneck. Values closer to 100% indicate a balanced workload. Balance delay is the remaining percentage and approximates idle time caused by imbalance during steady operation. Use these metrics to compare layouts over time, keeping station count consistent.
Takt comparison connects demand to rhythm
If you enter demand units for the same net time window, the calculator computes takt time. When bottleneck cycle time is higher than takt, the line cannot meet demand without changes. A positive takt gap indicates slack that can absorb variability, support quality checks, or allow maintenance. Revisit demand to keep the takt signal aligned with plans.
Use results to drive targeted improvements
Start by stabilizing downtime inputs with consistent definitions, then measure station times using repeatable methods. Reduce the bottleneck through micro-improvements, add parallel capacity, or redistribute elements of work while protecting ergonomics. Recalculate after each change to confirm the new constraint and expected shift output, then document the updated standard to sustain gains.
FAQs
1) What is the difference between cycle time and takt time?
Cycle time is how fast the line actually produces a unit. Takt time is the required pace to meet demand with the available net time window.
2) Why does the bottleneck station define observed cycle time?
In a paced flow, each unit must pass through every station. The slowest station limits release rate, so faster stations wait and do not increase throughput.
3) Which cycle time should I report to management?
Use bottleneck-based cycle time for line design and balancing. Use output-based cycle time to explain shift performance and verify whether downtime or variability drove gaps.
4) How many station time samples should I measure?
Take multiple cycles per station and include typical variation. If times swing widely, improve method stability first, then remeasure before making staffing or layout decisions.
5) What does low line efficiency usually indicate?
It typically signals unbalanced work content, excessive walking or searching, or a constraint that is much slower than other stations. Focus improvements on the constraint first.
6) Can I use this for batch or cell manufacturing?
Yes, as long as station times represent per-unit processing for the flow. For batches, convert batch time into per-unit time and reflect batch changeovers as planned downtime.