MTBI: the 74-second pulse of production
Mean Time Between Interruptions is the simplest vital sign a line has: how long it runs, on average, before something stops it. Across 62 lines we measured a pulse of just 1 minute and 14 seconds. Here's why that number should worry you, and how to read it honestly.
- MTBI is the average run-time between interruptions, a line's heartbeat.
- The portfolio-wide weighted average was a frantic 1m 14s.
- At that pulse, interruption time adds up fast, and each stop is too short to code.
- The steadiest sites in the study averaged 3m 27s between interruptions.
Measure this on your own line. One sensor per line, live within 48 hours of the kit arriving.
A line has a heartbeat
Every production line runs, stops, and runs again. Measure the average length of those runs and you have its pulse: Mean Time Between Interruptions. It is the most honest one-number summary of how stable a line really is, and unlike a shift total it can't be flattered by a good hour.
Augos calls those short halts interruptions (what standard OEE calls minor stops or micro-stops), and MTBI counts every one of them.
The number that stops you
Across the 62 lines in our study, the weighted-average MTBI was 1 minute and 14 seconds. Seventy-four seconds of running, then a stop. Then seventy-four more. That is not a line producing with the occasional hiccup. It is a line trapped in a constant cycle of interruptions, each one too short to code.
Performance losses on a fragmented line don't come from a slow machine. They come from a machine that is never allowed to run. MTBI is the metric that makes that visible, where a shift total hides it.
The steadier benchmark
The stable cohort in the study ran at an MTBI of about 3 minutes 27 seconds, nearly three times longer between stops. That is the benchmark worth chasing.
Reading MTBI honestly
One caution: a raw MTBI can mislead if you ignore the line's stop threshold, the delay before a pause is counted. A lenient threshold can make a chronically stuttering line look calm. That's why MTBI should always be read against the Threshold Exposure Index. Read together, they tell you both how fast the pulse is and whether you can trust the reading.
MTBI is one of the central metrics in the Interruption Whitepaper, and the raw material of the fragmentation gap.
What does MTBI measure?
Mean Time Between Interruptions is the average length of time a line runs before it is interrupted. A high MTBI means long, stable runs; a low MTBI means the line is constantly stopping and restarting.
Why is a 1m 14s MTBI a problem?
At roughly seventy-four seconds between stops, the time lost to interruptions adds up fast, and each stop is too short to get a reason code. In OEE that time sits inside performance, so the line looks slow even at its rated speed.
How is MTBI different from MTBF?
Mean Time Between Failures counts breakdowns, the longer stops that get a reason code. MTBI counts interruptions, including the short, high-frequency ones that never trigger a code but do the most cumulative damage.
Must MTBI be read with anything else?
Yes. A raw MTBI can be flattered or hidden by the line's stop threshold. Always read it alongside the Threshold Exposure Index so you know whether the number reflects reality.
See it on your own line.
A 30-minute call with a manufacturing specialist. We look at one of your lines together and show you what the first week of data would say about it.
- Live within 48 hours of your kit arriving
- One sensor, one terminal, no PLC and nothing to integrate
- R4,950 per line per month, ex VAT. 90 days, then a month's notice