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.
Self-healing, redundant field-device networks
Field-level networks that automatically detect a failed link or node and reroute traffic without engineering intervention, extending mesh-networking concepts to wired Ethernet-APL segments.
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
Industrial Ethernet already has several ways to survive a fault. Ring protocols reconfigure around a broken link within a defined recovery time, and parallel-redundancy schemes send every frame over two independent paths so that a single failure causes no interruption at all. These protect the backbone and the links between switches.
The weak point in a field network is the last segment. In a trunk-and-spur layout each instrument has one spur, and field switches may share one trunk. Self-healing concepts aim to extend redundancy and automatic rerouting down to that level, with software that monitors link quality, predicts degradation and reroutes before a failure.
Why it matters
Would bring the resilience of wireless mesh instrumentation to wired, high-bandwidth field networks, reducing unplanned loop outages from cabling faults.
Where it fits
Today the practical measures are careful topology design: field switches connected in a ring, redundant power, and critical measurements split across different switches. Fully automatic healing at device density is a research and early-pilot subject. It becomes more important as more functions, including control and eventually safety, share the same Ethernet infrastructure in the field.
Why we place it at the Emerging Idea stage
Ring and redundant-star topologies are established practice; fully autonomous, software-defined healing at field-device density is still a research-to-pilot topic. Estimated time to the Proven in Use stage: 5–10 yrs. What the stages mean.
Key risk
Deterministic control traffic and self-healing re-routing have competing latency requirements that are not yet fully reconciled in field-bus-class networks.
Questions to ask before committing
- What is the consequence of losing one field switch, and are redundant measurements deliberately placed on different switches?
- What recovery time does your control application tolerate, and does the chosen redundancy method meet it?
- Does network monitoring report degrading links before they fail, and does anyone receive those reports?
Standards and terms to know
- MRP
- Media Redundancy Protocol, a ring-redundancy method defined in IEC 62439-2.
- PRP and HSR
- Parallel-redundancy methods in IEC 62439-3 that give zero switchover time.
- Recovery time
- How long communication is interrupted while the network reconfigures after a fault.
Related technologies
See this entry on the full maturity map · All Control Devices 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.