Human-Machine Interface, HMI.
An HMI is the operator-facing graphical layer of a control system. The screens, faceplates, alarm summaries, and trend displays the operator looks at while running a plant. It runs on top of the BPCS and exposes the live process data in a form humans can interpret and act on.
Three drawings included on a new account.
What Human-Machine Interface, HMI means.
A human-machine interface is the layer of a control system the operator actually looks at. The process graphics that mirror the P&ID, the per-loop faceplates that show setpoint, measurement, output, and mode, the alarm summary, and the trends that give the numbers context. It is a component rather than a system. A distributed control system ships its HMI as part of the integrated package. A SCADA system runs an HMI on top of wide-area data acquisition. A PLC-based plant typically runs an HMI from a separate software product. Whatever hosts it, the HMI does not own data, it presents it. Every faceplate references one or more tags in the underlying controller, so the HMI tag database is a derivative of the controls dataset rather than an independent document, and a tag missing from the I/O list is a faceplate that has nothing to display. The design discipline around HMIs changed substantially after the high-performance HMI movement, codified in ANSI/ISA-101.01 in 2015, which strips colour and decoration from the base graphic and reserves saturated colour for genuine abnormal conditions, so that an alarm stands out instead of competing with a screen full of always-on process values. The rationale is operator response time under upset. A screen that is loud all the time is a screen on which a real problem is easy to miss.
What an HMI shows
Process graphics that mirror the P&ID layout, faceplates per loop showing setpoint, process variable, output, and mode, alarm banners and summary lists, trend windows for historical context, and navigation panes between unit areas. Modern HMI design follows ISA 101, high-performance HMI which favors muted greys-and-greens with color reserved for alarms, replacing the rainbow-coloured graphics of the 1990s.
HMI vs SCADA vs DCS
An HMI is a component, not a system. A DCS includes its HMI as part of the package. A SCADA system runs an HMI on top of remote-station data acquisition. A PLC-based plant typically runs an HMI from a third-party package, Wonderware, Ignition, FactoryTalk View, Siemens WinCC, GE iFix. The line between HMI and SCADA blurs because most modern HMI packages include data acquisition. The distinction is mostly about the operational scope they're configured for.
HMI against SCADA against DCS
The three words are used interchangeably in conversation and mean three different things in a specification. The distinction that matters is where control actually executes.
| Aspect | HMI | SCADA | DCS |
|---|---|---|---|
| What it is | The operator facing graphics layer | A supervisory system collecting from and commanding geographically spread sites | An integrated control system with its own controllers, I/O, database and consoles |
| Where control executes | Nowhere; it displays and commands | In the field controllers and remote terminal units | In the DCS controllers |
| Typical geography | One machine, skid or panel | A wide area: pipelines, water networks, power distribution | One plant or process unit |
| Communications | Direct to one controller | Polling or report by exception over radio, cellular or fibre, with latency and dropouts expected | A deterministic plant control network |
| History | Little or none held locally | A central historian; often the main reason the system exists | Built in and populated from the same tag database |
| Alarming | Local to the screen | Central, with call out and escalation to on call staff | Built in, and rationalised in the same database as the graphics |
| If the link drops | The machine keeps running on its own controller | The remote site keeps running; the control centre loses visibility | Controllers keep running; the console loses visibility |
| Engineering effort | Screens drawn per machine | A tag database plus screens, repeated per site | One tag database drives graphics, alarms and history together |
The ISA-101 display hierarchy
Four levels, each answering a different question. A plant that has only built level 2 and level 3 displays is why operators keep a paper list of what to watch.
| Level | What it shows | What the operator uses it for |
|---|---|---|
| Level 1 | The whole unit or area at a glance, with key indicators and anything abnormal | The home display; the one on screen when nothing is happening |
| Level 2 | One unit in detail, with the loops and equipment the operator controls | Routine control actions and normal adjustment |
| Level 3 | One sub-unit or one item of equipment in full detail | Diagnosing a problem, and supporting maintenance |
| Level 4 | Supporting detail: trends, diagnostics, procedures and help | Investigation, and following a written procedure |
Common questions
What is high-performance HMI.
Where does the HMI tag database come from.
What standard governs HMI graphic design in process plants.
Get the I/O list template.
Fourteen columns with the signal class as a dropdown, auto-filter on every column, frozen header. Plain .xlsx.