Presented by Emerson's Jonas Berge at the 2012 Emerson Exchange conference in Anaheim, California USA.

1. Device Revisions
Management Best Practices -
Is DD the problem or the
solution?
Jonas Berge, Director, Applied
Technology
Emerson Process Management
1

2. Photography & Video Recording Policy
Photography and audio/video recording is not permitted in any
sessions or in the exhibition areas without press credentials or
written permission from the Emerson Exchange Board of Directors.
Inquiries should be directed to:
EmersonExchange@Emerson.com
Thank you.
2

3. Presenters
Jonas Berge
3

4. Introduction
Keeping the system up to date with new types and
versions of devices is a challenge in most plants
– 4-20 mA/HART
– WirelessHART
– FOUNDATION fieldbus
– PROFIBUS
The role of Device Description (DD) files in interoperability
and compatibility often misunderstood
– How to manage DD in projects
– How to keep the system up to date with intelligent devices
Relevant to:
– Users of Emerson devices on Emerson systems
– Emerson devices on third-party systems
– Third-party devices on Emerson systems benefit alike
4

5. Topics Covered
Device Integration and Compatibility
Basics
Versioning and File Names
Troubleshooting
System Files
Poor Hosts
Project Execution Considerations
Plant Operations & Maintenance
Training for Competency
5

6. Device Integration and
Compatibility
Devices get better and better,
how does the system keep up?
6

7. Intelligent Digital Devices Require
Software Integration
Eight-channel two-wire
temperature transmitter Intelligent two-wire on/off valve
Electric actuators / Motor
Intrinsically safe intelligent two- Operated Valve (MOV)
wire inventory tank gauging
system
Fully integrated gas
chromatograph
7

8. Plant Challenge: Device Revisions
It is not a problem with DD file, it is a DEVICE “problem”:
– Manufacturers constantly release new revisions of devices with
new features
4-20 mA (HART), FOUNDATION fieldbus, PROFIBUS,
and WirelessHART devices periodically have new
versions
4-20 mA devices use HART for configuration and
calibration
– Therefore device revision is a challenge for 4-20 mA devices too
Ver 1 Ver 2 Ver 3 Ver 4
8

9. Solution: The IEC 61804-3 (EDDL) Device
Integration Technology
The EDDL file is in the computer
There is no EDDL in the device
– There is no such thing as an “EDDL device” or “non-EDDL device”
The EDDL file describes the device so the computer
knows how to talk to the device
– EDDL is a device integration technology
All systems use the same EDDL file for the device
There is no need to upgrade the system software version
to match the device version
9

10. Backwards and Forwards Compatibility
Provided by EDDL
Backwards compatible:
– Thanks to EDDL, new software and handhelds work with old
devices
Forward compatible:
– Thanks to EDDL, software and handhelds will work with future
devices without software upgrade
Pre-loaded EDDL files for old devices Load EDDL files for new devices in the future
New
System
Rev 1 Rev 2 Rev 3 Rev 4
Old Future
Backwards Compatibility Forward Compatibility
Devices Devices
10

11. How EDDL Works
The EDDL file is made by the device manufacturer
The EDDL file lets the system know the features of
each device
EDDL file
EDDL files keep the system up to date with new
DEV_REV devices
=1
New system and handhelds have EDDL files pre-
DEV_REV loaded
=2 Load EDDL files for new devices in the future
DEV_REV
Any system or handheld works with any device type
=3 All devices can be managed from the same software
EDDL file
•Transmit
•Receive
•Display
11

12. Same Technology, Same Procedures
Keep systems up to date and compatible with new
devices by loading the DD file for the device onto system
EDDL works the same way for HART, WirelessHART,
FOUNDATION fieldbus, and PROFIBUS
– Know one, and you know them all
4-20 mA devices use HART for configuration and
calibration; need EDDL to be commissioned
12

13. New Skills Required
EDDL files are downloaded from the Internet and loaded
on the system
– In 1996 this was totally new
In the past, people in general were not as used to using
software, downloading files from the Internet, and
synchronizing with devices
– Everyday MP3 players, digital cameras, smart phones, and tablets
have now changed this
Software, downloading files, and synchronizing with smart
devices is becoming second nature
13

14. Device Revision Management
Basics
In a nutshell...
14

15. Device Revision Management is Simple
If a new revision of a device is received, obtain the EDDL
file for that device revision and load on the system
For instance, if a revision 7 device arrives in the plant, get
a DD file for device revision 7
That is all you need to know
– The rest of this workshop is just details
15

16. Common Misunderstanding
Wrong Right
“What is the DD revision “What is the device
of the device?” revision of the device”
– This is not right because the “What device revision is
device does not know about this DD file used for?”
DD files
– The DD is not inside the
device
16

17. System and Handheld Update
Download EDDL file:
– Device manufacturer site
– Bus organization (HCF, FF, PI) site
– System supplier site
• Together with system files
– Automatic update
Small
– Via email even on low bandwidth connection
Copy and paste
– Document, not software
– Add device wizard
17

18. 475 Easy Update
The field communicator is ahead in usability
Utility software updates communicator with its device
support files
– No search for files on multiple websites
Makes 4-20 mA/HART devices easy to use
– Systems that don’t use HART don't need EDDL files
18

19. Guardian Automatic System Update
- DeltaV/AMS v12
DeltaV and AMS Device Manager automatically
download new DD files from the Guardian server
The system is automatically kept up to date, ready
for new device types and versions as they come to
the plant
– No need to search for files
Upgrade to DeltaV/AMS v12
Manual File
Transfer or
Network
Connection
19

20. EDDL Files for All Devices Managed The
Same Way
EDDL files are loaded the same way for 4-20 mA (HART)
and Fieldbus devices
EDDL File
4-20 mA (HART Device)
Fieldbus Device
HART
Fieldbus
System is kept up to date with HART, FOUNDATION
fieldbus, PROFIBUS, and WirelessHART devices the
same way
4-20 mA devices use HART and therefore need EDDL file
to be loaded
20

21. Versioning and File Names
Keeping the system evergreen
21

22. The Problem:
- Device Versions Get Better
A new revision device has new features
– New function blocks
– New parameters (setup, diagnostics, monitoring)
– New options (units, sensor types, etc.)
The system must know the features of every revision of
every device
Device (HART, FF, PROFIBUS, WirelessHART)
DEV_REV = 1 TB AI
Plugged Impulse Line
DEV_REV = 2 TB AI PID
Auto Tuning
Mass
DEV_REV = 3 TB AI PID
Flow
mmH2O @ 4 degC
22

23. Version Management (for Device)
Problem: A new revision Solution: Therefore a new
device has new features EDDL file is required to
– New function describe those new device
– New diagnostics features
– New options – Old files are not removed
Device (HART, FF, PROFIBUS, WirelessHART) EDDL file
DEV_REV = 1 Corresponds To: DEV_REV = 1
DEV_REV = 2 Corresponds To: DEV_REV = 2
DEV_REV = 3 Corresponds To: DEV_REV = 3
23

24. Version Management (for EDDL file)
New EDDL released even if there is no change in device
revision
– For example to improve the EDDL file
• Easier to use wizards
• More intuitive menus
• Better graphics
• Conditionals
• Clearer help text
When there is a new DD file for the same device revision,
this is when we get a new “DD revision”
Device (HART, FF, PROFIBUS, WirelessHART) EDDL File
DEV_REV = 1 DEV_REV = 1
DEV_REV Works With DD_REV = 1 DD_REV = 2
=1 0101.sym 0102.sym
DEV_REV = 2
DEV_REV Works With DD_REV = 1
=2 0201.sym
24

25. Recap: DD Revision is Different from
Device Revision
Device Revision DD Revision
Version of the device Version of the user
Incremented when interface, the file itself
firmware is improved with Incremented when the
new features user interface is improved
– New blocks with new features
– New features – Better graphics
– New diagnostics – Smarter wizards
– More helpful conditionals
– More intuitive menus
(HART, FF, PROFIBUS, WirelessHART)
25

26. Device Revision is What Matters
The Device Revision for the EDDL file must match the
device revision of the actual device
– Otherwise the system cannot work with the new device
This applies to 4-20 mA (with HART), FOUNDATION
fieldbus, PROFIBUS, and WirelessHART alike
The system does not care much about the DD revision of
the device
– The system usually picks the latest available DD file for the device
26

27. Understanding EDDL File Names
The DD file names consist of:
– Device revision
– DD file revision
Hexadecimal
Old files not removed when new files are loaded
The system automatically picks the correct EDDL file for
the device to be displayed
0701.sym 1703.sym
07 = Device Revision 7 17 = Device Revision 23 (17 in hexadecimal is 23 in decimal)
01 = DD File Revision 1 03 = DD File Revision 3
27

28. Device Library and Add Device Wizard
Lists all supported device
types and revisions
– That is, all the EDDL files
loaded on the system
Plain text model numbers
and descriptions
Organized by manufacturer
and protocol
28

29. Plug-‘n’-Play
System automatically picks
the correct EDDL file
– No manual configuration
(HART, FF, PROFIBUS, WirelessHART)
•Manufacturer ID
READ •Device Type
•Device Revision
29

30. Poor Host
Early days of DD
30

31. DD/EDDL Support in Systems
All systems support DD
In the past, not all systems supported wizards (methods)
and conditionals
– Some systems required “simplified” DD to work
Enhanced menus and graphics was not introduced until
2006
– Compliant systems must now implement full support
EDDL
Device Business User Interface
Definition Logic Description
•Blocks •Wizards •Menus
•Parameters •Conditionals •Graphics
31

32. Modified CFF
Most systems just ignore unsupported features in the CFF
file
– Can use CFF from the device supplier as-is
Some systems reject CFF file with unsupported content
– System manufacturer edits the CFF file to make the system accept
it
– The original CFF file from the device manufacturer does not work
32

33. System Files
Host System Interoperability
33

34. Device Files vs. System Files
Device Files System Files
Standard Non-standard
– IEC 61804-3 – Unique to each system
– Used by all systems Created by system
Created by device manufacturer
manufacturer Other files
This is the DD files Support system
Supports device functionality
functionality – System graphics (before
Download from bus EDDL)
organization site or device – Alarm management
– Default settings
manufacturer site – etc.
Download from system
manufacturer site
– May also include DD as a
single package
34

35. Downloading Device Files from The
Internet
Device Files:
www.fieldbus.org
System Files:
deltav.com
Field Communicator Files:
fieldcommunicator.com
35

36. Downloading System Files From the
Internet
36

37. Project Execution
Considerations
37

38. System Implementation
Protocol` Manufacturer Model Description Device
Revision
HART Yokogawa YTA320 Temperature 3
HART Metso VG800 Valve Guard 6
FF CSI 9210 Machinery Health 3
Transmitter
FF Rotork FF01 Mk2 Electric Actuator 2
WirelessHART Rosemount 3051S Pressure 1
WirelessHART Siemens TF280 Temperature 1
PROFIBUS-DP Siemens MM440 Drive 2
Confirm device revision to be used
Create checklist of all device types for all protocols:
– 4-20 mA (HART), Fieldbus, Profibus, WirelessHART
Load DD for all devices: used and unused
– Unexpected devices may show up at site
38

39. Integration and Factory Acceptance Test
(FAT)
Interoperability test one device of each type for all
protocols
– Will reveal if DD or system files for device are missing
Minimize surprises at site
39

40. Commissioning
A system or handheld needs the correct DD
and system files to be loaded in order for it to
configure and calibrate a device before
commissioning
– This applies to 4-20 mA (HART), Fieldbus, Profibus,
and WirelessHART
The system will prompt if DD or system file for
the device is missing
The system will prompt if configured device
revision is different from actual device
40

41. Plant Operations &
Maintenance
41

42. Device Replacement
Make sure DD and system files for the new device is
loaded
– Needed for configuration and calibration before commissioning
– This applies to 4-20 mA (HART), Fieldbus, Profibus, and
WirelessHART
There is no need to remove the old DD files
(HART, FF, PROFIBUS, WirelessHART)
02xx
DEV_REV = 2
DEV_REV = 1
42

43. Training for Competency
EDDL is where systems and devices meet System
Training is a critical success factor for any
project
– EDDL must be part of the training
Customized for role:
– Instrument technicians
– System administrators EDDL
Customized for the systems and portables
used
Devices
43

44. Device Revision
Troubleshooting
EDDL files do not fail
44

45. DD File Missing
The system or handheld field communicator will prompt if
a DD file is missing
The prompt will specify which DD file the system or
handheld needs
Without the DD the 4-20 mA (HART), Fieldbus, Profibus,
or WirelessHART device cannot be configured and
calibrated before commissioning
Use semi-automated field communicator DD file update
software
45

46. Proprietary System File Missing
The system will prompt if the proprietary system file such
as a “template” is missing
Newer systems don’t have this problem
– Upgrade to a version which automatically generate templates and
other proprietary files
46

47. Unable to Interpret CFF
The system will prompt if it is unable to interpret the CFF
file
Obtain modified CFF from system supplier
Newer systems don’t have this problem
– Upgrade to a version which has passed HPR
47

48. Device Revision Mismatch
This error appears when Device Revision for the tag place
holder created in the system database is different from the
Device Revision of the actual device connected
A device with device revision 02 requires:
– a DD file for Device Revision 02xx
– A system database tag place holder created for a device with
Device Revision 2
A 4-20 mA controller does not care about device revision
but handheld and configuration software do
Use automated system DD file update
DEV_REV = 2
DEV_REV = 3
48

49. Device Not Detected
EDDL files are not required to detect the presence of a
device
– If a device is not detected, it is not a problem with EDDL
A gateway can join a WirelessHART device to the network
without using EDDL
– Provided the network ID and join key have been set
– If device refuse to join, it is not because of EDDL file
– Software or a handheld field communicator requires DD files in
order to configure the network ID, join key, and update period in
the device before it can be detected by the gateway
49

50. Solution and Results
50

51. Solution
Incorporate device revision management as part of the
project training program
Upgrade existing systems to latest version to benefit from
improved device revision handling
Manage DD files during project execution
Invest in automated system DD file updates
Use the device revision management life-cycle application
guide
51

52. Business Results Achieved
Project-phase device commissioning delays due to device
revision issues can be reduced once system engineers
understand device revision management
– Ensuring on-time plant startup
• Avoiding project delay penalties
Less operational-phase device replacement down-time
can be achieved once instrument technicians and system
administrators understand device revision management
– Greater availability
The full features and diagnostics of devices can be
accessed once systems are kept up to date
– Optimal operation and lower maintenance cost
52

53. Summary
Device revisions are the “problem”, DD is the solution
Device revision affect all protocols
Study revision management further
Exercise device revision management
– Project execution
– System administration
Automate device revision management
Reduce project delays (commissioning)
Greater availability (device replacement)
!
Comments
?
Questions
53

54. Where To Get More Information
‘Device Revision and Lifecycle Management Guide’ can
be found on the EDDL Intelligent Device Management
(IDM) microsite:
– www.eddl.org
– FREE download
54