Planning worked example

Lead Time with queue time of 40 hr: a worked example

Push queue time up to 40 hr and the picture changes. This example computes every intermediate figure at that operating point. Use when quoting delivery dates or comparing batch size and queue-time tradeoffs.

The inputs for this scenario

  • Queue time: 40 hr (raised for this scenario; the documented default is 16)
  • Setup time: 2 hr (unchanged)
  • Run quantity: 850 units (unchanged)
  • Cycle time: 38 sec / unit (unchanged)
  • Inspection time: 3 hr (unchanged)
  • Move / wait time: 4 hr (unchanged)
  • Working hours per day: 8 hr / day (unchanged)

Working through the calculation

  • Applying the documented formula (Run hours = quantity × cycle time ÷ 3,600) to the inputs above produces each figure below.
  • At this operating point the engine returns 7.25 days for lead time, the number this scenario is built around.
  • At this operating point the engine returns 57.97 hr for total lead time.
  • At this operating point the engine returns 8.97 hr for run time.
  • At this operating point the engine returns 69 % for queue share.

How this compares with the baseline

  • Against the tool's baseline example, where queue time sits at 16 hr and the headline result is 4.25 days, this scenario comes in 70.65% above the baseline at 7.25 days.
  • It sums queue, setup, run (quantity times cycle time), inspection, and move time into total hours, converts to working days, and reports queue's share of the total. The value of this scenario is the size of the gap it exposes: that gap, priced out over a year, is the budget you can justify spending to close it.

Results at a glance

  • Lead time: 7.25 days (headline result)
  • Total lead time: 57.97 hr
  • Run time: 8.97 hr
  • Queue share: 69 %

Run it with your numbers

  • Every input above is editable in the live Lead Time calculator, which recalculates instantly and can be shared with the inputs intact.

Last reviewed 2026-05-12.