Remote Terminal Unit, RTU
A remote terminal unit is a ruggedized industrial controller deployed at a remote field site to acquire local I/O and communicate it to a central SCADA host. RTUs sit at pipeline valve sites, water reservoirs, electrical substations, oil & gas wellheads, and other locations where a full PLC and control building would be uneconomical.
Read one of your own drawings.
Drop a P&ID, instrument index, or schedule. Tagsight reads it to the tag and opens a workspace you keep when you sign in.
PDF · DWG · DXF · TIFF · PNG · XLSX
The RTU was designed to solve the problem of monitoring and controlling unmanned sites where installing a full instrument room and control building is not justified. A pipeline valve station 40 km from the nearest operations center needs to report pressure, temperature, and valve position, and to respond to open, close commands from the SCADA center, but the site has no resident personnel. The RTU is the device that bridges the field instruments at that site to the wide-area communications link. Early RTUs in the 1960s and 1970s were simple data concentrators with minimal local logic. Modern RTUs are full programmable controllers. A Schneider Electric SCADAPack, Emerson FloBoss, ABB RTU560, GE ControlWave, or Yokogawa STARDOM runs IEC 61131-3 logic, hosts multiple communication ports, and manages local alarming and data buffering during communications loss. The communications layer is a defining feature that distinguishes RTU selection from PLC selection. An RTU specification lists not only I/O count and logic capacity but also supported radio protocols, licensed UHF, VHF, 900 MHz spread spectrum, cellular interfaces, 4G, 5G with SIM management, satellite uplinks, Iridium, Inmarsat, VSAT, and protocol support, DNP3, IEC 60870-5-101, 104, Modbus, MQTT Sparkplug B. RTU I/O lists mirror the format of plant I/O lists. Tag number, signal class, range, and source P&ID or schematic reference, plus an additional column for the SCADA register address or DNP3 point number that maps the field signal to the SCADA host's data model.
RTU vs PLC, the line is blurred.
Historically RTUs were simpler than PLCs. Single-purpose data-acquisition with limited local control logic and an emphasis on resilient long-distance communications. Modern RTUs are programmable controllers with PLC-class logic capability plus radio, cellular, or satellite communications integrated. Vendors like SCADAPack, ControlWave, RTU-Lite, Bristol Babcock, and Emerson FloBoss straddle the RTU, PLC line. The distinction today is mostly about deployment. A PLC sits in a control room or panel. An RTU sits in a roadside enclosure 50 km from anywhere.
Communications protocols.
DNP3, Distributed Network Protocol is dominant in electrical and water utilities. Modbus over RTU and TCP is broadly used. IEC 60870-5-101, 104 in European electrical applications. Proprietary protocols, CDC Type II, Allen-Bradley DF1 survive in legacy installations. Cellular and satellite gateways increasingly carry MQTT and Sparkplug B as a convergence layer between OT field data and IT business systems.
I/O architecture at an RTU site.
A pipeline valve site RTU might carry. One AI channel for line pressure, PT-101 over 4-20 mA, one AI for temperature, two DI channels for block valve position feedback, ZSO-501 open, ZSC-502 close, one DO channel for the valve actuator command, and two DI channels for gas-detection alarm and cabinet intrusion. Total I/O. Four analog, two discrete inputs, one discrete output. The RTU I/O list for this site lists these seven points with their tag identifiers, signal classes, and SCADA register addresses. The SCADA host polls the RTU over the DNP3 link and maps each register to an HMI display point in the control center.
Store-and-forward and event sequencing.
RTU deployments differ from plant DCS deployments in how they handle communications outages. A DCS runs on a deterministic fiber or coaxial LAN that rarely fails. A wide-area RTU link drops regularly due to radio propagation, cellular coverage gaps, and satellite blackout windows. An RTU must buffer data locally during a link outage and upload the buffered data with accurate timestamps when the link is restored. DNP3 and IEC 60870-5-101 both support time-stamped event records and unsolicited reporting to address this. The SCADA historian receives a continuous, ordered record of events even when the link was intermittent, because the RTU stored and retransmitted them in sequence.
Power supply and environmental hardening.
Remote RTU enclosures draw power from a combination of mains, solar panels, and battery backup, sized for the site's power availability. An unmanned desert pipeline site may rely entirely on solar and battery with no grid connection. The RTU and its communications equipment must operate continuously through the full temperature range at the site, which can span -40 C to plus 70 C for outdoor enclosures in continental climates. Surge protection on all external connections, analog inputs, communications lines is standard because lightning is the most common cause of RTU hardware failure at isolated sites.
Frequently asked.
What is a typical RTU deployment.
Pipeline valve site. Pressure transmitter, valve position feedback, gas detection, intrusion alarm, communications back to the SCADA centre over cellular and satellite redundant links. Water reservoir. Tank level, pump run-status, chlorine residual, comms back over licensed-band radio.
Do RTUs run safety functions.
Some are certified for safety-related use, SIL-rated RTUs from major vendors, but the majority of safety-instrumented function execution at remote sites is delegated to a separate certified-safe logic device, with the RTU handling supervisory monitoring only.
How is an RTU different from a field gateway.
An RTU acquires I/O natively. It has physical analog and digital terminals that connect directly to sensors and actuators in the field. A field gateway translates between existing field protocols, Modbus, DNP3, Profibus and a northbound communications layer, OPC UA, MQTT without connecting to raw field signals. Many modern products blur the line by combining I/O terminals with protocol translation in a single enclosure.
How does DNP3 differ from Modbus for RTU communications.
Modbus is a simple polling protocol. The master asks, the slave responds. DNP3 adds features specifically for SCADA over unreliable wide-area links. Unsolicited reporting, the RTU can push data to the SCADA host when an event occurs, without being polled, time-stamped events with millisecond resolution, integrity polls, the SCADA host asks for all current values to resynchronize after a link outage, and data-link-layer acknowledgement for reliable delivery over noisy links. DNP3 is the protocol of choice when event sequence accuracy matters, as in electrical switching and interlock coordination.
What I/O list columns are unique to an RTU project.
RTU I/O lists add a SCADA register address or DNP3 point number column, so the SCADA host can map the incoming data to the correct HMI tag, a site or RTU identifier column, there are multiple sites, each with its own RTU, and a communications path column, cellular primary, satellite backup, or radio only. The base signal-class, range, and tag columns are the same as a plant I/O list.