idnits 2.17.1 draft-martocci-6lowapp-building-applications-00.txt: Checking boilerplate required by RFC 5378 and the IETF Trust (see https://trustee.ietf.org/license-info): ---------------------------------------------------------------------------- ** The document seems to lack a License Notice according IETF Trust Provisions of 28 Dec 2009, Section 6.b.ii or Provisions of 12 Sep 2009 Section 6.b -- however, there's a paragraph with a matching beginning. Boilerplate error? (You're using the IETF Trust Provisions' Section 6.b License Notice from 12 Feb 2009 rather than one of the newer Notices. See https://trustee.ietf.org/license-info/.) Checking nits according to https://www.ietf.org/id-info/1id-guidelines.txt: ---------------------------------------------------------------------------- No issues found here. Checking nits according to https://www.ietf.org/id-info/checklist : ---------------------------------------------------------------------------- No issues found here. Miscellaneous warnings: ---------------------------------------------------------------------------- == The copyright year in the IETF Trust and authors Copyright Line does not match the current year == Line 798 has weird spacing: '...esponse in...' == The document seems to lack the recommended RFC 2119 boilerplate, even if it appears to use RFC 2119 keywords -- however, there's a paragraph with a matching beginning. Boilerplate error? (The document does seem to have the reference to RFC 2119 which the ID-Checklist requires). -- The document date (October 16, 2009) is 5296 days in the past. Is this intentional? Checking references for intended status: Informational ---------------------------------------------------------------------------- == Missing Reference: 'I-D.ietf-roll-terminology' is mentioned on line 116, but not defined == Unused Reference: 'RFC2119' is defined on line 873, but no explicit reference was found in the text Summary: 1 error (**), 0 flaws (~~), 5 warnings (==), 1 comment (--). Run idnits with the --verbose option for more detailed information about the items above. -------------------------------------------------------------------------------- 1 Networking Working Group J. Martocci 2 Internet-Draft Johnson Controls Inc. 3 Intended status: Informational Anthony Schoofs 4 Expires: April 16, 2010 University College Dublin 5 October 16, 2009 7 Commercial Building Applications Requirements 8 draft-martocci-6lowapp-building-applications-00 10 Status of this Memo 12 This Internet-Draft is submitted to IETF in full conformance with the 13 provisions of BCP 78 and BCP 79. 15 Internet-Drafts are working documents of the Internet Engineering 16 Task Force (IETF), its areas, and its working groups. Note that 17 other groups may also distribute working documents as Internet- 18 Drafts. 20 Internet-Drafts are draft documents valid for a maximum of six months 21 and may be updated, replaced, or obsoleted by other documents at any 22 time. It is inappropriate to use Internet-Drafts as reference 23 material or to cite them other than as "work in progress." 25 The list of current Internet-Drafts can be accessed at 26 http://www.ietf.org/ietf/1id-abstracts.txt. 28 The list of Internet-Draft Shadow Directories can be accessed at 29 http://www.ietf.org/shadow.html. 31 This Internet-Draft will expire on April 16, 2010. 33 Copyright Notice 35 Copyright (c) 2009 IETF Trust and the persons identified as the 36 document authors. All rights reserved. 38 This document is subject to BCP 78 and the IETF Trust's Legal 39 Provisions Relating to IETF Documents in effect on the date of 40 publication of this document (http://trustee.ietf.org/license-info). 41 Please review these documents carefully, as they describe your rights 42 and restrictions with respect to this document. 44 Abstract 46 Building management systems have evolved toward IP communication at 47 the enterprise level during the past decade. IP implementation at 48 the real-time control and sensor layers would provide a single 49 pervasive protocol usable across the entire system increasing 50 flexibility and code reuse. This document will describe the topology 51 of these building networks, the application protocols widely used in 52 their deployment and the application use cases. 54 Requirements Language 56 The key words "MUST", "MUST NOT", "REQUIRED", "SHALL", "SHALL NOT", 57 "SHOULD", "SHOULD NOT", "RECOMMENDED", "MAY", and "OPTIONAL" in this 58 document are to be interpreted as described in (RFC2119). 60 Table of Contents 62 1. Terminology....................................................4 63 2. Overview.......................................................5 64 3. FMS Topology...................................................6 65 3.1. Introduction..............................................6 66 3.2. Sensors/Actuators.........................................8 67 3.3. Area Controllers..........................................8 68 3.4. Zone Controllers..........................................8 69 3.5. Building Controllers......................................9 70 4. FMS Communication Media........................................9 71 5. FMS Communication Protocols...................................10 72 5.1. Controller/Sensor/Actuator Communication Protocol........10 73 5.2. Enterprise Communication Protocol........................11 74 5.2.1. Peer-to-peer Controller Communication...............11 75 5.2.2. Enterprise Communication............................11 76 6. FMS Device Density............................................12 77 6.1. HVAC Device Density......................................12 78 6.2. Fire Device Density......................................12 79 6.3. Lighting Device Density..................................13 80 6.4. Physical Security Device Density.........................13 81 7. FMS Installation Methods......................................13 82 8. Building Application Use Cases................................14 83 8.1. Fire and Smoke Abatement.................................14 84 8.2. Evacuation...............................................15 85 8.3. Occupancy/shutdown.......................................16 86 8.4. Energy Management........................................17 87 8.5. Locking and Unlocking the Building.......................17 88 8.6. Building Energy Conservation.............................18 90 9. Building Requirements.........................................18 91 9.1. Additional Commercial Product Requirements...............18 92 9.1.1. Wired and Wireless Implementations..................18 93 9.1.2. World-wide Applicability............................18 94 9.1.3. Energy Harvested Sensors............................18 95 9.2. Additional Installation and Commissioning Requirements...18 96 9.2.1. Device Setup Time...................................18 97 9.2.2. Unavailability of an IT network.....................19 98 9.3. Additional Network Requirements..........................19 99 9.3.1. TCP/UDP.............................................19 100 9.3.2. Data Rate Performance...............................19 101 9.3.3. Interference Mitigation.............................19 102 9.3.4. Real-time Performance Measures......................19 103 9.3.5. Packet Reliability..................................19 104 10. Traffic Pattern..............................................20 105 11. Open issues..................................................20 106 12. Security Considerations......................................21 107 13. IANA Considerations..........................................21 108 14. Acknowledgments..............................................21 109 15. References...................................................21 110 15.1. Normative References....................................21 111 15.2. Informative References..................................21 113 1. Terminology 115 For the description of the general terminology used in this 116 specification, please see [I-D.ietf-roll-terminology]. 118 Specific terminology used in this document is defined below: 120 Actuator: A field device that controls and/or modulates a flow 121 of a gas or liquid; or controls electrical 122 distribution. 124 BACnet: Building Automation Control Network. A ISO 125 application protocol used in facility management 126 systems. 128 Channel: Radio frequency sub-band used to transmit a modulated 129 signal carrying packets. 131 DALI: Digital Addressable Lighting Interface. A protocol 132 used in lighting systems. 134 Fire: The term used to describe building equipment used to 135 monitor, control and evacuate an internal space in 136 case of a fire situation. Equipment includes smoke 137 detectors, pull boxes, sprinkler systems and 138 evacuation control. 140 Intrusion Protection: A term used to protect resources from 141 external infiltration. Intrusion protection systems 143 Lighting: The term used to describe building equipment used to 144 monitor and control an internal or external lighted 145 space. Equipment includes occupancy sensors, light 146 switches and ballasts. 148 Luminaire: Another term for a light fixture installed in a 149 ceiling. 151 Security: The term used to describe building equipment used to 152 monitor and control occupant and equipment safety 153 inside a building. Equipment includes window tamper 154 switches, door access systems, infrared detection 155 systems, and video cameras. 157 2. Overview 159 Facility Management systems are deployed in a wide variety of 160 commercial building topologies, including single buildings, multi- 161 building single site environments such as university campuses and 162 widely dispersed multi-building multi-site environments such as 163 franchise operations. These buildings range in size from 100K square 164 feet (10k square meters) structures (5 story office buildings), to 165 multi-million sqft skyscrapers (110 story Shanghai World Financial 166 Center) to complex government facilities (Pentagon). The described 167 topology is meant to be the model to be used in all these types of 168 environments, but clearly must be tailored to the building class, 169 building tenant and vertical market being served. 171 The following sections describe the FMS system architecture from the 172 lowest layer to the highest layers in the hierarchy. Each section 173 describes the basic functionality of the layer, its networking model, 174 power requirements and a brief description of the communication 175 requirements. The entire section references the block diagram noted 176 in Figure 1. This figure depicts six major subsystems comprising an 177 FMS. These subsystems all have layered solutions starting at the 178 sensor layer and moving upward in complexity toward the enterprise 179 network layer. While these six subsystems are common to many 180 facilities, they are by no means the exhaustive list - a chemical 181 facility may require a complete fume hood management system; a 182 manufacturing facility may require interfacing to the PLC subsystem; 183 or a multi-tenant facility might require a comprehensive power 184 management subsystem. The objective in the architecture is to 185 integrate all common functions into the system yet allow maximum 186 flexibility to modify these systems and add other subsystems as 187 dictated by the customer. 189 Commercial buildings have been fitted with pneumatic and subsequently 190 electronic communication pathways connecting sensors to their 191 controllers for over one hundred years. Pneumatics were displaced by 192 simple electronics and dry contacts in the 1960's. Smart processor 193 based sensors displaced simple contacts in the 1970's. Localized 194 digital control, introduced in the 1980's allowed applications to 195 operate independently from the upper layers of the system. Multi- 196 dropped twisted pair sensor/controller communication networks 197 displaced high cost cabled networks. 199 The 1990's ushered in the use of Ethernet IP networks at the 200 enterprise level. This transition allowed the previously independent 201 proprietary communication networks to coexist on the enterprise IP 202 LAN network. This migration reduced installation costs and allowed 203 pertinent building data to be injected onto the enterprise 204 application suite. Proprietary protocols were displaced by industry 205 standard application protocols such as BACnet for HVAC, DALI for 206 Lighting and LON as general backbone. 208 Recent economic and technical advances in wireless communication 209 allow facilities to increasingly utilize a wireless solution in lieu 210 of a wired solution; thereby reducing installation costs while 211 maintaining highly reliant communication. Wireless solutions will be 212 adapted from their existing wired counterparts in many of the 213 building applications including, but not limited to HVAC, Lighting, 214 Physical Security, Fire, and Elevator systems. These devices will be 215 developed to reduce installation costs; while increasing installation 216 and retrofit flexibility. Sensing devices may be battery, scavenged, 217 or mains powered. Actuators and area controllers will be mains 218 powered. Today, different networks based on their own standard (e.g. 219 BACnet, DALI) do not share cabling, sensors or actuators easily. The 220 arrival of IP for building control will change this picture. 222 The objective of this draft is to describe topologies, protocols and 223 application use cases. It will describe the application benefits and 224 concerns in converting to pervasive IP networks. It will further 225 describe the IP services required to operate these systems. Finally, 226 it will describe how the building data and IT data models might 227 converge to allow a free flowing of data on the converged FMS/IT 228 network. 230 3. FMS Topology 232 3.1. Introduction 234 To understand the network systems requirements of an FMS in a 235 commercial building, this document uses a framework to describe the 236 basic functions and composition of the system. An FMS is a 237 horizontally layered system of sensors, actuators, controllers and 238 user interface devices orchestrated to work together over selected 239 communication media. Additionally, an FMS may also be divided 240 vertically across alike, but different building subsystems such as 241 HVAC, Fire, Security, Lighting, Shutters and Elevator control systems 242 as denoted in Figure 1. These distinct areas are termed 'silos'. 243 Currently, the separation between the silos is rather sharp. Gateways 244 provide connections between the silos to support all encompassing 245 applications. With future IP deployment applications will have a flat 246 addressing space for accessing all nodes in any silo. 248 Much of the makeup of an FMS is optional and installed as required by 249 the customer. These systems are expensive and must be designed to 250 allow for incremental purchases as dictated by the customer's budget 251 cycle. 253 Sensors and actuators have no standalone functionality. All other 254 devices support partial or complete standalone functionality. These 255 devices can optionally be tethered to form a more cohesive system. 256 The customer requirements dictate the level of integration within the 257 facility. This architecture provides excellent fault tolerance since 258 each node is designed to operate independently but will accept 259 overrides from the higher layers when the higher layers are 260 available. 262 Heating, Ventilation and Air Conditioning (HVAC); Fire; Security and 263 Lighting are components that can be tethered together into a cohesive 264 set of all encompassing applications tailored to the customer's whim. 265 Shutter control is an emerging application domain prevalent in the 266 European market. These major subsystems are connected logically 267 through application software called Building Applications. 269 +------+ +-----+ +------+ +------+ +------+ +------+ 271 Bldg App'ns | | | | | | | | | | | | 273 | | | | | | | | | | | | 275 Building Cntl | | | | | S | | L | | S | | E | 277 | | | | | E | | I | | H | | L | 279 Zone Control | H | | F | | C | | G | | U | | E | 281 | V | | I | | U | | H | | T | | V | 283 Area Control | A | | R | | R | | T | | T | | A | 285 | C | | E | | I | | I | | E | | T | 287 Actuators | | | | | T | | N | | R | | O | 289 | | | | | Y | | G | | S | | R | 291 Sensors | | | | | | | | | | | | 292 +------+ +-----+ +------+ +------+ +------+ +------+ 294 Figure 1 - Building Systems and Devices 296 3.2. Sensors/Actuators 298 An FMS may be composed of many functional stacks or silos that are 299 interoperably woven together via Building Applications. Each silo 300 has an array of sensors that monitor the environment and actuators 301 that effect the environment as determined by the upper layers of the 302 FMS topology. The sensors typically are the leaves of the network 303 tree structure providing environmental data into the system. The 304 actuators are the sensors' counterparts modifying the characteristics 305 of the system based on the input sensor data and the applications 306 deployed. 308 3.3. Area Controllers 310 An area describes a small physical locale within a building, 311 typically a room; although public spaces such as hallways and atria 312 are also controlled by area controllers. The HVAC, Security and 313 Lighting functions within a building address area or room level 314 applications running in the area controllers. Area controls are fed 315 by sensor inputs that monitor the environmental conditions within the 316 room. Common sensors found in many rooms that feed the area 317 controllers include temperature, occupancy, lighting load, solar load 318 and relative humidity. Sensors found in specialized rooms (such as 319 chemistry labs) might include air flow, pressure, CO2 and CO particle 320 sensors. Room actuation includes temperature setpoint, lights and 321 blinds/curtains. 323 3.4. Zone Controllers 325 Zone Control supports a similar set of characteristics as the Area 326 Control albeit to an extended space. A zone is normally a logical 327 grouping or functional division of a commercial building. A zone may 328 also coincidentally map to a physical locale such as a floor. 330 Zone Control may have direct sensor inputs (smoke detectors for 331 fire), controller inputs (room controllers for air-handlers in HVAC) 332 or both (door controllers and tamper sensors for security). Like 333 area/room controllers, zone controllers are standalone devices that 334 operate independently or may be attached to the larger network for 335 more synergistic control. 337 3.5. Building Controllers 339 Building Controllers orchestrate the overall building control. These 340 devices provide higher level functionality such as web servers, 341 scheduling, time series data archival, energy monitoring and 342 reduction, and alarm management. Additionally they will cooperate 343 with the other silos to provide synergistic applications as noted in 344 the use case sections that follow. 346 4. FMS Communication Media 348 Today most FMSs communicate over four media; DALI, EIA-485, Ethernet 349 and wireless. 351 Sensors, actuators, area controllers, zone controllers, and building 352 controllers most often connect via EIA-485 3-wire twisted pair serial 353 media operating nominally at 38400 to 76800 baud. This allows runs to 354 5000 ft without a repeater. With the maximum of two repeaters, a 355 single communication trunk can serpentine 15000 ft. Figure 2 defines 356 a representative sampling of the devices and protocols of an FMS 357 wired network based on BACnet. For lighting the DALI standard 358 provides a 5-wire cable containing control and power-supply lines. Up 359 to 64 control units can be connected to one line. The maximum 360 distance between two directly connected DALI devices is 300m 361 operating at 1200 bits/s. In Figure 2 the field bus can be replaced 362 with DALI for lighting purposes. 364 The HVAC, Fire, Access, Intrusion and Lighting subsystems are 365 integrated using LAN based Ethernet technology. These enterprise 366 devices connect to standard Cat-5e through workgroup switches. WLAN 367 communications can replace the Ethernet connection if the application 368 can operate within the WLAN performance characteristics. Currently 369 all building controllers support only a RJ-45 connection. WLAN 370 connections require an external wireless bridge. Multi-building 371 sites can also connect onto the facility intranet if the intranet 372 performance matches the application requirements. 374 Recently sensors, area controllers and zone controllers have been 375 deployed on wireless mesh systems. 802.15.4 based mesh systems seem 376 to be the technology of choice by most manufacturers due to the cost 377 point of the radio technology and communication robustness. 379 ********************************************************************* 380 NOTE: Figure 2 deleted from this version of the draft, awaiting 381 author's agreement on figure's content. 383 ********************************************************************* 385 Figure 2 Media Types and Wired Protocols 387 5. FMS Communication Protocols 389 5.1. Controller/Sensor/Actuator Communication Protocol 391 The sensors, actuators, area controllers, zone controllers, and 392 building controllers all utilize BACnet (Building Automation Control 393 Network), DALI (Digital Addressable Lighting Interface), or LON 394 protocol. BACnet is an ISO world-wide Standard application layer 395 protocol designed to maximize interoperability across many products, 396 systems and vendors in commercial buildings. BACnet was conceived in 397 1987 and released in 1995 for the HVAC industry. Since that time 398 Fire, Security and Lighting functionality has been added. 400 BACnet supports six media types including Ethernet (802.3 and IP), 401 EIA-485, Arcnet, LON, RS-232 and ZigBee. 403 BACnet supports all expected network services including functions 404 such as device and object discovery; unicast and broadcast messaging; 405 full routing; flow control and fragmentation, and network security. 407 BACnet MS/TP is the BACnet data link for EIA-485 networks. MS/TP is 408 a token passing protocol (implemented in software) allowing 409 master/slave and peer-to-peer communication simultaneously. Devices 410 must designate themselves as slaves or masters on the network. Slave 411 devices may only access the network when solicited by a master 412 device. Masters may communicate to any node on the network whenever 413 it holds the token. BACnet MS/TP has a 1-octet MAC address allowing 414 for a maximum of 254 devices per network segment. (Address 255 is 415 reserved for broadcast designation). Table 1 describes the network 416 parameters in tabular form. 418 DALI standard was conceived in the late 1990 and consolidated in the 419 IEC 62386 standard (formerly IEC 60929). DALI network is ordered in 420 16 groups of each maximally 64 devices. 16 scenes can be defined 421 grouping sets of devices together to receive the same command 422 sequences. A DALI network is usually a lighting subnet connected to 423 the building network with a LON DALI gateway 425 BACnet/IP addressing currently supports IPv4 addressing only. An 426 IPv6 working group has been commissioned by the BACnet Committee to 427 develop the needed changes for BACnet to support IPv6. This proposal 428 has been written and is scheduled for Public Review in January 2010. 430 ********************************************************************* 432 NOTE: Table 1 deleted from this version of the draft, awaiting 433 author's agreement on figure's content. 435 ********************************************************************* 437 Table 1 Typical FMS Communication Parameters 439 5.2. Enterprise Communication Protocol 441 Multiple protocols are supported at the enterprise level of the FMS 442 since this layer supports not only the embedded control operation but 443 also the user interface and end-user enterprise applications. 445 5.2.1. Peer-to-peer Controller Communication 447 Building Controllers orchestrate the overall FMS system operations. 448 Control and data access functions implemented at this level utilize 449 BACnet IP. BACnet IP provides the complete building object model and 450 requisite services across all the FMS silos. Since BACnet is 451 deployed on the lower layers of the system, utilizing it to control 452 operations at the highest layer of the system is prudent. BACnet IP 453 implements UDP/IP with its own transport layer. It is designed to 454 operate efficiently and transparently on all IP networks. 456 5.2.2. Enterprise Communication 458 While BACnet and LON are the control protocols of choice; it is out 459 of scope for most enterprise applications. Web Services and SNMP 460 frequently is added to the enterprise layer to assist in integration 461 with end-user applications and Network Management Systems 462 respectively. The enterprise level also supports most ancillary IT 463 protocols such as SMTP, SNTP, DHCP and DNS. 465 6. FMS Device Density 467 Device density differs depending on the application and code 468 requirements. The following sections detail typical installation 469 densities for different applications. 471 6.1. HVAC Device Density 473 HVAC room applications typically have sensors and controllers spaced 474 about 50ft apart. In most cases there is a 3:1 ratio of sensors to 475 controllers. That is, for each room there is an installed 476 temperature sensor, flow sensor and damper controller for the 477 associated room controller. 479 HVAC equipment room applications are quite different. An air handler 480 system may have a single controller with upwards to 25 sensors and 481 actuators within 50 ft of the air handler. A chiller or boiler is 482 also controlled with a single equipment controller instrumented with 483 25 sensors and actuators. Each of these devices would be 484 individually addressed. Air handlers typically serve one or two 485 floors of the building. Chillers and boilers may be installed per 486 floor, but many times service a wing, building or the entire complex 487 via a central plant. 489 These numbers are typical. In special cases, such as clean rooms, 490 operating rooms, pharmaceuticals and labs, the ratio of sensors to 491 controllers can increase by a factor of three. Tenant installations 492 such as malls would opt for packaged units where much of the sensing 493 and actuation is integrated into the unit. Here a single device 494 address would serve the entire unit. 496 6.2. Fire Device Density 498 Fire systems are much more uniformly installed with smoke detectors 499 installed about every 50 feet. This is dictated by local building 500 codes. Fire pull boxes are installed uniformly about every 150 feet. 501 A fire controller will service a floor or wing. The fireman's fire 502 panel will service the entire building and typically is installed in 503 the atrium. 505 6.3. Lighting Device Density 507 Lighting is also very uniformly installed with ballasts installed 508 approximately every 10 feet. A lighting panel typically serves 48 to 509 64 zones. Wired systems typically tether many lights together into a 510 single zone. Wireless systems configure each fixture independently 511 to increase flexibility and reduce installation costs. 513 6.4. Physical Security Device Density 515 Security systems are non-uniformly oriented with heavy density near 516 doors and windows and lighter density in the building interior space. 517 The recent influx of interior and perimeter camera systems is 518 increasing the security footprint. These cameras are atypical 519 endpoints requiring upwards to 1mbps data rates per camera as 520 contrasted by the few kbps needed by most other FMS sensing 521 equipment. To date, camera systems have been deployed on a 522 proprietary wired high speed network or on enterprise VLAN. Camera 523 compression technology now supports full-frame video over wireless 524 media. 526 7. FMS Installation Methods 528 Wired FMS installation is a multifaceted procedure depending on the 529 extent of the system and the software interoperability requirement. 530 Unlike most IP installations, FMSs are installed from the bottom up. 531 That is the sensors, actuators and controllers are installed first. 532 Later the Zone Controllers are installed; and finally the system is 533 connected to the enterprise network. 535 The sensor/actuator and controller level, the procedure is typically 536 a two or three step process. Most FMS equipment is 24 VAC equipment 537 that can be installed by a low-voltage electrician. He/she arrives 538 on-site during the construction of the building prior to the sheet 539 wall and ceiling installation. This allows him/her to allocate wall 540 space, easily land the equipment and run the wired controller and 541 sensor networks. The Building Controllers and Enterprise network are 542 not normally installed until months later. The electrician completes 543 his task by running a wire verification procedure that shows proper 544 continuity between the devices and proper local operation of the 545 devices. 547 For lighting networks this means that light sensor, presence sensor, 548 switches, and luminaires are all connected within a room and 549 sometimes already connected to a room controller. Commissioning is 550 for DALI executed with a laptop to map network addresses to physical 551 devices. 553 Later in the installation cycle, the higher order controllers are 554 installed, programmed and commissioned together with the previously 555 installed sensors, actuators and controllers. In most cases the IP 556 network is still not operable. The Building Controllers are 557 completely commissioned using a crossover cable or a temporary IP 558 switch together with static IP addresses. 560 Once the IP network is operational, the FMS may optionally be added 561 to the enterprise network. Wireless installation will necessarily 562 need to keep the same work flow. The electrician will install the 563 products as before and run continuity tests between the wireless 564 devices to assure operation before leaving the job. The electrician 565 does not carry a laptop so the commissioning must be built into the 566 device operation. 568 8. Building Application Use Cases 570 The Building Application layer is a software layer that binds the 571 various system silos into a cohesive systemic application. This 572 discussion in not meant to be inclusive. Rather it is meant to show 573 how these diverse systems can be coordinated to provide innovated 574 synergistic applications for the customer safety and comfort. 576 8.1. Fire and Smoke Abatement 578 Most local codes now require commercial buildings to incorporate 579 comprehensive fire and life/safety systems into a building. It is 580 well documented that loss of life in a building is mainly caused by 581 smoke inhalation rather than the fire itself. Agencies, such as UL 582 (in the US market), have developed fire certification programs that 583 govern fire and smoke operations in commercial buildings. These 584 programs require very rigorous interactive testing for certification. 585 In addition to the obvious need to minimize life/safety situations in 586 a building, facility operators are highly encouraged to implement 587 these systems due to insurance cost reductions. 589 The fire and smoke abatement application requires a highly 590 coordinated interaction between the fire silo and the HVAC silo. The 591 fire system detects the smoke or fire and reports it to the HVAC 592 system. While the fire system is issuing evacuation notices, 593 sounding the alarms and flashing the strobes; the HVAC system 594 automatically shuts down all fan systems in the immediate area (to 595 starve the fire) while simultaneously opening all external dampers 596 and ratcheting up the fans in the adjacent areas to purge the smoke. 598 Meanwhile, the lighting systems will immediately turn on all safety 599 lights in the area to assure safe passage for the occupants. It will 600 also create light trails to assist occupants to the doors. The 601 physical security system will unlatch all doors to assure immediate 602 egress of the occupants. The elevator control system will either 603 shut off entirely or bypass normal operation to assist with the 604 emergency responders. 606 The fire and smoke systems operate in either a manual or automatic 607 mode. The manual mode provides critical fire and smoke information 608 on a display to be controlled by a Fire Marshal. The automatic mode 609 is a preprogrammed set of events that control the fire automatically. 610 In practice, the fire system will be set to automatic mode and 611 operate accordingly until the Fire Marshall arrives. At that point 612 the system is normally overridden to manual mode so that the Fire 613 Marshall can control operations from the command center as deemed 614 necessary. 616 While the smoke abatement operation could be the province of the fire 617 system alone, economics dictate that the fire system off-loads the 618 smoke abatement operation to the HVAC system. In practice, the fire 619 system will receive the initial fire indication by one or more of its 620 smoke detectors. It will then inform the HVAC system of the physical 621 locale of the fire. The HVAC system will then take charge of the 622 smoke abatement operation by automatically adjusting the air handlers 623 and dampers. The HVAC system must incorporate a comprehensive 624 prioritization scheme throughout its system. This prioritization 625 scheme must allow all smoke operations to take control precedence 626 over all other control operations including manual operator control. 627 All affected devices must support a supervision policy that assures 628 that all operations requested were executed properly. The system 629 must automatically return to well-defined normal operational state 630 once the smoke situation has abated. 632 8.2. Evacuation 634 Evacuation is another systemic operation that may be activated as 635 part of the Fire/Smoke Control application, or may be activated for 636 other reasons such as terrorist threats. Evacuation requirements 637 most often will activate subsystems of the Fire, Security and 638 Lighting silos. The Fire system normally supports the intercom 639 subsystem in the facility. The intercom system will then trigger the 640 recorded voice evacuation instructions. This may be in concert with 641 the fire system audio indications if a fire situation is active or 642 standalone. The lighting subsystem will be activated to turn on the 643 lights and evacuation paths to aid in the evacuation. The security 644 system will coincidentally open all doors to allow a smooth safe 645 egress from the building. If the building also supports elevator 646 control, the elevators will operates as directed by a preprogrammed 647 evacuation policy. 649 8.3. Occupancy/shutdown 651 A major energy saving technique in commercial buildings is to 652 automatically commence HVAC and lighting operations prior to building 653 occupancy. Conversely, building shutdown allows the systematic 654 reduction in HVAC and lighting operations as the building becomes 655 unoccupied. 657 The HVAC system is usually charged with defining occupied and 658 unoccupied times. The Fire and Security operations are always 659 operable and lighting is most often subservient to HVAC. These times 660 are typically programmed into the system by facility operations; 661 however, it could be learned adaptively by the security's access 662 control system. The target occupancy time drives the HVAC subsystem 663 to turn on all ventilation equipment at an optimal time so that each 664 space is ready for occupancy at the prescribed time. These 665 algorithms will be adaptive over time but also include systemic 666 instrumentation such as outdoor air and relative humidity to turn on 667 the equipment at the last possible moment yet still meet the target 668 environmental needs just before occupancy. The lighting systems are 669 turned on/off as function of the overall light intensity and the 670 presence of persons inside the room. Switching on is immediate on 671 arrival of persons, switching off is done with a suitable delay, 672 possibly involving dimming of lights. 674 Conversely, the HVAC systems will also determine the earliest 675 possible time it can shut down heating/cooling yet still control the 676 setpoints to meet the requisite parameters. Lighting again gets off 677 easier since the lights can be extinguished as soon as they are not 678 needed. Building owners may use the lighting systems to pace the 679 janitorial service providers by defining a strict timetable that the 680 lights will be on in a given area. Here, the janitorial service 681 providers will need to keep in step to complete their work prior to 682 the lights being turned off. 684 Facility Management Systems often include a telephone interface that 685 allows any late workers to override the normal HVAC and lighting 686 schedules simply by dialing into the system and specifying their 687 locale. The lights and fan system will continue to operate for a few 688 extra hours in the immediate vicinity. The same applies to occupancy 689 sensors in meeting rooms. Either by automatic sensing or a simple 690 push of the occupied switch, the HVAC and lighting schedules will 691 extend the normal schedule for the meeting room. 693 8.4. Energy Management 695 The occupancy/shutdown applications noted above optimize runtime of 696 large equipment. This in itself is a major component of energy 697 savings. However, even during occupancy large equipment can be 698 modulated or shutoff temporarily without affecting environment 699 comfort. This suite of applications run in the HVAC domain, however 700 the HVAC silo will interact with the lighting system to reduce the 701 lighting load to help in the overall reduction of energy. 703 The load rolling and demand limiting applications allow for the 704 sequencing of equipment to reduce the overall energy profile or to 705 shave off peak energy demands in the facility. The FMS system will 706 constantly monitor real-time energy usage and automatically turn 707 unneeded equipment off (or reduce the control setpoint) to stave off 708 peaking the facility's electrical profile. Demand peaks set by 709 commercial facilities are frowned upon heavily by utilities and are 710 often accompanied by huge energy charge increases for upwards to 1 711 year. 713 Recently real-time pricing has furthered the ability to save energy. 714 This allows a facility to proactively either use or curtail energy 715 based on the price/KWH of the energy. Again, the HVAC subsystem 716 takes the lead in this application. It can either poll the price 717 structure from the Utility off the Internet, or the current pricing 718 will be forwarded to the facility by the Utility. The HVAC subsystem 719 can then automatically defer unneeded operation or temporarily reduce 720 the cooling or lighting load as the cost warrants. 722 8.5. Locking and Unlocking the Building 724 The member of the cleaning staff arrives first in the morning 725 unlocking the building (or a part of it) from the control room. This 726 means that several doors are unlocked; the alarms are switched off; 727 the heating turns on; some lights switch on, etc. Similarly, the 728 last person leaving the building has to lock the building. This will 729 lock all the outer doors, turn the alarms on, switch off heating and 730 lights, etc. 732 8.6. Building Energy Conservation 734 A room that is not in use should not be heated, air conditioned or 735 ventilated and the lighting should be turned off. In a building with 736 366 rooms it can happen quite frequently that someone forgets to 737 switch off the HVAC and lighting. This is a real waste of valuable 738 energy. To prevent this from happening, the janitor can program the 739 building according to the day's schedule. This way, lighting and 740 HVAC is turned on prior to the use of a room, and turned off 741 afterwards. 743 9. Building Requirements 745 This section contains the overall set of building application as 746 dictated by the previous discussion. 748 9.1. Additional Commercial Product Requirements 750 9.1.1. Wired and Wireless Implementations 752 Solutions MUST support both wired and wireless implementations. 754 9.1.2. World-wide Applicability 756 Wireless devices MUST be supportable on unlicensed bands such as the 757 2.4Ghz. 759 9.1.3. Energy Harvested Sensors 761 Sleeping devices SHOULD target for operation using viable energy 762 harvesting techniques such as ambient light, mechanical action, solar 763 load, air pressure and differential temperature. 765 9.2. Additional Installation and Commissioning Requirements 767 9.2.1. Device Setup Time 769 Network setup by the installer MUST take no longer than 20 seconds 770 per device installed. 772 9.2.2. Unavailability of an IT network 774 Product commissioning MUST be performed by an application engineer 775 prior to the installation of the IT network. 777 9.3. Additional Network Requirements 779 9.3.1. TCP/UDP 781 Connection based and connectionless services MUST be supported 783 9.3.2. Data Rate Performance 785 An effective data rate of 20kbps is the lowest acceptable operational 786 data rate acceptable on the network. 788 9.3.3. Interference Mitigation 790 The network MUST automatically detect interference and migrate the 791 network to a better 802.15.4 channel to improve communication. 792 Channel changes and nodes response to the channel change MUST occur 793 within 60 seconds. 795 9.3.4. Real-time Performance Measures 797 A node transmitting a 'request with expected reply' to another node 798 MUST send the message to the destination and receive the response in 799 not more than 120 msec. This response time SHOULD be achievable with 800 5 or less hops in each direction. This requirement assumes network 801 quiescence and a negligible turnaround time at the destination node. 803 9.3.5. Packet Reliability 805 Reliability MUST meet the following minimum criteria : 807 < 1% MAC layer errors on all messages; After no more than three 808 retries 810 < .1% Network layer errors on all messages; 812 After no more than three additional retries; 814 < 0.01% Application layer errors on all messages. 816 Therefore application layer messages will fail no more than once 817 every 100,000 messages. 819 10. Traffic Pattern 821 The independent nature of the automation systems within a building 822 plays heavy onto the network traffic patterns. Much of the real-time 823 sensor data stays within the local environment. Alarming and other 824 event data will percolate to higher layers. 826 Systemic data may be either polled or event based. Polled data 827 systems will generate a uniform packet load on the network. This 828 architecture has proven not scalable. Most vendors have developed 829 event based systems which passes data on event. These systems are 830 highly scalable and generate low data on the network at quiescence. 831 Unfortunately, the systems will generate a heavy load on startup 832 since all the initial data must migrate to the controller level. 833 They also will generate a temporary but heavy load during firmware 834 upgrades. This latter load can normally be mitigated by performing 835 these downloads during off-peak hours. 837 Devices will need to reference peers occasionally for sensor data or 838 to coordinate across systems. Normally, though, data will migrate 839 from the sensor level upwards through the local, area then 840 supervisory level. Bottlenecks will typically form at the funnel 841 point from the area controllers to the supervisory controllers. 843 11. Open issues 845 Other items to be addressed in further revisions of this document 846 include: 848 Need to describe the set of application protocol service 849 requirements and the correlation to IP services. 851 Need to define security policy requirements for building 852 applications 854 Need to fully document these needs into well defined application 855 requirements. 857 12. Security Considerations 859 TBD 861 13. IANA Considerations 863 This document includes no requirement to IANA. 865 14. Acknowledgments 867 This document was prepared using 2-Word-v2.0.template.dot. 869 15. References 871 15.1. Normative References 873 [RFC2119] Bradner, S., "Key words for use in RFCs to Indicate 874 Requirement Levels", BCP 14, RFC 2119, March 1997. 876 15.2. Informative References 878 [I-D.ietf-roll-terminology]Vasseur, J., "Terminology in Low power And 879 Lossy Networks", draft-ietf-roll-terminology-00 (work in progress), 880 October 2008. 882 Authors' Addresses 884 Jerry Martocci 885 Johnson Controls 886 507 E. Michigan Street 887 Milwaukee, Wisconsin, 53202 888 USA 889 Phone: 414.524.4010 890 Email: jerald.p.martocci@jci.com 892 Anthony Schoofs 893 CLARITY Centre for Sensor Web Technologies 894 University College Dublin, 895 Dublin 4 Ireland 896 Phone: +353 1 7162488 897 Email: anthony.schoofs@ucdconnect.ie