The Energy Grid Is Becoming a Distributed IoT Network

The power grid used to be simple by comparison to what it is today. A handful of large generation assets fed power in one direction through a distribution network to end users. Monitoring and control happened at fixed substations with wired SCADA connections. The data flows were predictable and the network topology was stable.

That model is breaking down. Energy generation is now distributed across thousands of sites – solar arrays on commercial rooftops, wind installations in remote fields, battery storage units at industrial premises, EV chargepoints in car parks and forecourts. Each of these assets is a connected device. Each one generates operational data, requires remote monitoring, and in many cases participates actively in grid balancing through demand response or vehicle-to-grid (V2G) capabilities.

The challenge this creates is not primarily a technology challenge – it is a connectivity challenge. How do you maintain reliable, secure, manageable data links to thousands of distributed assets, many of them in locations where fixed network infrastructure was never installed and never will be? How do you operate a control loop across those assets with confidence that the connection will not drop at a critical moment?

Cellular connectivity is the answer the industry has converged on – and for good reason. It is available at virtually every location where energy assets are deployed. It scales without civil engineering. It can be made resilient with dual-SIM hardware. And it can be secured with private APN architecture that keeps operational data off the public internet entirely.

Why WiFi Is Not the Answer for Energy Deployments

The obvious question is why energy asset operators do not simply use the WiFi or fixed broadband at the installation site. The answer is that building critical infrastructure on top of a connectivity layer you do not control is a risk that the failure consequences do not justify.

A solar inverter connected to the site’s broadband goes offline whenever the broadband goes offline – for any reason, including the site owner changing their ISP, the router getting power cycled, or the WiFi password being changed. A BESS system managing grid export and import decisions cannot afford to lose its connection because a facility manager at the host site did something routine. The connectivity for the energy asset needs to be independent of the site’s consumer internet, managed by the asset operator, and subject to the asset operator’s SLAs – not the site owner’s ISP.

Cellular connectivity on a dedicated IoT SIM, with a private APN where required, provides exactly that independence. The connection is owned and managed by the energy asset operator. It is unaffected by anything happening on the site’s consumer network. It can be monitored centrally, managed remotely, and made resilient with a second SIM on a different network operator.

Battery Energy Storage Systems: The Connectivity Requirements Are Demanding

BESS deployments illustrate the connectivity requirements of modern energy assets more clearly than any other application. A battery storage system is not a passive device that reports data periodically. It is an active participant in energy markets and grid balancing – receiving dispatch instructions, responding to frequency events, managing charge and discharge cycles in response to energy prices, and in grid-connected applications communicating with SCADA systems running DNP3 or IEC 61850 protocols over TCP.

The connectivity requirements for a BESS deployment include:

• Continuous uptime – a BESS that loses connectivity during a dispatch event cannot respond. In frequency response applications, response times are measured in seconds. Connectivity gaps are operational failures with potential financial and contractual consequences.
• Low latency – SCADA control loops and frequency response applications require low-latency data paths. Cellular on LTE provides round-trip latency in the 30-80ms range – adequate for the majority of energy SCADA applications.
• Dual-SIM resilience – a single cellular connection on a single network operator is a single point of failure. BESS deployments warrant dual-SIM routers with SIMs from two independent network operators, configured for automatic failover with no traffic interruption.
• Private APN with fixed IP – SCADA communications over cellular should run through a private APN, keeping control traffic off the public internet. Fixed IP addressing allows firewall rules to permit only known-good traffic between the BESS controller and the SCADA head-end, with everything else blocked by default.
• Out-of-band management – the router managing the BESS connection needs to be remotely manageable via a separate channel. If the primary data connection has a problem, the management path cannot depend on that same connection.

A cellular router with dual independent modems – such as the Teltonika RUTM52, which runs two SIMs simultaneously on separate networks – combined with multi-network IoT SIM cards on a private APN is the standard architecture for this application. Add MWAN3 load balancing and the connection remains intact through a single MNO outage without the BESS losing communications. For the SCADA layer specifically, the connectivity and remote access architecture is covered in detail on IoTPortal’s SCADA remote access guide.

Solar and Wind: Remote Assets in Poor Network Locations

Solar farms and wind installations share a characteristic that makes fixed connectivity impractical: they are deliberately sited in locations chosen for solar irradiance or wind resource, not for proximity to network infrastructure. A solar array in an open field or a wind turbine on an exposed hillside is unlikely to have fibre or even decent fixed broadband available. Cellular is not a compromise here – it is the only practical connectivity option.

The monitoring and management requirements for renewable generation assets include:

• Inverter performance monitoring – real-time generation data, fault codes, and performance metrics from each inverter string
• Weather and environmental monitoring – irradiance, wind speed, temperature, and soiling measurement to benchmark actual against expected generation
• Remote diagnostics and firmware updates – the ability to access and update inverter and monitoring system firmware without a site visit
• Grid connection compliance – export limiting and curtailment commands from the DNO, which require a reliable, low-latency control path
• Energy trading and balancing – for assets participating in balancing mechanism or flexibility markets, dispatch instructions must arrive reliably and on time

A cellular gateway at each generation site – connected via 4G LTE with a fallback to a second network – handles all of these data flows over a single managed connection. The gateway provides the LAN interface for inverters and monitoring equipment on-site, and the WAN path to the asset management platform and SCADA head-end in the cloud or on-premise.

EV Chargepoints: Cellular at Consumer Scale

EV chargepoint networks have a connectivity problem that is structurally different from BESS or generation assets: they are deployed at consumer premises where the operator has no control over the host site’s network, in very large numbers, and often in locations – car parks, forecourts, on-street – where fixed network infrastructure is absent or impractical to use.

OCPP (Open Charge Point Protocol) – the standard communication protocol for EV chargepoints – runs over WebSocket connections to a central management system. Every chargepoint needs a persistent connection to authorise charging sessions, process payments, receive configuration updates, and participate in smart charging and load management schemes. Cellular is the connectivity technology that makes this viable at scale without depending on host site infrastructure.

The specific challenges in EV chargepoint cellular connectivity include:

• High device density – a large car park might have 50 to 100 chargepoints, each needing an independent connection or sharing a local network through a single cellular gateway. The architecture decision – one SIM per chargepoint vs shared cellular gateway per site – affects cost, management complexity, and resilience differently at different scales.
• Payment transaction security – chargepoints that process card payments are in scope for PCI-DSS. The cellular connectivity layer needs to meet the security requirements that come with that: private APN, no shared infrastructure with non-PCI devices, encrypted management access.
• Smart charging and V2G – demand response and vehicle-to-grid applications require the chargepoint to receive and act on dispatch instructions in near-real-time. Connectivity latency and reliability matter more here than in a basic charge-and-go scenario.

Smart Meters and Grid-Edge Devices: The Low-Power End

At the other end of the energy connectivity spectrum from BESS are the low-power, periodic-reporting devices: smart meters, grid-edge sensors, transformer monitors, and distribution substation instruments. These devices report infrequently – every 15 to 30 minutes in many smart metering applications – transmit small data payloads, and run on constrained power budgets.

NB-IoT and LTE-M are the cellular technologies designed for this application. Both are narrowband standards optimised for low power consumption, extended coverage in challenging radio environments, and support for large numbers of devices per cell. NB-IoT is the dominant technology for UK smart metering deployments. LTE-M offers slightly higher bandwidth and supports voice, making it appropriate for applications that need periodic but slightly more data-intensive reporting.

For fleet-scale smart meter deployments looking ahead, eSIM and the SGP.32 standard represent a significant operational improvement: the ability to switch network operator profiles over the air across millions of meters, without physical SIM replacement, using a constrained-network-friendly protocol. The SGP.32 eSIM guide at IoTSIMs covers how the standard works and what it means for large-scale cellular IoT deployments including smart metering.

Cybersecurity for Connected Energy Assets

Energy infrastructure is a high-value target for cyberattacks. IBM’s research consistently places the energy sector among the most targeted industries for cybersecurity incidents – around 24% of all attacks in recent years. A BESS system, a solar inverter, or an EV chargepoint connected to the internet without appropriate security controls is an entry point into operational technology that can have physical consequences.

The cellular connectivity layer provides several security advantages over fixed internet connections when correctly configured:

• Private APN – operational technology traffic on a private APN is not publicly routable. Devices are invisible to internet scanning tools like Shodan. There is no public internet attack surface to exploit.
• Fixed IP with allowlist firewall rules – with fixed IP SIM cards, firewall rules can permit only traffic between known device IP addresses and known platform endpoints. Everything else is blocked at the network level before it reaches the device.
• VPN for management access – remote access to device management interfaces must go through an encrypted VPN tunnel, not over a public internet management interface. WireGuard and OpenVPN are both well-supported on industrial cellular routers.
• Firmware update capability – energy assets have long deployment lifetimes. The hardware you install today needs to be maintainable throughout a 10 to 15 year asset life, which means firmware update capability via remote management is a procurement requirement, not a nice-to-have.

What to Specify When Procuring Cellular Connectivity for Energy Assets

Procurement decisions made at the design stage determine the security, resilience, and manageability of the deployment for its entire operational life. These are the questions to resolve before specifying the hardware and connectivity.

Single-site or fleet deployment?

A single BESS unit at one site has different management requirements from a 50-site solar portfolio. Fleet deployments warrant investment in centralised remote management platforms, zero-touch provisioning, and a connectivity management portal that provides per-SIM visibility across the estate. Single-site deployments can be managed more simply but still benefit from the same security architecture.

What protocols does the SCADA or asset management system use?

DNP3, IEC 61850, Modbus TCP, and MQTT each have different latency and reliability requirements. DNP3 over TCP for frequency response applications has tighter latency requirements than Modbus TCP for periodic data logging. Understanding the protocol requirements determines the acceptable latency budget for the cellular link and the appropriate failover architecture.

Does the application require private APN?

For any application involving SCADA communications, grid control, or payment transactions, the answer is almost always yes. Public internet connectivity for operational technology is an unnecessary risk. The cost difference between public and private APN SIM connectivity is small relative to the security and operational benefits.

What is the consequence of a connectivity gap?

A solar monitoring system that loses connectivity for 30 minutes loses 30 minutes of generation data – inconvenient but not critical. A BESS dispatched for frequency response that loses connectivity during an event may be in breach of its grid services contract. The connectivity uptime requirement should be derived from the operational consequence of failure, not from a generic “good enough” assessment.