In a very well-documented article, Computerworld describes the current status of building automation systems (BAS) that control heat, air conditioning or lighting and how these systems are merging with traditional IT infrastructures. Computerworld writes that they're not enough standards in this industry and asks a fundamental question: who will administer these building networks, IT or facilities managers? Take for example Yale University which wants to connect 210 campus buildings, but also wishes "to integrate the BAS with the university's accounting system for billing and chargeback." Imagine the security risks involved with such an approach. Read more...
Let's start with a an assessment of the current situation.
As building automation systems (BAS) that control heat, air conditioning, lighting and other building systems get smarter, they're converging with traditional IT infrastructures. Emerging standards are enabling data sharing between building systems as well as with other business applications, improving efficiency and real-time control over building operating costs. Information security concerns, immature standards, the reluctance of vendors to give up proprietary technologies and ignorance among IT professionals of the convergence trend are all slowing the pace of this transformation, but it's gathering momentum.
But who will control such networks? And are there enough standards in this industry?
Open standards are just beginning to evolve and will likely break down the silos between building systems ranging from physical security to elevator controls. And the data from those systems is likely to be shared with other business applications such as the accounting system. This will allow for more-efficient buildings as applications are developed that can capitalize on newly converged data streams and real-time access to data.
[Right now,] standardization has started from the bottom up. Proprietary cabling systems in networks that link sensors and other devices to controllers on individual floors have given way in recent years to two competing, open protocols, BACnet and LonTalk, while floor controllers are migrating onto IP backbones.
Barry Haaser, executive director of LonMark International, says LonTalk and BACnet will prevail at the device level for technical and cost reasons. Others aren't so sure. "Instead of two guys running the IT and controls networks, why not one guy? I see IP going down to the individual device," says Anno Scholten, chief technology officer at BAS vendor Plexus Technology Ltd. in Irving, Texas.
 |
This diagram shows how "building automation systems today rely on open, industry-specific protocols such as LonTalk (shown) or BACnet for device-level communications. But they increasingly leverage Ethernet and TCP/IP for home runs back to the control systems." (Credit for image and legend: Computerworld). |
Let's take the example of Yale University to see how complex can be the merge between control systems and IT infrastructure.
But sharing the IP backbone raises security concerns among network administrators. Yale University is starting a project to consolidate its BAS onto an IP network that will link 210 campus buildings, and it plans to tie the BAS into a room-scheduling system that will automatically control energy usage based on room occupancy. For security reasons, Bill Daniels, manager of systems and technologies for the university's facilities group, has created an isolated, parallel network that's protected by firewalls and uses nonroutable IP addresses to keep data off the Internet.
Jerry Hill, director of systems engineering at Yale, says security is paramount. "We don't want a student to hack into our building management systems just because they can," he says.
The problem is that Daniels wants to integrate the BAS with the university's accounting system for billing and chargeback.
One thing is sure: I wouldn't apply for an IT security job at Yale University. Too many nightmares...
Finally, this must-read article looks at how web technologies are used in building automation systems, such as the use of encrypted XML messages via SOAP to control heat and lights at an airport gate when needed.
Source: Robert L. Mitchell, Computerworld, March 14, 2005; and various websites
Related stories can be found in the following categories.
7:51:22 PM
Permalink
|
|
