sumivo

Sumivo · Manufacturing

Takt Time Calculator

Calculate the target production pace from available time and demand.

01 / inputs

min
units

02 / result

TAKT TIME

2 min/unit

Minutes per unit
2 min/unit
Seconds per unit
120 s/unit

Calculation trace

  1. 480 min ÷ 240 units = 2 min/unit
    2 min/unit
    Takt time
  2. 2 min/unit × 60 = 120 s/unit
    120 s/unit
    Takt time in seconds

Maintained by Jack Shi

§

How it works

Find the target time per unit needed to meet demand in a chosen period. Takt time = available production minutes ÷ demand units. The tool reports minutes per unit and multiplies that result by 60 for seconds per unit.

Assumptions & limits

  • Available time is in minutes and must be finite and greater than zero; fractional minutes are accepted. Demand must be a whole number from 1 to 9,007,199,254,740,991 (the largest exactly supported integer). Time has no fixed upper input limit, but both output times must remain finite and positive.
  • Enter available production time and customer demand for the same period, such as one shift. Enter the minutes remaining after any breaks or other time you choose to exclude; the calculator does not subtract them for you.
  • Demand is an input to a uniform target pace. This tool does not measure actual cycle time, balance stations, add scrap allowances or determine staffing. It treats a unit consistently throughout the selected period.

Verified runs

Synthetic examples executed at build revision 24533ff on . Cards round decimal results to 6 significant figures; matching uses full precision and the tolerance below. Matches cover the displayed fields, not every possible input or clinical or engineering validation.

  • Inputs: Available time: 480 min; Demand: 240 units

    Result: Takt time: 2 min/unit; Takt time: 120 s/unit (expected Takt time: 2 min/unit; Takt time: 120 s/unit) ✓

  • Inputs: Available time: 0.5 min; Demand: 1 units

    Result: Takt time: 0.5 min/unit; Takt time: 30 s/unit (expected Takt time: 0.5 min/unit; Takt time: 30 s/unit) ✓

  • Inputs: Available time: 450 min; Demand: 300 units

    Result: Takt time: 1.5 min/unit; Takt time: 90 s/unit (expected Takt time: 1.5 min/unit; Takt time: 90 s/unit) ✓

How these runs were checked

Method: takt-time@1.0.0. Expectations come from the listed test fixtures or hand arithmetic; they are not copied from these executions. Omitted optional inputs use the method defaults. Run dates record execution, not expert review or fresh measurements.

Download all verified runs (JSON) — full inputs, returned values, expectations, timestamps and buildRevision.

  • normal: . Absolute tolerance: 1e-10. Text and booleans match exactly. Full-precision result: Takt time: 2 min/unit; Takt time: 120 s/unit. Expected: Takt time: 2 min/unit; Takt time: 120 s/unit. Expectation: packages/calculator-core/tests/takt-time.test.ts
  • boundary: . Absolute tolerance: 1e-10. Text and booleans match exactly. Full-precision result: Takt time: 0.5 min/unit; Takt time: 30 s/unit. Expected: Takt time: 0.5 min/unit; Takt time: 30 s/unit. Expectation: packages/calculator-core/tests/takt-time.test.ts
  • sensitivity: . Absolute tolerance: 1e-10. Text and booleans match exactly. Full-precision result: Takt time: 1.5 min/unit; Takt time: 90 s/unit. Expected: Takt time: 1.5 min/unit; Takt time: 90 s/unit. Expectation: packages/calculator-core/tests/takt-time.test.ts

Reproduce from the source checkout with pnpm --filter @sumivo/web gen:verified-runs. A rebuild changes execution times; the revision identifies its Git starting point, including any uncommitted changes made for that build.

§

Synthetic example

A 480-minute shift with 30 minutes excluded, and demand for 300 units in that shift. Enter 450 min and 300 units.

  1. Prepare available time: 480 − 30 = 450 minutes. This subtraction happens before entering the value.
  2. Takt = 450 ÷ 300 = 1.5 minutes per unit.
  3. Convert to seconds: 1.5 × 60 = 90 seconds per unit.

Target pace: one unit every 1.5 minutes (90 seconds).

§

Boundary case

With 450 available minutes and demand of 0 units, the calculator shows an error and no takt result. Dividing by zero does not define a finite target pace. Demand of 1.5 units is also rejected because this version requires whole units; 1 unit is accepted.

§

How to read the result

The example allows an average of 90 seconds per demanded unit within the entered time budget. This is a demand-based target, not a measurement of how fast the process actually runs. If actual average output takes longer per unit under the same time budget, it will not meet that demand. Minutes per unit are a duration, not units per minute.

§

Sources and what they support

  • Takt time as available production time divided by customer demand, and its use as the demand-based production pace. The example and the pace comparison follow from that ratio. Lean Thinking and Methods — JIT/Kanban

The integer limit, input validation and omitted planning adjustments are implementation choices. Multiplying minutes by 60 converts to seconds; the shift and excluded time in the synthetic example are chosen inputs, not a recommended schedule.

§

FAQ

Does the calculator remove breaks?
No. Calculate your available minutes first and enter that number. Match demand to that same shift, day or other period.
§

Related calculators

§

SOURCES