A PLC and an HMI rarely fail at the same moment. When a line stops, the HMI is usually the first place an operator looks, while the PLC holds the sequence that actually drove the machine. That difference matters for the people developing the integration, because the two devices answer different questions, and confusion between them shows up later as a machine that runs but is difficult to troubleshoot, or an interface operators quietly stop trusting.
If you are buying automation as an integrator, or asking a manufacturer for customised equipment, the useful question is not which brand of controller to specify. It is what has to be agreed, in what order, before the cabinet is wired and the screen is drawn. The stages below are the ones we work through on our own equipment builds.
Stage 1: Write down what the machine has to do
Before anyone opens a programming tool, the machine gets described in plain language. Which states exist — manual, home, ready, running, paused, fault. What has to happen to leave each state and enter the next. Which conditions must hold true before motion is allowed, and what the machine does when a sensor disagrees.
A written sequence, numbered and signed off by the person who will operate the equipment, prevents an argument at the end of a build about what was agreed. On equipment such as our fixed steam cleaning machine, that description covers how steam and vacuum modes change hands, what has to be true before heating is enabled, and how each protection function behaves. It is the sort of machine where an undocumented interlock becomes a safety problem, not a convenience problem.
Stage 2: Build the I/O list
The sequence tells you how many inputs and outputs you need, and what kind. Digital sensors, analogue signals, motor starters, valves, drives, safety devices. Every point gets a tag name, a physical location, and a note about what it does.
Two practical points from experience. Leave spare capacity — a machine that has no free input at commissioning is a machine where the next small change costs a wiring modification. And keep tag names boring and consistent: tank_level_high tells a maintenance engineer what it means at two in the morning, while DI17 tells them nothing.
Stage 3: Decide what the PLC owns and what the HMI owns
The rule worth defending is this: the PLC makes decisions, the HMI displays them and collects requests. Any logic that affects machine motion, heating, pressure or safety lives in the controller. If a critical condition is evaluated on the screen, then a frozen screen, a dropped communication link, or an HMI reboot removes that condition from the machine.
The HMI does carry legitimate work. Operator-facing setpoints, mode selection, recipe values, alarms, and the prompts an operator needs to act on. What the screen should not do is be the only place where a decision is made.
Stage 4: Fix the tag map and the communication link
The interface is where the two halves meet, and it deserves the same attention as the code. Choose the protocol your hardware supports and your customer's maintenance team can work with — many controllers and panels on Modbus TCP or the vendor's own Ethernet protocol, and mixed-brand projects usually settle on one of those.
Then fix the address map in one document: which controller register or tag corresponds to which screen object, what units and scaling apply, and which direction each value travels. A display showing temperature or pressure in the wrong scale looks like a sensor fault and sends a technician down the wrong path. Writing scaling into the tag map once is cheaper than explaining it to every person who touches the machine afterwards.
Stage 5: Design the screens around the operator, not the engineer
Engineers draw screens that show everything they built. Operators need to know three things without hunting: what state the machine is in, what it is waiting for, and what they are allowed to change. A home screen with current mode, the values that matter, and the controls that are permitted on that machine usually does the job. Deep menus for setup belong behind a login.
Alarm text should say what happened and where. "Fault" is not an instruction. "Water level low — check supply and tank" points at the machine, not at a manual. For equipment a customer will run for years, that difference determines whether a stop is cleared in two minutes or waits for a service visit.
Stage 6: Prove the protection functions before the machine runs product
Protection interlocks are easy to write and easy to leave untested. Each one gets triggered deliberately at commissioning, with the result recorded: did the machine reach a safe state, and did the screen tell the operator why. On cleaning equipment with heating and pressure, the functions we test individually include leakage, short-circuit, high-temperature, high-voltage and water-shortage protection. Testing them as a group and ticking one line proves nothing about any one of them.
The record of those tests belongs with the machine documentation. Whoever maintains the equipment in year four needs to know what the protection functions were expected to do.
Stage 7: Commission with the people who will run it
Dry-run the sequence with no product, then run the real cycle, then let the customer's operators use it while a developer watches. Operators find things no test plan predicted — a sensor that gets covered during normal loading, a prompt that is impossible to read in the daylight by the machine, a step they always perform in a different order. Those findings should be captured as change notes, not absorbed silently.
Stage 8: Back up the program and hand over the map
The handover that makes a machine supportable: a dated copy of the PLC program, a dated copy of the HMI project, the tag map, the alarm list, and the interlock test record. A controller with no matching backup becomes a rebuild project the day the original developer is unavailable.
What to look for in a supplier
When you assess a manufacturer for customised or OEM equipment, ask for the artefacts rather than the assurances. Can they show a sequence description and an I/O list for a machine they have already built? Can they name the protocols they support and the panel brands they work with? Will the tag map and program backups come with the machine, and are the interlock tests documented?
Shenzhen PowerDe Automation Precision Equipment Co., Ltd. works on equipment development, custom configurations and engineering support, and our PowerDe steam cleaning machine range covers mobile and fixed machines for vehicle and industrial sites. If you are specifying equipment where the control system has to fit an existing plant, the practical route is to send us the sequence and the site conditions, and we will confirm what the control design needs.
