Consulting-Specifying Engineer - October 2008 - (Page 36)

the building, but also over the Internet. It is especially desirable when dealing with multiple facilities. TCP/IP allows facilities to take advantage of all new developments occurring in research and Web-based technology. Once TCP/IP has been specified, facilities can share data from different software packages that reside on the TCP/IP network. Data sharing is possible through the use of personal computers. Many system integrators use graphical user interfaces (GUIs) to visually share information from different systems on a single graphic video display. TCP/IP allows additional communication standards such as Open Database Connectivity (ODBC) and Open Process Control (OPC), along with Internet standards such as Extensible Markup Language (XML), Hypertext Markup Language (HTML), and Simple Object Access Protocol (SOAP). 5 Coordinate, coordinate, and then coordinate Project coordination is a challenging, yet essential, task in any interoperability and integration project. Project coordination becomes immediately apparent when optimizing multiple systems to function in a holistic manner. Through coordination efforts, always seek to maximize existing resources while minimizing disturbances to facility occupants or visitors. Along with the traditional coordination of electrical power for control equipment, coordination efforts should also include: Identifying project expectations: Make sure that all discussions and decisions are formally documented for all active parties to read and understand. Is system integration being considered to save energy or to standardize major building functions? Determine the driving factors through group discussion, and develop realistic goals. For instance, system integration does not have a direct correlation to energy reduction. Energy reduction control applications can be applied to an integration project. Meeting with the IT department: When an existing IT infrastructure is anticipated, coordinate all data drops for each BAS panel or smart device. Provide floor plans to the IT department indicating all BAS panel locations. This will ensure that BAS connectivity to the existing faculty network will be allocated. Identifying exact point mapping for all systems: Coordinate exact point information required from all equipment from each manufacturer that the BAS will monitor or control via a direct communicate interface. These direct communicate interfaces include protocols such as Modbus, OPC, and others. Make sure that essen- 4 Design with connectivity in mind Current technology allows disparate systems to converge onto an IP network. Thus, rather than using dedicated wires, many of these systems are able to tap into a communication network already installed and operated by the facility’s information technology (IT) group. An engineered structured cable plant allows several building systems, such as security, lighting control, and building automation, to share a single IT infrastructure. At the same time, each system communicates in a secure, independent manner. This strategy takes advantage of the fact that data communications for many systems share the same communication protocol, such as the industry standard of Ethernet TCP/IP (IEEE standard 802.3). New direct digital control panels that reside on local area networks also can connect to the Internet using static IP addresses. As more building systems are designed to integrate with others, less cabling will be required, reducing initial installation costs and yearly maintenance. Buildings with extensive IT infrastructures reap the most savings when their existing IT network is used. tial information is obtained from each system manufacturer that will be integrated. Just because it is possible to obtain “100 points of information” from a chiller control panel through integration does not mean you should do it. Systems will not need every available point of information to be mapped from direct communication interfaces to operate efficiently. Discussing GUI standards: Often, integration projects require that information from multiple manufacturers be visually displayed in a similar manner. This allows facility personnel to quickly familiarize themselves with different systems because “visually” information appears in a format they recognize. Always coordinate “how” different systems will be displayed. Design engineers should always request GUI screen samples in contract specifications. 36 Consulting-Specifying Engineer • OCTOBER 2008

Table of Contents Feed for the Digital Edition of Consulting-Specifying Engineer - October 2008

Consulting-Specifying Engineer - October 2008 Contents Viewpoint Letters News M/E Roundtable Cities Under One Roof Eight Design Tips for Integration Is 'Green' Really New? Down the Drain Product of the Year Awards Codes & Standards Case Study New Products Equipment Lifecycles Advertiser Index Green Space

Consulting-Specifying Engineer - October 2008

For optimal viewing of this digital publication, please enable JavaScript and then refresh the page. If you would like to try to load the digital publication without using Flash Player detection, please click here.