Augos Factory / Proof / Paint & coatings manufacturer
Case study · Manufacturing · South Africa
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 shifts the line was never scheduled to run were logged as downtime, and on separate runs quality showed 0%. The problem wasn't the factory. It was the measurement.
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 showed two things that didn't fit. First, over 243 hours were recorded as "Power Off" downtime. Some stops ran past four hours, and many fell on night shifts the line was never scheduled to run. Was the line down, or simply not planned to run?
Second, on separate runs the line ran at speed, yet quality showed 0%, as if every unit was rejected. The rejects entered at the terminal didn't match what the line had made.
The realisation
The diagnosis
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.
Questions
This case, answered
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.
Thirty minutes with a manufacturing specialist, on your own lines and products.
- Every stop timed and given a reason
- Read by your own team
- Prices in rand, ex VAT
A manufacturing specialist replies within two business hours to set a 30-minute call.