Micro-Stop Counter and Tally Sheet
Stand at the line and tap one big button when it stops and again when it runs. The counter times every stop, splits micro stops from breakdowns and shows what they cost. No phone at the line? Enter your counts, or print the blank tally sheet.
Count stops at the line
Keep this page open. A reload or a locked screen does not lose the count.
Reason for the last stop (optional, tap again to remove)
Edit reason labels
Enter what you counted
From a paper tally, a video or a stopwatch. The defaults are the worked example below.
Micro stops by reason
Sorted by count, because a micro stop costs most through how often it happens.
Stop log
| # | Started | Length | Type | Reason |
|---|
Newest first. Copy as CSV keeps every stop with its start and end time.
Get a second opinion on this result
Send it to the OEE Lab team. A Fabrico OEE specialist reads your numbers and gets back to you by email. To keep the result, use Copy as CSV or Print above.
No newsletter, no spam. What you enter here, this result and its link go to the OEE Lab team. Privacy
A phone catches the stops you see. A signal catches all of them.
Fabrico shows OEE live per line and per shift. Stops come from the PLC or IoT sensors, so every short stop is timed, and the operator gives the cause. AI cameras count output where a machine has no usable signal, and where cameras are fitted, video of a stop is streamed on request, not stored. EU customers are hosted on AWS in Frankfurt.
Request a demoHow to run a 30-minute micro-stop study
This page is the counting tool. For the background, read the OEE Lab primer on micro stops and the hidden factory, or Fabrico's guide to what micro stops are and why OEE misses them.
- Pick one machine. Start with the constraint, or the machine operators complain about. Write down the product and its ideal rate.
- Agree the threshold. Use the line your plant already uses for logging downtime. The counter starts at 2 minutes.
- Stand where you can see the infeed and the outfeed. A machine waiting for product looks like a jam from the wrong side. Tell the operator you are counting stops, not judging people.
- Tap Start observing while the line runs. Tap Stop the moment it stops and Running the moment it runs again.
- Tap a reason if you can see it. If not, ask the operator after the restart, then tap it. The chip always tags the last stop.
- Do not help. If you clear jams yourself, you change what you are measuring. After 30 minutes, tap Finish and Copy as CSV.
- Repeat on another shift and with another product before you trust the number.
On paper, print the tally sheet, tick one box per stop under its reason, and time each stop with a phone stopwatch. Then type the lengths into Enter counts.
The formulas
A micro stop is a stop shorter than the threshold. A stop at or over it is a breakdown. Observed time is treated as planned production time.
Micro stops per hour = micro stops ÷ observed min × 60
OEE points lost = micro-stop time ÷ observed time × 100
Mean time between stops = run time ÷ all stops
- Run time = observed time - all stop time, breakdowns included. The mean time between stops page explains the measure in depth.
- Mean micro stop = micro-stop time ÷ micro stops.
- Lost per shift = micro-stop share × planned minutes per shift. Lost per year = lost per shift × shifts per year.
- Units lost = lost minutes × ideal rate per minute. These are units the line could have made at full speed, so the real gain from a fix is smaller.
Which OEE factor? Most OEE practice books micro stops as a performance loss, because they are too short to log as downtime. Nakajima's six big losses put idling and minor stops under performance. Some plants log every stop as downtime and so book them in availability. The OEE points lost are the same either way; only the factor that shows them changes. Booked in performance, the factor loss is micro-stop time ÷ (observed time - breakdown time).
Worked example
The Enter counts defaults. A filler is watched for 30 minutes with a 2 minute threshold. Its ideal rate is 60 units a minute, a shift has 450 planned minutes, and the plant runs 500 shifts a year. The 13 stops last 15, 30, 10, 25, 20, 150, 35, 12, 18, 22, 8, 25 and 20 seconds.
| Step | Calculation | Result |
|---|---|---|
| Breakdowns | 150 s ≥ 120 s | 1, 150 s |
| Micro stops | 12 stops, sum | 12, 240 s |
| Micro stops per hour | 12 ÷ 30 × 60 | 24.0 |
| OEE points lost | 240 ÷ 1,800 × 100 | 13.3 |
| Mean micro stop | 240 ÷ 12 | 20 s |
| Run time | 1,800 - 240 - 150 | 1,410 s |
| Mean time between stops | 1,410 ÷ 13 | 108 s |
| Performance factor loss | 240 ÷ (1,800 - 150) | 14.5% |
| Lost per shift | 13.3% × 450 | 60 min |
| Units lost per shift | 60 × 60 | 3,600 |
| Per year | 60 min × 500 ÷ 60 | 500 h, 1,800,000 units |
Raise the threshold to 5 minutes and the 150 second stop becomes a micro stop too: 13 micro stops, 390 seconds, 26 per hour and 21.7 OEE points. The stops did not change, only the line you drew. That is why the threshold belongs on every sheet.
Thirty minutes is a small sample. Treat a yearly figure from one half hour as a size of the problem, not a forecast. To put a money figure on it, use the hidden factory calculator.
Common mistakes
- Watching only one good half hour. Stops cluster at start-up, after breaks and after changeovers. Spread your studies across the shift.
- Counting slow running as a stop. A machine that keeps cycling, just slowly, has a speed loss, not a stop. Tap only when output stops.
- Changing the threshold between studies. The counter reclassifies every stop, but two studies only compare if they use the same threshold.
- Counting the same minutes twice. If a stop is in the downtime log, it must not also sit in the speed loss. Each lost minute goes in one place.
- Guessing the reason from where you stand. Starved and blocked look like a jam if you cannot see the conveyors. Ask the operator. The conveyor short stops guide shows how to tell them apart.
- Stopping at the count. The count tells you where to look. The guide to reducing micro stops covers what to do next, starting with the top bar of the reason chart.
Micro-stop counter FAQ
How do I count micro stops without software?
Stand at the line with this counter open on your phone, or print the blank tally sheet. Tap or tick each stop as it happens, note the reason, and time each one with a stopwatch if you can. Thirty minutes is enough for a first look.
What threshold should I use for a micro stop?
There is no single standard. Use the same line your plant uses for logging downtime: stops shorter than that are the ones nobody writes down. The counter starts at 2 minutes. Change it any time and every stop is reclassified.
Do micro stops count against performance or availability?
Most OEE practice books them as a performance loss, because they are too short to log as downtime. Some plants log every stop as downtime and book them in availability. The OEE points lost are the same either way; only the factor that shows them changes.
How long should a micro-stop study last?
At least 30 minutes of normal running. Then repeat it on another shift and with another product before you trust the number, because one half hour can be a good or a bad one.
Does the counter keep my data if I reload the page?
Yes. The stop times are saved in this browser on this device, so a reload or a locked screen does not lose the observation. They are not sent to OEE Lab. Use Copy as CSV to keep a copy, and Clear to start again.
Why does the machine count more stops than I do?
A person misses stops that last a second or two, and attention drops after a while. A PLC or sensor signal catches every one. Treat a hand count as a floor, not the full number.