Cycle Time Calculator Widget
Embed a cycle time calculator that answers the shop-floor question: how fast are we really going? Enter the net running time and the units produced to get average cycle time and throughput, and add a takt target to see whether the process keeps up with demand.
Live preview
Under the widget on your page: Powered by A2Z Tools
Embed code
<iframe src="https://a2z.tools/embed/w/cycle-time-calculator" title="Cycle Time Calculator by A2Z Tools" width="100%" height="480" style="border:0;width:100%" loading="lazy" allow="clipboard-write"></iframe>
A plain iframe. Works everywhere, including site builders that strip scripts. Adjust height if your content needs more room.
<div data-a2z-widget="cycle-time-calculator" data-height="480"></div> <script async src="https://a2z.tools/embed.js"></script>
Adds a small script (what it does) that sizes the widget to fit its content, loads it lazily and keeps it isolated from your page's CSS.
Works with
How it works
Average cycle time is the net time the process actually ran divided by the units it completed. Net time excludes breaks and stoppages, so 450 minutes producing 300 parts is 27,000 seconds / 300 = 90 seconds a part, a throughput of 40 an hour. This is the measured pace. Takt time is a different quantity: the pace demand requires. When you enter a takt target the widget works out how many units demand would need in the same 450 minutes (27,000 / 100 = 270 at a 100-second takt) and shows the headroom, (takt - cycle) / takt. A negative headroom - a cycle time slower than takt - triggers a warning, because the gap has to be closed with overtime, an extra shift, a second station or a faster method. Fractional units are accepted so batch processes measured in tonnes or litres also work.
Calculation method
- Average cycle time (s) = net production time (min) x 60 / units produced
- Throughput per hour = units produced / (net production time / 60)
- Units required at takt in the same time = net time x 60 / takt time
- Headroom = (takt - cycle time) / takt; negative means slower than demand
Worked examples
Machining cell
Inputs: Net time 450 min; 300 parts; takt 100 s
Result: Cycle time 90 s; 40 parts an hour; demand needs 270 in the same time; 10% headroom
The cell can meet demand with time to spare for small disruptions.
Same cell, higher demand
Inputs: Net time 450 min; 300 parts; takt 75 s
Result: Cycle time 90 s; slower than takt by 20% (warning shown)
At a 75-second takt demand needs 360 parts, 60 more than the cell makes.
Limitations
- Gives an average; it does not show variation between cycles, which matters for line balancing.
- Assumes the units are comparable; a mix of products with very different work content should be split by product.
- Measures one step or one line, not the end-to-end lead time of an order.
Where publishers use it
- Time-study pages for industrial-engineering students
- A CNC job shop's blog comparing machining strategies by seconds per part
- Lean daily-management boards explained on a consultancy website
- Contract manufacturers quoting capacity to a new customer
- Bakery or brewery production blogs measuring batches per hour
Questions
Cycle time or takt time - which do I need?
Both, for different questions. Takt (available time / demand) is the target pace; cycle time (net time / units) is what the process achieves. If 90-second cycle time meets a 100-second takt, the line has 10% spare capacity; at a 75-second takt it falls 20% short.
Should I include breaks and breakdowns in the time?
Use net run time - exclude planned breaks and the time the process was stopped. Including stoppages turns the result into an effective cycle time, which mixes speed with availability and hides the cause of a shortfall.
Is this the same as lead time?
No. Lead time is how long one unit spends in the whole value stream, including queues between steps - often days. Cycle time covers only the work at one step or line and is usually seconds or minutes.
How many cycles should I time?
Industrial engineers usually time 10-20 consecutive cycles and use the average, discarding obvious one-off interruptions. This widget takes the shortcut of total net time divided by output, which averages automatically over a long run.
Why is my throughput lower than 3600 / cycle time suggests?
It should not be, if you entered net time: 3600 / 90 s = 40 an hour, exactly the throughput shown. If your real hourly output is lower, unrecorded micro-stops or waiting time are hiding in the shift.
Sources
- Cycle Time (lexicon) - Lean Enterprise Institute . Defines cycle time as the time required to produce a part or complete a process, as timed by actual measurement. Checked 2026-10-01.
- Takt Time (lexicon) - Lean Enterprise Institute . The demand-side pace the cycle time is compared against. Checked 2026-10-01.
Cite or recommend this tool
If you reference this tool in an article, course or documentation, these formats are ready to copy. They are optional - nothing is added to your site unless you paste it.
A2Z Tools Cycle Time Calculator https://a2z.tools/embed/cycle-time-calculator
<a href="https://a2z.tools/embed/cycle-time-calculator">A2Z Tools Cycle Time Calculator</a>
[A2Z Tools Cycle Time Calculator](https://a2z.tools/embed/cycle-time-calculator)
Cycle Time Calculator by A2Z Tools - https://a2z.tools/embed/cycle-time-calculator
Related widgets
-
The production pace customer demand requires, plus the operators a line needs to hold it.
-
Availability, Performance, Quality and overall equipment effectiveness from shift data.
-
First pass yield per step, rolled throughput yield, scrap rate and optional DPMO for up to six steps.
-
The stock level that should trigger a purchase order, and how many days remain before you hit it.
-
Statistical buffer stock from a service level, demand variability and optional lead-time variability.
-
Economic order quantity, orders per year and the lowest ordering-plus-holding cost, with a cost curve.