Cycle time is the elapsed time required to complete a defined process or process step. In supply chains, different cycle-time measures help teams understand how quickly orders, purchases, receipts, picks, production and deliveries move through the system.
Cycle Time vs Lead Time
The terms are sometimes used differently across organizations, so every KPI should have a written start and stop definition. A useful distinction is that cycle time measures the duration of a process being analyzed, while lead time often represents the elapsed time experienced between a request and fulfilment. Either can include waiting depending on the definition.
Common Supply-Chain Cycle Times
| Metric | Example start | Example finish |
|---|---|---|
| PR-to-PO cycle time | Approved requisition | PO issued |
| Supplier lead time | PO release | Goods receipt |
| Dock-to-stock | Vehicle arrival / unloading | Inventory available for use |
| Order fulfilment cycle | Customer order accepted | Shipment dispatched or delivered |
| Pick cycle time | Pick task release | Pick confirmation |
| Production cycle | Production start | Finished output complete |
Basic Calculation
Cycle Time = Finish Timestamp − Start Timestamp
For a group of transactions, report more than the average when possible. Median, percentile and variation can expose delays hidden by a simple mean.
Worked Example
An approved requisition is released at 09:00 Monday and the PO is issued at 15:00 Tuesday. If the organization measures elapsed clock time, the cycle is 30 hours. If the KPI is defined in working hours, weekends and non-working hours must be treated consistently.
Process Cycle Efficiency
A useful Lean measure is Process Cycle Efficiency = Value-Added Time ÷ Total Lead Time × 100%. If actual processing takes 45 minutes but the request spends four days waiting between steps, improving the 45 minutes will have little effect compared with removing the queues.
How to Improve Cycle Time
- Remove unnecessary approvals and handoffs
- Reduce batching and queues
- Automate repetitive data transfer where the process is stable
- Improve supplier or resource availability
- Set exception rules instead of manually reviewing every normal transaction
- Analyze variation, not only the average
Related: Value Stream Mapping and Variation Analysis.
Interview Question
Question: Why should you define the start and stop points before comparing cycle time across teams?
Answer: Because two teams may use the same KPI name but measure different intervals. A comparison is meaningful only when the process scope, timestamps, working-time rules and exceptions are defined consistently.
Download the Practical Workbook
Use the SCMANA Supply Chain Cycle Time Calculator to calculate order, procurement and warehouse cycle-time measures with sample inputs.
Comments 2