ItÃ¢â‚¬â„¢s about facilitating communication via open platforms
As more security systems become integrated with building automation, the call for open systems grows louder.
Most modern systems are using fairly common communications technologies, said Steve Thompson, director of marketing, fire and security at Johnson Controls.
Now, whether it is at the systems level through the use of BACnet, or the device level with the use of EchelonÃ¢â‚¬â„¢s LonWorks networking system and LonTalk protocol, increasingly security companies that want to become part of building automation integration need to look at ways to facilitate communications.
The rapidness with which integration occurs, said Heath Klein, product manager, integrated systems at Siemens Building Technologies, Ã¢â‚¬Å“is still prohibited by protocols.Ã¢â‚¬Â
Neither security nor fire has accepted BACnet or ModiconÃ¢â‚¬â„¢s MODBUS protocols, he said, which presents challenges on the integration side.
Ã¢â‚¬Å“A lot of building automation companies have BACnet as their protocol,Ã¢â‚¬Â he said, so accepting it would allow systems to Ã¢â‚¬Å“integrate without any bridge between systems.Ã¢â‚¬Â
As protocols take hold, he said, prices likely will fall. Ã¢â‚¬Å“As you arenÃ¢â‚¬â„¢t designing a link between two systems, the costs can come down.Ã¢â‚¬Â He said BACnet is perceived as the protocol Ã¢â‚¬Å“people are most willing to incorporateÃ¢â‚¬Â and he anticipates security companies moving in that direction Ã¢â‚¬Å“because they havenÃ¢â‚¬â„¢t come up with their own protocols.Ã¢â‚¬Â
However,Ã‚Â makingÃ‚Â aÃ‚Â caseÃ‚Â for
communication at the device level is Steve Nguyen, director of marketing for Echelon, which created the LonWorks networking platform and LonTalk protocol.
Nguyen said devices should be interoperable, whether itÃ¢â‚¬â„¢s a motion detector from the HVAC system or a security one.
About 80 percent of EchelonÃ¢â‚¬â„¢s products service the building industry, Nguyen said, and LonWorks has become part of most building product lines.
The challenge then becomes getting the security companies to recognize its usefulness as well.
Ã¢â‚¬Å“Security companies that wish to get a competitive edge will go this way (device-level communications),Ã¢â‚¬Â he said.
Already the U.S. Army and many school systems have requested device-level interoperability, he said.
Ã¢â‚¬Å“We think the message of openness is a worldwide one that will resonate,Ã¢â‚¬Â said Nguyen. Ã¢â‚¬Å“ItÃ¢â‚¬â„¢s not just about HVAC or security, but all the devices in a building working together,Ã¢â‚¬Â he said.
Ã¢â‚¬Å“Open connectivity standards would make it (integration) easier,Ã¢â‚¬ÂÃ‚Â conceded PaulÃ‚Â Smith, chief operating officerÃ‚Â for DVTel.Ã‚Â He said building automation systems that support BACnet also require video systems that support BACnet Ã¢â‚¬Å“and most do not.Ã¢â‚¬Â
Integration forÃ‚Â DVTel, depending on theÃ‚Â means and method, can take from a week to a month,Ã‚Â he said.
JamesÃ‚Â Reno, director of technical services at Amag, said the advantage of using BACnet is having open architecture. But for some security companies, he said, it is also viewed as a disadvantage because once your system is open, some of the control is lost.
He said building automation integrators who are familiar with BACnet also have an advantage over traditional security integrators. Ã¢â‚¬Å“Access control companies who want to do this (integrate with building systems) need to partner with somebody,Ã¢â‚¬Â Reno said. Ã¢â‚¬Å“The BACnet piece is complicated, while the security side is not.Ã¢â‚¬Â
Thompson of Johnson Controls said even as companies explore the BACnet and LonTalk protocols, the future will likely have fire, security and building automation moving in another direction - talking computer to computer via XML.