# A $373 ISO standard lets mobile robots from different vendors share a floor

By MarketScale Newsroom · Published 2026-11-03 · Industrial IoT on MarketScale
Canonical: https://www.marketscale.com/industries/industrial-iot/a-373-iso-standard-lets-mobile-robots-from-different-vendors-share-a-floor

> A3 published ISO 21423:2026, a cross-vendor communication standard for industrial mobile robots that also reaches lifts, doors, alarms and ERP tools.

## Key points

- A $373 document now gives a plant buyer something specific to ask for when a forklift from one vendor and a floor-cleaning robot from another have to share an aisle.
- Sites that already run MassRobotics or VDA 5050 interfaces start close to the new standard, since ISO 21423 was built from both and uses the same MQTT and JSON foundations.
- Robots calling a lift or passing an automated door fall inside the standard's scope, so the owners of building systems and ERP have a seat in robot buying decisions.

A3's own picture of the problem is a pretty ordinary one: autonomous forklifts from one vendor share a floor with floor-cleaning robots from another, and the two can't talk to each other or coordinate. The Association for Advancing Automation (A3) has published ISO 21423:2026, a new international standard that sets out how industrial mobile robots (IMRs) communicate and work together, no matter which vendor built them or which model they are. When machines from different suppliers run inside the same industrial facility, the standard gives them one shared set of communication requirements.

ISO Technical Committee 299 developed the standard through its robotics Working Group 10 (WG 10). It spells out the way IMRs, IMR fleet managers and other equipment pass information to one another and ask each other for actions. Under it, robots can share their location, speed, direction, condition, tasking and availability.

## Why shared position data matters on the floor

A3's announcement, issued November 2, 2026, describes the benefit for end users in operational terms. Robots should get in each other's way less often, whether on the floor or in their path planning, and that raises robot availability and the efficiency of the whole system. Location, speed and direction are the inputs a robot would need to work out who yields at a crossing aisle. Without them, each fleet plans its routes as if the other weren't there.

Aaron Prather, writing in his Six Degrees of Robotics newsletter, described what that looks like today. Mixed systems frequently stumble when they encounter one another, he wrote, creating costly bottlenecks and forcing humans to intervene, because robots without interoperability can't negotiate right-of-way or coordinate routes. That framing suggests the cost shows up less as a dramatic failure and more as idle robots and staff pulled off other work to clear a jam.

A3 sells the document through its online store for $373. For a plant or distribution center running robots from more than one supplier, the standard's main value could be that it gives the buyer something specific to ask for when a forklift from one vendor and a floor-cleaning robot from another have to share an aisle.

Block Field

## The lift, the door and the ERP system

The standard covers more than robots talking to robots. According to A3's announcement, distributed by Business Wire, ISO 21423 also covers communication with machines that robots tend, enterprise resource planning tools, and building systems such as lifts, automated doors and alarms. Workers carrying mobile devices can also exchange comparable data, which allows their tasks to be coordinated with the robots around them.

That scope suggests ISO 21423 will be more than a robot vendor's checkbox. Where robots need to call a lift, pass through an automated door or respond to an alarm, those handoffs fall within the standard. The people who own the lift controller, the door system and the ERP instance therefore have a reason to join the robot conversation early rather than after deployment.

It's also a different kind of document for A3. The group says ISO 21423 is the first non-safety robot standard it has helped produce. That suggests a shift in focus toward a different question: whether a mixed fleet can get work done together.

Prather draws the comparison directly, likening the effort to ISO 10218 for robot safety, which he says gained global traction because it balanced regulatory rigor with industry pragmatism. The benchmark is a useful one. It suggests ISO 21423's success will depend on the same thing: whether vendors and users find it practical enough to build into products, not just cite.

## Built from MassRobotics and VDA 5050

According to A3, ISO 21423 wasn't written from scratch. It builds on two existing frameworks, the MassRobotics Interoperability Standard and VDA 5050, which A3 says gives developers familiarity while extending functionality to broader use cases. Prather notes that the MassRobotics standard has already been piloted in North America, while VDA 5050 is widely adopted in Europe.

Members of VDMA, the German engineering association, were instrumental in keeping the approaches congruent, A3 said. The working group settled on MQTT and JSON, two widely adopted technologies, as the technical foundation, which A3 said lowers the barrier to adoption and links existing implementations to the ISO framework. In practice, that suggests a vendor already running either framework faces a shorter path to ISO 21423 than one starting cold.

A3 notes that because ISO 21423 is an ISO standard, it can be adopted in countries all around the world. For a manufacturer running facilities in several countries, one common reference could matter more than any single new feature.

The drafting reflected that reach. In a September 2025 editorial, A3 said almost 90 participants had contributed to the working group, from countries including France, the United States, India, England, Germany, Denmark, Japan, Korea, Singapore, China, Canada, Sweden, Norway, Turkey and Spain. Pulling the North American and European frameworks into one document, with that many national perspectives in the room, is what gives the global-adoption claim some weight.

Block Field

A3 framed the choice as one of fit rather than rivalry. Industry standards are always evolving, it wrote, there is usually no single answer for every case, and different customer needs may call for different approaches. Together, the two standards expand the options open to operators, integrators, software platform providers and manufacturers.

That architectural flexibility is the practical difference for buyers. A site built around one central fleet manager already fits the VDA 5050 model. A site where several vendors' fleet managers and robots have to work side by side, without one system in charge, is the case ISO 21423 was written to cover. The editorial doesn't spell out how distributed coordination works at the message level. Engineering teams will need the full document for that.

## End users asked for this

In the announcement, Carole Franklin, A3's director of standards development for robotics, said leading industrial users of mobile robots have wanted an interoperability standard for years. She said it should help companies expand automation with equipment from several vendors and get more out of the robots they already own. According to Franklin, ISO 21423 gives both manufacturers and users shared ground for fleets to communicate with one another, wherever their facility sits in the world.

> Companies want to choose the robots that fit their applications and have those robots work together on the same floor., Carole Franklin, director of standards development, robotics, A3

General Motors has been part of that demand since the start. Steven DuMont, GM's advanced automation development manager, said in A3's editorial that the company has backed the effort from the beginning. He said GM runs industrial mobile robots from multiple brands at sites worldwide, and as an end user it looks forward to a global standard that helps solve the interoperability problem.

According to A3, the working group brings together end users, robot manufacturers, software platforms, system integrators and academics. Prather's newsletter names Procter & Gamble alongside GM among the end users at the table.

That mix matters for how the document reads. When the companies that buy robots help write the rules, the standard is more likely to address the problems they actually run into on the floor, such as robots blocking each other's routes, than to formalize one vendor's preferred interface.

## Where the standard changes less

Mixed fleets can already work together. Florian Pestoni, founder of robot orchestration platform InOrbit.AI, said in A3's editorial that cross-vendor operation is possible today, but fragmentation still adds too much friction; he expects the standard to help accelerate scaled robot deployments. Add A3's own view that VDA 5050 and ISO 21423 are complementary, and the case for change is weakest at a centrally controlled site already running VDA 5050 with a settled vendor list. The case is strongest where a team wants to add a new robot brand without another round of custom integration.

Growth tilts that balance. Citing the International Federation of Robotics, Prather notes that mobile robot installations are among the fastest-growing segments of automation, especially in logistics and intralogistics, and argues that the cost of fragmentation rises as fleets expand. An operator planning to double a fleet over the next few buying cycles would feel that friction far more than one holding steady.

Block Field

A3 expects a common protocol to increase competition and support innovation among robot suppliers. That only happens once vendors implement it. The clearest sign the standard has made it from the store onto the plant floor will be ISO 21423 conformance listed on robot and fleet-manager spec sheets, next to payload and battery life.

## Sources

- [New ISO Standard Enables Interoperability for Mobile Robots](https://www.designnews.com/automation/new-iso-standard-enables-interoperability-for-mobile-robots) (Design News)
- [New ISO Interoperability Standard Helps Mobile Robots from Different ...](https://finance.yahoo.com/technology/ai/articles/iso-interoperability-standard-helps-mobile-142000420.html)
- [Editorials: ISO 21423 Standard for Mobile Robot Interoperability](https://www.automate.org/robotics/editorials/iso-21423-building-global-consensus-for-mobile-robot-interoperability)
- [Inside ISO 21423 and the Future of Interoperability](https://sixdegreesofrobotics.substack.com/p/when-robots-speak-the-same-language)

Tags: ISO 21423, Association for Advancing Automation, industrial mobile robots, autonomous mobile robots, robot interoperability, VDA 5050, MassRobotics, warehouse automation, manufacturing operations, procurement, fleet management, industrial standards

---
Source: MarketScale, https://www.marketscale.com/industries/industrial-iot/a-373-iso-standard-lets-mobile-robots-from-different-vendors-share-a-floor. Published for AI indexing and citation; cite the canonical URL. Site guide for agents: https://www.marketscale.com/llms.txt