NOTQIN — OT Track

Takt Time

2 min read

Takt Time

Definition

The demand-driven production pace. The maximum time per unit allowed to meet customer demand. From German Takt = beat / pulse. Foundational concept in TPS / lean.

If Cycle Time < Takt → you’re keeping up (and could potentially run fewer shifts). If Cycle Time > Takt → you cannot meet demand without overtime, extra shift, or process improvement.

Formula

Takt Time = Available Production Time / Customer Demand

Both in the same unit window (typically a shift or a day).

Required data

  • Available production time (shift length minus breaks, planned maintenance)
  • Customer demand quantity over the same window

Possible data sources

  • Customer EDI orders (auto Tier-2: weekly Renault/Stellantis releases)
  • ERP demand plan
  • Shift calendar

Factory example

Auto Tier-2 wiring-harness line.

  • Available time: 7.5 hours/shift × 60 = 450 min/shift
  • Demand: 360 harnesses/shift (from Renault weekly release)
  • Takt time = 450 / 360 = 1.25 min/harness = 75 sec/harness

If actual cycle time = 90 sec/harness → 20% short of takt → can’t ship.

Economic impact

  • Direct link to OTIF risk (if not at takt, you’ll miss shipment windows)
  • Drives line-balancing — every workstation must run at or under takt
  • Inputs to JIT scheduling

Common mistakes

  • Conflating takt with cycle time (takt is set by the customer, cycle is set by the process)
  • Recomputing takt monthly when demand actually varies weekly → planning lags reality
  • Treating takt as a constant when product mix changes within a shift
  • Setting takt by average demand when peak demand is the binding constraint

See also

Graph View

Backlinks