Industries / Industrial equipment and services / IoT and industrial automation / SCADA integration
Remote sites and telemetry
This is the equipment at unattended sites, chiefly the remote terminal unit (RTU), a rugged computer that reads instruments and works switches and valves, and the phone, radio, cellular or satellite links and message rules that connect it to a control room.
5
Milestones achieved, from 1943 to 2000.
2
To watch for: announced, not yet confirmed outside.
2
Open deliverables. Nobody has shipped them.
The road
AchievedWatch forOpen
Achieved
1943
Control by microwave radio
Westinghouse's Visicode supervisory control, which from 1929 needed only one pair of telephone wires, ran from 1935 over power-line carrier, signals sent along the high-voltage line itself, and by 1943 over a microwave radio link between the Cos Cob and Darien stations of the New York, New Haven and Hartford Railroad. Even so, the magazine noted in 1949 that most supervisory control still ran over telephone wires, leased or privately owned.
Credit
Westinghouse Electric
1950s
Staffed stations go remote
Before the Second World War nearly all of Los Angeles's distributing stations had an operator on duty around the clock, and into the early 1950s the city employed more than 1,000 station and power house operators. Its stations were converted to supervisory control from the early 1950s, the last in the 1980s, and all are now run through RTUs from the Energy Control Center, the Water and Power Associates history records.
Credit
Los Angeles Department of Water and Power
1993
An open protocol for RTUs
DNP3 is a protocol, a set of rules for messages, that lets a master station in the control room poll RTUs and substation devices and receive their reports. It was developed by Harris's Distributed Automation Products unit, and in November 1993 ownership of the specification passed to the DNP Users Group, made up of utilities and vendors. It spread from electric utilities to water, transport and oil and gas, and became IEEE Std 1815 in 2010.
Credit
Harris, Distributed Automation Products; DNP Users Group
1999
Messages sized for satellites
Andy Stanford-Clark of IBM and Arlen Nipper of Arcom wrote MQTT in 1999 to connect oil pipelines over satellite while using as little battery and bandwidth as possible. In MQTT, devices publish readings to a broker, a server that passes each message to whoever has asked for it. OASIS, a standards body, ratified version 3.1.1 as an open standard in November 2014, and its release says oil and gas companies use MQTT "to monitor thousands of miles of oil pipelines."
Credit
Andy Stanford-Clark (IBM); Arlen Nipper (Arcom)
2000
Telecontrol moves to TCP/IP
IEC 60870-5-101, published in 1995, set how a control centre and its outstations exchange telecontrol messages over circuits connected directly to each site. Its companion IEC 60870-5-104, first published in December 2000, carries the same messages over TCP/IP, the protocols of the internet, so that shared data networks can stand in for private lines. The standard states: "Security mechanisms are outside the scope of this standard."
LessonA protocol written for private circuits brings no protection of its own when it moves onto shared networks.
Credit
IEC Technical Committee 57
Watch for
Cellular IoT from satellites
Under 3GPP's Release 17, standard NB-IoT radios (narrowband IoT, a low-power cellular standard) can reach satellites directly. Myriota said its HyperPulse service would be generally available from 15 December 2025 in the US, Mexico, Brazil, Australia and Saudi Arabia, with oil and gas monitoring customers already connected. Over more than six months of measurements on the Skylo and Tiantong networks, which use satellites in geostationary orbit, Xiong Wang and colleagues found such service "remains in the initial stage," with much time and energy spent each time a device connects.
Achieved whenan operator outside the satellite companies publishes months of delivery rates and delays from remote sites that use such links for SCADA.
Claimed by
Myriota, December 2025
A DNP3 profile for solar
IEEE 1815.2-2025, announced on 5 February 2026 by the MESA Standards Alliance and the DNP Users Group, sets how utilities use DNP3 to monitor and command distributed energy resources (DER), such as solar, battery storage and other inverter-based power plants. Its backers say broad adoption will let utilities talk to many makers' DER equipment in the same way and lower the cost of connecting it.
Achieved whena utility reports plants whose equipment has been tested to IEEE 1815.2 connected to its SCADA and working.
Claimed by
MESA Standards Alliance and DNP Users Group, February 2026
Open
01
SCADA traffic over satellite IoT
A side-by-side field test at one remote site that sends the same SCADA traffic, regular readings and exception reports in both DNP3 and MQTT, over satellite NB-IoT, ground-based NB-IoT or LTE-M, and LoRaWAN for 90 days, logging every message's delivery, delay and energy use.
The briefCredit · unclaimed02
Why the RTU went quiet
An open tool that watches DNP3 and IEC 60870-5-104 traffic at the control room end and, when data from a remote site stops or turns bad, says whether the fault lies in the link, the RTU or the master station, and shows the evidence.
The briefCredit · unclaimed
Open 01 · the brief
SCADA traffic over satellite IoT
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
A side-by-side field test at one remote site that sends the same SCADA traffic, regular readings and exception reports in both DNP3 and MQTT, over satellite NB-IoT, ground-based NB-IoT or LTE-M, and LoRaWAN for 90 days, logging every message's delivery, delay and energy use.
Why it is still open
Published measurements of standard satellite IoT use general traffic, not SCADA protocols. Dominic Richter's 2026 thesis found that on a geostationary NB-IoT satellite link, TCP, which DNP3 and MQTT normally run on, "generated 147% protocol overhead and experienced frequent timeouts," while CoAP over UDP lost no packets, and that each satellite transmission took more than 10 times the power of a ground-network one.
Built with what exists
A satellite IoT development kit such as Myriota's HyperPulse Developer Kit, or the commercial NB-IoT satellite modems Richter used on Skylo's network; LTE-M modules; a LoRaWAN gateway with The Things Stack, an open-source network server; Eclipse Mosquitto, an open-source MQTT broker; Step Function I/O's open-source dnp3 library; a DC power logger.
First step
From one rooftop, send a reading every 15 minutes in MQTT over one satellite kit and one LTE-M module for a week, and compare the two logs.
Done looks like
90 days of logs from one site, published with the share of messages delivered, the median and 95th-percentile delay and the energy per message for each link and protocol, plus the timeout and keep-alive settings that made each one work.
Open 02 · the brief
Why the RTU went quiet
The first to publish is credited on this line, and the deliverable moves from Open to Achieved.
What to build
An open tool that watches DNP3 and IEC 60870-5-104 traffic at the control room end and, when data from a remote site stops or turns bad, says whether the fault lies in the link, the RTU or the master station, and shows the evidence.
Why it is still open
NERC found that 68 of the 203 grid control centre outages it processed for 2018 to 2020 "did not yield a root cause," and gave the example of bad data from one RTU that stopped a key calculation, after which inspection of the RTU found no defect. industrial-aiops-energy, an open server released in July 2026 that lets AI agents read DNP3 and IEC 104 points, publishes no test of such diagnoses, and searches of GitHub and arXiv found none.
Built with what exists
Wireshark, which decodes both protocols; Step Function I/O's dnp3 library and MZ Automation's lib60870 to simulate outstations and a master on a bench; a cellular or radio link that can be degraded on purpose; a small language model to write each explanation, such as one of Liquid AI's LFM3 models tuned on one graphics chip (see the Note "One GPU to fine-tune").
First step
Record a week of DNP3 traffic between a simulated outstation and master over a cellular modem, unplug the antenna at logged times, and see what the capture shows.
Done looks like
On a bench of five outstations and three link types, 100 faults induced in random order (cut link, noisy radio, RTU restart, wrong setting, master timeout), with the tool naming the right cause for at least 90 and the fault list and captures published.