Cycle Time Calculator

Adjust the calculator values below

Net operating time 7.25 h
Total units completed 400
Good units 390
Observed average cycle time 65.25 s/unit
Average time per good unit 66.92 s/good unit
Total throughput rate 55.17 units/h
Good-unit throughput rate 53.79 good units/h
First-pass yield 97.5%
Target cycle time 60 s/unit
Cycle-time variance 5.25 s/unit
Target comparison 5.25 s/unit slower than target
Capacity projection period 8 h
Identical parallel processes 1
Projected completed units 441
Projected good units 429
65.25 s/unit
Observed average cycle time Net operating time divided by all completed units in the observed period
Other Calculator

Cycle Time Calculator

Use this cycle time with scheduled production period, planned downtime and breaks, and unplanned downtime to get fast results, understand the formula...

What this cycle-time result measures

Cycle time is the time required to produce a part or complete a process. This calculator estimates the observed average completion interval for one process over a recorded period: scheduled time minus planned and unplanned downtime, divided by every completed unit. It is an aggregate period average, so it should not replace direct timing when individual cycles vary or a standard work element must be measured.

How quality and throughput are separated

Rejected or rework units remain in the denominator for the observed cycle-time calculation because they consumed completion capacity. Good units equal completed units minus rejected or rework units. The calculator separately reports time per good unit, total and good-unit throughput per operating hour, and first-pass yield so faster output is not mistaken for good output.

Target comparison and projection limitations

The target field compares the observed cycle time with a user-entered target for the same process scope. It is not automatically takt time, which is based on available production time divided by customer demand. The capacity projection assumes the observed cycle time, yield, downtime treatment, process mix, and parallel-process performance continue unchanged; bottlenecks, changeovers, staffing, maintenance, material constraints, learning, variability, and demand can make actual capacity different.

Frequently asked questions

Common questions about production cycle time, downtime, good units, targets, and capacity projections.

What does cycle time mean in this calculator?

Observed average cycle time is net operating time divided by all completed units. Net operating time is the scheduled period after the planned and unplanned downtime you enter has been removed.

Why are rejected or rework units included in cycle time?

Rejected units still consumed production time, so they remain in the completed-unit count used for observed cycle time. The calculator reports first-pass yield and time per good unit separately so quality loss stays visible.

Is target cycle time the same as takt time?

No. Target cycle time is a comparison value that you enter. Takt time is based on available production time divided by customer demand, so it requires a demand value and answers a different planning question.

Which downtime should I subtract?

Subtract time when the measured process was unavailable during the same scheduled period, such as breaks, changeovers, faults, or waiting time. Keep the boundary consistent when comparing shifts, lines, or dates.

What does the capacity projection assume?

The projection assumes the observed cycle time and first-pass yield continue for the selected period and that identical parallel processes perform at the same rate. It is a planning estimate, not a production guarantee.

When should I time individual cycles instead?

Use direct cycle observations when work varies substantially by product, operator, setup, or batch. An aggregate period is useful for actual throughput, while repeated individual timings are better for studying variation and standard work.