Process Control
Control is the part the customer never sees and feels constantly. A well-sequenced machine feels calm. A badly sequenced one feels like it's about to do something you didn't ask for, and operators are never wrong about that feeling.
Everything in this discipline is a variation on measure, compare, correct. The complexity isn't the loop — it's that a real machine runs dozens of them at once, they interact, and the interesting failures happen at the seams between them rather than inside any one.




Before there was a touchscreen there were pushbuttons, and the good news is that the discipline never changed. Position, color and labeling are the whole interface. Green means running, red means stopped, and if you ever invert that to save a lamp you will hurt someone.




Discrete automation counts parts. Process counts flow, pressure and temperature, and it never stops to let you work on it — which changes what a control system has to be. A palletizer can be stopped and restarted. A process line has a state you have to bring it back through.




Process equipment often ships as a skid: frame, piping, instruments, valves and its own control panel, built and wired in the shop so the site work is four bolts and a conduit run. Everything you can do on a bench is cheaper than doing it on a plant floor.




- 1Design for the worst shift, not the best one. Your screen will be read by someone tired, on their fourth hour, with a supervisor behind them. Clarity beats density every time.
- 2A fault message should say what to do. "Fault 47" is contempt. "Infeed jam — clear sensor at station 3" is the same information plus the part that helps.
- 3Show state, not just values. A number tells them what. The machine's state tells them whether that number is a problem, which is the only question they actually have.
- 4Don't hide the manual controls. Someone will need them at 3am, and if they can't find them they will find a way around your interlocks instead.
Most machines that "stop randomly" are sequenced by whoever needed it working that afternoon. A state machine that's explicit about every transition — including the illegal ones — costs a day up front and saves the entire life of the machine.
A panorama sweep that assumed the world would hold still. It did not. The algorithm made exactly one bad assumption and then committed to it, with total confidence, all the way across the frame.
Which is the whole argument for stating a tolerance: every measurement carries one, whether or not anybody wrote it down.
SCALE: NONENOT TO BE USED FOR FABRICATION