Cycle Time Calculator
Measure how long one unit actually takes on the line.
What this calculator does
Division of measured run time by measured output. No allowance, efficiency factor or standard time is applied.
Inputs and what they mean
- Run time in the period
- — The time the process was actually running..
- Units produced in that run time
- — number value.
How to use it
- Enter your own figures — the calculator never fills in a rate, price or benchmark for you.
- Press Calculate to see the result.
- Read the formula, variables, assumptions and source below the result before you rely on it.
Formula
Cycle time = Run time ÷ Units produced
Worked example
Measured cycle time for a run
Cycle time is measured from the line. Takt time is a demand pace and is calculated separately.
Reading the result
The headline figure is the main answer. Any breakdown underneath shows the parts that make it up, so you can check the working and see what changes when you adjust an input.
Limitations and assumptions
Results depend entirely on the figures you enter and are rounded for display. They are for general information and education, not professional advice.
Reference: Massachusetts Institute of Technology — 2.854 Introduction to Manufacturing Systems
Last reviewed:
Common questions
Formula, source and verification
Measured time per unit: the time the process ran, divided by what it produced in that time.
The question it answers: How fast is this line really going, how long does one unit take, and how long does an order take end to end?
The formula
Cycle time = Run time ÷ Units produced
- RT — Run time
- (min). Minutes the process was actually running.
- U — Units produced
- (count). Units produced in that run time.
Units: Minutes in; minutes per unit out, also shown in seconds.
What kind of calculation this is
Deterministic formula. The same inputs always give the same answer. The maths is fixed and does not depend on judgement.
Method
Division of measured run time by measured output. No allowance, efficiency factor or standard time is applied.
Assumptions built into the result
- Mathematical: Every quantity, time and rate is the figure the user entered, measured over the period they describe.
- Mathematical: Times and counts refer to the same period and the same resource.
Figures this calculator will never guess for you
- No industry benchmark, target utilisation or target availability is supplied or applied.
- No shift length, break allowance, downtime allowance or standard rate is assumed.
- Optional components are excluded from the result when left at zero.
Limitations
- Arithmetic over the figures entered — it cannot tell whether the measurements behind them are right.
- A measured result, an industry benchmark and an organisation's target are three different things; only the entered figures are used.
- Cycle time is measured from the line; takt time is a demand pace. Comparing them is the point, and they are never the same calculation.
Source and version
- Standard or reference
- Manufacturing systems — throughput, cycle time, work in process and line balancing — MIT OpenCourseWare (MIT OpenCourseWare 2.854 Introduction to Manufacturing Systems — throughput is output per unit of time, cycle time is run time divided by the units produced, line capacity is set by the slowest station, and balance efficiency compares total work content with the number of stations multiplied by the longest station time.)
- Published source
- Massachusetts Institute of Technology — Fall 2016
- Formula version
- Version 1
- Verification
- Reviewed against the cited source on
- How much weight the source carries
- Academic
- Applies to
- Currency
- The result is a ratio or index, so it does not depend on currency.
Related tools
Work out the hourly rate to charge a client so that target margin is met after overhead and non-billable time.
Find the true hourly cost of an employee once benefits, payroll cost and overhead are included.
Size a software application from its data and transaction functions before estimating effort or cost.
Estimate development effort, schedule and average team size for a software project of a known size.
Express cloud spend as a cost per customer, per transaction or per other business unit.
Set the rate used to apply manufacturing overhead to jobs for the coming period.