Field Device Integration
Evolution in Asset Integration

Introduction
 History to Collaboration
 FDI Cooperation
 FDI Technology
 Conformity Assessment
 The Path Forward
 Questions
Field Device Integration
2 © 2012 by Fieldbus Foundation -- All Rights Reserved

HISTORY TO
COLLABORATION
Field Device Integration
3 © 2012 by Fieldbus Foundation -- All Rights Reserved

The Fieldbus Wars
Mid 80’s until 1999
Field Device Integration
4 © 2012 by Fieldbus Foundation -- All Rights Reserved

The Truce
IEC changes strategy from
IEC 61158-1 Ed.1 (2003)
single to multiple IEC 61784 Ed. 1 (2003)
fieldbus standard
Foundation
fieldbus
ControlNet
Edition 1 (2003)
PROFIBUS
 7 Communication Families
 18 profiles P-NET
WorldFIP
Edition 4 (est. 2013) INTERBUS
 18 Communication Families SwiftNet
 51 Profiles *
* Excludes real time Ethernet (61784-2) and functional safety (61784-3) profiles
Field Device Integration
5 © 2012 by Fieldbus Foundation -- All Rights Reserved

Standards
The wonderful thing about
standards is that there are so
many of them to choose from.
- Grace Hopper *
* Typically attributed, but there is some dispute on the actual author.
Field Device Integration
6 © 2012 by Fieldbus Foundation -- All Rights Reserved

Device Integration Technology
Electronic Device
Field Device Tool
Description Language
(FDT)
(EDDL)
Field Device Integration
7 © 2012 by Fieldbus Foundation -- All Rights Reserved

Electronic Device Description Language
(EDDL)
 The “E” is for Electronic, not Enhanced
 Some technologies use the term Device Description
Language (DDL)
 Adopted for HART in 1992
 Adopted for Foundation Fieldbus in 1994
 Adopted for Profibus in 2000
 International Standard as IEC 61804-2 since 2004
 EDDL collectively maintained through IEC by
Fieldbus Foundation, HART Communication
Foundation and Profibus Organization
Field Device Integration
8 © 2012 by Fieldbus Foundation -- All Rights Reserved

EDDL Characteristics
 Communication Network Independent (with dialects)
 Platform Independent
 OS Independent
 Interpreted -- No machine level execution
 Parameter definitions and attributes
 Label, Help, Units, Handing
 Procedure through method calls (interpreted)
 Visualizations through menus
 Common look and feel with host
 EDDL developer influences presentation
Field Device Integration
9 © 2012 by Fieldbus Foundation -- All Rights Reserved

EDDL Cooperation Team
Formed in 2003 via Memorandum of Understanding
 Fieldbus Foundation
 HART Communication Foundation
 Profibus Organization
Phase 1 (2003)
 Extended visualization
 Persistent Data Storage
Phase 2 (2004)
 Added OPC Foundation
 Support for more complex devices
 Map EDDL to OPC UA Information Model
Field Device Integration
10 © 2012 by Fieldbus Foundation -- All Rights Reserved

Device Integration Standard
Field Device Tool (FDT)
 Association in 2003 between ABB, Endress+Hauser,
Invensys, Metso, and Siemens
 Became FDT Group in 2005
 Profiles for several communication networks
including HART, PROFIBUS, FOUNDATION Fieldbus,
DeviceNet, Interbus, AS-Interface, PROFINET IO
 International Standard as IEC 62453 since 2009
 FDT maintained through IEC by FDT Group
source: http://www.fdtgroup.org Field Device Integration
11 © 2012 by Fieldbus Foundation -- All Rights Reserved

FDT Characteristics
 Communication Network Independent
 Platform Independent
 Based on COM/ActiveX (FDT 1.x), .NET (FDT 2.x)
 DTM as the device driver (application plug-in)
 DTM executes within an FDT Frame application
 CommDTM for communication drivers (cards,
gateways)
 Strong visualization and business logic capabilities
 DTM developer controls the presentation
Field Device Integration
12 © 2012 by Fieldbus Foundation -- All Rights Reserved

Device Integration War?
Field Device Integration
13 © 2012 by Fieldbus Foundation -- All Rights Reserved

Complementary or Competing?
Both, but the question misses the point
End Users are frustrated
 Want the best of both worlds
 Limited choice of products based on vendors alignment
Device suppliers are frustrated
 Spending money on duplicated efforts
 Host specific implementations
System Suppliers are frustrated
 Protect the integrity of the process automation system
 Provide consistent user experiences
Field Device Integration
14 © 2012 by Fieldbus Foundation -- All Rights Reserved

The itm whitepaper
 Harmonize EDDL and
FDT Approaches
 Client / Server Model
 Using OPC UA
 Decouples device
information model
(DIM) and the device
object model (DOM)
 Becomes the basis of
the FDI Project
 Future becomes Field
Field Device Integration
15 © 2012 by Fieldbus Foundation -- All Rights Reserved

FDI Project Announcement
 Announced 2007 at
Interkama/Hannover
 FDT Group joins the
EDDL Cooperation Team
 Increase scope to create
unified solution based on
concepts from itm white
paper
Field Device Integration
16 © 2012 by Fieldbus Foundation -- All Rights Reserved

Why Field Device Integration?
Process automation end users are asking for a single
solution
 Current FDT and EDDL technologies with partial overlap cause
competitive positioning
 Current situation is confusing because of conflicting messages
Suppliers face expensive development
 Most suppliers are simultaneously part of ECT organization and
FDT.
 They must invest in parallel developments for EDDT and FDT.
Field Device Integration
17 © 2012 by Fieldbus Foundation -- All Rights Reserved

Lifecycle Driven Architecture
Input from AIDA, NAMUR, WIB and PNO on use case
development
Use cases based on plant life-cycle model
Requirements derived from use cases
System architecture derived from requirements
Field Device Integration
18 © 2012 by Fieldbus Foundation -- All Rights Reserved

FDI Project Extended Scope
Public commitment from
several key suppliers (2010)
Extended Scope
 Common Validation Effort
 FDI/FDT 2.0 Interoperability
 Common Tools
– Device Package Development
Tools (IDE)
– Host Interpreters
– Package Conformance Tools
– Host Conformance Tools
 EDDL Profile Harmonization and
Extensions
 Common EDDL File Format
Field Device Integration
19 © 2012 by Fieldbus Foundation -- All Rights Reserved

FDI COOPERATION LLC
Field Device Integration
20 © 2012 by Fieldbus Foundation -- All Rights Reserved

FDI Cooperation LLC
 Founded Sept 2011
 Not for Profit Limited
Liability Cooperation (US)
 Joint ownership by 5 ECT
Foundations
 Three year limited lifetime
 Replaces ECT
 Finish FDI as IEC standard
 Facilitate development of
common software tools
 Promotion
 Marketing
Field Device Integration
21 © 2012 by Fieldbus Foundation -- All Rights Reserved

FDI Cooperation Principles
 Features based on Use Cases and Requirements
 Harmonized EDDL
 Host System Independent
 Support FOUNDATION fieldbus, HART, PROFIBUS
and PROFINET
 Open to other industrial networks
 Support Nested communications through
heterogeneous networks
 Support Information exchange between FDI Host and
generic OPC UA Client
 FDI Packages must be compatible with FDT 2.0+
Field Device Integration
22 © 2012 by Fieldbus Foundation -- All Rights Reserved

FDI TECHNOLOGY
Field Device Integration
23 © 2012 by Fieldbus Foundation -- All Rights Reserved

FDI Features
 A unified device integration standard
 Built on knowledge gained from EDDL and FDT
 Uses OPC UA object model concepts
 Platform, Protocol Independent
 Technology Independent
 Supports scalable clients, from simple handhelds to
full asset management applications
 Scales appropriate to the device supplier needs
 Backward compatible
 Lifecycle concept
Field Device Integration
24 © 2012 by Fieldbus Foundation -- All Rights Reserved

New Terminology
FDI Package
 The file for device integration
 Based Open Packaging Conventions (IEC 29500)
User Interface Plug-in (UIP)
 executable plug-in
 Can support multiple platforms and technologies
 While it shares similarities, a UIP is not a DTM
User Interface Description (UID)
 Graphic visualization of device parameters
 Implemented as EDDL Menus and Methods
Field Device Integration
25 © 2012 by Fieldbus Foundation -- All Rights Reserved

FDI Package
Collection of components that provide all the
information necessary to integrate a type of
device into a system
User Interface
Communication
Device Package Profile Package Plug-in (UIP)
Package
Package
• Most common • Generic package • Provides one or • Provide
• Typically, one for devices more UIPs to an information to
package per without a specific FDI Server integrate an FDI
device type Device Package independent of Communication
• Multiple device • Typically Device Package Server
types for provided by • Value add-ons • Interface cards,
modular devices Foundation • Common plugins gateways, etc.
(e.g. remote IO) for a device
family
Field Device Integration
26 © 2012 by Fieldbus Foundation -- All Rights Reserved

FDI Device Package Standard
 Product Manuals
 Images
 Device Definition  Electronic Certifications
(Parameters)  User Interface Plugin
 Protocol specific Files
 Business logic (Rules)  Device Applications
(CFF)
 User Interface (Structure)
 Integrity
EDD UIP Attachments  Authenticity
(mandatory)
UIP
(optional)
Attachments
(optional)
(optional) (optional)
Microsoft .NET/WPF
Electronic Device
for Workstation
Description Language
Platform
(EDDL) Defined File Name Convention
e.g. acme.5930pressure.1.0.0.foundation_h1.fdix
Field Device Integration
27 © 2012 by Fieldbus Foundation -- All Rights Reserved

Standardized Access to
Device Information Model
 Enables access to
Vendor B Vendor A
device information for FDI Host
MES Systems Generic OPC
FDI Client
UA Client
 FDI specifies rules to
ensure that 3rd party
applications cannot OPC UA Services
FDI Server
access sensitive parts
of the information
model
 The FDI Server
controls the access to OPC UA Services
device information Communication Server
Field Device Integration
28 © 2012 by Fieldbus Foundation -- All Rights Reserved

Backward Compatibility
Critical End User Requirement
Foundation Fieldbus
 Full support to existing DD Library (DD4, DD5)
HART
 Full support of existing DD Library (FMS, FM6, FM8)
PROFIBUS
 Legacy EDDs were DDL Source
 Backward compatibility through new Tokenizer tool
Native FDT 2 based system can support FDI Packages
Native FDI Systems support EDDL
Native FDI Systems do not support DTMs
Field Device Integration
29 © 2012 by Fieldbus Foundation -- All Rights Reserved

Simplify Deployment
Into the System Within the System
 FDI Packages are  FDI Servers maintain
imported, not installed device models
 No Windows Installer  Servers push UIPs to
 No writing registries clients on demand
 No installing DLL or  Install once, use
other windows libraries everywhere
 Intuitive file name  All persistent data
convention resides at the FDI
 No more „0101.ffo‟
server
Field Device Integration
30 © 2012 by Fieldbus Foundation -- All Rights Reserved

Integrity and Authenticity
FDI Package is signed using x509 digital certificates
Industry standard for security
Integrity
 Verify the package has not been manipulated
Authenticity
 Verify the package developer
Field Device Integration
31 © 2012 by Fieldbus Foundation -- All Rights Reserved

Lifecycle Management
Standardized versioning concept
 <major.minor.revision>-build
Package versions
 update (patches)
 upgrades (new device versions)
Technology Versions
 managing future technology changes
 forward thinking, future proof
Field Device Integration
32 © 2012 by Fieldbus Foundation -- All Rights Reserved

User Requirements Namur NE105
 Investment Safety
 Version Conflicts
 Device Integration with Tools
 User Guidance
 Display of Devices
 Standard Profiles
 Device Descriptions
 Licensing of Device Descriptions
 Cross-Platform Compatibility
 Full Support of Device Functionality
 Standardized Data filing
 Certification
Field Device Integration
33 © 2012 by Fieldbus Foundation -- All Rights Reserved

FDI CONFORMITY
ASSESSMENT
Field Device Integration
34 © 2012 by Fieldbus Foundation -- All Rights Reserved

Common Device Tools
Development and Test of Device Packages
FDI Cooperation provides a cross protocol
Integrated Development Environment!
UIP
Device Package
Test Engine
Tokenizing
Packaging
Editing
EDD UIP
EDD UIP
EDD UIP
Device Vendor
Integrated Development Environment (IDE)
Development Test Certification/Registration
Field Device Integration
35 © 2012 by Fieldbus Foundation -- All Rights Reserved

Common Host Tools
FDI Cooperation provides protocol independent FDI Host
Standard Host Softwate Components FDI Client
Standard
FDI Host Components
OPC UA Services
FDI Server
OPC UA Services
Host System manufacturers implement FDI Host Communication Server
Components for:
 Device Management Tools
 Asset Management Tools
 DCS
Field Device Integration
36 © 2012 by Fieldbus Foundation -- All Rights Reserved

Conformity Assessment
Field Device Integration
37 © 2012 by Fieldbus Foundation -- All Rights Reserved

Registration/Certification
 Registration/Certification will be performed by
technology foundations
 Based on jointly developed common test tools
 No independent FDI Certification certificate
 Supplements existing registrations processes
Field Device Integration
38 © 2012 by Fieldbus Foundation -- All Rights Reserved

THE PATH FORWARD
Field Device Integration
39 © 2012 by Fieldbus Foundation -- All Rights Reserved

Cooperation Timeline
’03 ’04 ’05 ’06 ’07 ’08 ’09 ’10 ’11 ’12 ‘13
Phase 1 Phase 2 Maintenance FDI Project Enhanced Scope FDI Cooperation
Project Project Team
Common Tools LLC
Field Device Integration
40 © 2012 by Fieldbus Foundation -- All Rights Reserved

FDI Demo Stations
 ABB control system
 Communication
Protocols: FF, HART,
PROFIBUS
 Devices from various
vendors
 Use Cases:
Parameterization/Confi
guration, Diagnosis,
Status Monitoring
according NE 107,
Predictive Maintenance
Field Device Integration
41 © 2012 by Fieldbus Foundation -- All Rights Reserved

Active Tools Development
 Tools in development since 2011
 First Device IDE release set for mid-2013
 Specification 1.0 release set for mid-2013
 Device developers can get involved today
 Prototype tools available
 Interoperability workshops planned
 Get ahead of the development curve
Field Device Integration
42 © 2012 by Fieldbus Foundation -- All Rights Reserved

Standardization Progress
New Work Item Proposal
New Work Approval
First Committee Draft
Second Committee Draft
Committee Draft for Vote
Final Draft
International Standard
International
Standard
2011 2012 2013 2014
Field Device Integration
43 © 2012 by Fieldbus Foundation -- All Rights Reserved

Summary
 A real, unified device integration standard
 “Foundations” cooperate in FDI Cooperation to
complete and promote FDI Technology
 Process automation vendors engaged in FDI
development
 IEC Standardization has been initiated
 Interoperability is built into the specification
 Established lifecycle concept
 FDI fulfills NAMUR NE105 requirements
Field Device Integration
44 © 2012 by Fieldbus Foundation -- All Rights Reserved

Where To Get More Information
FDI Cooperation
 Website: www.fdi-cooperation.com
 Whitepaper:
www.fdi-cooperation.com/index.php/technology.html
Fieldbus Foundation
 Website: fieldbus.org
 Email: info@fieldbus.org
 User Forums: forums.fieldbus.org
 Blog: foundationfieldbus.blogspot.com
 Twitter: twitter.com/FOUNDATIONField
 LinkedIn: linkedin.com/company/fieldbus-foundation
 LinkedIn Discussion Group: Fieldbus Foundation
 YouTube: youtube.com/user/FieldbusFoundation
Field Device Integration
45 © 2012 by Fieldbus Foundation -- All Rights Reserved

QUESTIONS?
Field Device Integration
46 © 2012 by Fieldbus Foundation -- All Rights Reserved