OEE & Factory Performance worked example

Andon Response Time with total response time of 450 min: a worked example

This scenario runs the andon response time calculation on the strong side: total response time of 450 min, with every other input held at its documented default. Use it to track how fast support responds to line stops in OEE & Factory Performance.

The inputs for this scenario

  • Total response time: 450 min (raised for this scenario; the documented default is 180)
  • Number of andon calls: 24 calls (unchanged)

Working through the calculation

  • Applying the documented formula (Average andon response time = total response time รท number of calls) to the inputs above produces each figure below.
  • At this operating point the engine returns 18.75 min for avg response time, the number this scenario is built around.
  • At this operating point the engine returns 450 min for total response time.
  • At this operating point the engine returns 24 calls for andon calls.
  • At this operating point the engine returns 3.2 calls / hr for calls per hour basis.

How this compares with the baseline

  • Against the tool's baseline example, where total response time sits at 180 min and the headline result is 7.5 min, this scenario comes in 150% above the baseline at 18.75 min.
  • Use it during shift reviews or kaizen events to judge whether your andon support model is fast enough to keep operators confident in stopping the line. Treat this as a target state: the delta against the baseline quantifies what the improvement is worth before you commit to chasing it.

Results at a glance

  • Avg response time: 18.75 min (headline result)
  • Total response time: 450 min
  • Andon calls: 24 calls
  • Calls per hour basis: 3.2 calls / hr

Run it with your numbers

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

Last reviewed 2026-05-12.