What Is SCADA? How It Works, Parts and Costs

2026-10-02T00:00:00Z

SCADA stands for Supervisory Control And Data Acquisition. It is software that collects data from PLCs and other field devices across a plant or a wide area, shows it to operators, raises alarms, records history and lets people send commands back.

Think of a water utility with a dozen pump stations spread across a county. Each station has its own controller that runs the pumps. SCADA is how one person in one room sees all twelve, hears about a problem within seconds, looks at last Tuesday's flow, and starts a pump from a chair.

How a SCADA system works

Every SCADA system has the same shape, whatever the brand. Sensors and actuators sit at the bottom. Above them, controllers read the sensors and run the logic that keeps the process going. A network carries values from the controllers to a server, and the server turns raw values into screens, alarms and history.

Two things about this stack are worth knowing.

The controllers do the controlling

A PLC keeps running its logic whether or not the SCADA server is up. SCADA is supervisory: it watches, records and sends commands such as a setpoint change or a start request. If the server reboots, the process does not stop. This is a design rule worth testing on any system you buy.

The server talks to devices in their own language

A driver for each protocol reads registers or tags from the controller on a schedule, or receives reports the controller sends on its own. The server turns those into named values and passes them on to everything else.

The parts of a SCADA system

HMI screens

The screens are what operators see: a process graphic with live values, a pump with a color that shows if it is running, a button to start it. Good screens keep the normal state plain and make abnormal states easy to spot. A bright screen full of moving color tires people out and hides the one thing that matters.

Alarms

An alarm tells an operator that something needs attention now. The system watches a tag against a limit or a state, raises the alarm, keeps it on a list until someone acknowledges it, and logs who did and when. An alarm system turns annoying when alarms are not held to a rule: every alarm should need a response, have a priority and have a known action.

The reference standard is ANSI/ISA-18.2, Management of Alarm Systems for the Process Industries, which is aligned with IEC 62682. It describes an alarm life cycle: write a philosophy, rationalize each alarm, set priorities, then measure and improve. Features such as shelving (silencing one alarm for a set time, with a record) and alarm-rate reports are how a SCADA product supports it.

Historian and trends

The historian stores tag values over time so you can plot them. A trend is the plot. The questions it answers are the ones people ask after something goes wrong: what was the tank level in the hour before the overflow, and when did the pressure start to drift? Most historians store a value when it changes by more than a set amount, or on a fixed interval, to keep the data compact.

Reports

Reports turn history into documents: daily runtime and flow totals, a monthly summary for a regulator, a shift log. They are usually scheduled and sent as PDF or email. If a compliance report matters to your plant, ask any vendor to produce your real one during the demo.

Users and audit

Each person should have their own login and only the rights they need: an operator can acknowledge alarms, a technician can change setpoints, an engineer can edit screens. An audit trail records who changed what and when. After an incident, that record is the quickest way to find out what happened.

SCADA vs HMI vs PLC vs DCS

These four terms get mixed up constantly, but they do different jobs.

Term	What it is	Scope	Runs the process?
PLC	A rugged controller that reads inputs and runs logic in a fast scan	One machine or process area	Yes
HMI	A screen for operating a machine or area	One machine or one panel	No
SCADA	Software that supervises many controllers, with screens, alarms and history	A plant, or many sites	No, it supervises
DCS	An integrated control and operator system for a continuous process	One large plant	Yes

PLC

A programmable logic controller is a small industrial computer that reads inputs, runs your logic every few milliseconds and writes outputs. It is built for reliability and for predictable timing. Logic is usually written in ladder or structured text, per IEC 61131-3. A PLC has no screen of its own beyond what you attach.

HMI

A human-machine interface is the operator's window into a controller: a touchscreen on a machine, or a screen on a PC. An HMI shows values and sends commands, and it usually talks to one controller or a few.

SCADA

SCADA sits above the controllers. It collects from many of them, often from several vendors, stores history, manages alarms and users centrally, and serves screens to many operators. Its HMI part is only one piece.

DCS

A distributed control system is sold as one package: controllers, I/O, network, operator stations and engineering tools designed together. It has traditionally been the choice for continuous processes such as refining, chemicals and large power plants, where the control itself is the main product.

The lines blur. A large panel HMI can log history and raise alarms. A modern SCADA platform can run control scripts and serve a whole plant. A DCS can supervise remote sites. When a vendor says "SCADA" or "DCS," ask what it does in your project, and ignore the label.

Common SCADA protocols

A protocol is the language a controller speaks over the network. A SCADA server needs a driver for each one in your plant. These are the ones you will meet most.

Modbus TCP and Modbus RTU. A simple register-based protocol dating from 1979. RTU runs over serial lines such as RS-485, and TCP runs over Ethernet. You see it on meters, drives, small PLCs and a great deal of third-party equipment. It has no built-in security.
EtherNet/IP. The Rockwell Automation and ODVA protocol, built on the Common Industrial Protocol (CIP). It is how most SCADA systems read ControlLogix and CompactLogix PLCs, often by tag name.
OPC UA. A vendor-neutral standard that carries data and its description, with encryption and certificates built in. You see it as the common bridge between products from different vendors, and in newer controllers that include an OPC UA server.
DNP3. Common in water, wastewater and electric utilities. It was designed for remote sites on slow or unreliable links, and it can send timestamped events, so a breaker trip is recorded at the time it happened, not at the time it was polled.
S7. The protocol used to reach Siemens S7-300, S7-400, S7-1200 and S7-1500 controllers. Newer models need access settings enabled in the PLC before an outside system can read them.
BACnet. The standard for building automation: air handlers, chillers, boilers and VAV boxes. BACnet/IP runs over ordinary Ethernet.

If your equipment speaks something else, there is usually an OPC UA server or a gateway that converts it. Check the driver list before you buy, since a missing driver can cost more than the software.

Where SCADA is used

It is used anywhere something has to be watched and controlled from a distance, or from one place for many things. Five common settings:

Water and wastewater

A lift station pumps sewage from a low point to the next stage. Level sensors in the wet well start and stop pumps in a lead and lag order. SCADA shows the level, counts pump runtime, and alarms on high level or a failed pump, so a crew can get there before the well overflows. The station reports over radio or cellular to a central server.

Food and dairy

A dairy barn's ventilation needs fans staged by temperature and air speed so cows stay comfortable, and a failed fan matters on a hot day. SCADA runs the staging setpoints, shows each fan row, records temperatures and sends a text if the barn gets too warm. In processing, the same system records the temperatures and times that auditors ask for.

Oil and gas

A pipeline pump station is often unmanned and hours from the office. An RTU or small controller reads pressures, flows and motor status. SCADA polls it over radio, satellite or cellular, alerts on a pressure excursion and lets a controller in an office start or stop a unit.

Power

A substation has breakers, transformers and protective relays that report status, and a trip must be logged to the millisecond. SCADA gives the operator a one-line view of the network and a sequence of events after a fault. DNP3 is the common link.

Building systems

A campus has air handlers, chillers and boilers from several vendors on BACnet. SCADA gives facilities staff one set of screens, an alarm list and energy trends, so a stuck valve shows up as a trend and not as a complaint.

What SCADA costs and how it is licensed

Price depends mostly on how the vendor counts. The common models:

Per tag. You buy a tag count, such as 500, 1,500 or 5,000. It is easy to start small, and cost rises as the plant grows.
Per client or seat. You pay for each operator screen, either concurrent (at the same time) or named (a specific person or machine).
Per server or per site. One license covers a server and whatever connects to it.
Per driver or module. The base is priced low and each protocol, historian or reporting feature is added on.
Subscription or perpetual. A subscription is paid every year and ends if you stop. A perpetual license is bought once and usually has an optional annual support or update plan.

Whichever model you compare, price your own plant: your tags, your operators, your drivers, your historian and five years of support. Also ask what happens if you grow, and what happens if you stop paying.

Raylux sells it this way. The gateway is a perpetual license at $995, with every driver included and unlimited tags. Operator screens and the historian are modules you add when you need them. The details are on the pricing page.

How to choose a SCADA system

Use this list when you compare products. Each item has caused real trouble when skipped.

Drivers for your PLCs. Confirm every protocol and model you have is supported natively, and find out what a missing one costs.
Historian. Check where the data is stored, how long it is kept, how it is queried and whether you need a separate database server.
Alarm handling. Look for priorities, acknowledgement, shelving, an alarm history and a way to report alarm rates, in line with ISA-18.2.
Security and audit. Look for individual logins, role-based rights, encrypted connections and an audit log of changes and commands.
Licensing model. Work out the total for your tag count, clients and years, and note what is metered.
Offline and edge. Ask what happens when the link to the server is lost. A site should keep running and keep logging.
Lock-in. Check that you can export your tags, screens and history in open formats, and that screens run in a browser rather than needing an installed client.
Support. Find out who answers the phone, how fast, and whether you can reach an engineer and not just a ticket queue.

Frequently asked questions

Is SCADA the same as an HMI?

No. An HMI is the screen an operator looks at. SCADA is the larger system behind it: the data collection, alarms, history and commands, plus the screens. Every SCADA system has HMI screens, but an HMI on a single machine is not SCADA.

Do I need SCADA if I already have a PLC?

Not always. A PLC runs the control logic by itself, and a small panel on the machine is often all one machine needs. You start to need SCADA when you want one view of several PLCs or sites, alarm history, trends over months, remote access, or records for audits.

What is a historian?

A historian is the part of a SCADA system that stores tag values over time, each with a timestamp and a quality flag, so you can trend them and report on them later. It is usually a time-series store built to take many writes per second and keep years of data compactly.

Is SCADA secure?

It can be, depending on how it is deployed. Protocols such as Modbus have no authentication at all, so the network design has to do the work: keep control networks off the public internet, separate them with firewalls, give every person their own login with only the rights they need, use encrypted connections such as OPC UA with security or HTTPS, patch the servers, and keep an audit log. IEC 62443 is the standard most programs follow.

Can SCADA run on a Raspberry Pi or an ARM panel?

In general, yes if the software is built for it. SCADA gateways need modest CPU and memory, and many run on ARM64 Linux. It comes down to whether the vendor ships an ARM build and whether the hardware is rated for the job: flash storage wear, power loss, heat and vibration are where hobby boards fail. Raylux's gateway, Nexus, runs on ARM64 Linux, and one described deployment runs on an ARM64 touchscreen panel. The ARM64 build is provided on request.

What is the difference between SCADA and a DCS?

A DCS is built to control a continuous process inside one plant, with the control and the operator system engineered together. SCADA is built to supervise many controllers, often spread over a wide area, on top of whatever PLCs and RTUs are already there. Modern products overlap, so the label matters less than what the system must do.

How much does SCADA cost?

It varies a lot, because vendors license it differently: by tag count, by client or seat, by server, by driver, or by subscription. Compare the total for your own tag count, number of operators, drivers and years of support, not the headline number.

Where to go next

I build and commission these systems for a living, and Raylux is the SCADA gateway we make. If you would rather see one running than read about it, the download is free to try.

Raylux Insights