What Is SCADA and What Hardware Does It Need?
SCADA (Supervisory Control and Data Acquisition) is the software architecture used to monitor and control industrial processes — reading sensor data from PLCs and RTUs, visualising it on operator screens, logging trends, and issuing control commands. A SCADA deployment is typically split across several roles: the supervisory server or historian, the HMI (Human-Machine Interface) operator station, and the communication gateway that talks to field devices over Modbus, OPC UA, DNP3, IEC 61850 or MQTT.
The hardware requirements follow from that role. SCADA servers and HMIs are usually not compute-hungry in the burst sense; they are availability-hungry. They must boot reliably, run 24×7, survive dusty or hot control rooms, and keep the network link alive for years at a time. A fanless industrial mini PC with a solid-state drive, a wired Gigabit Ethernet port and a wide-input DC power supply covers the majority of SCADA HMI and edge-gateway installations.
Key Hardware Requirements for SCADA Deployments
| Requirement | Why it matters for SCADA | Typical specification |
|---|---|---|
| Fanless cooling | No fan = no dust ingestion, no bearing failure, no maintenance interval | Passive heatsink chassis, 0–50 °C operation |
| Wired Ethernet | SCADA traffic must be deterministic and secure; Wi-Fi is often prohibited on the control VLAN | 1× or 2× Gigabit RJ45 |
| Solid-state storage | Historians perform frequent small writes; HDDs fail early | 128 GB – 1 TB SSD |
| Memory | HMI graphics, trend buffers, OPC UA address space | 8 GB – 16 GB (16 GB comfortable) |
| Processor | Tag throughput and screen redraw, not raw compute | 4-core Intel Celeron/N-series class is sufficient for most HMIs |
| OS support | Vendor software is often certified per OS | Windows 11 Pro/IoT, Linux, or vendor-certified image |
| Mounting & power | Panel, DIN rail or VESA inside a cabinet | 12 V DC or 9–36 V wide input |
| Serial / fieldbus | Legacy PLCs still use RS-232/RS-485 | USB-to-serial or onboard COM ports |
Typical SCADA Use Cases
The most common deployment is an HMI operator station in a control room or on the plant floor, running a SCADA client that connects to a central server over the plant network. These stations are frequently installed in multiples, so a compact, low-power, fanless unit that mounts behind a monitor or on a VESA bracket is far easier to deploy than a full tower PC.
A second common role is the SCADA edge gateway or protocol converter, sitting between field equipment and the supervisory layer. Here the machine runs an OPC UA server, a Modbus TCP/RTU master, or a store-and-forward buffer, often under Linux, and reports upward over Ethernet, 4G or VPN.
Other frequent applications include data historian nodes for small sites, SCADA test and simulation rigs used during commissioning, water and wastewater treatment plant HMIs, energy sub-station gateways, building management systems, manufacturing line dashboards and remote pumping station controllers where an unattended, reboot-resilient box is essential.
Choosing Between Windows and Linux for SCADA
Most commercial SCADA packages — and the majority of legacy HMI runtimes — are certified on Windows. For those, a Windows 11 Pro or Windows 11 IoT image with a licensed, activated installation removes a deployment headache. For open-source stacks (Ignition Edge, Node-RED, Graf
