Invisible losses · A VIEOX perspective
When small interruptions change the whole shift.
Understand micro-stops and reduced-speed production through cycle timing, equipment states, product context and a clear boundary for counting losses.
The practical question
How can OT information help explain micro-stops and speed loss?
Connect brief equipment events and cycle timing with the product, operating mode and downstream effect. Establish how the site defines a stop and a comparable cycle, preserve gaps in observation and check whether the local change reduced useful line output. This creates a better investigation without treating a short event as a confirmed fault.
A production team may remember repeated interruptions that never appear as a major downtime event. Another shift may have few stops but still finish short. Examine these patterns separately before deciding whether the problem is stopping, cycling more slowly, waiting or recording the work differently.
Define the event before counting it
Agree when a short interruption starts and ends, which operating states are relevant and how adjacent events are handled. The rule should match the work the team is trying to understand. An intentional wait for inspection should not silently become an equipment failure merely because no cycle completed.
Preserve the chosen definition in the review record. If the rule changes, keep the earlier and later results distinguishable. Otherwise a revised reporting threshold can look like an operational improvement even when nothing changed on the floor.
Give cycle time its product and sequence
A cycle comparison needs more than two averages. Ask whether the product, recipe, tooling, handling sequence and accepted operating mode are comparable. Explain whether loading, unloading, waiting and inspection are inside the cycle boundary. An unfamiliar product can legitimately require a different sequence.
Look at the distribution and the period being compared, not just a shift total. A few prolonged cycles and a steady small delay lead to different questions. Missing or duplicated cycle events should be examined before interpreting either pattern.
A local change and a line result are different measures
NIST research on manufacturing KPIs examines relationships and dependencies between performance measures, including productivity, quality and maintenance perspectives. That is a useful reason to investigate how a local event relates to a wider result instead of assuming that each stopped second produces the same line-level consequence.
Sources: [1]
Listen to the explanation that the signal cannot provide
Ask operators what they were doing around the recorded period. A material presentation issue, fixture adjustment or unusual inspection may explain why the sequence differed. Preserve the person’s account as an account, alongside the observed events. Invite correction where the electronic record does not match their experience.
Hypothetical example: an assembly cell shows repeated short waits. The local machine looks responsible until the review includes a replenishment interval upstream. The next step is to examine the material-flow question with the relevant team, not assign a fault solely from event frequency.
Make missing observation part of the result
Document whether the available record can resolve the interruption being studied. A coarse reporting interval may hide a brief change; a missing connection period may resemble idle equipment. Explain which sources confirm that the process was actually stopped and which only show that an update did not arrive.
The first useful outcome may be a better event definition or a corrected identifier. Keep that outcome visible. It strengthens later comparisons and avoids presenting a data correction as recovered production time.
Take one pattern into the next operating review
Choose a recurring pattern with enough context to discuss. Bring the affected period, comparison rule, operator observations and any line-level consequence. Ask the responsible specialists what further evidence would separate the plausible explanations.
After authorised follow-up, compare the result using the same boundary and note any changed circumstances. A pattern that disappears during a different product mix has not yet established a durable improvement. The record should help the next team continue the question without starting again.
Put the question to work
A practical checklist
- Write down the micro-stop and cycle boundaries.
- Keep product, recipe and operating mode with the comparison.
- Check event resolution and missing intervals.
- Distinguish local interruption from line-level consequence.
- Review a repeated pattern with the people who operated the cell.
Questions, answered
Should every machine use the same short-stop threshold?
A common reporting convention can help comparison, but the threshold must remain meaningful for the process and the question. Preserve local definitions and make differences visible before combining results across dissimilar machines.
Is the fastest observed cycle the right target?
Not automatically. The comparison needs an agreed, valid operating basis that considers product requirements and the complete sequence. A single fast cycle does not establish a sustainable or appropriate production rate.