Inferensys

Glossary

OPC UA FX

OPC UA FX (Field eXchange) is an extension of the OPC UA PubSub model that standardizes deterministic, controller-to-controller communication at the field level for high-speed industrial automation.
ML engineer managing model versions on laptop, version history visible, technical Git-like workflow.
Field-Level Communication

What is OPC UA FX?

OPC UA FX (Field eXchange) is an extension of the OPC UA PubSub model that standardizes deterministic, controller-to-controller and controller-to-device communication at the field level for high-speed industrial automation.

OPC UA FX extends the OPC UA PubSub framework to the factory floor by enabling real-time, horizontal communication between controllers and field devices. It leverages Time-Sensitive Networking (TSN) to guarantee bounded low latency and jitter, replacing traditional hardwired and vendor-specific fieldbuses with a converged, Ethernet-based network. This allows standard and deterministic traffic to coexist on a single physical infrastructure.

The specification defines an information model for describing device capabilities and a connection management model for configuring end-to-end data flows. By standardizing the semantics for data exchange at the field level, OPC UA FX enables true controller-to-controller (C2C) and controller-to-device (C2D) interoperability, facilitating plug-and-produce automation where devices from different vendors can be seamlessly integrated without proprietary gateways.

FIELD-LEVEL COMMUNICATION

Key Features of OPC UA FX

OPC UA FX (Field eXchange) extends the OPC UA framework to the field level, standardizing controller-to-controller and controller-to-device communication with deterministic data exchange for high-speed automation.

01

Deterministic Real-Time Communication

OPC UA FX guarantees bounded low latency and jitter for time-critical automation tasks by leveraging Time-Sensitive Networking (TSN). This enables hard real-time control loops where data must arrive within microseconds. Key characteristics include:

  • Isochronous data exchange synchronized to a global network clock
  • Traffic scheduling to prevent collisions and ensure deterministic delivery
  • Sub-microsecond synchronization across all devices on the network
  • Converged network support where real-time and best-effort traffic coexist on a single wire
< 10 µs
Cycle Time
< 1 µs
Jitter
02

Controller-to-Controller (C2C) Communication

FX standardizes horizontal communication between PLCs and controllers without requiring a central coordinator. Using the PubSub over TSN transport profile, controllers publish DataSet messages directly onto the network, which are consumed by subscribing controllers. This replaces proprietary fieldbus protocols with an open, multi-vendor solution. Benefits include:

  • Decoupled architecture where publishers and subscribers operate independently
  • Peer-to-peer data sharing without routing through a supervisory system
  • Hot redundancy through seamless failover between redundant controllers
  • Simplified engineering with standardized connection configuration
03

Connection Manager (CM)

The Connection Manager is a centralized software component that automates the configuration of TSN streams and PubSub connections across the network. It translates application-level communication requirements into network-level Quality of Service (QoS) parameters. The CM handles:

  • Stream reservation and path computation through the TSN network
  • Talker and Listener endpoint configuration on each participating device
  • Dynamic reconfiguration when devices join, leave, or fail
  • Enforcement of security policies for data integrity and device authentication
04

OPC UA FX Information Model

FX defines a formal Companion Specification that extends the OPC UA Address Space with types for field-level communication. This includes standardized ObjectTypes and VariableTypes for:

  • ConnectionEndpoint objects representing the FX capabilities of a device
  • DataSet definitions describing the structure and semantics of published data
  • PubSub configuration exposed as addressable Nodes for online monitoring
  • Diagnostic and status variables for network health and stream quality This semantic model enables offline engineering tools to discover and configure FX-capable devices automatically.
05

Multi-Protocol Convergence

OPC UA FX is designed to coexist with and ultimately converge existing industrial Ethernet protocols. By mapping legacy fieldbus data models into the OPC UA Information Model, FX provides a unified semantic layer. Key convergence aspects:

  • Gateway-less translation between PROFINET, EtherNet/IP, and OPC UA FX
  • Shared TSN infrastructure where multiple protocols run on the same wire
  • Unified diagnostics across heterogeneous device fleets
  • Migration path from brownfield installations to fully converged FX networks
06

Safety and Security Integration

FX incorporates functional safety and cybersecurity as first-class architectural principles. OPC UA Safety defines a protocol layer for transmitting safety-related data over the same FX network, while the OPC UA Security Policy framework ensures:

  • End-to-end encryption and message signing for all published DataSets
  • X.509 certificate-based authentication for every device on the network
  • Role-Based Access Control (RBAC) to restrict which controllers can subscribe to specific data
  • Safety integrity levels up to SIL 3 for functional safety communication
OPC UA FX EXPLAINED

Frequently Asked Questions

Clear, technically precise answers to the most common questions about OPC UA Field eXchange (FX) and its role in deterministic, controller-to-controller industrial communication.

OPC UA FX (Field eXchange) is an extension of the OPC UA PubSub model that standardizes deterministic, controller-to-controller (C2C) communication at the field level for high-speed industrial automation. It works by combining the OPC UA PubSub information model with Time-Sensitive Networking (TSN) at the data link layer to guarantee bounded low latency and jitter. Unlike traditional OPC UA Client-Server connections, FX uses a publisher-subscriber pattern where a Publisher multicasts a DataSet containing multiple field-level variables (e.g., sensor values, actuator commands) directly onto the network. Subscribing controllers filter and consume only the data they need, eliminating the overhead of point-to-point connections. The core mechanism relies on a Connection Manager that configures and monitors these data flows, defining the exact timing, content, and quality-of-service parameters for each exchange. This allows a single network frame to replace dozens of hardwired signals, enabling true software-defined networking on the factory floor.

Prasad Kumkar

About the author

Prasad Kumkar

CEO & MD, Inference Systems

Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.

His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.