Cycle Time Calculator finds actual seconds per completed unit while a process runs. Compare that pace with ideal cycle time, stop-inclusive effective pace, customer-demand takt time, and a target cycle scenario. Enter one process, product, and reporting period with consistent units.
Enter production and demand
Cycle Time Calculator formulas
Convert minutes to seconds before comparing cycle metrics. The Cycle Time Calculator reports run-time cycle as the observed average during actual operation. Stop-inclusive effective time and takt answer different questions. The first reflects downtime; the second sets the good-unit pace required by demand over the planned window. Their numerators and denominators should not be swapped casually.
How to use this Cycle Time Calculator
Choose one machine or process and a fixed reporting window. Planned production time is the time that process was scheduled to make units. Exclude an unscheduled break before entering it. Stop time is the sum of stops within that planned production window. The tool subtracts stop time to find run time. Use the number of all completed units, including rejects, for the observed run-time cycle. The quality rate then uses good units divided by total units, so scrap cannot silently disappear from the demand scenario.
Enter the ideal cycle time as a validated fastest sustainable rate for this product. A run-time cycle faster than the claimed ideal signals an outdated standard or mismatched time or count data. A mixed-product line should use product-specific ideal times or an agreed equivalent-unit method. The Cycle Time Calculator flags an above-100% performance ratio rather than hiding it.
Set a scenario cycle to test a speed improvement with the same run time and quality fraction. Scenario output is an expected average, not a promise of whole shipped units; round conservatively for actual commitments. Enter demand for good units in the same period. The tool calculates takt over planned time and also derives a stricter required run cycle that accounts for stops and quality loss. If that required pace is faster than the ideal cycle, changing speed alone cannot meet the demand under the entered assumptions.
Worked cycle time example
A line is scheduled for 480 minutes, with 60 minutes of stops. It runs for 420 minutes, completes 500 units, and accepts 475 good units. The Cycle Time Calculator gives 420 × 60 ÷ 500 = 50.4 seconds per completed unit. The observed rate is about 71.43 units per run hour. Stop-inclusive pace is 480 × 60 ÷ 500 = 57.6 seconds per completed unit. Measured per good unit, it is 480 × 60 ÷ 475 = 60.63 seconds.
| Measure | Calculation | Result |
|---|---|---|
| Run-time cycle | 420 × 60 ÷ 500 | 50.4 s/unit |
| Quality rate | 475 ÷ 500 | 95% |
| Takt for 500 good units | 480 × 60 ÷ 500 | 57.6 s/good unit |
| Required run cycle | 420 × 60 × 0.95 ÷ 500 | 47.88 s/unit |
| Performance at 45 s ideal | 45 ÷ 50.4 | 89.29% |
For a scenario cycle of 48 seconds, expected total output is 420 × 60 ÷ 48 = 525 units. At the same 95% quality rate, expected good output is 498.75 units, a planning shortfall of 1.25 against demand of 500. At 48 seconds per unit, the run time needed for 500 expected good units is 500 ÷ 0.95 × 48 ÷ 60 = 421.05 minutes, about 1.05 more than currently available. The required run cycle of 47.88 seconds is slower than the 45-second ideal, so it is arithmetically within the stated maximum, though operational changes may still be needed.
Cycle time versus takt time, lead time, and OEE
Cycle time measures actual average process pace while operating. Takt time expresses the output interval implied by customer demand and available planned time. Lead time measures the elapsed time for an order or item through a broader process and can include waiting, transport, and queues. A machine cycle of 50 seconds does not mean an order has a 50-second lead time.
Overall Equipment Effectiveness Calculator combines availability, performance, and quality. Its performance factor equals ideal cycle time divided by observed run-time cycle under consistent counts and periods. Production Capacity Calculator models output from shifts, downtime, speed, yield, and bottlenecks. Capacity Utilization Calculator compares actual good output with sustainable good-unit capacity, which is another denominator.
Data quality and limits
Use the Cycle Time Calculator with records from one process boundary and reporting period. Record count at the same process boundary where you measure run time. Do not count units completed after the selected period against time from the earlier period. Include reject units in the total count and accepted units in good count. A zero-unit period cannot produce a finite average cycle. A zero-good-unit period has no finite good-unit pace or required run cycle at the current zero quality rate; this tool asks for a period with at least one good unit when demand planning is enabled.
OEE.com’s cycle metric guide separates run-time cycle from effective cycle measures and ideal cycle time. Its OEE calculation reference connects ideal cycle, total count, and run time to performance. These definitions inform this calculator’s labels. Some organizations use “cycle time” for a broader elapsed interval; document your chosen definition before comparing reports.
Frequently asked questions
Does cycle time include downtime?
The run-time cycle shown here excludes stop time. The effective time per completed unit includes stops within the planned production window and appears as a separate result.
Why is takt different from the actual cycle?
Takt is the demand-driven interval over planned time. The actual run-time cycle is observed run time divided by completed units. Stops and rejects create additional pressure when translating takt into a required operating cycle.
What if my cycle time is faster than the ideal?
Review the ideal standard, product mix, timing, and count boundaries. A performance result above 100% indicates the stated ideal may no longer be a valid fastest sustainable rate.
Can this predict output after a process change?
It models a changed cycle with the same run time and quality rate. Actual stops, yield, and product mix may change too, so test the scenario with production records.
Why is scenario good output fractional?
It is an expected planning value formed by applying a historical quality percentage to modeled total output. Only whole accepted items can be shipped; round conservatively for a commitment.
Can I download a report?
After a valid calculation, Download PDF opens the browser print-to-PDF workflow, and Download Excel creates an Excel-compatible CSV file.