SCADA (Supervisory Control and Data Acquisition) is a distributed control architecture that uses remote terminal units (RTUs) or programmable logic controllers (PLCs) to gather real-time electrical telemetry and execute supervisory commands across a wide-area network. In a real installation, it changes electrical operations from localized, manual breaker switching and analog meter reading into centralized, automated, and timestamped remote control. Beginners commonly confuse SCADA with HMI (Human Machine Interface); the HMI is merely the graphical screen the operator looks at, while SCADA encompasses the entire backend communication, data logging, and control logic. Another common mix-up is SCADA versus DCS (Distributed Control System)—DCS is for localized, continuous process control like a refinery, whereas SCADA handles geographically dispersed, discrete electrical assets.
The Core Architecture: RTUs, PLCs, and the Master Station
A functional SCADA system relies on three primary layers: the field devices, the remote telemetry layer, and the master station. Understanding the boundary between these layers is critical when specifying hardware for a new substation or solar farm.
Remote Terminal Units (RTUs) are rugged, low-power microprocessors designed for sparse I/O over high-latency links like cellular or VHF radio. They excel at polling a few dozen breaker statuses and analog transducer values. Programmable Logic Controllers (PLCs), conversely, are high-speed, rack-mounted processors built for dense, local I/O and fast deterministic logic (like motor starting sequences). In modern electrical engineering, the line is blurring with the rise of the RTAC (Real-Time Automation Controller), which merges PLC processing speed with RTU communication protocols.
The Master Station (or MTU) hosts the SCADA server software—platforms like Ignition, Wonderware, or open-source alternatives like ScadaBR. It maintains the central tag database, logs historical data to a SQL or time-series database (like InfluxDB), and pushes setpoints back down to the field. According to NIST SP 800-82 Revision 3, securing the boundary between the Master Station's enterprise network and the OT (Operational Technology) network via industrial DMZs is now a baseline requirement for critical infrastructure.
Polling, Bandwidth, and Latency: A Worked Numeric Example
The most common failure mode in greenfield SCADA deployments is underestimating network latency and polling overhead. Let us look at a concrete numeric example involving a 5MW commercial solar farm utilizing 10 string inverters.
Each inverter exposes 50 Modbus holding registers (voltages, currents, fault codes, active power) via Modbus TCP on port 502. You need to poll all 10 inverters to update the HMI dashboard.
- Total Registers: 10 inverters × 50 registers = 500 registers
- Modbus TCP Payload: A single Modbus TCP read holding registers (Function Code 03) request is roughly 12 bytes. The response header is 11 bytes, plus 2 bytes per register. For 50 registers, the payload is 111 bytes.
- Network Transmission: Over a 100 Mbps fiber link, transmitting 123 bytes takes less than 0.01 ms.
- Device Processing Time: The inverter's internal microcontroller takes roughly 15 ms to read its internal memory, format the Modbus frame, and reply.
If your SCADA master polls the 10 inverters sequentially over a single TCP socket, the total sweep time is 10 × (15 ms processing + 5 ms network overhead) = 200 ms. This easily meets a 1-second update SLA.
The Edge Case: If you scale this to a 50MW utility plant with 100 inverters, sequential polling takes 2 seconds. You will miss your 1-second SLA, causing HMI values to lag and potentially triggering false 'loss of communication' alarms. The engineering fix is to open concurrent Modbus TCP sessions (most modern SunSpec-compliant inverters support 4 to 8 concurrent sockets) or switch to a Report-by-Exception (RBE) protocol like DNP3, which only transmits data when a value changes by a configured deadband.
Where You Meet SCADA in Practice
You will encounter SCADA architectures in any electrical installation where the asset footprint exceeds a single building or requires utility-grade telemetry.
- Utility Substations: Here, SCADA monitors transformer tap changers, capacitor bank switching, and protective relay flags. The standard is strictly IEC 61850 or DNP3 over fiber.
- Utility-Scale Solar and BESS (Battery Energy Storage): Plant controllers use SCADA to throttle active power or inject reactive power (VARs) to meet grid interconnection agreements (PPA). Modbus TCP and MQTT are dominant here.
- Microgrids and Campus Power: University campuses or military bases use SCADA to sequence diesel generators, manage automatic transfer switches (ATS), and shed non-critical loads during peak demand windows.
- Water/Wastewater Lift Stations: While not purely 'electrical', the VFDs (Variable Frequency Drives) and motor control centers (MCCs) in these remote sites are polled via cellular RTUs to monitor amp draw and predict motor bearing failures.
Protocol Selection Matrix
Choosing the wrong protocol at the edge gateway leads to expensive middleware licensing or hard-coded polling scripts. Below is a comparison of the four protocols you will actually specify in 2026.
| Protocol | Topology | Best Use Case | Weakness |
|---|---|---|---|
| Modbus TCP | Master/Slave (Polling) | Commercial DERs, inverters, VFDs, basic meters. | No native timestamps; high bandwidth on large polls. |
| DNP3 | Master/Outstation (RBE) | Utility substations, transmission, large BESS. | Complex to configure; requires specialized outstation licenses. |
| IEC 61850 | Peer-to-Peer (GOOSE) | High-speed substation automation, protection schemes. | Extreme engineering cost; requires dedicated fiber networks. |
| MQTT (Sparkplug B) | Publish/Subscribe | Cloud-connected microgrids, IIoT edge computing. | Not natively supported by legacy protective relays. |
For a deep dive into the frame structures and deadband configurations of the utility standard, the DNP Users Group maintains the definitive technical reference for DNP3 outstation implementation.
Decision Path: Specifying Your Edge Gateway
When bridging field devices to the SCADA master, you need an edge gateway. Use this decision tree to select the exact hardware for your bill of materials.
| IF your field condition is... | AND your SCADA master requires... | THEN specify this hardware class |
|---|---|---|
| Serial Modbus RTU devices (meters, old VFDs) | Modbus TCP polling | Basic Serial-to-Ethernet Gateway |
| Modbus TCP inverters / BESS | DNP3 or secure MQTT to utility | Industrial Protocol Converter / RTAC |
| Substation Protective Relays (SEL, GE) | IEC 61850 GOOSE or DNP3 | Substation-grade RTAC with PRP/HSR |
For 90% of commercial solar, BESS, and microgrid projects integrating Modbus TCP/RTU devices into a central SCADA or cloud platform, deploy the Moxa MGate MB3280. It handles serial-to-TCP conversion, supports up to 256 concurrent connections, and includes built-in MQTT publishing.
However, if your project is a utility-interconnected substation where the AHJ (Authority Having Jurisdiction) or utility mandates native DNP3 outstation support and IEC 61850 routing, step up to the Schweitzer Engineering Laboratories (SEL) SEL-3373 RTAC. As detailed in the SEL-3373 product specifications, it provides the deterministic processing and ruggedized I/O required for high-voltage environments. Default Recommendation: Start with the Moxa MB3280 for standard DERs; only spec the SEL-3373 when utility interconnection agreements explicitly mandate DNP3/IEC 61850.
Frequently Asked Questions
Do I need a dedicated SCADA server PC, or can I run it on a standard IT server?
You can run SCADA software (like Ignition or WinCC) on a standard enterprise server or VM, provided it meets the software vendor's IOPS and CPU requirements. However, the server must be housed in an environment with UPS-backed power, and the network path to the OT (Operational Technology) layer must pass through an industrial DMZ to comply with IEC 62443 security standards.
What is the difference between a SCADA 'tag' and a PLC 'register'?
A PLC register (e.g., %MW100) is a raw memory address holding a 16-bit integer. A SCADA tag is the software abstraction of that register. The tag applies engineering units (scaling a 4-20mA raw value of 5500 to 120.5 Volts), sets alarm limits (High-High, Low), and logs historical trends. The SCADA master maps the tag to the PLC register via a device driver.
Can SCADA systems operate if the WAN (Wide Area Network) connection drops?
Yes, if designed correctly. Local PLCs and RTUs retain their autonomous control logic (e.g., a PLC will still trip a motor if a local hardwired overload relay opens, even if the fiber link to the SCADA master is severed). SCADA is strictly supervisory; it should never be the sole mechanism for critical, life-safety, or equipment-protection interlocks.
