Smart I/O systems vs. fieldbus networks

New configurable I/O systems bring greater flexibility to conventional instrumentation. How do they stand up to fieldbus networking for capabilities and convenience?

04/28/2014


Conventional field wiring requires lots of cabling and support structure. There are now multiple approaches that can avoid this kind of expensive complexity. Courtesy: Control Engineering, CFE MediaOver the last few years, one-by-one, major process control system suppliers have been introducing new field I/O systems that offer some sort of simplified wiring scheme and easier configurability. (See article from January 2013 at the bottom.) These new systems are far less complex than traditional analog field wiring using junction boxes, marshalling cabinets, and techniques like half-knit and fan-out. A visit to a plant with this kind of wiring must include seeing waterfalls of cables and trays. (See article from March 2013 at the bottom.)

Promoters of fieldbus technology, primarily Foundation fieldbus and Profibus PA, look at these new configurable I/O systems and point out that the kind of convenience now being touted has been available for many years using fieldbus networking. As Carl Henning, deputy director of PI North America, asks, "It's 2014—why would anyone architect a project with marshalling cabinets? In process applications, Profibus PA and Foundation fieldbus long ago eliminated the need for marshalling cabinets. These cabinets are expensive to engineer, build, wire, maintain, and troubleshoot. It's better to skip cabinets and go straight from the controller to devices. A fieldbus system provides multi-drop connections that eliminate the need to wire devices to an intermediate point like a marshalling cabinet. This has obvious benefits in initial costs, but more importantly, the fieldbus provides diagnostic data that can be used to prevent or shorten downtime."

While Henning's points are all valid, one might ask why there are not more fieldbus deployments and why companies still install systems with traditional wiring schemes. Plants that are committed to using fieldbus networks and have made the investment to install them and train users thoroughly, find them very reliable and remain generally loyal to them. There is a sizeable group of users concentrated in the oil, gas, and petrochemical industries who will consider nothing else. Over the last several years there have been a number of very large new greenfield fieldbus installations around the world to reinforce the point.

However, Klaus Erni, DeltaV and DeltaV SIS hardware product marketing/business development manager, Emerson Process Management, sees the fieldbus side of his business as essentially flat. "Big oil and gas companies that have selected fieldbus will stick with it for at least another decade," he says. "There are two types of customers now. One kind went for fieldbus a few years ago and they don't want to switch direction. They say, 'We standardized the whole fieldbus thing on the commissioning side. We have all the templates and testing done, so commissioning fieldbus for us is easier than HART.' That's fair, they want to continue using things they invented and procedures they have in place. The other kind of fieldbus user wants to pick and choose which approach depending on the application. Depending on functionality, they see situations where they need fieldbus and want to use it, but there are less critical situations where they say they are good with a HART device. They choose depending on the functionality and add those devices to their system, but that gets messy."

Joe Bastone, solution manager, Experion control and I/O for Honeywell Process Solutions, agrees but sees fewer of the second type precisely because of messy networks. "Companies decide, 'We're going to adopt fieldbus because of the diagnostic support it gives us,'" he says. "They aren't going to decide on a onesy-twosy basis and say, 'We're going to use fieldbus here and we're going to use HART over here.' It's more of a wholesale decision because there is other infrastructure that comes into play with asset management systems and the like."

Even so, Bastone says he has seen many plants with small isolated fieldbus deployments that were tried as an experiment but never used more widely. These can be problematic if technicians don't work on them often enough to keep their skills sharp.

Diagnostics and functionality

The new smart I/O systems still use conventional analog and HART devices. In that context, a digital device is strictly on-off. The new systems do not provide any more diagnostic information than conventional HART-enabled I/O; however, they do take full advantage of what HART offers. Traditionally, the working assumption was that fieldbus networks were capable of providing more diagnostic information than HART. That is still true, but more current versions of HART have closed that gap somewhat. Devices using HART 6 and 7 have added new capabilities since version 5, and the new I/O systems can read it.

The nature of the diagnostic differences varies depending on the type of device, but there are some that are more or less universal.

Multiple variables—HART devices can provide variables in addition to the primary variable, but a fieldbus device can provide more information and do it more directly. It's rare to find a plant that controls from a secondary HART variable, but it's far more common with fieldbus.

Control in the field—Foundation fieldbus supports having a sensor and actuator on the same segment communicating in a way that allows the two to drive a PID loop without support of an external host.

Link active scheduling—Foundation fieldbus also allows a segment to continue functioning, even controlling a loop, when the host system has failed. As long as there is power, there can be enough intelligence resident in the devices to continue functioning.

Companies that have deployed fieldbus networks but find them unsuccessful often cite training issues as the main problem rather than problems with the technology. Fieldbus is not intuitive and technicians find that it requires some effort to grasp. Even companies that are enthusiastic about using fieldbus networks find the process of designing segments daunting. Fortunately, once that process is over, it rarely needs to be revisited.

Electronic I/O is growing

While Erni sees sales of fieldbus equipment solid but flat, Emerson's electronic marshalling product line is growing steadily. The key factor of the equation is the flexibility offered by the new electronic systems, which effectively eliminates any need for designing I/O strategy. "Even fieldbus segments have to make some sense as to where devices are connected. You don't mix devices on a segment, and data is bound to where that segment goes. The big advantage of universal I/O is that it avoids any need to design device strategy. Anything can go anywhere."

Bastone says that capability can make a huge difference in new applications. He adds, "The killer app of universal I/O is the ability to make late changes during a project and not suffer the huge penalties that come with realizations like, 'Oh nuts, we forgot to design for this other compressor.' Now we're in a mad rush because we have to figure out where we're going to land this I/O, how we're going to get all the engineering drawings done, and trying to stay off the critical path for the project. That's where the beauty of universal I/O and universal cabinets comes into play."

What's next?

There's no question that the influence of cloud technologies is beginning to change how we think about field devices. The ability to direct information from any kind of device to any point in the control architecture by typing a few keystrokes is pretty compelling to anybody who has had to troubleshoot a hardwired device or redirect its output by moving the relevant cable.

Fieldbus architecture is easier to work with than traditional wiring, and it represents the ultimate in diagnostic capabilities so it will still have loyal followers for years to come. Even so, the simplicity and convenience of newer I/O systems that move closer to a true instrumentation cloud are difficult to ignore. Either way, there is little reason to continue using old-fashioned hardwired I/O. As Henning reminded us, it is 2014 after all.

Peter Welander is a Control Engineering contributing content specialist. Reach him at pwelander(at)cfemedia.com.

ONLINE

Read related articles more about field I/O strategies below.

For more information, visit:

www.emersonprocess.com

https://www.honeywellprocess.com

www.us.profinet.com 



Anonymous , 05/08/14 02:41 PM:

Control-in-the-field, as described, allows the segment to keep functioning without a host.
HART has Control-in-the-field and rights to the needed patents, it's just that not many installations use it.
Link-active-scheduling only impacts Foundation Fieldbus and is an extra requirement for that bus to continue functioning without a host to supply the scheduling.
Jonas , Singapore, 05/09/14 01:30 AM:

I personally agree that large companies in oil & gas, refining, petrochemicals, and chemicals have standardized on fieldbus. Until now fieldbus was not able to grow into the other industries. For the other industries the sticking point has been backwards compatibility at device replacements. Here’s what held them back in the past: when an old digital device of an old version failed and it was replaced by a new digital device of a new version if was necessary to download a DD file from the web and load onto the system in order to access everything in the new device. This is not difficult, but it is different from the analog 4-20 mA. Anyway, this has since been addressed. Fieldbus now supports "backwards compatibility" which means you can replace an old version device with a new version device, and the system will handle the replacement automatically without manual intervention. This means any instrument technician can do it, in less than 20 minutes.
http://www.fieldbus.org/index.php?option=com_content&task=view&id=1113&Itemid=281

This makes fieldbus easier to support for the run & maintain organization. No need to download DD files.
http://www.fieldbus.org/index.php?option=com_content&task=view&id=1236&Itemid=281

This takes the mystery out of fieldbus maintenance. Since fieldbus has been made easier, and the tools have become better, the need for specialized training is reduced – and less hard.

Of course what also is happening in parallel is that people today are much more familiar with computers, software, navigating the web, and downloading files from the Internet than they were 10 years ago. Everything is going digital. Downloading a DD file is no more difficult than downloading a tune, movie, or app for your smart phone or tablet. Consider using systems that automatically download the latest DD files so the system is ever ready for new devices – you don’t have to get the files manually at the last moment. People today are just as comfortable with a computer as with a multimeter, if not more... Thus this “new” more user friendly fieldbus is now ready for a broader spectrum of industry, and a broad spectrum of the industry is now ready to go digital from the very “first meter”, not just the energy giants.

Indeed fieldbus is primarily used for new projects, and when it is used, plants go all out using it everywhere in place of 4-20 mA and on/off signals. I stress on/off signals here, because fieldbus is traditionally only associated with taking the place of analog 4-20 mA devices, but today discrete devices such as two-wire on/off valves and electric actuators / motor operated valves (MOV) are also intelligent, networked via standard fieldbus, and providing diagnostics. This is not possible with hardwired signals.

Segment design practices have also been greatly simplified, particularly when using fieldbus interface cards with integrated power supply. In the past the design practice was to validate each individual bus segment according to Ohm’s law to make sure sufficient voltage was available at every device. This practice came about because safety barriers at that time used the traditional “entity concept” and were severely limited with respect to both current and voltage. You had to do make the Ohm’s law verification to make sure the devices would work – and designers had to input the exact current consumption and cable length in order to see if they could squeeze in another device. This was done for each and every bus segment; which for a petrochemical complex could be hundreds or even thousands. This was indeed daunting, but this practice is now a thing of the past. Sometimes it was even done for general purpose or other installation where intrinsic safety was not used, even though not required. Anyway, today we have far better safety barriers based on the FISCO model, High Power/Energy Trunk concept, and also the new DART concept. These new barriers provide sufficient power to fully load the bus. With this, the new simple practice is to only do the calculation once; as a “typical” based on worst case conditions such as 12 devices, 1000 m of cable, 20 mA per device on average. A simple calculation proves this works. As long as a bus segment falls within this envelope (shorter, fewer devices) you don’t need to do the calculation again. Only for rare exception such as a remote tank farm may a custom calculation be required. This takes the daunting out of fieldbus design. Fieldbus devices can now simply be assigned to field junction boxes just like designers have assigned 4-20 mA and on/off devices to junction boxes for years – the only difference being that from the junction box to the device you only run a single pair per device, you don’t need one pair of cable for each signal in that device. For instance, a fieldbus control valve only needs a single pair to the junction box because position feedback and limits are carried on the same two wires, a hardwired control valve needs one pair of wires for 4-20 mA to the positioner, plus two pairs of wires for limit switch feedback.
The Engineers' Choice Awards highlight some of the best new control, instrumentation and automation products as chosen by...
Each year, a panel of Control Engineering editors and industry expert judges select the System Integrator of the Year Award winners.
The Engineering Leaders Under 40 program identifies and gives recognition to young engineers who...
Learn how to increase device reliability in harsh environments and decrease unplanned system downtime.
This eGuide contains a series of articles and videos that considers theoretical and practical; immediate needs and a look into the future.
Learn how to create value with re-use; gain productivity with lean automation and connectivity, and optimize panel design and construction.
Go deep: Automation tackles offshore oil challenges; Ethernet advice; Wireless robotics; Product exclusives; Digital edition exclusives
Lost in the gray scale? How to get effective HMIs; Best practices: Integrate old and new wireless systems; Smart software, networks; Service provider certifications
Fixing PID: Part 2: Tweaking controller strategy; Machine safety networks; Salary survey and career advice; Smart I/O architecture; Product exclusives
The Ask Control Engineering blog covers all aspects of automation, including motors, drives, sensors, motion control, machine control, and embedded systems.
Look at the basics of industrial wireless technologies, wireless concepts, wireless standards, and wireless best practices with Daniel E. Capano of Diversified Technical Services Inc.
Join this ongoing discussion of machine guarding topics, including solutions assessments, regulatory compliance, gap analysis...
This is a blog from the trenches – written by engineers who are implementing and upgrading control systems every day across every industry.
IMS Research, recently acquired by IHS Inc., is a leading independent supplier of market research and consultancy to the global electronics industry.

Find and connect with the most suitable service provider for your unique application. Start searching the Global System Integrator Database Now!

Case Study Database

Case Study Database

Get more exposure for your case study by uploading it to the Control Engineering case study database, where end-users can identify relevant solutions and explore what the experts are doing to effectively implement a variety of technology and productivity related projects.

These case studies provide examples of how knowledgeable solution providers have used technology, processes and people to create effective and successful implementations in real-world situations. Case studies can be completed by filling out a simple online form where you can outline the project title, abstract, and full story in 1500 words or less; upload photos, videos and a logo.

Click here to visit the Case Study Database and upload your case study.