Hello readers!

This week, we’re talking about getting mobile robots from rival vendors to share a floor, what it will take to scale IoT eSIM, designing alerts for equipment nobody watches, and more!

Your forklift and your floor scrubber are about to start talking

Interoperability at the Edge: How to Build a Modular Process Control System

A warehouse that buys its first autonomous forklift is also choosing its second, third and tenth robot. Each vendor’s machines report to that vendor’s fleet manager, so bringing in a different brand, say a floor scrubber or a tugger, has meant paying for another custom integration or running a second fleet that plans its routes as if the first weren’t there. That lock has shaped how plants buy mobile robots for a decade, and it is starting to loosen. The rules for how robots describe themselves to each other are moving out of individual products and into a document a buyer can name in a purchase order. Once that happens, a mobile robot looks more like any other device on the facility network, and decisions about how it behaves at a crossing aisle or a lift door start to belong to the people who run the building as much as to the people who sold the robot.

On November 2, the Association for Advancing Automation published ISO 21423:2026, an international standard for how industrial mobile robots, fleet managers and other equipment exchange information and request actions, whatever the brand. Robots that follow it share their location, speed, direction, condition, tasking and availability, which is the information a machine needs to work out who yields where two routes cross. It builds on the MassRobotics Interoperability Standard, piloted in North America, and VDA 5050, widely used in Europe, and it runs on MQTT and JSON. Buyers pushed for it: General Motors, which runs mobile robots from several brands at sites worldwide, backed the effort from the start, and Procter & Gamble is among the other end users at the table. Aaron Prather, who writes the Six Degrees of Robotics newsletter, describes the status quo bluntly: mixed fleets stall when they meet, create bottlenecks and pull people off other work to clear them.

Process control hit the same wall around 2018, when ExxonMobil’s control engineers worked in a world where every device was proprietary, and Steve Bitar, then an R&D program manager there, recalled that changing anything meant migrating the entire control system. PICMG’s account of the fix lists two requirements: a connector everyone agrees on, and shared data models that define what each component reports. For mobile robots the connection is already a wireless network, so ISO 21423 supplies the other half, a common vocabulary. A vocabulary only pays off once vendors build it into their products. A3 calls this the first non-safety robot standard it has helped produce, and Prather compares it to ISO 10218, the robot safety standard that spread because manufacturers found it practical to follow. Florian Pestoni of InOrbit.AI points out that cross-vendor fleets already run today, with too much custom work holding them back. The clearest sign of adoption will be ISO 21423 conformance listed on spec sheets beside payload and runtime.

ISO 21423 also covers the machines robots tend, ERP systems, and building equipment such as lifts, automated doors and alarms, and it lets workers carrying mobile devices exchange the same kind of data. That pulls a new set of owners into robot projects: whoever manages the elevator controller, the door system and the warehouse software. Vimaan, writing about warehouse automation, found that integration with existing workflows is the most commonly underestimated risk in these projects, and that systems split across several vendors tend to break where the pieces meet. A shared protocol closes one of those gaps and leaves the network underneath it alone. Horizon Powered notes that Wi-Fi roaming between access points is uneven, and a dropout that would barely register on a laptop leaves a data gap for a moving robot. Location and speed updates only help two fleets negotiate an aisle if they arrive while the robots are still approaching it.

If you run mobile robots from more than one supplier, or expect to, start by asking each robot and fleet-manager vendor whether they support ISO 21423 and when, and put that question in your next RFQ rather than after installation. Sites already running VDA 5050 or the MassRobotics standard start closest, since the new standard is built from both. A site with a single central fleet manager and a settled vendor list has less to gain than one planning to add brands. Bring the owners of lifts, doors, alarms and the WMS or ERP into robot planning early, because those handoffs now sit inside the standard’s scope. Walk the robots’ routes with a coverage survey before blaming any protocol for stalls, since message standards assume the messages arrive. And give your engineers the full document: the published summaries don’t spell out how coordination works at the message level, and those details will decide whether two fleets share an aisle or wait for someone to clear it.

📖 Top Articles

Always-On IoT: Bridging Terrestrial and GEO Satellite Connectivity for Seamless Global Tracking

Rapid changes in IoT technology, regulations and business models make the connectivity landscape increasingly complex. A managed service provider can help enterprises navigate deployments and keep assets visible from first mile to last. But even the best terrestrial network has limits. Hybrid connectivity addresses these limitations by extending terrestrial coverage with satellite coverage, helping maintain connectivity in areas beyond the reach of terrestrial networks.

SGP.32 Adoption: What It Will Take to Scale IoT eSIM

The mobile industry has stopped asking whether IoT eSIM will arrive and is now working out how to run it in the field. Mid-year eSIM connection snapshot data released in October 2026 by the Trusted Connectivity Alliance (TCA) revealed a fivefold increase globally in the number of eSIM Subscription Manager platforms that enable profile downloads in accordance with SGP.32.

The Alert Nobody Answered: Designing IoT Monitoring for Equipment Nobody Watches

Most remote monitoring projects are judged on the sensor and the dashboard. Was the reading accurate? Does the chart look good? Those questions matter, but they are rarely where a deployment succeeds or fails. The projects that disappoint usually fail later, at 2 a.m., when an alert fires and nothing happens.

🔥 Rapid Fire

🎙 The IoT For All Podcast

In this episode of the IoT For All Podcast, Alper Yegin, CEO of the LoRa Alliance, joins Ryan Chacon to discuss the state of LoRaWAN in 2026. The conversation covers what's driving LoRaWAN adoption, how LoRaWAN compares to other connectivity options, new LoRaWAN capabilities, LoRaWAN deployments in smart buildings and other verticals, moving from a pilot to large-scale deployment, misconceptions about LoRaWAN, the role of LoRaWAN in physical AI, and the future of LoRaWAN.

📚 Ebooks & White Papers

Kigen white paper: Sovereign Grid Connectivity in the Age of Edge AI

Explore how eSIM remote management helps DSOs control connectivity, protect long-life assets and unlock edge AI for smarter utilities.