PLC vs DCS vs SCADA vs HMI: what each one does

PLC and DCS are controllers that run control logic, SCADA is a supervisory system that collects data from many controllers, and an HMI is the screen where operators see and operate the process.

The four terms are often used as if they were alternatives, but most plants use two or three of them together. This guide sets them side by side, shows where each sits in a plant and explains how to decide what a site needs. For the full picture of the supervisory layer, start with what SCADA is and how its architecture works; for the controller itself, see what a PLC is.

The simplest way to tell them apart is to ask what each one is responsible for. Controllers decide, supervisory systems watch and record, and screens let people take part.

The table compares their job, scale and typical use. The product names in the last row are the ones that appear in Citia project records, not a market survey.

Each system has its own level in the plant hierarchy. Seeing them as layers removes most of the confusion.

ISA-95, the ISA model for linking plant control to business systems, puts sensors and actuators at level 1, PLCs and DCS controllers at level 2, and SCADA with manufacturing operations at level 3. Business planning and ERP sit at level 4. HMIs appear wherever people need a view: on a machine, in a control room, or inside a DCS operator station.

NIST SP 800-82 Rev. 3, the US guide to operational technology security, describes the same families of systems from a security angle. Its point for owners is practical: every layer is a separate asset with its own software, accounts and backups.

Safety systems sit beside these layers, not inside them. An emergency shutdown or safety instrumented system (SIS) has its own controller, often a safety PLC, so that a fault in the PLC, DCS or SCADA cannot block a protective action. SCADA and the DCS usually show its status and record its trips, but they do not replace it.

A PLC and a DCS both run control logic, so the difference is less about what they do and more about how the system around them is built.

A DCS (distributed control system) comes as one package. Controllers, I/O, operator stations, the alarm system and the engineering tool share a single database, so a tag defined once appears everywhere. Redundant controllers and networks are normal. That integration suits refineries and continuous plants with many analog loops that interact.

A PLC-based system is assembled. The PLC, SCADA software, network and HMI may come from different vendors and are joined through drivers and protocols. It is flexible and suits discrete logic, packaged equipment and sites that grow area by area. The price of that flexibility is integration work: every tag, alarm and address has to be mapped between products.

Modern products overlap. Some PLC families support redundancy and large I/O counts, and some DCS platforms are sold for small plants. Decide on the needs of the process, not on the label.

The choice also shapes the long term. A DCS ties the site to one vendor's upgrade path, which simplifies planning but narrows the options. A mixed PLC and SCADA system can be renewed piece by piece, yet every piece has its own lifecycle to track. The trade-offs are compared in repairing or migrating obsolete PLC and SCADA.

An RTU (remote terminal unit) is a controller built for remote or scattered sites that reports to SCADA over long links. Think of it as a PLC designed for distance.

RTUs appear where the control room is far away: island berths, pipeline stations and remote pump houses. They are built to cope with slow or interrupted links, often buffering data and sending it when the link returns. At an island berth for LPG or fuel unloading, for example, the RTU gathers instrument data so SCADA can show it in real time; the island berth RTU and SCADA bulletin describes that setup.

In practice the line between RTU and PLC is thin. Many sites use a PLC with a good communication module in the RTU role, and project documents may say RTU/PLC for the same box.

Pipelines show why the link matters as much as the controller. On the Balongan-Plumpang fuel pipeline, pressure transmitters, RTU/PLC devices and field panels report to SCADA over fibre optic. When converters degraded, data dropped intermittently and the shutdown trigger path was affected, until Citia replaced the converters and retested monitoring and shutdown. See the Balongan PressMon restoration.