Key takeaways
See how micro-stops feed into the OEE calculation.
A micro stop (or minor stop) is a short, operator-cleared production stoppage, typically under five minutes, caused by jams, misfeeds, sensor blockages, or quick cleaning. It sits inside the Performance factor of OEE as part of the Six Big Losses, and is the single most under-reported loss on most production lines.
Micro stops are brief interruptions in production that the operator resolves without calling maintenance. According to Vorne's Six Big Losses framework, Idling and Minor Stops "accounts for time where the equipment stops for a short period of time (typically a minute or two) with the stop resolved by the operator." Common terminology used interchangeably includes minor stops, small stops, idling, and chokes.
The practical industry threshold is roughly five minutes. Stops shorter than that are typically classified as minor stops; longer events are treated as breakdowns or unplanned downtime and routed to maintenance. That distinction matters because the two losses live in different parts of the OEE equation and demand very different responses.
OEE has three factors: Availability, Performance, and Quality. Micro stops are classified as a Performance loss because the line is technically still in its run state and the operator clears the issue in seconds. They eat into the gap between ideal cycle time and actual cycle time, which is exactly what the Performance factor measures. For the full breakdown of the framework, see our guides to the Six Big Losses and OEE calculation.
Because they are too brief to log and too frequent to remember. A 90-second jam that an operator clears, restarts, and moves past will almost never make it into the shift log. By end of shift, the count is gone. Vorne notes that "the underlying problems are often chronic (same problem/different day), which can make operators somewhat blind to their impact" and that "most companies do not accurately track Idling and Minor Stops."
The result is a measurement blind spot. Independent industry research summarised by Evocon found that the effect of speed loss on OEE is at least 9 to 15 percent, and probably higher because of measurement difficulties and the tendency to set speed targets too low. When operators log micro stops by hand, the underreporting compounds week over week, and Performance numbers drift upward into a false sense of confidence.
Consider a packaging line with a 30-second ideal cycle and a 16-hour run day. If micro stops cost an average of 90 seconds each, and 15 of them per shift go unlogged, that is 22.5 minutes per shift of invisible Performance loss, around 2.3 percent of available run time, never attributed to a fixable cause. Multiply that across a year and the line is producing tens of thousands of fewer units than its OEE report claims.
Performance is calculated as (Ideal Cycle Time x Total Count) / Run Time. Micro stops do not pause the Run Time clock because they are too short to trigger an availability event, but they slow the actual cycle. So they hide inside the denominator and the count, surfacing as a Performance percentage that is lower than the line's cycle-tag data suggests it should be.
| OEE factor | What it measures | Where micro stops appear |
|---|---|---|
| Availability | Run Time / Planned Production Time | Not here, stops are too short to trigger |
| Performance | (Ideal Cycle Time x Total Count) / Run Time | Here, as the gap between ideal and actual cycle |
| Quality | Good Count / Total Count | Occasionally, when restarts produce scrap |
If your team is still untangling the basics, our explainer on what OEE is and the difference between utilization and OEE are good starting points.
Vorne's reference list of common causes for Idling and Minor Stops includes "misfeeds, material jams, obstructed product flow, incorrect settings, misaligned or blocked sensors, equipment design issues, and periodic quick cleaning." On most lines, three or four root causes generate the long tail.
You cannot fix what you cannot see, and you cannot see micro stops with a clipboard. The only reliable method is automatic capture, layered in three steps.
Pull cycle counts and machine-state tags directly from the PLC. Any cycle that is longer than the ideal by a defined threshold (often 1.5x to 2x) gets flagged as a candidate stoppage. This alone removes most of the under-reporting problem.
Raw PLC data tells you a stop happened, not why. Some plants close this gap with a pop-up reason code on an HMI, but that re-introduces the operator-logging problem. Computer vision at the choke point captures the true cause, jam, misfeed, missing label, sensor occlusion, without asking anyone to type anything. Fabrico's platform pairs PLC capture with vision specifically for this loss, which is why micro stops are the single strongest argument for moving off paper logs.
Detection without action is just a prettier report. When the same micro-stop signature repeats, it should generate a prioritized digital work order, parts pre-staged, with a QR-enforced checklist on the technician's phone. That is the fault-to-fix loop, and it is the difference between a dashboard and a fix. If your maintenance side is still paper-based, our guide to what a CMMS is covers the basics.
Operators often confuse the two because both feel like "the line stopped." The OEE framework is unambiguous, and treating them as one bucket erodes both metrics.
| Attribute | Micro stop (minor stop) | Unplanned downtime (breakdown) |
|---|---|---|
| Typical duration | Under 5 minutes | 5 minutes or more |
| Resolved by | Operator at the machine | Maintenance technician |
| OEE factor hit | Performance | Availability |
| Six Big Losses bucket | Idling and Minor Stops | Equipment Failure |
| Most common gap | Under-reporting | Late notification of maintenance |
If your event durations are bunching just above five minutes, it is usually a classification problem, not a process one. See our deeper write-ups on unplanned downtime and availability.
Total Productive Maintenance treats micro stops as a leading indicator of degraded condition. A line that produces more micro stops this month than last is telling you something has drifted, a wear surface, a sensor mount, a material spec. Folding micro-stop frequency into your preventive maintenance schedule turns it from a reactive nuisance into a predictive signal. The same data feeds into your TPM program as the Focused Improvement metric for the affected asset.
Micro stops do not show up in classic MTBF and MTTR because they are below the maintenance-call threshold. That is exactly why the Performance factor of OEE and the Six Big Losses exist, to surface the losses that reliability metrics ignore.
There is no single benchmark, because micro-stop frequency is a function of line type, material, and product mix. A useful working target is to drive operator-logged micro stops and PLC-detected micro stops within 10 percent of each other within 30 days. Once the measurement is honest, the Performance number is honest, and the improvement work starts producing real OEE gains rather than reporting gains.
If your line is in packaging, food, or pharma, expect to find more micro stops than you fear. Manual logs in those environments typically miss a large share of short stoppages, and the recovered minutes show up directly in throughput. [INSERT VERIFIED PROOF POINT, operator to confirm]
Fabrico is built for exactly this loss. The platform reads OEE and cycle times directly from the PLC, uses computer vision at choke points to attribute the true cause of each short stoppage, and turns recurring signatures into prioritized, parts-ready digital work orders on the technician's phone, with QR-enforced checklists at the asset. That is the fault-to-fix loop, in one system, EU-built and EU-hosted.
If you want to see what your hidden micro-stop loss actually is, book a short Fabrico demo and we will walk through it on your line, not a slide.
There is no difference. Micro stop, minor stop, small stop, and idling are used interchangeably for short, operator-cleared production stoppages, typically under five minutes, that fall under the Performance factor of OEE.
The widely used industry threshold is under five minutes. Stops longer than that are usually reclassified as unplanned downtime or breakdowns and routed to maintenance, while shorter stops are treated as Performance loss inside the Six Big Losses framework.
Because micro stops are too brief to log in the moment and too frequent to remember at the end of a shift. Vorne notes that the underlying problems are often chronic, which makes operators somewhat blind to their impact, and that most companies do not accurately track Idling and Minor Stops.
Micro stops are a Performance loss, not an Availability loss. They do not stop the Run Time clock because the line is still in a run state, but they slow the actual cycle, which shows up as a gap between ideal and actual cycle time in the Performance factor of OEE.
You read cycle-count and machine-state tags directly from the PLC and flag any cycle longer than a defined threshold (often 1.5x to 2x ideal) as a candidate stoppage. Adding computer vision at the choke point attributes the true cause without asking operators to type a reason code.
Industry analysis summarised by Evocon estimates the effect of speed loss on OEE is at least 9 to 15 percent, and probably higher because measurement difficulties and low speed targets hide the real impact. The exact share depends on line type, material, and product mix.
Login
Blog