Solutions
Resources
© 2025 Caddis Systems. All rights reserved.
A cycle time report logs the actual time each machine takes to complete one unit, cycle by cycle, then compares that data against an ideal or target cycle time to reveal drift, variance, and slowdowns. Build one by capturing individual cycle timestamps directly from the machine, not from operator estimates, then analyze average, minimum, maximum, and standard deviation to catch problems before they show up as missed output.
A cycle time report shows whether a machine is actually running at the speed it's supposed to, cycle by cycle, instead of relying on a single average that hides real problems. If you're a plant manager or process engineer trying to catch tooling wear, process drift, or performance losses before they hurt output, this is the report that surfaces it.
This guide covers what to track, how to build the report, and how to read the results.
A cycle time report needs individual cycle data, not just a shift average, since averages smooth over the exact variance that matters most:
Machine or asset ID: the specific equipment being measured
Timestamp per cycle: the exact time each individual cycle occurred
Actual cycle time: measured in seconds or minutes for that specific cycle
Ideal cycle time: the theoretical best cycle time the machine can achieve under perfect conditions
Part or job number: to separate cycle time data by product, since different parts naturally run at different speeds
Shift and operator: to identify whether variance is tied to a specific crew or handoff
Ideal cycle time matters because it's the benchmark every other calculation depends on, including OEE Performance, which measures actual output against theoretical maximum output.
The build process depends on capturing cycle start and stop events consistently, ideally at the individual part level rather than aggregated per shift.
Define ideal cycle time for each part number or job, based on engineering specs or historical best performance
Capture actual cycle time for every individual unit produced, not a sampled subset
Timestamp each cycle so trends over the shift, day, or week are visible, not just a single average
Roll the data up into summary statistics: average, minimum, maximum, and standard deviation per machine and part
Manual timing with a stopwatch or operator logs works for a spot check, but it can't sustain the volume of data needed to see gradual drift. Manufacturers without automated tracking can start with a structured log before moving to continuous capture.
Analysis starts by comparing actual cycle time against ideal cycle time and against takt time, the maximum time allowed per unit to meet customer demand.
Calculate the gap between actual average cycle time and ideal cycle time; a growing gap over weeks often signals tooling wear or mechanical degradation
Check standard deviation, not just the average; high variation between cycles points to an inconsistent process even if the average looks fine
Compare actual cycle time against takt time to confirm the station can keep pace with demand
Look for gradual drift over time rather than single outliers, since a slow trend is a more reliable early warning than one unusually long cycle
Standard deviation is often the most overlooked number on the report. Two machines can share the same average cycle time while one runs consistently and the other swings wildly between fast and slow cycles, a sign of an underlying process problem the average alone won't reveal.
Gradual cycle time drift, a slow but steady increase in actual cycle time over days or weeks, is one of the earliest warning signs of tooling wear, machine degradation, or process creep. Catching that drift early, before it shows up as a missed shipment or a scrapped batch, is one of the strongest arguments for continuous cycle time tracking over periodic spot checks.
Automated cycle time tracking captures every individual cycle directly from the machine, removing the rounding and sampling gaps that come with manual timing. That data feeds directly into OEE Performance calculations, since cycle time accuracy is the foundation those numbers depend on.
Manufacturers can use the cycle time calculator to compare ideal versus actual cycle times and quantify lost production, and reference the guide to reducing cycle time once the report identifies where the losses are concentrated.
Ideal cycle time is the theoretical best performance under perfect conditions. Actual cycle time is what really happened on the floor. The gap between the two reveals performance losses.
Standard deviation shows how consistent the process is, not just how fast it is on average. High variation between cycles often points to an intermittent problem that a single average would hide completely.
Continuously if possible, since drift develops gradually. A weekly or monthly review can miss a slow trend that's already costing significant output by the time it's noticed.
Yes. Accurate historical cycle time data grounded in real machine performance produces far more reliable cost estimates and customer quotes than engineering assumptions or outdated time studies.
It varies by process and equipment, so the more useful comparison is a machine's variance against its own historical baseline rather than a fixed industry number. A sudden increase in variance is the signal worth investigating.
A cycle time report is only as useful as the granularity behind it. Individual cycle data, tracked continuously and compared against ideal cycle time and takt time, catches problems that shift averages hide. See how Caddis Systems can automate cycle time capture down to the individual part. Book a demo today.