Voices: Rezabek

Forays into Fieldbus Technology Pay Off

Plenty of Training Resources Available to Get Team On Board

By John Rezabek

Back around the time smart transmitters were becoming mainstream — 1989 — Keystone beer introduced an ad campaign touting its, well, relative lack of flavor. The beer delivered refreshment guaranteed to minimally challenge one's palate. In the ad, a quaff of “bitter” beer sent its subject into facial contortions, revolting to all who witnessed them. Better flee to an insipid, corn-adjunct-diluted brew.

There are those who've taken a sip of fieldbus technology, experienced an episode of “bitter beer face,” and remain unwilling to go near it since. Unforeseen struggles with a supplier, service provider or technology can be enough to quash any inclination to get another six-pack.

But what if you want to escape the bland world of 4-20 mA? If you have a thirst for an all-digital, 21st-century process control infrastructure, you'll encounter many who consider forays into new technology—for example, digitally integrated field devices using an open standard—a gamble with too much chance of potentially bitter consequences. How do you convince these folks to try a sip of your proposed brew?

Training: Training junkets aren't just about learning technology. They're also for learning about each other, and gaining an appreciation of your end users' fears and challenges. If it's a class with attendees from other locations, you both have a great opportunity to learn things from them and share war stories. It can be a great comfort for your plant's guys and gals to see they're not the first pioneers on the prairie, and often you—and they—will learn as much or more from your peers as you do from the course material. Sessions should not be restricted only to specialized training focused on fieldbus. They should include training from systems suppliers (once they're chosen), asset management system providers and possibly device suppliers as well.

Device Replacement: Device replacement has been distasteful for a lot of end users, especially when they need to call an engineer when a device or fieldbus segment needs downloading. In Foundation fieldbus (FF), by design, devices come out of the box as blank slates with minimal configuration. The idea is that a centrally stored database in the DCS is a more desirable repository to preserve a consistent device configuration. But complications arise when instrument technicians are neither trained nor permitted to perform any operations on the DCS. Other complications ensue if the device checked out of the storehouse is a later revision than the one originally installed. If they don't match, the system configuration requires sediting, and sometimes new device descriptors (DDs) have to be downloaded. This is particularly onerous for remote sites with dicey Internet access. Bitter beer face!

The Fieldbus Foundation is addressing this issue today, beginning with a specification called compatibility_rev. Devices and host systems employing this parameter will allow a new device to be commissioned as an earlier revision—all the way back to the revision specified by compatibility_rev. It works like this: If your project installs Revision 3 of a transmitter, when the storehouse restocks with the latest revision, this new device can still be commissioned as Revision 3 without installing a new DD or changing the system configuration. A number of systems and device suppliers have begun creating tools and wizards that exploit this feature. It's been an optional feature since ITK5 devices, but consideration is being given to making it mandatory before the next major update.

When taking your first sip of fieldbus “beer,” you don't need to brace yourself for a bitter experience. There are plenty of training resources to get your team on board, and the Fieldbus Foundation's focus on H1 usability aims to make FF as simple as old 4-20 mA. Once you've trained your palate, you'll wonder how you ever put up with the bland brews of yesteryear.

More from this voice

Title

Smart Pipe--One Bus to Rule Them All

What Revolutionary Technology Is Coming Along That Will Kill Fieldbus?

06/05/2012

Digital Integration Commissioning: Take It Easy!

To Fully Exploit the Capabilities of Digitally Integrated Field Devices, Field People Need to Touch the DCS. Let the Plebs Touch the DCS!

07/05/2012

Easier Commissioning with Wireless

With a Capable System, the End User Is Mouse-Clicks Away From Knowing 99% of What He Needs to Know About the Device Without Ever Lifting a Wire

07/30/2012

How Can Incompatible DCS and Asset Management Suppliers Get Along?

One Throat to Choke: When a Site Has an Installed Base of Incompatible DCS and Asset Management Suppliers, It May Have to Revert to the Host's Offerings

09/04/2012

One Remarkable Transmitter

Two Decades Ago Engineers Saw No Value in Smart Transmitters, but Today They Have All Finally Accepted the Fully Digital Transmitter and Its Value

10/03/2012

When to Use Control in the Field

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

11/02/2012

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

12/04/2012

Fieldbus Flavor of the Month

We May Be Missing Real Innovation in Our Field. Lets Adopt the Latest Controls or Instrument or Network Technology Flavor

01/03/2013

Contemplating Couplers, Part 1

What's the Purpose of a Coupler, Aside from Being a Handy Gadget for Landing the Segment's Trunk and Spurs?

01/31/2013

Why Industrial Couplers Aren't Commodities?

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

02/26/2013

Is Field-Based Control More Secure?

If We Hide Our Controls in Field Devices, Are We More Immune From the Infections of the Higher-Level Networks?

04/03/2013

Fieldbus is Dead! Long Live Fieldbus!

The Competing Communications Technology That Presumably Will Replace All These Buses, Including Process Fieldbuses, Is Ethernet

05/02/2013

Fieldbus Savings the Same in Dollars or Yuan

There's Been Too Much Hype About the Cost Savings of Fieldbus. The Same Thing Can Be Done With Remote I/O

06/11/2013

Is Fieldbus a Three-Beanie Copter Problem?

There Is Work Going on to Simplify Selecting and Designing Useful Fieldbus Applications. It Remains to Be Seen if We'll Ever Get to Fieldbus for Dummies

07/11/2013

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

08/07/2013

No KISS for Digital Integration?

If KISS ("Keep It Simple, Stupid") Is the Tactic to Survive the Combat, What's the Strategy?

09/09/2013

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

10/11/2013

Foolproof Fieldbus II

Sometimes Our Well-Intentioned Attempts to Make a System "Foolproof" Create as Many Hazards as We Were Aiming to Prevent

11/07/2013

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?

12/17/2013

Fieldbus: Do Fence Me In!

Just Because You Can Put 12 Devices on Each Fieldbus Segment, Doesn't Mean You Should

01/14/2014