Voices: Rezabek

You Want More Foolproof Fieldbus?

Should We Shut Off All the Diagnostic Messages and Risk Missing Some Valuable Intelligence During Start-Up, or Leave Them All Enabled and Deal with the Nuances of the Configuration Later?

By John Rezabek

An enormous Shell hydrocarbon upgrading facility in the Middle East was preparing for start-up and commissioning, and the engineers were at odds about how to handle "device alerts"—diagnostic messages from smart devices about their self-evaluated "health" or lack thereof. Some devices had a large number of diagnostics available.

When engineers sat down with the asset management software and attempted to configure their intelligent HART and fieldbus instruments on a device-by-device basis, they found it to be rather time-consuming—many mouse clicks and 30 to 45 minutes or more for a typical positioner. There wasn't going to be time to optimize the settings prior to start-up. The debate became, shall we shut off all the diagnostic messages and risk missing some valuable intelligence during start-up, or leave them all enabled and deal with the nuances of the configuration later?

The "leave them enabled" camp prevailed, and to their dismay, the ensuing start-up was fraught with nuisance alarms and alarm floods that had some concerned about the ability of operators to maintain control of the plant. Leaving all device alerts disabled, in retrospect, may have been a more prudent choice for those circumstances.

Also Read "They'll Make a Better Software Fool"

But engineers deploying intelligent devices and asset management systems want their customers—the "operate and maintain" organization—to glean the value from digitally integrated devices. Would they be forced to begin months in advance, trudging through the configurations of each intelligent field device on their project?

There had to be a better way. There should be a path, they thought, to pre-configure some default settings for an entire class of field devices, which could then be downloaded to devices when the wires were landed and the devices commissioned in the field.

When confronted with the challenge of deploying thousands of fieldbus devices for a new project, Shell engaged its main automation vendor, Emerson Process Management, and Emerson's strategic planning manager, Scott Hokeness, to help engineer this vision.

Emerson's AMS Device Manager and DeltaV DCS engineering tools, like a lot of their kin, employ a configuration element called a "placeholder" to allow systems designers to represent the assignment and location of every fieldbus device on a project, its function block capabilities and settings for the parameters in those function blocks. Device-resident blocks used in control could be configured offline and bulk-edited using Excel spreadsheet templates.

But most diagnostic settings are configured in the device's transducer block, whose function is primarily to provide a process variable (PV) in engineering units from a raw measurement. Normally, the transducer block placeholder was populated with default settings, many of which were not interesting to Shell or whose settings were inappropriate for the service.

So Hokeness and his crew went to work, and devised a way for users to create their own library of templates for each device on a project. Shell's engineers created templates for each category of device; e.g., a 648 temperature transmitter with a Type K thermocouple or a fail-open rotary DVC6200. Emerson's system then converted the templates containing the settings and generated a placeholder for each, which Shell's systems engineers could use for populating the project's configuration database.

This capability has great promise to make Shell's next large project amazingly efficient, the FAT and commissioning trouble-free, providing a distinctly useful foundation for intelligent device management for the operating plant. Plans are in place to explore extending this capability to HART devices (which have a similar number of diagnostic settings) in a future release. All of Emerson's AMS Device Manager users will get the Foundation fieldbus templating tools when they upgrade to the new version 12.5 release.

More from this voice


You Want More Foolproof Fieldbus?

Should We Shut Off All the Diagnostic Messages and Risk Missing Some Valuable Intelligence During Start-Up, or Leave Them All Enabled and Deal with the Nuances of the Configuration Later?


Yikes! Look out for that Chasm!

The best practice by far is to choose a main instrument vendor who is accountable for the integration of all field devices.


Wireless or Fieldbus?

Is Wireless Easier to Integrate with Legacy Systems than Fieldbus? Since Wireless Emerged as Viable Option, Users Have Been Pleased to Find That Wireless Connects Easily with Their Old System


Wireless Smart Devices: Unhand Me, Handheld!

Handhelds: What's Not to Love?


Wireless Measurements

A Minute to Measure It: Hazardous-Area-Capable Multiplexers and I/O Bus Extenders and Modules Can Simplify Heat Exchanger Measurements, Providing a Quicker Method Than Routing a Cable for Process Monitoring and a More Reliable Method Than Portable Measurements


Wireless Control in the Field

Users Will Have to Exert Their Influence with Suppliers to Get Control in the Field Implemented in WirelessHART


Wired or Wireless - Just DO It

Why Let Another Week Slip by with All Your Smart Devices Asleep on the Couch? Just Do It


Will Wireless Replace Fieldbus?

Hardwired Instruments Are Going to Be Around Until a Generation of Plant Operators Retires


Why Industrial Couplers Aren't Commodities?

Maybe We Should Ask If Couplers Can Be Procured on the Basis of Cost Only


Which Bus--If Any--for On-Off Valves?

Profibus PA and Foundation Fieldbus Give the End User Flexibility to Integrate On-Off Valves Wherever the Process Places Them


When to Use Control in the Field

Exploiting Control in the Field Is Never an All-or-Nothing Proposition


We Get It - Wireless Works

Can Anyone Remember an Instrument Technology That Was Marketed With Such Persistence and Zeal?


Want Open Standards? Work at It

End Users Have to Insist Their Favorite Suppliers Support Open, Interoperable Solutions, or We'll Remain Saddled With the Closed, Proprietary Ones


Using Your Best People

Getting to Know Those Working Around You. How Did They Become an "Instrument" Person?


Using Fieldbus in your HMI

Digitally Integrated Field Device Information Is Useful to Your Operator


Trunk Testing Tribulation

It's Challenging to Power Down Segments While the Plant is Down, Let Alone While a Process Is Up. Powering Down Is Not an Attractive Option


Training Wheels for Fieldbus

Even in Lean Times, There Are Ways to Get a Fieldbus Testbed If You Think Creatively


Tolerate less redundancy

Today, with Foundation fieldbus, the old redundancy paradigm no longer applies. Chances are, though, it isn’t free. So where should you apply it to achieve the fault tolerance you need?


Tinker with Defaults to Get Value From Smart Devices

Empower Your Staff So They Can Show Thoughtful, Proactive Use of Intelligent Devices, says Writer John Rezabek


They'll Make a Better Software Fool

Because We're Working With Hazardous Processes, We Have to Think Through the Consequences of Every Errant Mouse Click