From New Hire to Plex-Confident in 30 Days

Image
ERP implementations don't usually fail on the software. They fail on Monday morning, when a new hire logs in for the first time, stares at the launch page, and quietly decides to keep using the spreadsheet. I've watched this happen for years. The system goes live, the consultants leave, and the people who actually run the plant get about twenty minutes of "here's how you log in" before they're expected to be productive. Then everyone acts surprised when the new hire routes around the system by the end of week one. It doesn't have to go that way. The fix is not a longer training class. It is a 30-day path with a clear job for each week. Week one, the new hire learns to move around. Week two, they learn their own job's screens. Week three, they learn quality and traceability. Week four, they work alone while someone watches. At the end of it, you have an operator who uses the system because it works for them, not because someone told them to. Adopt...

Your OEE Is Lying to You: Fix Your Downtime Reason Codes


Back in June, we walked through Plex's three Production Monitoring views: the Control Panel for the operator at the machine, Production Statuses for the supervisor across the line, and the Visual Plant Floor for the manager who needs the whole building at a glance.

Every one of those views has a quiet dependency nobody talks about. They are only as honest as the downtime data underneath them. And the downtime data is only as honest as the reason codes your operators enter.

Here is the uncomfortable version: if your operators are stamping "Other," "Misc," or "Downtime" on two-thirds of your stoppages, or entering everything from memory at the end of the shift, then your OEE number is a work of fiction. A nicely formatted, color-coded work of fiction - but fiction all the same.

Listen to this post:

The gap hiding in your dashboards

Production Monitoring is excellent at one thing: telling you when a workcenter stopped and for how long. The OEE tile on the Control Panel knows exactly how many minutes of available time you lost.

What it cannot tell you is why - unless the reason code is real. And in too many plants, the reason-code field is where good data goes to die.

We have all seen the pattern. The shift starts, a machine stops for three minutes because the operator needed material, then again for six minutes for a sensor fault, then twelve for a changeover that ran long. At 3:00 PM the operator opens the downtime list, scrolls past forty codes, sighs, and selects "Other" for all three. Or the worst one: they leave it blank and let the system default to "Unassigned."

Now your weekly downtime report says the top reason your line loses time is "Other." You cannot fix "Other." You cannot Pareto "Unassigned." You cannot assign an owner to "Misc."

What bad reason codes actually cost you

This is not a data-quality lecture for its own sake. Bad reason codes send improvement money to the wrong problems.

Picture this: your downtime summary shows "Changeover" eating 22% of available time. Engineering spends a month on a SMED project, cuts changeover time by a third - and the needle barely moves. Why? Because operators were dumping everything that happened during a changeover window into the changeover code: the actual changeover, the missing fixture that took nine minutes to find, the four minutes waiting on a forklift for the new coil. The real thief was material handling, and the honest data was nowhere in the report.

Another classic: "Material - No Stock" climbing every week, so purchasing starts overstocking to compensate. But half those entries were really "Waiting - No Operator" during break overlaps, entered in a rush at shift end. Now you carry extra inventory for a problem that was a staffing schedule.

The pattern is always the same. You invest real time and money to fix what the report shows, and the report was never showing the truth. Garbage in, capital out.

Design a code list operators will actually use

The fix starts with the list itself. Most reason-code lists fail the same way: they are built by engineers in a conference room, with forty-seven options in precise technical language, and handed to operators who have three seconds to pick one while a line is down.

A good downtime reason-code list follows a few hard rules:

  • Planned vs. unplanned first. Separate the two before anything else. A scheduled break, a planned PM, a model changeover is not the same animal as a sensor fault at 2:00 AM. If your report cannot split these, your availability number is mud.
  • Ten codes, not forty. Eight to twelve codes cover 95% of real life. Every code beyond that is one more reason for the operator to give up and pick "Other." Specificity helps only when someone will use it.
  • Write what the floor calls it. "Starved - Waiting on Forklift" beats "Material Handling Delay - Upstream." "Sensor Fault - Photo-eye" beats "Instrumentation Anomaly." The code list is a shop-floor tool, not a whitepaper.
  • No catch-all as the first option. "Other" needs to exist for the genuinely strange days, but bury it at the bottom and require a note when it is used. The moment "Other" is the easiest choice, it becomes the only choice.
  • Built with the people who will use it. Walk the codes with two operators and a shift lead before you lock them in. They will spot the overlap your conference room missed: your "Jam" and their "Jam" are not the same machine event.

One screen, plain language, and the list fits the moment. That is the whole design brief.

Audit the codes you already have

Before you change anything, look at what the last month of data tells you. Pull downtime by reason code for one line or one department - Plex's reporting can slice this - and run it through three quick checks:

  • The 60% test. Is a single code carrying 60% or more of your downtime entries? Then the list is broken, not the floor. That code has become the new "Other," and you need to split it into three or four real reasons.
  • The vague-code check. Add up every "Other," "Misc," "Unassigned," and blank entry. If it is more than 15% of entries, your dashboards are steering by rumor.
  • The planned split. What share of downtime is tagged planned? If it looks suspiciously low, operators are probably logging PMs and breaks as unplanned - or not logging them at all. Either way, your availability math is wrong.

This audit is a thirty-minute exercise that will change how you read every production report you already have. Most plants find their top "reason" is actually a confession that the code list does not work.

Coach the habit without blame

Here is the trap: once you see the bad data, the instinct is to make accurate codes a compliance issue. Track who enters "Other" most often. Send warning emails. That gets you exactly one outcome: operators who enter codes beautifully and dishonestly.

End-of-shift batch entry is not laziness - it is the rational response to a workflow that interrupts real work. Entering a reason code at the moment of the stoppage feels like paperwork when the line needs you. The fix is to make honest entry the path of least resistance:

  • Keep the entry step on the same screen the operator already uses for the stoppage, so it is one tap, not a detour.
  • Time-stamp matters more than prose. A correct code picked in the moment beats a paragraph typed at 3:00 PM. Save the detail for the big stops.
  • Review the codes in the morning huddle, not in a discipline meeting. "Yesterday we had nine 'Other' entries on Line 2 - what was actually happening?" turns the codes into a conversation about the work, not an audit of the person.
  • Celebrate the unflattering codes. The day "Waiting - No Operator" shows up honestly is the day you can finally fix the break schedule. The code is doing its job.

Operators give you honest data when honest data clearly feeds fixes they can see. The fastest way to kill the habit is to use a reason code as evidence in a disciplinary conversation. The day the codes become a blame tool is the day they become fiction again.

Run the weekly top-code review

This is where the honest codes pay rent. Once the data is trustworthy, a thirty-minute weekly review of the top downtime codes becomes the most valuable meeting on your calendar:

  • Pareto the top three codes for the week by minutes lost. Not entries - minutes. One five-minute code hit two hundred times matters less than a forty-minute code hit twelve times.
  • Assign one owner and one fix per code. "No Material - Waiting on Forklift: staging coils at the line by 6:30 AM - owner: Materials Lead - due Friday."
  • Re-measure next week. If the fix worked, the code drops down the Pareto. If it did not, you learned something and pick the next move.

Three codes, one owner each, one week at a time. Within a quarter, the floor starts treating the codes as the input to real fixes - and that closes the loop that keeps the data honest in the first place. People enter good codes when they see good codes change their shift.

The bottom line

The Control Panel, Production Statuses, and the Visual Plant Floor are only ever as honest as the data feeding them. The dashboards do the math; your operators supply the truth.

Your OEE is not lying to you. It is faithfully reporting exactly what your reason codes told it. Give it better codes, enter them in the moment, audit them like you mean it, and review the top three every week. Within a few months, the number on the screen stops being a decoration and starts being a weapon.

The dashboard was never the hard part. The honest ten codes were.

Download the checklist

Use this one-page checklist to audit your ten codes before your next review. Download the OEE Data Trust Checklist and run it on the floor before you trust the next number.

Popular posts from this blog

Ticket Triage for Plex ERP: How Small BA Teams Decide What Gets Fixed First

The Quarantine Corner: How an MRB Keeps bad parts from becoming bad shipments

Stop Typing Weights: What a Scale Connected to Plex Actually Changes