Technology Update

Topics Covered

2

FOUNDATION fieldbusFDIHART

FOUNDATION FieldbusTECHNOLOGY UPDATE

Usability Initiatives

4

EDD Templates•Application defaults for offline configuration• Supplements system‐provided templates

Backward Compatibility•Automatic exchange of like device configuration without controller downloads

•Utilize existing configuration with newer device

Easy Connectivity•Utilize familiar 4‐20mA practices to connect fieldbus devices•Replace with an unlike device without controller downloads•Device interchangeability

Scalable Integration

Control Integration

Asset Integration

Process Variable Integration

No EDDs RequiredPV Device InterchangeabilityUnlike Device Replacement

EDDs for setup and maintenanceAutomated Like Device Replacement

Template‐based Commissioning

Control in the FieldAdvanced Applications

Template-based Commissioning

Project Data

(e.g. units)

HostProjectDatabase

User ApplicationTemplates

EDDTemplates

Simplified, Automated

Commissioning

EDD-based Templates

TB1TB2

AIAI

Template 2

Label Single Temperature

Help This template permits ….

Block Parameter Value

AI [1] L_TYPE Direct

AI [1] CHANNEL 1

TB1 CONFIG1 2

TB1 CONFIG2

… … …

Template 1

Label Single Temperature Measurement

Help This template permits ….

Block Parameter Value

AI [1] L_TYPE Direct

AI [1] CHANNEL 1

TB1 CONFIG1 2

TB2 CONFIG2 SINGLE

… … …

Device supplier provides a set of usable 

configuration parameters for different 

device applications

Just make it workSimplified engineeringSupports bulk data managementFDI Ready – EDD Templates are a key FDI feature

Future VisionOpen interface for exchanging user templates between multi-vendor systems

EDD-based Templates Key Facts

Backward Compatibility with Like Devices

No new files to install!

CommissionedManufacture: AcmeDevice Type: Pressure Device Revision: 1

Acme Pressure Rev 1

InstalledManufacture:  Acme Device Type:  PressureDevice Revision:  2Compatibility: 1

Automated Download

Configure Tag

No new EDD files to installNo offline configuration changes requiredSupports Automated Download

Set Tag with Handheld/Bench tool and attachImmediate access to PV and diagnosticsNew device features integrated as necessary

Like Device Replacement Key Facts

Standard Connection Points

Key enabler is distribution network configuration using known rules

Simplified PV Integration with ITK 7

1. Tag Instrument2. Configure Units3. Sensor configuration/valve auto-calibration4. Attach device to network

Instrument tagged by a handheld or integrated/bench host

Simplified interfaces / pre‐configuration

ITK 7 Devices are fully interoperable with current FOUNDATIONS hosts

Access fieldbus using familiar work practicesFocused on to AI/AO MAI/MAO (and discretes)Standard scaling and linearizationNo EDD files for PV accessFull sensor range (not just 4-20mA)No 4-20mA loop testsIntegrated data qualityIntegrated position feedbackSimpler host interfaces (cost, availability)

PV Integration Key Facts

FDITECHNOLOGY UPDATE

Connect to DataGET CONNECTED TO Intelligent device information

12

A Need for Improved InteroperabilitySuppliers with troubleDevices to be integrated for all tools

User with troubleNot all devices supported by his tool

13

Supplier1) ADevice Type A1Device Type An

Tool #2(EDDL based)

Tool #1(EDDL based)

Tool #4(FDT based)

Tool #3(FDT based)

1) Users request to support all tools  n device description for n tools for every device type2) Uses ONE tool for complete life cycle 

Supplier BDevice Type B1Device Type Bn

Supplier XDevice Type X1Device Type Xn

User 12)

User 22)

User 32)

User 42)

Partnering to Solve the Problem

14

FOUNDATIONS AND INDUSTRY PARTNERS COME TOGETHERFDT Group, Fieldbus Foundation, HART Communication Foundation, OPC Foundation and PROFIBUS InternationalContribution of Industry PartnersInvestment over past 5 years

The Solution: Introducing FDIField Device integration - ONE DEVICE. ONE PACKAGE. ALL Tools

15

Commissioning

Field Devices Automation System

Engineering

Operation

Maintenance

Consistent device visualization and parameterization across platformsApplication portability on any systemEnterprise connectivity with standard interfaces

Integrate with FDI

16

FDI – Benefits and Advantages for End Users

17

SIMPLIFIES WORKFLOWDevice package delivers accessDevice package provides documentation for product

REDUCES INTEGRATION EFFORTFDI support embedded in host systems and apsIndependent of Windows version

REDUCES FRUSTRATIONFDI packages are not programs needed to be installedUpgrade from existing DD to or DTM without device modificationHost independent FDI packages

FUTURE PROOFFDI brings field device to the Industrial Internet of Things

Ease of use for system 

administrators

Robustness

Migration and investment protection

Interoperability

Ease of use for users

FDI Now Available through FieldComm Group

Fdi device package ide and host components available nowo Single Device Package IDE Product across protocolso Delivering tools now for development by manufacturerso Comprehensive standardized host testing being put in place

HART and/or FF Hosts registered as compliant with FDI will be backward compatible with all registered DDs and FDI Device Packages

18

Integration Technology Detail

22

FDI – Field Device Integration

Blending the best of what you already use

40

The Device Package:The Heart of FDI

FDI Host

FDT/FDI Host

The best of EDDL

The best of FDT

FDT2

 Fram

e

EDDDevice 

DefinitionBusiness LogicUser 

Interface Description

UIPUser Interface 

Plug‐in,Device 

Applications(Optional)

AttachmentsManuals

CertificatesProtocol Specific

Files (GSD/ML/etc.)

FDI Device Package

AuthenticityIntegrity

FDI - One Package for All Systems From Any Vendor

Device and Device Package o Includes everything needed for the deviceo Common look and feel through style guideo Receive from device vendor or foundationso Easy to Use

24

Client-ServerStand-alone

Portable

FDI and Industrial Internet of Things (IIoT)

• Physical objects (with embedded microcontroller) exchange information with the “outside world” through the internet

• The objects, virtually represented in the internet are used to interact with software applications (services) or human users

• Objects or “things” are e.g.• Field devices (sensors, actors)• Drives, motors, valves, pumps• Controllers

25

IIoT

FDI brings Field Devices to the IIoT

Services, Applications,Algorithms

26

FDI Server Information Model

MES, CMMI, Engineering, ERP, …Data Collection, storage, analysis

…

Communication» OPCUA (IEC 62541)

Objects - “Things”» Real devices

FDI (IEC 62769)» Device Information Model

(OPCUA, IEC 62541-100)» Virtual device objects

Reference Architecture for IIoT

German industry Associations BITKOM, VDMA and ZVEI recommend a Reference Architecture Model for Industry 4.0 (RAMI)

Communication layer: OPCUAInformation layer: FDIFunctional layer: FDI

FDI integrates seamlessly into the Reference Architecture Model for Industry 4.0

27

FDI System IntegrationNATIVE FDI HOST IMPLEMENTATION

o Manages Device Packageso Manages and provides device datao Processes device specific user interfaces:

Mandatory, EDDL based UIDOptional, WPF based UIP

o Processes EDD Business Logic

Communicates with deviceso The use of common host components (UI

Engine, EDD Engine) ensures interoperability

28

FDI Host

FDI Client

FDI ServerInformation Model

EDD Engine**)

Communication Server

OPC‐UA Services

OPC‐UA ServicesFDI Device Package

EDDencoded  file

format

UIP(optional)

Attachments

Import

*) User Interfaces Device Applications**) Device Definition Business Logic Communication

UI Engine *)

FDI System integration

FDT based FDI Host

o Behaves as FDI host towards FDI Device Package

o FDI Frame Application processes FDI Packages in a “FDI DTM”

o FDI DTM uses Common Host Components

29

FDT2

  Frame Ap

plication

FDI DTM

FDI DTM UI

FDI DTM BLInformation Model

EDD Engine

Communication DTMs

FDI Device Package

EDDencoded  file

format

UIP(optional)

Attachments

Import

UI Engine 

FDI Cooperation - Mission Completed

o FDI specification releasedIEC 62769 publication pending

o FDI Integrated Development Environment released

Device vendors can develop FDI Packages

o FDI Common Host Components releasedSystem vendors can develop interoperable host systems

o First products have already been introduced to the market

o FieldComm Group and PNO will jointly maintain and further develop FDI

Technology transfer ongoing

30

FDI Package IDE

Development Test Certification/Registration

Package

EDD UIP

Package

EDD UIP

Package

EDD UIP

Device Package

Reference Runtime

Test Engine

Packaging

Tokenizin

g

Editing

HARTTECHNOLOGY UPDATE

HART Continuous Improvements – Get Connected

32

4-20 mA/HARTWirelessHARTHART-IP

HART Protocol Continues to Grow

33

High growth rate, even with huge volume is remarkable, even amazing!o Shipping millions of HART devices per year and still 4.7% growth !!!

Data for pending HART Common Tables Specification release:o > 420 Manufacturer ID Codeso > 1620 Device Types (includes unreleased products)

> 100 HART devices registration tests performed per yearo > 95 % HART 7

"2013 HART Installed Base 38.1 Million Devices" HART Field Devices Installed Base EstimateARC Advisory Group May 17, 2015

"A recent ARC study (2013 –2018) found that the compound annual growth rate of the market for pressure transmitters shows 4.7% for HART"Control Engineering Europe20 October 2015

HART 7.6 Release Pending

34

A business-as-usual updateo FSK Physical Layer Specification (v 9.1)

New - simplified specifications for "Maintenance Ports"o 2.4GHz DSSS O-QPSK Physical Layer Specification (v1.1)

Clarifications and Correctionso TDMA Data-Link Layer (v1.2)

Clarifications and Correctionso Command Summary Specification (v10.0)

More guidance on Device Caching, Command Aggregation) o Common Practice Command Specification (v11.0)

Clarifications on NAMUR Condensed Status implementationNew - Client Application Subscriptions (more on HART-IP later)

o Common Tables Specification (v24.0)More Unit Codes; Manufacturer IDs; Device Types

New HART Specification releases always backwards compatibleo HART always protects the installed baseo Existing HART 7 devices are good - not affected by Minor Releases

HART 7 is Released, Accepted, Growing

35

Today: Optimizing HART 7 o Clarifying and Improving

Helping developers make great productsImproving the Specifications

o Updating Test Specifications and Developer Tools

o Some new features can be expected

No New Major Protocol Revision PlannedGreat time to be making and buying HART 7 compliant products

Inventing

Protocol Life Cycle

Specifying

Optimizing

Introducing

CopyrightCopyright © 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, FOUNDATIONFieldbus 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.

36