How to use this calculator
- Enter the measured operating data.
- Check that the displayed units match your records.
- Select Calculate to update the result.
- Review the supporting metrics before making a capacity decision.
Find the average time required to produce one good unit during a measured run. Account for downtime and rejected output so the result reflects usable production rather than the clock alone.
A lower cycle time means more good output per unit of operating time. Compare runs only when product mix and measurement boundaries are consistent.
Changeover time can be counted as downtime or scheduled time, but use the same convention across comparisons.
A 480-minute run with 45 minutes down and 212 good units has a good-unit cycle time of about 2.05 minutes.
Use a period that represents normal work and keep the same start and end boundaries when comparing results.
Yes. A genuine zero is valid for optional loss or delay inputs, while required time, demand, or denominator fields must remain above zero.
Reports may use different boundaries, exclude rework or planned stops, or round intermediate values. Match those definitions before comparing figures.
Only through the averages you enter. Run separate calculations when products have materially different processing times or yields.
Recalculate after a staffing, process, routing, demand, or equipment change and use a representative sample rather than a single unusual run.
| Item | How to use it |
|---|---|
| Main result | Use for the primary planning decision described above. |
| Supporting metrics | Use them to locate the source of the result. |
| Reset | Restores the worked example values. |