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

Training Wheels for Fieldbus

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

02/06/2009

Finding Freebies in Fieldbus

Can We Use the Standard Deviation Method to Flag a Suspicious Measurement?

03/02/2009

Save Money. Calibrate Less?

Have Our Calibration Skills and Practices Quietly Migrated to Being Largely "Plug-N-Play.”"Or Are They "Plug-N-Pray?"

04/03/2009

DCS Disasters

This Month We Join an End User Who’d Like Her Off-Hours to Be Less Subject to Distress Messages from Her Place of Employment. Dang! Cletus Been in My DCS!

05/11/2009

Certainty of Outcome with Fieldbus

What Are Some of the Key Areas Where Effort and/or Investment Are Needed to Obtain Sufficient Certainty of Outcome for Even the Smallest Project?

06/24/2009

Finally, Registered Hosts

"Compliant Host" Came to Be Because Users Were Seeking Objective Ways to Evaluate Different Hosts's Capabilities

07/13/2009

Simplifying Fieldbus Device Calibration

Creative End Users Have Been Exploring the Use of 802.11 Wireless to Display their DCS Interface on a Wireless Laptop or Notebook PC

08/12/2009

Control Systems, We Know What You Need

We Know What It Is You Want, So Step Aside While We Give It to You

09/15/2009

How's Your Fieldbus Resume?

What Kind of Qualifications Should You Be Displaying to Qualify for the Jobs That Are Available?

10/12/2009

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

11/18/2009

A Logical Path to Device Criticality

If You're Aiming to Improve the Usefulness of Your Digitally Integrated Intelligent Field Devices, There's Help Available to Help You Get Moving Down This Road

12/14/2009

New Guidelines for Fieldbus Systems

Experienced Users Concluded That the Effort of Classifying and Segregating Critical Service Loops Is Not Worth the Effort

01/08/2010

Is Field-Based Control Really All That?

Recent Studies Shown That the Fieldbus-for-I/O-Only Approach Is Likely a Source of Compromised Performance and Unknown Latencies

02/02/2010

Surprise! Field-Based Control Beats DCS

It Is Evident That Device-Based Control Exceeds DCS-Based Control in Reliability and Performance

03/04/2010

Failed Bus Blame Game

If You Allow Yourself to Be Dour, Defeated and Critical of Your Selected System, You Could Be Headed for Disaster

04/09/2010

Wireless Control in the Field

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

05/05/2010

Birds of a Feather

If You Recognize Your Peers and Competitors Attending or Presenting at a Trade Group Seminar, Then You May Have Found Your Home

06/02/2010

Can You Specify "Or Equal" with Fieldbus?

Does the Fieldbus "Checkmark" Confer Some Uniformity that Minimizes the Capabilities of One Vendor's Offering Compared to Another?

07/02/2010

Wired or Wireless - Just DO It

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

07/13/2010

Everyone, Do Your Own Math

The Incremental Costs to Add Spurs to These Fieldbus Segments make WirelessHART at Best a Break-Even Option in Many Circumstances

08/30/2010