exOS 允许创建 由自动化运行时和 Linux 两部分组成的混合自动化组件 。在每一方，组件都能以其平台原生形式代表整个功能。这意味着，IEC 功能块可以是 IEC 程序员与 Linux 软件的接口，反之亦然，C++ 类可以是 Linux 程序员与 "运动和 I/O 控制器 "的接口。
该接口独立于各进程之间的通信数据模型。
exOS 数据通信机制为运行在相同或不同设备和平台上的软件模块提供进程间通信。它遵循发布者/订阅者原则，允许多个监听者同时接收一组发送的数据。
通过 exOS 通信应用程序接口发送的数据都有缓冲区，因此可以保证（在预先配置的缓冲区范围内）送达。这使得它们不受底层系统实时行为的影响。
为了参与 exOS 数据通信，系统需要运行一个名为 数据集消息路由器的本地代理 。数据集信息路由器负责与参与的应用程序之间的信息路由。
exOS allows the creation of Hybrid Automation Components that consist of both Automation Runtime and Linux parts. On each side, the component may represent the whole functionality in its platform-native form. That means that e.g. an IEC function block may be the interface of an IEC programmer to a software which is running on Linux, or - vice-versa - a C++ class may be the interface for a Linux programmer towards a "motion and I/O controller".
This interface is independent of the communication datamodel between the respective processes.
The exOS data communication mechanism provides inter-process communication between software modules running on the same or on different devices and platforms. It follows the publisher/subscriber principle which allows to have multiple listeners receiving a set of sent data at the same time.
Data sent via the exOS communication API are buffered and therefore guaranteed to be delivered (within the range of the preconfigured buffers). This makes them independent of the real-time behaviour of the underlying system.
In order for a system to participate in the exOS data communication, it needs to run a local broker called the Dataset Message Router. The Dataset Message Routers are responsible for information routing with and among the participating applications.