This estimator calculates observed equipment cycle time from actual run time and the number of units produced. Cycle time answers a simple operational question: on average, how much running time did the equipment use for each unit during the measured period?
The result is useful for capacity checks, bottleneck reviews, and comparisons with takt time or an engineering reference cycle. Because it is an average, it can hide variation between individual cycles, micro-stops, product mixes, and changeovers. Use run time and unit counts that cover the same operating window, then compare the result only with benchmarks built on the same inclusion rules.
Observed production
min
units
Result
—
average cycle time
Units per minute—
Units per hour—
Seconds per unit—
1. Enter actual run time Use the minutes during which the equipment was considered running under your measurement standard.
2. Enter unit count Use the total units associated with that same run-time window.
3. Read average cycle time The main result shows minutes per unit; the detail rows translate the same average into seconds per unit and output rates.
4. Compare with a reference Compare observed cycle time with a design cycle, historical baseline, or takt time only when the definitions and product mix are compatible.
Average cycle time = Actual run time ÷ Units produced
Units per hour = Units produced ÷ Actual run time × 60
Seconds per unit = Average cycle time × 60
Run time is entered in minutes. The formula assumes the unit count represents output from that same run period. It is an average cycle measure rather than a distribution of individual cycle observations.
What the result means
Average cycle time is the mean amount of actual running time associated with one produced unit.
If products have very different routing or standard times, a single blended cycle time may not be suitable for detailed performance analysis.
Given: 375 minutes of run time and 250 units produced.
Calculation: Average cycle time = 375 ÷ 250 = 1.5 min/unit. Units per hour = 250 ÷ 375 × 60 = 40 units/hour. Seconds per unit = 1.5 × 60 = 90 seconds.
Result: The observed cycle time is 1.5 minutes per unit.
Interpretation: A takt time below 1.5 minutes would indicate that this observed pace is not fast enough to meet that demand without added capacity or improvement.
Should downtime be included in run time?
Only if your cycle-time definition intentionally includes it. For an operating cycle time, use actual running time; for elapsed production time per unit, a broader time basis may be appropriate.
Can I use good units instead of total units?
You can, but that changes the metric to good-output cycle time. Label and compare it consistently so it is not confused with gross production cycle time.
Why does product mix matter?
Different products can require different processing times. A blended average can move because the mix changed even if the equipment performed the same on each product.
Is lower cycle time always better?
Not automatically. Faster operation must still meet safety, quality, equipment, and process requirements; an unrealistically low cycle time can also signal a measurement issue.
How does cycle time differ from takt time?
Cycle time describes the observed production pace, while takt time is the maximum average pace required to satisfy demand with the available production time.