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.
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.
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.
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.
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, and the site's OEE didn't crawl upward, it jumped from 16.46% to roughly 44.70%. Availability improved, quality stabilised, and the factory suddenly looked a lot less broken.
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.
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.
No. The jump from 16.46% to 44.70% came entirely from correcting how performance was measured, reclassifying unscheduled time as unpaid and fixing quality inputs. Only then did the real problems become worth chasing.
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.
Book a demo with one of our manufacturing experts.