Cycle time tracking is the single most actionable metric on a production line, yet most plants track it wrong — or don't track it at all. Operators record cycle times on paper clipboards. Spreadsheets calculate averages once a week. PLCs count cycles but ignore micro-stops and speed losses. This cycle time tracking checklist covers every element required to measure, analyse, and improve cycle time per part — from sensor configuration and target setting through deviation analysis and root-cause action. Based on iFactory's deployment data across 1,000+ manufacturing plants, these 30 items ensure your cycle time tracking captures every fraction of a second and converts it into throughput improvement.
Measure Every Cycle Automatically — See Actual vs Target in Real Time
iFactory's cycle time dashboard captures actual cycle time per part from your PLCs, compares it against targets and takt time, and flags deviations before they become downtime. See your line in a 30-minute session.
Why Structured Cycle Time Tracking Drives Throughput
Manufacturing plants that implement structured cycle time tracking — per-part, per-station, per-shift — achieve 18–27% throughput improvement within 90 days. The four pillars below form the foundation of a production-grade cycle time measurement system that converts every second of data into actionable improvement.
Cycle Time Anatomy — What Makes Up Your Total Cycle
Total cycle time is not a single number. It is the sum of five distinct components, each with different causes and improvement levers. Understanding this anatomy is the prerequisite to accurate tracking and targeted reduction.
Cycle Time KPIs — What Every Dashboard Must Show
These six KPIs define whether your cycle time tracking is delivering actionable insight or just recording numbers. Each KPI is calculated automatically from live production data in iFactory's cycle time dashboard.
Average time per part measured at the station over the last shift. Includes all five anatomy components. Updated every cycle with rolling 60-minute window.
Engineered standard time per part based on method study, equipment specs, and operator work standards. Recalculated after every process change.
Customer demand rate — available production time divided by customer requirement. The heartbeat of the line. If actual CT exceeds takt, you cannot meet customer demand.
Percentage deviation of actual from target. Positive means slower than target. Red-flagged when >10%, yellow when 5–10%, green when <5%.
Target cycle time divided by actual cycle time, expressed as a percentage. The performance factor in OEE. A performance below 85% triggers mandatory root-cause analysis.
Spread between fastest and slowest cycle in the measurement window. High range indicates unstable process — inconsistent operator pace, material variation, or equipment degradation.
Compare Every Cycle Against Target — Live, Per Part, Per Station
iFactory's cycle time dashboard captures actual cycle time per part, compares it against engineered targets, and flags every deviation with root-cause context. See your first station in a 30-minute session.
Cycle Time Tracking Checklist — 30 Items
Each checklist item includes the specific action required, type, priority, and status toggles. The type indicates whether the item is a pass/fail check, a structured selection, or a numeric configuration. Priority marks implementation order. Use the Photo, Required, and Critical toggles to track completion.
| # | Checklist Item | Type | Priority | Photo | Req. | Crit. |
|---|---|---|---|---|---|---|
| 1 | Part-present sensor configured at each station — photo-eye or proximity switch triggers cycle start; sensor must detect every part without false triggers | Pass/Fail | High | ✓ | ✓ | ✓ |
| 2 | Cycle start and end events defined per station — start = part-in-position or cycle-start button, end = part-out or cycle-complete signal with sub-second precision | Pass/Fail | High | — | ✓ | ✓ |
| 3 | PLC cycle counter tag identified — each production cycle increments a counter; counter reset only by authorised Engineering, never by operator | Pass/Fail | High | — | ✓ | ✓ |
| 4 | Micro-stop detection threshold configured — any interruption ≤120 seconds logged as micro-stop with start and end timestamp, reason code optional but recommended | Numeric | High | — | ✓ | ✓ |
| 5 | Speed-loss detection algorithm enabled — actual cycle time compared against rated cycle time per part type; deviation >15% triggers speed-loss event logged to station | Pass/Fail | Med | — | ✓ | — |
| # | Checklist Item | Type | Priority | Photo | Req. | Crit. |
|---|---|---|---|---|---|---|
| 6 | Engineered cycle time standard established per part-station combination — based on time study, motion analysis, or machine spec sheet; not historical average | Pass/Fail | High | ✓ | ✓ | ✓ |
| 7 | Takt time calculated per production line — available operating time per shift divided by customer demand per shift; updated weekly based on order book | Numeric | High | — | ✓ | ✓ |
| 8 | Allowance factor applied to target cycle time — typically 10–15% for fatigue, personal time, and small delays; documented and reviewed quarterly | Numeric | High | — | ✓ | ✓ |
| 9 | Cycle time targets loaded per product variant — different part numbers on the same station may have different engineered cycle times; all must be in the dashboard | Pass/Fail | High | — | ✓ | ✓ |
| 10 | Cycle time target review governance defined — targets reviewed after every process change, new product launch, or quarterly; only Engineering or Industrial Engineering may approve changes | Pass/Fail | Med | — | ✓ | — |
| # | Checklist Item | Type | Priority | Photo | Req. | Crit. |
|---|---|---|---|---|---|---|
| 11 | Cycle time deviation alert threshold configured — red at >10% above target, yellow at 5–10%, green at <5%; alert routed to station operator and line supervisor | Numeric | High | — | ✓ | ✓ |
| 12 | Trended cycle time view enabled per station — last 100 cycles plotted with rolling average, target line, and upper/lower control limits (3-sigma) | Pass/Fail | High | — | ✓ | ✓ |
| 13 | Cycle time histogram displayed per part-station — distribution shape shows whether variation is random (normal) or patterned (bimodal, skewed) indicating assignable cause | Pass/Fail | Med | — | ✓ | — |
| 14 | Cycle time by operator view configured — same station, same part, different operators; highlights training gaps, pacing differences, and best-practice opportunities | Pass/Fail | Med | — | ✓ | — |
| 15 | Cycle time correlation with quality configured — slow cycles flagged for quality inspection; research shows 73% of quality defects occur on cycles outside ±2-sigma of mean | Pass/Fail | Med | — | — | — |
| # | Checklist Item | Type | Priority | Photo | Req. | Crit. |
|---|---|---|---|---|---|---|
| 16 | Out-of-standard action plan linked to each station — operator sees specific corrective actions when actual cycle time exceeds target by more than 10% | Pass/Fail | High | ✓ | ✓ | ✓ |
| 17 | Micro-stop Pareto chart generated automatically per shift — top 10 micro-stop reasons ranked by frequency; reviewed at daily stand-up meeting | Pass/Fail | High | — | ✓ | ✓ |
| 18 | Corrective action tracking integrated with cycle time data — each action linked to station, part, and expected cycle time improvement with target completion date | Pass/Fail | High | — | ✓ | ✓ |
| 19 | Before-and-after cycle time comparison automated — when corrective action is marked complete, dashboard shows pre-action baseline vs post-action actual with statistical significance test | Pass/Fail | Med | — | ✓ | — |
| 20 | Escalation rule defined for sustained deviation — actual > target for 3+ consecutive hours triggers supervisor notification; 8+ hours triggers plant manager review | Pass/Fail | Med | — | ✓ | — |
| # | Checklist Item | Type | Priority | Photo | Req. | Crit. |
|---|---|---|---|---|---|---|
| 21 | Shift-level cycle time summary configured — average CT, min CT, max CT, CT deviation %, and performance % per station per shift with shift-to-shift comparison | Pass/Fail | High | — | ✓ | ✓ |
| 22 | Cycle time gauge chart visible on station-level dashboard — actual CT needle on a gauge with target (green zone), warning (yellow), and out-of-standard (red) bands | Pass/Fail | High | — | ✓ | ✓ |
| 23 | Cycle time waterfall chart available — breaks total cycle time into anatomy components (run, load, idle, micro-stop, speed loss) per station for loss visualisation | Pass/Fail | Med | — | ✓ | — |
| 24 | Cycle time vs takt time comparison displayed on line-level dashboard — each station shown as a bar with actual CT, target CT, and takt line; stations exceeding takt flagged red | Pass/Fail | Med | — | ✓ | — |
| 25 | Daily cycle time report automated — PDF or dashboard link sent to line supervisor, production manager, and plant manager at shift end with key highlights and exceptions | Pass/Fail | Med | — | — | — |
| # | Checklist Item | Type | Priority | Photo | Req. | Crit. |
|---|---|---|---|---|---|---|
| 26 | Weekly cycle time review meeting established — review top-3 stations by CT deviation, review micro-stop Pareto, assign corrective actions with owners and due dates | Pass/Fail | High | — | ✓ | ✓ |
| 27 | Cycle time improvement target set per quarter — specific CT reduction target (e.g. −5% for Station 3) with named owner and defined improvement method | Numeric | High | — | ✓ | ✓ |
| 28 | Cycle time Kaizen events tracked — number of Kaizen events per quarter focused on CT reduction, with average CT improvement per event and total throughput gain | Numeric | Med | — | ✓ | — |
| 29 | Cycle time target recalibration process active — targets reviewed every 6 months or after process changes; if actual CT is consistently <95% of target, target may be too loose | Pass/Fail | Med | — | ✓ | — |
| 30 | Best-practice cycle time sharing process active — when a station achieves sustained performance >95% for 30 days, the method is documented and shared across all lines | Pass/Fail | Med | — | — | — |
Cycle Time Loss Categories — Find Your Biggest Opportunity
Cycle time losses fall into four categories. Each category has different root causes, different detection methods, and different improvement potential. Use this reference to identify which loss category represents your biggest improvement opportunity.
- Worn tooling causing slow cuts
- Spindle speed below rated RPM
- Hydraulic/pneumatic pressure drops
- Sensor misalignment causing false stops
- Harder material reducing cutting speed
- Inconsistent material dimensions causing adjustments
- Moisture or temperature variation affecting processing
- Batch-to-batch material property variation
- Non-standardised work methods
- Fatigue-related pacing slowdown
- Waiting for instructions or tools
- Inexperience on product or process change
- Unbalanced line causing station idle
- Wrong part-feeder setup or jammed feeder
- Changeover-related cycle time degradation
- Batch-size-induced waiting at downstream stations
Cycle Time Tracking Maturity Levels
Cycle time tracking maturity progresses from manual stopwatch studies to real-time per-part measurement with automated deviation response. Each level unlocks faster detection and faster improvement cycles.
Manual
Stopwatch & ClipboardCycle time measured by industrial engineer with stopwatch during time studies. Data collected quarterly or after process changes. No continuous tracking. No deviation alerts. Improvement cycles: 3–6 months.
Average
PLC Counter & SpreadsheetPLC counts total cycles per shift. Average CT calculated as shift time divided by cycle count. No per-part measurement. Micro-stops and speed losses invisible. Improvement cycles: monthly.
Per-Part
Live Per-Part DashboardActual CT measured per part from sensor events. Target CT, takt time, and deviation displayed live. Micro-stops and speed loss tracked per station. Alerts at >10% deviation. Improvement cycles: weekly.
Predictive
AI-Predicted DeviationsCT trend prediction identifies increasing cycle times before target is breached. Root-cause suggestions based on pattern matching. Auto-correlation with tool wear, material lot, and operator data. Improvement cycles: daily.
Cycle Time Tracking Deployment Stages
iFactory deploys cycle time tracking in four stages. Each stage adds measurement granularity and analytical depth — from basic cycle counting to fully automated deviation detection and corrective action tracking.
- Configure part-present sensors and cycle start/end events per station
- Map PLC cycle counter and fault code tags to analytics schema
- Set micro-stop detection threshold at 120 seconds
- Verify cycle data streaming end-to-end from PLC to dashboard
- Load engineered cycle time targets per part-station combination
- Calculate takt time from customer demand and available operating time
- Configure allowance factor (10–15%) and apply to target
- Set deviation alert thresholds with yellow/red colour bands
- Enable trended cycle time view with 3-sigma control limits
- Configure micro-stop Pareto chart and speed-loss detection
- Set up cycle time by operator view for pacing analysis
- Enable cycle time vs quality correlation reporting
- Link out-of-standard action plans to each station
- Deploy automated daily cycle time report with exception highlights
- Establish weekly CT review meeting cadence with Pareto-driven agenda
- Set quarterly CT improvement targets with named owners and methods
Cycle Time Tracking — Frequently Asked Questions
What is the difference between cycle time, takt time, and lead time?
Cycle time is the actual time a station takes to complete one part — measured from part-in to part-out. Takt time is the customer demand rate — available production time divided by customer requirement per period. Lead time is the total time from order receipt to delivery, including queue, processing, and shipping. In practice: if takt time is 60 seconds and cycle time is 75 seconds, the station cannot meet customer demand. The goal is to operate each station at or below takt time. Cycle time is the only one of the three that operators can directly affect moment to moment, which is why real-time cycle time tracking is the most actionable manufacturing KPI.
How do you handle cycle time tracking for multi-product lines with different cycle times?
Multi-product lines require product-specific cycle time targets loaded into the dashboard. When the station changes over to a different product, the dashboard automatically switches to that product's target cycle time, takt time, and deviation thresholds. This is achieved by integrating the PLC product-code signal or the MES work-order routing — the dashboard reads the product being produced and selects the correct reference values. iFactory's cycle time dashboard supports unlimited product variants per station with automatic target switching at changeover. The system also tracks changeover time separately so it does not distort the cycle time measurement for production parts.
How do you detect micro-stops that are invisible to traditional OEE tracking?
Micro-stops — interruptions under 2 minutes — are invisible to traditional OEE systems because most OEE implementations only log downtime events exceeding a configurable threshold, typically 2–5 minutes. To detect micro-stops, the cycle time tracking system must measure the time between consecutive cycle completions at each station. If a station's expected cycle time is 45 seconds and no cycle completes for 90 seconds (2x expected), a micro-stop is inferred even if no fault code was triggered. iFactory's cycle time dashboard detects micro-stops automatically using this cycle-gap method, categorises them by duration, and tracks their frequency per station per shift. This single capability typically recovers 3–10% hidden capacity on most production lines.
What is a good cycle time tracking data collection frequency?
For effective cycle time tracking, data must be collected at the individual cycle level — every cycle completion should generate a record with the station ID, part ID, cycle start timestamp, cycle end timestamp, and calculated cycle time. Aggregated collection (shift-level averages from PLC counters) hides the variation that contains the improvement opportunity. The minimum recommended collection frequency is per-cycle with sub-second timestamp precision. For stations with cycle times under 10 seconds, millisecond precision is recommended. iFactory's edge gateway captures per-cycle events from PLCs with <1 ms timestamp resolution and streams them to the analytics layer in real time.
How does cycle time tracking relate to OEE performance?
Cycle time tracking provides the performance component of OEE — one of the three OEE factors alongside availability and quality. The OEE performance factor is calculated as target cycle time divided by actual cycle time. Without per-part cycle time tracking, OEE performance is estimated using ideal run rate vs actual parts produced, which cannot distinguish between micro-stops, speed losses, and actual cycle time variation. Per-part cycle time tracking gives you the true performance factor, which is typically 5–15% lower than estimated performance because it captures micro-stops and speed losses that average-rate calculations miss. This makes cycle time tracking the foundation of accurate OEE measurement, not just a separate KPI.
What sensors are required to start per-part cycle time tracking?
Per-part cycle time tracking requires at minimum one part-present sensor per station — typically a through-beam photo-eye, retro-reflective sensor, or inductive proximity switch that detects when a part is in position for processing. For automated stations, the PLC's cycle-complete signal can serve as the cycle-end event. For manual stations, a cycle-start button or foot pedal provides the start signal. No additional sensors beyond what most production lines already have are required for basic per-part tracking. To capture the full cycle time anatomy (run, load, idle, micro-stop, speed loss), the system uses the PLC's existing I/O signals — no additional hardware investment is needed. iFactory connects to sensors through the existing PLC infrastructure and does not require dedicated cycle time sensors.
Track Every Cycle Per Part — See Your True Performance in 30 Minutes
iFactory connects to your existing PLCs and sensors to measure cycle time per part, compare against target and takt time, and flag every deviation in real time. No additional sensors, no wiring, no programming required.
