23.03.2017 Views

wilamowski-b-m-irwin-j-d-industrial-communication-systems-2011

Create successful ePaper yourself

Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.

Building and Home Automation 26-5<br />

permanently decreasing, so-called intelligent field devices became available. Sensors, actuators, and<br />

room units (control panels with sensor function) now take over automation functions that were previously<br />

exclusively provided by DDC stations. At the same time, DDC stations are increasingly often<br />

equipped with network interfaces and, therefore, can be used for automation and management functions.<br />

This leads to the virtual collapse of the automation layer and the reassignment of its functions.<br />

While <strong>communication</strong> at the field and automation layers still remains geared toward process data<br />

exchange, a change in the network model can be observed. Process values can typically be represented<br />

in a compact way (considering a single value at a single point in time). Moreover, the control of the<br />

building environment has relaxed requirements regarding the frequency of the control loops [33]. Also,<br />

the spatial extension of most control loops is limited. Therefore, large <strong>systems</strong> are divided into network<br />

segments, in which low data rates are sufficient even if acceptable response times to selected events are<br />

required. The main criteria for the <strong>communication</strong> infrastructure are cost efficiency, robustness, and<br />

easy installation (free topology wiring, link power).<br />

At the management layer, access to data from all segments is mandatory. Therefore, all system data<br />

pass through the network segment that the management layer devices are connected to. The amount of<br />

traffic accumulated there can be considerably high, especially in larger <strong>systems</strong> where thousands of data<br />

points can be found. Therefore, networks with a higher bandwidth are employed at this layer.<br />

For the backbone, Internet protocol (IP) has found widespread acceptance. Its not entirely deterministic<br />

behavior does not restrict its use in building automation due to the moderate requirements present.<br />

Because of compatibility issues with installed devices, the transport and network layers of existing<br />

fieldbus protocols cannot be changed to take care of the intricacies for IP [32]. This shortcoming can be<br />

alleviated by the use of tunneling [2,3]. Tunneling routers encapsulate fieldbus data packets and distribute<br />

them over any given backbone network. This happens completely transparent to the fieldbus devices.<br />

Tunneling routers also provide an access point for remote <strong>communication</strong>. Nearly all manufacturers<br />

offer gateways and interfaces that allow access to data points handled by their DDC stations for the<br />

purpose of integrating them into BMS.<br />

26.2.3 technologies and Integration Aspects<br />

In today’s BAS, a number of different technologies can be found [28]. Figure 26.2 displays a brief overview,<br />

which technologies are prevalent in the respective layers. By tradition, non-open, proprietary<br />

solutions dominate the field of building automation on the automation and management layer. This<br />

may be due to the fact that custom solutions are possible at relatively low cost, given the moderate<br />

performance requirements involved. For the classic automation field bus, the majority of these solutions<br />

follow the EIA-485 standard. In certain cases, also the open standards Profibus, CANOpen<br />

Management<br />

layer<br />

BACnet/WS<br />

Automation<br />

layer<br />

Field<br />

layer<br />

STANDARD<br />

MOTOR INTERFACE<br />

SBT P1<br />

JCI N2<br />

FIGURE 26.2<br />

Networking technologies in BAS.<br />

© <strong>2011</strong> by Taylor and Francis Group, LLC

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!