23.03.2017 Views

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

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

26-8 Industrial Communication Systems<br />

lighting <strong>systems</strong> are examples of alarm processing <strong>systems</strong>. Shutters are frequently found to use Modbus<br />

to control them. LonWorks can be found in a number of emergency lighting installations. The main task<br />

is to react to a building alarm and constantly monitor the health status of emergency light devices as well<br />

as the generation of alarms to the operator as soon as they show failures.<br />

To operate a building, supervisory control and data acquisition (SCADA) <strong>systems</strong> are frequently<br />

used. These high-level management <strong>systems</strong> collect and visualize operational data from the building<br />

and provide parameters to the building manager for configuration of building services. As opposed<br />

to low-level control loops, the timing aspects of these <strong>systems</strong> are very relaxed. Still, SCADA services<br />

must exhibit high reliability. To improve reliability, the data acquisition may be distributed and placed<br />

as near to the field level as possible. In this case, the sub<strong>systems</strong> can function autonomously in case the<br />

backbone or central SCADA fails to operate. Trending of data is partly already done in building controllers<br />

or even lower in the system, and SCADA <strong>systems</strong> only need to collect and store data in batch cycles.<br />

Room control panels are also examples of a small SCADA service in rooms or corridors.<br />

Traditional BAS are often installed by different contractors for different building service domains.<br />

This means that in the past, almost no cross-<strong>communication</strong> existed between service domains. The<br />

emergence of new, tighter integrated building services, however, now requires different domains to<br />

share data. Examples are data exchange between presence detectors from lighting with HVAC or controlling<br />

sunblinds of the lighting domain from the HVAC service. From a <strong>communication</strong> viewpoint,<br />

this requires horizontal integration. Performance contracting and energy monitoring also demand a<br />

global view of the building across different building service domains. These are high-level <strong>systems</strong> that<br />

need access to data in the lower levels of the BAS. This is the area of vertical integration.<br />

26.3 Home Automation<br />

26.3.1 Motivation and Overview<br />

Adopting automation technology is equally attractive in the residential domain. Besides efficiency considerations,<br />

increased comfort and peace of mind are key motives here. Also, elderly people can live<br />

in their own homes longer (ambient assisted living, smart home care). The importance of this aspect<br />

continuously increases as life expectancy does.<br />

Although the number of devices involved in a home automation project is by orders of magnitude<br />

lower than for large functional buildings, the complexity of such projects must not be underestimated.<br />

While many applications and techniques are similar to the ones found in building automation, additional<br />

challenges arise in <strong>systems</strong> tailored to people’s needs in private households. Additional application<br />

domains (household appliances and consumer electronics) must be integrated. Easy configuration<br />

is of particular importance, since the disproportionately high setup cost will otherwise reduce the<br />

attractiveness of automation. Acknowledging these specific challenges, one explicitly speaks of “home<br />

automation” <strong>systems</strong> (HAS).<br />

A key challenge is the integration of the traditional automation domains (HVAC, lighting/shading)<br />

with the many established services in the home such as home appliances, tele<strong>communication</strong>s, multimedia,<br />

as well as energy metering and security devices. Solutions that want to persist in the home<br />

market must guarantee a seamless integration of these heterogeneous <strong>systems</strong> (both in terms of applications<br />

and manufacturers) in order to fully activate all inherent benefits. However, it is not sufficient<br />

that <strong>systems</strong> merely provide all functionalities, but they must also become usable for nonprofessionals<br />

in everyday life. This ultimately calls for two qualifications. First, installation, setup, configuration, and<br />

maintenance of a HAS should come near the famous “plug and play” paradigm and configure itself automatically<br />

as far as possible (e.g., zero-configuration networking). Especially, no technician or engineer<br />

should be needed to successfully install and use the system. Additionally, integrating any existing equipment<br />

of homes (i.e., in case of refurbishment or extension) should get by with a minimum of physical intervention.<br />

Second, the system must be usable for the residents during regular operation. This demands<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!