The New Generation of FOUNDATION Fieldbus Solutions

Transcription

1 The New Generation of FOUNDATION Fieldbus Solutions

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: Thank you.

3 Panel - Introduction John Rezabek (Process Control Specialist) Alan Dewey (Product Marketing Manager) Jonas Berge (Director of Applied Technology) Rong Gul (Subject Matter Expert) Marcos Peluso (Distinguished Technologist) Klaus Erni (DeltaV Hardware Product Marketing Manager)

4 Discussion Format Identify past customer pain points with FOUNDATION fieldbus Describe recent enhancements to FOUNDATON technology addressing pain points Provide examples of technology implementation Q & A from attendees

5 John Rezabek PROCESS CONTROL SPECIALIST

6 About the Presenter Employment: 23 years 9 years

7 Past Pain Point - Control in the Field Some Host Systems do not support Control in the Field in my Devices Using Control in the Field with FOUNDATION fieldbus limits the number of devices I can put on a segment

8 FF Host Registration Helps Its predecessor, the HIST test, didn t help users discern host capabilities. Host Registration requires that specific capabilities are demonstrated to obtain a checkmark Currently integrated hosts (e.g., DeltaV and Ovation) exist that are certified to two levels, 61a and 61b Not all capabilities are mandatory, but end users can specify the capabilities they require. Both 61a and 61b support CIF (mandatory)

9 Host Profile Testing and ITK Testing

10 Role-Dependent Host Classes

11 Registered Hosts can be searched on web Fieldbus.org > End User Resources > Registered Products > Search Hosts

12 Host Capabilities In Detail 61a Host 61b Host

13 In Days of Yore: A lot of people did control in the host fieldbus was not exploited for its control capabilities H1 cards of 1999 had VCR limitations Function blocks especially PID solved in valves were not especially fast

14 Faster Function Blocks = More Loops per Segment Current Emerson offerings have industry-leading FB execution times 25 millisecond PID 120 millisecond PID 20 millisecond AO 50 millisecond AO

15 Klaus Erni DELTAV HARDWARE PRODUCT MARKETING MANAGER

16 Fieldbus Diagnostics Past Pain Point Fieldbus diagnostics among different types of devices are inconsistent Fieldbus diagnostics flood the operator with too much information

17 Fieldbus Diagnostics Past Pain Point Fieldbus Device specific Diagnostic Properties used so far : Inconsistent!

18 Fieldbus Diagnostics Past Pain Point latest Fieldbus Device specific Diagnostic Properties :

19 Fieldbus Diagnostics Past Pain Point Harmonizing the so far existing Diagnostic Properties: NE 107 Spec. =

20 DeltaV V12.3 provides Harmonized Device Alerts Support for FOUNDATION fieldbus Diagnostics Profile Specification (FF-912) Based on NAMUR NE107 recommendations Delivers consistent presentation of diagnostic conditions for Emerson and non-emerson devices Allows standardization of work practices The Value of PlantWeb Alerts Now Available for All Ff Devices!

21 PlantWeb and NE107 Alarms comparison : NE-107 Categories PlantWeb Categories DeltaV v12 Only one Alert per category Investigate fields do provide more (all) details on Demand to the operator

22 Pain Point - FF Segment Component Costs Requiring special power supplies and conditioners on FF segments increases implementation cost and reduces payback. Also if Physical Layer Diagnostic is desired, some of those Solutions are getting complex or they are only providing benefit if installed in multiple of 8-segments

23 Pain Point - FF Segment Component Costs When we were looking into this, we considered the following to be most important (highest cost) we would like to eliminate by Integrating it into our architecture : - 24 VDC Power distribution - Segment Power conditioning - Segment Power diagnostic - Segment based Communication Diagnostic - Segment Termination

24 Pain Point - FF Segment Component Costs Simplified installation with S-series Power integrated Fieldbus Card : Eliminate segment Power design and hardware Use standard Bulk 24 VDC power to H1 Card Uses Power Buss Plugs on the Carrier Redundant Power with Redundant H1 Cards Reduced footprint Simplified segment wiring Basic segment diagnostics

25 Foundation FieldBus M-series Solution S-series Solution - 2 powered H1 segments - Isolated power ma per segment - Fully redundant - Basic diagnostics DeltaV makes Fieldbus Easy!

26 Pain Point - FF Segment Component Costs So what s left? - Advanced Physical Layer Diagnostic, how to add it?` P+F AMS Snap On Segment 1 and 2

27 Rong Gul SENIOR AUTOMATION ENGINEER / SUBJECT MATTER EXPERT

28 Pain Point Replacing FF Device with Newer Revision Replacing an FF device on my DCS requires many clicks especially when it is a new revision of the device being replaced

29 Improved Device Replacement New parameter COMPATIBILITY_REV declare compatibility rules Enables systems to use an updated device that was commissioned with a prior device version Devices Available for Device ITK Profile 6 (available now!) Tested (if present) under ITK 6.1 (available now!) Hosts Available for Host Profile C (4Q 2013) Tested (if supported) under Host Test Kit 3 (1Q 2014)

30 Device Replacement Scenarios Characteristic Identical Device Like Device Unlike Device Manufacturer Same Same Different Device Type Same Same Different Device Revision Same Newer Different Capability Level Same Same Different

31 Like Device Replacement Example /ABCD/0101 Commissioned X Manufacture ID: Device Type: ABCD Device Revision: 01 MANUFAC_ID : DEV_TYPE : ABCD DEV_REV : 01 Instrument fails

32 Like Device Replacement Example /ABCD/0101 Manufacture ID: Device Type: ABCD Device Revision: 01 Commissioned MANUFAC_ID: DEV_TYPE: ABCD DEV_REV: 02 COMPATIBILITY_REV: 01 No new files to install!

33 Past Pain Point Configuring New, Unfamiliar FF Devices How do I figure out which of the many parameters in an unfamiliar FF device need to be configured and what values do I use?

34 Managing Big Data from Smart Devices Pressure Transmitter 3051s has ~ 100 configurable parameters 2700 Mass Flow has ~ 290 configurable parameters DVC 6000 has ~ 170 (68 must be set per user manual) Thousands of devices amounts to a mountain of configuration data

35 Big Data Business Case Many default Device Definition (DD) parameter settings only set up the communication between the device and host. The rest of the parameters enable diagnostics, features or device options For each device there can also be commissioning or even application specific parameters

36 Big Data Business Case Many Shell sites utilizing FOUNDATION FIELDBUS or HART devices are also using corporate standards for the setting of the parameters on these devices. Many of these settings are not the default settings from the device manufacturer up to XX% on some devices. These settings are critical for effective Smart Instrument Asset Management.

37 Why Template? These parameter settings are stored in corporate template files with XX to YYY parameter settings depending on the type of device and world area in order to: Optimise diagnostics Select features and options Ensure error-free downloads to the device Identify application and commissioning parameters

38 Multiply Parameters x Devices Configuring the devices one at time is laborious and prone to errors one Digital Valve Controller may take minutes Configuring and commissioning smart assets is time consuming Average configuration time for a 3051S is XX minutes Verifying that smart assets are configured properly is an arduous process Countless hours are involved in this exercise and is also prone to either not being done or being incorrect

39 Device Template Concept Template 2 Template 1 Label Single Temperature Label Help Single Temperature Measurement This template permits. Help Block This template permits. Parameter Value Block AI [1] Parameter L_TYPE Value Direct AI [1] AI [1] L_TYPE CHANNEL Direct 1 AI TB1 [1] CHANNEL CONFIG1 1 2 TB1 TB1 CONFIG1 CONFIG2 2 TB2 CONFIG2 SINGLE AI TB1 TB2 AI

40 Device Templates Benefits Each template is identified by a label Each template can have additional help information Both label and help can be localized A device can contain more than one template Each template can reference multiple blocks Templates list may be filtered for easier selection

41 More Information on Templates FF Templates Managing Big Data for Success Wednesday, 9:00 AM to 9:45 AM, Mustang 1

42 Al Dewey PRODUCT MARKETING MANAGER

43 Past Pain Point Unfriendly, Hard to Use User Interface with FF Devices FF Device suppliers have little control over how their device is displayed in DCS User Interface DD technology restricts FF device displays primarily to alphanumeric format Data displays were organized by blocks rather than function.

44 Typical Asset Management Display Before EDDL Organized By Blocks Formatting controlled by DCS Host Primarily text data

45 Typical Asset Management Display After EDDL Formatting controlled by EDD Organization by task rather than blocks More use of Graphic Elements

46 BEFORE Typical 475 Field Communicator Before and After EDDL AFTER

47 FDT-DTM Technology with FF Enables complex FF device diagnostics within the DTM Use with PactWare and other non- Emerson Hosts

48 Past Pain Point Potential of Disrupting FF Control System with Portable Tools How can I minimize the possibility that a handheld or laptop used on an FF segment in the field will interfere with or disrupt communications with the DCS?

49 FF Host Profiles Host Profiles defined by FF restrict the types of changes possible from portable tools/

50 FF Host Profiles (Excerpt)

51 FF Host Profiles (Excerpt)

52 Host Testing and Registration

53 Best Practices for Averting Problems Make sure you understand the behavior of your FF Host system when commissioning devices that have been preconfigured with handheld.

54 Best Practices for Averting Problems Make sure you understand the behavior of your FF Host system when commissioning devices that have been preconfigured with handheld.

55 Best Practices for Averting Problems When making change to Function Block parameters (e.g. AI, AO, etc), be sure To UPLOAD FUNCTION BLOCKS before doing a Download.

56 Jonas Berge DIRECTOR OF APPLIED TECHNOLOGY

57 Past Pain Point Troubleshooting Unfamiliar FF Devices How can I troubleshoot problems with unfamiliar FF devices especially more complex devices like valves and analyzers?

58 NAMUR NE107 Status Signals (Icons)

59 Easy Interpretation of Diagnostics - Intelligent 2-wire on/off Valve Diagnostics

60 Easy Interpretation of Diagnostics - Intelligent 2-wire on/off Actuator Diagnostics

61 Easy Interpretation of Diagnostics - Temperature Transmitter Diagnostics

62 Easy Interpretation of Diagnostics - GC Diagnostics

63 Easy Interpretation of Diagnostics - Electric Actuator / Motor Operated Valve (MOV) Diagnostics

64 Past Pain Point Making Sure I Have the Latest DDs For All My FF Devices I often try to do a task with an FF Device and find out I do not have the latest DD. How can I be assured of having the latest FF DDs or easily acquire them if I don t?

65 Download EDDL Files from the Fieldbus FOUNDATION Website Accepted by DeltaV

66 Guardian Automatic System Update - DD Update Manager 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

67 Automatic System Update 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

68 Field Communicator Easy Update Utility software updates communicator with its device support files No search for files on multiple websites Simple step process to get all the last FF DDs Free downloadable toolkit allows FF DDs to be downloaded from FF or Vendor Site and easily installed.

69 Marcos Peluso DISTINGUISHED TECHNOLOGIST

70 Past Pain Point FF Downloads Require Multiple Downloads For some FF devices, my downloads often fail unless I do the download multiple times.

71 The reasons In order to protect the user, the specifications established that several parameters should have a non initialized initial value. Many of these parameters have no meaning to the user Several control systems also assume that a good initial value for parameters should be zero (Channel, Linearization Type, etc) Many times the value zero is not accepted by the field device, generating error messages. And the block remains in Out of Service During Download, the system tries to write to parameters that cannot be overwritten (serial number, calibration data, etc) or violate a conditional (a thermocouple can only have two wires, not three, not four)

72 Did you have to configure all this in your computer?

73 So, why should you worry about this?

74 Reducing Complexity Device suppliers supply a list the parameters with meaningful values in the form of a standard template. Host system suppliers or users can use these templates as a foundation for their configurations. Device suppliers list the parameters that should not be download. The non download list is used by the host system, avoiding error messages or configuration issues. Conditionals are only checked after the configuration is ready, to allow smooth download

75 Past Pain Point Inconsistent Transducer Configuration Among Different Device Suppliers I have FF flow devices from several different device suppliers. Configuration of the transducer is totally different for each of them making this task very difficult

76 Too much creativity Fieldbus Function Blocks have a standard list of parameters for the proposed functionality. Parameters may be added by a supplier, but all suppliers have to support the standard parameters As there was more freedom for the transducer blocks, each supplier came with its own list of parameters, with different names and different function. No consistency across devices of the same type, not even from the same supplier.

77 Standard Transducer blocks made it easy Use of standard transducer blocks make it easier to configure and maintain devices of different suppliers

78 4-20 ma/hart Implementation CARD n Analog Input + - Channel 1 A/D XD_SCALE OUT_SCALE 4-20 ma + HART A/D A/D Channel 2 Channel 3 Ch 100% 100% Direct Indirect Square Root Filter OU T Transmitter Data A/D A/D Channel 4 Channel 5 Unit 0% 0% Unit A/D A/D A/D Channel 6 Channel 7 Channel 8 Assigned to CARD n, Channel 3 HART capable cards: PV, SV, Analog Input Block offers the same functions available in some transmitters

79 Fieldbus Implementation Resource Block Transducer Block AI Block Out Cyclic AI Block (Shadow) Other Function Blocks Transmitter Other Parameters Acyclic DCS

80 Fieldbus Device Sensor Transducer Analog Input XD_SCALE OUT_SCALE 100% 100% Process Variables Pressure Temperature Channel 1 Channel 2 Ch Direct Indirect Square Root Filter OU T 0% 0% Unit Unit BIGGEST PAIN!

81 Channel and Scale

82 Where To Get More Information FF End User Training Next Seminar: November SS Lee College in Houston Certified Training Fieldbuses for Process Control, Engineering, Operation, and Maintenance Jonas Berge

83 Where Can I Learn More? What is FOUNDATION fieldbus? Breaking the Limits of Analog Technology Proven Benefits in Projects Worldwide Enhanced Operations and Maintenance Ease of Use ages/stories/technology/a boutthetechology/overview /fieldbus_brochure.pdf

84 QUESTION AND ANSWER SESSION

85 Thank You for Attending! Enjoy the rest of the conference.