PlantOps BI

KPI Library / Production

Takt Time

Formula: Available production time ÷ customer demand
Typical range: No universal benchmark: takt time is specific to each line and product, and resets whenever demand or available time changes

Takt time is the pace a line must hit, one unit produced every so many seconds, to keep up with actual customer demand over the available production time. It is not a measure of how the line performed, like cycle time; it is the target the line gets measured against, derived entirely from the order book and the calendar.

What good looks like

Because takt time is a demand-driven target rather than a performance outcome, “good” doesn’t mean low or high, it means accurate and current. A shorter takt time signals stronger demand relative to available capacity, and a longer one signals the opposite; neither is automatically good news on its own. What matters operationally is whether cycle time stays at or below takt time. A line running comfortably under takt has slack; a line running above it is falling behind regardless of what OEE or attainment say.

Where this metric gets gamed is on the “available time” side of the formula. Inflating available time (not deducting breaks, changeovers, or planned maintenance) makes takt time longer and easier to hit, which flatters the line without changing whether it can actually meet demand. The other common failure is letting takt time go stale: recalculating it only at the quarterly S&OP cycle while demand shifts week to week underneath it.

Takt Time in Power BI (DAX)

With a shift calendar table and a demand fact by date:

Available Minutes =
SUM ( dim_shift_calendar[planned_minutes] )
    - SUM ( dim_shift_calendar[break_minutes] )

Daily Demand =
DIVIDE (
    SUM ( fact_demand[units_ordered] ),
    DISTINCTCOUNT ( fact_demand[order_date] )
)

Takt Time (sec) =
DIVIDE ( [Available Minutes] * 60, [Daily Demand] )

Cycle Time vs Takt (sec) = [Avg Cycle Time (sec)] - [Takt Time (sec)]

A positive Cycle Time vs Takt means the line is running slower than demand requires; that is the number to put in front of a supervisor, not takt time alone.

Common mistakes

  1. Using planned production time instead of net available time. Forgetting to subtract breaks, changeovers, and PM time makes takt time look more achievable than it is.
  2. Recalculating takt time too infrequently. A number set once a quarter goes stale the moment demand moves, and the line ends up chasing a target that no longer reflects reality.
  3. Confusing takt time with cycle time on a dashboard. They answer different questions (what pace is required versus what pace is happening), and mislabeling one as the other misleads the floor about whether they’re actually behind.