SCADA vs HMI: What’s the Difference and How They Work Together

Key takeaways

  • An HMI (Human Machine Interface) is the screen an operator uses to see and control a process. SCADA (Supervisory Control and Data Acquisition) is the whole supervisory system: data acquisition, communications, historian, alarm management and one or more HMIs.
  • An HMI answers “What is this machine doing right now?” SCADA answers “How is the whole operation performing?”
  • A PLC controls, an HMI displays, SCADA supervises. They are layers of one architecture, not competing products.
  • Move from HMI-only to SCADA when you supervise more than one machine, line or site, or need long-term history and central alarm management.

What is the difference between SCADA and HMI? An HMI is the operator interface: the screens, trends, alarms and buttons used to monitor and control a process. SCADA is the broader supervisory system that collects data from PLCs and RTUs across a plant or many sites, stores it, manages alarms and sends supervisory commands. An HMI can run on its own beside a single PLC, and most SCADA systems include one or more HMIs as their presentation layer. In short, the HMI is the window, and SCADA is the system behind it.

The two terms appear together so often that many people use them interchangeably. Knowing where one ends and the other begins matters when you specify a new system, troubleshoot a slow display, or evaluate a platform that provides both.

HMI vs SCADA comparison. The HMI covers one machine and answers what it is doing now; SCADA includes the operator HMI plus data acquisition, communications, historian, alarms and supervisory control.
Figure 1. The HMI is one layer of a SCADA system. On its own, it covers one machine or line.

SCADA vs HMI at a glance

The table below compares the two across the points engineers check when specifying a system.

Aspect HMI SCADA
What it is An operator interface (software and display) A supervisory system made of several components
Scope One machine, skid or line Several lines, a whole plant, or geographically distributed sites
Question it answers What is this machine doing right now? How is the whole operation performing?
Purdue model level Level 2 (panel HMIs are mounted next to Level 1 controllers) Levels 2–3
Core functions Visualization, operator commands, local alarms, short trends Data acquisition, supervisory control, central alarm management, historian, reporting, and HMIs
Data storage A short local buffer, if any Historian or database, typically months to years
Connects to Usually one PLC Many PLCs, RTUs and OPC servers over plant and wide-area networks
Typical protocols Vendor PLC drivers, Modbus, OPC UA OPC UA, OPC DA, Modbus, DNP3, IEC 60870-5-104, MQTT
Runs standalone? Yes Yes. It normally includes HMIs, but its data can also feed web dashboards and other applications
Typical example Touch panel on a packaging machine Control room supervising a pipeline or a water distribution network

What is an HMI?

An HMI (Human Machine Interface) is the graphical interface that turns raw industrial data into something an operator can read and act on: mimic diagrams, live values, trends, alarm banners and control buttons. It can be a small touchscreen on one machine or a multi-screen workstation in a control room.

Types of HMI

  • Panel HMI: a rugged touchscreen mounted on a machine or skid, connected to one PLC (Programmable Logic Controller). Its scope is local by design.
  • PC-based or supervisory HMI: operator workstations in a control room. These are usually part of a SCADA or DCS (Distributed Control System).
  • Web and mobile HMI: screens served to a browser, so supervisors and engineers can view the process from any device, with access controlled by user role.

What an HMI does

  • Displays live values and setpoints for a specific process
  • Issues operator commands: start and stop, open and close, setpoint changes
  • Shows alarms and short-term trends for that process
  • Runs independently of any wider supervisory network, if needed

Good HMI design

ANSI/ISA-101.01 is the standard for HMIs in process automation. It defines a lifecycle for HMI design, including a display hierarchy that goes from plant overview down to equipment detail. It is closely linked to high-performance HMI practice, which keeps colour for abnormal conditions so that problems stand out at a glance.

What is SCADA?

SCADA (Supervisory Control and Data Acquisition) is a supervisory system that sits above field controllers such as PLCs and RTUs (Remote Terminal Units). It acquires data from them, often over long distances, and provides centralized visualization, alarm management, historical data and supervisory control. Local HMIs can keep running alongside it at the machine level.

A SCADA system typically includes:

  • One or more HMIs: the presentation layer, also called operator screens or workstations
  • Data acquisition: drivers that poll PLCs, RTUs and OPC servers and consolidate the data
  • Communications: fiber, cellular, radio or leased lines linking remote equipment and sites to a control center
  • Historian: time-series storage for trends, reports, compliance records and analytics
  • Alarm and event management: one place to see, acknowledge and analyze alarms. ANSI/ISA-18.2 is the reference standard for the alarm management lifecycle
  • Supervisory control: setpoints and commands sent to controllers across sites

SCADA is common wherever assets are spread out or processes are large: oil and gas pipelines and wellfields, water and desalination networks, power generation and distribution, mining, and multi-line manufacturing.

For a deeper introduction, read our guide What Is SCADA? A Beginner’s Guide.

What does “HMI/SCADA” mean?

You will often see “HMI/SCADA” or “SCADA HMI” written as one term. It usually refers to software that provides both: the drivers, alarms and history of SCADA, plus the tools to build operator screens. When people ask “what is HMI in SCADA?”, the answer is the presentation layer: the screens, mimic diagrams, trends and alarm lists operators use to supervise everything the SCADA system collects.

PLC vs HMI vs SCADA: where does the PLC fit?

Most confusion disappears once the PLC is added to the picture. The PLC runs the control logic in real time. The HMI shows that process to an operator. SCADA supervises many PLCs and RTUs at once, and keeps the history. A simple way to remember it: the PLC decides, the HMI shows, SCADA oversees.

PLC vs SCADA vs HMI
Figure 2. PLC, HMI and SCADA compared. Note what happens when each one stops.

The last row matters in practice. If a SCADA server goes offline, the PLCs keep controlling the process and local HMIs keep working. Operators lose the central view and history until it returns. This separation is deliberate: supervisory systems should never be a single point of failure for control.

Discover SIOTH® SCADA

Where HMI and SCADA sit in the Purdue model

The Purdue model, used as a reference in ISA-95 and ISA/IEC 62443, splits an industrial architecture into levels. HMIs and SCADA servers belong to Level 2, supervisory control. SCADA historians and reporting often reach into Level 3, site operations. PLCs and RTUs sit at Level 1, and the sensors and actuators they control sit at Level 0.

HMI in SCADA / Purdue model SCADA
Figure 3. HMI, SCADA and PLC mapped to the Purdue model.

The industrial DMZ (demilitarized zone) between Levels 3 and 4 is where OT (Operational Technology) data is passed to IT (Information Technology) systems without exposing control networks directly.

Read more in IT vs OT: Key Differences Every Engineer and IT Manager Should Know.

How SCADA and HMI work together: a reference architecture

In a real deployment, HMIs appear twice: at the machines and in the control room. The animation below follows normal data flow, then an alarm and an operator response.

SCADA HMI architecture / how SCADA and HMI work together
Figure 4. Data flows up from the sites, alarms reach the control room, and operator commands flow back down.
  1. Field devices (sensors, valves, pumps) are wired to PLCs and RTUs at each site.
  2. Local HMIs give operators a real-time view and manual control at the machine or line.
  3. The SCADA data acquisition layer polls the same controllers over the available network, using protocols such as Modbus TCP, DNP3 or OPC UA (Open Platform Communications Unified Architecture).
  4. The historian stores every value with a timestamp for trends, reports and compliance.
  5. Alarm management raises the alarm centrally. Here, a high tank level at Site B appears on the supervisory HMI.
  6. The operator acknowledges the alarm and sends a supervisory command, such as closing the inlet valve, back to the RTU.

A machine-level HMI works on its own. A supervisory HMI is one component of a much larger system, with data acquisition, history and alarm management working underneath it.

From sensor to screen: how one value becomes information

Another way to see the difference is to follow a single measurement. Each layer adds meaning that the previous one did not have.

what is HMI in SCADA
Figure 5. Signal, number, tag, information: what the PLC, SCADA and HMI each add.
  1. Field device: a flow transmitter sends a 4–20 mA current proportional to flow.
  2. PLC: the analog input turns the current into a raw integer. The PLC can control with it, but it has no name or engineering unit.
  3. SCADA: the value becomes a tag, FIC101.PV = 412.7 m³/h, with a quality flag and timestamp, and it is stored in the historian.
  4. HMI: the operator sees “Feed flow, reverse osmosis (RO) train 2” with a trend and a high limit. When flow passes the limit, the alarm appears on screen and is logged.

The same idea extends beyond the control room. Once tags are organized in an asset hierarchy (site, area, unit, equipment), the data can be reused by historians, analytics and business systems without being remapped each time.

HMI only or SCADA? How to decide

do I need SCADA or HMI
Figure 6. Three questions that decide between an HMI-only setup and SCADA.

An HMI is usually enough for a single machine or skid with one PLC, where operators work at the equipment and short-term trends are sufficient.

You need SCADA when any of these apply:

  • You supervise several machines, lines or remote sites from one place.
  • You need months or years of history for reporting, troubleshooting or regulatory records.
  • You need central alarm management, shift handover and an audit trail of operator actions.
  • Engineers or managers need secure remote access to live and historical data.

A standalone HMI usually costs far less than a SCADA deployment, because SCADA adds data acquisition, historian storage, communications, redundancy and often multi-site licensing. Size the system to the operation: architecture built for multi-site supervision adds cost and complexity to a single-line plant.

Common misconceptions

  • “SCADA and HMI are the same product.” No. An HMI is an operator interface. SCADA is a supervisory system that usually includes one or more HMIs.
  • “You need SCADA to have an HMI.” False. A machine-level HMI can run with no supervisory system at all.
  • “An HMI is just a screen.” Modern HMIs often include local logic, alarm handling, recipes and short-term trending.
  • “SCADA controls the process.” Mostly not. PLCs and RTUs run the control logic. SCADA supervises and sends setpoints and commands.
  • “SCADA is outdated.” The concept is not. SCADA is moving to web-based clients, OPC UA and MQTT (Message Queuing Telemetry Transport) connectivity, and integration with IT and cloud systems.

One environment for local screens and supervisory dashboards: SIOTH® Unified HMI

HMI and SCADA are different concepts, but they do not have to be different products. In many brownfield plants, panel HMI software, SCADA software, the historian and management dashboards each have their own design environment, licensing and tag database. The same tag ends up mapped several times, and every change has to be repeated.

HMI SCADA software / unified HMI
Figure 7. Separate tools per level vs one environment with SIOTH®.

SIOTH® takes a different approach. Its Data Flow module connects to more than 100 OT protocols, including OPC UA, OPC DA, Modbus, PROFINET, DNP3 and MQTT. Its Data Model module organizes tags in an ISA-95 compatible asset hierarchy. Its Unified HMI module is a single web-based environment used to build both local operator screens and plant-wide or multi-site SCADA dashboards on that same model.

The practical result: one design environment instead of several, tags modelled once and reused on every screen, and views that scale from a single line to a multi-site operations picture, accessible from any device with a browser.

Discover SIOTH®

Frequently asked questions

Usually, yes. The HMI is the presentation layer of a SCADA system. But an HMI can also exist without SCADA, for example a touch panel connected to a single PLC on one machine.

A traditional SCADA deployment includes at least one operator interface, but its functions do not strictly require a conventional HMI. Data acquisition, alarming and history can also be exposed through web dashboards, reports or APIs (Application Programming Interfaces).

No. A PLC is a hardware controller that runs control logic for a machine or process. SCADA is supervisory software that collects data from many PLCs and RTUs, and sends them setpoints and commands.

A DCS (Distributed Control System) is an integrated control system, usually for one large continuous process plant, where control and operator interfaces come from one vendor and are tightly coupled. SCADA supervises controllers that are often spread over large areas and from different vendors. The line has blurred, and many plants use both.

No. SCADA remains the standard way to supervise distributed industrial operations. What is changing is the technology: web-based HMIs, OPC UA and MQTT connectivity, and integration with historians, analytics and cloud platforms.

A standalone machine-level HMI is typically far less expensive than a SCADA deployment. SCADA adds data acquisition, historian storage, communications, redundancy and often multi-site licensing.

A single machine often only needs an HMI. SCADA becomes necessary when you supervise several machines, lines or sites from a central point, or need long-term history and central alarm management.

HMI/SCADA software generally falls into three groups: packages supplied by PLC and DCS manufacturers for their own hardware, independent SCADA platforms that connect to equipment from many vendors, and web-based platforms that combine SCADA with IT/OT integration. SIOTH® SCADA from Integration Objects belongs to the third group: web-based SCADA and dashboards built on the SIOTH® integration platform, which connects to more than 100 OT protocols.

Related reading

Related Posts