SCADA Over Cellular

What Is SCADA and Why Does It Need a Network?

SCADA stands for Supervisory Control and Data Acquisition. It is the software and hardware architecture used to monitor and control industrial processes across geographically distributed sites – power substations, water treatment works, gas compressor stations, solar farms, manufacturing lines, transport infrastructure, and more.

At its most basic, a SCADA system consists of a control centre – the master terminal unit (MTU) or SCADA server – that communicates with remote field devices. Those field devices are either remote terminal units (RTUs), which collect analogue and digital signals from sensors and actuators, or programmable logic controllers (PLCs), which execute local control logic. In more modern deployments you will also encounter intelligent electronic devices (IEDs) – microprocessor-based relays and protection devices used heavily in electrical substations.

The human-machine interface (HMI) is what the operator actually sees: a graphical representation of the process, with live values, alarm states, and control buttons. Behind it, the SCADA server is constantly polling or receiving data from every field device in the network.

None of this works without a communications infrastructure to carry data between the control centre and the field. That has historically meant leased lines, radio, or private WAN. Cellular has progressively replaced all three.

Industries That Depend on SCADA

While the energy sector is the most visible user of SCADA – electricity generation, transmission, and distribution are built on it – the same architecture appears across a wide range of sectors:

• Energy and utilities – electricity distribution networks, substations, renewable generation sites (solar, wind, battery storage), smart meters, demand response
• Water and wastewater – pump stations, treatment works, reservoir level monitoring, pressure management zones, flood control
• Oil and gas – pipeline SCADA, compressor stations, wellhead monitoring, tank level management, leak detection
• Transport – level crossings, signal infrastructure, tunnel ventilation, highway traffic management systems
• Building automation – building management systems (BMS) in large facilities; often uses BACnet rather than traditional SCADA protocols, but the connectivity requirements are identical
• Agriculture and irrigation – remote pump monitoring, soil sensors, irrigation control across large land areas
• Manufacturing – production line telemetry, environmental monitoring, condition-based maintenance

Why Send SCADA Data to the Cloud?

Traditional SCADA ran on closed, private networks by design. The control centre was a dedicated facility. Field devices communicated over dedicated circuits – serial links, private radio, or leased lines. Data stayed within the operational boundary. That architecture made sense when the threat model was physical and the tooling was proprietary.

The shift toward cloud-based SCADA platforms has been driven by several converging factors, and the connectivity question – how to get data from a remote field site to a cloud endpoint reliably and securely – is what makes cellular so relevant.

Reasons for Cloud Migration

Multi-site visibility. A water company operating 200 pump stations across a region cannot economically maintain a private WAN to every site. Cellular plus cloud gives every site an IP uplink. All telemetry lands in a single platform, aggregated and searchable.

Predictive maintenance. Cloud analytics platforms – including SCADA-specific tools like Ignition (Inductive Automation), AVEVA, and Wonderware, as well as general IoT platforms like Azure IoT Hub, AWS IoT Core, and Google Cloud IoT – can run anomaly detection and machine learning against historical time-series data at a scale that an on-premise SCADA server cannot match.

Remote access without VPN complexity. An engineer can pull up a live HMI view from a laptop or mobile device without being on the corporate WAN. Modern platforms handle authentication and access control at the application layer.

Eliminating leased lines. A 4G SIM in an industrial router typically costs a fraction of what an MPLS circuit or leased line costs per month, with greater flexibility and no minimum contract tied to physical infrastructure.

Integration with IT systems. Cloud-hosted SCADA data can feed into ERP, asset management, billing, and reporting systems that live in the same cloud environment. The IT/OT convergence question becomes much simpler when both sides are talking IP to the same platform.

Which Cellular Technology for SCADA?

There is no single answer – the right cellular technology depends on the data volume, latency requirement, power budget, and deployment environment. Here is how the main options stack up for SCADA applications.

4G LTE – The Workhorse (Today)

The overwhelming majority of SCADA cellular deployments in the UK and globally run on 4G LTE. Within that, two LTE categories dominate:

LTE Cat 1 offers download speeds up to 10 Mbps and upload up to 5 Mbps. It is well-matched to SCADA: the protocol traffic is relatively low-bandwidth, but you need reliable latency and a genuine IP connection, not LPWAN-class performance. Cat 1 modules are cost-effective, widely available, and supported by all UK networks. The Teltonika TRB142 (RS232) and TRB145 (RS485) are examples of compact gateways built around LTE Cat 1 specifically for this kind of serial-to-cellular conversion.

LTE Cat 4 (up to 150 Mbps down, 50 Mbps up) is the natural step up for deployments that need more headroom – for example, where the same router is backhauling SCADA data alongside HD camera feeds, firmware updates, or rich diagnostic data. Most industrial routers in current production use Cat 4 as the cellular modem. The Teltonika RUT986, TRB246, and equivalent products from Robustel and Milesight are all Cat 4 devices.

NB-IoT and LTE-M – Role in SCADA is Limited

NB-IoT (Narrowband IoT) and LTE-M (also known as Cat-M1 or Cat-M) are 3GPP low-power wide area (LPWA) standards designed for devices that send small payloads infrequently and need multi-year battery life. They are well-suited to smart metering, parking sensors, environmental monitors, and asset tracking.

For SCADA backhaul, they are generally not appropriate. SCADA polling cycles are typically seconds to minutes, not hours. Protocol traffic includes control commands as well as telemetry – the communications must be bidirectional and reasonably responsive. NB-IoT’s latency (often several seconds for a round-trip) and its limited TCP/IP support make it unsuitable as a primary SCADA link. LTE-M is somewhat better – it supports full-duplex TCP/IP and is used in smart metering – but for a deployment where you are running Modbus polling or DNP3 unsolicited reporting over an IP connection, Cat 1 or Cat 4 is the right choice.

Where NB-IoT and LTE-M have a genuine role in the SCADA ecosystem is as the connectivity layer for individual sensors and meters that feed data into an edge gateway, which then handles the SCADA protocol and cellular backhaul upstream. In that architecture, NB-IoT collects data from dispersed low-power sensors; the gateway aggregates it and forwards over LTE.

Full 5G NR – Where It Makes Sense

Full 5G NR (New Radio) – specifically 5G Standalone (SA) architecture with network slicing and sub-10ms latency – is relevant for SCADA in a relatively narrow set of applications: real-time remote control of machinery, closed-loop automation with sub-50ms round-trip requirements, or high-density industrial environments where LTE cell capacity is a constraint. Private 5G campus networks in large manufacturing facilities or energy sites are a genuine use case, particularly where you need deterministic latency that a shared public network cannot guarantee.

For most field SCADA deployments – substations, pump stations, remote pipeline monitoring, renewable generation sites – full 5G NR is over-specified. The throughput is not needed, the cost premium is real, and public 5G SA coverage outside urban centres remains patchy in the UK as of 2026.

5G RedCap – The Emerging Sweet Spot

5G RedCap (Reduced Capability), formally called NR-Light and standardised in 3GPP Release 17, is designed precisely for the middle ground that SCADA occupies. It delivers up to 150 Mbps downlink and 50 Mbps uplink with sub-100ms latency – far beyond what SCADA needs in terms of raw throughput, but the key advantage is that it runs on a 5G Standalone core, which means access to network slicing, improved security architecture, and a technology lifecycle measured in decades rather than years.

RedCap modules cost significantly less than full 5G NR hardware, consume less power, and fit into smaller form factors – making them compatible with the kind of compact industrial gateway used in substations and control panels. For SCADA deployments being specified today for equipment that will be in service for 10 or 15 years, a RedCap-capable device future-proofs the connectivity layer against the eventual 4G sunset.

In the UK, EE and Vodafone are commercially live with RedCap on their 5G SA networks as of early 2026. Three and O2 (VMO2) are in active testing with commercial launches expected through 2026. Outside major urban centres, LTE fallback remains essential in any RedCap deployment – a requirement to design around, not an obstacle to consider RedCap at all. For more detail on UK RedCap status and hardware options, see 5gredcap.co.uk.

Cellular Technology Comparison for SCADA

The Protocol Layer: How SCADA Data Gets from Field Device to Cloud

Understanding the connectivity technology is only half the picture. SCADA systems use industrial communication protocols that are distinct from standard IT networking – and the cellular router sitting between the field device and the cloud must understand, or at minimum transport, these protocols correctly.

Modbus

Modbus is the most widely deployed serial protocol in industrial automation and has been in use since 1979. It exists in two main forms: Modbus RTU (binary serial, over RS232 or RS485) and Modbus TCP (the same register model carried over an IP network). An industrial router connecting a legacy RTU or energy meter over RS485 will typically receive Modbus RTU data and need to either forward it as-is, convert it to Modbus TCP for an IP-based SCADA platform, or translate it to MQTT for cloud forwarding. Modbus is the standard interface for inverters, energy meters, variable speed drives, and most basic RTUs. It is the starting point for almost every SCADA-over-cellular project in the energy sector.

DNP3

DNP3 (Distributed Network Protocol 3) was developed specifically for the utilities sector and is the dominant protocol in electricity distribution and water industry SCADA in the UK, US, and Australia. It supports unsolicited reporting (field devices can push data on change rather than waiting to be polled), timestamping of events at the point of occurrence, and data integrity checking – features that Modbus lacks. DNP3 runs natively over serial (RS232, RS485) and over TCP/IP. An industrial router supporting DNP3 over serial interfaces and forwarding it over cellular to a DNP3 master is a common architecture in substation and distribution automation. DNP3 Secure Authentication (SA), standardised in DNP3 v5, adds a challenge-response layer for protection against man-in-the-middle attacks.

IEC 60870-5-104

IEC 60870-5-104 is the TCP/IP adaptation of the IEC 60870-5-101 serial protocol. It is widely used in European electricity utility SCADA and performs a similar function to DNP3 in terms of supporting event-driven reporting, integrity interrogation, and time synchronisation. Where a deployment uses IEC 104, the router must transport the TCP sessions reliably – typically through a VPN tunnel to a private APN – without interfering with the protocol’s connection state.

OPC UA

OPC UA (Unified Architecture) is the modern, platform-independent industrial data exchange standard. Unlike Modbus and DNP3 – which are primarily polling or event protocols – OPC UA provides a full information model, service-oriented architecture, and built-in security (including PKI certificate-based authentication and message encryption). It is the standard interface for Industry 4.0 and IIoT platforms, and modern industrial routers that support OPC UA can act as OPC UA servers – exposing field data directly to OPC UA clients in a cloud platform or local HMI without requiring a separate protocol gateway.

MQTT

MQTT (Message Queuing Telemetry Transport) is not a SCADA protocol in the traditional sense – it is a lightweight publish-subscribe messaging protocol widely used for IoT cloud connectivity. Many cloud SCADA and IIoT platforms (Azure IoT Hub, AWS IoT Core, ThingsBoard, Ignition) accept data over MQTT. Industrial routers with data-to-server or I/O rule capabilities can read Modbus registers locally and publish them as MQTT topics to a cloud broker – effectively acting as a lightweight edge integration layer without requiring a full SCADA protocol stack at the cloud end.

DLMS/COSEM

DLMS (Device Language Message Specification) / COSEM (Companion Specification for Energy Metering) is the smart metering standard used in AMI (Advanced Metering Infrastructure) and AMR (Automatic Meter Reading) deployments. It is supported by certain industrial routers and gateways in the energy sector where meter data is being backhauled over cellular to a head-end system. DLMS/COSEM is specific to the metering domain; it is less commonly needed in general SCADA router deployments but appears in energy-focused hardware from Teltonika and others.

Teltonika Routers and Gateways for SCADA Deployments

Teltonika Networks produce a range of industrial cellular routers and gateways that are well-suited to SCADA connectivity. All run RutOS – a purpose-built industrial operating system based on OpenWRT – which provides native support for Modbus, DNP3, OPC UA, BACnet, and DLMS/COSEM without licence keys or additional software. Remote management across a fleet of devices is handled through Teltonika RMS (Remote Management System), which supports configuration, monitoring, firmware updates, and remote access from a central cloud dashboard.

Note that Teltonika’s product catalogue does not specifically label products by SCADA application – there is no SCADA filter on their website. The relevant selection criteria are the serial interfaces (RS232 and/or RS485), the industrial protocol support, the cellular category, and whether dual SIM failover is required. The products below cover the main use cases.

Other Industrial Cellular Routers for SCADA

While Teltonika is the most widely deployed industrial cellular router brand in the UK IoT and SCADA market, two other manufacturers are worth noting for specific deployment contexts: Robustel and Milesight. Neither currently has direct links from this site – the product details below are for reference.

Network Resilience for SCADA: What Happens When the Link Drops

A SCADA link serving a power substation, water pumping station, or gas compressor cannot simply go down. The communications architecture must account for link failure from the outset – not as an edge case, but as an expected operating condition.

Dual SIM Failover

The most common resilience mechanism in cellular SCADA is dual SIM: the router carries two SIM cards, potentially on different networks, and automatically switches to the backup SIM if the primary connection fails. Most industrial routers support this – the TRB246, RUT986, and their equivalents all include dual SIM with configurable failover criteria (signal quality, ping failure, data inactivity threshold). The failover time is typically configurable from seconds to minutes, depending on how quickly an alarm condition needs to propagate.

Multi-Network and Roaming SIMs

A multi-network roaming SIM can connect to multiple MNOs from a single SIM card, using network steering to maintain connectivity as signal conditions change. This is particularly valuable in remote or semi-rural locations where any single network’s 4G coverage may be marginal, and where deploying a dual-SIM device with two separate operator contracts adds overhead. A multi-network SIM effectively extends the coverage footprint without adding hardware complexity. roamingsim.co.uk and multinetworksim.com both offer multi-network IoT SIMs suitable for fixed SCADA deployments.

eSIM – Reducing Site Visits

eSIM (eUICC – embedded Universal Integrated Circuit Card) offers a meaningful operational advantage in SCADA deployments: the ability to remotely switch the cellular network profile on a deployed device without a physical SIM swap. For a substation with an installed router that needs to move to a different network – because coverage has changed, pricing has changed, or the original operator is sunsetting 2G/3G services – an eSIM allows that change to be made remotely via a profile download, eliminating the need to send an engineer to site. Given that SCADA deployments often involve hundreds of remote sites, the operational saving is significant.

eUICC for IoT is covered in depth at euicc.co.uk, including the SGP.02 (M2M) and SGP.32 (IoT) remote SIM provisioning specifications relevant to industrial deployments.

VPN and Private APN

SCADA traffic must be protected from the public internet. The standard approach is either a private APN (Access Point Name) – which keeps traffic on the operator’s private network and prevents it from traversing the public internet at all – or a VPN tunnel (IPsec, OpenVPN, or WireGuard) between the field router and the control centre or cloud endpoint. In practice, many deployments use both: a private APN for the base network isolation, plus an encrypted VPN tunnel for application-layer security and authentication. Industrial routers used in SCADA must support these VPN protocols natively – this is a non-negotiable requirement, not an optional feature.

Local Data Buffering

Where a cellular link fails and the connection cannot be immediately restored, the router should be capable of buffering outgoing data locally and retransmitting it once connectivity is re-established. The Teltonika RUT986 includes a Micro SD slot for precisely this purpose. For deployments with strict audit and reporting requirements – metered energy consumption, flow measurement, alarm history – data loss during a connectivity gap can have regulatory and contractual implications.

Antennas for SCADA Cellular Deployments

The supplied stub antennas on an industrial router are adequate for a bench test. They are not appropriate for a deployed SCADA installation. SCADA sites are, by their nature, frequently located in environments with compromised RF conditions: inside steel electrical cabinets, within concrete buildings, on the edge of rural coverage, or in electrically noisy substation environments. The antenna is the single component that most directly affects whether a cellular link is reliable or marginal.

Cabinet-Mounted External Antennas

For industrial cabinets and enclosures, a bulkhead-mount antenna with an SMA or N-type connector and a short run of low-loss coax to the router is the standard solution. The antenna is mounted on the outside of the cabinet, typically on the lid or side panel, where it has line-of-sight to the sky. This alone can make the difference between a marginal connection and full signal. For 4G LTE, MIMO 2×2 antennas covering the relevant UK bands (Band 20 at 800 MHz for rural coverage, Band 3 at 1800 MHz for urban density) are the baseline specification.

Mast and Pole-Mounted Antennas

Where an SCADA site is remote – a wind turbine base, a river gauging station, a pipeline compressor station in open countryside – a mast-mounted antenna with a longer coax run to the router inside the equipment shelter is the right approach. Directional panel antennas can be aimed at the nearest base station to maximise gain where omnidirectional coverage is insufficient. For 5G sites, 4×4 MIMO antennas covering the n78 (3500 MHz) band alongside the 4G bands are the current specification for forward-compatible installations.

Antenna Resources

For SCADA and industrial IoT antenna selection, mastlink.co.uk covers mast infrastructure and mounting hardware for cellular and RF installations. The IoT antenna directory at iotantenna.co.uk covers the antenna products themselves – panel, dome, omnidirectional, and vehicle-mount options for LTE and 5G deployments.

Bringing It Together: SCADA Over Cellular by Sector

The architecture is consistent across sectors – a field device communicating over a serial or Ethernet interface, an industrial cellular router converting and forwarding data over a 4G or 5G link, and a cloud or on-premise SCADA platform receiving and processing it. What varies is the protocol (DNP3 in electricity utilities, Modbus in building and energy monitoring, IEC 104 in European grid SCADA) and the resilience requirement (critical infrastructure needs dual SIM and private APN; an agricultural pump station needs a reliable connection but not the same uptime SLA).

For teams specifying cellular SCADA hardware today, the practical selection process is: choose the router with the serial interfaces your field devices need, verify it supports your target protocols natively, specify an appropriate external antenna for the installation environment, and use a private APN with VPN for security. If the deployment will be in service beyond 2030, consider whether the router’s cellular category (or the vendor’s eSIM support) gives you a reasonable upgrade path as UK networks evolve.

The Teltonika product range available from routerstore.com covers the full spectrum from compact serial-to-cellular gateways (TRB142, TRB246) through to full-featured industrial routers with every protocol and interface combination (RUT986) and 5G-capable units for forward-looking deployments (TRB501). All are backed by Teltonika RMS for remote management across any scale of deployment.