Calculator Inputs
Example Data Table
| Total Units | Good Units | Batch Size | Runtime Hours | Downtime Minutes | Setup Minutes | Cycle Time per Unit |
|---|---|---|---|---|---|---|
| 1000 | 960 | 120 | 8.0 | 43 | 45 | 0.6980 min |
| 720 | 700 | 90 | 6.5 | 35 | 30 | 0.6903 min |
| 1500 | 1455 | 150 | 10.0 | 52 | 55 | 0.6467 min |
Formula Used
1. Effective Time
Effective Time = Runtime Minutes − Break Minutes − Planned Downtime − Unplanned Downtime
2. Batches
Batches = Ceiling(Total Units ÷ Batch Size)
3. Added Process Time
Added Process Time = Setup + Changeover + Inspection + Rework + Transport + Queue Wait
4. Loaded Cycle Minutes
Loaded Cycle Minutes = Effective Time + Added Process Time
5. Cycle Time per Unit
Cycle Time per Unit = Loaded Cycle Minutes ÷ Total Units
This model estimates a richer cycle time by including setup, wait, movement, inspection, and rework factors instead of using pure runtime alone.
How to Use This Calculator
- Enter total units produced during the measured production window.
- Enter good units to reflect scrap, defects, or rework demand.
- Provide batch size so transport and queue impacts scale properly.
- Add runtime, breaks, setup, changeover, and downtime values.
- Include inspection and rework seconds for more realistic timing.
- Enter transport and queue minutes per batch if material waits occur.
- Click the calculate button to show results above the form.
- Use CSV or PDF download buttons to save the calculated summary.
Frequently Asked Questions
1. What does production cycle time measure?
It measures the average time required to produce one unit after including operating time and supporting delays. This version also considers setup, transport, queue, inspection, and rework factors for a more complete planning view.
2. Why are good units separate from total units?
Good units show usable output, while total units include rejected items. Separating them helps estimate quality losses, rework effort, and the true effective time consumed per acceptable unit.
3. Should I include break time in runtime?
Yes, you can enter planned runtime for the shift and then subtract breaks separately. That method keeps the calculation transparent and makes it easier to compare staffing schedules across days or lines.
4. What is the benefit of batch-based inputs?
Batch-based transport and queue inputs reflect real factory movement and waiting patterns. This is useful when materials travel between workstations or when partially finished items wait before the next process.
5. How is utilization used here?
Utilization adjusts the base cycle result to show what the cycle time looks like under actual line loading. Lower utilization stretches the effective time needed to deliver the same output.
6. Is this the same as takt time?
No. Takt time is demand-driven and shows the pace needed to meet customer demand. Cycle time measures the actual pace of production based on operating and support time consumed.
7. Can I use this for service processes?
Yes, with adapted inputs. Units can represent tickets, jobs, or requests, and queue or rework fields can represent waiting, review, and correction time inside a service workflow.
8. Why is my cycle time higher than expected?
High values usually come from hidden delays such as setup, downtime, inspection, handoffs, and rework. Including those factors often reveals the real bottlenecks that pure machine runtime misses.