FDI OVERVIEW

2Q2017

FieldComm Group is the Home of HART, FF, and FDI

Technology

FDI is part of the IIoT for the Process Industry

3

Industrial internet of

things Supports

mission critical

Enterprise-wide

requirements

FDI – The Big Picture

4

Physical devices are virtualized in software as FDI Device Packages

Packages are imported into an FDI Server

Clients including systems, handhelds and

cloud services get information from the

server

What is the Motivation Behind FDI?

5

1. Reduce lifecyle costs

Currently EDDL and FDT technologies are recognized and widely

used in the process management industry.

Result is that the industry typically has to implement solutions for

each technology, duplicating work. This also requires a variety of

toolsets and skill sets be maintained.

Goal: A single technology that leverages the best of both existing

technologies.

Motivation Pre-FDI host requirements and

conformance tests did not drive

interoperability

Result is that device vendors often

have to develop custom DDs for

specific hosts

Goal: A technology where DDs will

operate consistently on every host

2. Reduce lifecyle costs

Motivation

Whether you have a simple device or a complex device, the use of

two technologies drives a similar workflow.

Result is that it is expensive and difficult to roll out a device, even if

it is a very simple device.

Goal: A solution where a programmatic user interface is optional

and used only when needed to address complexity.

3. Need a scalable solution

Motivation

Current programmatic UI solution – FDT/DTM – has a dependency

on the operating system. It also requires installation of the DTM.

Result is that the system is maintenance heavy. NAMUR does not

want to “install” software with each device.

Goal: A technology that has minimal dependency on the OS and IT

platform.

2001 2009 2012

2015

4. Reduced dependence on IT platform

Device Integration Before FDI

Host #1 (EDDL based)

Host #2 (EDDL based)

Host #3 (FDT Frame)

Host #4 (FDT Frame)

Host #5 (Custom App)

EDDL File (1) Usually per host

EDDL File (2) Usually per host

DTM File (1) May vary by OS rev

DTM File (2) May vary by OS Rev

App File (1)

One Device Multiple Integration

Files/Drivers

Device Integration with FDI

Host #1 (Native FDI host)

Host #2 (Native FDI host)

Host #3 (FDT Frame – FDI DTM)

Host #4 (FDT Frame – FDI DTM)

Host #5 (Custom App – FDI UIP)

FDI Device

Package

One Device One Device Package

FDI – The Better Way of Field Device Integration

11

The primary objective of FDI is to dramatically simplify

software installation, configuration, maintenance, and

management of field instruments and host systems

Before FDI

FDI

Today’s field devices often include over 200 files that

are needed for a successful integration with a host

FDI brings standardization to the

packaging and distribution of all

the software and tools

Only one FDI Device Package is

needed for a successful integration

with a host

ONE Device

ONE Package

ALL Tools

FDI Device Packages – The Core of FDI

14

◦ The FDI Device Package is the core

component of an FDI enabled system.

◦ An FDI Device Package is a single

software package that contains all tools,

device information and user interface

plug-ins needed for the device.

FDI Packages us the Open Packaging Convention to bundle all parts into a single file *.fdix

Attachments can can be device pictures, registration certificates, user guides,

and protocol integration text files

A UIP is a programmed user interface. This is an optional component that allows more flexibility than the mandatory UID.

The UID is a mandatory component written in EEDL that provides a basic unit interface

Differences between UID and UIP

UID

Mandatory package component

Written in EDDL

Provides standard and familiar

EDD intefaces

UIP

Optional component

.NET today, HTML5 future

Allows complicated interfaces and

graphics

13

Packaged are Consumed by FDI Hosts via an import

process. NO INSTALLATION REQUIRED

14

FDI Device Package

FDI Host The information model is a server of all imported packages and instances

FDI Cyber Security Considerations

15

FDI Device Packages

o Include all information needed by the end user to integrate

a field device into their system. Information in the FDI Device Package includes the

required Enhanced Device Description (EDD) File, anoptional User

Interface Plugin (UIP) and optional attachments.

Digital Signatures

o The FDI technology utilizes digital signatures to guarantee

the contents of an FDI Device Package have not been

altered in transit. The originator of the package signs over the entire contents of the FDI

package before making it available to end users.

o FDI Hosts that consume FDI Device Packages check the

digital signature before allowing the FDI Package to be

loaded Detects a compromised FDI Package before loading it into the system.

FDI Cyber Security Considerations

16

Secure “Sandbox” Execution

o In addition to digital signatures, the FDI Technology

provides robust security for the UIP hosting environment. UIPs provide a programmatic means for implementing solutions where

a complex user interface or complex diagnostics are required.

o The FDI Technology requires that every FDI Host

implement a “sandbox” where UIPs are executed. The FDI Host does not allow the UIP to access any system resources

outside this “sandbox” (e.g. the internet) and thereby limits adverse

effects an errant or compromised UIP can have on the system.

Compliance Testing & Registration

17

A Product bearing the Registered

Mark undergo a rigorous testing

process

FieldComm Group governs the overall

process – for all supported

communication protocols

Customer Benefits of FDI – A summary

18

Interoperability

• FieldComm Group performs conformance tests for FDI

Device Packages and hosts to ensure interoperability

• Software components for the FDI host are standardized

• An FDI Device Package uses harmonized EDDL

compatible with the FDI standard host components

Ease of use for System Admins

• An optional OPC UA communication server can be

used for connecting to ERP and MES systems

• No software in-stallation is required when an FDI

Device Package is imported by the FDI host

Robustness

• FDI Device Packages do not impact system’s robustness

• Packages are not programs which have to be installed

• An FDI Device Package for one device type does not

impact devices already integrated

Migration and investment protection

• New version of FDI hosts must be compatible with older

versions of FDI Device Packages

• FDI host may support existing EDD and FDT based hosts

Ease of use for Users

• FDI provides the same look and feel for all devices

• FDI hosts can support FDI Device Packages for

HART, FOUNDATION Fieldbus, PROFIBUS,

PROFINET and other protocols Ease of use for

system administrators

Robustness

Migration and investment protection

Interoperability

Ease of use for users

FDI Packages + Hosts + Registration

= Secure Stress-Free Integration

19

FDI TODAY

ISA100

Annex

FDI supports new protocols

21

FDI Package IDE

Reference Runtime Environment

Device Package Test Tool

Pac

kagi

ng

Toke

niz

ing

Edit

ing

UIP

Device Information Model

PROFINET

Annex

HART/HART IP/ Wireless HART

FF

Profibus

PROFINET

ISA100 FDI Comm Server

Generic Protocol Extension (GPE) Annex

Modbus FDI Comm Server

Ethernet/IP FDI Comm Server

FDI Modbus PSD Specification

FDI Ethernet/IP PSD Specification

POC Ready

Future Protocols….

FCG/PNO

3rd party

FDI FUTURE

22

Example NAMUR open architecture (NOA) - idea

23

Support NAMUR open architecture (NOA)

24

New Protocols

25

- Additional protocol drivers

will be integrated via

OPCUA

- No impact on FDT Tools

and Components.

FDI Package IDE

Reference Runtime Environment

Test Engine

Pac

kagi

ng

Toke

niz

ing

Edit

ing

UIP

HART FF H1

PROFIBUS PROFINET

HARTIP

ISA100

OP

CU

A

other

Development Test Certification/

Registration

Package

EDD UIP

Package

EDD UIP

Package

EDD UIP

Device Package

Package

EDD UIP

Package

EDD UIP

Package

EDD UIP T. B. D.

Copyright

26

Copyright © 2015 FieldComm Group™

This document contains copyrighted material and may not be reproduced in any fashion without the written permission of the

FieldComm Group™.

Trademark Information

FieldComm Group™, FOUNDATION™ Fieldbus and HART-IP™ are trademarks, and HART® and WirelessHART® are registered

trademarks of FieldComm Group, Austin, Texas, USA. FDI® is a registered trademark of FDI Cooperation, LLC. Any use of these

terms hereafter in this document, or in any document referenced by this document, implies the trademark/registered trademark. All

other trademarks used in this or referenced documents are trademarks of their respective companies. For more information, contact

FieldComm Group at the address below.

Attention: FieldComm Group President

FieldComm Group

9390 Research Boulevard, Suite I-350

Austin, TX 78759, USA

Voice: (512) 794-0369

Fax: (512) 794-3904

http://www.fieldcommgroup.org

Intellectual Property Rights

The FieldComm Group (the Group) does not knowingly use or incorporate any information or data into the HART, FOUNDATION

Fieldbus and FDI protocol standards, which the Group does not own or have lawful rights to use. Should the Group receive any

notification regarding the existence of any conflicting private IPR, the Group will review the disclosure and either (A) determine there is

no conflict; (B) resolve the conflict with the IPR owner; or (C) modify the standard to remove the conflicting requirement. In no case

does the Group encourage implementers to infringe on any individual's or organization's IPR.

Backup Slides

FDI brings Field Devices to the IIoT

28

Services, Applications,

Algorithms

FDI Server Information Model

MES, CMMI, Engineering, ERP, …

Data Collection, storage, analysis

…

Communication

» OPCUA (IEC 62541)

Real Devices

FDI (IEC 62769)

» Device Information Model

(OPCUA, IEC 62541-100)

» Virtual device objects

Reference architecture for Industry 4.0

29

German industry Associations BITKOM,

VDMA and ZVEI recommend a Reference

Architecture Model for Industry 4.0 (RAMI)

Functional layer: FDI

Information layer: FDI

Communication layer: OPCUA

FDI integrates seamlessly into the Reference

Architecture Model for Industry 4.0

The FDI Package

page 30

Blending the best of what you already use

• Device Packages are processed on native and FDI based FDI hosts FDT Systems!

• Additional DTMs or EDDs are no longer required.

FDI Device Package The best plus more

FDI Host

FDT/FDI Host

The best of EDDL

The best of FDT FD

T2

Fram

e

Suggest moving to Backup

Developer Section

Forward Focused – Backward Compatible

32

Millions of devices worldwide are currently installed, configured,

operated, and maintained by control systems and tools that support

either the EDDL or FDT standards.

FDI is designed to support FDI Device Packages as well as DTMs and

EDDs in parallel.

FDI Compliant EDD Host

Development Tools Aid Suppliers:

FDI Standard Host Components

Development Tools Aid Suppliers:

Integrated Development Environment

9 January 2013

Development

Integrated Development Environment (IDE)

Test Certification/Registration