L0 the plan · layout & roadmap
Before the first sensor: the drawing, and the long plan.
I'm in the room while a plant is still a layout drawing. I work with our sales team so the layout really meets the customer's needs, and I bring the gotchas they can't be expected to know: what our controls can and can't do, and which choice on paper turns into a headache in year three.
I also try to keep the software from becoming a rule book. It grows with the pressure each new plant puts on it, and I run its long-term roadmap, so even small, fast changes land inside one bigger plan: giving laundries what they need to run. We don't just program these plants. We're part of how they get sold, specified and built.
layout designworking with salescustom requirementsproduct roadmap
L1 I/O · field devices
Everything starts as a bit.
Out on the floor are the field devices. A photo-eye sees an item go by. A proximity switch confirms a gate is closed. A scale weighs a load, and in this business weight is money. A motor drive moves a conveyor, a reader tells one kind of item from another, and a switch sends each down its own track. Each of those is a wire, an I/O point, and network modules gather them onto the plant network. One plant I support maps 8,700 I/O points into a single controller, about 7,700 of them simple on/off signals.
In early 2009 I started the habit that became our testing standard: click to force, a test tool for commissioning a plant, not something left on in production. Click any sensor in the software and the plant acts as if a real item were sitting there, so whatever is coming up behind it stops and waits. Paired with a test PLC, it lets us exercise the whole stack, from the controller up to the reports, before a single real item moves. Tap a ◆ on the conveyor to force it on; tap again to let go.
photo-eyesproximity switchesscalesmotor drivesnetworked I/O
L2 machine control
I don't hand-write the PLC programs. I generate them.
The PLC is the plant's industrial controller: it reads the sensors and runs the motors, many times a second. When I started, we wrote those programs by hand, plant by plant. One of the first things I did was turn our standards into a generator: describe a plant once and the program writes itself. Not just a parts list of conveyors, lifts and panels: how each one is configured, and the network of what feeds what, and for what purpose. The detailed interactions between devices are modeled, so a wide range of capability comes standard instead of being written fresh each time. Fewer errors, much faster projects, and a small team that could take on far more of them at once. Today it covers 129 device types, with a hash check that proves a change didn't move a byte it shouldn't.
Talking to the PLC has had three lives: SOAP from Rails in 2007, an Elixir service I wrote in 2019, an OPC UA bridge today. One rule survived all three. Never act on a stale sensor. Read it again, live, before releasing anything.
B&R controllersgenerated programsOPC UAModbus TCP
L3 screens & workflows
Then a person has to run it.
In 2007 the operator screens were a per-seat license. The floor wanted eyes everywhere; the invoice said pick two. So we made the screen a web page. Nearly twenty years on, that page is eVue, and it's still what operators work in every shift at 400+ plants: a live picture of the whole plant, every item moving through it, and alarms that say in plain words why something isn't moving. In warehouse terms it sits where the control and execution systems (WCS, WES) would; in a factory, where the MES would.
One system runs every move across the whole building: the plant behind that I/O count has 611 rail sections and 93 machines, every one routed by eVue.
No two laundries work the same way, either. A hospital plant, a hotel plant and an airline plant each sort, store and send work through in their own order. So eVue is configured, not rebuilt, for each one: every station shows its operator just what they need to do that task right, not one generic screen for everything.
eVuelive plant viewconfigured per plantsince 2007
L4 people & productivity
Then there's the people.
Machines report on themselves. People are harder, and labor tracking is a different product with a different job: knowing who worked which station, on what, for how long, and measuring it in a way the floor accepts as fair. It takes understanding how a plant actually runs its shifts, not just its machines.
Operators log in to a task at a station. Their work is measured the way it really happens: per piece where that's fair, as a team in pounds per operator-hour where it isn't, and some jobs, like catching at the end of a line, are scored by the pace of the people feeding them. Breaks and shifts are built in, logins don't churn every time a customer changes, and supervisors get it by text and email, not just on a screen.
operator loginspiece rate & team ratebreaks & shiftsproductivity reports
L5 local reporting
The plant reads its own numbers.
Every time an item passes a sensor, a machine finishes a load or an operator logs in, it's a row in a database. So the plant can answer for itself: output by the hour, how long each machine runs, how busy each station is, and where the day is going wrong while there's still time to fix it. Plus a 6 a.m. report email someone actually opens.
All of it lives on the plant's own server. When the internet goes down, the floor doesn't notice.
KPI dashboardslabor standardsscheduled reports
L6 cloud reporting
Then the company reads all of them.
Each plant runs on its own. A hub at every site rolls its numbers up to the cloud every minute, so the people running a company of plants see one picture instead of forty phone calls.
The fleet is the hard part: 400+ plants, each its own building, floor plan and set of machines. This layer is a team build: Jason and Larry carried most of it, and I've added my share.
edge hub per plant1-minute rollupmulti-tenant warehouse
L7 mobile
And finally, a phone in a pocket.
Plant networks are walled off, and they should be. Pulse is how the plant's data gets out anyway, securely: a supervisor links a phone by scanning a QR code at the plant, then gets the numbers that matter, and a push when something is really wrong.
It's the top of the stack, and the part people actually carry. That's the whole building, bottom to top.
PulsePWAweb pushQR-linked devices