he three organizations that use Device Description (DD) technology as the basis for the interoperability of their devicesHART Foundation, Fieldbus Foundation and Profibus Nutzerorganisation e.V. (PA component)recently announced the release of EDDL (Elementary Device Description Language) Phase 1 as a means to provide users with a number of enhancements to the ability of their devices to represent more data intense information such as tables, graphs and images.
This is only one of the battlegrounds at present, since the bar on the fieldbus wars of the past has been raised to the next layer or two of the enterprise. The war is now taking place not only at the control level, layer 2, with the various flavors of Ethernet, it is also happening at the layer 2/layer 3 interface. This is where information available from data rich environments is being integrated into the asset management solutions being offered not only by each of the automation system suppliers but also the big guns such as SAP.
Are fieldbus wars heating up again?
CONTROL Editor in Chief Walt Boyes provides analysis and commentary.
Of course, in addition to the Big Three fieldbuses in the process industries, other fieldbuses, such as DeviceNet, Modbus, LONworks, AS-i and others, are not standing still either.
What will all these new features mean to the control landscape of the future, say around 2010? As we enter 2005 and hence, the middle of this decade, it is time to look into our crystal ball and make an educated prediction on how things will unfold so that you readers can take this into consideration as you plan your new facilities and future automation upgrades.
Lets have a look at each of the above points in turn.
EDDL vs. FDT/DTM
Despite the fact that Phase 1 is a significant improvement over the present text-only representation supported by these protocols, EDDL Phase 1 is a beginning on which to build better platforms in the future. The analogy is that DDL is presently in the DOS days, EDDL Phase 1 is like Windows 3.2 and EDDL Phase 2 will be the Windows NT release. In the interim, end users will continue to use what they have and be innovative in how it is applied, including the use of work-arounds if necessary.
Its competition is FDT/DTM (Field Device Tool/Device Type Manager) from Europe. When asked for his thoughts on EDDL/FDT, Jim Sprague, a controls engineer with a major Middle East oil and gas producer/refiner responded, We are counting on EDDL and FDT/DTM to fully deliver on Foundation Fieldbus (FF) promise of giving us âbest in class instrument choice. Sprague continued, Our company is moving ahead strongly with FF use, but we still have to be careful about our instrument selection to make sure Host âPlug-Ins or âSnap-Ons are available to give us full access to instrument maintenance features and diagnostics. We look forward to the time when we can choose best in class FF instruments and just know we will get everything at the host.
The EDDL-FDT/DTM conundrum is a small part of the battle to integrate the abundance of information available from a modern integrated digital control system and effectively use it to increase the bottom line. Many end users are taking advantage of the additional information to operate their facilities in a more reliable way using asset management or maintenance system solutions but, as indicated above, are experiencing difficulties getting all the parts to play nicely together.
Another end user in Northern Europe responded to my inquiry on the impact of EDDL by saying The (host) manufacturer that supports full functionality of non-host devices will have an advantage in the market.
This confirms that end users are not so much interested in the technology used to provide them the information they require, but rather the content of the information itself and hence the use of FDT/DTM to get that information if it is not available from fieldbus directly. FDT/DTM uses DD technology as the basis on which it enables the device manufacturer to represent the information in their device the way they wish, rather than how the host or maintenance system supplier thinks it should be done. Obviously, if the maintenance system supplier manufactures an end device, it is going to integrate it more tightly into its system than someone elses product and hence the request or need for FDT/DTM to fill a void. Interestingly, some speculate that the EDDL enhancements were driven not so much by end users but the competition from FDT/DTM.