Maximizing Interoperability with BACnet
Part 1: What is BACnet Interoperability
Part 2: Understanding BACnet Capabilities, Getting Past Obstacles
Part 3: Verifying and Customizing Interoperability
What is BACnet Interoperability
August 2010 - Building Automation
Ask most facility managers what BACnet means and they'll answer with one word: interoperability. The whole point of the protocol is that it operates across multiple systems.
BACnet has been so successful that all major building automation system (BAS) manufacturers now offer "BACnet systems." But the fact is that all so-called "BACnet systems" are not created equal. Simply buying products that offer BACnet capability doesn't necessarily guarantee interoperability within a BAS.
"It is reliable communication at both the device and network management levels," says Ben Dorsey, vice president of marketing for KMC Controls. "But it also is a standard, and some providers do a better job than others at implementing this standard. As such, certain things can inhibit interoperability. I always encourage facility professionals to be aware of these things so that their expectations can be met."
It's important for facility managers to dig below the surface of claims for interoperability of various systems. That's because true interoperability can bring benefits for the life of the system. Creating a BACnet-based, interoperable system provides a strong basis for future expansion, says Tom Zaban, executive vice president of sales and marketing at Reliable Controls.
"The whole 'future-proofing' concept is key here," Zaban says. "With whatever new equipment is added from here forward, facility managers need to consider that equipment's connectivity and data-sharing capabilities and ask themselves the important question, 'How do we want to grow our control systems?'"
The flexibility provided by an interoperable system becomes especially powerful for the "smartest" buildings.
"Designing an intelligent building and making it interoperable is the ultimate business value," says Marc Petock, vice president of global marketing and communications at Tridium, Inc. "The building can be operated at lower cost, meaning equipment and systems — lighting, HVAC, elevators, security — can run for a lot less money. It's easierÊfor maintenance and monitoring, too. You're able to manage and control all interoperable building systems 24/7 from anywhere. You can pull up the interface on your Blackberry orÊother PDA and make it work as easily as you can from inside the maintenance department."
Those are powerful benefits. But it takes a little homework on the part of facility managers to ensure that they get those benefits.
Interoperability 101In the past, if an existing building system, such as a chiller, came from a particular manufacturer, facility managers would need to assure that they had that same company's front-end software on their computers if they wanted to make any changes to the system remotely. "But, if you operate with BACnet, you can access an entire building's systems — not one, but all — through a Web browser on any computer," says Mike Olson, power and controls sales manager for ABB. Interoperability allows control systems manufactured by different vendors to work together, sharing data as required via a Web-based interface that operators can access through a single front end. An open interoperable system is based upon an open standard, such as BACnet, that can be used by any manufacturer without requiring licensing fees or restrictions on use. "It helps give you better access to information," says Roy Kolasa, open system integration manager at Honeywell Building Solutions. "This allows facility managers to make more informed, efficient business decisions." As such, interoperability's ability to allow various building systems to work together to create new monitoring and control strategies gives facility managers the opportunity to achieve important operational goals. These include reduced energy consumption, occupancy-based control and general streamlined maintenance and operation. Interoperability can yield lower life-cycle costs, increased system flexibility and lower supplier risk. "The ability to monitor and control a building's interconnected system can offer substantial savings in time and effort," says Larry Haakenstad, Alerton's director of sales. "The availability of information to multiple users can positively impact productivity, making it easier and less time-consuming to manage these systems." There are various levels at which interoperability takes place:
"For various reasons, different vendors sometimes supply systems to different wings of a building. Or, on a large campus, different vendors may supply the BAS in different buildings," says Steve Tom, director of technical information at Automated Logic Corp. "This is particularly common if the systems are installed at different times, under different contracts." This can present challenges, particularly if not all products in the system comply with an open protocol, such as BACnet. |
Litmus Tests for InteroperabilityFor facility managers considering a BACnet-based interoperable system, it's worthwhile to determine if vendors can pass two important tests. One is to find out if the vendor has devices listed by BACnet Testing Laboratories (BTL), which tests devices to ensure that they have correctly implemented the BACnet features they claim to offer. BTL listing ensures that a product conforms to the BACnet standard. For a list of BTL-listed devices, visit: www.bacnetinternational.net/btl Another important indication that a vendor will be able to deliver a truly interoperable BACnet system is to ensure that they've worked successfully with other vendors in the past. For case studies on successful multivendor BACnet installations, visit: www.bacnetinternational.net/success/stories.php |
Comments
Daryl Clasen wrote re: What is BACnet Interoperability
on 9/24/2010 4:15:32 PM
So, my second part of the inquiry is tailored to asking what is in place or upcoming with keeping track of bacnet networks and routing over IP.
Daryl Clasen wrote re: What is BACnet Interoperability
on 9/24/2010 4:14:04 PM
Hello Michael,
For the Kuwait job you need to really pull out the Lighting, Power monitoring, water monitoring and smoke because there is only a bacnet gateway, right? And certainly the CCTV is not bacnet. Again, a gateway. I do know a couple firms that tried LON based CCTV. It was doable, but I would think kind of rough. Anyway, this looks primarily a one-vendor project.
On Fordham University, same type of thing. The lighting controls or ballasts aren't bacnet. No bacnet light switches or occupancy sensors either I'm guessing.
What I'm really driving at here is that you don't really see any MSTP mixed level installations like you do with LON. I think it has much to do with the poor performance of MSTP in comparison. I don't see how any MSTP would be functionally acceptable controlling integrated sun blinds, lights and HVAC on the same MSTP fieldbus.
Most of the integration is gateway supervisor level on BACnet/IP, which seems to be a much better place for bacnet.
I wonder with the deficiencies in bacnet MSTP for higher level integrations how soon manufacturers move to the better bacnet/IP instead?
ecs1231 wrote re: What is BACnet Interoperability
on 9/23/2010 2:36:25 PM
Think open protocol, non-proprietary controls whenever possible. Try to avoid large dollar service contracts and keep integrated systems as "user friendly as possible".
Michael_R_Wilson wrote re: What is BACnet Interoperability
on 9/22/2010 2:03:54 PM
Howdy Daryl,
Actually, there are several really good examples of multi-vendor BACnet integrations in the BACnet Success Stories (www.bacnetinternational.net/success/stories.php)
Couple of good examples:
1) Kuwait Oil Company Headquarters - http://www.bacnetinternational.net/success/stories.php?sid=34 is an example where multiple systems were integrated: Chiller, HVAC, Lighting, Power Monitoring, Security, Smoke, VAV, Water Monitoring and were supplied by multiple BACnet vendors: KMC Controls, Carrier, Honeywell International.
2) Fordham University - http://www.bacnetinternational.net/success/stories.php?sid=8 - systems integrated: Boiler, Chiller, CO2 Monitoring, HVAC, Lighting, Power Monitoring, Smoke, VAV, Water Monitoring. BACnet manufacturers supplying equipment that was integrated: Delta Controls, Reliable Controls, Alerton, Automated Logic
Another, free resource for similar integration stories is the Cornerstones eNewsletter: > http://archive.constantcontact.com/fs009/1101622110435/archive/1103675513146.html
Lastly, depending upon your availability, I and several colleagues \ competing manufacturers will be speaking at the Facility Decisions trade show on this and related subjects in the BACnet Education Track. This show is October 5-6, 2010, at the Las Vegas convention center and is free.
BACnet Tracks > http://www.facilitydecisions.com/Education/TracksDetails.asp?trackid=110
HoustonButler wrote re: What is BACnet Interoperability
on 8/24/2010 1:20:21 PM
Open Building Automation Systems such as BACnet and LON do enable a multi-vendor environment at the controller and equipment level. The problem comes during the integration process in frontend where you have proprietary software from the BAS manufacturer that locks in the customer to the controls contractor and the BAS manufacturer (sometimes the same) for the life of the system. There are open frontend platforms used by many system integrators/ controls contractors that enable the building owner to change contractors and “open“ hardware selections based on performance and value. On the other hand it is not the best interest in the building owner to change contractors frequently to save some money because in the end the Building Automation System will be a programming disaster which provides poor building comfort and even worse energy performance.
