LADX
Start free
← Resources
HMI & SCADA·6 min read·

SCADA or HMI: what the words actually distinguish

Scope, architecture and history. Why the distinction blurred, and the questions that still separate them.

Short answer

An HMI is the operator interface to one machine or unit, usually a panel mounted on it. SCADA is a system for supervising and acquiring data from many distributed units, with a server, a historian and multiple clients. The distinction is scope and architecture rather than software: the same package often builds both, and the useful questions are how many machines, how far apart, and does the data need to outlive the shift.

Which protocol sits whereENTERPRISEOPC UAMQTTCONTROLEtherNet/IPPROFINETModbus TCPDEVICEIO-LinkPROFIBUS DPModbus RTUEthernet carries most of it now, which is why the layers blur.

The two words are used interchangeably in sales material and mean genuinely different things in a design review, which is where the confusion costs something.

The historical distinction

SCADA came from utilities: pipelines, water networks, electricity distribution. Assets spread over hundreds of kilometres, talking back over slow links to a control centre. Supervisory control and data acquisition, and the acquisition part was the hard bit.

HMI came from the machine. A panel on the front of it, showing what it is doing and letting somebody operate it.

The tooling converged, so the same software now builds both, and the words drifted with it.

The questions that still separate them

How many units, and how far apart? One machine in front of you is an HMI. Forty units across a site with a control room is SCADA.

Does the data outlive the shift? An HMI trend is typically a rolling buffer. When somebody needs to compare this batch with one from March, that is a historian, and a historian is a SCADA component.

Is there a server? An HMI panel holds its own configuration and its own data. A SCADA system has a server that clients connect to, which brings redundancy, licensing, backup and a single point of failure to think about.

Who is looking? One operator at the machine, or several people in different places including somebody on a laptop at home. The second needs authentication, roles and an audit trail.

What SCADA adds, and what it costs

The additions are real: historian, cross unit alarm management, reporting, redundancy, remote access, integration upward to production systems.

The costs are also real and are usually underestimated: a server to maintain and patch, a licensing model that scales with tags or clients, a database that needs backing up, network dependencies that turn a machine level fault into a site level one, and a security surface that a panel bolted to a machine does not have.

The most common expensive mistake in this area is specifying SCADA for a single machine because the word sounds more capable. It adds a server between the operator and the machine they are standing next to.

The middle ground

Plenty of installations sit between. Several panel HMIs, each running its own machine, plus a small supervisory layer collecting data for reporting.

That arrangement is often the right one, and it has a specific virtue: each machine keeps working when the supervisory layer is down. A design where the machine stops because a server is being patched has put a dependency in the wrong place.

Where LADX sits

Worth being plain about. The HMI builder in LADX builds operator screens against a controller's tag table, with alarms, trends and a runtime that runs the logic at a desk.

It is not a SCADA system. There is no server, no historian, and no plant wide alarm management, and it does not open sockets to plant equipment. It is for designing, proving and handing over the screens for a machine, which is a different job from supervising a site.

Common questions

Is SCADA just a big HMI?
Not quite. The additions that matter are a data historian, a server that clients connect to rather than each panel holding its own data, alarm management across units, and communication with geographically distributed sites. Any one of those pushes a design past what an HMI does.
Do I need SCADA for a single machine?
Almost never. A single machine with a panel HMI, storing what it needs locally, is simpler, cheaper and has fewer things to fail. SCADA earns its complexity when there are many units, when data must be compared across them, or when it must be kept.
What is a historian?
A time series database built for process data: high write rates, compression tuned for slowly changing analogue values, and queries by time range. It is what lets somebody ask what the temperature was doing at four in the morning three weeks ago, which no HMI holding a rolling buffer can answer.

Keep reading