themerlanos

Every plant has one. The operator everyone walks over to when the line acts up, the job runs hot, or the new hire is stuck. They don't just run the machine — they carry the judgment calls, the workarounds, and the "don't do it that way" lessons that never made it into a manual. The problem isn't that this operator will leave someday. It's that when they do, the knowledge leaves with them — unless the handoff itself is a system, not a farewell lunch and a week of shadowing. Listen to this post: Why shadowing isn't a handoff Shadowing feels thorough, but it transfers habits, not judgment. The new operator watches what the veteran does, not why. The veteran can't narrate thirty years of decisions in two weeks, and once they're gone, there's no record to check when the odd case comes back. A real handoff leaves something behind that the next operator — and the one after that — can actually use. Three places in Plex where know-how can live 1. ...

Every plant I walk into has the same two conversations happening at once. The first one is about hiring. Good people are hard to find, experienced operators are retiring, and the open positions on the board just stay open. The tribal knowledge walks out the door with the veteran who ran that line for twenty years - I wrote about that back in July, and it has only gotten louder since. The second conversation is about AI. Plant leaders see the demos, read the announcements, and want some of it. If we can't hire enough skilled people, maybe the machines can be smarter instead. Both conversations are legitimate. But there is a problem sitting underneath both of them that nobody wants to name: the data is a mess. Listen to this post: AI doesn't fix bad data. It amplifies it. Here's the uncomfortable truth about every AI tool being sold to manufacturing right now, including the newer AI features arriving inside Plex itself. Rockwell's integration of FactoryTalk ...

Picture the receiving dock on a busy morning. A pallet comes off the truck, someone reads the scale display, walks to a terminal, and types the weight in. Three things can go wrong before lunch, and usually one of them does: the number is misread, mistyped, or entered against the wrong lot. Nobody catches it until a customer disputes a shipment weight, a count doesn't reconcile, or finance finds an invoice that doesn't match what actually shipped. Now picture the same dock with the scale connected. The operator opens the receiving transaction, sets the pallet on the scale, and taps the weigh scale button — the reading lands in the transaction by itself. No walk to the terminal, no transcription, no second guess about which digits were on the display. That is the whole change, and it is bigger than it sounds — because weight is one of the few shop-floor numbers that gets typed by hand long after everything else got a barcode. Listen to this post: How it actually connects This...

Every plant has one: the corner, cage, or red-tagged pallet where suspect material waits. Someone found something wrong — a dimension out of tolerance, a failed test, a shipment that doesn't match its paperwork — and instead of going into production, the material went into limbo. The question that corner asks every day is simple: who decides what happens to it, and how fast? That is what a Material Review Board is for. MRB stands for Material Review Board: a small cross-functional group — Quality, Engineering, and Manufacturing, with Supply Chain at the table when a vendor is involved — that dispositions nonconforming material. Not one person with a gut call. A board, with a record. Listen to this episode: The flow, in six steps 1. Find it, tag it, segregate it. The moment a nonconformance is found — at receiving inspection, in process, or at final test — the material is identified, tagged with the problem, and physically separated from good stock. Just as important is the syst...

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...

It is 7:40 am on a Monday morning and your inbox already has four Plex problems in it. A supervisor at one plant cannot print labels. An accountant at another company cannot close last month's books. Somebody - you are not sure who - reports that "Plex is slow." And a text message from a plant manager says a workcenter stopped recording production two hours ago. Four tickets. One of you. Which one do you touch first? If your answer is "whichever one I saw first" or "whoever is loudest," you do not have a support process - you have a reaction process. The fix is an old idea borrowed from emergency medicine: triage . This article covers what ticket triage is, why it pays for itself in a Plex ERP environment, the five-step pass I recommend for every incoming ticket, and the specific challenges that hit small Plex business analysts who support more than one company, in more than one location, at the same time. Listen to the podcast version of this post:...

Every plant has the same scavenger hunt. A job is waiting, a part or a tool is not where anyone expects it, and somebody burns fifteen minutes walking the floor to find out what is actually running, what is down, and what changed since the shift started. Lean has a name for that walking and searching: waste. Motion that adds no value, multiplied by every shift, every day. Plex ERP has a screen built to end the scavenger hunt: the Visual Plant Floor . It is exactly what the name says - a visual map of your plant floor, drawn inside Plex, where every workcenter sits in its real position on the layout and changes color with its live status. If you run Plex and have never opened it, you are sitting on one of the most practical screens in the system. A map that breathes Each machine on the floor gets an icon in its actual spot on the plan. The icon's color is the workcenter's status right now, using the same status language the shop floor already speaks: Production, Idle, Setup, Pro...

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. What follows is predictable: workarounds, shadow spreadsheets, tribal knowledge that never makes it into the system, and data nobody trusts. Here's the uncomfortable truth: adoption is a navigation problem before it's anything else. A new Plex user who can log in confidently, find their launch page, read the navigation bar, search for a record with the % wildcard, sort a display grid, and save a favorite is a user who will actually use the system. A user who can't do those things by the end of day one will route around the system by...

A year ago, I wrote about setting up cycle counting for supply items in the Plex ERP tool crib . We covered why counting a little throughout the year works better than doing one large annual count, how to set up counts in Plex, and the basics of ABC classification and assigning ownership. That post focused on how to count . This one is about what the count results can teach you. Listen to this post When the Counts Start Drifting You set up the cycle types, define the parameters, and get Plex Mobile scanning. Counts happen on schedule—and then the same variances keep appearing. A few carbide inserts are short. A drill index is over. The differences aren’t huge, but they keep coming back. The first instinct may be to count more often. But if the same items repeatedly drift in the same direction, counting more frequently probably won’t fix the cau...