English is currently available.
SCADA & HMI DISCUSSION
I am a student on an internship at a water treatment plant and the terms are used loosely here. There are PLCs in the panels, touch screens on the panel doors that people call HMIs, and a control room with PCs that everyone calls "the SCADA". A senior engineer also mentioned that the neighbouring chemical plant uses a DCS instead.
Which of these actually controls the process, and what would stop working if the SCADA PCs were switched off? Where does a DCS fit in?
The PLC is the controller. It reads the field inputs, runs the logic and the PID loops in a fixed scan, typically every few milliseconds to a few tens of milliseconds, and drives the outputs. It keeps doing that whether or not anything is watching it.
An HMI is the operator's window into one machine or one panel: it displays PLC tags and writes setpoints and commands back. SCADA is the supervisory layer above many controllers: it collects data from all of them over a network, shows plant-wide screens, handles alarms, logs history and lets operators send commands from the control room.
In a properly designed plant, switching off the SCADA PCs should not stop the process. The PLCs keep controlling with their last setpoints, and the local panels still work. What you lose is the overview: central alarms, trends, the historian record and remote commands.
That separation is deliberate. Interlocks and safety functions belong in the controller or in a separate safety system, never in a script on the SCADA server, because a PC, a network switch or a software update can take the supervisory layer away at any time. If you find logic that the process depends on running in SCADA scripts, treat it as a design weakness.
A DCS covers the same functions as PLCs plus SCADA but is supplied as one integrated system: controllers, I/O, operator stations, engineering tools and a single shared tag database. You configure a loop once and the faceplate, alarm and history come with it. It is aimed at large continuous processes such as refining, chemicals and power, with thousands of analog loops, redundant controllers and changes made while the plant runs.
PLC plus SCADA grew from discrete and geographically spread applications: machines, pumping stations, pipelines. Today the two overlap heavily, and the choice is driven more by plant size, redundancy needs and what the site already maintains than by a hard technical boundary.
A way to keep the layers straight is response time and scope. The PLC or DCS controller handles one process unit and reacts in milliseconds. An HMI serves one machine, with a person reacting in seconds. SCADA covers the whole site or several sites, updates roughly once a second or slower, and stores years of data. Above that sit MES and business systems working in minutes to days.
In water and utilities you will also meet the term RTU: a controller built for remote sites, with low power consumption and telemetry protocols such as DNP3 or IEC 60870-5-104, which reports to the SCADA master over radio or cellular links.
Back to SCADA & HMI community
