Field device integration evolution in asset integration

Field Device Integration

Evolution in Asset Integration

2Field Device Integration

Introduction

History to Collaboration FDI Cooperation FDI Technology Conformity Assessment The Path Forward Questions

HISTORY TO COLLABORATION

The Fieldbus Wars

Mid 80’s until 1999

The Truce

IEC changes strategy from single to multiple fieldbus standard

Edition 1 (2003) 7 Communication Families 18 profiles

Edition 4 (est. 2013) 18 Communication Families 51 Profiles *

Foundation fieldbus

IEC 61158-1 Ed.1 (2003)

IEC 61784 Ed. 1 (2003)

ControlNet

PROFIBUS

WorldFIP

INTERBUS

SwiftNet

* Excludes real time Ethernet (61784-2) and functional safety (61784-3) profiles

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.

Device Integration Technology

Electronic Device

Description Language

(EDDL)

Field Device Tool

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

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

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

Device Integration StandardField 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

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

Device Integration War?

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

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

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

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.

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

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

FDI COOPERATION LLC

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

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+

FDI TECHNOLOGY

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

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

FDI Package

Collection of components that provide all the information necessary to integrate a type of device into a system

Device Package

•Most common•Typically, one package per device type•Multiple device types for modular devices (e.g. remote IO)

Profile Package

•Generic package for devices without a specific Device Package•Typically provided by Foundation

User Interface Plug-in (UIP) Package

•Provides one or more UIPs to an FDI Server independent of Device Package•Value add-ons•Common plugins for a device family

Communication Package

•Provide information to integrate an FDI Communication Server•Interface cards, gateways, etc.

FDI Device Package Standard

EDD(mandatory)

Electronic Device

Description Language

(EDDL)

Microsoft .NET/WPF

for Workstation

Platform

Device Definition (Parameters)

Business logic (Rules) User Interface (Structure)

User Interface Plugin Device Applications

Product Manuals Images Electronic Certifications Protocol specific Files

Integrity AuthenticityUIP

(optional)

UIP(optional)

Attachments

(optional)

Attachments

(optional)

Defined File Name Convention

e.g. acme.5930pressure.1.0.0.foundation_h1.fdix

Standardized Access to Device Information Model

Enables access to device information for MES Systems

FDI specifies rules to ensure that 3rd party applications cannot access sensitive parts of the information model

The FDI Server controls the access to device information

Generic OPC

UA Client

OPC UA Services

Communication Server

OPC UA Services

FDI Client

FDI Server

Information Model

EDD Engine

FDI Host

UID Renderer

UIP Hosting

Vendor B Vendor A

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

Simplify Deployment

Into the System

FDI Packages are imported, not installed

No Windows Installer No writing registries No installing DLL or

other windows libraries Intuitive file name

convention No more ‘0101.ffo’

Within the System

FDI Servers maintain device models

Servers push UIPs to clients on demand

Install once, use everywhere

All persistent data resides at the FDI server

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

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

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

FDI CONFORMITY ASSESSMENT

Common Device Tools

Development

Integrated Development Environment (IDE)

EDD UIP

Test EngineTo

gReference

HostUID Renderer

UIP Hosting

EDD Engine

Test Certification/Registration

Device Vendor

Device Package

EDD UIP

FDI Cooperation provides a cross protocol Integrated Development Environment!

Development and Test of Device Packages

Common Host Tools

FDI Cooperation provides protocol independent Standard Host Softwate Components

Host System manufacturers implement FDI Host Components for:

Device Management Tools Asset Management Tools DCS

OPC UA Services

Communication Server

OPC UA Services

FDI Client

FDI Server

Information Model

EDD Engine

FDI Host

UID Renderer

UIP Hosting

UID Render

EDD Engine

UIP Hostin

StandardFDI Host Components

Conformity Assessment

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

THE PATH FORWARD

Enhanced ScopeCommon Tools

Phase 1

Project

Phase 2

Project

FDI ProjectMaintenance

FDI CooperationLLC

’03 ’04 ’05 ’06 ’07 ’08 ’09 ’10 ’11 ’12 ‘13

Cooperation Timeline

FDI Demo Stations

ABB control system Communication

Protocols: FF, HART, PROFIBUS

Devices from various vendors

Use Cases: Parameterization/Configuration, Diagnosis, Status Monitoring according NE 107, Predictive Maintenance

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

Standardization Progress

2011 2012 2013 2014

New Work Item Proposal

New Work Approval

First Committee Draft

Committee Draft for Vote

Final Draft International Standard

International Standard

Second Committee Draft

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

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

QUESTIONS?

Field device integration evolution in asset integration

Technology

Choice Behavior, Asset Integration and Natural Reference Points

Locomotive asset management: integration of - WIT … asset management: integration of GPS, ... • proprietary communications protocols or single network provider ... Cognizant of

IBM FileNet and IBM Maximo Asset Management Integration

SOFTWARE ASSET MANAGEMENT Mobile Device ... ASSET MANAGEMENT Mobile Device Management SAM Engagement Kit B SAM Engagement Kit Table of Contents Introduction 1 Conducting a Mobile Device

External Device Integration with Mobile

Integration of Mechanical Information in Device ...urst.org/siteadmin/upload/5712U1015113.pdf · Integration of Mechanical Information in Device Descriptions ... Manual recording

Challenges of External Device Integration with Mobile

xPico Embedded Device Server Integration Guide - … · xPico® Embedded Device Server Integration Guide 3 ... The OEM integrator should be aware of ... SMT Embedded Device Server

Providing the Next Generation of Device Integration · DATASHEET wonderware.com/hmi-scada/device-integration | 2 Device Integration Servers Providing the Next Generation of Device

Cisco ISE Integration with Mobile Device Management

Medical Device Integration with an Ambulatory EMR

Commodity and Asset Pricing Models: An Integration

Asset Specificity and Vertical Integration: Williamson’s ... Files/09-119_11486f59-a32c-46e3-8544...Asset Speciﬁcity and Vertical Integration: Williamson’s Hypothesis Reconsidered

Partial Integration and Asset Specific Investmentjcavanau/cavanaugh2.pdfPartial Integration and Asset Specific Investment by ... 3 The costs of vertical integration ... buyer will

Entrust® Mobile Device Management (MDM) integration

XPort Pro Device Server Integration Guide

Medical Device Asset Tracking and Inventory Management7medical.com/wp-content/uploads/X-HIS_Med_Device_Asset_Mgt... · Medical Device Asset Tracking and Inventory Management ... Collect

DynaMix: Dynamic Mobile Device Integration for Efficient ... · DynaMix: Dynamic Mobile Device Integration for Efﬁcient Cross-device Resource Sharing Dongju Chae¶ Joonsung Kim†

Global Asset Management ﬁrm’s ESG Integration program

Data Integration Transportation Asset Management Colorado Case