What Is SCADA?

SCADA, short for supervisory control and data acquisition, is a system that collects live data from equipment spread across a site or a region, presents it to operators and lets them act on it. The word “supervisory” matters: the fast, second-by-second control of a pump or valve stays with a local controller, while SCADA watches the whole process, raises alarms and sends set points and commands from above.

A typical cycle has four steps. Sensors and instruments measure levels, pressures, flows, temperatures and switch states. PLCs and RTUs read those signals, run local logic and hold the values as tags. The SCADA server polls the field devices, or receives changes as they happen, over a network or telemetry link. Operators then see the process on HMI screens, acknowledge alarms and send commands back down the same path.

Everything that passes through is time-stamped and stored in a historian, a database built for time-series data. That history is what turns SCADA from a remote control into a tool for reports, trend analysis, compliance records and maintenance planning.

Every SCADA system is a mix of hardware and software in layers, from the field instruments to the control room. The names vary between vendors, but the building blocks are the same.

SCADA is often confused with a distributed control system (DCS). Both supervise industrial processes and both use operator screens, but they grew up for different jobs. In practice the line has blurred, and many plants run both.

A useful rule of thumb: if the equipment is spread over kilometers and the links are slow or intermittent, the system is usually SCADA. If it sits in one building and runs hundreds of tightly linked control loops, it is usually a DCS.

The first SCADA systems of the 1960s and 1970s were single mainframes with proprietary links to their field devices. In the 1980s they moved to networks of minicomputers sharing the load. From the 1990s they adopted Ethernet, TCP/IP and open protocols such as Modbus, so equipment from different vendors could share one system.

Current SCADA software usually runs on standard servers or virtual machines, serves screens to web browsers and tablets, and publishes data to other systems through OPC UA or MQTT. Edge computers at remote sites can now buffer data, run local analytics and keep logging if the link drops, then forward the backlog when it returns. SCADA has not been replaced by IIoT; in most plants it has become the source of the data that IIoT and analytics tools use.

SCADA appears wherever a few people have to supervise many assets. The sector shapes the protocols, the links and the rules.

SCADA was designed for closed networks, and older protocols such as Modbus and early DNP3 have no authentication. Once the system is connected to business networks or the internet, an attacker who reaches it can read data or send commands. Attacks on power and water systems have made SCADA security a regulatory issue on both sides of the Atlantic.

The main reference is the IEC 62443 series, which sets out zones, conduits and security levels for industrial control systems, with NIST SP 800-82 as the US guide. In the USA, water and energy operators fall under the NIS Regulations and are assessed against the NCSC Cyber Assessment Framework. In the US, bulk electric operators follow NERC CIP and CISA publishes advisories for industrial control systems. Common measures are network segmentation, secure remote access, Secure Authentication for DNP3, patch planning around maintenance windows and hardened computers at each level.

SCADA hardware is usually ordinary industrial computing chosen for each layer: industrial panel PCs as operator screens beside the process, DIN rail PCs and industrial IoT gateways in cabinets at remote sites, and rack mount servers for the SCADA servers and historian.

We supply and integrate the industrial computers for each SCADA layer as standard, with the operating system, drivers and network settings prepared before the systems ship.