A SCADA RTU (Remote Terminal Unit) is a ruggedised, microprocessor-based field device that acquires analog and digital signals from field equipment at a remote site.
It executes limited local control logic and communicates collected data to the central SCADA master station over a wide-area network link.
This guide covers RTU hardware architecture, I/O modules, communication protocols, local autonomy, and the differences between an RTU, a PLC, and an IED.
The "remote" in SCADA RTU refers to geography, not capability. Modern RTUs run embedded operating systems, support multiple protocols, and trigger local alarms or fail-safe actions independently of the master station.
This local autonomy separates an RTU from a simple I/O multiplexer — the RTU continues to protect the site even when the SCADA communication link is down.
What Is a SCADA RTU and How Is It Used?
An RTU is the hardware interface between the physical process and the supervisory control layer. It reads sensor inputs, writes actuator outputs, and relays data to the SCADA master station.
The SCADA RTU is installed at the remote site, not the control room. The master station link goes over a wide-area network — cellular, leased serial, licensed radio, satellite, or IP WAN.
The RTU must handle these link limitations — latency, intermittent connectivity, bandwidth — without losing data or abandoning control.
These devices had no microprocessors — the "programming" was done with physical wiring and relay contacts. When a breaker opened, a specific relay contact closed, completing a circuit that sent a specific coded signal back to the control centre.
The introduction of microprocessor-based RTUs in the late 1970s and 1980s transformed this into the programmable, multi-protocol devices we use today. The function is the same — interface between field and control centre — but the capability is vastly greater.
SCADA RTU Hardware Architecture
CPU Module
The CPU module is the intelligence of the RTU. It runs the embedded operating system, executes the local control program, manages I/O scanning, and handles all master station communication.
Modern RTU CPUs use low-power ARM processors with an RTOS. The module contains flash memory, RAM for the real-time database, a real-time clock, and a watchdog timer. See the watchdog timer guide.
Power Supply Module
Remote RTU sites often have unreliable mains power. Most RTUs have a power supply accepting 85 to 265 VAC or 18 to 60 VDC and providing regulated DC to all internal modules.
A battery backup module is almost always included. It maintains RTU operation during mains power outages — critical for sites that must continue monitoring and control when power is interrupted.
Battery capacity is sized for the expected outage: typically 4 to 8 hours for utility substations and up to 72 hours for critical infrastructure.
A power outage at a remote site often coincides with a communication outage — the cell tower or radio repeater may also lose power at the same time.
If the SCADA RTU is storing data locally during a communication outage (store-and-forward mode), the battery must last long enough to keep the RTU running until both power and communication are restored. Design for 72 hours of battery autonomy for critical sites, and test the battery under full load at least annually.
I/O Modules
I/O modules interface the RTU with field devices. Most RTUs use a modular backplane where I/O modules plug in alongside the CPU, allowing I/O expansion without replacing the unit.
Digital Input (DI): Reads discrete on/off signals from breaker positions, valve feedback, pump status, and flow switch contacts. Most RTU DI modules record the state-change time to millisecond resolution for event sequencing.
Digital Output (DO): Sends discrete commands to field devices — trip a breaker, open or close a valve, start or stop a pump. DO modules use relay contact outputs (NO/NC).
Safety-critical DO modules are designed to fail to the safe state on power loss.
Analog Input (AI): Reads continuous measurements from field transmitters — pressure, temperature, flow, level. Standard ranges: 4-20 mA (loop-powered), 0-10 V, and RTD/thermocouple inputs. AI resolution is typically 12 to 16 bits.
Analog Output (AO): Sends continuous setpoint signals to field devices — valve position commands, speed references to drives, setpoints to local controllers. Standard output is 4-20 mA or 0-10 V.
COS detection uses hardware interrupt logic rather than software polling. When a digital input changes state, the hardware immediately captures the event with a timestamp from the RTU's real-time clock — independently of the scan cycle.
This is critical for event sequencing in electrical substations, where multiple protection relays may operate within milliseconds of each other during a fault. COS timestamps allow the SCADA master to reconstruct the exact sequence of events rather than inferring it from scan-cycle data, which might only show that two events occurred "in the same scan."
Communication Modules
The RTU communicates with the master station on its WAN-side interface, and with local field devices on its field-side interface. These are separate communication ports, often using different protocols.
WAN-side: The RTU connects to the SCADA master over DNP3, IEC 60870-5-104, or Modbus. Modern RTUs have dual redundant WAN paths — primary cellular and backup radio, or fibre and backup cellular.
See the DNP3 vs IEC 104 guide for protocol details.
Field-side: The RTU has RS-485 serial ports for Modbus RTU to local devices — energy meters, protection relays, flow computers. An Ethernet port serves IEC 61850 or Modbus TCP for modern IEDs.
SCADA RTU Local Autonomy: Why It Matters
The defining characteristic of a SCADA RTU is the ability to operate independently when the WAN link to the master station is down.
During a communication outage, the RTU continues to scan inputs, timestamp state changes, store events locally, execute local control logic, and maintain outputs in their last commanded or fail-safe state.
When communication is restored, the RTU forwards all buffered events in timestamp order, filling the gap in the historian.
A pipeline RTU on a cellular network may experience daily brief outages during network congestion or base station maintenance. Each outage is typically 15 to 30 minutes.
The store-and-forward buffer should hold at least 24 hours of events at the site's normal event rate — not just twice the typical outage. A rare but extended outage (antenna damage, extended power failure) will produce far more events than normal, as alarms fire and reset repeatedly. A buffer sized for normal conditions will overflow during the events it was most needed for. Size the buffer conservatively, and monitor buffer fill level as a health KPI for each RTU.
This is used in applications where the controlled variable — pressure in a pipeline segment, level in a tank, temperature in a heat trace — must be maintained even when the SCADA communication is down. The master station monitors the loop, adjusts the setpoint remotely, and oversees the trend data. But the actual PID calculation runs in the RTU, with the actuator connected directly to the RTU output.
This architecture — supervisory control at the master, execution control at the RTU — is the design intent of the "supervisory" in SCADA. The master station supervises; the RTU executes.
SCADA RTU vs PLC vs IED: Key Differences
| Feature | SCADA RTU | PLC | IED (Intelligent Electronic Device) |
|---|---|---|---|
| Primary purpose | Remote data acquisition, local control, and WAN communication to SCADA master station | High-speed local machine or process control. Rarely communicates over WAN. | Protection, measurement, or control of one specific piece of equipment (breaker, transformer, relay) |
| Location | Remote field site — substation, pump station, well site, pipeline metering station | Machine panel, local control cabinet, near the process being controlled | In the switchgear or on the protected equipment |
| Scan cycle | 100 ms to 1 second typical. Slower than PLC but adequate for field monitoring. | 1 to 100 ms typical. Fast enough for machine control and motion control. | 1 ms to 20 ms for protection functions. Fastest of the three. |
| WAN communication | Primary function. Multiple WAN protocols built-in: DNP3, IEC 60870-5-101/104, Modbus. | Not designed for WAN. LAN protocols (EtherNet/IP, Profibus, PROFINET) are the norm. | Site-level communication only. IEC 61850 GOOSE/MMS for inter-device communication at the substation. |
| I/O count | Typically 16 to 512 I/O points per RTU. Scalable via I/O module expansion. | 8 to thousands of I/O points. High-density I/O for complex machine control. | Fixed I/O tied to the specific device being protected or measured. |
| Local autonomy | High. Store-and-forward, local alarming, local PID, fail-safe outputs — all without master station. | Moderate. Runs the program continuously regardless of network state. | Very high. Protection functions must operate without any external communication. |
| Environmental rating | Designed for outdoor or harsh environments: -40°C to +70°C, IP65 to IP67, vibration-rated for mobile applications. | Designed for panel-mount in a controlled environment. Less harsh rating than RTU. | Designed for switchgear environment: high voltage proximity, EMC immunity required. |
| Typical industries | Electric utilities, oil and gas pipelines, water and wastewater networks, municipal infrastructure | Manufacturing, automotive, food and beverage, pharmaceuticals, machine automation | Electric utilities, substation protection and control |
RTU I/O Sizing and Communication Estimator
Watch: Why DNP3 Protocol Is Used Between SCADA and RTU
SCADA RTU Questions
External References
- What Is a Remote Terminal Unit (RTU)? | Control.com Technical Articles (2024)
- RTU (Remote Terminal Unit): Architecture and Communication | Tractian (2025)
What We Learn Today
- A SCADA RTU has five core hardware components: CPU module (RTOS, real-time clock, watchdog), power supply with battery backup, I/O modules (DI, DO, AI, AO), and communication modules for both WAN-side SCADA communication and field-side local device communication.
- The defining difference between a SCADA RTU and a PLC is local autonomy. A SCADA RTU continues scanning, alarming, timestamping events, and storing data in its store-and-forward buffer even when the WAN link to the master station is completely down. A PLC is not designed for WAN communication or extended remote autonomy.
- Modern SCADA RTUs support multiple simultaneous protocols: DNP3 or IEC 60870-5-104 to the SCADA master, and Modbus RTU or IEC 61850 to local field devices. Dual-path WAN communication (primary cellular plus backup radio) is standard for high-availability SCADA applications.