3 Steps to FDIIT’S IN YOUR HANDSWELCOME TO FDI

Ready for the three simple steps?

Ted Masters
President and CEO
FieldComm Group

Copyright information
FDI, HART, FOUNDATION Fieldbus logos - FieldComm GroupPROFIBUS, PROFINET Logos - PROFIBUS & PROFINET International
ISA100 Logo - International Society of Automation (ISA)OPC UA Logo - OPC Foundation
Product logos, all rights reserved by owning companies
Graphics and texts - FieldComm Group
Graphics on page 25, 27 - theseamuss, fotolia.com & FieldComm GroupIcons - mdesignstudio, fotolia.com
Photo on page 6 - rendermax, fotolia.com & FieldComm Group
Photo on title page and page 8/9 - sdecoret, fotolia.com

2

Achim Laubenstein
Director of Integration
FieldComm Group“FDI is a critical path building block for Digital Transformation as the new standard for communication
between field devices and hosts.”“FDI is much more than a standardized way of device
parameterization. The FDI architecture provides
all means to expose field device information to theInternet of Things.“

The revolution of Digital Transformation is taking
shape all over the automation industry. The needfor standards has never been more relevant andboth end users and manufacturers must be assured
their products meet strict standards to deliver all
the capability, system-wide interoperability, security
and performance they expect and require. FDI is a
critical component of this revolution, with a mission tosimplify the integration between devices and hosts ofall types: ONE device - ONE package - ALL tools!

The FDI development was is an unprecedented levelof cooperation of major process automation suppliers
and standards organizations listening to end users’
requirements. The result is a device integration
technology across protocols for the management ofdevice information throughout all areas of a plant.
With one FDI Device Package applicable for all hostsystems, device integration interoperability issues
disappear and all involved parties, end users, device
vendors and host vendors benefit from significant
operational savings.

Now, regardless of protocol, software language or
manufacturer, users who purchase FDI registered
hosts and device packages can be assured thesestandards are met with a common look and feel for
their staff to utilize. Sure, it will take time to migrate
existing plants and operations to “all FDI”. As weevolve in this direction, backward compatibility isimperative and a requirement for FDI registered hosts,
serving to protect the users’ investment in existing
assets. The FDI migration is starting now and provides
users an opportunity to revolutionize the integration of
the digital data from field devices across the systems
that need it to run their enterprises better!
This brochure will explain why and how FDI can be
implemented. All the tools and training you need toget started exist today and can be delivered throughFieldComm Group. I encourage you to get started on
the path of evolving your plant in this digital revolution
by implementing FDI technology as your future-proof
integration standard!

Additionally, FDI’s architecture enables standardized
access to device information through the OPC-UA
Device Information Model for new devices and – evenmore important - the installed base. This includes
semantic information to allow interpretation ofdevice information by computer programs, e.g. cloud
applications.
FDI technology is a perfect fit for upcoming
system architectures as required by NAMUR Open
Architecture, Industrie 4.0, Industrial Internet ofThings and similar initiatives. FDI Technology is forend users and manufacturers the enabler to create
additional value from device information.

ONE device - ONE package - ALL tools

3

STRESS-FREE INTEGRATIONFDI Device Packages + Hosts + Registration

The primary objective of FDI is to dramatically simplify software installation, configuration, maintenance, andintegration of field instruments with host systems. Today’s field devices often include a device information filesuch as an EDD or a DTM™ that provides software access to the features and functions of the device, one or moreuser interface plug-ins that integrate with host system software to enhance usability of the field device with thehost, numerous user manuals, installation instructions and data sheets.

Learn about FDI + Create solutions + Register products = Stress Free Integration
DD
000100100011
000100100011
000100100111

Before FDI - multiple integration products had to be implemented and maintained by the device manufacturers,
supportive documents had to be searched and collected by the users, and several integration standards had to besupported by the system vendors.

EDD

Plug-In

EDD

UIP

000100100011
000100100011
000100100111

FDI Device Package

generic

SpecialUIP

Instances

ATTACHMENTS

Types

Documentation

8

EDD

UIP

ATTACHMENTS

000100100011
000100100011
000100100111

FDI Device Package

10

Applications
Notes

16

1

FDI Device Package
per protocol

2.
CreateCreate FDI solutions.
Use technical specifications,development tools, common
software components toincrease eﬃciency to save costs
and to ensure interoperability.

13

SafetyInstructions

24

EDD
000100100011
000100100011
000100100111

OperatingInstructions

18

ATTACHMENTS

1.
Learn

200+

Manufacturer
ReadmeUIP000100100011
000100100011
000100100111

Learn about how
FDI works and what thebenefits compared to past
integration technologies are.

downloadable
files available for acommon flowmeter

BeforeFDI

LOGICLOGIC
000100100011
000100100011
000100100111

FDI Package

FDI brings standardization to the packaging and distribution of all the software and tools necessary to integrate adevice with a host system regardless of protocol. All registered FDI devices will have one single FDI Device Package
consisting of all the host needs to optimize the capabilities of each device.

Installation
Instructions

UID
000100100011
000100100011
000100100111

FDI

STRESS-FREE
INTEGRATION

3.
Register
Register your FDI solution
with FieldComm Groupto indicate conformance tothe international FDI standard
and proven interoperability withother FDI solutions.

DeviceDrivers

53

Country
Registration
Certificates

62

4

FDI is a system-wide solution. Host systems, like asset management systems, configurators, and device managers
must support the FDI client-server architecture. Field device suppliers encapsulate device specific software anddocumentation into an FDI Device Package. Finally, product registration service providers, like FieldComm Group,deliver high quality conformance testing, registration, and FDI Device Package distribution services.

ONE Device – ONE Package – ALL Tools

When host systems, FDI Device Packages, and high-quality registration are combined, end users can take advantage
of a truly stress free device integration solution.

ONEdevice- ONE
package
- ALL
tools
ONE
device- ONE
package
- ALL
tools

5

THE HOME OF FDI

We are the FieldComm GroupThe development of international technology standards requires real experts. These experts are member company
volunteers who come together in working groups several times a year or meet up in online conferences to collectknowledge, discuss technical aspects and to write technical specifications - creating technologies that target theneeds of the end users. All activities are organized, supported and managed by FieldComm Group.
For the development of FDI, not only member companies but also different technology organizations cooperated
and still cooperate. FieldComm Group, PROFIBUS and PROFINET International (PI), OPC Foundation and FDT Group
share knowledge and jointly invest into the development and maintenance of FDI.
FDI Technical Specifications available here:
go.fieldcommgroup.org/fdispecification

FieldComm Group is a global standards-based non-profit member organization consisting of leading process
end users, manufacturers, universities and research organizations. FieldComm Group develops, manages andpromotes global standards for industrial communication protocols (HART® and FOUNDATION™ Fieldbus) and forthe integration of intelligent devices into automation system architectures (EDDL and FDI). FieldComm Group was
founded in 2015 when the assets of HART Communication Foundation and Fieldbus Foundation were combined.
In 2016, FDI technology was added to the extensive IP portfolio of FieldComm Group. While being based in Austin,
TX in the USA FieldComm Group has representatives all over the world, providing members with the latest on
integration and communication technologies for products mainly used in the process automation industry.

Become a FieldComm Group member:go.fieldcommgroup.org/becomeamember

30,000,000+
Products
available

3,000,000+
Products
available

Registering
products
today!

6

The FieldComm Group not only manages thestandardization and maintenance of different
technologies but also provides extensive producttesting and registration services, product development
services, design consulting services and technicalsupport for the several development software
products.
These services can be used by the growing communityof member companies (350+ global members) toensure reliable and interoperable HART, FOUNDATION
Fieldbus and FDI products.

FDI Technical Specifications(IEC 62769)

Technical
Specifications(Parts 1 – 7)

Communication
Protocol Profiles(Parts 10x-y)

ProtocolIndepedent

ProtocollinkageTechnology Mapping(UIP Development)

Guidelines(Usability Style
Guide, Validation
Status)Microsoft.NET / WPF

Informative

Number may grow in the futureHTML 5(coming soon)

Referenced Technologies

EDDL(IEC 61804)

OPC UA(IEC 62541)

FDT(IEC 62453)

Language
specification

Not mandatory

Not mandatory

ONE device - ONE package - ALL tools

Open Packaging
Convention(IEC 29500-2:2011)

For Packages
and UIPs

7

READY?

Here are the three steps to FDI

Learn
Learn about how FDI works and what
the benefits are, compared to past
integration technologies.

8

CreateRegister

Create FDI solutions. Use technicalspecifications, development tools
and common software components toincrease eﬃciency, to save costs andto ensure interoperability.

Register your FDI products withFieldComm Group to indicate
conformance to the international FDI
standard and proven interoperability
with other FDI solutions.

ONE device - ONE package - ALL tools

9

STEP 1: LEARN

How does FDI work and generate value for everybody?

ONE package for ALL tools = value
More options to learn more...

FDI Clienton Mobile Device

FDI Clientfor Asset Management

importPhysical Device

EDD

UIP

There are many ways to get a more in-depth
knowledge about FDI and learn about the benefits
the technology brings to different interest groups.
Furthermore best practices and hands-on can beexperienced as well as classic training sessions.

use

ATTACHMENTS

000100100011
000100100011
000100100111

FDI Device Package

Data Analysis

Cloud
Data
FDI Server
FDI Clientfor Engineering / Operations

represented byToday’s intelligent field devices can be configured to perfectly meet process requirements. They furthermore
provide data and functions to visualize the current operation or to analyze device failures. In FDI, knowledge
about a device type is encapsulated into a single file, the FDI Device Package. This package can simply
be imported into any FDI Server, no real installation procedure is required. The device’s parameters, its
functions and user interfaces, are kept in the server’s information model and can be accessed by any FDI
Client application (the execution of all package parts including UIPs must be supported by the FDI Client).
Clients can run under different operating systems and platforms, can be mobile or stationary - It’s one package forall tools. In a digitalized industrial environment of the IIoT, device data can furthermore be published into a cloud
and accessed by client and software applications in order to generate even more value for the plant operators.

10

FieldComm Group provides:• Training Programs• Webinars• FDI PlugFest experience
Also available:• Technology Roadshows• Seminars / Trainings• Book / eBook:“FDI - Field Device Integration
Handbook for the unified Device
Integration Technology”
ISBN 978-3-8007-3630-0

Learn more about the training program:go.fieldcommgroup.org/fditraining

FDI will provide a reduction of tools, costsavings, consistent interfaces, and ease of use
for both manufacturers and end users.
Peter Zornio
Chief Strategic Oﬃcer, Emerson

ONE device - ONE package - ALL tools

11

STEP 1: LEARN

FDI Hosts - the device data control centers

The FDI Host consists of two major entities, the FDI Server and the FDI Client. The server provides means to importand manage FDI Packages and also to read and interpret the content. The device data is held in the information
model created by the server and based on the FDI Package content. An FDI Client is able to access this information
model, to manipulate device parameters, to read measurement data and to render user interfaces to access thisinformation.
FDI Hosts are capable of working with all FDI Package types (depending on the available Facet, see below) and thecomplete defined content without exceptions. The different architectures shown below are possible to meet therequirements of the users in the process industry.
Your benefits:
Harmonized, single integration technology with standardized, open data model, full support of different
host architectures and powerful optional facets; prepared for connection to the IIoT.

FDI Server
FDI Client

UI Engine
For rendering of descriptive UI (XMLrepresentation generated by FDI Server) and for
hosting and execution of User Interface Plug-Ins(UIPs). The UI Engine is not aware of the EDDL.

FDI Host
FDI Client

FDI Server

UI Engine

Information Model (IM)UIP

Instances

ATTACHMENTS

Single user / single node
Typically monolithic architecture with one user at a timeworking with the Information Model.
> Device Tools, handhelds, stand alone device applications

Catalog
EDD

UIP

EDD Engine

ATTACHMENTS

EDD

000100100011
000100100011
000100100111

FDI Device Package

FDI Server

Multi user / client server
Multiple users access the device data at a time. Client
server architectures are frequent.
> Distributed host systems, asset management systems

FDI Client

Types

OPC UA*

Industrial
ProtocolFDI Client

Information Model (IM)
Structured and standardized representation ofdevice models (parameters and addressing) andUser Interfaces (Menus). The IM contains type
information and knows specific instances derived
from those types.

000100100011
000100100011
000100100111

importEDD

UIP

EDD Engine
Interprets EDDs, is aware of
the FDI common binary format.
Used to execute EDD methods oractions (logic). The EDD engine
reads parameter descriptions,
protocol specific addressing and UI
descriptions (UID) from the EDD.

OPC UAATTACHMENTS

000100100011
000100100011
000100100111

FDI Device Package

Industrial
ProtocolCommunication Server

FDI Host Facets (optional)
FDI Client

OPC UA

FDI Server

OPC UA Client
OPC UA

FDI Communication
ServerIndustrial
ProtocolInformation Model Facet
Allows FDI Clients with OPC UA interface or native OPC UA
Clients to connect to FDI Servers in order to access thedefined Information Model. Selective and safe transmissionof device data to IIoT applications is possible.
FDI Communication Server Facet
Allows the use of FDI Communication Packages / Servers
to add any communication device to the FDI Server. Anykind of complex communication topology can be modeledwith this facet being implemented.

Communication Server
Represents communication devices(end points). FDI Server and Communication
Servers are connected via FDI specific
OPC UA services. Complex communication
topologies can be modeled with this mechanism.

Field
Devices* Optional: OPC UA Facet allows access to the IM via OPC UA services. IIoT enabler. Otherwise private interface.

12

ONE device - ONE package - ALL tools

13

STEP 1: LEARN

Get ready for the IIoT with FDI

The revolution in our industry referred to as the Digital Transformation, the Industrial Internet of Things (IIoT), theIndustrie 4.0 refers to unleashing the power of data that’s available in industrial plants, but remains largely unused
and to the creating of additional value using this powerful intelligent data.
In FDI technology the ‘Things’ are represented by the different field devices (e.g. smart sensors, actuators,
communication devices). With the FDI Package these devices are integrated into the operational infrastructureof the industrial plant, the FDI Host. FDI Clients are then able to access the data, to render user interfaces and toaccess device functions directly.

IIoT Services*
Can be available on premise or in the cloud.
Provide additional value (e.g. through big data
analysis, specified user interfaces, multi-nodecondition monitoring, ...). Read only access todevice parameters (recommended).

The FDI Hosts Information Model Facet with OPC UA is the key to the IIoTAn FDI Host implementing the Information Model Facet exposes a standardized OPC UA Information Modelcontaining the complete device data, accessible via FDI Clients and standard OPC UA Clients / Servers. As part of
the OPC UA infrastructure, the data collected from the ‘Things’ can be used by Asset Management Systems or canbe published into IIoT platforms and processors to generate even more value for the plant operators.

publishOPC UA Clients
Have access to the parameter set of theInformation Model. Read only access to device
parameters (recommended).
OPC UA Clients

FDI + OPC UA = IIoT connected

FDI Client (full featured)Have access to the entire Information Model,
render UID and host UIPs. Can read from andwrite to device parameter nodes. Execute logic.

Digital Transformation
Digital transformation is the actof leveraging digital connectivity,
scalability, analytics and reimagined business processes todramatically improve operationaleﬃciency, safety and value
creation.

FDI Clients

FDI Host with Information Model Facet
Has knowledge about the device data, functions
and how to access this data (knowledge about
the communication protocol) through theimported FDI Device Package. This knowledge isavailable in the FDI Host Information Model (IM)exposeOPC UA Information Model
Instances

Catalog
EDD

UIP

Types

EDD Engine

ATTACHMENTS

000100100011
000100100011
000100100111

FDI Device Package

EDD
000100100011
000100100011
000100100111

EDD

UIP

FDI Server

ATTACHMENTS

000100100011
000100100011
000100100111

FDI Device Package

Communication
Infrastructure

Smart device represented by FDI Device Package
All device data and functions have been describedby the device manufacturer and encapsulated in
an FDI Device Package.

Your benefits:
FDI has a built in IIoT connector - the Information Model Facet (OPC UA). Devices are integrated once into
the IT infrastructure with the FDI Package.

‘Things’ in the field* List of services not complete. Represents example services.

14

ONE device - ONE package - ALL tools

15

STEP 1: LEARN

FDI Packages - the key to device data

User Interface Description (UID)
Description of user interfaces written in
EDDL. UID supports basic parts such as
windows, tabs, input fields, buttons as wellas complex elements such as trends, gauges
and bar graphs. Part of binary EDD.

Logic
Source code written in EDDL with a syntax
comparable with C. Allows the implementation oflogic, e.g. describing parameter dependencies or
algorithms for value calculation. Part of binary EDD.

> Mandatory element> Mandatory Element

Device Definition
Description of the device model,
written in the Electronic Device
Description Language (EDDL), e.g.
Parameters, Variables, Addressing
principles. Part of binary EDD.
> Mandatory element

DD
000100100011
000100100011
000100100111

UID
000100100011
000100100011
000100100111

Attachments
Device pictures, documentation,
registration certificates but also protocol
integration files are bundled into the FDI
Package. The file formats are defined.

LOGICLOGIC> Optional element(can be mandatory for selected protocols)> Allowed number = 1..n000100100011
000100100011
000100100111

In the FDI world not only field devices, but also communication devices and gateways are all represented by FDI
Packages. Different package types make sure that the different specialties of the device groups are considered.
Device descriptions or programmed user interfaces, documentation and protocol integration files can be delivered
with a package. Everything the user needs is bundled in a single file. FDI Packages are typically created anddelivered with the hardware product by the device manufacturers, who seal the package to protect the content. If
this seal is broken the FDI Host informs the user about the security breach. To ensure interoperability the package
should be registered with FieldComm Group. The signed registration certificate is included in the package and will
be checked by the FDI Host.
Your benefits:
Harmonized, authenticated, single integration technology with all possibilities to perfectly represent thedevice type and all required artifacts encapsulated in a single file.

EDD

UIP

ATTACHMENTS

000100100011
000100100011
000100100111

FDI Device Package
Electronic Device Description (EDD)
Tokenized binary containing Device
Definition, UID and Logic written in
EDDL.
> Mandatory element> Allowed number = 1

Packaging (*.fdix)
FDI Packages use the Open Packaging
Convention (OPC) to bundle all package
parts (mandatory and optional) intoa single file with the ending *.fdix. A
specified naming convention has to befollowed.

EDD

UIP

ATTACHMENTS

000100100011
000100100011
000100100111

EDD

FDI Package

User Interface Plug-In (UIP)
Programmed user interfaces. Consists of UIP
Variants for different platforms, implemented
by using different technologies (e.g.
Workstation platform requires .NET / WPF UIP
implementations). Bundled by using the OPC
Technology into a single file with the ending *.uip.

UIP> Mandatory element> Allowed number = 1

FDI Profile Package

EDD

UIP

ATTACHMENTS

000100100011
000100100011
000100100111

FDI Communication Package

UIP

UIP

FDI UIP Package

16

ATTACHMENTS

000100100011
000100100011
000100100111

Catalog FileContains information about the device
type (identification, versioning, protocol
details), the device manufacturer(name, contact information) as wellas compatibility information (e.g.
supported device revisions, supported
UIP versions)> Optional element> Allowed number = 0..n

FDI Device Package
Represents sensors, actuators and other intelligent devices in the plant. Can beused with a specific device type and its specified versions.
Mandatory > Catalog, EDD, Attachments (e.g. CFF for FOUNDATION Fieldbus)
Optional > UIPs, Attachments (e.g. Manual, Certificates)

ONE device - ONE package - ALL tools

UIP

FDI Profile Package
Can be used with all device types for view and manipulation of profile
parameters and functions of a single profile (e.g. HART Universal and Common
Practice Commands).
Mandatory > Catalog, EDD, Attachments (e.g. CFF for FOUNDATION Fieldbus)
Optional > UIPs, Attachments (e.g. Manual)
FDI Communication Package
Represents communication devices (e.g. HART Modems, Gateways) and also
provides translation knowledge between different protocols. Communication
end points, directly connected to the PC additionally require an
FDI Communication Server.
Mandatory > Catalog, EDD
Optional > UIPs, Attachments (e.g. Manual)

FDI UIP Package
Container for UIPs. Only allowed to be used to deliver UIPs, not required for
device parameterization but to provide added value for the users.
Mandatory > Catalog, UIPs
Optional > None

17

STEP 1: LEARNUID and UIP - What is the difference?

UID
000100100011
000100100011
000100100111
Examples: Rosemount, ABB, KrohneYour benefits:
Easy to use and fast to implement. Full eﬃciency and platform independence with simple descriptive userinterfaces and the implementation of basic logic.
The User Interface Description (UID) is part of the Electronic Device Description Language EDDL and allows theeﬃcient development of user interfaces to access device parameters and functions. Typical UI parts used arewindows, tabs and input fields. For more sophisticated user interfaces special UI parts pictures, trends or gauges
can be used.
The user interface can be structured by using menus. FDI defines standard menus which are used as main entry
points (e.g. Diagnostics, Maintenance, Process Variables). In addition, the UID allows the implementation of
dynamic user interfaces. The visibility of parameters or input options can for example be based on conditionals.
The majority of the user interface should be implemented as UID since it is not bound to a specific platform or
operating system and part of FieldComm Group managed EDDL technology. User Interface Descriptions can be
implemented very eﬃciently. However UID is limited to the UI parts defined in EDDL and the basic logic capabilitiesof the descriptive programming language.

&

Examples: Krohne, Endress+ Hauser

UIP

User Interface Plug-Ins (UIP) extend the capabilities of UID. High-level programming languages and state of theart implementation technologies such as .NET or HTML5 (coming soon) can be used to implement impressive,
complex UI and algorithms. Complex device functions can be exposed in an understandable and usable way to theusers (e.g. tank geometry, valve signatures, NE107 status configurations). This increases the work eﬃciency onsite. A UIP consists of platform / operating system specific variants. The different variants consider the specialtiesof the platforms such as screen sizes, touchability or even different use cases. The FDI Technology clearly defines
how the UIP interacts with the FDI Client and the Information Model as well as with the hosting PC. They are
executed in a sandbox to protect the FDI Host.
Currently FDI defines two platforms: WORKSTATION and MOBILE. The platform specific implementation
technologies for UIPs are constantly monitored to ensure interoperability and to secure the life cycle.
Your benefits:
Unlimited possibilities for visualization of complex device functions, implementation of complex algorithms
and unique selling points. Support of different platforms and their specialties.
“UIP is a great enhancement offering thefunctionality not available with EDDs. It enables
smooth parametrization and sophisticated display
options.”
Dr. Christian Brehm
Product Manager Device Interfaces, Krohne

18

ONE device - ONE package - ALL tools

19

STEP 2: CREATE

How to implement an FDI Host?

Before creating an FDI Host, the following importantquestions must be answered:• What shall be the FDI platform(WORKSTATION or MOBILE)?
• Will it be a single or multi user application?
• Single node or client / server?
• Which FDI Host facet will be supported(Information Model, Communication Server)?
• Should the interoperability be ensured by using
standard software components(FDI Common Host Components)?

“We see the use of the Common Host Components
as a major factor in minimizing integration
issues that occurred in the past as a result of
manufacturer-specific solutions. This is underlinedby the requirement, documented in the annex of theNE105 (Device Integration), to have a consistentuse of FDI standard software components.
This requirement is valid for both host systems
and development environments for FDI Device
Packages. Goal is the ‘Plug and Produce’ device
integration in all host systems through a single
Device Package per device type.”

The FDI Common Host Components (CHC) ease the development of a reliable and interoperable FDI Host byproviding the core for an FDI Host implementation. The Reference Runtime Environment, included into the FDI
Package IDE is also based on the CHC. FDI Packages are also implemented against this reference - The CHC
facilitate the creation of a fully compliant, interoperable FDI Host. FieldComm Group and industry partners arecollaboratively working on the development, maintenance and improvement of the CHC since 2010 and willcontinue this commitment in the future.

Michael Pelz, Sven Seintsch
Namur

What about the legacy EDDs in the market?
EDD technology was and still is a wide spread, proven technology. EDDs have been implemented and work reliably
in numerous EDD Host. In order to allow backward compatibility even with a brand new FDI Hosts, the FDI Common
Host Components support the interpretation and execution of EDD files tokenized with legacy tokenizers for HART(*.fm6, *.fm8) and FOUNDATION Fieldbus (*.ff5, *.ffo).

key interoperability elements

Where can I get the FDI Common Host Components?
The components can be licensed from FieldComm Group or PI (PROFIBUS & PROFINET International). The initiallicense includes one year of maintenance under the Product Service Program.

Learn more about the FDI Common Host Components:
go.fieldcommgroup.org/fdichc

FDI Host
FDI Client

FDI Server

UI Engine

Information Model (IM)UIP

Instances

ATTACHMENTS

Types

OPC UA*

Catalog
EDD

UIP

ATTACHMENTS

000100100011
000100100011
000100100111

FDI Device Package

UI Engine
Renders descriptive UI reliably; hosts
UIPs without endangering the stabilityof the FDI Host / FDI Client.

EDD Engine

EDD Engine
Encapsulates knowledge andexpertise of the EDDL and every
detail shows how to deal withspecialties implemented by using
this proven device description
language. Knowledge collectedfrom hundreds of registered
EDDs.

2010

EDD

2003

Prepare Release
Development of test packages
and UIPs, acceptance test
procedures and productization
efforts.

2013

2014

First Results
The first internal test versions of
the FDI Package IDE and the
FDI Common Host Components
are available

000100100011
000100100011
000100100111

FDI Common Host Components (CHC)

20

Kick Off
Involved technology
foundations and big
automation vendors decided
to develop common tools andcomponents and to jointly
fund this activity.

2015

Maintenance Release v1.1
Feedback from members,
working with the Package IDE
and the Common Host
Components is used for firstimporvements.

2016

First release to the public
The first release of Package IDE
and the CHC is published. On
ACHEMA 2015 the FDI tools aredemonstrated to a large
audience.

2017

Stress Free
Integration

More features and legacy EDDs
Release v1.2 improves IT security
and adds development support
for legacy EDDs.

Your benefits:
The FDI Common Host Components are a reliable and interoperable technology enabler for FDI as well as
for existing EDDs. Neither knowledge about EDDL interpretation and execution, nor expertise on FDI userinterfaces rendering or UIP hosting is required in order to successfully build an FDI Host when FDI Common
Host Components are used. FieldComm Group continues to improve the CHC for a Stress Free Integration.

ONE device - ONE package - ALL tools

21

STEP 2: CREATE

How to implement an FDI Package?

Before creating an FDI Package, the following
important questions must be answered:• Which Package Type is required for the device tobe described (Device, Profile, Communication)?
• Can EDDL source code be reused?
• Which Attachments are required and what
documents should be included in the package?
• What needs to be implemented in UID? Whichfunction should be implemented in a UIP?
• For which platforms should the UIPs be built for(WORKSTATION and / or MOBILE)?

Learn more about the FDI Package IDE:
go.fieldcommgroup.org/fdipackageide

Reference Runtime Environment
FDI Host application for test of theimplemented FDI Packages and legacy
EDDs (WORKSTATION, single user,
Communication Server facet)

FDI Plug-In for Eclipse
Project wizards, coding helper (e.g. synthax
highlighting, ‘go to definition’), packaging of FDI
Packages, tokenizer configuration, invocationand much more

FDI
Reference Runtime
Environment

Eclipsetool suite for full eﬃciency
Plug-In

Your benefits:
The FDI Package IDE is a full featured tool suite for the eﬃcient development of EDD and FDI Package
solutions.

Where can I get the FDI Package IDE?
The development environment can be licensed from FieldComm Group or PROFIBUS and PROFINET International(PI). The FDI Package IDE can be licensed for certain communication protocols, e.g. HART, FOUNDATION Fieldbus,
PROFIBUS/PROFINET, ISA 100 or for other protocols with the ‘Generic Protocol Annex’ license.
What about the legacy EDDs for the market?
EDD Technology was and still is a wide spread, proven technology. Numerous EDD Hosts are in the market andstill require EDDs for device integration. With the FDI Package IDE a single development environment can be usedby the integration software developer, to implement reliable and interoperable EDD and FDI solutions. The FDI
Package IDE supports the development and test of legacy HART (*.fm6, *.fm8) and FOUNDATION Fieldbus (*.ff5,*.ffo) EDDs - One single tool suite for FDI Packages and EDDs.

22

UIP

ATTACHMENTS

FDI Common
Host Components

FDI Device Package

FDI Package
Conformance
Test Tool (CTT)The FDI Package IDE speeds up the development of reliable and interoperable FDI Packages. The development
environment supports the coding and tokenization of EDDL source code for use in FDI Packages or in EDD Hosts. A
reference runtime environment which contains the FDI Common Host Components allows the test of the solution
in a real FDI Host. A configurable and extensible conformance test tool completes the tool suite - The FDI Package
IDE facilitates the creation of fully compliant FDI Packages.
Can existing EDDs be reused in FDI Packages?
Most device manufacturers have EDDs available for their existing products. This EDDL source code can easily be
used as a basis for the FDI Device Package development. Just a few adjustments and extensions are required tomake the EDD ready for FDI (more details on page 24/25).

EDD
000100100011
000100100011
000100100111

generic

Tokenizers
Tokenizers
For creation of binary EDD files used in FDI Packages
or directly in EDD Hosts. (protocols available depends
on license). The license option ‘Generic Protocol
Annex’ allows the development of packages for any
additional protocol.

Conformance Test Tool
Test suite for pre-test of FDI
Packages for conformance or for
implementation of individual testplans.

FDI Package IDE
Create FDI Packages
AND EDDs with asingle tool

“The FDI Package IDE provides eﬃcient means to develop
both EDDs and FDI Packages in a single development
environment. The developed packages can conveniently bechecked directly in the Reference Runtime Environment.”
Frank Fengler
Head of Device Integration and Cyber Security , ABB

ONE device - ONE package - ALL tools

23

STEP 2: MIGRATE

How to migrate from existing EDD to FDI?

FDI is the next generation, unified device integration technology. In order to protect the current investment into
EDD based solutions and to effectively extend their life cycle a migration of those products to FDI Device Packages
should be considered. The process is quite simple, fully supported by the FDI Package IDE and allows the device
manufacturers to clean up the existing EDD and to move implementations of complex UI or algorithms to UIPs.
This eases the maintainability of the EDDL source code and potentially increases the usability of the respective
features. Furthermore, the harmonized and extended EDDL allows the device experts to also add value throughoﬄine configuration or the communication protocol independent, cumulated device health status (NE107).
The FDI Device Package is the next logical, evolutionary step for every EDD solution, with better maintainability,
improved usability, more features, more value and improved interoperability.

UIP
Adjust to harmonized FDI EDDL
Clean up and improve code
Add oﬄine configuration support (mandatory)

EDD
000100100011
000100100011
000100100111

EDD

000100100011
000100100011
000100100111

000100100011
000100100011

User benefits (examples):Oﬄine configuration
The oﬄine configuration is a mandatory feature in
FDI EDDs. The preparation of the device configuration
without having a real device available is possible withthis feature. Users simply prepare device datasets anddownload those to the device when it is available.
Standard menus
All FDI EDDs have to provide a specified set of root
menus as standard entry points. The basic menu
structure is therefore the same across all device
manufacturers. This eases the use of packages andreduces training and documentation overhead.

24

EDD

EDD

UIP

Create standard menus (mandatory)
Implement GetDeviceHealth method (mandatory)
Use Private attribute (OPC UA browse) (optional)
Tokenize to FDI Common Binary Format

01

ATTACHMENTS

000100100011
000100100011
000100100111

UIP

FDI Package

04

ATTACHMENTS

GetDeviceHealth method
The health of an entire device can be indicated by theNE107 status. This value is usually calculated by thedevice from different states and parameter values
and exposed via communication protocol specificmechanisms. FDI allows an FDI Host to easily readthe value by executing the GetDeviceHealth method
independently of any protocol specifics for all device
instances available in the topology.

Extract existing complex UI or algorithms
Identify unique device selling points
Decide on UIPs and required UIP Platforms
Move features from EDD to UIPs (usability)
Introduce new features with UIPs

02

Use correct filename (naming convention)

03

Test the package with the device

Collect existing PDF documents (e.g. manuals)

Send to FieldComm Group for registration

Collect device pictures (different sizes)

Create FDI Package with all files (*.fdix )ATTACHMENTS

Create new PDF documents if required
Add mandatory Attachments (e.g. CFF, GSD)
EDD

UIP

ATTACHMENTS

000100100011
000100100011
000100100111

FDI Package

ONE device - ONE package - ALL tools

25

STEP 2: MIGRATE

How to migrate from existing FDT®/DTM™ to FDI?

Millions of devices currently installed worldwide are configured, operated and maintained by control systems andtools that support either the EDDL or FDT® standards. In order to protect the current investment into FDT®/DTM™
based solutions and to effectively extend their life-cycle a migration of those products to FDI Device Packages
should be considered. The FDI Package IDE fully supports this migration process.
UIPs for Workstations reuse Microsoft implementation technologies which are also used for DTM developments.
As a starting point, complex user interfaces and algorithms can be transferred into UIPs. This is also true for
special user interfaces underlining the device’s unique selling points. Even the reuse of existing Microsoft .NET
source code in UIPs is possible. The remaining parts of the DTM can simply be described by using EDDL which ismost likely already available for most of the device types.

EDD
000100100011
000100100011
000100100111

Identify existing complex UI or algorithms

UIP

With UIPs, the FDI Device Package is a perfect replacement for existing DTMs with improved interoperability,
reduced maintenance effort and all of the benefits of FDI.

Define aspects to be moved to EDD
Decide on UIPs and required UIP Platforms
Transfer features from DTM™ to UIPs

DTM

EDD

UIP

04

ATTACHMENTS

000100100011
000100100011
000100100111

EDD
000100100011
000100100011
000100100111

FDI Package

ATTACHMENTS

Create FDI Package with all files (*.fdix )Filename according to naming convention

Your benefits (examples):Reduced operating system dependency
The major part of an FDI Device Package consists of
the operating and platform independent descriptive
EDD. Special UIs and algorithms can be encapsulated
into UIPs which have a certain platform and operating
system dependency due to the implementation
technology used (e.g. Microsoft .NET). This reduced
number however already eases the life cycle
management for both, device manufacturers andusers.

26

Test the package with the device
Send to FieldComm Group for registration

Improved usability
EDDL has been extended over time with quite rich UI
capabilities, but standard paradigms like drag & drop,
multi media or other state of the art user interface
mechanisms are not supported. UIPs close this gap.
Powerful technologies like Microsoft .NET/WPF or
HTML5 can be used to create rich and usable userinterfaces for any operating system and platform.

ONE device - ONE package - ALL tools

EDD

UIP

Reuse existing EDDs if available
Add oﬄine configuration support (mandatory)
Create standard menus (mandatory)

Introduce new features with UIPs

Implement GetDeviceHealth (mandatory)

01
UIP

Create EDDs for DTM™ device types

Use Private attribute (OPC browse) (optional)
Tokenize to FDI Common Binary Format

02

03
Collect existing PDF documents (e.g. manuals)
ATTACHMENTS
Collect device pictures (different sizes)
Create new PDF documents if required
Add mandatory Attachments (e.g. CFF, GSD)ATTACHMENTS

000100100011
000100100011
000100100111

FDI Package

27

STEP 3: REGISTER

Register your FDI products = ensure interoperability

Registration steps

Access Support Portal

Testing and registration is key to interoperability. It ensures specific devices and systems conform to the same
standard. FieldComm Group is one of the only automation industry organizations with a registration program
requiring mandatory testing of critical elements of its technologies. Today, our testing and registration effort
encompasses FDI, FOUNDATION Fieldbus, and HART host systems and field devices, as well as physical layercomponents such as power supplies, cables, and device couplers. One of the founding principles of FieldComm
Group is the support of interoperability – the ability to operate multiple devices from multiple manufacturers, in thesame system, without loss of functionality.

LOGINŰ)QVQJVVRUWRRQTVƒGNFEQOOITQWRQTI
Ű.QIKPQTTGIKUVGTCPGYCEEQWPV
KE
TIC

T

Submit a TicketŰ$GIKP2TQFWEV4GIKUVTCVKQPD[UWDOKVVKPICVKEMGVEJQQUGū2TQFWEV4GIKUVTCVKQPŬHTQO
VJGCXCKNCDNGQRVKQPU

There are two levels of testing and registration within FieldComm Group:Ű4GEGKXGCPCWVQOCVGFKPUVTWEVKQPCNGOCKN

Reserve Test Slot

1. Field Level - testing of FDI and FDI-based H1 FOUNDATION Fieldbus and HART & WirelessHART devices
2. Integration Level - testing of FDI-based Host Profile Testing for FOUNDATION Fieldbus and HART-IP & Host
Testing for HART Protocol

Ű5WDOKVRC[OGPVKPHQTOCVKQP
5GG6GUVKPICPF4GIKUVTCVKQP(GGU
RQUVGFKPVJG2QTVCNŰ4GEGKXGCEQPƒTOGFUEJGFWNGFVGUVFCVGYKVJKPDWUKPGUUFC[USubmit Required MaterialsŰ5WDOKVTGSWKTGFTGIKUVTCVKQPFQEWOGPVCVKQPŰ5JKRJCTFYCTGVQCTTKXGYGGMURTKQTVQUEJGFWNGFVGUVFCVG

Testing
Testing fee applies

Ű/GODGTUJCXGXKUKDKNKV[VQVJGRTQEGUUVJTQWIJVJG5WRRQTV2QTVCNŰ+HCPKUUWGCTKUGUPQVKƒECVKQPKUUGPVVQVJGVKEMGVUWDOKVVGT

Products bearing the FOUNDATION Fieldbus, HART Product Registration and FDI symbols have undergone a seriesof rigorous tests administered by FieldComm Group. End users can select any registered product and be assured
that the product will provide a consistent level of functionality and interoperability regardless of the host systemor other devices used. Testing and registration enables a user to achieve the best return on their investment. FDIenabled products further ensure that products can be integrated in a consistent and familiar way across varying
systems, thus enabling enterprise-wide support and eﬃciency.

PASS
FAIL

FieldComm Group has test kits available for each level of testing so that manufacturers can ensure robust productofferings and strong pre-testing before submission for oﬃcial registration.
Hundreds of global companies are already supporting the above mentioned leading industry standards today! As
plants are built and modernized, they’re joining an ever growing digital workforce supporting smarter systems andsensors designed to help run plants more eﬃciently and safely. Smart instrumentation is the key to the digitaltransformation of industry and the Industrial Internet of Things, so don’t wait - take initiatives to transform yourinstrumentation and systems today!

Test ReportŰ6GUVTGUWNVUKUUWGFVQUWRRNKGTŰ2TQFWEVUOGGVKPICNNTGSWKTGOGPVUITCPVGFTGIKUVTCVKQP

Registered Product Packet
Ű/CPWHCEVWTGTTGEGKXGUC%GTVKƒECVG
4GRQTV4GIKUVGTGFNQIQ U CPFOC[
NCDGNRTQFWEVUCUQHƒEKCNN[ū4GIKUVGTGFŬ

Learn more about the FDI Product registration:
go.fieldcommgroup.org/productregistration

Ű0QPEQORNKCPVRTQFWEVUCTGTGVWTPGFCPF
KPXQKEGFHQTVGUVKPIUGTXKEGU0GYVKEMGVCPFHGGTGSWKTGFHQTTGVGUVProduct RegistryŰ2TQFWEVCFFGFVQVJGQHƒEKCN2TQFWEV4GIKUVT[

28

ONE device - ONE package - ALL tools

29Notes30

Notes

ONE device - ONE package - ALL tools

31

Attend an Event!

Get Trained!

FieldComm Group participates in many global seminars,

For organizations desiring to

exhibitions and user group events covering all our technologies

position themselves as leaders

and applications.

in their competitive field, theirpersonnel must be trained toWhether you are located in North or South America, Europe, Mid-take advantage of the latest

dle East, Africa or Asia, you can always find an event near you.

technology capabilities. Certified end user training is offeredat prestigious training facilities around the world to ensure

Visit fieldcommgroup.org/events to see where we will be next!

your staff are trained on the leading edge of the technologies.
Through this program, training facilities, curriculum, and instruc-

Become a Member!
Membership with FieldComm: Gain the Competitive Edge

tors are audited to ensure they meet stringent program requirements for vendor neutrality and up-to-date competency. Learn
more by visiting the Education section of fieldcommgroup.org.
FDI unifies device drivers, configuration
tools, diagnostics and documentation
regardless of operating system with anindependent and downloadable soft-

FieldComm Group offers a significant number of benefits
through membership. Whether you are a manufacturer,
systems integrator, educational institution, end user orother professional in the business, FieldComm Group helps
you gain the competitive edge through open interoperable
standards supporting the digital transformation of industry.
Learn more by visiting go.fieldcommgroup.org/membershipware package compatible with any FDI
registered host system.

FOUNDATION™ Fieldbus provides anall-digital infrastructure, with powerfulmultivariable measurement capabilities, robust device diagnostics, andthe ability to integrate wireless devices
across multiple networks.

With over 40 million supported field
FieldComm Group

instruments installed worldwide, HART

9430 Research Blvd., Ste 1-120

technology offers a reliable, long-

Austin, TX 78759 USA

term solution for leveraging benefits

info@fieldcommgroup.org • +1 512.792.2300

of intelligent devices through digitalfieldcommgroup.org

communication.

© 2017 FieldComm Group, Document Number: PS10200, Rev. 1.0

Global Communication Standards

JOIN US