What is cycle time in manufacturing?

Cycle time is the average time to produce one good unit under actual operating conditions, calculated as net available time divided by units produced. In the worked example, 25,800 seconds of net time and 1,200 units give 21.5 seconds per unit. It reflects real pace including manual work, machine speed, and minor stops, unlike a theoretical spec rate from the equipment nameplate.

How do I calculate cycle time for a production line?

Start with shift time, subtract breaks and planned downtime to get net available time, then divide by good units produced. In the example: 480 minus 30 minus 20 equals 430 minutes, times 60 equals 25,800 seconds, divided by 1,200 units equals 21.5 seconds per unit. Always convert to seconds first and count only good units, not scrap, in the denominator.

What is a good cycle time?

There is no universal target; a good cycle time is one that sits comfortably below your takt time. If takt is 30 seconds and cycle time is 21.5 seconds, you have about 8.5 seconds of buffer per unit to absorb variation. Aim for cycle time at 80 to 90 percent of takt. Consistency matters as much as the average, so watch the hour-to-hour spread.

Why is my cycle time higher than expected?

Usually one station or event is dragging the average. Check for micro-stops, jams, tool changes, or an operator waiting on parts. Also confirm you subtracted breaks and downtime correctly and counted only good units. If scrap sneaks into the count, cycle time looks better than reality. Measure each station individually to find the bottleneck rather than trusting the line-level number alone.

How do I convert cycle time from minutes to seconds?

Multiply net available time in minutes by 60 before dividing by units. In the example, 430 minutes times 60 equals 25,800 seconds, which divided by 1,200 units gives 21.5 seconds per unit. Keeping the numerator in seconds produces a per-unit result in seconds, the standard unit on most shop floors. If you leave time in minutes you get 0.358 minutes per unit, which is harder to read.

What is the difference between cycle time and lead time?

Cycle time measures how long one station or line takes to make a single unit, 21.5 seconds in the example. Lead time is the total elapsed time from order receipt to delivery, including queue, transport, and waiting between steps. Lead time is usually hours or days and is far longer than cycle time. Reducing cycle time helps throughput, but attacking queues often cuts lead time more.

Production and Throughput

Cycle Time Formula

Cycle time tells you how long it takes to produce one unit under actual conditions. Use it to confirm a line is keeping pace with demand or to find how much output is lost to downtime and breaks.

Formula

Cycle Time = Net Available Time / Units Produced

Variables

Net Available Time: Shift time minus breaks and planned downtime, in seconds or minutes
Units Produced: Actual good units completed during that net time window

Understanding the Cycle Time Formula

Cycle time measures the real pace of your line: how many seconds elapse between one finished good unit and the next, under the conditions you actually run in. In the example, 25,800 seconds of net time yielding 1,200 units gives 21.5 seconds per unit. That single number tells operators and planners whether the process can hit its rate. It captures the combined effect of manual work, machine speed, and small stops that a nameplate spec never shows.

Pull net available time from the shift schedule and subtract breaks, meetings, and planned downtime. In the example that is 480 minus 30 minus 20, or 430 minutes, then multiply by 60 to get 25,800 seconds. Count only good units in the denominator, not scrap. Keep time in seconds so the result reads as seconds per unit. The common trap is using the full 480 minutes, which understates cycle time and hides lost capacity.

Compare cycle time against takt time to judge health. If takt is 30 seconds and your cycle is 21.5 seconds, you have roughly 8.5 seconds of buffer per unit and can meet demand with room for variation. If measured cycle time climbs above takt, the line falls behind and orders slip. Track cycle time by hour or by shift; a rising trend usually points to a specific station, a tooling issue, or growing micro-stops worth investigating.

Worked Example

A shift runs 480 minutes. Breaks and meetings take 30 minutes. Planned downtime is 20 minutes. The line produced 1,200 units.

Net available time = 480 - 30 - 20 = 430 minutes
Net available time in seconds = 430 x 60 = 25,800 seconds
Cycle time = 25,800 / 1,200 = 21.5 seconds per unit

Result: 21.5 seconds per unit

Common Mistake

Using total shift time instead of net available time. If you skip the break and downtime subtraction, your cycle time looks faster than it actually is, and the line appears to have more capacity than it does.

Frequently Asked Questions

What is cycle time in manufacturing?: Cycle time is the average time to produce one good unit under actual operating conditions, calculated as net available time divided by units produced. In the worked example, 25,800 seconds of net time and 1,200 units give 21.5 seconds per unit. It reflects real pace including manual work, machine speed, and minor stops, unlike a theoretical spec rate from the equipment nameplate.
How do I calculate cycle time for a production line?: Start with shift time, subtract breaks and planned downtime to get net available time, then divide by good units produced. In the example: 480 minus 30 minus 20 equals 430 minutes, times 60 equals 25,800 seconds, divided by 1,200 units equals 21.5 seconds per unit. Always convert to seconds first and count only good units, not scrap, in the denominator.
What is a good cycle time?: There is no universal target; a good cycle time is one that sits comfortably below your takt time. If takt is 30 seconds and cycle time is 21.5 seconds, you have about 8.5 seconds of buffer per unit to absorb variation. Aim for cycle time at 80 to 90 percent of takt. Consistency matters as much as the average, so watch the hour-to-hour spread.
Why is my cycle time higher than expected?: Usually one station or event is dragging the average. Check for micro-stops, jams, tool changes, or an operator waiting on parts. Also confirm you subtracted breaks and downtime correctly and counted only good units. If scrap sneaks into the count, cycle time looks better than reality. Measure each station individually to find the bottleneck rather than trusting the line-level number alone.
How do I convert cycle time from minutes to seconds?: Multiply net available time in minutes by 60 before dividing by units. In the example, 430 minutes times 60 equals 25,800 seconds, which divided by 1,200 units gives 21.5 seconds per unit. Keeping the numerator in seconds produces a per-unit result in seconds, the standard unit on most shop floors. If you leave time in minutes you get 0.358 minutes per unit, which is harder to read.
What is the difference between cycle time and lead time?: Cycle time measures how long one station or line takes to make a single unit, 21.5 seconds in the example. Lead time is the total elapsed time from order receipt to delivery, including queue, transport, and waiting between steps. Lead time is usually hours or days and is far longer than cycle time. Reducing cycle time helps throughput, but attacking queues often cuts lead time more.