<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>ISO 21423 &#8211; MachTech News</title>
	<atom:link href="https://machtechnews.com/tag/iso-21423/feed/" rel="self" type="application/rss+xml" />
	<link>https://machtechnews.com</link>
	<description>Machinery and Industrial Technology News Hub</description>
	<lastBuildDate>Tue, 17 Nov 2026 13:44:50 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	

<image>
	<url>https://machtechnews.com/files/2025/11/favicon.png</url>
	<title>ISO 21423 &#8211; MachTech News</title>
	<link>https://machtechnews.com</link>
	<width>32</width>
	<height>32</height>
</image> 
	<item>
		<title>ISO 21423: The New Standard for Industrial Robot Interoperability</title>
		<link>https://machtechnews.com/iso-21423/</link>
					<comments>https://machtechnews.com/iso-21423/#respond</comments>
		
		<dc:creator><![CDATA[Editorial Staff]]></dc:creator>
		<pubDate>Tue, 17 Nov 2026 13:25:41 +0000</pubDate>
				<category><![CDATA[Technology & Machinery]]></category>
		<category><![CDATA[AI in Industry]]></category>
		<category><![CDATA[Future of Manufacturing]]></category>
		<category><![CDATA[industrial automation]]></category>
		<category><![CDATA[ISO 21423]]></category>
		<category><![CDATA[Smart Manufacturing]]></category>
		<guid isPermaLink="false">https://machtechnews.com/?p=4482</guid>

					<description><![CDATA[<p>Industrial mobile robots are becoming a familiar part of modern factories and warehouses. But when machines from different manufacturers need to share&#8230;</p>
<p>The post <a rel="nofollow" href="https://machtechnews.com/iso-21423/">ISO 21423: The New Standard for Industrial Robot Interoperability</a> appeared first on <a rel="nofollow" href="https://machtechnews.com">MachTech News</a>.</p>
]]></description>
										<content:encoded><![CDATA[
<p class="wp-block-paragraph"><em>Industrial mobile robots are becoming a familiar part of modern factories and warehouses. But when machines from different manufacturers need to share the same workspace, communication can become a major obstacle. ISO 21423 aims to establish a common framework for making that interaction more predictable.</em></p>



<div class="wp-block-rank-math-toc-block" id="rank-math-toc"><h2>In This Article</h2><nav><ul><li><a href="#why-industrial-robot-interoperability-has-become-a-problem">Why Industrial Robot Interoperability Has Become a Problem</a></li><li><a href="#what-iso-21423-actually-standardizes">What ISO 21423 Actually Standardizes</a></li><li><a href="#a-shared-coordinate-system-for-different-robot-fleets">A Shared Coordinate System for Different Robot Fleets</a></li><li><a href="#how-robots-share-identity-capabilities-and-status">How Robots Share Identity, Capabilities and Status</a></li><li><a href="#mqtt-and-json-the-communication-foundation">MQTT and JSON: The Communication Foundation</a></li><li><a href="#the-relationship-with-mass-robotics-and-vda-5050">The Relationship with MassRobotics and VDA 5050</a></li><li><a href="#what-iso-21423-does-not-solve">What ISO 21423 Does Not Solve</a></li><li><a href="#what-the-new-standard-could-mean-for-manufacturers">What the New Standard Could Mean for Manufacturers</a></li></ul></nav></div>



<p class="wp-block-paragraph">A factory can operate <a href="/the-rise-of-autonomous-mobile-robots-trend-or-future-tool/">autonomous mobile robots</a> (AMRs) from several manufacturers and still struggle to coordinate them efficiently. One fleet may be controlled by its own software, another by a different platform, while production systems, automated doors, lifts and other equipment operate through separate interfaces.</p>



<p class="wp-block-paragraph">The problem is not necessarily a lack of automation. It is the difficulty of making independently developed systems exchange information in a consistent way.</p>



<p class="wp-block-paragraph"><a href="https://www.iso.org" target="_blank" rel="noreferrer noopener">Published on 14 October 2026, <strong>ISO 21423:2026</strong></a> addresses this challenge. Officially titled <em>Robotics — Industrial mobile robots — Communications and interoperability</em>, the international standard defines communication requirements for industrial mobile robots, their fleet management systems and other equipment or applications operating in a shared industrial environment.</p>



<p class="wp-block-paragraph">Its importance lies in a shift in <a href="/how-robotics-is-transforming-industrial-automation-in-2025/">how industrial automation</a> can be designed: instead of treating every robot fleet as a separate technical environment, manufacturers and system integrators gain a common framework for exchanging operational information.</p>



<h2 class="wp-block-heading">Why Industrial Robot Interoperability Has Become a Problem</h2>



<p class="wp-block-paragraph">Industrial mobile robots are used to transport materials, move components between production stages, supply assembly lines and support warehouse operations. As deployments expand, manufacturers increasingly need robots with different capabilities to work within the same facility.</p>



<p class="wp-block-paragraph">A single supplier may provide an effective solution for pallet transport, while another offers robots better suited to smaller loads or more flexible movement. Replacing one complete fleet with a single manufacturer&#8217;s products is not always economically or technically practical.</p>



<p class="wp-block-paragraph">However, integrating different systems can require custom software, separate communication interfaces and additional coordination logic. A robot may know its own position and task, but that information is not necessarily available in a format that another fleet manager can understand.</p>



<p class="wp-block-paragraph">This creates practical limitations. Systems may have difficulty sharing location data, identifying available robots, understanding operating states or coordinating requests. Integrators then have to build and maintain connections between platforms that were not originally designed to communicate.</p>



<p class="wp-block-paragraph">The result can be higher integration costs, greater dependence on individual suppliers and more complicated expansion when a facility introduces additional equipment.</p>



<p class="wp-block-paragraph">ISO 21423 is intended to address the communication layer behind this problem.</p>



<h2 class="wp-block-heading">What ISO 21423 Actually Standardizes</h2>



<figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
<iframe title="Robotics Standards Update: AMR Interoperability, Humanoid Safety &amp; What&amp;apos;s Next | Automate Rewind" width="1170" height="658" src="https://www.youtube.com/embed/8CZps-YiNFY?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
</div></figure>



<p class="wp-block-paragraph">The standard defines communication requirements between two or more of three main groups:</p>



<ul class="wp-block-list">
<li>Industrial Mobile Robots (IMRs)</li>



<li>Industrial Mobile Robot Fleet Managers (IMRFMs)</li>



<li>Other machines, equipment and applications in the shared industrial environment</li>
</ul>



<p class="wp-block-paragraph">The third group is particularly important. The standard&#8217;s scope is not limited to communication between robots. It also includes systems such as ERP applications, machines served by mobile robots, automated doors, lifts and alarm systems.</p>



<p class="wp-block-paragraph">In practical terms, this means a robot fleet can exchange relevant information not only with other robots but also with parts of the facility infrastructure and the software responsible for production or resource management.</p>



<p class="wp-block-paragraph">ISO 21423 establishes a common structure for identifying devices, describing their capabilities, reporting location and operating status, and exchanging requests.</p>



<p class="wp-block-paragraph">It does not require every manufacturer to build identical robots or use the same internal control software. Instead, it provides a defined communication framework through which different systems can exchange information.</p>



<p class="wp-block-paragraph">That distinction is central to the standard&#8217;s purpose: interoperability does not mean technological uniformity.</p>



<h2 class="wp-block-heading">A Shared Coordinate System for Different Robot Fleets</h2>



<p class="wp-block-paragraph">One of the most practical challenges in a multi-vendor environment is location.</p>



<p class="wp-block-paragraph">Different robot manufacturers may use their own maps, reference points and coordinate systems. Even when two robots operate in the same building, their software may describe the same physical position differently.</p>



<p class="wp-block-paragraph">ISO 21423 addresses this through a Common Coordinate System (CCS).</p>



<p class="wp-block-paragraph">Robot fleets operating in the same physical space are required to use a shared coordinate system. The standard specifies at least three reference points to establish it, with measurements expressed in metres. These points allow individual maps to be related to a common reference.</p>



<p class="wp-block-paragraph">The purpose is straightforward: different systems need a consistent way to interpret where a robot is located.</p>



<p class="wp-block-paragraph">This information can support location visualisation, traffic management and coordination between fleet management platforms. It can also help surrounding equipment understand the position of a robot within the facility.</p>



<p class="wp-block-paragraph">The requirement does not mean that every robot must abandon its own navigation map. Instead, local maps need to be related to the common reference system so that location information can be exchanged consistently.</p>



<p class="wp-block-paragraph">This is an important technical foundation for multi-vendor operation, although it does not solve navigation itself.</p>



<h2 class="wp-block-heading">How Robots Share Identity, Capabilities and Status</h2>



<p class="wp-block-paragraph">Knowing where a robot is located is only part of the communication problem. Other systems also need to understand what the robot is, what it can do and what condition it is currently in.</p>



<p class="wp-block-paragraph">ISO 21423 defines structured information for robot identity and capabilities. This includes details such as manufacturer, model, software versions, unique identification, physical dimensions and supported capabilities.</p>



<p class="wp-block-paragraph">The standard also addresses operational information. Robots can report their location, operating mode and current states. Depending on the information supported by the system, this can include movement-related data, battery status and trajectory information.</p>



<p class="wp-block-paragraph">For a fleet manager, these details provide a more consistent picture of the robots operating in the facility.</p>



<p class="wp-block-paragraph">Consider a production environment where several robots serve different workstations. A fleet management system needs to know which units are available, which are moving, which are waiting for an external event and which require intervention. Without consistent status information, coordination becomes more difficult.</p>



<p class="wp-block-paragraph">The standard also defines request messages. These allow one system to request an action from another, with responses reporting changes in the request&#8217;s status. The specified examples include requests to move, pause, resume or cancel a robot&#8217;s activity.</p>



<p class="wp-block-paragraph">This creates a structured way for systems to communicate operational intentions rather than relying entirely on separate, manufacturer-specific integrations.</p>



<h2 class="wp-block-heading">MQTT and JSON: The Communication Foundation</h2>



<p class="wp-block-paragraph">ISO 21423 uses established communication technologies rather than introducing an entirely new networking ecosystem.</p>



<p class="wp-block-paragraph">Messages are exchanged using MQTT, while JSON provides the message format and data structure. The standard references the relevant ISO/IEC specifications for these technologies and defines the required message structures in its annexes.</p>



<p class="wp-block-paragraph">MQTT is widely used in connected systems because it supports message exchange through a publish-and-subscribe model. Systems can publish information to defined topics, while other authorised participants subscribe to the information relevant to them.</p>



<p class="wp-block-paragraph">JSON provides a structured representation of the data being exchanged. This makes it possible for different software platforms to interpret messages according to a common schema.</p>



<p class="wp-block-paragraph">For manufacturers and integrators, using established technologies can reduce the need to develop proprietary communication mechanisms from scratch. However, using MQTT and JSON alone does not guarantee interoperability. Systems must still implement the same data definitions, message structures, identifiers and communication behaviour.</p>



<p class="wp-block-paragraph">The standard also points to cybersecurity and authentication best practices, including those associated with IEC 62443 and ISO/IEC 27001. This is important because connecting more devices and systems also expands the industrial communication environment that must be protected.</p>



<h2 class="wp-block-heading">The Relationship with MassRobotics and VDA 5050</h2>



<figure class="wp-block-embed is-type-video is-provider-youtube wp-block-embed-youtube wp-embed-aspect-16-9 wp-has-aspect-ratio"><div class="wp-block-embed__wrapper">
<iframe title="VDA 5050 v3.0 Explained (15 min): Key Changes for Mobile Robots &amp; Fleet Control" width="1170" height="658" src="https://www.youtube.com/embed/SLUcnva1lRs?feature=oembed" frameborder="0" allow="accelerometer; autoplay; clipboard-write; encrypted-media; gyroscope; picture-in-picture; web-share" referrerpolicy="strict-origin-when-cross-origin" allowfullscreen></iframe>
</div></figure>



<p class="wp-block-paragraph">ISO 21423 did not emerge in isolation. Its development builds on earlier efforts to improve communication between mobile robots from different manufacturers.</p>



<p class="wp-block-paragraph">One important foundation is the MassRobotics Interoperability Standard, developed through an industry working group involving robot manufacturers, technology developers and end users. The initiative began in 2020 to address the practical difficulties of operating mixed robot fleets.</p>



<p class="wp-block-paragraph">The work also draws on experience from VDA 5050, a communication interface developed in Germany by the German Association of the Automotive Industry (VDA) and the VDMA Materials Handling and Intralogistics Association.</p>



<p class="wp-block-paragraph">VDA 5050 has provided a framework for connecting mobile robots to a common fleet control system. Its version 3.0, released in April 2026, further addresses the integration of freely navigating mobile robots.</p>



<p class="wp-block-paragraph">These initiatives share a broad objective: reducing the need for isolated, manufacturer-specific communication arrangements.</p>



<p class="wp-block-paragraph">However, ISO 21423 should not be treated as simply another name for VDA 5050 or as an automatic replacement for existing interfaces. They are distinct specifications with their own scope and implementation details. Their relationship is relevant because both contribute to the wider effort to make industrial mobile robot systems more interoperable.</p>



<p class="wp-block-paragraph">The publication of ISO 21423 gives this effort an international standard that can support wider alignment across markets and industries.</p>



<h2 class="wp-block-heading">What ISO 21423 Does Not Solve</h2>



<p class="wp-block-paragraph">The scope of the standard is important because it defines both its value and its limitations.</p>



<p class="wp-block-paragraph">ISO 21423 is a communication and interoperability standard. It is not a safety standard and does not establish safety requirements for industrial mobile robots. Navigation requirements are also explicitly excluded.</p>



<p class="wp-block-paragraph">This means that a common communication framework does not automatically make robots safe to operate together. Collision avoidance, risk assessment, emergency stopping, protective systems and the safe separation of people and machines remain separate engineering responsibilities.</p>



<p class="wp-block-paragraph">Nor does the standard guarantee that every existing robot can become interoperable through a simple software update.</p>



<p class="wp-block-paragraph">Manufacturers still need to implement the required communication structures. Fleet management systems must support the relevant information and requests. Facilities may also need to align maps, reference points, network infrastructure, cybersecurity controls and operational procedures.</p>



<p class="wp-block-paragraph">Legacy equipment can present additional challenges, particularly when it lacks suitable interfaces or the ability to expose the required data.</p>



<p class="wp-block-paragraph">For companies planning an implementation, the practical question is therefore not simply whether a supplier supports ISO 21423. They also need to understand which functions are implemented, which systems can communicate and what integration work remains necessary.</p>



<h2 class="wp-block-heading">What the New Standard Could Mean for Manufacturers</h2>



<p class="wp-block-paragraph">The long-term significance of ISO 21423 will depend on adoption by robot manufacturers, fleet management software providers and system integrators.</p>



<p class="wp-block-paragraph">If implementation becomes widespread, manufacturers could gain more flexibility when selecting mobile robots for different tasks. They may be able to introduce specialised equipment without rebuilding the entire fleet management environment around a single supplier.</p>



<p class="wp-block-paragraph">System integrators could also benefit from a more consistent communication foundation. Instead of repeatedly solving the same basic interoperability problems, they may be able to focus more of their work on facility-specific requirements, production workflows and operational optimisation.</p>



<p class="wp-block-paragraph">For industrial users, the potential benefits include easier fleet expansion, more flexible supplier selection and better coordination between mobile robots and surrounding systems.</p>



<p class="wp-block-paragraph">These outcomes are not guaranteed by publication alone. They will depend on how consistently the standard is implemented and how well vendors support real-world integration.</p>



<p class="wp-block-paragraph">The broader direction, however, is clear. As factories introduce more autonomous equipment, the ability of individual machines to operate independently will no longer be enough. Their value will increasingly depend on how effectively they communicate with the rest of the production environment.</p>



<p class="wp-block-paragraph">ISO 21423 provides a common framework for addressing that challenge. Its success will not be measured by the number of documents published or systems claiming compliance, but by whether manufacturers can build mixed industrial robot environments that work reliably without requiring a separate integration project for every new machine.</p>
<p>The post <a rel="nofollow" href="https://machtechnews.com/iso-21423/">ISO 21423: The New Standard for Industrial Robot Interoperability</a> appeared first on <a rel="nofollow" href="https://machtechnews.com">MachTech News</a>.</p>
]]></content:encoded>
					
					<wfw:commentRss>https://machtechnews.com/iso-21423/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
