Voices: Rezabek

Hungry for Open Network Protocol Standards

You Just Can't Be Apple to Your Customer and Control Every Widget You Sell

By John Rezabek

A few years ago, our site upgraded the natural gas metering for custody transfer with a remote terminal unit (RTU), which now transmits our daily gas usage over a cellular connection to our supplier. The single-board device simply populates its data table by polling our DCS over a Modbus serial link, and then "phones home" using a cellular modem. We're hardly taxing its capabilities, which include interfaces for multiple positive-displacement or Coriolis flowmeters, temperature and pressure correction, and meter calibration checks. It's a powerful little box, customized for this sort of point-of-sale custody transfer application.

While I can count on one hand, thankfully, the number of unique, one-off configuration tools for which our controls people need to maintain software and stay proficient in, the spread of little specialized and proprietary boxes—RTUs and their cousins of every ilk—is marching on. With scores of small systems houses and shops producing such applications by the hundreds or thousands, how exactly will I&C professionals maintain them all?

Ponder this: There's a little, one-of-its-kind-on-your-site PLC that shipped on a package, say a deaerator or cooling water treatment skid, that stops functioning one day after 10 years of quietly doing its thing. Is the skid supplier still there? Is the person who configured the controls still around? Does the copy you have of the engineering interface from 10 years ago run on a Windows 7 laptop? Did the person you used to call at the vendor retire yet?

Aslo Read "Proprietary Protocols Hang Tough"

Lifecycle support for all these little disparate mini-systems threatens to be a challenge for most everyone. We're doing it to ourselves, or our enterprise is doing it to us, when we or they defer to expedient, proprietary solutions in the name of cost and schedule.

We need to get hungry for open standards. There's one standard whose purpose is to mitigate this towering Babel of random proprietary solutions. Called Foundation fieldbus for remote operations management (FF-ROM), it's a technology aimed at providing standardized, DCS-like tools and services for integrating data sources from remote sites. From conventional I/O to wired HART and FF to WirelessHART, ISA 100.11 and Modbus, the FF-ROM specification brings it all together. It does this by defined mappings of various signal types to FF transducer blocks, which in turn can be integrated with the entire repertoire of standard fieldbus function blocks, like analog input (AI) and discrete input (DI).

How does this help as opposed to adding complexity? Well, my current practice is to integrate these disparate signals with Modbus or OPC. It's already complex, as some data is contained in blocks of 32-bit, floating point registers, or some may be 16-bit integers. The sizes of the blocks of data, the scaling, linearization and so on is all done on a register-by-register basis. It's highly customized and a challenge to document and maintain.

Fieldbus function blocks, in contrast, are an open standard, all of which can be accessed and configured using the same tools and services from a variety of suppliers that we're already using. The AI block the systems guy configured in our system in 1999 can be configured and downloaded for a fieldbus device that was just delivered yesterday. For us, data quality is vitally important, and it's already prepackaged and delivered in the FF function block. FF-ROM would decipher the Tower of Babel—if we could buy it.

We can't buy it right now because suppliers aren't feeling any end-user pull. We aren't insisting on open solutions. But eventually, our suppliers will feel the bite of this mayhem of mini-systems, just like we do. In our scope of deliverables, you just can't be Apple to your customer and control every widget you sell.

There are many of our favorite suppliers with great products who can lead the way—as they have in the past—with open solutions. I'm pulling for them!

More from this voice

Title

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

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

When to Use Control in the Field

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

11/02/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

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

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

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

Smart Pipe--One Bus to Rule Them All

What Revolutionary Technology Is Coming Along That Will Kill Fieldbus?

06/05/2012

Selling Diagnostics to Management, Part 2

Dear Plant Manager, We See a Chance to Get Distinctive and Strategic Value From Intelligent Devices; Give Us a Chance to Prove We Can Do It

05/07/2012

Selling Diagnostics to Management

Managers Are Paid the Big Bucks to Make Decisions That Many Times Boil Down to "How Much Insurance Do I Want to Buy?

04/05/2012

Using Your Best People

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

03/02/2012

Is Lick-'n-Stick Wireless the Future?

Wireless Networks Don't Come Cheap Nor Does Running Lengthy Wiring That Is Also Time Consumming. Are You Waiting on Standards Convergence or on the Right Application?

02/06/2012

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

12/30/2011

Operations Drives Reliability

Operators Can Have a Bigger Impact on Asset Reliability Than Our Maintenance Department

12/05/2011

Choosing a Fieldbus Host

Selecting a Fieldbus Host Is Not an Easy Decision. It Might Be as Life-Changing as Getting Married

11/02/2011

Are Users Happy with ESD Solutions?

Seems to Be That Users Are Quite Happy With Separate Emergency Shutdown (ESD) Packages

10/03/2011

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

08/31/2011

Easy Oscilloscopes for All Buses

Troubleshooting Fieldbus Is Rarely Straightforward. One Might Need to Disconnect Segments and Shoot Them With Oscilloscopes and Meters

08/02/2011

Death of the Loop Drawing

Loop Drawings Have Become Mere "Wiring" Diagrams. Are They Needed for Fieldbus Projects?

07/05/2011

Siemens–Not Just for Profibus Anymore

In PCS 7 We May Have the First SIL-Capable Logic Solver With Native Support for Foundation Fieldbus

06/06/2011