The field of the invention is alert systems and methods therefor.

Currently known alert systems typically include various subsystems to provide effective notification to first responders and a potentially affected population in an area hit by a disaster or other contingency. For example, where an alert system is in the same jurisdiction as a chemical plant processing hazardous materials, subsystems may include pager systems to alert one or more hazmat teams, physicians, hospitals, public sirens to warn the potentially affected population, highway display boards to reroute traffic, and control circuitry that shuts off air intake ducts in shopping malls and other public buildings.

Proper selection and coordination of alert activities is often problematic, especially where the central operator is inexperienced and/or where the emergency fails to conform to a previously established pattern. To alleviate such difficulties, contingency plans can be designed that allow for at least some degree of flexibility. However, even in a relatively sophisticated contingency plan, proper subsystems need to be separately and individually identified, accessed, and operated by the central operator as each of the subsystems typically has individual modes and routes of activation. A typical known alert system is depicted in Prior Art Figure 1A. Here, a contingency plan (typically handbook or manual) is consulted by an operator that then interacts via several and distinct operator interfaces (e.g., siren network using switchboard, pager notification using telephone, etc.) to provide notification. Cleary, such system is time-consuming, error-prone, and will typically be delayed or even fail where two or more types of notification require the same communication channel (e.g., where paging and fax transmission of an action plan employs the same dialer).

Upon notification of a particular incident, the operator enters appropriate information into the computer and is prompted by the rules engine to take certain specific actions (most typically, an administrator has oversight over the implementation and/or design of the rules engine). For example, the operator will be prompted to activate the public siren subsystem, then to page the first responders using specific text messages, and then to display warnings and reroute traffic using the highway display board system. While such notification systems provide at least some guidance to the operator, several difficulties remain.

Among other things, currently known systems require multiple independent activation activities for the respective subsystems. Moreover, and especially where a component of a subsystem is inoperable or otherwise unavailable, the operator typically needs to request alternative routes or modes from the rules engine (if available at all), which is time consuming and error prone. Moreover, system upgrades to add or modify a subsystem will require a modification of the rules engine, which needs to be implemented as soon as possible, or the subsystem will perform in an undesirable manner. Still further, where a subsequent contingency evolved from the first emergency (e.g., earthquake followed by fire, followed by aftershocks that block roadways), coordination and activation of subsystems quickly becomes a daunting task using currently known alert systems.

Such problems are typically compounded where the contingency event spans across multiple jurisdictions. In such an event, it can be almost expected that the subsystems of the Individual jurisdictions will not be responsive to an activation attempt from another jurisdiction. Moreover, even if the subsystems would be compatible to at least some degree, rules engines in different jurisdictions will often reflect economic, geographic, and political characteristics of the particular jurisdiction and therefore dictate inconsistent use of subsystems that are available. As a consequence, synergistic interaction among different jurisdictions is often not achieved as depicted in Prior Art Figure 1B.

Therefore, while numerous configurations and methods for alert systems are known in the art, all or almost all of them suffer from one or more disadvantages. Consequently, there is still a need to provide improved configurations and methods for alert systems, and especially integrated alert systems that facilitate activation and coordination of multiple subsystems.

Document "Design and implementation of a real-time clinical alerting system for intensive care unit",Hsiao-Ting Chen et al., in "Proceedings AMIA Annual Symposium", 1 January 2002, pages 131-135, defines a rules-based notification alert system. Documents US 6 078 649 A (SMALL JAMES M [US] et al.) 20 June 2000 and US 4 141 006 A (BRAXTON KENNETH J) 20 February 1979 define a centralized alert notification system.

The present invention provides an alert notification system as set out in Claim 1. A GUI provides the interactive platform for both rule building and modification as well as for triggering an alert in which multiple distinct alert devices are involved. Most preferably, contemplated alert systems will include a subsystem for each alert device, wherein the subsystem is configured to provide information in a bidirectional manner (e.g., to and from the rules engine and/or GUI). Among other advantages, use of such subsystems allows integration of multiple and distinct alert devices into a single GUI that provides real time information (e.g., on type, status, and operational capability) of all alert devices coupled to the rules engine and/or GUI.

The alert system includes a rules engine informationally coupled to a first subsystem and a second subsystem, wherein first and second subsystems are coupled to first and second alert devices, respectively. A GUI is informationally coupled to the rules engine, wherein the GUI is configured to display an operational parameter and/or an operational status of at least one of the first and second alert devices. wherein the subsystem is configured to provide at least one of the operational parameter and the operational status to at least of the rules engine and the GUI, and wherein at least one of the rules engine and the GUI are configured to allow building of a rule using at least one of the displayed operational parameter and operational status.

In such systems, the first and second subsystems comprise a first and second device adapter and a first and second channel adapter, respectively, and the that first and second subsystems are configured such that the first device adapter controls the second channel adapter if the second device adapter malfunctions or is unavailable. Still further, it is contemplated that the first subsystem has a plurality of redundant first device adapters and a plurality of redundant first channel adapters. Where appropriate, a scheduler may be included that is configured to schedule activation of the first and second alert devices upon activation of the first and second alert devices via the first channel adapter to avoid alert activation conflicts and/or streamline multiple activations through a single channel.

It is contemplated that at least one of the rules engine, the first subsystem, and the second subsystems are configured to automatically provide an updated displayed operational parameter and/or an updated operational status upon modification or exchange of the first alert device. Furthermore, the GUI is preferably configured to allow for operator input of a contingency and to further allow selection of a defined area in which first and second alert devices are to be activated in response to the contingency. The GUI may also be configured to display at least one of the operational parameter and operational status of all alert devices coupled to the rules engine. Still further, it is contemplated that at least one of the alert devices is configured to provide upon activation by the rules engine a feedback signal to the operator, optionally via the GUI. Most preferably, the alert device in such feedback scenario is a computer configured to provide an alert screen to a person, and wherein the alert device is further configured to lock other applications on the computer until the person has provided the feedback signal.

Therefore, and viewed from another perspective, an integrated system for control of multiple subsystems comprising a GUI and an optionally redundant rules engine that is configured to control each of the subsystems, wherein each of the subsystems includes a device adapter that provides bi-directional flow of information between the rules engine and/or GUI and a channel adapter and/or an alert device coupled to the subsystem. In such systems, the information that flows from the at least one of the rules engine and the GUI to the channel adapter is selected from the group consisting of a query into operational capability, a query into operational status, and an alert command based on previously identified operational capability, while the information that flows from the channel adapter to at least one of the rules engine and the GUI is selected from the group consisting of operational capability information, operational status information, and a feedback signal in response to an alert command.

It is further preferred that in such systems the rules engine, the GUI, and the subsystems are configured to allow building of a rule using the GUI, and wherein the alert device and subsystem are configured such that GUI provides real-time information on at least one of operational capability and operational status of the alert device. Additionally, it is preferred that the rules engine, the GUI, and the subsystems are configured to allow activation of a multi-alert device alert using the GUI in response to (a) definition of an affected area and (b) definition of a contingency.

The method of operating an alert system includes a step of providing a GUI, a rules engine, a plurality of subsystems, and a plurality of alert devices, and coupling the GUI, the rules engine, the plurality of subsystems, and the plurality of alert devices to each other such that (a) the subsystems receive alert commands from at least one of the GUI and the rules engine and transfer the alert commands to the alert devices, and (b) the subsystems provide at least one of operational capability and operational status of the alert devices to at least one of the GUI and the rules engine. In another step, a rule is built for the rules engine using the GUI and information displayed on the GUI, wherein the displayed information is the at least one of the operational capability and operational status provided by the subsystem.

The method includes a step of selecting a contingency and defining an area of alert notification using the GUI, and activating a contingency responsive alert in the area using the GUI, wherein the contingency responsive alert employs at least two distinct alert devices, wherein defining the area of notification comprises selecting on the GUI an area using at least one of a Venn diagram, a geographic coordinate, a jurisdictional boundary, an area code, and a Zip code, wherein the GUI optionally displays at least one of a satellite image and a moving or three-dimensional object. Contemplated methods preferably further include a step of receiving feedback information from a person in response to activation of at least one of the two alert devices, and the subsystems are configured such that an alert device is activatable by at least two distinct subsystems.

Various objects, features, aspects and advantages of the present invention will become more apparent from the following detailed description of the embodiment of the invention.

• Prior Art Figure 1A is a schematic illustration of an exemplary known alert system.
• Prior Art Figure 1A is a schematic illustration of failing cooperativity between exemplary known alert systems.
• Figure 2A is a schematic illustration of an exemplary integrated alert system according to the inventive subject matter.
• Figure 2B is a schematic illustration of cooperativity of various exemplary integrated alert systems and prior art systems according to the inventive subject matter.

The inventor has discovered that an alert system can be configured and operated to allow single-click activation of multiple alert devices from a graphical user interface (GUI). In such systems and methods, each of the alert devices is coupled to the GUI and/or rules engine via a subsystem that typically includes a device adapter and a channel adapter, wherein the adapters are preferably configured to allow bidirectional flow of information between the alert devices, the device adapter, the channel adapter, the rules engine, and/or GUI. Contemplated alert systems are preferably driven by a rules engine that cooperates with the GUI to provide a rapid, emergency-specific, and geographically defined alert notification to a relevant population.

In one preferred aspect of the inventive subject matter, the integrated alert system has a configuration as exemplarily depicted in Figure 2A. Here, the alert system 200 includes a rules engine 210, typically run on one or more computers (e.g., server or otherwise networked CPU, preferably physically or logically configured as a single unit) that interface with one or more users via GUI 220 via a local or wide-area network 202. Most preferably, emergency notification is provided by a notifier 204 to the operator 230 via network 202. As in most known systems, the rules engine 210 can be modified by administrator 206. However, it should be especially noted that in contemplated systems 200 the flow of information is not unidirectional (i.e., from operator or administrator to device), but that the GUI and the rules engine can receive information from the subsystems and even from the devices as discussed below. With further reference to Figure 2A, system 200 includes subsystems 240, 250, and 260, and scheduler 270 in an optional tower or rack 204, wherein each of the subsystems are coupled to the respective devices 248, 258, and 268. Each subsystem preferably includes a device adapter 242 and a channel adapter 244 (only enumerated for subsystem #1), wherein each of the device and channel adapters have multiple redundant copies (as hardware copies and/or software copies; shown in Figure 2A as stacked rectangles).

In the example of Figure 2A, it is especially preferred that the all communication paths between the devices and the rules engine are bidirectional. For example, the device adapter 242 of subsystem 240 may poll the channel adapter 244 to enquire what channels of activation are available and provide the polling results to the rules engine 210 and/or the GUI 220. In response to the request, channel adapter 244 may also optionally poll device 248 to identify the operational status and/or other device specific parameters (e.g., what types of signals may be provided to the public). The device reply is then relayed from the channel adapter 244 to the rules engine 210 via device adapter 242. Where two or more alert signals are to be provided using the same channel, scheduler 270 is included to coordinate channel sharing and/or to provide a suitable time sequence for these tasks. As with the device adapters and channel adapters, it should be noted that the scheduler is preferably redundant (in physical and/or virtual copies).

Thus, it should be particularly appreciated that the rules engine and GUI are dynamically updated on the status, availability, and/or capability of the downstream alert devices. Moreover, and viewed from another perspective, it should be recognized that the subsystems of the alert systems contemplated herein are configured to cooperate with a plurality of distinct alert devices and act as unifying and bidirectional communication bridge between the alert devices and the rules engine and GUI. Thus, any given set of alert devices can be controlled and activated using a single GUI by coupling the alert devices to the respective subsystems that then cooperate with the rules engine and GUI. Thus, as the rules engine and/or the GUI are informed of all available alert devices and their functionalities at all times, execution of rules for a contingency is dramatically simplified by defining an alert notification zone in which a predefined set of notifications should take place. The rules engine will then automatically, and in many instances simultaneously activate the downstream devices using available channels as appropriate. Still further, by providing a plurality of subsystems with relatively diverse sets of functionalities, multiple levels of redundancy can be achieved. Most significantly, by using contemplated subsystems, a first alert device (ordinarily activated by its first subsystem) can be activated using a second subsystem.

This is in significant contrast to heretofore known alert notification systems as shown in Prior Art Figure 1A in which an administrator 100 is responsible to generate a response manual or handbook 102 in which emergency response scenarios are outlined for one or more operators (such manuals can be in printed format, or in an electronic version similar to a flow chart). Most typically, each time the emergency system is modified or updated, the administrator 100 must not only update the manual 102 to properly integrate the changes into the contingency responses, but also ascertain that each operator has the latest version available. In case of an emergency, the operator 110 will be notified by the appropriate sources and consults the manual 102 to identify the appropriate course of action depending on the type of emergency. In the example of Figure 1A, the operator 110 then activates in sequence, and according to the manual 102, the first device 120A (e.g., siren) via interface 112A (e.g., siren controller), the second device 120B (e.g., pager) via interface 112B (e.g., dialer/text messenger controller), the third device 120C (e.g., highway display board) via interface 112C (e.g., board controller), and the fourth device 120D (e.g., TV alert) via interface 112D (e.g., TV alert controller).

With respect to contemplated GUIs it is generally preferred that the GUIs is a map-based interface, optionally with a satellite aerial view overlay. Furthermore, it is generally preferred that the GUI also provides pictograms or other identifiers of locations of relevant objects (e.g., location of plants, hospitals, sirens, fire stations, etc.) in the displayed map. There are numerous manners of displaying interactive maps known in the art, and all manners are deemed suitable for use herein. For example, contemplated maps may be two- or three-dimensional representations of a particular location, area, county, state, or country (most preferably to scale). Alternatively, or additionally, suitable maps also include more abstract maps, including those in which at least one of streets, rails, waterways, cities, geographical features, and political lines are illustrated in a schematic manner. It is still further preferred that such map-based GUIs allow zooming, panning, and/or jumping to a specific location (e.g., by entering a geographic coordinate, ZIP code, name of location, etc.). Moreover, and where desirable, contemplated map-based GUIs will provide multiple alternative views of the same location between which an operator can toggle, or which are at least partially overlaid on the same screen.

The GUI also displays all alert devices located in the displayed area (e.g., as a siren symbol, highway display board, etc.) and further provides for each of the alert devices at least one of two on-screen options: First, the GUI displays operational status and/or all available commands for a particular alert device, wherein the data for status information and/or available commands are drawn directly (and most preferably automatically) from at least one of the alert device, the channel adapter, and the device adapter using the bidirectional features of the subsystem for the alert device. Second, the GUI is preferably also configured such that during rule making an administrator can select one or more of the available commands for a particular device to be executed for a specified contingency. Therefore, it should be appreciated that the GUI will greatly assist the administrator in the rule making process by having displaying the actual device capabilities from the devices installed in the field. Still further, if a device becomes inoperable, or is replaced with a device having not identical capabilities, the rules engine and/or GUI can notify the operator and/or administrator of a change in the operational status or capabilities and prompt for repair or updating of the rules engine.

Once the administrator has completed installation and/or updating of the rules in the rules engine, area-specific activation for predefined rules may be performed in numerous manners. For example, where an area is likely to be hit by a tornado, the operator may display that area on the GUI and define by point-and-click, click and drag, or other mouse or trackball based operation an area (e.g., circular rectangular, etc.) in which the appropriate alert devices are set off. In such an example, the operator may define the area by clicking on the potentially affected counties and then select from a predefined set of contingencies the option 'tornado warning'. Based on the rules that were established using device and channel information of the associated alert devices and other parameters, the appropriate devices are then activated in the selected areas using the GUI.

Alternatively, activation of alerts in a specific area may also be performed using Venn diagram-type operations (e.g., multiple areas selected with certain overlapping areas excluded and others defined with modified parameters), or be performed by entry of a ZIP code, telephone area code, city and/or county name, using any known input device (including voice recognition software). In still further preferred aspects, a geographic coordinate (e.g., identified by longitude and latitude), location name, or other identifier may be associated with an object, and most preferably a 3-dimensional object, to provide further detailed information. For example, the object at the particular coordinate may be a (multi-story) building, wherein the GUI provides a three-dimensional representation of that building having one or more significant items (e.g., remote-controllable components of the building, such as entry doors, ventilation systems, public announcement system, etc.). In such examples, the GUI may be programmed to display the building, factory, or other structure as an icon or other graphic representation (e.g., schematic using floor plan, or photographic), wherein the operator may select detail views (e.g., to focus on a particular floor level of a building, or particular device within the building and/or floor). Thus, it should be recognized that single objects at a coordinate may be expanded to display multiple aspects and/or devices, wherein such devices are preferably coupled to the GUI via a subsystem as discussed above. Therefore, such devices may also be remotely controllable via the GUI. Among other example, devices in a building controllable using the systems contemplated herein include air intake vents, access controlled doors, audible/visual alarm systems, display boards/screens, etc. Still further contemplated objects displayed on the GUI may be mobile. Among other suitable choices, such objects include school buses, mobile hospitals, etc, wherein such mobile objects may have one or more remotely activated devices (e.g., messaging system, ignition interrupt, etc.). Typically, activation follows a rule from the rules engine. Furthermore, in such mobile devices, it is generally preferred that the mobile device provides positional information to the GUI.

Consequently, it should be noted that the GUI can be used to program the rules engine using information provided by the subsystem (device adapter and/or channel adapter) and that the GUI is also used to (a) define an alert area (b) selected from a predefined set of emergencies the applicable choice, and (c) trigger the appropriate alert devices in the defined area. In yet further contemplated aspects, the user input on the GUI may also be bypassed by installation of an I/O controller that directly interacts with the rules engine (see below). Such user independent input is typically optional and available as an additional and alternate manner of providing an alert.

Once a desired region for an alert notification and the suitable action for the selected region been defined using operator input via the GUI, the rules engine will preferably identify available subsystems, their operational capability and status, and optionally display and/or highlight those subsystems on the GUI. Depending on the particular contingency and predefined rules (also known as recipes), the rules engine will typically request a confirmation from the operator to activate simultaneously (or in a predetermined sequence) and automatically multiple appropriate subsystems. It should be noted that such an integrated system will greatly facilitate proper and expeditious operation of the alert system as the user only has to define the area to be alerted and to specify the type of contingency.

It is generally preferred that the rules engine is configured as a single logical unit and closely cooperates with the GUI to display area-specific information, alert device specific information, and contingency specific information. However, in alternative aspects of the inventive subject matter, the rules engine may also be located and/or executed on separate computers, which may be physically or logically distinct units. Furthermore, it should be noted that more than one operator may interact via more than one GUI with the rules engine. For example, different departments (e.g., fire, police, homeland security) may use the same GUI in distinct locations and may be logically coupled to the same rules engine. Thus, contemplated rules engines may be physically present as one or more computers, which may operate independently, or interconnected using networks well known in the art.

The rules engine is preferably software based and configured by an administrator via the GUI. In a typical operation, the rules engine will poll all available subsystems (and optionally even alert devices) to collect positional and/or operational information of the associated alert devices, and relate at least some of the information to the GUI. The GUI will then present the alert devices in the respective positions on the map or other graphical representation. The administrator can then define recipes based on likely or anticipated contingencies using the alert device capabilities presented on the GUI. Once the rules are defined, activation of suitable alerts in response to a contingency only require an operator to specify the contingency and the area to be alerted. Thus, it should be appreciated that the integrated system not only provides a simple and efficient mode of rule building, but also provides a simplified mode of activation of numerous alert devices in a single activation device (GUI), even if multiple channels or channel conflicts are present. Moreover, contemplated systems also provide for manners of activation of alert devices that transcend boundaries ordinarily set by jurisdictions, departments, or other predefined structures of authority or command. Therefore, the rules engine will most typically receive commands for alert notification from the GUI and pass the appropriate alerts then to the alert devices via the device/channel adapters.

However, in further aspects of the inventive subject matter, the rules engine can also receive one or more commands from an I/O device that is preferably coupled to the rules engine via a subsystem having at least one of a device adapter and a channel adapter. Such configuration will advantageously provide a fully automated operation in which a plurality of alerts using a plurality of channels can be triggered in a user independent manner (i.e., no need for an operator to define type of emergency and area of notification) in a predetermined fashion. In such configurations, an alert device is replaced with an I/O (Input/Output) module to allow the rules engine to receive an input from an external device. While all known external devices are deemed suitable, especially preferred external devices include PLCs (programmable logic controllers), sensors reactive to a chemical, microbial, or radiological stimulus, and alert radios (e.g., those receiving a NOAA weather alert). In such systems, the rules engine can be programmed to activate an alert sequence that has been preestablished upon a response received from the input channel rather than from an operator.

For example, actions could be set up that would call selected responders in an emergency via a telephone device/channel adapter, set off certain sirens via a siren device/channel adapter, and trigger computer emergency messaging (e.g., using Notifier, commercially available from Centralert Corp., Kennewick, WA) that could provide appropriate messages to selected computers on a network. This action could be automatically activated by an I/O module that is either directly coupled to the rules engine, or that is coupled to the rules engine via a subsystem in the same way as an alert device. For example, if NOAA issues a tornado warning, an alert radio coupled to the I/O module would receive the NOAA signal and close a contact in the I/O module, which in turn is coupled to the rules engine to thereby initiate the above action.

The rules engine is also configured to cooperate with the subsystems to provide increased redundancy using the bidirectional flow of information across the subsystems. For example, where the device adapter of a first subsystem is nonfunctional, the rules engine can detect such non-function and activate a device adapter of a second subsystem. The device adapter (or redundant copy thereof) of the second subsystem is then instructed by the rules engine to provide the activation signal to the channel adapter of the first subsystem for activation of the alert device coupled to the first subsystem.

With respect to the subsystems, it is generally preferred that each subsystem comprises a device adapter and a channel adapter that control the operation of an alert device. Most typically, the device adapter and the channel adapter are electronically coupled to the computer(s) running the rules engine via the device adapter, while the alert device is coupled to the channel adapter. There are numerous manners of electronically coupling computer devices known in the art, and all known manners are deemed suitable for use herein. For example, coupling of the device adapter to the computer running the rules engine may be performed using Ethernet connectivity, Internet connectivity, wireless connectivity (e.g., Bluetooth, cellular, radio, satellite, etc.) using well known protocols, and all reasonable combinations thereof. Similarly, the alert devices can be coupled to the channel adapters using all manners known in the art. For example, a telephony, paging, and/or fax system (optionally interactive) can be coupled to the subsystem via a phone jack (and dialer acting as the channel adapter), while a highway display board system may be coupled to the subsystem via wireless connectivity. In further contemplated aspects, it should be noted that at least one component of the subsystem may also be a virtual component that is simulated by software executed on a distinct computer and/or the computer that also runs the rules engine and/or GUI.

Thus, and viewed from one perspective, a device adapter may be viewed as an electronic representation or replica of the actual alert device, wherein the device adapter is configured to electronically communicate with the rules engine, and wherein the device adapter provides information of the operational capabilities and/or status to the rules engine/GUI. Communication is preferably done via standard interface technology and may therefore include USB ports, parallel and/or serial ports, Bluetooth connectivity, etc. Therefore, and viewed from another perspective, contemplated device adapters are not merely passive devices that receive electronic commands from the rules engine, but are interactive devices that provide the rules engine (preferably upon query) with information on status and/or capabilities of the downstream installed alert device. Moreover, in still further preferred aspects, the device adapter will also have querying capabilities to determine the operational status of the associated channel adapter and downstream alert device, which the device adapter will then relay to the rules engine. In addition, it is contemplated that failure of communication to and/or from a device adapter may trigger operation of the device adapter in fail safe mode.

Device adapters may be configured in numerous manners, and all known manners are contemplated suitable for use herein. For example, where suitable, device adapters may be program modules that simulate the downstream alert device. Such virtual adapters may be run on a separate computer, or on the same computer on which the rules engine runs. Alternatively, the device adapter may also be a hardware device that is electronically coupled to the rules engine. Such hardware devices may be plug-and-play cards that are installed on the computer that executes the rules engine, or may be devices installed or operating independently of the computer that executes the rules engine. In still further particularly preferred aspects of device adapters contemplated herein, the device adapter may be configured as a multiple redundant device with redundant copies at the same locale, and/or with at least one redundant copy in a remote position (exemplary redundant systems are described in our copending U.S. provisional application with the serial number 60/522,865, which was filed November 15, 2004.

Moreover, preferred device adapters will be configured to not only provide redundancy within a single subsystem, but also to provide functional capabilities of a second device adapter that is functionally associated with a second, distinct subsystem. For example, a device adapter for a pager notification alert subsystem may also include functionalities of a device adapter for a fax notification subsystem, and/or a telephonic notification subsystem. Therefore, vertical as well as horizontal redundancy is realized. Consequently, it should be appreciated that one device adapter may be electronically coupled to at least two channel adapters. Such cross coupling may be done via cable connectivity as well as logical connectivity (e.g., where multiple device adapters of multiple subsystems are run in a single computer) and is schematically illustrated in Figure 2A as lines crossing between subsystems 1 and 2, optionally using different copies of the redundant device adapters.

With respect to contemplated channel adapters, it should be recognized that the channel adapter will preferably be coupled between the device adapter and an alert device. Particularly preferred channel adapters will therefore translate signals received from the device adapter (and with that signals from the rules engine) into signals that will drive directly or indirectly the actual alert device using pathways suitable for the alert device. For example, suitable channel adapters include telephone dialers, radio transmitters, optical network components, simple wiring, etc. There are numerous such devices known in the art, and all of those are deemed suitable for use in conjunction with the teachings presented herein. However, and in contrast to currently known alert systems that are passive systems in which commands flow only from the rules engine to the alert device, contemplated channel adapters will be configured to provide bi-directional flow of information between the channel adapter and the device adapter/rules engine and between the channel adapter and the alert device.

Similar to the redundancy for the device adapter discussed above, it is generally preferred that the channel adapter is configured to provide multiple levels of redundancy. Among other things, suitable channel adapters may include multiple copies (e.g., physical and/or virtual, collocated or in different locations). Alternatively, or additionally, contemplated channel adapters for one subsystem (e.g., pager subsystem) may also provide functionalities for another subsystem (e.g., public siren subsystem). Therefore, redundancy is achieved not only within components of one subsystem, but also among multiple components across multiple subsystems. Subsystems, device adapters, and/or channel adapters may be located in a single device, multiple directly connected devices, or in a plurality of independent devices that may be networked using network protocols well known in the art. Furthermore, the subsystems and/or devices are preferably, but not necessarily, logically separated, While it is generally preferred that the channel adapter will be a separate device and/or program, integrated functionality between device adapter and channel adapter into a single program, board, and/or device are also contemplated. Furthermore, the device adapter and/or the channel adapter are configured as plug-and-play modules such that a user can add, modify, or remove a device with only minimal technical knowledge.

Thus, and especially where contemplated rules engines are standard in a jurisdiction, it is contemplated that the subsystem, device adapter, and/or channel adapter may be offered not only by the providers of the alert system, but also by the providers of alert devices to allow the alert device manufacturer to have seamless integration into a standardized system. Consequently, it should be noted that contemplated alert systems provide a platform for unification of diverse alert devices and communities in which existing devices are maintained and integrated into the alert system using the device adapter/channel adapter. Moreover, such integration advantageously also allows simplification and streamlining of configuration of the rules engine by using bidirectional flow of information. Consequently, and as already discussed above, the rules engine will preferably include a functionality that allows bidirectional communication between the rules engine and downstream components of one or more subsystems to identify operational functions, operational status, and/or availability for an alert device.

Preferably, the rules engine will be programmed such that the operator/administrator can configure an emergency response in a flexible manner in which the capabilities of the alert devices are made available to the operator/administrator without actual knowledge of the device in the field. In most instances, the rules engine will query the device adapter, which will provide device-specific information (available functionality, operational status, etc.) to the rules engine. Such feedback may also involve querying of the channel adapter and/or the alert device. Among other advantages, it should be especially recognized that contemplated integrated alert systems not only allow an operator initiate a comprehensive and preprogrammed multi-device alert with a single click on a single system, but also enable an operator/administrator to adaptively program a rules engine with capabilities that are actually present in the field. Still further, contemplated bi-directional communication capabilities may also be employed for periodic operational checks of the system, which may alert the system operator of malfunctions, intrusions, or other remote events.

Additionally, or alternatively, the rules engine and/or subsystem may be configured in a manner that allows receipt of confirmation of receipt of a notification by an alert device. Such confirmation is particularly advantageous where the alert device includes a telephone system, a pager system, a text messaging system, and/or a Internet based alert system. Among other benefits, an operator may readily assess the emergency response force available for a particular incident and initiate subsequent alerts or de-escalating notifications. For example, an instant messaging system may be provided in which a first responder is notified by a pop-up message that will disable other use of the responders computer until acknowledgement has been sent to the rules engine or other component/operator in contemplated systems. Thus, an authorized user may not only notify another user, a group, or area of users and but also receive feedback from the notified parties. Communication may be facilitated among users/responders separate from general broadcast, chat, or instant message.

With respect to contemplated alert devices it should be appreciated that all known alert devices are deemed suitable for use herein, including personal alert devices, group alert devices, and public alert devices. For example, contemplated public alert devices include highway billboards, sirens, tone alert radios, and public announcement speakers, while suitable group alert devices include emergency pagers, cell phones, etc. Contemplated personal alert devices include TV sets, radios, telephone, and walkie-talkies. However, and as already discussed above, the alert system according to the inventive subject matter can also be used to remotely control operation of control devices that are coupled to the rules engine/GUI via an appropriate subsystem. For example, such control devices include access control devices, ventilation components, electronic control circuits of vehicles, etc.

Additionally, it should be appreciated that two or more systems according to the inventive subject matter may informationally coupled to each other as exemplarily depicted in Figure 2B. Here, alert systems 200B (corresponding to the system 200 as depicted in Figure 2A) of three jurisdictions are informationally coupled to each other via a wide area network (e.g., fiber optic network on Internet) and have subscribed to event-based notifications (e.g., earthquake or tsunami notification among three counties). As with the system 200 of Figure 2A above, notification can be provided by automated sensors (e.g., seismic, chemical, biological), operator input from emergency response departments (e.g., police or fire), and/or from commercial notifiers. It should be recognized that in such systems notification can be relayed among all subscribing parties and automated notifications advantageously may trigger downstream notifications in each of the subscribing parties in an automated manner. Moreover, and depending on the particular configurations, even heretofore known alert systems (201B) may be at least partially included in the subscription system as also depicted in Figure 2B.