The factory that wasn't broken
On paper the plant was in trouble: an OEE of 16.46%. But the story didn't add up, night-shift 'downtime' on a line nobody had scheduled, whole runs logged at 0% quality. The problem wasn't the factory. It was the measurement.
- A reported OEE of 16.46% suggested a plant in crisis.
- Over 243 hours of non-operational time had been mislogged as 'Power Off' downtime.
- Correcting the data lifted true OEE to 44.70%, no process changes needed.
- With the noise gone, the real bottleneck, label-feed delays, finally stood out.
Your plant, the same method. One sensor per line, live within 48 hours of the kit arriving.
The alarm bell
On paper, the numbers were worrying. One site reported an OEE of just 16.46%. For any production team that raises immediate concern: lost output, a plant that's struggling, something on the floor that needs urgent fixing. If the data was right, someone had a serious problem. There was only one issue, the story didn't quite add up.
The first clue
A closer look revealed something odd. Large chunks of time, over 243 hours, were being recorded as "Power Off" downtime. Some events stretched beyond four hours. Many landed squarely on night shifts. The question shifted: was the line actually down, or was it never meant to be running?
At the same time, certain runs showed 0% quality, as if everything produced had been rejected. But the line had been running at speed, consistently. Thousands of units, all scrapped? Highly unlikely.
The realisation
This wasn't a performance problem, it was a data problem. Unscheduled time was being counted as downtime, and operator inputs were skewing quality. The system was technically correct, and operationally misleading. The factory wasn't underperforming, it was being measured incorrectly.
Resetting the lens
Rather than jump into mechanical fixes, the focus went to the measurement first. Long "Power Off" periods were reclassified as unpaid time. Quality inputs were reviewed against actual production reality. Job-level data was used to separate true losses from logging errors. As the noise disappeared, the signal became clear. Measured correctly, the site's OEE was about 44.70%, not 16.46%. Nothing on the floor had changed; the record now matched what the line had been doing all along.
The real problem, now visible
With the distortion gone, the actual constraint stood out: label-feed delays, responsible for dozens of stoppages and nearly 40 hours of lost time a month. For the first time the team could target a real, measurable bottleneck instead of a misleading headline number.
The lesson generalises. In many factories the instinct is to fix the process, the machine, or the people. But before fixing performance, make sure you're seeing it clearly, because sometimes it isn't the factory that needs fixing. It's the measurement.
More results like this.
What monitoring reveals when you leave it running
One line, watched continuously for four months. Planned downtime took a third of its time, and the trend kept surfacing slow drifts a one-off audit would miss.
Read the case study → Food and beverage · Beverage bottlerThe filler was not the problem
A beverage bottler blamed its filler for a line that kept stopping. The first month of monitoring showed 9,848 stops, nearly a quarter of paid time spent waiting, and an air-supply loss of over 34 hours.
Read the case study → Packaging and bags · Bag manufacturerThree shifts, one live board
A three-shift bag maker tracked output on paper, one number per shift. Demand was rising and nobody could say whether the machines had headroom. A live record of every stop answered it with data.
Read the case study →How can bad data make OEE look worse than reality?
If time when the line was never meant to run is logged as downtime, availability is understated. If operator inputs record good production as rejected, quality is understated. Both drag the OEE figure below the plant's true performance.
Did the plant improve, or the measurement?
The measurement. The move from 16.46% to 44.70% came entirely from correcting how performance was recorded: unscheduled time reclassified as unpaid, and quality inputs fixed. Only then did the real problems become worth chasing.
What was the real bottleneck?
Once the distortion was removed, label-feed delays stood out clearly, responsible for dozens of stoppages and nearly 40 hours of lost time. That is a measurable, fixable constraint, unlike the misleading headline number.
Find losses like these on your own line.
A 30-minute call with a manufacturing specialist. We look at one of your lines together and show you what the first week of data would say about it.
- Live within 48 hours of your kit arriving
- One sensor, one terminal, no PLC and nothing to integrate
- R4,950 per line per month, ex VAT. 90 days, then a month's notice