Electronic emergency response management system with automated rule-based alert notifications and response deployment

• US 20060047543A1
• Filed: 08/30/2004
• Published: 03/02/2006
• Est. Priority Date: 08/30/2004
• Status: Abandoned Application

• Current Assignee: Thomas H. Moses
• Original Assignee: Thomas H. Moses
• Inventors: Moses, Thomas H.
• Application Number:
  US10/930,281
• Publication Number:
  US 20060047543A1
• Time in Patent Office: Days
• US Class Current: 705/7
• CPC Class Codes: G06Q 50/265 Personal security, identity or safety
• CPC Class Codes: G08B 21/10 responsive to calamitous events, e.g. tornados or earthquakes
• CPC Class Codes: G08B 21/12 responsive to undesired emission of substances, e.g. pollution alarms
• CPC Class Codes: G08B 31/00 Predictive alarm systems characterised by extrapolation or other computation using updated historic data
• CPC Class Codes: H04L 67/12 specially adapted for proprietary or special-purpose networking environments, e.g. medical networks, sensor networks, networks in vehicles or remote metering networks

Abstract

A computerized method and related system (10) for identifying matches between emergency response units (ERU) and stationary response units (SRU) includes identifying a group of emergency response units, wherein each emergency and stationary response unit has particular physical attributes. A beacon (20, 36) is installed on each emergency response unit in the group and emits a unique identifiable signal. A database (DB) is maintained for identifying each stationary and emergency response unit, their corresponding physical attributes; and a location based on the unique identifiable signal. The database can then be accessed via a call center (12) to determine area response capabilities for a particular type of calamity needing physical attributes provided by the group of emergency response units. The database may also monitor critical assets (CA) such as hazardous material to ensure that they are not diverted, and if so what response units need to respond. The database further includes a set of predetermined rules for generating alert notices to owners of critical assets and vulnerable targets. The rules also identify the manner in which response units are to be alerted.

Claims

1. A computerized method for identifying matches between emergency response units and a response event comprising:

identifying a group of emergency response units (ERU), each said emergency response unit having particular physical attributes;

installing an ERU beacon on each said ERU, said ERU beacon emitting a unique identifiable ERU signal;

maintaining a database identifying each ERU, their corresponding physical attributes, and a location based on said unique identifiable ERU signal;

loading into said database a set of rules associated with each said ERU;

accessing said database to determine area response capabilities for a particular type of response event needing physical attributes provided by said group of ERUs;

applying said unique identifiable ERU signals to said set of rules; and

generating at least one alert based upon matching of said unique identifiable ERU signal with at least one of said rules.

2. The method according to claim 1, further comprising:

identifying a group of critical assets (CA), each said CA having particular physical attributes;

installing a CA beacon on each said CA, said CA beacon emitting a unique identifiable CA signal;

maintaining on said database, each CA, each CA'"'"'s corresponding physical attributes, and a location based upon said unique identifiable CA signal; and

monitoring said group of CA.

3. The method according to claim 2, further comprising:

installing at least one sensor on each said CA which is in communication with said CA beacon and generating an alert signal when appropriate, wherein said monitoring step monitors each said CA and alerts an appropriate ERU whenever said alert signal is generated.

4. The method according to claim 3, further comprising:

maintaining a map in said database with pre-identified features; and

alerting an appropriate ERU whenever one of said CAs is within a predetermined distance of one of said pre-identified features.

5. The method according to claim 4, further comprising:

identifying a group of stationary response units (SRU), each said SRU capable of communicating with select ERUs; and

including in said database a location of each said SRU and an inventory of items maintained at each said SRU.

6. The method according to claim 5, further comprising:

providing a call center which maintains said database and communication links with said ERUs, CA, and SRUs.

7. The method according to claim 6, further comprising:

generating an alert signal when said at least one sensor is disconnected.

8. The method according to claim 7, further comprising:

maintaining a direct communication link between selected ERUs and selected said SRUs.

9. The method according to claim 1, further comprising:

automatically sending said at least one alert to an agency as defined by said set of rules.

10. The method according to claim 1, further comprising:

routing said unique identifiable ERU signal through a telematics provider and than to a call center which maintains said database.

11. The method according to claim 10, further comprising:

loading said set of rules into a limited access website maintained on a global computer information network.

12. The method according to claim 11, further comprising:

designating a priority code for each rule in said set of rules.

13. A system for identifying emergency response capabilities in a geographical area, comprising:

a database component operative to maintain an ERU database identifying emergency response units, their physical attributes and their physical location;

a communications component for observing physical locations of said emergency response units a rules component operative with said database component; and

a processor programmed to;

periodically update said ERU database component with data supplied by said communications component;

process queries to determine response capabilities of the emergency response units in the geographical area; and

generate alerts based upon input received by said rules component for distribution by said communications component.

14. The system according to claim 13, further comprising:

said database component operative to maintain a CA database component identifying critical assets, their physical attributes and their physical location, said communications component observing physical locations of said critical assets;

said processor programmed to;

update said CA database component with data supplied by said communications component; and

process queries to determine the status of said critical assets and determine response capabilities of the emergency response units.

15. The system according to claim 14, further comprising:

at least one sensor coupled to each said critical asset and linked to said communications component, said sensor sending an alert signal upon detection of an abnormal event via said communications component; and

said processor notifying appropriate emergency response units via said communications component upon receipt of said alert signal.

16. The system according to claim 15, further comprising:

said database component further operative to maintain a mapping component, said communications component alerting at least said emergency response units when one of said critical assets is in proximity to pre-designated areas in said mapping component.

17. The system according to claim 16, wherein said processor monitors inventory of said stationary response units and issues on alert via said communications component when said fixed response resources inventory reaches a predetermined level.

18. The system according to claim 13, further comprising:

said database component operative to maintain a SRU database component identifying stationary response units, their physical attributes, and their physical location, said communication component linked to said fixed response resources; and

said processor linking said fixed response resources to said emergency response units when appropriate.

19. The system according to claim 18, further comprising:

said database component operative to maintain a CA database component identifying critical assets, their physical attributes and their physical location, said communications component observing physical locations of said critical assets;

said processor programmed to;

update said CA database component with data supplied by said communications component; and

process queries to determine the status of said critical assets and determine response capabilities of the emergency response units.

22. A system for predicting potential threats, comprising:

a database component operative to maintain a CA database identifying critical assets, their physical attributes and their physical location;

a communications component for observing physical characteristics of said critical assets;

a rules component operative with said database component; and

a processor programmed to;

periodically update said CA database component with data supplied by said communications component; and

perform automated process queries of said rules component to determine whether any one of said critical assets has a physical characteristic outside of a predetermined norm.

23. The system according to claim 22, wherein said processor is programmed to generate an alert signal when any one of said critical assets has a physical characteristic outside of said predetermined norm as determined by said rules component.

24. The system according to claim 22, further comprising:

said database component operative to maintain an RU database component identifying response units, their physical attributes and their physical location, said communications component observing physical locations of said response units;

said processor programmed to;

update said RU database component with data supplied by said communications component; and

analyzes trends associated with said physical characteristics to predict potential emergency events.

25. The system according to claim 24, wherein said processor is programmed to:

generate an appropriate alert signal to said response units best able to respond to the potential emergency events.

26. The system according to claim 25, wherein said processor is programmed to:

generate said appropriate alert signals to agencies designated by said rules component.

27. The method according to claim 26, wherein said processor is programmed to designate code levels with said alert signals.

28. A computerized method for generating alert notifications, comprising:

maintaining a database identifying at least one asset and a set of predetermined rules associated with said at least one asset;

receiving and applying input to said set of predetermined rules; and

sending an alert notification to an agency if warranted by implementation of said set of predetermined rules.

29. The method according to claim 28, further comprising:

deploying at least one telematics device on at least one critical asset;

generating an event message by said telematics device upon detection of an event; and

receiving and applying said event message to said set of pre-determined rules.

30. The method according to claim 29, further comprising:

associating a sensor with each said telematics device;

said sensor monitoring for the occurrence of said event.

31. The method according to claim 29, further comprising:

distributing said alert notification to an owner of said at least one critical asset associated with said event message according to said set of pre-determined rules.

32. The method according to claim 29, further comprising:

distributing said alert notification to a governmental agency in a format established by said set of pre-determined rules.

33. The method according to claim 28, further comprising:

coordinating maintenance of said database, said set of pre-determined rules, and said alert notifications by a call center.

34. The method according to claim 28, further comprising:

deploying at least one telematics device on at least one response unit; and

routing said alert notification to said at least one response unit'"'"'s telematics device according to said set of pre-determined rules.

35. The method according to claim 34, further comprising:

notifying an agency responsible for said response unit that receives said alert notification.

36. The method according to claim 28, further comprising:

notifying an owner of at least one critical asset in a manner defined by said set of predetermined rules.

37. The method according to claim 36, further comprising:

monitoring events associated with said critical asset and determining a risk level according to said set of predetermined rules.

38. A system for generating alerts comprising:

a database component operative to maintain an asset database identifying assets, their physical attributes and their physical location;

a communications component;

a rules component operative with said database; and

a processor programmed to;

monitor inputs received from sources via said communications component or otherwise applicable to said assets;

generate alert notices via said communications component when said monitored inputs are applied to said rules component and deemed to qualify as an event.

39. The system according to claim 38, wherein said processor is programmed to receive inputs from a telematics provider via said communications component, wherein said telematics provider is linked to said sources.

40. The system according to claim 39, wherein said processor is programmed to distribute said alert notices to owners of said asset in a format defined by said rules component.

41. The system according to claim 39, wherein said processor is programmed to distribute said alert notices to agencies defined by owners of said asset in a format requested by said agencies and defined by said rules component.

42. The system according to claim 38, wherein said processor is programmed to receive inputs from sources designated by said asset owner via said communications component.

43. The system according to claim 42, wherein said processor is programmed to distribute said alert notices to owners of said asset in a format defined by said rules component.

44. The system according to claim 42, wherein said processor is programmed to distribute said alert notices to agencies defined by owners of said asset in a format requested by said agencies and defined by said rules component.

45. The system according to claim 38, wherein said processor is programmed to generate said alert notices via said communications component for receipt by a telematics provider linked with, said asset in a format defined by said rules component to deployment of said asset.

46. The system according to claim 38, wherein said processor is programmed to generate said alert notices via said communications component for receipt by a telematics provider linked with, said asset in a format defined by said rules component to deployment of said asset for notification of agencies defined by owners of said asset in a format requested by said agencies and defined by said rules component.