Practical writing on OEE, downtime, and getting a plant to trust its own numbers — from the first honest measurement to keeping the improvement program alive past month three.
Most OEE software advice assumes you have an IT department, an integration budget, and a year. If you have three lines and a supervisor with strong opinions, the evaluation looks completely different.
Your downtime data has the accuracy of its least-trained recorder. A practical approach to teaching stop classification — designed for how people actually learn, not how the code list is organized.
OEE programs rarely fail loudly. They launch well, bank some early wins, and then — around month three — quietly stop mattering. The stall has mechanics, and the mechanics have fixes.
Every plant eventually mounts a big screen over the line. Six weeks later, nobody looks at it. The difference between a dashboard and wallpaper is what you choose to show — and who you design it for.
The filler was running rough all afternoon, the fix was half-finished, and none of it survived the five minutes between shifts. Every plant loses hours this way — in the gap between two crews who each know half the story.
Every downtime tracking effort starts with clean sheets and good intentions. Six weeks later the logs say 'misc — 45 min.' The decay is predictable, which means it's preventable.
The daily production meeting is where OEE data either becomes action or becomes wallpaper. The difference isn't the dashboard — it's whether the meeting is built to narrate yesterday or to change today.
Somewhere right now a plant is postponing OEE tracking until the sensor project is approved, budgeted, and integrated. The sensors will take a year. The clipboard could start Monday.
Every plant eventually has the meeting: does the changeover count against us? Does cleaning? The answers you pick decide what your OEE number is able to see — and what it hides forever.
A thermometer tells you the patient has a fever. Nobody blames the thermometer, and nobody blames the patient for having a temperature. The moment OEE becomes a grade, it stops being a measurement.
Two lines can post the same 60% OEE for completely different reasons — and need completely different fixes. Reading the three factors separately is where the diagnosis starts.
SMED has a reputation as a methodology for plants with lean departments. Strip away the vocabulary and it's one powerful question: what are we doing while the machine is stopped that we could do while it's running?
The 85% figure gets treated like a law of physics. It's actually a 1980s illustration that escaped its textbook. Here's what real plants score, and a better way to pick your target.
Every OEE journey starts with a spreadsheet, and that's fine — ours did too. The trouble isn't that Excel is bad. It's that the moment it starts failing is almost impossible to see from inside.
A 30-second jam doesn't feel like downtime. It feels like part of the job. Multiply it by ninety occurrences a shift and it's your biggest loss — and it's completely absent from your records.
When a tracking rollout struggles, the post-mortem always blames training or the software. It's almost never either. It's that nobody answered the question every operator silently asked on day one: is this thing for me, or about me?
The OEE formula takes thirty seconds to learn. The judgment calls — what counts as planned time, which speed to use, where changeovers go — are where every plant gets tangled. Let's walk one shift all the way through.
Every plant's downtime follows the same brutal arithmetic: a handful of reasons cause most of the loss. The Pareto chart finds them — if you avoid the three classic ways of doing it wrong.
The six big losses sound like textbook material until you realize you can name a machine in your plant for every single one. A tour of all six, with the examples the textbooks leave out.
OEE gets explained with formulas and pyramids and consultant slides. Here's the version we give to a supervisor on their first day: what the number means, and what it doesn't.
Tell us a bit about your plant floor and we'll show you EnicSoft OEE running on your own numbers.
