20 Micro-Stops per Shift: The Downtime Nobody Reports

A machine stops for 45 seconds. The operator removes a blocked part, presses reset and production continues. Nobody calls Maintenance. Nobody writes a report. Nobody considers it a breakdown. Then it happens another 19 times during the same shift.

Individually, these interruptions seem insignificant. Together, they can consume a surprising amount of production capacity. And because they are short, quickly resolved and often considered part of normal production, micro-stops can remain almost invisible to management.

A major machine failure gets attention. A 45-second stop usually does not.

But production loses time in both cases.

What can 45 seconds really cost?

The problem with micro-stops is not their duration—it is their frequency.

Consider an illustrative production line experiencing 20 micro-stops per shift, each lasting an average of 45 seconds.

The calculation initially looks harmless:

20 × 45 seconds = 15 minutes per shift.

But the same line operates three shifts per day:

15 minutes × 3 shifts = 45 minutes per day.

Across 250 production days, those apparently insignificant interruptions accumulate to:

187.5 hours of lost production time per year.

If the line normally produces 120 good units per hour, the theoretical production capacity represented by those interruptions is approximately 22,500 units per year.

What people notice	What production can lose
One micro-stop	45 sec
20 per shift	15 min
3 shifts	45 min/day
250 production days	187.5 h/year
At 120 units/hour	22,500 units/year

These figures are illustrative, but they demonstrate why very small losses should not automatically be treated as insignificant.

Why does nobody report a 45-second stop?

Because from the operator's perspective, solving the problem may be faster than reporting it.

A component becomes misaligned. A sensor needs to be reset. Material does not arrive correctly. A product jams briefly. The operator reacts immediately and production continues.

That is often exactly what an experienced operator should do.

The problem is expecting people to manually record every 30-, 40- or 60-second interruption.

If an operator experiences 20 such events during a shift, asking for 20 manual downtime reports adds work and can interfere with production itself. As a result, many micro-stops never appear in conventional reports.

At the end of the shift, the line appears to have been running almost continuously.

Yet the production quantity tells a different story.

Why can a running machine still miss its production target?

A machine does not need to experience a major breakdown to lose Performance.

Suppose a line should produce 120 units per hour. It is available for most of the shift, there is no major failure and the scrap rate is low.

Yet actual output averages only 108 units per hour.

Where did the missing production go?

Some losses may come from slower cycles. Others may come from brief interruptions that are too small to attract attention individually.

This is an important part of OEE (Overall Equipment Effectiveness). Long equipment failures clearly affect Availability, while recurring micro-stops and reduced operating speed can appear as Performance losses, depending on how the production process and OEE calculation are configured.

An OEE software solution therefore needs more than a list of major breakdowns. It needs sufficiently detailed production data to reveal the small losses accumulating between them.

What if Machine 7 stopped 436 times last month?

One micro-stop tells you almost nothing. Hundreds of similar micro-stops may reveal a production problem.

Imagine that a production report shows no major failure on Machine 7 during the previous month.

That sounds positive.

Now add another piece of information:

Machine 7 experienced 436 interruptions lasting less than two minutes.

Suddenly the situation deserves investigation.

Perhaps 70% occurred while producing the same product. Perhaps they became more frequent after several hours of continuous operation. Maybe they appeared mainly after a specific changeover or were concentrated around one particular process condition.

This is why automatic machine downtime monitoring is valuable. The system does not need to decide that a 45-second event is important when it occurs.

It needs to capture the event accurately enough for its importance to become visible later.

How does Production Management provide the missing context?

Knowing that a machine stopped 436 times is useful. Knowing what production was doing during those stops is much more useful.

Micro-stop information becomes more actionable when it can be connected with work orders, products, shifts, planned quantities and actual production.

Instead of asking:

“Why does this machine keep stopping?”

the production team can ask:

“Why does this machine keep stopping while producing Product B?”

or:

“Why do micro-stops increase after this particular changeover?”

This is where Production Management and OEE complement raw machine data.

The machine provides the event.

Production provides the context.

OEE shows the effect on performance.

Together, they provide a much stronger foundation for Lean Manufacturing and Kaizen activities than a monthly downtime total alone.

Can Factory Intelligence find a pattern hidden inside hundreds of stops?

436 events may look like 436 separate problems to a person. Factory Intelligence can help determine whether they are actually manifestations of the same recurring pattern.

Once machine events are connected with production history, the number of possible relationships becomes much larger.

Micro-stops can be analyzed in relation to machine, product, work order, shift, cycle time, previous maintenance activity and other available process information.

This is where Factory Intelligence can add another level of analysis.

For example, the system may help identify that micro-stops become more frequent under a particular combination of production conditions, or highlight an unusual change in the frequency or duration of short interruptions.

The objective is not for AI to invent a root cause.

It is to search large amounts of production data for patterns that would be difficult and time-consuming for people to identify manually.

That gives engineers a much better place to start their investigation.

Could micro-stops also be an early warning?

A growing number of small interruptions can sometimes be more interesting than one isolated stop.

Imagine a machine that normally experiences 10 short interruptions per week.

Then the number increases:

Week 1: 11
Week 2: 14
Week 3: 23
Week 4: 38

There may be a perfectly understandable production reason for the increase. A different product mix, new material or changed operating conditions could explain it.

But the trend may also deserve maintenance attention.

When Maintenance information and production history are available together, recurring changes can be investigated before they are simply accepted as the new normal. Over time, the same connected data can also provide the foundation for predictive analysis within Factory Intelligence.

How does TAP Smart Factory make invisible losses visible?

TAP Smart Factory is a modular MES system for real-time production monitoring developed by T3Soft.

By connecting machine information with OEE, Production Management, Maintenance and Reporting, TAP can provide context around production losses that would otherwise be difficult to see.

TAP Smart Factory is not an ERP solution. It can complement systems such as SAP and Microsoft Dynamics 365 Business Central (formerly Navision) while communicating with PLCs, machines, sensors, cameras, printers and other production equipment.

This creates a connected Smart Manufacturing environment in which short events do not need to disappear simply because nobody had time to write them down.

A 45-second interruption may not matter.

Even 20 of them may not seem dramatic during a busy shift.

But when the same pattern repeats day after day, the calculation changes.

20 micro-stops per shift can become 187.5 hours of lost production time per year.

And hundreds of apparently unrelated events may turn out to have something in common.

The most expensive downtime may not be the breakdown everyone remembers. It may be the 45 seconds nobody reports.