Takt Time
Takt time from your shift pattern and customer demand, with the stations a given cycle time needs and the capacity they give.
The takt in seconds per unit, demand per hour, how many stations or operators a process cycle time needs, the load on the ones you have, and whether daily capacity covers demand.
Example: Demand of 400 units in a 450-minute shift with 30 minutes of breaks gives a takt time of 63 seconds per unit.
The customer
sets the beat.
Takt is demand, cycle time is capability.
Takt time
Takt = available production time ÷ customer demand, both on the same day. Available time is the shift minus breaks, times shifts per day; weekly or monthly demand is divided by the working days you enter. Two 8-hour shifts with 30-minute breaks and 1,000 units a day give 900 minutes ÷ 1,000 = 54 seconds: one unit must leave the line every 54 seconds, on average, to keep up.
Cycle time, stations, and load
Cycle time is how long one station takes per unit; it must be at or below takt or the work has to be split. Stations needed = ⌈cycle ÷ takt⌉. With a chosen number of stations, load = cycle ÷ (takt × stations), and capacity per day = available time × stations ÷ cycle. Above 90 % load there is little room for variation, changeovers, or absence, so the utility says so.
Planned OEE, and what is left out
Lines do not run at 100 %. Entering a planned OEE shortens the available time and gives an effective takt to design to; the plain takt is still shown, because that is what the customer demands. Not covered: mixed-model weighting, changeover time as a separate term, or shift patterns that differ by day. Nothing you enter is stored; the same four anonymous usage counts as the rest of the site apply.