An HMI is the operator's control panel for a machine: it shows PLC values and alarms, and it lets the operator start, stop and change settings. An MES is plant software that manages orders, counts, stops, quality and OEE across machines and shifts. Both can appear on a touchscreen at the line, but they are at different levels and most plants need both.
The confusion is understandable: stand at a modern line and you may see two touchscreens a metre apart. One belongs to the machine and the other belongs to production.
The fastest way to tell them apart is to walk one stop through both.
What an HMI does
A human machine interface (HMI) is the window into a PLC. It displays process values, shows alarms and sends operator commands, such as start, jog or a new setpoint.
Most HMIs are tied to one machine or cell. In ISA-95 terms they sit at Level 2, with the control system, and the ISA-101 committee sets design standards for them.
It must keep working if the plant network fails, since the operator needs it to run the machine. Emergency stops, by the way, belong on a hardwired safety circuit and never only on a screen.
What an MES does
A manufacturing execution system works one level up, at Level 3. It knows the order, the product, the shift, the planned quantity and what the line should have made by now.
It is built to keep records: every stop with a cause, every count by order, every quality check. These records live for months or years, and supervisors and engineers read them far from the machine.
Five questions that separate them
| Question on the floor | Answered by |
|---|---|
| Why will this machine not start? | HMI, through its active alarm |
| How do I change the fill speed? | HMI, within its permissions |
| Which order runs next? | MES, from its dispatch list |
| Why did nights miss the plan? | MES, from stops and causes |
| Which lot went into this batch? | MES, from its genealogy |
An alarm is not a stop
People often ask whether the HMI's alarm history can replace MES downtime data. It helps, but it counts something else.
Example: in one shift, a line's HMIs log 212 alarms while the line records 31 real stops. Many alarms are warnings that never stop anything, and one jam can trigger a flood of them.
Some stops raise no alarm at all, such as waiting for material or a slow start after a break. So an alarm log cannot tell you where the shift went, and downtime reason codes still need a person or a mapped rule.
The alarm is still useful as a hint. The first alarm in a stop is often a good candidate for the cause, so mapping it can spare the operator some typing.
Alarm management has its own standard, ISA-18.2, from ISA's alarm systems committee. It is written for the process industries, and it is still worth reading if your alarm list is noisy.
What flows between them
The link is usually through the PLC. The HMI and the MES are both clients of the same controller, and they rarely talk to each other directly.
- PLC to MES: run state, good and reject counts, speed, fault codes. Details are in PLC signals for OEE.
- MES to PLC: order number, product code, recipe or target quantity, where you allow it. The HMI then shows them to the operator.
- Operator to MES: stop causes, checks and material scans, entered on the MES terminal.
Common connections are OPC UA or the PLC's own protocol, covered in MES PLC integration. On older machines, Modbus or a gateway does the job.
Some HMI panels can also act as an OPC UA server or data gateway, which helps when you cannot touch the PLC program. Treat that as a practical route and check its load on the panel.
When one screen seems to do both jobs
- The same touchscreen. Many panels can show an MES web page in a browser next to the machine screens. The hardware is shared, while the systems stay separate.
- Stop reasons on the HMI. A machine builder can add a reason menu to the HMI, with the PLC passing the choice up. This works when a second screen will not fit.
- Recipes. The HMI can store recipes locally. An MES can send them centrally, which helps stop the wrong settings being used. Choose one master.
- Dashboards. A SCADA or HMI trend can look like an MES chart, but ask where the shift, order and cause come from.
Do you need an MES if you have HMIs?
Almost every automated machine comes with an HMI, so the real question is whether to add an MES above it. Three signs say yes.
- Production history still lives on clipboards and shift sheets.
- Nobody can compare two lines, because each panel only knows its own machine.
- Stop causes vanish once the alarm clears and the operator moves on.
Machines with no panel can still feed an MES. A retrofit sensor supplies state and counts, and a tablet takes the causes.
Hand-operated benches with no signals are the exception. Start with a paper or spreadsheet log until the questions outgrow it.
Design rules when both are at the line
- The machine must run with the MES down. A server fault should never stop production, so the MES stays out of the control loop.
- One job per screen. Running the machine and recording production are separate tasks. Keep the MES screen to a few big buttons.
- Few reasons, plain words. Six to ten choices per machine type work better than a list of 80 fault codes.
- Lock down writes. Reading tags is low risk, and writing setpoints from a plant system needs a review, tests and a log.
- Keep the screen near the work. If the operator has to walk 20 metres, causes get entered late or not at all. See operator downtime logging.
Your HMI can show that a machine stopped. Fabrico is a light MES for OEE: it takes stops, speed and counts live from PLCs or IoT sensors, and operators tag the cause at the line, so stops carry a reason and OEE builds per line and shift. See how Fabrico tracks stops and causes.
What people ask next
Is SCADA the same as an HMI?
Not quite. An HMI is usually one machine's panel, while SCADA supervises many machines or a whole site from central stations and logs more data. Our ISA-95 levels guide draws both at Level 2, while ISA's own summary lists SCADA under Level 3.
Can an HMI calculate OEE?
A machine builder can add a basic OEE screen using PLC counts. It normally covers one machine and has limited history, shifts and causes. For comparing lines, see line OEE vs machine OEE.
Does the MES connect to the HMI or to the PLC?
Normally the PLC, because that is where the signals originate. Some panels offer an OPC UA server, which can help if the PLC is locked. See MES OPC UA integration.
Can an MES change machine settings?
It can send recipes or setpoints to the PLC if the plant allows it, and regulated sectors use this to stop manual errors. Validate it carefully and keep the PLC's own limits as the final guard.
What should an MES terminal at the line show?
The current order, the count against target, the current state and a quick way to enter a cause. Keep it readable from a few metres, as the OEE dashboard examples show.
Fabrico is a light MES for OEE. It takes stops, speed and counts from PLCs or IoT sensors, with add-on AI cameras counting output where a machine has no usable signal, and operators tag the cause at the line.