top of page





Enabling Interoperability with System-level Connectivity

Updated: Aug 15, 2021

Multiple AGV/AMR providers have already embraced the“ interoperability” value proposition. As a result, there are three interface categories being delivered:

  1. Open API and SDKs for robot OEM integration.

  2. The emerging standards dominated by VDA5050 and MassRobotics.

  3. OEM management software including: FLM, RCS, WMS, etc.

The mobile robot industry will benefit greatly from interoperability, making buying and integrating robots a straightforward process. Unfortunately, this is only one part of the problem. The actual challenges go beyond the entire system or entire plant including manufacturing and intralogistics equipment.

By creating a fourth category of interface, FARobot allows system integrators to add greater value to their projects, guaranteeing standard quality. This fourth category allows interoperability at the Agent level (which refers mostly to robots) as well as the Artifact level (which refers to factory and warehouse equipment).

Before trying to address the challenges from a system prospective, it is important to first understand the value of standard protocols. Standard protocols provide:

  1. Standard communication quality: adaptable to use cases peculiarity while guaranteeing resilience

  2. Predictable behavior: the system latency is known

  3. Fast debug: identifying issues is much faster and easier

  4. Lower project non-recurring engineering: the time spent integrating different devices diminishes greatly

  5. Inter-device integration: enable cross-brand, cross-devices communication

Standard protocols prove to be valuable tools for industrial-grade robotic solutions.

At FARobot, we develop our own protocol called Swarm Protocol. Check here to find out more about how to harmonize system interoperability with Swarm Protocol.


bottom of page