Micro-stop
A micro-stop is a brief interruption on a line or cell, commonly on the order of seconds up to a couple of minutes, that someone on the station clears without calling maintenance or opening a downtime record. Jams, sensor resets, a missing kit, a late stillage, and a short wait for the next pallet all sit in this family. The board can look calm while the hour is already leaking.
Plant teams care because standard overall equipment effectiveness (OEE) practice often books only stops long enough to deserve a reason code as availability loss. Shorter stops then hide inside performance, or they never get written down at all. Three waits of two minutes inside one hour are already six minutes. Across a shift that is a real slice of capacity, and it is a common reason Saturday gets booked to repurchase output the scheduled week already paid for.
A micro-stop is not the same object as a coded breakdown. Breakdowns have a trade, a spare, and a mean time to repair clock. Micro-stops are often organizational: material not at the station, a radio auction still open, a feeder blocked. Treating every red minute as a maintenance fault sends the wrong crew and leaves the quiet loss unnamed.
Key Components
Duration cutoff - The plant rule for which stops earn a code. Anything under that cutoff is easy to miss on a paper log.
Cause family - Machine jam, material wait, changeover overrun, or a blocked handoff. The fix depends on which family it is.
Who clears it - Usually the operator, in seconds, which is why the event never reaches CMMS.
Capacity math - Count times length, not the drama of one event. Short and frequent beats rare and long on many lines.
Where it lands in OEE - Availability if coded as downtime, performance if the machine is treated as still running. Output lost is the same either way.
Applications in Manufacturing and Logistics
On assembly and packaging lines, micro-stops cluster around material arrival, label jams, and sensor trips the operator resets by habit. In internal logistics the same minutes show up as a station waiting on a material call-off that never became a claimable job. Andon may flash and still leave no code if the light clears before anyone writes the reason.
An operational digital twin does not replace the downtime engine. It can place the wait next to mover location and order state so the quiet minutes have a where and a why. That packaging is the operations cost page under quiet minutes that never hit the downtime board.
Benefits and Challenges
Benefit: once short stops are counted, recovered minutes can be argued with production instead of only with coded downtime. Challenge: logging every thirty-second reset by hand creates a second job and still undercounts. Automatic capture plus a reason family beats a longer paper log. Another challenge is blaming the operator for waits that are really late material.
Related Terms
Muda is the lean name for the waste. OEE is where the minutes hide or show. Andon is the signal. Material call-off is a common logistics cause. MTTR covers the longer repair clock, not the reset the operator already finished.
Frequently Asked Questions
Do micro-stops count as downtime? On the machine they are lost time. On the report they count only if your cutoff and your capture method record them. Many plants see them as a vague performance gap.
How short is short? Plants often treat stops under about two to five minutes as minor. Use your own coding rule. The cost is the minutes, not the label.
Can a calm downtime board still be losing capacity? Yes. If operators clear the stop and never code it, the board stays green while output is already behind.
What is the first useful count? Stops per hour and average length on one line for one week, split into machine resets versus material waits. That split tells you whether maintenance, logistics, or both own the bill.