- Vendors are shipping LLM-based agents that read machine data and propose actions; the ones that work keep a human or a PLC between the model and the actuator.
- OPC UA PubSub over MQTT is becoming the default way to get factory data to the cloud without a custom gateway per machine.
- 2G and 3G sunsets continue country by country; fleets on old modems need a migration plan, not a hope.
- Digital twins are being rebuilt around event streams rather than CAD models, which makes them cheaper and more useful.
Agents on the floor, with guardrails
The demos were inevitable: an AI agent that reads OPC UA tags, notices a temperature trend, looks up the maintenance manual and suggests a fix. The deployments that have followed are more conservative, and rightly so. The pattern that is emerging keeps the large language model in an advisory loop: it can query data, draft work orders and explain anomalies, but writes to equipment go through the existing PLC logic and a human approval step. That is not a limitation of the models so much as a consequence of IEC 62443 zoning and plain engineering sense.
Why it matters: the value is in triage and documentation, not autonomy, at least for now. AI agents on the factory floor goes through the architecture and the failure modes.
OPC UA PubSub over MQTT
Classic OPC UA is client-server: a SCADA system polls a machine. The PubSub profile lets a machine publish its data model over MQTT to a broker, where cloud platforms, historians and analytics can subscribe without each one opening a session to the machine. Combined with the Sparkplug specification for topic and payload conventions, this is becoming the plain default for new factory-to-cloud connections, replacing the custom gateway per machine type that used to eat integration budgets.
Why it matters: it shifts the hard problem from connectivity to information modeling. If the machine publishes a well-formed OPC UA model, the cloud side gets semantics for free. The industrial IoT guide has more on where OPC UA, Modbus and PROFINET fit.
2G and 3G sunsets are a fleet problem
Operators keep retiring legacy networks to reuse spectrum for 4G and 5G, and the schedule varies by country and even by operator within a country. For consumer phones this is a footnote; for a fleet of meters, trackers or alarm panels with 2G modems installed a decade ago it is a hard deadline with a truck roll attached. The migration targets are LTE-M and NB-IoT, both designed to live for a long time on 4G and 5G cores, with 5G RedCap for devices that need more throughput.
Why it matters: the lesson for new designs is to budget for the radio’s lifetime, not just the device’s. Our cellular IoT entry and the connectivity overview cover the choices.
Digital twins, rebuilt around events
The first wave of digital twins started from 3D models and tried to attach data to them. The current wave starts from the data: an event stream per asset, a state model that updates from it, and visualization only where someone needs it. The twins are less impressive in a demo and far more useful in operations, because they answer “what is the state of pump 14 and what happened to it last Tuesday” without a rendering engine. See Digital twins explained.
Also worth your time
- The companies directory is open with the first profiles; listings are free in this phase.
- From the glossary: pilot purgatory, the place IoT projects go when nobody owns the business case.
Sources
Topics: AI agents, OPC UA, MQTT, network sunset, industrial IoT