What an HMI is, and why it sits between the operator and the PLC
HMI stands for Human-Machine Interface: the hardware and software that let an operator see what a PLC is doing and interact with it without opening the electrical cabinet or reading a line of code. The simplest form of HMI is a pushbutton and a pilot light; the most common one today is a touchscreen mounted on the cabinet or the machine itself, showing real-time values, letting the operator enter setpoints, and flagging when something goes wrong.
The reason this intermediate layer exists is simple: the PLC program works with internal variables, flags and function blocks that mean nothing to whoever operates the machine day to day. The HMI translates that internal state into something readable — a temperature, a green/red status, a plain-text alarm — and translates the operator's actions in the other direction — pressing "start," changing a setpoint — into the variables the program expects to receive.
What information an HMI handles: screens, alarms and trends
A well-designed HMI isn't a single screen, but a set of views with different purposes:
- Overview or synoptic screen: a schematic representation of the process or machine, with the most relevant values and states visible at a glance.
- Alarm list: active and historical anomalous events, with date, time, descriptive text and acknowledgement status.
- Trends: charts showing analog variables over time, essential for diagnosing drift before it turns into a stoppage.
- Recipes: saved parameter sets to switch product or operating mode without re-entering values by hand.
- User management: separate access levels for operator, maintainer and administrator, so not just anyone can change a critical setpoint.
HMI, SCADA and WebVisu: where one ends and the other begins
These three terms get confused often because, at a glance, all of them "show screens." The real difference is in scope:
| System | Scope | Where it lives |
|---|---|---|
| HMI | One machine or one specific cabinet | Dedicated panel next to the equipment |
| SCADA | Several machines, lines, or an entire plant | Central supervision server or PC |
| WebVisu | Variable: from a single machine to a whole building | Served directly from the PLC itself, no intermediate PC |
A SCADA system adds, on top of the HMI concept, supervision of multiple pieces of equipment at once, long-term data historians, report generation, and integration with higher-level systems. WebVisu, in turn, blurs the line: it's a web visualization with no supervision PC, served directly by the PLC, which in small and medium installations can cover both the local HMI role and much of what a traditional SCADA would do.
Types of HMI by hardware
The hardware choice shapes much of the project. The most common options on the plant floor are:
- Dedicated HMI panel (Siemens KTP/Comfort, Weintek, Beckhoff CP): a touchscreen with its own processor and operating system, mounted on the cabinet door. It's the most robust option and the most widely used on individual machines.
- Industrial PC with SCADA/HMI software: more processing power and more simultaneous screens, at the cost of hardware with a fan, a disk and an operating system to maintain.
- WebVisu embedded in the PLC: no extra hardware needed; any device's browser becomes the screen.
- Remote tablet or phone: occasional access from the plant floor with no fixed panel, usually complementing one of the above rather than replacing it.
How the HMI talks to the PLC
The HMI needs to read and write the PLC program's variables, and different protocols exist for that depending on the manufacturer and the project's architecture: proprietary protocols (like Siemens' S7 protocol, direct and efficient within its own ecosystem), OPC UA when the HMI needs to be manufacturer-independent or integrate with several systems at once, and Modbus TCP for budget panels or for integrating with field devices that already speak that protocol natively. The protocol choice isn't a minor detail — it determines how easy it will be to swap out the HMI or the PLC down the line without rewriting the whole project.
Screen design: principles of a good operator interface
A technically correct HMI can still be hard to use. Industrial operator-interface design discipline recommends a fairly different approach from the traditional "colorful" HMI: neutral gray backgrounds, with color reserved almost exclusively for alarms and abnormal states, so the operator spots a problem through visual contrast rather than having to read every value. Navigation hierarchy also matters — critical information shouldn't be more than two or three taps from the home screen — and avoiding the "Christmas tree" effect: if everything blinks or is red all the time, nothing really stands out when something genuinely serious happens.
Alarm management: why the ISA-18.2 standard matters
The alarm list is, in practice, the most-used screen during an unplanned stoppage. Poor alarm management — too many alarms, badly prioritized, unclear text — is one of the most common reasons an operator takes minutes to identify what actually failed. The ISA-18.2 standard, which we covered in detail in our real-time SCADA guide, applies just as much to designing alarms on a local HMI: prioritization by severity, rationalization to eliminate redundant alarms, and descriptive text pointing to the action to take, not just the symptom.
How to choose the right HMI for your project
The decision comes down to several concrete factors more than a brand preference: the space available on the cabinet door, the environment (a screen in a food plant with pressure washdown needs a far higher IP rating than one in a technical office), the number of variables and screens it needs to handle, the need for remote access from outside the plant, and the software licensing cost, which varies a lot between manufacturers. An oversized HMI on a simple machine is money poorly spent; an undersized one on a complex line is a maintenance bottleneck from day one.
As we explain in our guide on how to choose an industrial automation company, the quality of the final HMI depends as much on the hardware choice as on the screen-design judgement of the engineer programming it: two projects using the exact same panel can deliver radically different operating experiences.
How we do it at Bluemation
At Bluemation we program HMIs on the most common platforms on the market — Siemens, Weintek, Beckhoff — applying the same interface design principles across every project: a clear screen hierarchy, alarms prioritized according to ISA-18.2, and communication that stays consistent with the rest of the system, whether that's the PLC, a SCADA system, or a BMS. The HMI is designed as part of the same automation project, not bolted on afterward.
If you have a machine or a plant and need an HMI your operators will understand from day one, check out our HMI programming service or get in touch with us. We'll help you choose the hardware and design the screens, no strings attached.