Representative End User Clients
Representative Automation Clients
Representative Software Clients
The industrial edge is rarely a flat network. Field devices often sit behind gateways, switches, remote I/O, and other communications infrastructure. Each additional layer can make device discovery, configuration, and lifecycle management more difficult—particularly when plants combine multiple protocols, vendors, and generations of installed equipment.
FieldComm Group’s latest Field Device Integration (FDI) specification release addresses that problem with a standardized approach to nested communications. FDI is a standardized technology for integrating intelligent field devices into host systems such as DCS platforms, engineering tools, asset management systems, and maintenance applications. FDI provides a standardized method for integrating field devices into these host systems, allowing engineering, configuration, diagnostics, and lifecycle management functions to be handled consistently across multiple device suppliers.
The update defines how an FDI Host Application, or FDI Server, can reach end devices through intermediate networking infrastructure. For suppliers, it creates a common way to represent gateways and related communications devices in FDI. For users, it points toward more consistent engineering and maintenance workflows across mixed-topology architectures.
The release introduces two new specifications and updates the broader specification set:
FCG_TS62769-6-300: FDI Technology Mapping for Gateway Plugins.
FCG_TS62769-9: FDI Gateway Devices.
FCG_TS62769-4: Updates to FDI Packages, together with changes in other parts of the specification, support nested communications and modular device architectures.
Why Nested Communications Matter
FDI combines device information, user-interface content, and business logic in a standardized package that host systems can consume. That model is most valuable when it can follow a device through the real network path—not only when a device is directly visible to the host. By defining gateway devices and gateway plugins, the new specifications extend the FDI model into architectures where an intermediate device provides access to downstream assets.
This is an important step for brownfield environments. Plants frequently rely on remote I/O, protocol gateways, and network segments that reflect years of expansion. A standard representation for those layers can reduce the need for host-specific or vendor-specific integration and give application developers a clearer mechanism for navigating to an end device.
ARC Advisory Group Recommendations
Host and tool suppliers should review the complete specification set, not only the two new gateway documents, because supporting changes extend into FDI Packages and other parts of the architecture.
Gateway, switch, and remote I/O suppliers should identify candidate products for early implementation and interoperability testing.
Device suppliers should test how existing and future FDI Packages behave when devices are accessed through nested communications paths.
End users should add nested-device access and multi-vendor interoperability to FDI evaluation criteria, especially for brownfield modernization projects.
All stakeholders should validate the corrected two-byte FDI_TECHNOLOGY_VERSION field while maintaining the defined value of 0x0104.
The latest FDI specifications move the standard closer to the way industrial networks are actually built. By standardizing how hosts reach devices through gateways and other intermediate infrastructure, FieldComm Group is addressing a persistent integration challenge at the field level. The value will depend on supplier adoption and interoperability testing, but the direction is clear: device integration must account for the full communications path if it is to scale across complex, mixed-topology plants.
ARC is currently completing Supplier Positioning MarketMaps on both Ethernet-APL and the underlying Single Pair Ethernet (SPE) technologies. Find out more by contacting the author at [email protected].