What Is Cycle Time?
Also known as: actual cycle time, process cycle time
Definition
Cycle time is the actual elapsed time a process takes to complete one unit, measured from the start of work on that unit to the start of work on the next. It describes what the process does, not what the customer requires.
Cycle Time Explained
Cycle time is measured at a specific step and for a specific unit of output. The cleanest operational definition is the interval between successive units exiting the process, which automatically includes load, run, unload, and any repeating micro-delay embedded in the operation. Measuring it as pure machine run time is a common error that understates true cycle time by 20 to 40 percent in manual load operations, because part handling, gauging, and deburr never appear in the spindle timer.
Practitioners split cycle time into components. Machine cycle time is the automatic portion; operator cycle time is the manual work content; and total or effective cycle time is what the line actually delivers including minor stops. In a well-designed cell, operator cycle time is less than machine cycle time so the person can tend multiple machines. When the reverse is true, adding equipment capacity buys nothing until labor content is reduced.
Cycle time is frequently confused with lead time and with throughput time. Lead time is what the customer experiences, from order receipt to delivery, and is dominated by queue and wait, not processing. In most discrete plants, value-added cycle time is under five percent of total lead time. Reducing cycle time at a non-constraint step therefore has almost no effect on delivery performance, which is why cycle-time reduction projects so often fail to move the promised date.
In ERP terms, cycle time is what routing run times are supposed to represent. Infor SyteLine and LN store run rates per operation as hours per piece, pieces per hour, or fixed run duration, and finite scheduling multiplies those by quantity to build the schedule. Standards that drifted away from reality by even 15 percent will systematically produce infeasible schedules, inaccurate job costs, and capacity plans nobody trusts, so periodic re-timing against measured cycle time is basic hygiene.
Why It Matters
- Routing run times in the ERP are cycle times; when they drift, finite scheduling, capacity planning, and standard costs all degrade together.
- Comparing measured cycle time against takt time is the single fastest way to identify which station cannot support demand.
- Separating machine from operator cycle time reveals whether the constraint is equipment or labor, which points to entirely different investments.
- Cycle time drives job cost through absorbed labor and machine hours, so stale standards distort product-level margin analysis.
In Practice
A press operation shows a 42-second machine run in the controller, and the routing carries 0.0117 hours per piece, matching that number. A stopwatch study over 30 consecutive parts shows 68 seconds between successive parts leaving the press: 42 seconds run, 14 seconds load and unload, 7 seconds gauge every third part, and 5 seconds average for chip clearing. The routing understates true cycle time by 62 percent, which is why this work center is always behind schedule despite showing available capacity in the ERP.
Frequently Asked Questions
What is the difference between cycle time and lead time?
Cycle time measures how long one process step takes to produce a unit. Lead time measures the total elapsed time the customer waits, from order to delivery, including queue, material wait, transport, inspection, and shipping. Lead time is usually ten to fifty times longer than the sum of cycle times, because most of it is waiting rather than working.
Can cycle time be shorter than takt time?
Yes, and it should be. Takt is the required pace; cycle time is the achieved pace. A healthy line runs a cycle time roughly 85 to 95 percent of takt so it has headroom to absorb minor stops and still meet demand. Cycle time above takt means the process cannot satisfy demand without overtime or added capacity.
Related Terms
Takt Time
Takt time is the rate at which a process must complete one unit to meet customer demand, calculated as available production time divided by demand for that period. It sets the pace a line must sustain, not the speed it can achieve.
Throughput
Throughput is the rate at which a process, line, or plant produces good, sellable units over a defined period, expressed as units per hour, shift, or week. Only conforming output that can be sold counts toward throughput.
Bottleneck
A bottleneck is the resource in a process whose available capacity is less than the demand placed on it, making it the step that limits total system output. Every other resource can only run as fast as the bottleneck permits.
Go Deeper
Takt Time Calculator
Compute the takt time your line must hit to meet customer demand, plus the required hourly rate for supervisors and schedulers.
Finite Capacity Scheduling: A Practical Guide
Finite capacity scheduling explained: how it differs from infinite MRP loading, APS options for SyteLine and LN, data prerequisites, and AI-assisted scheduling.
Manufacturing Costing Methods Compared: Standard, Actual, Average
Standard, actual, and average costing compared for manufacturers: variance analysis, ERP setup in SyteLine and LN, DFARS considerations, and AI cost intelligence.
Working with Cycle Time in a live environment? Our engineers do this every day - and our AI agents automate most of it.