Two-wire, intrinsically-safe Ethernet that runs all the way to the transmitter — finally bringing native Ethernet, and the bandwidth it carries, into hazardous-area field instrumentation.
TSN + OPC UA FX deterministic Ethernet control
Time-Sensitive Networking standards combined with OPC UA FX give standard Ethernet the deterministic, low-jitter behaviour that motion and safety control traffic requires.
Short entry. This page summarises our current placement. Full, sourced analyses are published first for the technologies closest to practical use; see the list of full analyses.
How it works
Time-Sensitive Networking is a set of IEEE 802.1 Ethernet standards that add guaranteed timing to ordinary switched Ethernet. All devices share a precise common clock, switches open scheduled time windows for critical traffic, and a long low-priority frame can be interrupted to let an urgent one through. Other standards in the set provide seamless redundancy.
OPC UA FX, for Field eXchange, extends OPC UA from the supervisory level down to the field. It defines how controllers exchange real-time data with each other and with field devices using a common information model, with safety and motion extensions, and can use TSN underneath for determinism. The intent is one vendor-neutral communication stack from sensor to cloud.
Why it matters
Converges what used to be separate control, safety and monitoring networks onto one deterministic Ethernet fabric, cutting cabling and switch infrastructure.
Where it fits
The first use is controller-to-controller communication between equipment from different suppliers, a long-standing integration problem on packaged units and production lines. Convergence of control, motion, safety, video and IT traffic on one network follows. A joint IEC and IEEE profile for industrial automation exists so that TSN products from different vendors make compatible choices.
Why we place it at the Reality Check stage
After years of promotion, the industrial TSN profile (IEC/IEEE 60802) was only published in June 2026, and the OPC UA FX specifications released so far cover controller-to-controller exchange; controller-to-device profiles are still being written. Multi-vendor demonstrations run, but production use in process plants is rare. Estimated time to the Proven in Use stage: 5–10 yrs. What the stages mean.
Key risk
Full benefit requires a TSN-capable device at every node in the loop — a mixed legacy/TSN network gets partial, not full, determinism.
Questions to ask before committing
- Which TSN features does each product actually implement, and do they follow the industrial automation profile?
- Has interoperability between your specific controllers been demonstrated, or only conformance of each one separately?
- Who will engineer and maintain the network schedule, and with which tools?
Standards and terms to know
- IEEE 802.1AS
- The TSN standard for time synchronisation across the network.
- IEEE 802.1Qbv
- The time-aware shaper that reserves transmission windows for scheduled traffic.
- IEC/IEEE 60802
- The TSN profile for industrial automation.
Related technologies
See this entry on the full maturity map · All Control Systems entries · How placements are made. Stage and time-horizon placements are editorial judgements based on public information as of October 2026, not engineering, safety or investment advice; see the Terms of Use.