Enter your production run duration and total units produced to find your cycle time — the average time required to complete one unit. Choose your preferred time unit (seconds, minutes, or hours) and the calculator returns your actual cycle time per part along with throughput per hour and parts per minute.
Actual Cycle Time
--
Cycle Time (Minutes/Part)
--
Throughput (Parts/Hour)
--
Parts Per Minute
--
Total Run Duration (Seconds)
--
Cycle time is the average elapsed time required to produce one unit or complete one process from start to finish. It is calculated by dividing the total net production time by the number of units produced during that period. A lower cycle time generally means higher productivity.
The formula is: Cycle Time = Net Production Time ÷ Units Produced. For example, if you run a machine for 60 minutes and produce 120 parts, your cycle time is 0.5 minutes (30 seconds) per part.
Cycle time measures how long it actually takes to produce one unit, while takt time is the rate at which units must be produced to meet customer demand. Ideally, cycle time should be equal to or less than takt time to keep up with demand without overproducing.
Throughput is the number of units produced per unit of time — typically expressed as parts per hour. It is the inverse of cycle time. If your cycle time is 30 seconds per part, your throughput is 120 parts per hour (3600 ÷ 30).
Knowing your cycle time helps you identify production bottlenecks, plan capacity, set realistic output targets, and benchmark improvements over time. It is a foundational metric in lean manufacturing and continuous improvement initiatives.
Machine cycle time refers to the time a single machine takes to complete one operation on one part, such as a CNC mill finishing a cut. Process cycle time is the total time a part spends within an entire process step, including any waiting or loading time — which is typically longer.
Common strategies include eliminating non-value-added steps, reducing setup and changeover times, improving equipment reliability, balancing workloads across workstations, and automating repetitive tasks. Even small reductions in cycle time can significantly increase overall throughput.
Yes. Cycle time applies to any repeatable process. In software development, it might measure the average time to complete a feature or resolve a ticket. In a restaurant, it could track how long it takes to serve one order. The formula remains the same: total time divided by completed units.