Related Application

[001] This application claims the benefit of U.S. Provisional Application No. 62/592,149, filed on 29 November 2017, entitled“Crisis Management System”, the contents of which are incorporated herein by reference.

Background

[002] In educational environments, providing a safe and secure learning environment is one of the most daunting challenges facing K-12 schools, universities and colleges today. Additionally, personal safety has become one of the most debilitating workplace stress factors for housekeeping staff today in the hospitality industry. Housekeeping staff and other employees who work alone or in vulnerable areas must deal with the potential for personal harm on a daily basis. Further, with incidents of violence on the rise in retail stores and shopping centers, employee safety has never been more critical. In a public-facing environment, anything can happen at any given moment. In business industries, research shows that employees who feel happy and secure in their workplace are more productive employees. Whether it’s a corporate office, manufacturing plant, warehouse or a public-facing branch location, employee peace of mind has a direct impact on the bottom line.

[003] In an effort to reduce incidents of violence in educational environments, hospitality industries, retail stores, and in workplaces generally, everyone is encouraged to report suspicious activity and to seek help quickly to resolve potential threats. However, conventional alert management systems are unable to quickly and efficiently report an emergency or provide an alert to others who can help.

Summary of Disclosure

[004] In one implementation, an alert communication device is provided. The alert communication device may include a first transceiver configured to communicatively couple the alert communication device with one or more other alert communication devices via a first communication path, a second transceiver configured to communicatively couple the alert communication device with the one or more other alert communication devices via a second communication path, and one or more of a visual alert system and an audio alert system.

[005] One or more of the following features may be included. The alert communication device may include a third transceiver configured to communicatively couple the alert communication device with one or more alert activation devices via a third communication path. The alert communication device may be configured to receive an alert signal from the one or more alert activation devices and transmit the alert signal to the one or more other alert communication devices via the first communication path determine that the first communication path is inaccessible and transmit the alert signal to the one or more alert communication devices via the second communication path in response to determining that the first communication path is inaccessible. The alert communication device may be configured to establish a communication channel between two or more client devices via one or more of the first communication path and the second communication path. The visual alert system may include a plurality of electronically-controlled lights configured to provide a plurality of visual alerts. The third transceiver may be a Bluetooth Low Energy® transceiver configured to determine the location of the one or more alert activation devices relative to the alert communication device.

[006] In another implementation, an alert activation device is provided. The alert activation device may include a transceiver configured to communicatively couple the alert activation device to at least one alert communication device and an activation button communicatively coupled to the transceiver. The alert activation device may be configured to transmit an alert signal via the transceiver in response to a user engaging the activation button.

[007] One or more of the following features may be included. The alert activation device may be a wearable alert activation device. The alert activation device may be configured to be affixed to an identification badge. The transceiver may be configured to transmit a location of the alert activation device when transmitting the alert signal. The transceiver may be a Bluetooth Low Energy® transceiver.

[008] In another implementation, an alert management system is provided. The alert management system may include one or more alert communication devices communicatively coupled to one or more other alert communication devices and configured to provide one or more of a visual alert and an audio alert and one or more alert activation devices communicatively coupled to at least one alert communication device of the one or more alert communication devices.

[009] One or more of the following features may be included. The alert management system may include one or more alert gateways. The one or more alert communication devices may be communicatively coupled to the one or more alert gateways. The one or more alert communication devices may include a plurality of alert communication devices and are configured to communicatively couple the alert communication device with one or more other alert communication devices of the plurality of alert communication devices via a first communication path. The one or more alert communication devices may be configured to communicatively couple the alert communication device with the one or more other alert communication devices of the plurality of alert communication devices via a second communication path. The alert management system may be configured to receive, at the one or more alert communication devices, an alert signal from the one or more alert activation devices and transmit the alert signal to the one or more other alert communication devices via a first communication path formed between a plurality of alert communication devices. The alert management system may be configured to determine that the first communication path is inaccessible and transmit the alert signal to the one or more alert communication devices via the second communication path in response to determining that the first communication path is inaccessible. The alert management system may be configured to establish a communication channel between two or more client devices via one or more of the first communication path and the second communication path. The alert management system may include at least one client device communicatively coupled to the alert management system. The at least one client device may include a user interface. The alert management system may be configured to provide one or more of an alert signal and a map to the user interface of the at least one client device.

[0010] The details of one or more implementations are set forth in the accompanying drawings and the description below. Other features and advantages will become apparent from the description, the drawings, and the claims.

Brief Description of the Drawings

[0011] FIG 1 is a diagrammatic view of a distributed computing network including a computing device that executes an alert management process according to an embodiment of the present disclosure;

[0012] FIG. 2 is a diagrammatic view of an alert communication device according to an embodiment of the present disclosure;

[0013] FIGS. 3-4 are diagrammatic views of an alert management system according to various embodiments of the present disclosure;

[0014] FIG 5 is a diagrammatic view of a user interface generated on a client device according to an embodiment of the present disclosure;

[0015] FIGS. 6A-6B are diagrammatic views of an alert activation device according to various embodiments of the present disclosure;

[0016] FIG. 7 is a flowchart of another embodiment of the alert management process of FIG. 1 according to an embodiment of the present disclosure; and

[0017] FIG. 8 is a diagrammatic view of a client electronic device executing the alert management process of FIG. 1 according to an embodiment of the present disclosure.

[0018] Like reference symbols in the various drawings indicate like elements. Detailed Description of the Preferred Embodiments

System Overview

[0019] In FIG 1, there is shown alert management process 10. Alert management process 10 may be implemented as a server-side process, a client-side process, or a hybrid server-side / client-side process.

[0020] For example, alert management process 10 may be implemented as a purely server-side process via alert management process lOs. Alternatively, alert management process 10 may be implemented as a purely client-side process via one or more of alert management process lOcl, alert management process l0c2, alert management process l0c3, and alert management process l0c4. Alternatively still, alert management process 10 may be implemented as a hybrid server-side / client-side process via alert management process lOs in combination with one or more of alert management process lOcl, alert management process l0c2, alert management process l0c3, and alert management process l0c4. Accordingly, alert management process 10 as used in this disclosure may include any combination of alert management process lOs, alert management process lOcl, alert management process l0c2, alert management process l0c3, and alert management process l0c4.

[0021] Alert management process lOs may be a server application and may reside on and may be executed by computing device 12, which may be connected to network 14 (e.g., the Internet or a local area network). Examples of computing device 12 may include, but are not limited to: a personal computer, a server computer, a series of server computers, a mini computer, a mainframe computer, or a cloud-based computing network.

[0022] The instruction sets and subroutines of alert management process lOs, which may be stored on storage device 16 coupled to computing device 12, may be executed by one or more processors (not shown) and one or more memory architectures (not shown) included within computing device 12. Examples of storage device 16 may include but are not limited to: a hard disk drive; a RAID device; a random access memory (RAM); a read-only memory (ROM); and all forms of flash memory storage devices.

[0023] Network 14 may be connected to one or more secondary networks (e.g., network 18), examples of which may include but are not limited to: a local area network; a wide area network; or an intranet, for example.

[0024] Examples of alert management processes lOcl, l0c2, l0c3, l0c4 may include but are not limited to a corporate user interface, a web browser, or a specialized application (e.g., an application running on e.g., the Android ^tm platform or the iOS ^tm platform). The instruction sets and subroutines of alert management processes lOcl, l0c2, l0c3, l0c4, which may be stored on storage devices 20, 22, 24, 26 (respectively) coupled to client electronic devices 28, 30, 32, 34 (respectively), may be executed by one or more processors (not shown) and one or more memory architectures (not shown) incorporated into client electronic devices 28, 30, 32, 34 (respectively). Examples of storage devices 20, 22, 24, 26 may include but are not limited to: hard disk drives; RAID devices; random access memories (RAM); read only memories (ROM), and all forms of flash memory storage devices.

[0025] Examples of client electronic devices 28, 30, 32, 34 may include, but are not limited to: smartphone 28; laptop computer 30; specialty device 32; personal computer 34; a notebook computer (not shown); a server computer (not shown); a dedicated network device (not shown); and a tablet computer (not shown).

[0026] Client electronic devices 28, 30, 32, 34 may each execute an operating system, examples of which may include but are not limited to Microsoft Windows ^tm , Android ^tm , iOS ^lm . Linux ^tm , or a custom operating system.

[0027] Users 36, 38, 40, 42 may access alert management process 10 directly through network 14 or through secondary network 18. Further, alert management process 10 may be connected to network 14 through secondary network 18, as illustrated with link line 44. [0028] The various client electronic devices (e.g., client electronic devices 28, 30, 32, 34) may be directly or indirectly coupled to network 14 (or network 18). For example, smartphone 28 and laptop computer 30 are shown wirelessly coupled to network 14 via wireless communication channels 44, 46 (respectively) established between smartphone 28, laptop computer 30 (respectively) and cellular network / bridge 48, which is shown directly coupled to network 14. Further, specialty device 32 is shown wirelessly coupled to network 14 via wireless communication channel 50 established between specialty device 32 and wireless access point (i.e., WAP) 52, which is shown directly coupled to network 14. Additionally, personal computer 34 is shown directly coupled to network 18 via a hardwired network connection.

[0029] WAP 52 may be, for example, an IEEE 802.1 la, 802.1 lb, 802. llg, 802.11h, Wi-Fi, and/or Bluetooth device that is capable of establishing wireless communication channel 50 between specialty device 32 and WAP 52. As is known in the art, IEEE 802.1 lx specifications may use Ethernet protocol and carrier sense multiple access with collision avoidance (i.e., CSMA/CA) for path sharing. The various 802.1 lx specifications may use phase-shift keying (i.e., PSK) modulation or complementary code keying (i.e., CCK) modulation, for example. As is known in the art, Bluetooth® is a telecommunications industry specification that allows e.g., mobile phones, computers, and personal digital assistants to be interconnected using a short-range wireless connection.

[0030] Referring to FIGS. 2-8 and as will be discussed in greater detail below, embodiments of the present disclosure may comprise a blend of hardware, software and wireless technologies to ensure fast, accurate, and reliable emergency communication when it's needed most. From alert activation to alert tracking and updating to secure two-way communication, embodiments of the present disclosure may provide a full complement of capabilities to automate and accelerate an alert and crisis management process. [0031] As will be discussed in greater detail below, an alert can be activated instantly from multiple touchpoints, including mobile and desktop software, as well as a wearable alert activation devices that can be custom-programmed to generate various kinds of alerts (e.g., staff or building-level alerts). Whether a staff requests assistance or a higher-level alert notifying building occupants of a particular state of emergency, embodiments of the present disclosure may empower staff and administrators alike to put desired protocols in motion faster than ever.

[0032] In addition, embodiments of the present disclosure may utilize a mesh network of alert communication devices or“hubs” that provide both notifying (e.g., color-coded visual and audible alerts) and locating capabilities, which extend to exterior coverage, creating a robust security net that reaches places like playgrounds, athletic fields, and parking lots.

[0033] As will be discussed in greater detail below and in some implementations, the alert communication devices may not only signal that specific emergency response is needed through flashing LEDs, they may also communicate critical locating data to inform response. In some implementations, this information may be instantly sent to and presented on multiple devices (desktop/laptop, mobile phone, and TV) in the form of a floor view (single location) and map view (multiple locations), and displays are updated dynamically as changes occur.

Alert Communication Device:

[0034] In some implementations and as will be discussed in greater detail below, an alert communication device may generally include a smoke detector-size (6" x 6" x 1.5") notification and wireless communication device configured to create instant awareness among building occupants by providing audible and color-coded visual notification as well as visual feed that is transmitted directly to the enterprise location. While exemplary dimensions of an alert communication device have been discussed above, it will be appreciated that various dimensions for the alert communication device may be used within the scope of the present disclosure. [0035] Referring also to FIG. 2 and in some implementations, an alert communication device may include a first transceiver configured to communicatively couple the alert communication device with one or more other alert communication devices via a first communication path. As shown in FIG 2, first transceiver 202 may be positioned within alert communication device 200. However, it will be appreciated that first transceiver 202 may be positioned on and/or adjacent to the exterior of alert communication device 200. In some implementations, first communication path may be a wireless communication channel utilizing IEEE 802.1 lx specifications, as discussed above. In this manner, the first transceiver may be a Wi-Fi® module.

[0036] Referring also to FIG. 3, a plurality of alert communication devices may be configured to form a “Wi-Fi® mesh” that may allow up to e.g., 1,000 alert communication devices (e.g., alert communication devices 302, 304, 306, 308) to be communicatively coupled together via the first communication path or channel. As will be discussed in greater detail below, the plurality of alert communication devices may be communicatively connected and linked to an alert gateway. While a Wi-Fi® communication path or communication channel has been discussed, it will be appreciated that other communication protocols are within the scope of the present disclosure for implementing the first communication path between the alert communication device and the one or more other alert communication devices (e.g., alert communication devices 302, 304, 306, 308). In some implementations and upon powering of the alert communication device, alert communication device 302 may automatically establish one or more first communication paths (e.g., first communication paths 310, 312, 314) to one or more adjacent or proximate alert communication devices (e.g., alert communication devices 304, 306). In some implementations, each alert communication device may automatically establish the first communication path (e.g., first communication paths 310, 312, 314, 316) with each alert communication device within the operating range of the first transceiver. In this example, even non-adjacent alert communication devices may be communicatively coupled when each alert communication device is within the operating range of the first transceiver. It will be appreciated that the operating range of the first transceiver may be dependent upon many external factors such as distance between alert communication devices, temperature, electromagnetic interference, obstacles, power constraints, etc.

[0037] Referring again to FIG. 2 and in some implementations, the alert communication device may include a second transceiver configured to communicatively couple the alert communication device with the one or more other alert communication devices via a second communication path. As shown in FIG. Z, second transceiver 204 may be positioned within alert communication device 200. However, it will be appreciated that second transceiver 204 may be positioned on and/or adjacent to the exterior of alert communication device 200. In some implementations, the second transceiver may include a Zigbee® communication module configured to wirelessly couple alert communication devices. In this manner, the second communication path may define at least a portion of a Zigbee® mesh wireless communication between alert communication devices and/or an alert gateway.

[0038] Referring also to FIG. 3 and in some implementations, the second communication path (e.g., second communication paths 318, 320, 322) between the alert communication device (e.g., alert communication device 302) and the one or more other alert communication devices (e.g., alert communication devices 304, 306) may be established by the second transceivers of each alert communication device. While a Zigbee® communication path or communication channel has been discussed, it will be appreciated that other communication protocols are within the scope of the present disclosure for implementing the second communication path between the alert communication device and the one or more other alert communication devices (e.g., alert communication devices 302, 304, 306, 308). [0039] In some implementations and upon powering of the alert communication device, alert communication device 302 may automatically establish one or more second communication paths (e.g., second communication paths 318, 320) to one or more adjacent or proximate alert communication devices (e.g., alert communication devices 304, 306). In some implementations, each alert communication device may automatically establish the second communication path (e.g., second communication paths 318, 320, 322, 324) with each alert communication device within the operating range of the second transceiver. In this example, even non-adjacent alert communication devices may be communicatively coupled when each alert communication device is within the operating range of the second transceiver. It will be appreciated that the operating range of the second transceiver may be dependent upon many external factors such as distance between alert communication devices, temperature, electromagnetic interference, obstacles, power constraints, etc.

[0040] As will be discussed in greater detail below and in some implementations, the second communication path may include a communication protocol that is separate or different from the communication protocol of the first communication path (e.g., a first communication path established between e.g., Wi-Fi® transceivers and a second communication path established between e.g., Zigbee® transceivers.

[0041] Returning to FIG. 2 and in some implementations, the alert communication device may include one or more of a visual alert system and an audio alert system. In this manner, alert communication device may also provide alert signals through one or more visual alerts and one or more audio alerts. In some implementations, alert communication device 200 may include a visual alert system in the form of a plurality of electronically-controlled lights configured to provide a plurality of visual alerts. For example, a plurality of electronically-controlled lights (e.g., electronically- controlled lights 206, 208, 210, 212) may be positioned on the exterior of alert communication device 200. In some implementations, the visual alert system may be configured to receive an alert signal and provide visual alerts (e.g., flashing lights) in a color and/or pattern corresponding to the alert signal. For example, the visual alert system may include highly visible multi-color LEDs that can be programmed to match the desired color, audio, and flashing characteristics of each alert.

[0042] In some implementations, the audio alert system may include one or more speakers or buzzers within and/or on the exterior of the alert communication device. For example, speaker 214 may be configured to provide one or more audio alerts (e.g., sirens, whistling, voice commands, etc.) in response to receiving an alert signal at the alert communication device (e.g., alert communication device 200). With the above-described visual alert system and/or audio alert system, critical information can be seen and heard on multiple platforms. In some implementations, the audio alert system may be combined with built-in text-to-speech capability to provide speech alerts in response to text alert signals received by alert communication devices. In some implementations, the alert communication device may include a microphone (e.g., microphone 216) for recording audio signals adjacent to the alert communication device.

[0043] In some implementations, the alert communication device may include a third transceiver configured to communicatively couple the alert communication device with one or more alert activation devices via a third communication path. As shown in FIG 2, third transceiver 218 may be positioned within alert communication device 200. However, it will be appreciated that third transceiver 218 may be positioned on and/or adjacent to the exterior of alert communication device 200. In some implementations, the third transceiver may be a Bluetooth Low Energy® transceiver. As is known in the art, Bluetooth Low Energy® or BLE is a specification that allows radio frequency communication between various types of devices. For example, devices may provide advertising packets or signals that may be received by scanning devices. These advertising packets may be sent without a formal pairing between devices. In this manner and as will be discussed in greater detail below, alert activation devices may provide alert signals to the alert communication device without pairing to a specific alert communication device. Referring also to FIG. 3 and in some implementations, the third transceiver (e.g., third transceiver 218) may be configured to receive alert signals from an alert activation device (e.g., alert activation device 326) and/or a client device (e.g., client device 28) via the third communication path (e.g., third communication path 328). For example and through a user interface provided to a client device, a user may initiate an alert signal by selecting one or more buttons in the user interface.

[0044] In some implementations, the third transceiver (e.g., third transceiver 218) may be configured to determine the location of the one or more alert activation devices relative to the alert communication device. For example and in some implementations, the alert communication device may determine the location of the alert activation device or client device relative to the alert communication device based upon, at least in part, the alert signal received by the third transceiver (e.g., third transceiver 218). In this manner, the alert communication device may communicate with applications and the wearable alert activation device to determine personnel location. In some implementations, the alert communication device may also provide tracking capability by functioning as a locating beacon. In some implementations, the alert communication device may deliver the specific nature of the alert (i.e.: anything from a confrontation with a student or customer to the identification of an armed intruder).

[0045] In some implementations, the alert communication device may be configured to receive an alert signal from the one or more alert activation devices. In some implementations and referring also to the example of FIG. 4, a plurality of alert communication devices (e.g., alert communication devices 402, 404) may be positioned throughout e.g., a school building. The alert communication devices (e.g., alert communication devices 402, 404) may be mounted to e.g., the ceiling throughout the building. As will be discussed in greater detail below, the alert communication devices (e.g., alert communication devices 402, 404) may be communicatively coupled to an alert gateway (e.g., alert gateway 406). In some implementations, members of the school staff may have access to an alert activation device (e.g., alert activation device 408). In some implementations, alert communication device 402 may be configured to receive an alert signal from the alert activation device (e.g., alert activation device 408). As discussed above, the alert signal may be received by the third transceiver of alert communication device 402 via the third communication path (e.g., third communication path 410). In some implementations, the alert communication device may be configured to transmit the alert signal to the one or more other alert communication devices via the first communication path (e.g., first communication path 412). In this example, alert communication device 402 may be configured to transmit the alert signal to another alert communication device (e.g., alert communication device 404) in response to receiving the alert signal (e.g., via third communication path 410).

[0046] In some implementations, the alert communication device may be configured to determine that the first communication path is inaccessible. Referring again to FIG 3 and in some implementations, an alert communication device (e.g., alert communication device 302) may be configured to determine that the first communication path (e.g., first communication path 310 between alert communication device 302 and alert communication device 304) is inaccessible (e.g., by determining that the first transceiver is not able to send or receive signals via the first communication path). In some implementations, the alert communication device (e.g., alert communication device 302) may be configured to transmit the alert signal to the one or more alert communication devices (e.g., alert communication 304) via the second communication path in response to determining that the first communication path is inaccessible. For example, in response to determining that the first communication path is inaccessible, alert communication device 302 may transmit an alert signal via the second communication path (e.g., second communication path 318 between alert communication device 302 and alert communication device 304).

[0047] In some implementations, the alert communication device may be configured to establish a communication channel between two or more client devices via one or more of the first communication path and the second communication path. In some implementations, to streamline communication among crisis managers, first responders and other key stakeholders, alert communication devices may provide two-way communication to client devices over a secure channel. Referring again to the example of FIG 3 and in some implementations, client device 28 may be communicatively coupled to alert communication device 304 and client device 12 may be communicatively coupled to alert communication device 308. In some implementations and via one or more of the first communication path and the second communication path between alert communication device 304 and alert communication device 308, a communication channel may be established between client device 28 and client device 28. Referring also to FIG 5 and in some implementations, alert management process 10 may provide a user interface or application (e.g., user interface 500) on a client device to establish a communication channel between client devices. For example, a user may select a button (e.g., button 502). In some implementations, the button may be a touchscreen button or a physical button on the client device. In some implementations, alert communication devices may integrate with existing radios to facilitate the same functionality without the need to change communication devices.

Alert Activation Device:

[0048] In some implementations, an alert activation device may be used by a user to generate an alert signal. In some implementations, the alert activation device may include a transceiver configured to communicatively couple the alert activation device to at least one alert communication device. For example and as shown in FIGS. 6 A and 6B, an alert activation device (e.g., alert activation devices 602, 604) may each include a transceiver (e.g., transceiver 606, 608, respectively) configured to communicatively couple the alert activation device to at least one alert communication device. In some implementations, the transceiver may be embedded within the alert activation device and/or be positioned on the exterior of the alert activation device. It will be appreciated that the transceiver (e.g., transceiver 606, 608) may be positioned in a variety of ways relative to the alert activation device within the scope of the present disclosure.

[0049] In some implementations, the alert activation device may include an activation button communicatively coupled to the transceiver. Referring also to FIG 6A and in some implementations, the activation button (e.g., activation button 610) may occupy at least a portion of an exterior surface of the alert activation device. For example, activation button 610 may occupy a portion of alert activation device such that when a user presses the portion labeled“Push for help”, the activation button may be engaged. In some implementations and referring also to the example of FIG 6B, the activation button may represent an entire side of the alert activation device (e.g., alert activation device 604 is a button device, where the activation button is an entire side of the alert activation device. In this manner, a user need only press the shown side of alert activation device to engage the activation button. It will be appreciated that various sizes and positions may be used for the activation button within the scope of the present disclosure.

[0050] In some implementations, the alert activation device may be a wearable alert activation device. For example, the alert activation device may be designed for instant accessibility and multi-function wireless communication capability. In some implementations, the alert activation device may be an ID/access card-size (e.g., 3- 3/8" x 2-1/8" x 1/8") wearable alert device. While exemplary dimensions of an alert activation device have been discussed above, it will be appreciated that various dimensions for the alert activation device may be used within the scope of the present disclosure. In some implementations, the alert activation device may be configured to be affixed to an identification badge. For example, it can be discreetly affixed behind an identification badge and quickly engaged to initiate an alert.

[0051] In some implementations, the transceiver (e.g., transceiver 606, 608) may be configured to transmit a location of the alert activation device when transmitting the alert signal. As discussed above and in some implementations, the transceiver may be a Bluetooth® Low Energy transceiver. With integrated Bluetooth Low Energy®, the alert activation device may allow beaconing capability for device locating. This functionality may support the capture and reporting of critical information, thus shortening response times and facilitating real-time incident updates.

Alert Management System:

[0052] In some implementations, an alert management system may include one or more alert communication devices communicatively coupled to one or more other alert communication devices and configured to provide one or more of a visual alert and an audio alert. Referring again to FIG. 4 and in some implementations, the alert management system (e.g., alert management system 400) may include one or more alert communication devices communicatively coupled to one or more other alert communication devices (e.g., alert communication devices 402, 404). As discussed above, the one or more alert communication devices may be configured to provide one or more of a visual alert and an audio alert.

[0053] In some implementations, the alert management system may include one or more alert activation devices communicatively coupled to at least one alert communication device of the one or more alert communication devices. For example, the alert management system (e.g., alert management system 400) may include one or more alert activation devices (e.g., alert activation devices 408) communicatively coupled to at least one alert communication device (e.g., alert communication devices 402, 404). [0054] In some implementations, the alert management system may further include one or more alert gateways. In some implementations, the one or more alert communication devices may be communicatively coupled to the one or more alert gateways. For example, the alert management system (e.g., alert management system 400) may include one or more alert gateways (e.g., alert gateway 406) configured to interconnect the one or more alert communication devices with one or more external resources. For example, alert gateway may be configured to provide the alert signals from the one or more alert communication devices to a district office, a police building, first responders, and/or to mobile and desktop applications of alert management process 10. In this manner, the alert signals of the alert management system may be provided for external resources to access and to process. For example and in some implementations, at least one client device may be communicatively coupled to the alert management system. In some implementations, the at least one client device may include a user interface.

[0055] In some implementations, alert management system 400 may be configured to provide one or more of an alert signal and a multi-location map to the user interface of the at least one client device. A multi-location map may generally include a plurality of maps of a building, park, playground, or other area of interest associated with an alert signals. From this alert signal and multi-location map, users associated with the alert signal may provide support and/or initiate one or more emergency procedures. Referring again to FIG 5, each client device may include a user interface (e.g., user interface 500) with a multi-location map (e.g., multi-location map 504) configured to show the location of the origin of an alert signal and/or position of an alert activation device.

[0056] In some implementations, alert management process 10 may be composed of applications across multiple platforms: Web (server side), Desktop and Mobile (client side). In some implementations, everything from user management to location mapping to alert and device configuration may be accessed from any Web browser because of the one or more alert gateways. For example, desktop client applications may be installed on a computing device and may provide alert notification and activation functionality, along with full crisis management capability. In some implementations, this may include secure communication (e.g., audio/visual interaction and direct messaging) functions, plus building floor plan and multi location map displays indicating impacted areas, with real-time information updating. It may also include quick access to emergency plans and procedures for reference. In some implementations, alert management system may provide customizable analytics/reports to any authorized personnel.

[0057] In some implementations and as discussed above, the one or more alert communication devices may include a plurality of alert communication devices and may be configured to communicatively couple the alert communication device with one or more other alert communication devices of the plurality of alert communication devices via a first communication path. In some implementations, the one or more alert communication devices may be configured to communicatively couple the alert communication device with the one or more other alert communication devices of the plurality of alert communication devices via a second communication path.

Alert Management Process:

[0058] In some implementations and as discussed above, alert management process 10 may reside on and may be executed by storage system 12; and may be configured to process the above-described alert signals through the alert management system. For example and referring also to FIG. 7, alert management process 10 may be configured to receive 700, at the one or more alert communication devices, an alert signal from the one or more alert activation devices and/or one or more client devices, transmit 702 the alert signal to the one or more other alert communication devices via a first communication path formed between a plurality of alert communication devices, and provide 704 an alert via the visual alert system and/or the audio alert system of the alert communication device. In some implementations and as discussed above, alert management process 10 may be configured to determine 706 that the first communication path is inaccessible and transmit 708 the alert signal to the one or more alert communication devices via the second communication path in response to determining that the first communication path is inaccessible. For example, the alert management system may be designed to operate independently from a customer network. The communication mesh (e.g., mesh of alert communication devices) may be distinct from the host network but may be designed to integrate with that network. In some implementations, the alert management system may be secured by encryption technology from any outside interference/hacking of the network.

[0059] In some implementations and as discussed above, alert management process 10 may be configured to establish 710 a communication channel between two or more client devices via one or more of the first communication path and the second communication path.

[0060] In some implementations, the alert management system may provide the same notification, alert management and communication functions as the desktop application, including push-to-talk two-way radio capability on a secure communication channel to any client device. In some implementations and as discussed above, alert management process 10 may be configured to provide 712 one or more of an alert signal and a map to the user interface of at least one client device.

[0061] In some implementations, alert management process 10 may capture and record all incident data - including an alert cause - to guide a "forensic review" of an event for investigative purposes as well as supporting updated protocols for future crises.

[0062] Referring also to FIG 8, there is shown a diagrammatic view of client electronic device 34. While client electronic device 34 is shown in this figure, this is for illustrative purposes only and is not intended to be a limitation of this disclosure, as other configurations are possible. For example, any computing device capable of executing, in whole or in part, alert management process 10 may be substituted for client electronic device 34 within FIG 8, examples of which may include but are not limited to computing device 12 and/or client electronic devices 28, 30, 32.

[0063] Client electronic device 34 may include a processor and/or microprocessor (e.g., microprocessor 800) configured to, e.g., process data and execute the above- noted code / instruction sets and subroutines. Microprocessor 800 may be coupled via a storage adaptor (not shown) to the above-noted storage device(s) (e.g., storage device 26). An I/O controller (e.g., I/O controller 802) may be configured to couple microprocessor 800 with various devices, such as keyboard 804, pointing/selecting device (e.g., mouse 806), custom device, such a microphone (e.g., device 808), USB ports (not shown), and printer ports (not shown). A display adaptor (e.g., display adaptor 810) may be configured to couple display 812 (e.g., CRT or LCD monitor(s)) with microprocessor 800, while network controller/adaptor 814 (e.g., an Ethernet adaptor) may be configured to couple microprocessor 800 to the above-noted network 18 (e.g., the Internet or a local area network).

[0064] As will be appreciated by one skilled in the art, the present disclosure may be embodied as a method, a system, or a computer program product. Accordingly, the present disclosure 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“circuit,”“module” or“system.” Furthermore, the present disclosure may take the form of a computer program product on a computer-usable storage medium having computer-usable program code embodied in the medium.

[0065] Any suitable computer usable or computer readable medium may be utilized. The computer-usable or computer-readable medium may be, for example but not limited to, an electronic, magnetic, optical, electromagnetic, infrared, or semiconductor system, apparatus, device, or propagation medium. More specific examples (a non-exhaustive list) of the computer-readable medium may 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 transmission media such as those supporting the Internet or an intranet, or a magnetic storage device. The computer-usable or computer-readable medium may also be paper or another suitable medium upon which the program is printed, as the program can be electronically captured, via, for instance, optical scanning of the paper or other medium, then compiled, interpreted, or otherwise processed in a suitable manner, if necessary, and then stored in a computer memory. In the context of this document, a computer-usable or computer-readable medium may be any medium that can contain, store, communicate, propagate, or transport the program for use by or in connection with the instruction execution system, apparatus, or device. The computer-usable medium may include a propagated data signal with the computer- usable program code embodied therewith, either in baseband or as part of a carrier wave. The computer usable program code may be transmitted using any appropriate medium, including but not limited to the Internet, wireline, optical fiber cable, RF, etc.

[0066] Computer program code for carrying out operations of the present disclosure may be written in an object oriented programming language such as Java, Smalltalk, C++ or the like. However, the computer program code for carrying out operations of the present disclosure may also be written in conventional procedural programming languages, such as the "C" programming language or similar programming languages. The program code may execute entirely on the user's computer, partly on the user's computer, as a stand-alone software package, partly on the user’s computer and partly on a remote computer or entirely on the remote computer or server. In the latter scenario, the remote computer may be connected to the user’s computer through a local area network / a wide area network / the Internet (e.g., network 14). [0067] The present disclosure is described with reference to flowchart illustrations and/or block diagrams of methods, apparatus (systems) and computer program products according to embodiments of the disclosure. It will be understood that each block of the flowchart illustrations and/or block diagrams, and combinations of blocks in the flowchart illustrations and/or block diagrams, may be implemented by computer program instructions. These computer program instructions may be provided to a processor of a general purpose computer / special purpose computer / other programmable data processing apparatus, such that the instructions, which execute via the processor of the computer or other programmable data processing apparatus, create means for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0068] These computer program instructions may also be stored in a computer- readable memory that may direct a computer or other programmable data processing apparatus to function in a particular manner, such that the instructions stored in the computer-readable memory produce an article of manufacture including instruction means which implement the function/act specified in the flowchart and/or block diagram block or blocks.

[0069] The computer program instructions may also be loaded onto a computer or other programmable data processing apparatus to cause a series of operational steps to be performed on the computer or other programmable apparatus to produce a computer implemented process such that the instructions which execute on the computer or other programmable apparatus provide steps for implementing the functions/acts specified in the flowchart and/or block diagram block or blocks.

[0070] The flowcharts and block diagrams in the figures may illustrate the architecture, functionality, and operation of possible implementations of systems, methods and computer program products according to 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 illustrations, and combinations of blocks in the block diagrams and/or flowchart illustrations, may be implemented by special purpose hardware-based systems that perform the specified functions or acts, or combinations of special purpose hardware and computer instructions.

[0071] The terminology used herein is for the purpose of describing particular embodiments only and is not intended to be limiting of the disclosure. As used herein, the singular forms "a", "an" and "the" are intended to include the plural forms as well, unless the context clearly indicates otherwise. It will be further understood that the terms "comprises" and/or "comprising," when used in this specification, specify the presence of stated features, integers, steps, operations, elements, and/or components, but do not preclude the presence or addition of one or more other features, integers, steps, operations, elements, components, and/or groups thereof.

[0072] The corresponding structures, materials, acts, and equivalents of all means or step plus function elements in the claims below are intended to include any structure, material, or act for performing the function in combination with other claimed elements as specifically claimed. The description of the present disclosure has been presented for purposes of illustration and description, but is not intended to be exhaustive or limited to the disclosure in the form disclosed. Many modifications and variations will be apparent to those of ordinary skill in the art without departing from the scope and spirit of the disclosure. The embodiment was chosen and described in order to best explain the principles of the disclosure and the practical application, and to enable others of ordinary skill in the art to understand the disclosure for various embodiments with various modifications as are suited to the particular use contemplated.

[0073] A number of implementations have been described. Having thus described the disclosure of the present application in detail and by reference to embodiments thereof, it will be apparent that modifications and variations are possible without departing from the scope of the disclosure defined in the appended claims.