EtherNet/IP + FDI = Value in Process Automation
Smitha Rao
Co-founder, Director
Utthunga Technologies Pvt. Ltd.

Chatrapathi G V
Senior Software Architect
Utthunga Technologies Pvt. Ltd.

Yashaswini T
Senior Software Engineer
Utthunga Technologies Pvt. Ltd.

Presented at the ODVA2018 Industry Conference & 18th Annual Meeting
October 10, 2018
Stone Mountain, Georgia, USA

2018 ODVA Industry Conference

1©2018 ODVA, Inc.

1. Abstract
As per the NAMUR's position paper on "An Ethernet communication system for the process industry",
NAMUR calls for protocols IEC 61784-2 CPF2/2 ‘EtherNet/IP‘ and IEC 61784-2 CPF3/5 ‘PROFINET IO CC
B‘ to become minimum binding requirements for the process industry. NAMUR also recommends FDI
device packages required for Field Device Integration (FDI) shall be available in the devices and capableof being transmitted to central tools. Hence EtherNet/IP protocol and FDI Device Integration standard isgoing to play vital role in the Process Automation Industries in the near future.
OPC UA is an interoperability standard for secure and reliable information exchange widely adopted in
the industrial automation. FieldComm Group has collaborated with OPC Foundation to create the FDI
Information Model which provides the harmonized protocol agnostic data to the enterprise layer.
EtherNet/IP device supporting FDI technology can be made available via FDI Information model tomanufacturing execution systems (MES), and enterprise applications such as Enterprise Resource
Planning (ERP) and Supply Chain Management (SCM).
This paper describes research and prototype done by Utthunga on supporting the EtherNet/IP protocol
in Device Integration Standard FDI and how it benefits EtherNet/IP device suppliers, Automation host
suppliers as well as ODVA and FieldComm Group community in achieving their objective towards
providing optimized solution in Process Industries.

2. Keywords
OPI - Optimization of Process Integration (OPI™)ICS - Industrial Control System
PAM - Plant Asset Management
EDS - Electronic Data Sheet
FDI - Field Device Integration
FDT/DTM - Field Device Tool/Device Type Manager
GPE - Generic Protocol Extension
PSD - Protocol Specific Definition
OPC UA - OPC Unified Architecture
EDD - Electronic Device Description
DCS - Distributed Control System
ECT - EDDL Cooperation TeamUIP - User Interface Plug-in
CIP - Common Industrial Protocol

2018 ODVA Industry Conference

2©2018 ODVA, Inc.

3. Overview of ODVA’s initiative in OPIWith its strong installation base and user experience in Hybrid and Discrete Industry, ODVA vision to
proliferate adoption of EtherNet/IP in the process industries with its new initiative OPI(Optimization ofProcess Integration) which defines a strategic vision for manufacturers looking to maintain costeffective, sustainable production capacity in the process industries. The approach will simplify exchangeof configuration, diagnostic and production data between field devices and higher-level systems such as
supervisory control and data acquisition systems (SCADA), plant asset management (PAM). Secure
remote access of field installation will be enabled and plant to enterprise communication simplified.
ODVA envisions an approach to the optimization of process integration that is convergent, compatible,
scalable, and open for users and their suppliers.

Image Source: Optimization of Process Integration - ODVA

Above image shows ODVA's technical approach to OPI's Unified Communication Solution based on
EtherNet/IP and CIP.

2018 ODVA Industry Conference

3©2018 ODVA, Inc.

ODVA has identified 3 primary use cases for OPI
1. Field Device to ICS Integration
This use case is the foundation of OPI. It envisions the integration of all existing installed process
Fieldbus into EtherNet/IP system and communication improvements like enhanced diagnostics andinstrumentation data on Industrial EtherNet. It also includes physical layer options such as Power over-Ethernet and confirming to the emerging standards for intrinsically safe.
2. Field Device to PAM Integration
This use case is the accelerant for OPI. It envisions that in all stages of field device life cycle fromcommissioning and operation to calibration and maintenance, it provides optimal performance
which is very crucial for the Process Automation Industries where installations are expected tooperate for long periods without shutdown.
3. Holistic field-to-Enterprise Communication ArchitectureThis use case is the integrator for OPI. It envisions with a single, converged and transparent
enterprise-wide communication architecture which can provide full access between the automationand enterprise resource planning that allows virtually unlimited access to data anywhere, any time.
OPI will allow users to update and improve the performance and serviceability of field installations
as well the integration of process applications with the overall enterprise in a safe and securemanner.

4. Role of FDI in ODVA’s initiative
One of the primary 3 use cases of OPI is Field Device to PAM Integration which envisions thesimplifying the exchange of configuration, diagnostic and process data between field devices andhigher level systems that must be standardized, usable across all systems, and independent ofdevice suppliers, system suppliers, or vendor-specific tools.

5. Existing Device Integration Standard
5.1 EDDL (Electronic Device Description Language)
EDDL is an international, IEC-61804 standard for Device Integration. Since 1992, EDDL is the mostwidely used Device Integration Standard in Process Industries. EDDL is used in the Intelligent Device
Management (IDM) software part of major process control systems and in portable maintenancetool to support device diagnostics, configuration, calibration, and access to internal variables of thedevice. EDDL is descriptive language and Operating System independent. EDDL can be supported invarious platforms like Linux, Windows, Android etc. EDDL files are imported, not installed hence itdoes not affect the runtime stability of the DCS system. However, EDDL influences the presentationin the host system and has limitation in representing the complex device functionalities.
Supported Communication Protocols
HART, Wireless HART, PROFIBUS, PROFINET, Foundation Fieldbus, ISA100 Wireless.

2018 ODVA Industry Conference

4©2018 ODVA, Inc.

Content of the EDDLAs shown in the above image, EDDL file basically includes the definition for Device Identification
 Data Description
 User Interface Description
 Communication Description
 Method Description
Device Identification: Every DD file is identified using Device Identification information and it
contains MANUFACTURER Code, Device Type Code, Device Revision and DD revision
Sample device identification information in the EDD for temperature device from ABB is shown
below

Data Description: Data definition describes how the data can be accessed by EDD applications fromthe device using EDDL constructs like VARIABLE, ARRAY, BLOCK, LIST etc.
VARIABLE construct is the principle mechanism for modeling the data items found in the device.
Sample VARIABLE construct for temperature unit along with condition based enumeration list is
shown below. Below VARIABLE definition shows that, Temperature unit ‘degC’ is not available whensensor type value (trans_sensor_type) is ‘LINEAR’.

2018 ODVA Industry Conference

5©2018 ODVA, Inc.

User Interface Description: EDD applications can be characterized as either PC application or ahandheld application. Menus, Graphs, & Charts are the few of the item types widely used in User
Interface.
Sample Menu definition with various styles is shown below. Based on the style definition in the
MENU EDDL construct, User Interface differs.

2018 ODVA Industry Conference

6©2018 ODVA, Inc.

CHART construct is used to graphically display the dynamic variables. CHART TYPE could be Gauge,
Horizontal Bar, Vertical Bar, Sweep and Strip and is shown below.

2018 ODVA Industry Conference

7©2018 ODVA, Inc.

COMMUNICATION DESCRIPTION: Communication definition is protocol dependent and is defined using
various attributes within COMMAND definitions in the EDDL File.
Sample command definition for EtherNet/IP device is shown below.
METHOD Description: METHODs are represented as Wizards as shown in below image. Some of thedevice functionalities like Device Setup, Trim, Calibration etc. will be implemented as Methods in the
EDDL file.
Sample EDD method definition for aborting the gas calibration is shown below

2018 ODVA Industry Conference

8©2018 ODVA, Inc.

Sample EDD method wizard screen is shown below

5.2 FDT (Field Device Tool)
FDT is an international, IEC-62453 open standard for industrial automation integration of networks
and devices, harnessing IIoT and Industrie 4.0 for enterprise-wide connectivity. The technology
enables configuration, operation and maintenance through a single, standardized user interface regardless of supplier, device type/function or communication protocol. Most major systemmanufacturers today integrate the FDT Technology in their product/solution offerings and morethan 8,000 devices currently employ this technology. Unlike EDDL, FDT is a software component andcan offer rich graphical user interface with no limitation to depict complex device functionalities.
FDT specification v1.2x depends on Microsoft COM and ActiveX technology and FDT v2.0 is based on
Microsoft .Net technology, hence FDT v1.2x and v2.0 supports only Windows Operating System. FDTGroup upcoming FDT IIoT Server based architecture (FITS) supports other platform as well.

2018 ODVA Industry Conference

9©2018 ODVA, Inc.

Technology evolution of FDT standard is shown below

Image Source: FDT Group
Supported Communication Protocols
16 communication protocol have been supported by FDT standard like CANOpen, CC-Link,
CompoNet, ControlNet, DeviceNet, EtherNet/IP, EtherCAT, Foundation Fieldbus, HART, Interbus, IOLink, Modbus, ISA100 Wireless, PROFIBUS, PROFINET and SERCOS.

5.3 FDI (Field Device Integration)
FDI is an international, IEC-62769 standard for Device Integration and Device Management
Technology, combining base concepts and technology aspects of the Electronic Device Description
Language (EDDL) according to IEC 61804 and Field Device Tool (FDT®) according to IEC 62453, as wellas in IEC 62541 1 (OPC UA).
Supported Communication Protocols
HART, Wireless HART, PROFIBUS, PROFINET, Foundation Fieldbus, ISA100 Wireless, Modbus andGeneric protocol.
FDI basically consists of two elements
1. FDI Device Package
2. FDI Host Systems
FDI Device Package - The Core of FDI
FDI Device Package offers all the elements necessary to integrate field device into the host system. It
consists of EDD and an optional UIP (User Interface Plug-in) and an Attachments. EDD file consistsof Device Definition, User Interface Descriptions, and Business Logic associated with the field device.

2018 ODVA Industry Conference

10©2018 ODVA, Inc.

UIP (User Interface Plugin) is the programmed user interface (software component) offers flexibility
to represent complex device functionalities. Wiring diagrams, registration certificates, and user
manuals can be added to the FDI Device Package as an attachments. All these elements are digitally
signed in the secure FDI Device Package.

Image Source: FieldComm Group2018 ODVA Industry Conference

11©2018 ODVA, Inc.

FDI Host System
FDI Device Packages are imported into the FDI host system. FDI Host system consist of FDI Client and
FDI Server. EDD Engine component within the FDI Server interprets the EDD element within the FDI
Device Package and builds the FDI Information Model (OPC UA) which will be exposed to the FDI
Client. FDI Client is responsible for rendering the user Interface defined in the EDD file and also theUIPs. FDI Server can have the native communication driver or use the FDI Communication Server tocommunicate with underlying field devices.

Image Source: FieldComm Group

6. EtherNet/IP Protocol support in Device Integration Standards
EtherNet/IP has been supported by FDT Standard. By supporting FDI also as the standard
communication and configuration interface between the field devices supporting EtherNet/IP and
host system will proliferate the ODVA's Field Device to PAM Integration use case.

7. Technical Aspects of supporting EtherNet/IP in FDI
This section covers the technical details on supporting the EtherNet/IP device in FDI host systemusing Generic Protocol Extension

7.1 EtherNet/IP support in FDI using GPE (Generic Protocol Extension)
FDI is built with vision of being one device integration standard for all devices of process
Industry, independent of communication and manufacturer.

2018 ODVA Industry Conference

12©2018 ODVA, Inc.

As shown in below image, FDI specification contains Annex document to support specific protocols
like HART, WirelessHART, Foundation Fieldbus, PROFIBUS, PROFINET, ISA100 wireless networks andother standard and/or proprietary communication.

FDI Generic Protocol Extension (GPE) Specification has been developed with the vision of adding
support for more protocols including proprietary without changing host implementation. Any
protocol including proprietary protocol can be supported using GPE specification along with
Protocol Specific Definition (PSD). PSD specification document contains the protocol specificinformation and needs to be specified per protocol so that FDI Communication Servers and FDI
Device Packages supporting such protocol can work together in a host which is not aware about thisspecific protocol.
7.1.1 Modbus support in FDI
Modbus communication protocol has been supported and verified in FDI. FDI Host withsupport for FDI Communication Server with Generic Protocol Extension will be capable of supporting
any communication protocol. This has enabled any Modbus device to be supported in FDI Host using
Modbus Device Packages and Modbus FDI Communication Server/Package.
7.1.2 EtherNet/IP support in FDI

To support EtherNet/IP Device in FDI, it requires
1. FDI Host to support Generic Protocol Extension
2. EtherNet/IP FDI Communication Server
3. EtherNet/IP FDI Device Package for EtherNet/IP field device
7.1.2.1 FDI Host to support Generic Protocol Extension
FDI Host can have native communication drivers or integrate the FDI Communication Server tosupport various communication networks in the plant. FDI Host with support for Generic Protocol
Extension can support any protocol by integrating the specific FDI Communication Server and device
package without changing the host implementation.

2018 ODVA Industry Conference

13©2018 ODVA, Inc.

7.1.2.2 EtherNet/IP FDI Communication Server
EtherNet/IP FDI Communication Server is a dedicated OPC UA Server hosting the FDI
Communication Server Information model and EtherNet/IP driver. EtherNet/IP driver communicateswith the underlying network and provides the information to the FDI Communication Server
Information model.

Note: product images are owned by owning companies and shown here for illustration purposes only

2018 ODVA Industry Conference

14©2018 ODVA, Inc.

FDI Communication Server Information Model

Image Source: FDI Specification

Above image shows the FDI Communication Server information model. FDI Communication Server
Information model reflect the communication networks including their properties, relationships andoperations that can be performed on them. FDI Server communicates with FDI Communication Server
over standard OPC UA communication services.
Configure the FDI Communication Server

As shown in the above information model, ParameterSet in the CommunicationServerType willcontains all the necessary parameters like IP Address, Port etc to configure the FDI
Communication Server and this information will be fetched from the EtherNet/IP FDI
Communication Package associated with the EtherNet/IP FDI Communication Server. These
parameter settings are used during Initialize operation to initialize the unde rlying network.
EtherNet/IP FDI Communication Package is used along with FDI Communication Server to validate
and configure the communication channel parameters.

2018 ODVA Industry Conference

15©2018 ODVA, Inc.

EtherNet/IP FDI Communication Package

EtherNet/IP Communication Package shall contain the Communication EDD as per the service
parameters in the Connection Manager Object Specific service Forward_Open.
Some of the possible parameters are defined below.
1. IP Address (MAC Address)
2. Port
3. Connection Size with option for Fixed/Variable
4. Priority with possible values of Low, High, Scheduled, Urgent
5. Connection Type with possible values of Null, Multicast, Point2Point, Reserved.
Scan & Rescan EtherNet/IP Devices

As shown in the above information model, Scan operation from FDI Server will trigger the Scan
operation available in the ServerCommunicationDeviceType and returns the list of devices as
specified in the protocol specific profile of FDI specification. In case of an EtherNet/IP, Scan Methodin the FDI Communication Server Information model sends the ListIdentity request to the underlying
network. Response received for ListIdentity request will be mapped to the TopologyScanResult
schema used in the Scan method. List Identity response includes some of the attributes of the
Identity Object (Class Code 01Hex). TopologyScanResult schema is defined in the Generic Protocol
Extension specification of FDI Annex document.
Below table shows the possible mapping of response received for ListIdentity request to the
TopologyScanResult schema.
EtherNet/IP Identity Object Response
Expected Identity Object parameter in
TopologyScanResult of GPE
Variable
Data Type
Variable
DataType
Vendor ID
UINT
Manufacturer
StringDevice TypeUINT
DeviceModel
StringProduct Code
UINT
Revision
STRUCT
DeviceRevision
StringStatus
WORD
Serial Number
UDINT
SerialNumber
StringProduct Name
SHORT_STRING
Note: DeviceModel in TopologyScanResult shall also include Device Type and Product CodeConnect and Disconnect EtherNet/IP Device

As shown in the above information model, Connect to Device operation will trigger the Initialize
method and then Connect method available in the ServerCommunicationServiceType. Disconnect
from device will trigger the Disconnect operation from the ServerCommunicationServiceType.
In case of the EtherNet/IP, Connect API shall use the configured parameter set within the FDI
Communication Server Information model in order to perform Connection. EtherNet/IP Driver shalluse the implemented Connection Manager Object as per EtherNet/IP specification to connect withthe underlying EtherNet/IP network.

2018 ODVA Industry Conference

16©2018 ODVA, Inc.

Device I/O operation using Transfer and GetPublishedData method

Any Read/Write operation from FDI Server shall trigger the Transfer operation on theServerCommunicationServiceProvider in the above FDI Communication Server Information model.
Header attribute defined within the Command construct of FDI Device Package includes thenecessary information like Class ID, Instance ID and Attribute ID to perform read/write Operation.
Sample EtherNet/IP Device Package Command definition is shown below.
For Transfer method in the FDI Communication Server Information Model, EtherNet/IP driver shalluse the SendRRData command within the EtherNet/IP specification to perform Read/write operationon the EtherNet/IP device.
It is also possible to use the Class 0/1 connection in the EtherNet/IP to perform cyclic I/O Dataexchange operation and it shall be mapped to GetPublishedData method in the above FDI
Communication Server Information model.
7.1.2.3 EtherNet/IP FDI Device Package
EtherNet/IP FDI Device Package represents the EtherNet/IP Device and shall be provided by the
EtherNet/IP device vendors. It provides all the elements necessary to integrate EtherNet/IP device
to the Automation Host systems.
Sample EtherNet/IP FDI Device Package

Sample EtherNet/IP FDI Device Package shall be developed as per the Generic Profile Extension of
the FDI Specification.
Sample Variable definition for VendorID in the EtherNet/IP EDD file

2018 ODVA Industry Conference

17©2018 ODVA, Inc.

Sample Command definition for ReadIdentityObject in the EtherNet/IP EDD file

Note that structure of the HEADER attribute like SERVCIE_CODE, CLASS, and INSTANCE etc will bedefined in the FDI EtherNet/IP PSD specification.

7.2 EtherNet/IP EDS file in FDI Host system
Existing EtherNet/IP devices in the market has an associated EDS file and contains configuration
details relevant to EtherNet/IP device. These EDS file could be used in the FDI technology in two
ways

1. EDS file as an attachment in FDI Device Package
Existing EDS file associated with EtherNet/IP device can be added as an attachment in FDI Device
Package. FDI Host which supports EDS parser can use this information associated with the FDI
Device Package.

2. EDS file to FDI Device Package conversion
Existing EDS file can be converted manually or using tool to create the EtherNet/IP EDD filepackaged as FDI Device Package. In this case, it is not necessary for the FDI host to support EDS
Parser.

2018 ODVA Industry Conference

18©2018 ODVA, Inc.

7.3 Workflow of EtherNet/IP protocol support in FDI
Below image shows high level architecture of supporting EtherNet/IP device in FDI.

FDI Device Packages for EtherNet/IP device are imported into the FDI Host system. The Device
Definition and Business Logic are used exclusively by an FDI Server and the User Interface
Description (UID) is processed by the FDI Server and transferred to the FDI Client. Each EtherNet/IP
Device package instance is represented in the FDI Server Information model and provide an accessto the FDI Client.
FDI Server is responsible for communicating with underlying EtherNet/IP device network via
EtherNet/IP FDI Communication Server using standard OPC UA interfaces. Any read/write andsubscription operation invoked on EtherNet/IP device will be passed to the FDI Server which in turn
passes it to the EtherNet/IP FDI Communication Server and passes the processed result back to the
FDI Client.
FDI Client is responsible for rendering the User Interface both for UID (User Interface
Description) which will be provided in EDD file of EtherNet/IP Device Package and an UIP. FDI Server
provides FDI Client an access to information about Device Instances (FDI Information model) which
is driven largely by the EtherNet/IP Device Definition file in FDI Packages. This information can beprovided via OPC UA services.

8. FDI Information Model
The FDI Information model (IEC62769-5) is a companion standard to the OPCUA for Devices(IEC62541-100) specification which is an extension to the OPC Unified Architecture specification
series.

2018 ODVA Industry Conference

19©2018 ODVA, Inc.

OPC UA for devices defines the information model associated with field Devices in below threemodels which builds upon each other
1. Device Model
2. Device Communication Model
3. Device Integration Host Model
FDI Information Model reflects the topology of the automation system and represents the devices of
the automation system, connecting communication networks including their properties,
relationships, and the operations that can be performed on them.

Image Source: OPC UA for Devices companion specification

9. EtherNet/IP Device to cloud integration using FDI Information Model
FDI Technology can be used as platform for providing the harmonized data to the higher levelsystems. It standardizes and harmonizes the wealth of information provided by underlying various
Industrial network. This enables any FDI compliant OPC UA client to harvest the data from the FDI
host in a standardized way and provides the plant level to enterprise wide connectivity.
FDI Server hosts the FDI Information Model exposing the underlying device network. FDI Server canchoose to have either native communication driver or FDI Communication Server for supporting
underlying device network. Device instance of the loaded FDI Device Package associated with thefield device will be exposed in the FDI Information Model. Engineering Station, Maintenance Station,
Operator Station or handheld configuration tool can have FDI client communicating with the FDI
OPC UA Server over OPC UA communication channel. Generic or any third party client application
can also connect to FDI OPC UA Server. FDI OPC UA Server can also provide the connectivity to thecloud platform for further processing to support various IIoT use cases like remote data monitoring,predictive maintenance etc.

2018 ODVA Industry Conference

20©2018 ODVA, Inc.

10. Value proposition of EtherNet/IP support in FDI
10.1 End User
Most of the FDI requirements are driven by NAMUR, the "User Association of Automation
Technology in Process Industries", hence EtherNet/IP combined with FDI brings value addition to the
End User community. FDI has got quick market acceptance as the new device integration standard.
FDI's User Style guide ensure that plant operators, maintenance engineers will have similar look andfeel of the field information irrespective of underlying communication networks like HART,PROFIBUS, Modbus, EtherNet/IP etc. This helps to have the single standardized device management
tool for maintaining EtherNet/IP device as well as other communication protocols in the process
Industry.

10.2 EtherNet/IP Device Supplier
FDI combines the simplicity of the text-based EDD technology with the flexibility of FDT. FDT
specification has already been supported for EtherNet/IP devices, hence this paper only focusses on
FDI mapping for EtherNet/IP devices in detail.

2018 ODVA Industry Conference

21©2018 ODVA, Inc.

FDI enables the EtherNet/IP device suppliers to choose the simple EtherNet/IP FDI Device Packagewith only EtherNet/IP EDD for simple devices and FDI Device Package with multiple UIPs torepresent the complex device diagnostics features of complex device. EtherNet/IP device supplierneeds to develop EtherNet/IP FDI Device Package in order to support their EtherNet/IP device in the
FDI compliant host in the Process Industry. EtherNet/IP support in FDI may help to increase themarket share of the EtherNet/IP devices in the process Industry hence bringing more revenue to the
EtherNet/IP device suppliers.

10.3 System Suppliers
Any FDI host supporting the GPE (Generic Protocol Extension) will be able to host the EtherNet/IP
devices along with Modbus or any future protocol. This reduces the cost and risk of upgrading thehost to support new protocols for system suppliers. Also, FDI Communication Server for various
protocols could be bought off the shelf, hence it simplifies the integration of new protocol anddevices to the host system. Also, FDI's client server architecture with standardized OPC UA
interfaces will help the system suppliers in simplifying the device data access in the distributed
control system. This also allows the safe and secure access of valuable device data from the generic
OPC client that can be maintenance tools or MES (Manufacturing Execution Systems) or ERP(Enterprise Resource Planning) systems.

10.4 ODVA and FDI community
Vendor and User community of ODVA will get benefits by having support for another Device
Integration standard FDI which allows the simplified and harmonized access of the EtherNet/IP
device to the PAM and higher level tools. Vendor and User community of FDI would benefit fromhaving the most promising EtherNet/IP protocol support in their standard. This brings more value
and adoption for both of these two standards in the process Industry.
EtherNet/IP support in FDI specification can be achieved by developing the FDI Annex document for
EtherNet/IP communication protocol in line with the approach mentioned in this white paper, by
ODVA (ODVA Process SIG) and FieldComm Group (FDI Specification working group).

11.Conclusion
EtherNet/IP Communication protocol with its huge installation base in Hybrid and Discrete Industry
has all the potential to become the most accepted Industrial communication protocol in the Process
Industry as well. ODVA's initiative of OPI (Optimization for Process Integration) will show its interestin adopting to the special needs of Process Industry. On the other hand, Most of the FDI
requirements are driven by NAMUR, the "User Association of Automation Technology in Process
Industries" and FDI has received good market acceptance in the process Industry. FDI's flexible
architecture to add more protocols without changing the host implementation will help in adding
more protocols to the FDI standard in the coming years. As mentioned in NAMUR's position paperon "An Ethernet communication system for the process industry", EtherNet/IP and FDI standard isgoing to play vital role in the Process Industry in the near future and having the EtherNet/IP supportin FDI would benefit End User community, EtherNet/IP device supplier, System Supplier and ODVA
as well as FDI community.

2018 ODVA Industry Conference

22©2018 ODVA, Inc.

12.References
Optimization of Process Integration: Using EtherNet/IP for Integration of Field Devices with a Process
Automation System - ODVA
https://www.odva.org/Portals/0/Library/Conference/2015_ODVA_Conference_OPI_FINAL.pdf
Optimization to Process Integration - ODVA
https://www.odva.org/Optimization-40/Optimization-of-Process-Integration-OPI
https://www.odva.org/Portals/0/Library/Publications_Numbered/PUB00286R1_ODVA-Optimization-ofProcess-Integration.pdf
NAMUR - User Association of Automation Technology in Process Industries
https://www.namur,net
3 Steps to FDI
https://www.fieldcommgroup.org/sites/default/files/ technologies/fdi/ThreeStepsToFDI_v1.0.pdf
Digital Transformation in the Age of IIoT - White Paper from FieldComm Grouphttps://www.fieldcommgroup.org/sites/default/files/ technologies /Digital%20Transformation%20in%20the%0Age%20of%20IIoT%20-%20white%20paper.pdf
FDI-User-Requirements 2011, in addition to NE 105
http://www.namur.net/index.php?id=208&tx_ttnews [tt_news]=218&L=1
FDI technology in detailhttps://fieldcommgroup.org/technologies/fdi/fdi-technology-detail
OPC UA for devices companion specification document
EtherNet/IP Specification from ODVAFDI Specification from FieldComm Group

13.Copyright
EtherNet/IP Logo - ODVAFDI, HART, WirelessHART, Foundation Fieldbus Logos - FieldComm GroupPROFIBUS, PROFINET Logos - PROFIBUS & PROFINET International
ISA100 Logo - International Society of Automation
OPC UA Logo - OPC Foundation
Modbus Logo - Modbus Organization
EtherNet/IP, OPI and OPI - enabled are trademarks of ODVAGraphics and Texts – ODVA, FieldComm Group, FDT Group and OPC Foundation
Product logos, images all rights reserved by owning companies
Other trademarks are property of their respective owners******************************************************************************************************************************************************The ideas, opinions, and recommendations expressed herein are intended to describe concepts of the author(s) for the possible use of ODVA
technologies and do not reflect the ideas, opinions, and recommendation of ODVA per se. Because ODVA technologies may be applied in many
diverse situations and in conjunction with products and systems from multiple vendors, the reader and those responsible for specifying ODVA
networks must determine for themselves the suitability and the suitability of ideas, opinions, and recommendations expressed herein for
intended use. Copyright ©2018 ODVA, Inc. All rights reserved. For permission to reproduce excerpts of this material, with appropriate
attribution to the author(s), please contact ODVA on: TEL +1 734-975-8840 FAX +1 734-922-0027 EMAIL odva@odva.org WEB www.odva.org.
CIP, Common Industrial Protocol, CIP Energy, CIP Motion, CIP Safety, CIP Sync, CIP Security, CompoNet, ControlNet, DeviceNet, and EtherNet/IP
are trademarks of ODVA, Inc. All other trademarks are property of their respective owners.

2018 ODVA Industry Conference

23©2018 ODVA, Inc.