Key takeaways
Short answer: Cycle time measures how long one unit actually takes to produce. Takt time measures how fast you need to produce to meet demand. Lead time measures total elapsed time from customer order to delivery. They are different metrics that answer different questions, and conflating them is one of the most common operational errors. See also Torque Monitoring vs Cycle Monitoring.
Cycle time is the time between completion of successive units at a workstation, line, or process. It is a measurement, not a target.
Cycle time = Net production time / Units produced
If a line runs 7 hours net and produces 420 units, cycle time is 60 seconds per unit. The point of measuring cycle time is to compare against takt time and against the ideal cycle time used in the Performance factor of OEE.
Takt comes from the German word for beat or pulse. Takt time is the maximum acceptable cycle time given customer demand.
Takt time = Available production time / Customer demand
If you have 7 hours of net production time per shift and customers need 504 units that shift, takt time = 25200s / 504 = 50 seconds. You must finish one unit every 50 seconds to meet demand.
Takt is a planning input. It tells you what cycle time you need to hit, and therefore how much capacity, balancing, or improvement you need.
Lead time is the total elapsed time from order received to product delivered. It includes:
Lead time is almost always much longer than cycle time because of queueing, batching, and transport delays. A unit may have a 60-second cycle time but a 14-day lead time.
Think of it as three different lenses on the same operation:
A factory can have cycle time matched to takt time and still have a 30-day lead time because of order queues, supplier wait, and finished-goods storage. Reducing lead time often means reducing queues and batch sizes, not speeding up the line.
1. Reporting cycle time as if it were takt. "Our cycle time is 45 seconds" is meaningless without the takt target. If takt is 30 seconds you are behind. If takt is 60 you have headroom.
2. Treating lead time as a production metric. Lead time mostly lives outside the line. Improving line cycle time by 10% may not move lead time at all if queue time dominates.
3. Setting takt time to ideal cycle time. Takt is set by customer demand, not by what the line can theoretically do. If demand is steady, takt is steady.
OEE Performance compares actual cycle time to ideal cycle time. Takt time is a separate metric used for planning. They are related but not the same: ideal cycle time is what the machine can do at design speed; takt time is what the schedule demands.
Plants that hit ideal cycle time but miss takt have a capacity problem (need more lines or shifts). Plants that miss ideal cycle time have a Performance problem (need to fix the line). Plants that hit both still need to manage lead time separately because queues and procurement live outside the line.
See how Fabrico captures this automatically — explore OEE for manufacturing or book a demo.
If takt is shorter than cycle, you cannot meet demand without overtime or capacity addition. That gap is the planning signal to act.
No. Takt is set by customer demand; ideal cycle time is the maximum theoretical speed of the line. A line can have ideal cycle of 30s and takt of 50s, meaning it has 20s of slack.
Yes, for different decisions. Cycle time for line performance, takt time for capacity planning, lead time for customer experience.
Usually by attacking queue time, not cycle time. Smaller batches, level loading, supplier integration, and pull systems shrink the wait that dominates lead time.
Cycle time and ideal cycle time live inside the OEE calculation. Takt time is usually managed in production planning or MES. Lead time is tracked in ERP order management.
Login
Blog
