CROSS REFERENCE TO RELATED APPLICATIONS

[0001] This international application claims the benefit of and priority to U.S Non- Provisional Application No. 17/124,544, filed on December 17, 2020 and U.S. Provisional Application No. 62/950,756, filed on December 19, 2019 under 35 U.S.C. 119(e), which applications are incorporated by reference herein in their entirety.

TECHNICAL FIELD

[0002] The present disclosure relates to integrating building automation emergency response systems into building automation systems, and more particularly to dynamically directing occupants to a safe location in the event of an emergency.

BACKGROUND

[0003] In the event of an emergency arising in a building, such as an office building, a school building, a theater, or the like, the building’s occupants must be quickly directed to a safe evacuation route to exit the building. Possible building emergencies may include fire, explosion, hazardous materials release, natural gas leaks, plumbing failure or flooding, power failure, elevator failure, and medical emergencies. Other types of emergencies perpetrated by actors may include active shooter, bomb threats and suspicious mail, demonstrations or protests, and workplace violence. Any delay in providing safe evacuation route directions to occupants could have potentially disastrous consequences.

SUMMARY

[0004] In accordance with one embodiment described herein, a server associated with a building automation emergency response system of a building, receives indications of a detected emergency in the building from one or more sensors distributed among one or more zones in the building. The indications comprise a sensor reading level of the detected emergency and an identity of the one or more sensors. The server determines a zone danger level of the detected emergency in the one or more zones, based on the identity of the one or more sensors indicating a location in the one or more zones, and based on the sensor reading level of the detected emergency of the one or more sensors in the one or more zones. The server calculates a respective evacuation route commencing from one or more user interfaces distributed among the one or more zones in the building. The evacuation route is calculated to traverse one or more zones having respective zone danger levels. A route danger level is computed as a sum of products of distance segments along the route and the respective zone danger level of the zones traversed by the segments. The safest evacuation route is the route that has a minimum route danger level in reaching a respective safe exit location of the building. The server then transmits a depiction of the safest evacuation route to the one or more user interfaces for display on a display device. The server continues receiving updated indications of the detected emergency from the one or more sensors. In response, the server determines updated zone danger levels, updated route danger levels, calculates an updated safest evacuation route commencing from the one or more user interfaces, and transmits an updated depiction of the safest evacuation route to the one or more user interfaces for display, to guide occupants to a safe location in the event of an emergency.

[0005] In accordance with an embodiment described herein, the server maintains a record of past indications comprising past instances of sensor reading level of the detected emergency and the identity of the one or more sensors in the one of the one or more zones. The server determines a weight for the past instances of sensor reading level of the detected emergency of the one or more sensors in the one or more zones. The weight is based on how frequently and recently the past instances of sensor reading level of the detected emergency have been detected by the one or more sensors. The server determines a past zone danger level of the detected emergency in the one or more zones, based on the past sensor reading levels of the detected emergency of the one or more sensors in the one or more zones. The server calculates a past-present zone danger level of the one or more zones by adding the present zone sensor level with the past zone danger level of the one or more zones. The server then calculates the safest evacuation route based on the past-present zone danger level of the one or more zones. [0006] In accordance with an embodiment described herein, the server determines a predicted sensor danger level of the detected emergency in the one or more sensors. The predicted sensor danger level is based on a predicted rate of movement of the emergency or on structural or other conditions of the zones. The server determines a predicted zone danger level of the detected emergency in the one or more zones. The predicted zone danger level is based on the predicted sensor danger level of the detected emergency of the one or more sensors in the one or more zones. The server calculates a past-present- predicted zone danger level of the one or more zones by adding the past-present zone danger level with the predicted zone danger level of the one or more zones. The server then calculates the safest evacuation route based on the past-present-predicted zone danger level of the one or more zones.

[0007] In accordance with an embodiment described herein, the server determines that the first evacuation route having the first route danger level is safer than the second evacuation route having the second route danger level. The server then transmits a depiction of the safer first evacuation route to a respective one of the one or more user interfaces for display on the display device as the safest evacuation route.

[0008] In accordance with an embodiment described the sensor for detecting an emergency is at least one of a gunshot sensor, a fire sensor, an explosion sensor, a hazardous materials release sensor, a natural gas leak sensor, a smoke sensor, a plumbing flooding sensor, a power failure sensor, or an elevator failure sensor.

[0009] In accordance with an embodiment described herein, a server, comprises:

[0010] at least one processor;

[0011] at least one memory, including computer program code, wherein the computer program code, when executed by operation of the at least one processor, causes an operation to be performed, the operation comprising:

[0012] receiving, by the server, one or more indications of a detected emergency in a building from one or more sensors distributed among one or more zones in the building, the one or more indications comprising a sensor reading level of the detected emergency and an identity of the one or more sensors; [0013] determining, by the server, one or more zone danger levels of the detected emergency in the one or more zones, based on the identity of the one or more sensors indicating a location in the one or more zones, and based on the sensor reading level of the detected emergency of the one or more sensors in the one or more zones;

[0014] calculating, by the server, a route danger level of one or more evacuation routes from one or more user interfaces located in the one or more zones in the building toward one or more respective exit locations of the building, the one or more evacuation routes comprising a sequence of one or more distance segments traversing the one or more zones having respective zone danger levels;

[0015] determining, by the server, one or more safest evacuation routes of the one or more evacuation routes from the one or more user interfaces respectively located in the one or more zones, the safest evacuation routes having route danger levels that are less than a route danger level of other ones of the one or more evacuation routes from the respective user interfaces;

[0016] transmitting, by the server, one or more depictions of the safest evacuation routes to the one or more user interfaces in the one or more zones for display on one or more display devices, wherein the one or more depictions are of the one or more safest routes transmitted to respective ones of the one or more user interfaces, based on the locations of the respective ones of the one or more user interfaces relative to the one or more exit locations and the detected emergency; and

[0017] receiving, by the server, updated indications of the detected emergency in the building from the one or more sensors, and in response, determining updated zone danger levels in the one or more zones, calculating updated route danger levels based on the updated zone danger levels, determining updated safest evacuation routes based on the updated route danger levels, and transmitting updated depictions of the safest evacuation routes to the one or more user interfaces for display. [0018] In accordance with an embodiment described herein, the server further comprises:

[0019] the at least one memory, including computer program code, wherein the computer program code, when executed by operation of the at least one processor, causes an operation to be performed comprising:

[0020] maintaining, by the server, a record of past indications comprising past instances of sensor reading level of the detected emergency and the identity of the one or more sensors in the one of the one or more zones;

[0021] determining, by the server, weights for the past instances of sensor reading level of the detected emergency of the one or more sensors in the one or more zones, the weights based on how frequently and recently the past instances of sensor reading level of the detected emergency have been detected by the one or more sensors;

[0022] calculating, by the server, a past sensor danger level of the detected emergency in the one or more zones, based on a sum of products of the weights for the past instances of sensor reading level times the past sensor reading levels;

[0023] calculating, by the server, a past-present-zone danger level of the one or more zones by adding the received sensor reading level and the past sensor danger level of the one or more zones;

[0024] calculating, by the server, a past-present route danger level of one or more evacuation routes from one or more user interfaces located in the one or more zones in the building, based on the past-present-zone danger level of the one or more zones; and

[0025] determining, by the server, the safest evacuation route of the one or more evacuation routes from the one or more user interfaces located in the one or more zones, based on the past-present route danger level of one or more evacuation routes.

[0026] In accordance with an embodiment described herein, the server further comprises: [0027] the at least one memory, including computer program code, wherein the computer program code, when executed by operation of the at least one processor, causes an operation to be performed comprising:

[0028] determining, by the server, a predicted sensor danger level of the detected emergency in the one or more sensors, based on a predicted rate of movement of the emergency or on conditions of the zones;

[0029] determining, by the server, a predicted zone danger level of the detected emergency in the one or more zones, based on the predicted sensor danger level of the detected emergency of the one or more sensors in the one or more zones;

[0030] calculating, by the server, a past-present-predicted zone danger level of the one or more zones by adding the past-present zone danger level and the predicted zone danger level of the one or more zones; and

[0031] calculating, by the server, the safest evacuation route based on the past-present-predicted zone danger level of the one or more zones.

[0032] In accordance with an embodiment described herein, the server further comprises:

[0033] the at least one memory, including computer program code, wherein the computer program code, when executed by operation of the at least one processor, causes an operation to be performed comprising:

[0034] determining, by the server, a predicted sensor danger level of the detected emergency in the one or more sensors, based on a predicted rate of movement of the emergency or on conditions of the zones;

[0035] determining, by the server, a predicted zone danger level of the detected emergency in the one or more zones, based on the predicted sensor danger level of the detected emergency of the one or more sensors in the one or more zones;

[0036] calculating, by the server, a present-predicted zone danger level of the one or more zones by adding the present zone danger level and the predicted zone danger level of the one or more zones; and [0037] calculating, by the server, the safest evacuation route based on the present-predicted zone danger level of the one or more zones.

[0038] In accordance with an embodiment described herein, the server further comprises:

[0039] the at least one memory, including computer program code, wherein the computer program code, when executed by operation of the at least one processor, causes an operation to be performed comprising:

[0040] calculating, by the server, a first evacuation route commencing from one or more user interfaces distributed among respective ones of the one or more zones in the building, the one or more user interfaces including a display device, the evacuation route calculated to traverse a first sequence of respective ones of the one or more zones having a first route danger level;

[0041] calculating, by the server, a second evacuation route commencing from one or more user interfaces distributed among respective ones of the one or more zones in the building, the one or more user interfaces including a display device, the evacuation route calculated to traverse a second sequence of respective ones of the one or more zones having a second route danger level;

[0042] determining, by the server, that the first evacuation route having the first route danger level is safer than the second evacuation route having the second route danger level; and

[0043] transmitting, by the server, a depiction of the first evacuation route to a respective one of the one or more user interfaces for display on the display device as the safest evacuation route.

[0044] In accordance with an embodiment described herein, the server further comprises:

[0045] the at least one memory, including computer program code, wherein the computer program code, when executed by operation of the at least one processor, causes an operation to be performed comprising: [0046] calculating, by the server, the safest evacuation route, based at least on one of [1] avoiding where the emergency has been located and is currently located, or [2] avoiding where the emergency is predicted to be located.

[0047] In accordance with an embodiment described herein, the server further comprises:

[0048] wherein when the sensor for detecting an emergency is at least one of a gunshot sensor, a fire sensor, an explosion sensor, a hazardous materials release sensor, a natural gas leak sensor, a smoke sensor, a plumbing flooding sensor, a power failure sensor, or an elevator failure sensor.

[0049] In accordance with an embodiment described herein, a computer program product comprising computer executable program code recorded on a computer readable non-transitory storage medium, the computer executable program code comprises:

[0050] code for receiving, by the server, one or more indications of a detected emergency in a building from one or more sensors distributed among one or more zones in the building, the one or more indications comprising a sensor reading level of the detected emergency and an identity of the one or more sensors;

[0051] code for determining, by the server, one or more zone danger levels of the detected emergency in the one or more zones, based on the identity of the one or more sensors indicating a location in the one or more zones, and based on the sensor reading level of the detected emergency of the one or more sensors in the one or more zones;

[0052] code for calculating, by the server, a route danger level of one or more evacuation routes from one or more user interfaces located in the one or more zones in the building toward one or more respective exit locations of the building, the one or more evacuation routes comprising a sequence of one or more distance segments traversing the one or more zones having respective zone danger levels;

[0053] code for determining, by the server, one or more safest evacuation routes of the one or more evacuation routes from the one or more user interfaces respectively located in the one or more zones, the safest evacuation routes having route danger levels that are less than a route danger level of other ones of the one or more evacuation routes from the respective user interfaces;

[0054] code for transmitting, by the server, a one or more depictions of the safest evacuation routes to the one or more user interfaces in the one or more zones for display on a one or more display devices, wherein the one or more depictions are of the one or more safest routes transmitted to respective ones of the one or more user interfaces, based on the locations of the respective ones of the one or more user interfaces relative to the one or more exit locations and the detected emergency; and

[0055] code for receiving, by the server, updated indications of the detected emergency in the building from the one or more sensors, and in response, determining updated zone danger levels in the one or more zones, calculating updated route danger levels based on the updated zone danger levels, determining updated safest evacuation routes based on the updated route danger levels, and transmitting updated depictions of the safest evacuation routes to the one or more user interfaces for display.

[0056] In accordance with an embodiment described herein, the computer program product further comprises:

[0057] code for maintaining, by the server, a record of past indications comprising past instances of sensor reading level of the detected emergency and the identity of the one or more sensors in the one of the one or more zones;

[0058] code for determining, by the server, weights for the past instances of sensor reading level of the detected emergency of the one or more sensors in the one or more zones, the weights based on how frequently and recently the past instances of sensor reading level of the detected emergency have been detected by the one or more sensors;

[0059] code for calculating, by the server, a past sensor danger level of the detected emergency in the one or more zones, based on a sum of products of the weights for the past instances of sensor reading level times the past sensor reading levels; [0060] code for calculating, by the server, a past-present-zone danger level of the one or more zones by adding the received sensor reading level and the past sensor danger level of the one or more zones;

[0061] code for calculating, by the server, a past-present route danger level of one or more evacuation routes from one or more user interfaces located in the one or more zones in the building, based on the past-present-zone danger level of the one or more zones; and

[0062] code for determining, by the server, the safest evacuation route of the one or more evacuation routes from the one or more user interfaces located in the one or more zones, based on the past-present route danger level of one or more evacuation routes.

[0063] In accordance with an embodiment described herein, the computer program product further comprises:

[0064] code for determining, by the server, a predicted sensor danger level of the detected emergency in the one or more sensors, based on a predicted rate of movement of the emergency or on conditions of the zones;

[0065] code for determining, by the server, a predicted zone danger level of the detected emergency in the one or more zones, based on the predicted sensor danger level of the detected emergency of the one or more sensors in the one or more zones;

[0066] code for calculating, by the server, a past-present-predicted zone danger level of the one or more zones by adding the past-present zone danger level and the predicted zone danger level of the one or more zones; and

[0067] code for calculating, by the server, the safest evacuation route based on the past-present-predicted zone danger level of the one or more zones.

[0068] In accordance with an embodiment described herein, the computer program product further comprises:

[0069] code for determining, by the server, a predicted sensor danger level of the detected emergency in the one or more sensors, based on a predicted rate of movement of the emergency or on conditions of the zones; [0070] code for determining, by the server, a predicted zone danger level of the detected emergency in the one or more zones, based on the predicted sensor danger level of the detected emergency of the one or more sensors in the one or more zones;

[0071] code for calculating, by the server, a present-predicted zone danger level of the one or more zones by adding the present zone danger level and the predicted zone danger level of the one or more zones; and

[0072] code for calculating, by the server, the safest evacuation route based on the present-predicted zone danger level of the one or more zones.

[0073] In accordance with an embodiment described herein, the computer program product further comprises:

[0074] code for calculating, by the server, a first evacuation route commencing from one or more user interfaces distributed among respective ones of the one or more zones in the building, the one or more user interfaces including a display device, the evacuation route calculated to traverse a first sequence of respective ones of the one or more zones having a first route danger level;

[0075] code for calculating, by the server, a second evacuation route commencing from one or more user interfaces distributed among respective ones of the one or more zones in the building, the one or more user interfaces including a display device, the evacuation route calculated to traverse a second sequence of respective ones of the one or more zones having a second route danger level;

[0076] code for determining, by the server, that the first evacuation route having the first route danger level is safer than the second evacuation route having the second route danger level; and

[0077] code for transmitting, by the server, a depiction of the first evacuation route to a respective one of the one or more user interfaces for display on the display device as the safest evacuation route. [0078] In accordance with an embodiment described herein, the computer program product further comprises:

[0079] code for calculating, by the server, the safest evacuation route, based at least on one of [1] avoiding where the emergency has been located and is currently located, or [2] avoiding where the emergency is predicted to be located.

[0080] In accordance with an embodiment described herein, the computer program product further comprises:

[0081] wherein when the sensor for detecting an emergency is at least one of a gunshot sensor, a fire sensor, an explosion sensor, a hazardous materials release sensor, a natural gas leak sensor, a smoke sensor, a plumbing flooding sensor, a power failure sensor, or an elevator failure sensor.

[0082] In accordance with an embodiment described herein, a method, comprises:

[0083] receiving, by the server, one or more indications of a detected emergency in a building from one or more sensors distributed among one or more zones in the building, the one or more indications comprising a sensor reading level of the detected emergency and an identity of the one or more sensors;

[0084] determining, by the server, one or more zone danger levels of the detected emergency in the one or more zones, based on the identity of the one or more sensors indicating a location in the one or more zones, and based on the sensor reading level of the detected emergency of the one or more sensors in the one or more zones;

[0085] calculating, by the server, a route danger level of one or more evacuation routes from one or more user interfaces located in the one or more zones in the building toward one or more respective exit locations of the building, the one or more evacuation routes comprising a sequence of one or more distance segments traversing the one or more zones having respective zone danger levels; [0086] determining, by the server, one or more safest evacuation routes of the one or more evacuation routes from the one or more user interfaces respectively located in the one or more zones, the safest evacuation routes having route danger levels that are less than a route danger level of other ones of the one or more evacuation routes from the respective user interfaces;

[0087] transmitting, by the server, a one or more depictions of the safest evacuation routes to the one or more user interfaces in the one or more zones for display on a one or more display devices, wherein the one or more depictions are of the one or more safest routes transmitted to respective ones of the one or more user interfaces, based on the locations of the respective ones of the one or more user interfaces relative to the one or more exit locations and the detected emergency; and

[0088] receiving, by the server, updated indications of the detected emergency in the building from the one or more sensors, and in response, determining updated zone danger levels in the one or more zones, calculating updated route danger levels based on the updated zone danger levels, determining updated safest evacuation routes based on the updated route danger levels, and transmitting updated depictions of the safest evacuation routes to the one or more user interfaces for display.

[0089] In accordance with an embodiment described herein, the method further comprises:

[0090] maintaining, by the server, a record of past indications comprising past instances of sensor reading level of the detected emergency and the identity of the one or more sensors in the one of the one or more zones;

[0091] determining, by the server, weights for the past instances of sensor reading level of the detected emergency of the one or more sensors in the one or more zones, the weights based on how frequently and recently the past instances of sensor reading level of the detected emergency have been detected by the one or more sensors;

[0092] calculating, by the server, a past sensor danger level of the detected emergency in the one or more zones, based on a sum of products of the weights for the past instances of sensor reading level times the past sensor reading levels;

[0093] calculating, by the server, a past-present-zone danger level of the one or more zones by adding the received sensor reading level and the past sensor danger level of the one or more zones;

[0094] calculating, by the server, a past-present route danger level of one or more evacuation routes from one or more user interfaces located in the one or more zones in the building, based on the past-present-zone danger level of the one or more zones; and

[0095] determining, by the server, the safest evacuation route of the one or more evacuation routes from the one or more user interfaces located in the one or more zones, based on the past-present route danger level of one or more evacuation routes;

[0096] determining, by the server, a predicted sensor danger level of the detected emergency in the one or more sensors, based on a predicted rate of movement of the emergency or on conditions of the zones;

[0097] determining, by the server, a predicted zone danger level of the detected emergency in the one or more zones, based on the predicted sensor danger level of the detected emergency of the one or more sensors in the one or more zones;

[0098] calculating, by the server, a past-present-predicted zone danger level of the one or more zones by adding the past-present zone danger level and the predicted zone danger level of the one or more zones; and

[0099] calculating, by the server, the safest evacuation route based on the past-present-predicted zone danger level of the one or more zones.

[00100] In accordance with an embodiment described herein, the method further comprises:

[00101] determining, by the server, a predicted sensor danger level of the detected emergency in the one or more sensors, based on a predicted rate of movement of the emergency or on conditions of the zones; [00102] determining, by the server, a predicted zone danger level of the detected emergency in the one or more zones, based on the predicted sensor danger level of the detected emergency of the one or more sensors in the one or more zones;

[00103] calculating, by the server, a present-predicted zone danger level of the one or more zones by adding the present zone danger level and the predicted zone danger level of the one or more zones; and

[00104] calculating, by the server, the safest evacuation route based on the present-predicted zone danger level of the one or more zones.

[00105] In accordance with an embodiment described herein, the method further comprises:

[00106] calculating, by the server, a first evacuation route commencing from one or more user interfaces distributed among respective ones of the one or more zones in the building, the one or more user interfaces including a display device, the evacuation route calculated to traverse a first sequence of respective ones of the one or more zones having a first route danger level;

[00107] calculating, by the server, a second evacuation route commencing from one or more user interfaces distributed among respective ones of the one or more zones in the building, the one or more user interfaces including a display device, the evacuation route calculated to traverse a second sequence of respective ones of the one or more zones having a second route danger level;

[00108] determining, by the server, that the first evacuation route having the first route danger level is safer than the second evacuation route having the second route danger level; and

[00109] transmitting, by the server, a depiction of the first evacuation route to a respective one of the one or more user interfaces for display on the display device as the safest evacuation route.

[00110] In accordance with an embodiment described herein, the method further comprises: [00111] wherein when the sensor for detecting an emergency is at least one of a gunshot sensor, a fire sensor, an explosion sensor, a hazardous materials release sensor, a natural gas leak sensor, a smoke sensor, a plumbing flooding sensor, a power failure sensor, or an elevator failure sensor.

[00112] In accordance with an embodiment described herein, the server further comprises:

[00113] wherein the server calculates the route danger level as a sum of products of the one or more distance segments times the respective zone danger levels of the one or more zones traversed.

[00114] The resulting method, apparatus, system, and computer program product integrates building automation emergency response and occupant evacuation systems into building automation systems to dynamically direct occupants to a safe location in the event of an emergency.

BRIEF DESCRIPTION OF THE DRAWINGS

[00115] A more detailed description of the disclosure, briefly summarized above, may be had by reference to various embodiments, some of which are illustrated in the appended drawings. While the appended drawings illustrate select embodiments of this disclosure, these drawings are not to be considered limiting of its scope, for the disclosure may admit to other equally effective embodiments.

[00116] FIG. 1 is an example network and functional block diagram of a building automation emergency response and occupant evacuation system integrated into a building automation system, having sensor inputs directed to the server, to dynamically guide occupants to a safe location in the event of an emergency, according to an embodiment of the disclosure.

[00117] FIG. 1A is an example network and functional block diagram of another embodiment of the building automation emergency response and occupant evacuation system integrated into the building automation system of FIG. 1, having the sensor inputs directed to the user interface, according to an embodiment of the disclosure.

[00118] FIG. IB is an example network and functional block diagram of another embodiment of the building automation emergency response and occupant evacuation system integrated into the building automation system of FIG. 1, wherein the evacuation route is displayed on the occupant’s mobile wireless device, according to an embodiment of the disclosure.

[00119] FIG. 2 is an example plan view of the floor plan of the building, including sensors and user interfaces distributed in the building, according to an embodiment of the disclosure.

[00120] FIG. 2A is an example plan view of the floor plan of the building of FIG. 2, showing zones in the building and the sensors and user interfaces distributed among the zones, according to an embodiment of the disclosure.

[00121] FIG. 2B is an example plan view of the floor plan of the building of FIG. 2 A, showing three possible evacuation routes for Zone(B), according to an embodiment of the disclosure. [00122] FIG. 2C is an example plan view of the floor plan of the building of FIG. 2 A, showing three possible evacuation routes for Zone(J), according to an embodiment of the disclosure.

[00123] FIG. 3 A is an example display on the user interface UI(2) in Zone(B) showing the floor plan of the building of FIG. 2A, and showing the safest evacuation route ROUTE(B3) from Zone(B), to avoid the emergency detected in Zone (A) and Zone(N).

[00124] FIG. 3B is an example display on the user interface UI(6) in Zone(F) showing the floor plan of the building of FIG. 2A, and showing the safest evacuation route ROUTE(F2) from Zone(F), to avoid the emergency detected in Zone (A) and Zone(N).

[00125] FIG. 3C is an example flow diagram of an example method for computing past- present zone danger level of a zone, according to an embodiment of the disclosure.

[00126] FIG. 4 is an example plan view of the floor plan of the building of FIG. 2, showing a fire prediction map for fire in Zone(A) with 30-second time increments for spreading the fire to other zones, according to an embodiment of the disclosure.

[00127] FIG. 4A is an example display on the user interface UI(2) in Zone(B) showing the display by user interface UI(2) of the safest evacuation ROUTE(B3) from Zone(B) at 30 seconds into the future, according to an embodiment of the disclosure.

[00128] FIG. 4B is an example display on the user interface UI(2) in Zone(B) showing the display by user interface UI(2) of the safest evacuation ROUTE(B2) from Zone(B) at 60 seconds into the future, according to an embodiment of the disclosure.

[00129] FIG. 4C is an example flow diagram of an example method for computing present-predicted (future) zone danger level of a zone, according to an embodiment of the disclosure.

[00130] FIG. 4D is an example flow diagram of an example method for computing past- present-predicted (future) zone danger level of a zone, according to an embodiment of the disclosure.

[00131] FIG. 5 is an example plan view of the floor plan of the building of FIG. 2, showing an active shooter prediction map for a gunman in Zone(A) with 3 -minute time increments for movements of the gunman to other zones, according to an embodiment of the disclosure. [00132] FIG. 5A is an example display on the user interface UI(2) in Zone(B) showing the display by user interface UI(2) of the active shooter prediction map, showing the safest evacuation ROUTE(B2) from Zone(B) at 6 minutes into the future, according to an embodiment of the disclosure.

[00133] FIG. 6 is an example flow diagram of a method performed by the example building automation emergency response and occupant evacuation system of FIG. 1, according to an embodiment of the disclosure.

[00134] Identical reference numerals have been used, where possible, to designate identical elements that are common to the figures. However, elements disclosed in one embodiment may be beneficially utilized on other embodiments without specific recitation.

DETAILED DESCRIPTION

[00135] What is needed is a way to integrate building automation emergency response and occupant evacuation systems into building automation systems to dynamically direct occupants to a safe location in the event of an emergency.

[00136] FIG. 1 is an example network and functional block diagram of a building automation emergency response and occupant evacuation system 160 integrated into a building automation system 150 of a building, such as an office building, a school building, a theater, or the like. The building automation emergency response and occupant evacuation system 160 may be computer program code residing in at least one memory 132 of the emergency server 130, which when executed by operation of at least one processor in the emergency server 130, carries out the operations of the building automation emergency response and occupant evacuation system 160. In another embodiment, the building automation emergency response and occupant evacuation system 160 may be logic blocks implemented by computer hardware logic in the emergency server 130, which may carry out the functions specified by the logic blocks. The emergency server 130 may reside in the same building as the building automation system 150 or it may be a cloud server accessed over a communications medium.

[00137] In the embodiment of FIG. 1, the emergency server 130 is connected by wired or wireless links to one or more sensors 124 distributed throughout the building, such as gunshot sensors 120A, fire sensors 122A, explosion sensors 120B, hazardous materials release sensors 122B, natural gas leak sensors 120C, smoke sensors 122C, and other types of sensors 124, such as plumbing failure or flooding sensors, power failure sensors, elevator failure sensors, and the like. The building automation emergency response and occupant evacuation system 160 in the emergency server 130 determines that an emergency has occurred in the building, based on detection of the emergency by one or more of the sensors 124 distributed at respective locations in the building. FIG. 2 is an example plan view of the floor plan of the building, including the sensors 124 labeled S(l), S(2), ... S(37), distributed throughout the building. The building automation emergency response and occupant evacuation system 160 in the emergency server 130, receives present indications of a detected emergency in the building from one or more sensors 124. The present indications comprise a present sensor reading level of the detected emergency and an identity of the one or more sensors. The building automation emergency response and occupant evacuation system 160 may continuously monitor the one or more sensors 124 for present indications of a detected emergency in the building.

[00138] In the embodiment of FIG. 1, the emergency server 130 is connected by communication links such as ethemet, bacnet, or other wired or wireless links to one or more user interfaces 100 distributed throughout the building. The user interfaces may include, for example, thermostats 102 connected to the building’s HVAC system 110, the thermostats including a two-dimensional pictorial display device 107 and a processor and memory 108. Other example user interfaces 100 may include public announcement devices connected to the building’s public address system and including a two- dimensional pictorial display device, a processor and memory, televised advertising displays connected to the building’s communication system, televised news broadcasting displays connected to the building’s communication system, or other wired or wireless display devices including a two-dimensional pictorial display device, a processor and memory connected to the building’s communication system. FIG. 2 is an example plan view of the floor plan of the building, including the user interfaces 100 labeled UI(1), UI(2), ... UI(11), distributed throughout the building. In the event of an emergency, the building automation emergency response and occupant evacuation system 160 calculates a respective evacuation route commencing from the one or more user interfaces 100 distributed throughout the building, toward a safe exit. The user interfaces include a display device 107. The building automation emergency response and occupant evacuation system 160 transmits a depiction of an evacuation route, such as shown in FIG. 3 A and FIG. 3B, to the user interfaces 100 for display on the display device 107.

[00139] FIG. 1 A is an example network and functional block diagram of another embodiment of the building automation emergency response and occupant evacuation system 160 integrated into the building automation system 150 of FIG. 1, having the sensor 124 inputs directed to the user interface 100, such as thermostats 102, according to an embodiment of the disclosure. The thermostats 102 may be connected to the building’s HVAC system 110. The thermostats 102 receive present indications of a detected emergency in the building from one or more sensors 124, comprising a present sensor reading level of the detected emergency and an identity of the one or more sensors. The thermostats report the emergency to the building automation emergency response and occupant evacuation system 160. The building automation emergency response and occupant evacuation system 160 transmits a depiction of an evacuation route, such as shown in FIG. 3 A and FIG. 3B, to the user interfaces 100 for display on the display device 107.

[00140] FIG. IB is an example network and functional block diagram of another embodiment of the building automation emergency response and occupant evacuation system 160 integrated into the building automation system 150 of FIG. 1, wherein the evacuation route is displayed on the occupant’s mobile wireless device 170, according to an embodiment of the disclosure. The building automation emergency response and occupant evacuation system 160 transmits, for example over a wireless local area network (WLAN) 152 to a WLAN receiver 174, a depiction of an evacuation route, such as shown in FIG. 3 A and FIG. 3B, to the occupant’s mobile wireless device 170 for display on the display 104 of the wireless device. The occupant’s mobile wireless device 170 may be triggered to display the depiction of the evacuation route when it is proximate to the user interface 100, by means of a short-range wireless beacon, such as a Bluetooth beacon, transmitted from a Bluetooth beacon transmitter 109 in the user interface 100, to a Bluetooth receiver 172 in the occupant’s mobile wireless device 170. When the occupant’s mobile wireless device 170 is proximate to the user interface 100 in a particular zone, the user interface 100 senses the presence of the occupant’s device 170 over the Bluetooth link and, in response, signals the building automation emergency response and occupant evacuation system 160 to transmit to the occupant’s mobile wireless device 170 the same depiction of the evacuation route that is being sent to the user interface 100 in that particular zone.

[00141] FIG. 2A is an example plan view of the floor plan of the building of FIG. 2, showing zones in the building and the sensors and user interfaces distributed among the zones, according to an embodiment of the disclosure. The zones labeled Zone(A) through Zone(N) may be defined on the floor plan of FIG. 2 at the time of commissioning the building automation emergency response and occupant evacuation system 160 integrated into the building automation system 150 for the building. Each of the zones may include one or more sensors 124 and one or more user interfaces 100. The positioning of the zones, sensors 124 and user interfaces 100 in the building may be recorded in the building automation emergency response and occupant evacuation system 160 at the time of commissioning. PAST-PRESENT ZONE DANGER LEVEL

[00142] The building automation emergency response and occupant evacuation system 160 maintains a record of past received indications comprising past instances of sensor reading levels of the detected emergency and the identity of the sensors 124 producing the reading level in a zone. The zone that includes a particular sensor 124 is determined from a look-up table of unique identities for the respective sensors 124 and the identity of a zone where a respective sensor is located. The building automation emergency response and occupant evacuation system 160 determines a past-present zone danger level of the detected emergency in a zone, based on calculating a sum of products of weight values for the past instances of the sensor reading levels times the past sensor reading levels.

The weight values for the past instances of sensor reading level may be based on how frequently and recently the past instances of sensor reading level have been detected by the sensors. The past-present zone danger level of a zone is calculated by adding the present sensor reading level and the past sensor reading levels of the zone. The following Table A shows an example of a record of past instances of the sensor reading level SA[t] at time “t” for sensors s(l) and S(2) in Zone(A). The time t starts at t=0 and continues as t=l, then t=2, etc. The table also shows an example calculation of the sensor danger values for S(l) and S(2) as sums of products of the sensor reading times an example weight value “W”. The table also shows an example calculation of the danger value for Zone(A) as a sum of the danger values for the fire sensor S(l) and the smoke sensor S(2) in Zone(A):

Table A

[00143] To more clearly show weighting of sensor types in Table A, weights (W) may be applied to the total for each sensor. This is a way of expressing that type of danger is worse than another. For example, if fire is considered to be twice as dangerous as smoke, then S(l) could have a weight of Ws=0.5 for smoke and S(0) would have a weight of Wf=l for fire. In Table A, this would give:

Zone(A) Danger Sum of Sensors = (150 * Wf) + (100 * Ws) = Danger (at time t=l) Zone(A) Danger Sum of Sensors = (150 * 1) + (100 * 0.5) = 200 (at time t=l)

[00144] A record is kept of each zone in which an emergency sensor has been triggered. Danger in a zone may be determined by number of sensor activations weighted by how long ago they occurred. Given the type of sensor, a scale factor or weight may be applied to the sensor danger value, for example gunshots are more dangerous than a fire emergency. The sensor readings for fire emergencies or gas leak emergencies may provide an analog sensor reading based on the severity of the emergency. The sensor readings for gunshot emergencies may provide an analog sensor reading based on a decibel level indicating a caliber of the gun. The example weight value may be a function that may be tuned by a systems installer or by data accumulation over time.

[00145] FIG. 2B is an example plan view of the floor plan of the building of FIG. 2 A, showing three possible evacuation routes labeled ROUTE(Bl), ROUTE(B2), and ROUTE(B3) for Zone(B), according to an embodiment of the disclosure. Similarly, FIG. 2C is an example plan view of the floor plan of the building of FIG. 2A, showing two possible evacuation routes labeled ROUTE(Fl) and ROUTE(F2) for Zone(F), according to an embodiment of the disclosure. The possible evacuation routes may be defined on the floor plan of FIG. 2 at the time of commissioning the building automation emergency response and occupant evacuation system 160 integrated into the building automation system 150 for the building. As part of the definition of each route, the length of the component segments, such as Dl, D2, and D3 for Route(B3) from Zone(B) in FIG. 2B, is recorded and will be used during an emergency to determine the safest evacuation route. The following Table B shows an example of a record of the possible evacuation routes labeled ROUTE(Bl), ROUTE(B2), and ROUTE(B3) for Zone(B) in FIG. 2B. The length of the component segments, such as Dl, D2, and D3, is shown in meters.

Table B

[00146] During a detected emergency, as discussed above, the past-present zone danger level of a zone for the zones in the building is calculated by adding the present sensor reading level and the past sensor reading levels of the zone. In this example, fire has been detected by the sensor S(l) in Zone(A) and smoke has been detected by sensor S(36) in Zone(N). The building automation emergency response and occupant evacuation system 160 calculates a respective evacuation route commencing from the user interfaces 100 distributed among the zones in the building. The evacuation route is calculated to traverse one or more zones having respective zone danger levels. A route danger level is computed as a sum of products of distance segments along the route and the respective zone danger level of the zones traversed by the segments. The safest evacuation route is the route that has a minimum route danger level in reaching a respective safe exit location of the building. Each proposed evacuation route commencing from a given zone is examined by calculating a route danger level as the sum of the products of the length of the component segments, such as Dl, D2, and D3 for Route(B3) from Zone(B), times the zone danger level for each respective zone through which the segment passes in FIG. 2B. The following Table C shows an example calculation of the route danger level during the example emergency to determine the safest evacuation route commencing from Zone(B), from among the three possible evacuation routes: ROUTE(Bl), ROUTE(B2), and ROUTE(B3) in FIG. 2B.

Table C

[00147] The Route(B3) has the smallest route danger level for the sum of the products of the length of the component segments, Dl, D2, and D3 for Route(B3) from Zone(B), times the zone danger level for each respective zone Zone(N), Zone(F), and Zone(O) through which the respective segments pass in FIG. 2B. Thus, ROUTE(B3) is the safest evacuation route commencing from Zone(B), to avoid the fire emergency detected in Zone (A) and smoke emergency in Zone(N), according to an embodiment of the disclosure. FIG. 3 A is an example display on the user interface UI(2) in Zone(B) showing of the floor plan of the building of FIG. 2A, and showing the safest evacuation route ROUTE(B3) from Zone(B), to avoid the emergency detected in Zone (A) and Zone(N). FIG. 3C is an example flow diagram of an example method for computing past-present zone danger level of a zone, according to an embodiment of the disclosure.

[00148] Continuing with the example, fire has been detected by the sensor S(l) in Zone(A) and smoke has been detected by sensor S(36) in Zone(N). For an evacuation commencing from Zone(F), each proposed evacuation route is examined by calculating the route danger level as a sum of the products of the length of the component segments, such as Dl, D2, and D3 for Route(Fl) from Zone(F), times the zone danger level for each respective zone through which the segment passes. The following Table D shows an example calculation of the route danger level during the example emergency to determine the safest evacuation route commencing from Zone(F), from among the two possible evacuation routes: ROUTE(Fl) and ROUTE(F2).

Table D

[00149] The Route(F2) has the smallest route danger level for the sum of the products of the length of the component segment Dl for Route(F2) from Zone(F), times the zone danger level for Zone(O) through which the respective segment passes. Thus, ROUTE(F2) is the safest evacuation route commencing from Zone(F), to avoid the fire emergency detected in Zone (A) and smoke emergency in Zone(N), according to an embodiment of the disclosure. FIG. 3B is an example display on the user interface UI(6) in Zone(F) showing of the floor plan of the building of FIG. 2 A, and showing the safest evacuation route ROUTE(F2) commencing from Zone(F), to avoid the emergency detected in Zone (A) and Zone(N).

[00150] Continuing with the example, fire has been detected by the sensor S(l) in Zone(A) and smoke has been detected by sensor S(36) in Zone(N). An occupant in the office in Zone(B) may begin an evacuation by viewing the user interface UI(2) in Zone(B) showing the safest evacuation route ROUTE(B3) commencing from Zone(B), to avoid the emergency detected in Zone (A) and Zone(N). The occupant follows ROUTE(B3), which leads into Zone(F). The occupant may continue the evacuation by viewing the user interface UI(6) in Zone(F) showing the safest evacuation route ROUTE(F2) commencing from Zone(F), to the exit at the back door of the building. The building automation emergency response and occupant evacuation system 160 provides to each user interface 100 in each respective zone of the building, a respective depiction of the evacuation route commencing from the respective zone, which provides an occupant viewing each respective user interface along the evacuation route, with a situational awareness that is unique to that respective zone.

[00151] Different safest routes are transmitted to the different user interfaces, since the user interfaces each have their own safest route based on their location relative to the exits and the emergency. The server transmits one or more depictions of the safest evacuation routes to the one or more user interfaces in the one or more zones for display on one or more display devices. The one or more depictions are of the one or more safest routes transmitted to respective ones of the one or more user interfaces, based on the locations of the respective ones of the one or more user interfaces relative to the one or more exit locations and the detected emergency.

[00152] The building automation emergency response and occupant evacuation system 160 may receive updated indications of the detected emergency in the building from the one or more sensors 124. In response, the building automation emergency response and occupant evacuation system 160 determines updated zone danger levels in the one or more zones, calculates updated route danger levels based on the updated zone danger levels, determines updated safest evacuation routes based on the updated route danger levels, and transmits the updated depictions of the safest evacuation routes to the one or more user interfaces 100 for display.

[00153] FIG. 3C is an example flow diagram of an example method for computing past- present zone danger level of a zone, according to an embodiment of the disclosure. When danger is detected in any zone “X”, for each zone in the building, each sensor “Y” is read. The building automation emergency response and occupant evacuation system 160 determines a past-present zone danger level of the detected emergency in a zone “X”, based on calculating a sum of products of weight values for the past instances of the sensor reading levels times the past sensor reading levels. The weight values for the past instances of sensor reading level may be based on how frequently and recently the past instances of sensor reading level have been detected by the sensors. The past-present zone danger level of a zone is calculated by adding the present sensor reading level and the past sensor reading levels of the zone.

[00154] The building automation emergency response and occupant evacuation system 160 calculates a respective evacuation route “Z” commencing from the user interfaces 100 distributed among the zones in the building. The evacuation route is calculated to traverse one or more zones having respective zone danger levels. A route danger level is computed as a sum of products of distance segments along the route and the respective zone danger level of the zones traversed by the segments. The safest evacuation route is the route that has a minimum route danger level in reaching a respective safe exit location of the building.

PRESENT-PREDICTED ZONE DANGER LEVEL

[00155] The building automation emergency response and occupant evacuation system 160 may determine a predicted sensor danger level of the detected emergency in the one or more sensors, based on a predicted rate of movement of the emergency or on structural or other conditions of the zones. For example, emergencies such as fire, smoke, hazardous materials release, natural gas leaks, and flooding naturally expand, sometimes quickly, from a zone of initial occurrence to adjacent zones. For example, in FIG. 2B, an initial fire emergency detected by the fire sensor S(l) in Zone(A) has produced an initial smoke emergency detected by the smoke sensor S(36) in the adjacent Zone(N). It is predictable that, in a short time, the heat and flames from the fire emergency in Zone(l) will spread to the adjacent Zone(N) and become a more dangerous fire emergency in Zone(N). The building automation emergency response and occupant evacuation system 160 determines a predicted zone danger level in the adjacent Zone(N), based the detected emergency in the zone of initial occurrence, Zone(A). The likelihood of the spreading of a particular type of emergency, such as fire, smoke, hazardous materials release, natural gas leaks, or flooding, may be characterized by a predicted zone danger level that may be stored in the system’s memory 132 at the time of commissioning the building automation emergency response and occupant evacuation system 160 or that may be tuned by a systems installer or by data accumulation over time. The predicted zone danger level for a fire emergency, for example, may be based on the relative flammability of structural materials in an adjacent zone or the proximity of ventilation fans to an adjacent zone. The building automation emergency response and occupant evacuation system 160 calculates a present-predicted zone danger level of an adjacent zone, such as Zone(N), by adding the present zone danger level of the adjacent zone and the predicted zone danger level of the adjacent zone.

[00156] Continue with the example of the fire detected by the sensor S(l) in Zone(A) and smoke detected by sensor S(36) in Zone(N). For an evacuation commencing from Zone(B), each proposed evacuation route commencing from Zone(B) is examined by calculating a route danger level as the sum of the products of the length of the component segments, such as Dl, D2, and D3 for Route(B3) from Zone(B), times the zone danger level for each respective zone through which the segment passes in FIG. 2B.

[00157] FIG. 4 is an example plan view of the floor plan of the building of FIG. 2, showing a fire prediction map for fire in Zone(A) with 3 -minute time increments for the fire to spread to the other zones, according to an embodiment of the disclosure. At the time of commissioning the building automation emergency response and occupant evacuation system 160, the fire prediction map of FIG. 4 is compiled and stored in memory 132, of the predicted sensor danger level in each of the zones (A) through (N) for a fire starting in Zone(A). The fire prediction map is based on structural or other conditions of each of the zones (A) through (N) where each sensor is located. A total of 14 different fire prediction maps are compiled and stored, one for each of the zones (A) through (N) where a different fire is simulated to originate. Each zone on the fire prediction map of FIG. 4 has an encircled label indicating the number of minutes it is predicted for a spreading fire to reach the zone since the instant of the origin of the fire in Zone(A).

[00158] At the time of 3 minutes after the fire starts in Zone(A), the fire is predicted to spread to the adjacent Zone(N). The building automation emergency response and occupant evacuation system 160 calculates a present-predicted zone danger level of Zone(N), by adding the present zone danger level of Zone(N) (smoke = 100) and the predicted zone danger level of Zone(N) at 3 minutes into the future (fire = 100). In this example, the predicted zone danger level of Zone(N) at 3 minutes into the future is 100, because it is adjacent to Zone(A) where there is presently a fire emergency. The following Table E shows an example calculation of the route danger level during the example emergency at 3 minutes into the future, to determine the safest evacuation route commencing from Zone(B), from among the three possible evacuation routes: ROUTE(Bl), ROUTE(B2), and ROUTE(B3) in FIG. 2B.

Table E - At 30 Minutes into the Future

[00159] For the adjacent Zone(N), the building automation emergency response and occupant evacuation system 160 calculates a present-predicted zone danger level of Zone(N), by adding the present zone danger level of Zone(N) (smoke = 100) and the predicted zone danger level of Zone(N) (fire at 3 minutes = 100). In this example, the predicted zone danger level of Zone(N) at 3 minutes is 100. The Route(B3) has the smallest route danger level for the sum of the products of the length of the component segments, Dl, D2, and D3 for Route(B3) from Zone(B), times the zone danger level at 3 minutes for each respective zone Zone(N), Zone(F), and Zone(O) through which the respective segments pass in FIG. 2B. Thus, ROUTE(B3) is the safest evacuation route commencing from Zone(B), to avoid the fire emergency detected in Zone (A) and the potential of fire emergency, as well as smoke emergency, in Zone(N), according to an embodiment of the disclosure. FIG. 4A is an example display on the user interface UI(2) in Zone(B) showing the display by user interface UI(2) of the safest evacuation ROUTE(B3) from Zone(B) at 3 minutes into the future, according to an embodiment of the disclosure. In this situation, the user may take ROUTE(B3) through Zone(N) with a higher danger score of 600, because the route only passes through a short distance D1 through Zone(N) and therefore gives an overall lower danger score for the route. Note that at the time of 3 minutes, a fire begins in the Zone(B), indicating the increasing urgency of evacuation.

[00160] At the time of 6 minutes after the fire starts in Zone(A), the fire prediction map indicates the fire is predicted to have spread to zones (B), ( C), (D), (F), (M), and (N).

The building automation emergency response and occupant evacuation system 160 calculates a present-predicted zone danger level of Zone(F), by adding the present zone danger level of Zone(F) (= 0) and the predicted zone danger level of Zone(F) (fire = 100) at 6 minutes into the future. In this example, the predicted zone danger level of Zone(F) is 100 at 6 minutes after the fire starts in Zone(A), which raises the route danger level for ROUTE(B3) 1200. The ROUTE(B3) is no longer the safest evacuation route, because fire is predicted to have spread to Zone(F) by 6 minutes. The ROUTE(B2) will be the safest evacuation route, by 6 minutes after the fire starts in Zone(A). The following Table F shows an example calculation of the route danger level during the example emergency at 6 minutes into the future, to determine the safest evacuation route commencing from Zone(B), from among the three possible evacuation routes: ROUTE(Bl), ROUTE(B2), and ROUTE(B3) in FIG. 2B.

Table F - At 60 Minutes into the Future

[00161] For the Zone(F), the building automation emergency response and occupant evacuation system 160 calculates a present-predicted zone danger level of Zone(F), by adding the present zone danger level of Zone(F) (= 0) and the predicted zone danger level of Zone(F) (fire at 6 minutes = 100). The Route(B2) has the smallest route danger level for the sum of the products of the length of the component segments, Dl, D2, and D3 for Route(B2) from Zone(B), times the zone danger level at 6 minutes for each respective zone Zone(N), Zone(L), and Zone(O) through which the respective segments pass in FIG. 2B. Thus, ROUTE(B2) is the safest evacuation route commencing from Zone(B) at 6 minutes into the future, to avoid the fire emergency detected in Zone (A) and the fire emergency in Zone(F), according to an embodiment of the disclosure. FIG. 4B is an example display on the user interface UI(2) in Zone(B) showing the display by user interface UI(2) of the safest evacuation ROUTE(B2) from Zone(B) at 6 minutes into the future, according to an embodiment of the disclosure. In this situation, the user may take ROUTE(B2) through Zone(N) with a higher danger score of 600, because the route only passes through a short distance Dl through Zone(N) and therefore gives an overall lower danger score for the route. Note that at the time of 6 minutes, a fire is in the Zone(B), indicating the urgency of evacuation.

[00162] In an embodiment, the building automation emergency response and occupant evacuation system 160 may determine the safest route by calculating the route dangers over time (for example in increments of 1 minute) and add them all together to get a total for each route. The danger of a zone may change as the occupant is passing through the zone. The change in danger may be determined by observing the occupant’s movement speed and simulating the occupant’s motion through the path/zones over time and calculating the danger at each point in time along a path through the zones. [00163] A predicted sensor danger level of the detected emergency for a sensor may be based on structural or other conditions of the zone where the sensor is located. For example, the building may have been constructed in stages, with the back section of the building having been constructed of wood and wall board materials, which are more combustible than brick and block construction in other parts of the building. At the time of commissioning the building automation emergency response and occupant evacuation system 160, a table is compiled and stored in memory 132 of the predicted sensor danger level in the zones, based on structural or other conditions of the zone where each sensor is located. The following example Table G stored in memory 132, correlates the predicted sensor danger level in the zones Zone(G), Zone(H), and Zone(L) that are constructed of combustible wood and wall board materials. Other zones Zone(D), and Zone(E) are also shown in Table G, which are located in portions of the building that are not constructed of combustible materials, and thus have a low value for the predicted sensor danger level.

The following Table G is used when the detected emergency is a fire emergency.

Table G-Zone Combustibility Conditions

[00164] Continue with the example of the fire detected by the sensor S(l) in Zone(A) and smoke detected by sensor S(36) in Zone(N). For an evacuation commencing from Zone(B), each proposed evacuation route commencing from Zone(B) is examined by calculating a route danger level as the sum of the products of the length of the component segments, such as Dl, D2, and D3 for Route(B2) from Zone(B), times the zone danger level for each respective zone through which the segment passes in FIG. 2B. For the Zone(L) through which ROUTE(B2) passes, the building automation emergency response and occupant evacuation system 160 calculates a present-predicted zone danger level of Zone(L), by adding the present zone danger level of Zone(L) and the predicted zone danger level of Zone(L). In this example, the predicted zone danger level of Zone(L) is 100 because it is listed in Table G as constructed of combustible materials. The following Table H shows an example calculation of the route danger level during the example emergency to determine the safest evacuation route commencing from Zone(B), from among the three possible evacuation routes: ROUTE(Bl), ROUTE(B2), and ROUTE(B3) in FIG. 2B.

Table H - Effect of Combustible Zones

[00165] For the Zone(L), the building automation emergency response and occupant evacuation system 160 calculates a present-predicted zone danger level of Zone(L), by adding the present zone danger level of Zone(L) and the predicted zone danger level of Zone(L) in Table G due to combustibility of the zone. The Route(B2) route danger level is calculated as the sum of the products of the length of the component segments, Dl, D2, and D3 for Route(B2) from Zone(B), times the zone danger level for each respective zone Zone(N), Zone(L), and Zone(O) through which the respective segments pass in FIG. 2B. In this example, the predicted zone danger level of Zone(L) is 100 in Table G, which raises the route danger level of ROUTE(B2) to 1500 in Table H. The example predicted zone danger levels for zones in Table G may be a function that may be tuned by a systems installer or by data accumulation over time.

[00166] The Route(B3) has the smallest route danger level in Table H for the sum of the products of the length of the component segments, Dl, D2, and D3 for Route(B3) from Zone(B), times the zone danger level for each respective zone Zone(N), Zone(F), and Zone(O) through which the respective segments pass in FIG. 2B. Thus, ROUTE(B3) is the safest evacuation route commencing from Zone(B), to avoid the fire emergency detected in Zone (A) and the potential of fire emergency, as well as smoke emergency, in Zone(N), according to an embodiment of the disclosure. FIG. 3 A is an example display on the user interface UI(2) in Zone(B) showing of the floor plan of the building of FIG. 2A, and showing the safest evacuation route ROUTE(B3) from Zone(B), to avoid the emergency detected in Zone (A) and Zone(N).

[00167] For certain types of threats, there are logical paths the threat is likely to proceed on. For non human threats such as fire and gas leaks, it may be assumed that they will spread into surrounding zones, factoring in the material of the zones and any barriers. A speed factor may be applied during commissioning to change the rate of spread based on the building materials and ventilation connections. Danger may be calculated into the future for T seconds (t=0 ... t=T). At each point in time (t), the system may determine the location of the danger along a vector of movement and if the danger is expected to enter a zone, the zone danger level may be increased.

PAST-PRESENT-PREDICTED ZONE DANGER LEVEL

[00168] In example embodiments, the building automation emergency response and occupant evacuation system 160 determines a predicted sensor danger level of the detected emergency in the one or more sensors, based on a predicted rate of movement of the emergency or on structural or other conditions of the zones, as previously discussed. The building automation emergency response and occupant evacuation system 160 determines a predicted zone danger level of the detected emergency in the one or more zones, based on the predicted sensor danger level of the detected emergency of the one or more sensors in the one or more zones, as previously discussed. In this embodiment, the building automation emergency response and occupant evacuation system 160 calculates a past-present-predicted zone danger level of the one or more zones by adding the past- present zone danger level and the predicted zone danger level of the one or more zones. The building automation emergency response and occupant evacuation system 160 then calculates the safest evacuation route as the minimum value route danger level for the one or more evacuation routes based on the past-present-predicted zone danger level of the one or more zones.

[00169] In example embodiments, the building automation emergency response and occupant evacuation system 160 calculates the safest evacuation route, based at least on one of [1] avoiding where the emergency has been located and is currently located, or [2] avoiding where the emergency is predicted to be located.

[00170] FIG. 4C is an example flow diagram of an example method for computing present-predicted (future) zone danger level of a zone, according to an embodiment of the disclosure. When danger is detected in any zone, for each zone “X” in the building, each sensor “Y” is read. During the emergency, prior movement of the threat “Q” may be used to predict future movement of the location of that threat entering zone “X” at a time “T”. Add the danger to future predictions of the zone “X” at time “T” for the threat “Q”. The zone “X” danger level is calculated by adding the present sensor reading level and the future predictions of the zone “X” at time “T” for the threat “Q”.

[00171] The building automation emergency response and occupant evacuation system 160 calculates a respective evacuation route “Z” commencing from the user interfaces 100 distributed among the zones in the building. The evacuation route is calculated to traverse one or more zones having respective zone danger levels. A route danger level is computed as a sum of products of distance segments along the route and the respective zone danger level of the zones traversed by the segments. The safest evacuation route is the route that has a minimum route danger level in reaching a respective safe exit location of the building.

[00172] FIG. 4D is an example flow diagram of an example method for computing past- present-predicted (future) zone danger level of a zone, according to an embodiment of the disclosure. When danger is detected in any zone “X”, for each zone in the building, each sensor “Y” is read. The building automation emergency response and occupant evacuation system 160 determines a past-present zone danger level of the detected emergency in a zone “X”, based on calculating a sum of products of weight values for the past instances of the sensor reading levels times the past sensor reading levels. The weight values for the past instances of sensor reading level may be based on how frequently and recently the past instances of sensor reading level have been detected by the sensors. The past-present zone danger level of a zone is calculated by adding the present sensor reading level and the past sensor reading levels of the zone. During the emergency, prior movement of the threat “Q” may be used to predict future movement of the location of that threat entering zone “X” at a time “T”. Add the danger to future predictions of the zone “X” at time “T” for the threat “Q”. The zone “X” danger level is calculated by adding the past-present zone danger level and the future predictions of the zone “X” at time “T” for the threat “Q”.

[00173] The building automation emergency response and occupant evacuation system 160 calculates a respective evacuation route “Z” commencing from the user interfaces 100 distributed among the zones in the building. The evacuation route is calculated to traverse one or more zones having respective zone danger levels. A route danger level is computed as a sum of products of distance segments along the route and the respective zone danger level of the zones traversed by the segments. The safest evacuation route is the route that has a minimum route danger level in reaching a respective safe exit location of the building.

PREDICTED ZONE DANGER LEVEL FROM HUMAN THREATS

[00174] For human threats, it may be more likely that they will proceed in a given direction in search of some target or goal and will move along human traversable paths provided in the building’s floor plan during commissioning. The likelihood of the human threat traversing a possible path may be determined by each possible path’s similarity in its direction to a predicted direction of travel by the human threat. During the emergency, prior movement of the human threat may be used to predict future movement of the location of that threat. In predicting where a human threat may be located in the future, the system may simulate future situations and display evacuation routes according to present and predicted threats. For simulation of a predicted danger, an algorithm for calculating the safest evacuation route may consider time (t) at each step of the calculation. An assumption may be made as to the movement speed of the occupants during an evacuation. The time needed by an occupant to reach a given zone along the evacuation route may be used as a weight value to be multiplied times a given zone danger level. A safest evacuation route will be based on a minimum route danger level among the possible evacuation routes.

[00175] FIG. 5 is an example plan view of the floor plan of the building of FIG. 2, showing an active shooter prediction map for a gunman entering the reception area in Zone(A) with 3 -minute time increments for the gunman to move to the other zones, according to an embodiment of the disclosure. At the time of commissioning the building automation emergency response and occupant evacuation system 160, the active shooter prediction map of FIG. 5 is compiled and stored in memory 132, of the predicted gunshot sensor danger level in each of the zones (A) through (N) for a gunman starting in Zone(A). The active shooter prediction map is based on national experiences over several years of active shooter situations. Estimates are made of the rate of movement of a hypothetical active shooter through each of the zones (A) through (N) where each gunshot sensor is located. In this example, since there are only two entrances to the building where an active shooter could enter, through the front and back doors, a total of two different active shooter prediction maps may be compiled and stored, one for Zone(A) at the front door and one for Zone(O) at the back door. Each zone on the active shooter prediction map of FIG. 5 has an encircled label indicating the number of minutes it is predicted for a gunman to reach the zone since the instant of the first gunshot detected from the gunman in Zone(A).

[00176] FIG. 5A is an example display on the user interface UI(2) in Zone(B) showing the display by user interface UI(2) of the active shooter prediction map. Among the three routes ROUTE(Bl), ROUTE(B2), and ROUTE(B3) shown in FIG. 2B, the safest evacuation route is ROUTE(B2) from Zone(B) at 6 minutes into the future, according to an embodiment of the disclosure. At the time of 6 minutes after the gunman starts in Zone(A), the active shooter prediction map of FIG. 5 indicates that the gunman is predicted to have moved to zones (B), ( C), (D), (F), (M), and (N). The building automation emergency response and occupant evacuation system 160 calculates a present-predicted zone danger level of Zone(F), by adding the present zone danger level of Zone(F) (= 0) and the predicted zone danger level of Zone(F) (gunman = 100) at 6 minutes into the future. In this example, the predicted zone danger level of Zone(F) is 100 at 6 minutes after the gunman starts in Zone(A), which raises the route danger level for ROUTE(B3) 1050. The ROUTE(B3) is no longer the safest evacuation route, because gunman is predicted to have moved to Zone(F) by 6 minutes. The ROUTE(B2) will be the safest evacuation route, by 6 minutes after the gunman starts in Zone(A). The following Table I shows an example calculation of the route danger level during the example emergency at 6 minutes into the future, to determine the safest evacuation route commencing from Zone(B), from among the three possible evacuation routes: ROUTE(Bl), ROUTE(B2), and ROUTE(B3) in FIG. 2B.

Table I - At 6 Minutes into the Future

[00177] For Zone(F), the building automation emergency response and occupant evacuation system 160 calculates a present-predicted zone danger level of Zone(F), by adding the present zone danger level of Zone(F) (= 0) and the predicted zone danger level of Zone(F) (gunman at 6 minutes = 100). The Route(B2) has the smallest route danger level for the sum of the products of the length of the component segments, Dl, D2, and D3 for Route(B2) from Zone(B), times the zone danger level at 6 minutes for each respective zone Zone(N), Zone(L), and Zone(O) through which the respective segments pass in FIG. 2B. Thus, ROUTE(B2) is the safest evacuation route commencing from Zone(B) at 6 minutes into the future, to avoid the gunman emergency detected in Zone (A) and the gunman emergency in Zone(F), according to an embodiment of the disclosure. FIG. 5A is an example display on the user interface UI(2) in Zone(B) showing the display by user interface UI(2) of the safest evacuation ROUTE(B2) from Zone(B) at 6 minutes into the future, according to an embodiment of the disclosure. In this situation, the user may take ROUTE(B2) through Zone(N) with a higher danger score of 300, because the route only passes through a short distance Dl through Zone(N) and therefore gives an overall lower danger score for the route. Note that at the time of 6 minutes, a gunman is in the Zone(B), indicating the urgency of evacuation.

[00178] FIG. 6 is an example flow diagram of a method performed by the example building automation emergency response and occupant evacuation system 160 of FIG. 1, according to an embodiment of the disclosure. The logic blocks 500 of the flow diagram may be implemented by computer program instructions stored in the memory 132 and executed by the processor in the emergency server 130 of FIG. 1. Alternately, the logic blocks 500 of the flow diagram may also be implemented by computer hardware logic in the emergency server 130 of FIG. 1, which can carry out the functions specified by the logic blocks.

[00179] The method performed by the example logic blocks 500, comprises the following logic blocks:

[00180] Block 502: receiving, by the server, one or more indications of a detected emergency in a building from one or more sensors distributed among one or more zones in the building, the one or more indications comprising a sensor reading level of the detected emergency and an identity of the one or more sensors;

[00181] Block 504: determining, by the server, one or more zone danger levels of the detected emergency in the one or more zones, based on the identity of the one or more sensors indicating a location in the one or more zones, and based on the sensor reading level of the detected emergency of the one or more sensors in the one or more zones; [00182] Block 506: calculating, by the server, a route danger level of one or more evacuation routes from one or more user interfaces located in the one or more zones in the building toward one or more respective exit locations of the building, the one or more evacuation routes comprising a sequence of one or more distance segments traversing the one or more zones having respective zone danger levels, the server calculating the route danger level as a sum of products of the one or more distance segments times the respective zone danger levels of the one or more zones traversed;

[00183] Block 508: determining, by the server, one or more safest evacuation routes of the one or more evacuation routes from the one or more user interfaces respectively located in the one or more zones, the safest evacuation routes having route danger levels that are less than a route danger level of other ones of the one or more evacuation routes from the respective user interfaces;

[00184] Block 510: transmitting, by the server, one or more depictions of the safest evacuation routes to the one or more user interfaces in the one or more zones for display on one or more display devices, wherein the one or more depictions are of the one or more safest routes transmitted to respective ones of the one or more user interfaces, based on the locations of the respective ones of the one or more user interfaces relative to the one or more exit locations and the detected emergency; and

[00185] Block 512: receiving, by the server, updated indications of the detected emergency in the building from the one or more sensors, and in response, determining updated zone danger levels in the one or more zones, calculating updated route danger levels based on the updated zone danger levels, determining updated safest evacuation routes based on the updated route danger levels, and transmitting updated depictions of the safest evacuation routes to the one or more user interfaces for display.

[00186] Current building automation emergency response systems are not designed to accurately determine the safest route to safety using indications of emergency received from building sensors, transmit the safest route to user interfaces for display, determine updated safest evacuation routes based on updated danger levels, and transmit the updated safest evacuation routes for display on user interfaces. This is a technical problem. An exemplary embodiment of a building automation emergency response system may comprise a processor instructed to receive, by the server, an indication of a detected emergency in a building from sensors among one or more zones in the building. The indications may comprise sensor reading levels of the detected emergency and an identity of the sensors. The processor may determine a danger zone level of the detected emergency in the one or more zones, based on the identity of the sensors indicating a location in the one or more zones, and based on the sensor reading levels of the detected emergency of the sensors in the one or more zones. The processor may calculate a route danger level of one or more evacuation routes from one or more user interfaces located in the one or more zones toward one or more respective exit locations of the building. The one or more evacuation routes may comprise a sequence of one or more distance segments traversing the one or more zones having respective zone danger levels. The processor may determine one or more safest evacuation routes of the one or more evacuation routes from the one or more user interfaces, respectively, located in the one or more zones, the safest evacuation routes having route danger levels that are less than a route danger level of other ones of the one or more evacuation routes from the respective user interfaces. The processor may transmit one or more depictions of the safest evacuation routes to the one or more user interfaces in the one or more zones for display on one or more display devices. The depictions may be of the safest routes transmitted to the respective user interfaces based on the locations of the respective user interfaces relative to the exit locations and the detected emergency. The processor may receive updated indications of the detected emergency in the building from one or more sensors, and, in response, determine updated zone danger levels in the one or more zones, calculate updated route danger levels based on the updated zone danger levels, determine updated safest evacuation routes based on the updated route danger levels, and transmit updated depictions of the safest evacuation routes to the one or more user interfaces for display. At least this foregoing combination of features comprises a building automation emergency response system that serves as a technical solution to the foregoing technical problem. This technical solution is not routine and is unconventional. This technical solution is a practical application of a building automation emergency response system that solves the foregoing technical problem and constitutes an improvement in the technical field of building-automation-system design at least by facilitating accurately determining the safest route to safety using indications of emergency received from building sensors, transmitting the safest route to user interfaces for display, determining updated safest evacuation routes based on updated danger levels, and transmitting the updated safest evacuation routes for display. [00187] In the preceding, reference is made to various embodiments. However, the scope of the present disclosure is not limited to the specific described embodiments. Instead, any combination of the described features and elements, whether related to different embodiments or not, is contemplated to implement and practice contemplated embodiments. Furthermore, although embodiments may achieve advantages over other possible solutions or over the prior art, whether or not a particular advantage is achieved by a given embodiment is not limiting of the scope of the present disclosure. Thus, the preceding aspects, features, embodiments and advantages are merely illustrative and are not considered elements or limitations of the appended claims except where explicitly recited in a claim(s).

[00188] The various embodiments disclosed herein may be implemented as a system, method or computer program product. Accordingly, aspects may take the form of an entirely hardware embodiment, an entirely software embodiment (including firmware, resident software, micro-code, etc.) or an embodiment combining software and hardware aspects that may all generally be referred to herein as a “component”, “circuit,” “module” or “system.” Furthermore, aspects may take the form of a computer program product embodied in one or more computer-readable medium(s) having computer-readable program code embodied thereon.

[00189] Any combination of one or more computer-readable medium(s) may be utilized. The computer-readable medium may be a non-transitory computer-readable medium. A non-transitory computer-readable medium may be, for example, but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, or device, or any suitable combination of the foregoing. More specific examples (a non-exhaustive list) of the non-transitory computer-readable medium can include the following: an electrical connection having one or more wires, a portable computer diskette, a hard disk, a random access memory (RAM), a read-only memory (ROM), an erasable programmable read-only memory (EPROM or Flash memory), an optical fiber, a portable compact disc read-only memory (CD-ROM), an optical storage device, a magnetic storage device, or any suitable combination of the foregoing. Program code embodied on a computer-readable medium may be transmitted using any appropriate medium, including but not limited to wireless, wireline, optical fiber cable, RF, etc., or any suitable combination of the foregoing. [00190] Computer program code for carrying out operations for aspects of the present disclosure may be written in any combination of one or more programming languages. Moreover, such computer program code can execute using a single computer system or by multiple computer systems communicating with one another (e.g., using a local area network (LAN), wide area network (WAN), the Internet, etc.). While various features in the preceding are described with reference to flowchart illustrations and/or block diagrams, a person of ordinary skill in the art will understand that each block of the flowchart illustrations and/or block diagrams, as well as combinations of blocks in the flowchart illustrations and/or block diagrams, can be implemented by computer logic (e.g., computer program instructions, hardware logic, a combination of the two, etc.). Generally, computer program instructions may be provided to a processor(s) of a general- purpose computer, special-purpose computer, or other programmable data processing apparatus. Moreover, the execution of such computer program instructions using the processor(s) produces a machine that can carry out a function(s) or act(s) specified in the flowchart and/or block diagram block or blocks.

[00191] The flowchart and block diagrams in the Figures illustrate the architecture, functionality and/or operation of possible implementations of various embodiments of the present disclosure. In this regard, each block in the flowchart or block diagrams may represent a module, segment or portion of code, which comprises one or more executable instructions for implementing the specified logical function(s). It should also be noted that, in some alternative implementations, the functions noted in the block may occur out of the order noted in the figures. For example, two blocks shown in succession may, in fact, be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending upon the functionality involved. It will also be noted that each block of the block diagrams and/or flowchart illustration, and combinations of blocks in the block diagrams and/or flowchart illustration, can be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

[00192] It is to be understood that the above description is intended to be illustrative, and not restrictive. Many other implementation examples are apparent upon reading and understanding the above description. Although the disclosure describes specific examples, it is recognized that the systems and methods of the disclosure are not limited to the examples described herein but may be practiced with modifications within the scope of the appended claims. Accordingly, the specification and drawings are to be regarded in an illustrative sense rather than a restrictive sense. The scope of the disclosure should, therefore, be determined with reference to the appended claims, along with the full scope of equivalents to which such claims are entitled.