US20080071442A1 - Method and apparatus for global relief management - Google Patents
Method and apparatus for global relief management Download PDFInfo
- Publication number
- US20080071442A1 US20080071442A1 US11/878,771 US87877107A US2008071442A1 US 20080071442 A1 US20080071442 A1 US 20080071442A1 US 87877107 A US87877107 A US 87877107A US 2008071442 A1 US2008071442 A1 US 2008071442A1
- Authority
- US
- United States
- Prior art keywords
- field
- information
- field assessment
- data
- assessment
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Abandoned
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
- G06Q99/00—Subject matter not provided for in other groups of this subclass
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/912—Applications of a database
- Y10S707/918—Location
- Y10S707/919—Geographic
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/912—Applications of a database
- Y10S707/922—Communications
-
- Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10—TECHNICAL SUBJECTS COVERED BY FORMER USPC
- Y10S—TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
- Y10S707/00—Data processing: database and file management or data structures
- Y10S707/99931—Database or file accessing
- Y10S707/99939—Privileged access
Definitions
- the present invention is directed to a system for managing field level evaluation and relief efforts and, more particularly, to a system for inputting, characterizing, managing and distributing information for the provision of humanitarian relief over large and remote geographical areas.
- a primary objective of organizations, agencies and other entities providing humanitarian relief is to provide immediate, necessary relief to victims of humanitarian crises arising from, for example, natural disasters such as floods, earthquakes, hurricanes and man-made disasters such as war.
- the destruction in such situations can involve dwellings, agricultural systems, health-care systems, sanitation, transportation, water and power systems.
- the crises further include the human risks facing displaced populations occupying regions themselves having inadequate supporting infrastructure.
- several relief agencies respond.
- the several agencies may provide concurrent relief assistance, and/or different agencies may provide different assistance at respective stages of the overall relief effort.
- the agencies must have, and be able to distribute, accurate, real-time information describing the situation.
- a plurality of relief agencies responds.
- the agencies may be international organizations (IG), government organizations, (GO), and non-government organizations (NGOs).
- IG international organizations
- GO government organizations
- NGOs non-government organizations
- Each agency typically begins its relief effort by sending in a number of its field personnel.
- the initial mission of the field personnel is to obtain damage assessment reports for their respective agency.
- the field personnel typically generate the damage assessment reports by traveling to a damage site and writing down unformatted personal observations on the site's geography, a general summary of the population and developmental condition of the area prior to the disaster, if that information is available, and an inventory or estimate of the damage.
- the field person might write in a notebook that a village named X had an estimated pre-damage population of two thousand, the population occupying approximately five hundred mud-brick homes, and that they had a local power generating station, and a local water supply.
- the field person would then write an estimate/inventory of the damage.
- the write-up information would include, in an unformatted manner, that approximately 100 mud-brick homes were still standing, about 200 were damaged but had the majority of their outer walls reasonably intact, and that the remainder were destroyed. It would further an estimate of injuries, by number and type of injuries, and the deaths, including the locations and retrievability of the bodies.
- Other information would be, for example, the field person's observation on the local water supply, including the reservoir, or the wells, and the filtering facilities and distribution system, and assessments of the electrical power system, and other systems of the local economy.
- the field person After writing the information, the field person would typically type a report and e-mail or fax it to the agency. The agency would then, based on the information, estimate the relief it could provide.
- An example embodiment of the present system and method includes providing a database having a plurality of damage characterization data and a geographical location associated with each.
- a plurality of portable communication units are provided, each having a display, a manual data entry mechanism, and a geolocation detector for generating a geolocation data based on an externally generated geolocation signal.
- a first of the portable communication units is associated with a first subscribing party and a second of the portable communication units is associated with a second subscribing party.
- a sharing privilege list identifies, for the first subscribing party, at least one other subscribing party authorized to receive damage assessment data from the first subscriber.
- a geolocation data is generated at the first of the portable communication units based on its geolocation.
- a damage assessment data is input, by the user, into the first of the portable communication units.
- a damage assessment report is transmitted from the first of the portable communication units to the database, the damage assessment report including data reflecting a damage assessment data, an identification data identifying the sender of the damage assessment report, and the geolocation data.
- the database is updated based on the damage assessment report. Then, depending on whether or not the second subscribing party is on the sharing privilege list, a data is communicated to the second of the portable communication units reflecting, or based on, the damage assessment report.
- a plurality of subscribing party headquarter communication units is provided.
- a first of the subscribing party headquarter communication units is associated with the first subscribing party and a second of the subscribing party headquarter communication units with the second subscribing party.
- at least one data reflecting the damage assessment report is communicated to the second of the subscribing party headquarter communication units.
- FIG. 1 is an example high level block diagram of an example embodiment of the described system
- FIG. 2 is an example high level system-level software architecture supporting the FIG. 1 system
- FIG. 3 is an illustrative diagram showing an example functional hierarchy of users of, and nodes within a described system such as that of the FIG. 1 example;
- FIG. 4 is an example functional flow chart for a mobile application such as, for example, a damage assessment report uploading;
- FIG. 5 is an example functional flow chart for web application such as, for example, receiving a damage assessment report from a field unit and, in response, conditionally updating the databases and distributing the information;
- FIG. 6 is an example damage assessment form with user selectable options, displayed on a field unit, for the user to input and upload damage assessment data;
- FIG. 7 is an example situational map all, or part of which, is displayed on the user's field unit.
- FIG. 8 is an example set of symbols for a real-time situational map.
- the term “relief agency” encompasses all of the phrase's ordinary and customary meanings including, but not limited to, government, non-government, and international organizations and other entities that assess damage wrought by natural forces, such as hurricanes, typhoons, earthquakes, and the damages wrought by man-made forces such as war and insurrection.
- the described system is an end-to-end service through which field personnel inspect and collect information from disaster areas, the information is organized as a selectable privilege-based user-accessible database, and the information is distributed among, through default and user-selectable formats, and between disaster relief agencies, and other users through privilege-based access.
- An example of the described system includes a central information distribution and management center, one or more agency headquarter centers, and a plurality of field units, which are portable communication devices carried by or mounted to the vehicles of field personnel.
- a typical system further includes a wide-area communication network such as, for example, the Internet, and other described networks for communication among and between the field units, the central information management center, and the one or more relief agency headquarter centers.
- a wide-area communication network such as, for example, the Internet, and other described networks for communication among and between the field units, the central information management center, and the one or more relief agency headquarter centers.
- the field units operate within, and have circuitry for utilizing, a geo-positioning system such as, for example, the Global Positioning System (GPS).
- a geo-positioning system such as, for example, the Global Positioning System (GPS).
- GPS Global Positioning System
- the field units display graphical user interface (GUI) forms to the user for entry of damage assessment information and for uploading the information as a damage assessment report.
- GUI graphical user interface
- the forms are typically stored in the field units, and are typically customized for the particular relief agency associated with the field person possessing the field unit. Updating of the forms by downlink from the central information management center is contemplated.
- the damage assessment reports include the geolocation of the sending field unit and a data, or other information, identifying the relief agency associated with the sender.
- the central information management center has distribution privilege data that typically maintains, for each relief agency, a list of other agencies, if any, to which the sending agency's damage assessment report information may be distributed.
- the distribution privilege data may specify the distribution more particularly, such as certain types of information being distributed to certain other agencies.
- the field units also display real-time maps to the user, a typical map utilizing geographical map data stored in the field unit on which updated situation information, received by downlink from the central information management center, is overlaid and displayed.
- WAN wide-area networks
- VPN virtual private networks
- LAN local area networks
- LAN local area networks
- LAN commercially available database software and hardware systems
- interface protocols for users to access same, available satellite telephone systems, cellular telephone systems, and personal computers and hand-held computing devices. Details for implementing the described systems and methods, to the extent such details are knowledge possessed by persons of skill in the above-listed arts, by which such persons after reading this description can select from among, configure and assemble commercial components into the described systems, are omitted.
- FIG. 1 shows a high-level functional block diagram of an example embodiment of the system.
- FIG. 2 is an example system-level software architectural chart for the software supporting, and implemented on, the FIG. 1 system.
- FIG. 1 is a graphic representation of an example and is arranged according to functional blocks. The depicted block segmentation and arrangement is selected to assist in the understanding of functions and operational features of the described system. The depicted blocks do not necessarily represent, or limit, the physical hardware blocks, or subsystems, for implementing a system in accordance with this description.
- various functional blocks of the FIG. 1 example diagram may be implemented on a distributed arrangement of, for example, mass storage units and servers.
- FIG. 1 a single interconnected system of mass storage units, servers and user interface devices may perform the functions represented by a plurality of FIG. 1 functional blocks. Still further, the particular FIG. 1 segmentation of functional blocks, and the labeling of the blocks, is for purposes of example only, and is not a limitation on the scope of the particular architectures, communication and database structures that may be used for implementing the described system.
- the depicted example system includes a network operations center 10 , which is referenced hereinafter as the GRT network operations center 10 , its associated GRT data center 12 , a plurality of customer field sites 14 , and one or more customer headquarter centers 16 .
- a field unit communication network 18 provides for uploading communications from the plurality of customer field sites 14 to the GRT data center 12 and for downloading communications from the GRT data center to the plurality of customer field sites 14 .
- the uploading function of the wireless communication network 18 is represented, along with an example list of specific uploading communications, as block 20 .
- the downloading function with an example list of download operations, is represented as block 22 .
- a WAN 24 provides for communications between the one or more customer headquarter centers 16 and the GRT data center 12 .
- the uploading function of the wide area network 24 is represented, together with an example list of specific uploading communications, as block 26 .
- the downloading function of the wide area network with an example list of download operations, is represented as block 28 .
- an example customer field site 14 is a portable computing device, preferably ruggedized, such as, for example, a Panasonic ToughbookTM, a Howard Portall WorkbookTM, or any of the equivalents available from various commercial vendors.
- the customer field site 14 includes a wireless communication feature, of a type dependent on the implementation of the field unit communication network 18 in which the unit 14 is operating. Examples off-the-shelf wireless communication devices are an INMARSAT GAN and an INMARSAT Mini-M, which are readily attached to commercially available portable computing devices, such as the Panasonic ToughbookTM and other off-the-shelf examples of the field site 14 identified herein.
- the customer field site 14 further includes a GPS receiver, or an interface to an external GPS receiver.
- An example GPS receiver which connects to the Panasonic ToughbookTM and to equivalent laptop computers, is the Trip-NavTM model TN 200 GPS receiver with Universal Serial Bus (USB) connectivity.
- USB Universal Serial Bus
- a field unit 14 is a hand-held computing device such as, for example, a DellTM AximTM X5 or X3i, preferably ruggedized with a commercially available environment casing, or “skin”, or an equivalent hand-held such as the Symbol TechnologiesTM model SPT-1800TM or model PPT-2800TM, the hand-held computing device, having a GPS receiver such as, for example, a LinksPointTM GlobalPointTM GPS, or a PharosTM model PFD22TM GPS receiver, and having, for example, an INMARSAT Mini-M Satellite Phone.
- GPS receiver such as, for example, a LinksPointTM GlobalPointTM GPS, or a PharosTM model PFD22TM GPS receiver
- INMARSAT Mini-M Satellite Phone are only for purposes of example. Persons of skill in the relevant arts can, upon reading the present description, readily identify equivalent kinds and models of off-the-shelf devices available from various commercial vendors.
- an example implementation of the GRT network operations center 10 and its associated GRT data center 12 is the date center 12 including one or more commercially available application servers 30 , a GRT database 32 , a web server 34 , and an optional firewall 36 , and the GRT network operations center 10 including a plurality of user terminals 38 .
- the GRT network operations center 10 , the GRT data center 12 and the customer headquarter centers 16 are functional blocks, and each is not necessarily a single brick-and-mortar facility.
- the GRT network operations center 10 and the GRT data center 12 are functional blocks, and are not necessarily implemented on hardware systems separate from one another. Accordingly, the terminals 38 may be co-located with one another and with the computer hardware of the GRT data center 12 , or may be distributed over a wide geographic area.
- the described components of the GRT network operations center 10 and the GRT database 12 are connected to one another using, for example, a LAN.
- the LAN connection is only an example because, as stated above, one or more of the functions of the GRT network operations center 10 and the GRT database 12 can be implemented on distributed hardware systems.
- the GRT database 32 may be a distributed cluster of server-controlled mass storage devices, interconnected by, for example a virtual private network (VPN) carried over the Internet. Construction, operation and maintenance of distributed cluster databases is known to persons of ordinary skill in the arts pertaining to this described system.
- VPN virtual private network
- FIG. 1 application server 30 of the GRT network center 10 is a Dell PowerEdgeTM server or a Sun SunFireTM server, running under a standard commercially available operating system.
- An example implementation of the database 32 is a Dell PowerVaultTM Storage Unit.
- the identified examples of makes and models of the server 30 and the database 32 are only for purposes of illustration. Many alternative commercially available implementations can be chosen from, and the selection from these is a design choice based on conventional selection criteria known to persons of ordinary skill in the computer arts. Examples of such selection criteria, which are known, include, for example, the number of users, size of the database, desired access time, and desired security.
- the GRT terminals 38 may be, for example, conventional personal computers or may be what is termed in the pertinent arts as an “ultra-thin client” having only a data input/output device and a visual display device.
- a typical preferred embodiment is a satellite phone system such as, for example, INMARSAT, because satellite phones provide excellent coverage, to even the most remote areas, and do not require a local communications infrastructure.
- Another contemplated embodiment is a cellular-type network, at least for the portion of the communication network 18 to which the field unit 14 interfaces.
- bandwidth requirements it will be understood from the further detailed description of the present methods and their example operations that the bandwidth requirements of the field unit communication network 18 , at least for the preferred embodiments, are not particularly high.
- ASSESSMENT files and the transmitted DAMAGE ASSESSMENT REPORTS containing same that will be uploaded by the field units 14
- AREA SITUATION GIS reports that will be communicated from the GRT network operations center 10 to the field units 14 .
- WAN 24 connecting the GRT network operations center 10 and its associated GRT data center 12 to the one or more customer headquarter centers 16 may be implemented on the Internet, or on a combination of the Internet and point-to-point T1 lines, the T1 lines being leased from commercial communications entities as known in the art.
- FIG. 2 shows an example system level chart for the software supporting and implemented on the FIG. 1 example system. Dotted line boxes on FIG. 2 that have number labels corresponding to the number labels of functional blocks of FIG. 1 are the software blocks corresponding to that functional block Referring to FIG. 2 , the block labeled “Backend,” with reference numbers 10 and 12 , represents the software architecture for the GRT network management center 10 and the GRT database 12 .
- the web server block 40 within the Backend block is the web server block 40 , which is the software associated with the FIG. 1 web server 34 .
- the web server block 40 processes DAMAGE ASSESSMENT REPORTS and other data uploads and requests from the field units 14 , as well as access and other requests from the client headquarter centers 16 .
- Example commercial software for implementing these web server 40 functions includes the Java Virtual Machine Servlet engine.
- the other software blocks in the Backend are the GIS Application block 42 , the GRT Application block 44 and Relational Database Management System 46 .
- the GIS Application block 42 creates, distributes and administers, under the control of the GRT Application block 44 , GIS services described herein, and the associated integration of data from the field units 14 , the GRT database 32 , and outside databases.
- Example commercial software for implementing the GIS Application block 42 includes ArcMS ⁇ and ArcSDETM from ArcSoftTM Corporation, and equivalent software products from other suppliers such as, for example, ESRI Corp. and Autodesk Corp.
- the Relational Database Management System block 46 performs the data storage and management functions described herein, and example implementations include the Microsoft SQL Server product.
- the GRT Application block 44 preferably resides on the FIG. 1 application server 30 , and performs the described GRT GIS map and associated data services, including updating the GRT GIS maps in response to DAMAGE ASSESSMENT REPORTS, maintaining different GRT GIS maps for different relief agencies, overseeing the transmission of described reports and alerts to the field units 14 , and to relief agencies, and others, associated with the customer headquarter centers 16 .
- Person of ordinary skill in the pertinent arts listed above can readily write the GRT Application block software, using commercially available software languages and development tools.
- the dotted-line block labeled “Clientside(Field),” having the reference number 14 is a generic representation of the software resident on the field units 14 .
- the FIG. 2 Clientside(Field) block includes the Field GRT Application block 48 and the Field Database block 50 .
- the Field GRT Application block 48 is typically a subset, at least in part, of the GRT Application block 44 of the Backend block.
- the functions of the Field GRT Application block 48 which are more fully described in reference to FIGS. 4-6 , include login operations, overlaying GIS data with stored local maps, and the upload and download operations for connecting to, and receiving situational data and alerts from the network operations center 10 and other FIG. 1 blocks corresponding to the FIG. Backend block containing software blocks 40 , 42 , 44 , and 46 :
- the functions of the Field Database block include storing local geographical maps and damage assessment forms.
- the dotted line block labeled “Clientside(HQ)” with the reference numeral 16 includes the Viewer software application block 52 and the Client Headquarter GRT Application block 54 .
- the function of the Viewer block 52 is for the client, such as home office personnel of a relief agency, to be able to view the situational maps downloaded to the agency's field units 14 , and the DAMAGE ASSESSMENT REPORTS received from its field units 14 .
- the block 54 is shown as a dotted line because typical embodiments contemplate no significant application software required at the client headquarter centers 16 . Instead, the preferred embodiment contemplates the Client Headquarter GRT Application block 54 as an application within the GRT Application block 44 of the FIG. 2 Backend.
- the Viewer application block 52 can be implemented as, for example, a Microsoft Explorer or equivalent web browser. It can therefore be seen that the client headquarter centers 16 are not limited to brick and mortar facilities. On the contrary, a relief agency can provide certain of its personnel with, for example, laptop computers, and agency proprietary administrative privilege codes allowing the person to connect, from any location having Internet access, and from that location be a client headquarter center 16 . Software features for the Backend Web Server application block 40 , and the GRT Application block 44 implementing such a “mobile” client headquarter center 16 can be easily written by persons skilled in the listed pertinent arts.
- FIG. 3 shows the general privilege hierarchy implemented by the FIG. 1 system and FIG. 2 example software architecture.
- Table I presents an example of a further detailed privilege/role definition for the FIG. 1 system and FIG. 2 example software architecture. TABLE I USER'S USER/ FIG.
- FIGS. 1 and 2 A method, and examples of its included operations, as performed on a system in accordance with the above-described example system 1 , will be described Referring to FIGS. 1 and 2 , the described operations may be performed at the field site 14 , by operations of its field database 50 and field GRT Application software block 48 .
- the references to the FIG. 1 depicted example system are not a limitation on the method or its operations. Instead, such references enable a better understanding of the method, by mapping its example operations onto a system having a described architecture. In other words, novel features and aspects of the described method are independent of the example system on which the operation is described.
- FIG. 4 is an example block diagram depiction of what is termed herein as a “mobile application”, labeled generally as 100 which, unless otherwise stated, is a mobile user, using for example the customer field site 14 of FIG. 1 , collection and uploading of disaster descriptive information. As described, the disaster descriptive information typically quantifies, describes, and/or categorizes the kinds and quantities of disasters and disaster-related damage.
- FIG. 5 is an example block diagram depiction of what is termed herein as a “web application”, labeled generally as 200 which, unless otherwise stated, is an operation performed at, or including, a management center and central database, such as the GRT network operations center 10 and GRT data center 12 .
- examples of such web applications 200 are collecting the uploaded disaster descriptive information, which are termed ASSESSMENT files in the examples described herein, updating the central database, and the distribution of all, or portions of the disaster descriptive information to other users and databases, such as the client headquarters 16 , and other customer field sites 14 .
- block 102 represents the start of a mobile application 100 .
- An example implementation of block 102 is a user switching on and/or logging into his or her customer field site 14 .
- the term “logging in” and “log on” may include interactions with, and gaining access to only the customer field site 14 , without establishing a “session”, as that term is known in the pertinent arts, with the GRT management center 10 .
- Such log on or logging in operations, including designation and entry of security passwords, are well known in the pertinent arts and, therefore, further description is not necessary.
- the process goes to block 104 to collect and generate GEODATA, which is geoposition coordinate data such as, for example, that available from GPS.
- GEODATA geoposition coordinate data
- FIG. 6 shows an example damage assessment options form 400 presented to the user at block 104 , for use m selecting and starting a site assessment.
- the user is presented with a plurality of assessment forms which, for this example are: LOCATION 402 , LOCATION/LEADERSHIP 404 , POPULATION 406 , SHELTER 408 , SANITATION/SAFE WATER 410 , HEALTH/NUTRITION 412 , INFRASTRUCTURE 414 , and ECONOMY 416 .
- the FIG. 6 list is only for purposes of example. The number of specific types of damage assessment forms is a design choice.
- the form that is visible on FIG. 6 is the SHELTER damage assessment form 408 .
- the FIG. 6 depicted example SHELTER damage assessment form 408 presents the user with a damage level assessment guide 420 showing four levels of damage, labeled 420 A, 420 B, 420 C and 420 D, respectively named as “None/Minor,” “Moderate,” “Severe” 420 C and “Destroyed,” with an illustrative example of each as a guideline.
- the FIG. 6 example form 400 assigns numerical values of “1”, “2”, “3”, and “4” to the four levels of damage, to better enable user entry of these damage assessment values into the form 408 , as will be described. It will be understood that the particular damage level assessment guide 420 shown by FIG. 6 is only an example.
- the software displaying the SHELTER damage assessment form 408 could include additional guidelines for the damage level assessment guide 420 .
- a “right click,” other user operated options selector, when a mouse cursor, or other GUI user-movable pointer, is positioned on a specific example damage type, such as 420 B “Moderate,” could display an options list allowing the user to select, for example, a longer narrative description.
- Such “right click” and other types of user-friendly means for accessing user interface options associated with an icon or GUI field are well known in the above-listed pertinent arts.
- the FIG. 6 example SHELTER damage assessment form 408 includes the following graphical user interface (GUI) data enter fields: TOTAL # RESIDENCES field 422 , ESTIMATED PERCENTAGE DAMAGED UNITS fields 424 A, 424 B, 424 C and 424 D, for damage levels “1”, “2”, “3” and “4”, respectively, PREDOMINATE BUILDING MATERIALS fields 426 A through 426 E, and corresponding BUILDING MATERIAL PERCENTAGE fields 428 A through 428 E.
- the FIG. 4 example form 400 also includes ESTIMATED NUMBER DAMAGED UNITS fields 430 A through 430 D as an alternative to the ESTIMATED PERCENTAGE DAMAGED UNITS fields 424 A, 424 B, 424 C and 424 D.
- Each of the remaining forms 402 , 404 , 406 , 410 , 412 , 414 , and 416 have a similar arrangement to the visible example SHELTER damage assessment form 408 , namely guidelines, buttons, and GUI data entry fields for guiding the user, and effectuating his or her entry of information assessing damage of the type that the form is labeled to collect.
- the forms 402 - 416 may also include pull-down lists, sub-forms, and assistance files stored in the displaying device, e.g., the field site 14 . Such pull-downs and assistance files are known in the above-listed pertinent arts.
- the user selects an assessment form, such as one of the FIG. 6 damage assessment forms 402 - 416 by, for example, clicking on the visible top tab and then proceeds to block 108 for collecting damage assessment data.
- an assessment form such as one of the FIG. 6 damage assessment forms 402 - 416 by, for example, clicking on the visible top tab and then proceeds to block 108 for collecting damage assessment data.
- the user proceeds to enter data into the form Examples are the number of residences at the site of the damage, which the user would enter into the TOTAL # RESIDENCES field 422 and, for each of the damage levels “1”, “2”, “3”, and “4”, the corresponding number of the residential, which the user would enter into fields 430 A through 430 D.
- the ASSESSMENT file includes the GEODATE generated at block 104 , and a USERID data.
- the USERID data may be prestored in the user's device, such as the field site 14 , or may be entered by the user at the start block 102 .
- the ASSESSMENT file may also include AGENCYID data, which represents the relief agency that the user is associated with.
- the GRT network operations center 10 may use the AGENCYID for routing, and for determining the distribution of the ASSESSMENT file. Similar to the USERID, the AGENCYID may be prestored in the user's device, e.g., the field site 14 , or entered by the user during the execution of block 102 .
- uploading the ASSESSMENT file would typically include the dialing protocol, and formatting the ASSESSMENT file as required by the satellite phone service provided
- the uploading may be implemented as an e-mail operation, as satellite phone-based e-mail transmission is known in the art.
- Software for the uploading operations is typically supplied, off-the-shelf, by the satellite phone service provider.
- block 110 could be executed, i.e., an ASSESSMENT file transmitted to the GRT network operations center 10 each time the user clicks the OK button 432 .
- the damage assessment options form 400 or one or more of the specific damage assessment forms such as 402 through 416 , could include a pull-down or other GUI data entry field for entry of a priority code or attribute.
- a priority code or attribute could be included whereby the user assigns, by requirement or option, a priority code or attribute to an ASSESSMENT.
- a priority or kind attribute could be used for determining the scope of dissemination of the DAMAGE ASSESSMENT.
- FIG. 4 mobile application Another variation or option for the FIG. 4 mobile application is that immediately after block 104 generates the GEODATA specifying the location of the field unit 14 , a “here I am” type of notice could be uploaded to the GRT network operations center 12 , prior to proceeding to the assessment block 106 . Such a field unit location notice could, in turn, be immediately forwarded to the client headquarters 16 of the specific relief agency associated with the sending field unit 14 . This will be addressed further in the description referencing FIG. 5 of methods and operations carried by the GRT network communications center 10 and GRT data center 12 upon receipt of an ASSESSMENT file.
- a still further variation is that immediately after the field unit 14 sends a “here I am” type of notice, the GRT network operations center 10 would immediately download information relevant to the user associated with the sending field unit 14 . As described more fully in reference to FIG. 5 , the information would be based in part on the particular user, as reflected by the USERID, and the relief agency that the user is associated with.
- the FIG. 4 method uses forms stored in the field unit 14 .
- the only communication between the field unit 14 and the GRT network operations center 10 is the uploading of the DAMAGE ASSESSMENT REPORT at block 110 .
- One benefit of this FIG. 4 implementation of uploading damage information is that it typically minimizes bandwidth and channel integrity requirement for the field unit communication network 18 .
- An alternative is to structure the communication, in whole or in pan, between the field units 14 and the GRT network operations center 10 clients in a web-type system, with less than the entire set of assessment forms actually stored in the field unit 14 .
- User entry of damage assessments, and uploading of the information from each could be performed in a web-browser mode, or in a remote dial-in session mode. Bother of these remote user access methods are known in the above-listed pertinent arts. This may be preferred for certain implementations.
- block 202 represents a start web application that may, for example, be a GRT network operations center 10 receiving a DAMAGE ASSESSMENT REPORT uploaded at block 110 of the FIG. 4 example mobile application 100 .
- the web application 200 then proceeds to block 204 , where the DAMAGE ASSESSMENT REPORT is reviewed.
- the specific operations performed by block 204 are, to a substantial extent, either a design choice or are based on requirements specific to the relief agency associated with the field unit 14 that sent the DAMAGE ASSESSMENT REPORT.
- the FIG. 6 web application 200 contemplates the review operations at block 204 being a combination of automatic review, for template-type qualification criteria such as, for example, required GUI fields being filled out, and review requiring, or allowing for, human judgment.
- the block 204 review decision branch is represented as block 206 . As shown, if the DAMAGE ASSESSMENT REPORT fails the criteria applied at block 204 the process goes to block 208 and ends.
- the process goes to block 210 , which decides whether the data included in the DAMAGE ASSESSMENT REPORT is shared with agencies other than the agency associated with the field unit 14 that sent the report.
- the sharing decision or rules are not necessarily global with respect to the entire DAMAGE ASSESSMENT REPORT and, instead, sharing may be different with different parts of the report data.
- the sharing rules are set by the relief agencies and may, for example, be updated by a web session invoked at an agency's respective client headquarter center 16 . It is further contemplated that final implementation of a change to the inter-agency sharing rules may require transmission of the proposed change from the GRT network operations center 10 to the proposed receiving agency and receipt of authorization from that agency.
- block 210 determines the information from the DAMAGE ASSESSMENT REPORT to be not sharable, the process goes to block 212 . Blocks 222 - 226 will be discussed further below. If block 210 determines that the information from the DAMAGE ASSESSMENT REPORT is sharable the process goes to block 214 to incorporate data, or certain fields or portions of the data into the various GIS databases, or user-apparent GIS databases, stored by the GRT date center 12 . Referring to FIG. 2 the specific arrangement by which the Backend Relational Database Management System 46 maintains, or can provide, a different GIS database, or apparent GIS database, for each of relief agency, e.g., each different client headquarters 16 , is a design choice.
- the term “apparent GIS database” is used because the Backend Relational Database Management System 46 may be configured to maintain a plurality of records, each record having fields of, for example, location, date, damage type(s), damage quantity(ies), reporting agency(ies), authorized sharing agencies, a data quality indicator, and other situational facts such as, for example, ongoing armed conflict.
- an updated map such as the below-described SITUATIONAL MAP (G, A), where G is an index for geographical area and A is an index for the agency receiving the map
- the Backend blocks 42 , 44 and 46 may retrieve data for overlays representing all facts from the database that are within or associated with the G geographical area and are (a) authorized for the A agency to see and (b) preselected by the A agency for seeing.
- block 214 incorporates the DAMAGE ASSESSMENT REPORT into the GRT database center 12 , under control of the Backend Relational Database Management System 46 and then proceeds to block 216 to generate a new SITUATIONAL MAP (G, A), and to block 218 to transmit an UPDATE REPORT (G, A), using the same G and A indices to represent the geographical area(s) and agency(ies), respectively, to which the UPDATE REPORT will be sent.
- the process by which the field sites 14 receive an UPDATE REPORT is largely a design choice. For example, referring to FIG. 4 , each time a user logs in at block 102 and the site 14 transmits a “here I am” notice, the site 14 may receive all UPDATE REPORTS that the user is authorized to receive. Depending on the implementation, the user may be given a choice to see UPDATE REPORTS that have no information with the respect to the location of field site 14 .
- a variation for the report block 218 of FIG. 5 is that the user would have to send a “check for updates” request, instead of automatically receiving the update.
- Still another variation is to send a “check for updates notice” to the persons listed as authorized users of agency's' field sites 14 by, for example, wireless e-mail.
- Block 218 also sends UPDATE REPORTS to the relief agency(ies) at, for example, their respective client headquarter sites 16 . This may be done by, for example, e-mail, with the e-mail having the UPDATE REPORT attached, or by an e-mail notice for the agency(ies) to log into their respective GIS databases and check for updates using, for example, the FIG. 2 viewer/web browser block 52 . The process then goes to block 220 and ends.
- blocks 212 followed by 222 through 226 are executed much the same as blocks 214 through 220 , the only difference being that only one relief agency and one relief agency's field sites 14 receive the UPDATE REPORT.
- FIG. 7 is an example display, either on the video display of the customer headquarters 16 or the video display of the field sites 14 , as would be seen after receiving an UPDATE REPORT.
- the FIG. 7 example uses call-outs that describe, with words, situations at a plurality of geographical locations.
- FIG. 8 is an example of symbols for use in overlay maps displayed on the video display of the customer headquarters 16 or the video display of the field sites 14 , either separate from in conjunction with call-outs as shown by FIG. 7 .
Landscapes
- Business, Economics & Management (AREA)
- Physics & Mathematics (AREA)
- General Business, Economics & Management (AREA)
- General Physics & Mathematics (AREA)
- Engineering & Computer Science (AREA)
- Theoretical Computer Science (AREA)
- Management, Administration, Business Operations System, And Electronic Commerce (AREA)
Abstract
A system and method includes providing a database having a plurality of damage characterization data and a geographical location associated with each. A first and a second portable communication unit are associated, respectively, with a first subscribing party and a second subscribing party. A sharing privilege list identifies, for the first subscribing party, parties authorized to receive damage assessment data. A damage assessment report is transmitted from the first of the portable communication units to the database. The database is updated based on the damage assessment report. Then, depending on whether or not the second subscribing party is on the sharing privilege list, a data is communicated to the second of the portable communication units reflecting, or based on, the damage assessment report.
Description
- This application is a continuation of prior U.S. patent application Ser. No. 10/768,114, filed Feb. 2, 2004. The entirety of this aforementioned application is incorporated herein by reference.
- The present invention is directed to a system for managing field level evaluation and relief efforts and, more particularly, to a system for inputting, characterizing, managing and distributing information for the provision of humanitarian relief over large and remote geographical areas.
- A primary objective of organizations, agencies and other entities providing humanitarian relief (collectively referenced as “relief agencies”) is to provide immediate, necessary relief to victims of humanitarian crises arising from, for example, natural disasters such as floods, earthquakes, hurricanes and man-made disasters such as war. The destruction in such situations can involve dwellings, agricultural systems, health-care systems, sanitation, transportation, water and power systems. The crises further include the human risks facing displaced populations occupying regions themselves having inadequate supporting infrastructure. Frequently, because of the scale of the destruction, and the stricken area's requirement for immediate receipt of a range of necessities, several relief agencies respond. The several agencies may provide concurrent relief assistance, and/or different agencies may provide different assistance at respective stages of the overall relief effort. The agencies must have, and be able to distribute, accurate, real-time information describing the situation.
- In a typical present relief effort, such as that provided to a populated area after experiencing a high-magnitude earthquake, a plurality of relief agencies responds. The agencies may be international organizations (IG), government organizations, (GO), and non-government organizations (NGOs). Each agency typically begins its relief effort by sending in a number of its field personnel. The initial mission of the field personnel is to obtain damage assessment reports for their respective agency. The field personnel typically generate the damage assessment reports by traveling to a damage site and writing down unformatted personal observations on the site's geography, a general summary of the population and developmental condition of the area prior to the disaster, if that information is available, and an inventory or estimate of the damage. For example, the field person might write in a notebook that a village named X had an estimated pre-damage population of two thousand, the population occupying approximately five hundred mud-brick homes, and that they had a local power generating station, and a local water supply. The field person would then write an estimate/inventory of the damage. The write-up information would include, in an unformatted manner, that approximately 100 mud-brick homes were still standing, about 200 were damaged but had the majority of their outer walls reasonably intact, and that the remainder were destroyed. It would further an estimate of injuries, by number and type of injuries, and the deaths, including the locations and retrievability of the bodies. Other information would be, for example, the field person's observation on the local water supply, including the reservoir, or the wells, and the filtering facilities and distribution system, and assessments of the electrical power system, and other systems of the local economy.
- After writing the information, the field person would typically type a report and e-mail or fax it to the agency. The agency would then, based on the information, estimate the relief it could provide.
- An example embodiment of the present system and method includes providing a database having a plurality of damage characterization data and a geographical location associated with each. A plurality of portable communication units are provided, each having a display, a manual data entry mechanism, and a geolocation detector for generating a geolocation data based on an externally generated geolocation signal. A first of the portable communication units is associated with a first subscribing party and a second of the portable communication units is associated with a second subscribing party. A sharing privilege list identifies, for the first subscribing party, at least one other subscribing party authorized to receive damage assessment data from the first subscriber. A geolocation data is generated at the first of the portable communication units based on its geolocation. A damage assessment data is input, by the user, into the first of the portable communication units. When entry of the damage assessment data is completed a damage assessment report is transmitted from the first of the portable communication units to the database, the damage assessment report including data reflecting a damage assessment data, an identification data identifying the sender of the damage assessment report, and the geolocation data. In response, the database is updated based on the damage assessment report. Then, depending on whether or not the second subscribing party is on the sharing privilege list, a data is communicated to the second of the portable communication units reflecting, or based on, the damage assessment report.
- In a further embodiment, a plurality of subscribing party headquarter communication units is provided. A first of the subscribing party headquarter communication units is associated with the first subscribing party and a second of the subscribing party headquarter communication units with the second subscribing party. Depending on whether or not the second subscribing party is on the sharing privilege list, at least one data reflecting the damage assessment report is communicated to the second of the subscribing party headquarter communication units.
- These and other objects, features and advantages of the present system will become more apparent to, and better understood by, those skilled in the relevant art from the following more detailed description of the preferred embodiments, taken with reference to the accompanying drawings, in which like features are identified by like reference numerals.
-
FIG. 1 is an example high level block diagram of an example embodiment of the described system; -
FIG. 2 is an example high level system-level software architecture supporting theFIG. 1 system; -
FIG. 3 is an illustrative diagram showing an example functional hierarchy of users of, and nodes within a described system such as that of theFIG. 1 example; -
FIG. 4 is an example functional flow chart for a mobile application such as, for example, a damage assessment report uploading; -
FIG. 5 is an example functional flow chart for web application such as, for example, receiving a damage assessment report from a field unit and, in response, conditionally updating the databases and distributing the information; -
FIG. 6 is an example damage assessment form with user selectable options, displayed on a field unit, for the user to input and upload damage assessment data; -
FIG. 7 is an example situational map all, or part of which, is displayed on the user's field unit; and -
FIG. 8 is an example set of symbols for a real-time situational map. - Overview
- For purposes of this description, the term “relief agency” encompasses all of the phrase's ordinary and customary meanings including, but not limited to, government, non-government, and international organizations and other entities that assess damage wrought by natural forces, such as hurricanes, typhoons, earthquakes, and the damages wrought by man-made forces such as war and insurrection.
- The described system is an end-to-end service through which field personnel inspect and collect information from disaster areas, the information is organized as a selectable privilege-based user-accessible database, and the information is distributed among, through default and user-selectable formats, and between disaster relief agencies, and other users through privilege-based access.
- An example of the described system includes a central information distribution and management center, one or more agency headquarter centers, and a plurality of field units, which are portable communication devices carried by or mounted to the vehicles of field personnel.
- A typical system further includes a wide-area communication network such as, for example, the Internet, and other described networks for communication among and between the field units, the central information management center, and the one or more relief agency headquarter centers.
- In the described embodiments, the field units operate within, and have circuitry for utilizing, a geo-positioning system such as, for example, the Global Positioning System (GPS). Utilization of geo-positioning system is preferred because, as will be described, the field unit's geo-location is included in the evaluation reports that the units deliver via uplink to the central information management center.
- The field units display graphical user interface (GUI) forms to the user for entry of damage assessment information and for uploading the information as a damage assessment report. The forms are typically stored in the field units, and are typically customized for the particular relief agency associated with the field person possessing the field unit. Updating of the forms by downlink from the central information management center is contemplated. The damage assessment reports include the geolocation of the sending field unit and a data, or other information, identifying the relief agency associated with the sender. The central information management center has distribution privilege data that typically maintains, for each relief agency, a list of other agencies, if any, to which the sending agency's damage assessment report information may be distributed. The distribution privilege data may specify the distribution more particularly, such as certain types of information being distributed to certain other agencies.
- The field units also display real-time maps to the user, a typical map utilizing geographical map data stored in the field unit on which updated situation information, received by downlink from the central information management center, is overlaid and displayed.
- The following description includes numerous example details and specifics, some of which pertain only to the specific examples presented, and which are included only to assist in describing these specific examples, and thus assist the reader in understanding the features and elements of the described system. It will be evident to ones skilled in the art that the described systems and methods can be practiced without, and with different ones of, these details and specifics.
- This description assumes the reader to have ordinary skill in the relevant arts of wide-area networks (WAN) such as, for example, the Internet, virtual private networks (VPN) employing public channels, local area networks (LAN), commercially available database software and hardware systems, and the interface protocols for users to access same, available satellite telephone systems, cellular telephone systems, and personal computers and hand-held computing devices. Details for implementing the described systems and methods, to the extent such details are knowledge possessed by persons of skill in the above-listed arts, by which such persons after reading this description can select from among, configure and assemble commercial components into the described systems, are omitted.
-
FIG. 1 shows a high-level functional block diagram of an example embodiment of the system.FIG. 2 is an example system-level software architectural chart for the software supporting, and implemented on, theFIG. 1 system. It will be understood thatFIG. 1 is a graphic representation of an example and is arranged according to functional blocks. The depicted block segmentation and arrangement is selected to assist in the understanding of functions and operational features of the described system. The depicted blocks do not necessarily represent, or limit, the physical hardware blocks, or subsystems, for implementing a system in accordance with this description. For example, as will be further understood from this detailed description, various functional blocks of theFIG. 1 example diagram may be implemented on a distributed arrangement of, for example, mass storage units and servers. Likewise, a single interconnected system of mass storage units, servers and user interface devices may perform the functions represented by a plurality ofFIG. 1 functional blocks. Still further, the particularFIG. 1 segmentation of functional blocks, and the labeling of the blocks, is for purposes of example only, and is not a limitation on the scope of the particular architectures, communication and database structures that may be used for implementing the described system. - Referring to
FIG. 1 , the depicted example system includes anetwork operations center 10, which is referenced hereinafter as the GRTnetwork operations center 10, its associatedGRT data center 12, a plurality ofcustomer field sites 14, and one or more customer headquarter centers 16. A fieldunit communication network 18 provides for uploading communications from the plurality ofcustomer field sites 14 to theGRT data center 12 and for downloading communications from the GRT data center to the plurality ofcustomer field sites 14. The uploading function of thewireless communication network 18 is represented, along with an example list of specific uploading communications, asblock 20. Likewise, the downloading function, with an example list of download operations, is represented asblock 22. AWAN 24 provides for communications between the one or more customer headquarter centers 16 and theGRT data center 12. The uploading function of thewide area network 24 is represented, together with an example list of specific uploading communications, as block 26. Similarly, the downloading function of the wide area network with an example list of download operations, is represented as block 28. - With continuing reference to
FIG. 1 , an examplecustomer field site 14 is a portable computing device, preferably ruggedized, such as, for example, a Panasonic Toughbook™, a Howard Portall Workbook™, or any of the equivalents available from various commercial vendors. Thecustomer field site 14 includes a wireless communication feature, of a type dependent on the implementation of the fieldunit communication network 18 in which theunit 14 is operating. Examples off-the-shelf wireless communication devices are an INMARSAT GAN and an INMARSAT Mini-M, which are readily attached to commercially available portable computing devices, such as the Panasonic Toughbook™ and other off-the-shelf examples of thefield site 14 identified herein. Thecustomer field site 14 further includes a GPS receiver, or an interface to an external GPS receiver. An example GPS receiver, which connects to the Panasonic Toughbook™ and to equivalent laptop computers, is the Trip-Nav™ model TN 200 GPS receiver with Universal Serial Bus (USB) connectivity. - Another example implementation of a
field unit 14 is a hand-held computing device such as, for example, a Dell™ Axim™ X5 or X3i, preferably ruggedized with a commercially available environment casing, or “skin”, or an equivalent hand-held such as the Symbol Technologies™ model SPT-1800™ or model PPT-2800™, the hand-held computing device, having a GPS receiver such as, for example, a LinksPoint™ GlobalPoint™ GPS, or a Pharos™ model PFD22™ GPS receiver, and having, for example, an INMARSAT Mini-M Satellite Phone. These particular make/model of ruggedized laptops and ruggedized handheld computing devices, and their respective GPS receivers, are only for purposes of example. Persons of skill in the relevant arts can, upon reading the present description, readily identify equivalent kinds and models of off-the-shelf devices available from various commercial vendors. - Referring again to
FIG. 1 , an example implementation of the GRTnetwork operations center 10 and its associatedGRT data center 12 is thedate center 12 including one or more commerciallyavailable application servers 30, aGRT database 32, aweb server 34, and anoptional firewall 36, and the GRTnetwork operations center 10 including a plurality ofuser terminals 38. It should be understood that the GRTnetwork operations center 10, theGRT data center 12 and the customer headquarter centers 16, are functional blocks, and each is not necessarily a single brick-and-mortar facility. Further, the GRTnetwork operations center 10 and theGRT data center 12 are functional blocks, and are not necessarily implemented on hardware systems separate from one another. Accordingly, theterminals 38 may be co-located with one another and with the computer hardware of theGRT data center 12, or may be distributed over a wide geographic area. - The described components of the GRT
network operations center 10 and theGRT database 12, to the extent they are implemented on, or reside in separate hardware units are connected to one another using, for example, a LAN. The LAN connection, though, is only an example because, as stated above, one or more of the functions of the GRTnetwork operations center 10 and theGRT database 12 can be implemented on distributed hardware systems. For example, theGRT database 32 may be a distributed cluster of server-controlled mass storage devices, interconnected by, for example a virtual private network (VPN) carried over the Internet. Construction, operation and maintenance of distributed cluster databases is known to persons of ordinary skill in the arts pertaining to this described system. - An example implementation of the
FIG. 1 application server 30 of theGRT network center 10 is a Dell PowerEdge™ server or a Sun SunFire™ server, running under a standard commercially available operating system. An example implementation of thedatabase 32 is a Dell PowerVault™ Storage Unit. The identified examples of makes and models of theserver 30 and thedatabase 32 are only for purposes of illustration. Many alternative commercially available implementations can be chosen from, and the selection from these is a design choice based on conventional selection criteria known to persons of ordinary skill in the computer arts. Examples of such selection criteria, which are known, include, for example, the number of users, size of the database, desired access time, and desired security. - With continuing reference to
FIG. 1 , theGRT terminals 38 may be, for example, conventional personal computers or may be what is termed in the pertinent arts as an “ultra-thin client” having only a data input/output device and a visual display device. - With continuing reference to
FIG. 1 , various implementations of the fieldunit communication network 18 are contemplated. A typical preferred embodiment is a satellite phone system such as, for example, INMARSAT, because satellite phones provide excellent coverage, to even the most remote areas, and do not require a local communications infrastructure. Another contemplated embodiment is a cellular-type network, at least for the portion of thecommunication network 18 to which thefield unit 14 interfaces. With respect to bandwidth requirements, it will be understood from the further detailed description of the present methods and their example operations that the bandwidth requirements of the fieldunit communication network 18, at least for the preferred embodiments, are not particularly high. Reasons for the typical bandwidth requirements being not high include the anticipated size of the disaster evaluation files, termed ASSESSMENT files and the transmitted DAMAGE ASSESSMENT REPORTS containing same, that will be uploaded by thefield units 14, and the anticipated refresh or new report rate, and data quantity per refresh or new report, of the geographical information, termed AREA SITUATION GIS reports, that will be communicated from the GRTnetwork operations center 10 to thefield units 14. - With continuing reference to
FIG. 1 ,WAN 24, connecting the GRTnetwork operations center 10 and its associatedGRT data center 12 to the one or more customer headquarter centers 16 may be implemented on the Internet, or on a combination of the Internet and point-to-point T1 lines, the T1 lines being leased from commercial communications entities as known in the art. -
FIG. 2 shows an example system level chart for the software supporting and implemented on theFIG. 1 example system. Dotted line boxes onFIG. 2 that have number labels corresponding to the number labels of functional blocks ofFIG. 1 are the software blocks corresponding to that functional block Referring toFIG. 2 , the block labeled “Backend,” withreference numbers network management center 10 and theGRT database 12. - With continuing reference to
FIG. 2 , within the Backend block is theweb server block 40, which is the software associated with theFIG. 1 web server 34. Theweb server block 40 processes DAMAGE ASSESSMENT REPORTS and other data uploads and requests from thefield units 14, as well as access and other requests from the client headquarter centers 16. Example commercial software for implementing theseweb server 40 functions includes the Java Virtual Machine Servlet engine. The other software blocks in the Backend are theGIS Application block 42, theGRT Application block 44 and RelationalDatabase Management System 46. TheGIS Application block 42 creates, distributes and administers, under the control of theGRT Application block 44, GIS services described herein, and the associated integration of data from thefield units 14, theGRT database 32, and outside databases. Example commercial software for implementing theGIS Application block 42 includes ArcMS˜ and ArcSDE™ from ArcSoft™ Corporation, and equivalent software products from other suppliers such as, for example, ESRI Corp. and Autodesk Corp. The Relational DatabaseManagement System block 46 performs the data storage and management functions described herein, and example implementations include the Microsoft SQL Server product. TheGRT Application block 44 preferably resides on theFIG. 1 application server 30, and performs the described GRT GIS map and associated data services, including updating the GRT GIS maps in response to DAMAGE ASSESSMENT REPORTS, maintaining different GRT GIS maps for different relief agencies, overseeing the transmission of described reports and alerts to thefield units 14, and to relief agencies, and others, associated with the customer headquarter centers 16. Upon reading the present disclosure, persons of ordinary skill in the pertinent arts listed above can readily write the GRT Application block software, using commercially available software languages and development tools. - With continuing reference to
FIG. 2 , the dotted-line block labeled “Clientside(Field),” having thereference number 14, is a generic representation of the software resident on thefield units 14. TheFIG. 2 Clientside(Field) block includes the FieldGRT Application block 48 and theField Database block 50. The FieldGRT Application block 48 is typically a subset, at least in part, of theGRT Application block 44 of the Backend block The functions of the FieldGRT Application block 48, which are more fully described in reference toFIGS. 4-6 , include login operations, overlaying GIS data with stored local maps, and the upload and download operations for connecting to, and receiving situational data and alerts from thenetwork operations center 10 and otherFIG. 1 blocks corresponding to the FIG. Backend block containing software blocks 40, 42, 44, and 46: The functions of the Field Database block include storing local geographical maps and damage assessment forms. - Referring again to
FIG. 2 , the dotted line block labeled “Clientside(HQ)” with thereference numeral 16, includes the Viewersoftware application block 52 and the Client HeadquarterGRT Application block 54. The function of theViewer block 52 is for the client, such as home office personnel of a relief agency, to be able to view the situational maps downloaded to the agency'sfield units 14, and the DAMAGE ASSESSMENT REPORTS received from itsfield units 14. Theblock 54 is shown as a dotted line because typical embodiments contemplate no significant application software required at the client headquarter centers 16. Instead, the preferred embodiment contemplates the Client HeadquarterGRT Application block 54 as an application within theGRT Application block 44 of theFIG. 2 Backend. Accordingly, theViewer application block 52 can be implemented as, for example, a Microsoft Explorer or equivalent web browser. It can therefore be seen that the client headquarter centers 16 are not limited to brick and mortar facilities. On the contrary, a relief agency can provide certain of its personnel with, for example, laptop computers, and agency proprietary administrative privilege codes allowing the person to connect, from any location having Internet access, and from that location be aclient headquarter center 16. Software features for the Backend WebServer application block 40, and theGRT Application block 44 implementing such a “mobile”client headquarter center 16 can be easily written by persons skilled in the listed pertinent arts. -
FIG. 3 shows the general privilege hierarchy implemented by theFIG. 1 system andFIG. 2 example software architecture. Table I below presents an example of a further detailed privilege/role definition for theFIG. 1 system andFIG. 2 example software architecture.TABLE I USER'S USER/ FIG. 1 BLOCKPRIVILEGES ASSIGNED ROLE GRT - Network Add, Edit, Delete, GRT Administrator Operations Center 10 Approve (upon client recommendation), View All Client HQ and Field Data GRT - Network Sets and administers GRT Systems Operations Center 10 privileges for all clients 16Administrator GRT - Network Views all Client HQ 16 andGRT Service Operations Center 10 Field Unit 14 DataAnalyst CLIENT HQ - Client Add, Edit, Delete, Client HQ HQ 16 Approve and View Own Administrator Client HQ 16 Data and View Own Field Unit 14Data. CLIENT HQ - Client View Own Client HQ 16Client HQ Analyst HQ 16 Data and View Own Field Unit 14 Data. FIELD HQ - Client Add, Edit, Delete, Field Administrator HQ 16 Approve and View Own Client Field HQ 16 Dataand View Own Field Unit 14 Data. FIELD HQ - Client View Own Client Field Field Analyst HQ 16 HQ 16 Data and ViewOwn Field Unit 14 Data.FIELD WORKER - Add, Edit, Delete, Upload Field Worker Field Unit 14 Own reports, View own HQ 16 data view own fielddata Others, including View authorized data open Public or other public to public or specific other - A method, and examples of its included operations, as performed on a system in accordance with the above-described
example system 1, will be described Referring toFIGS. 1 and 2 , the described operations may be performed at thefield site 14, by operations of itsfield database 50 and field GRTApplication software block 48. The references to theFIG. 1 depicted example system are not a limitation on the method or its operations. Instead, such references enable a better understanding of the method, by mapping its example operations onto a system having a described architecture. In other words, novel features and aspects of the described method are independent of the example system on which the operation is described. -
FIG. 4 is an example block diagram depiction of what is termed herein as a “mobile application”, labeled generally as 100 which, unless otherwise stated, is a mobile user, using for example thecustomer field site 14 ofFIG. 1 , collection and uploading of disaster descriptive information. As described, the disaster descriptive information typically quantifies, describes, and/or categorizes the kinds and quantities of disasters and disaster-related damage.FIG. 5 is an example block diagram depiction of what is termed herein as a “web application”, labeled generally as 200 which, unless otherwise stated, is an operation performed at, or including, a management center and central database, such as the GRTnetwork operations center 10 andGRT data center 12. As will be described, examples ofsuch web applications 200 are collecting the uploaded disaster descriptive information, which are termed ASSESSMENT files in the examples described herein, updating the central database, and the distribution of all, or portions of the disaster descriptive information to other users and databases, such as theclient headquarters 16, and othercustomer field sites 14. - Referring to
FIG. 4 , block 102 represents the start of amobile application 100. An example implementation ofblock 102 is a user switching on and/or logging into his or hercustomer field site 14. Forblock 102 the term “logging in” and “log on” may include interactions with, and gaining access to only thecustomer field site 14, without establishing a “session”, as that term is known in the pertinent arts, with theGRT management center 10. Such log on or logging in operations, including designation and entry of security passwords, are well known in the pertinent arts and, therefore, further description is not necessary. Upon completion of theblock 102 start operation, the process goes to block 104 to collect and generate GEODATA, which is geoposition coordinate data such as, for example, that available from GPS. - After, or concurrent with collecting geoposition coordinate data at
block 104, the process goes to block 106 for selection of one or more types of damage assessment and to start entering observed damage and situational information.FIG. 6 shows an example damage assessment options form 400 presented to the user atblock 104, for use m selecting and starting a site assessment. Referring toFIG. 6 , the user is presented with a plurality of assessment forms which, for this example are:LOCATION 402, LOCATION/LEADERSHIP 404,POPULATION 406,SHELTER 408, SANITATION/SAFE WATER 410, HEALTH/NUTRITION 412,INFRASTRUCTURE 414, andECONOMY 416. TheFIG. 6 list is only for purposes of example. The number of specific types of damage assessment forms is a design choice. The form that is visible onFIG. 6 is the SHELTERdamage assessment form 408. - The
FIG. 6 depicted example SHELTERdamage assessment form 408 presents the user with a damagelevel assessment guide 420 showing four levels of damage, labeled 420A, 420B, 420C and 420D, respectively named as “None/Minor,” “Moderate,” “Severe” 420C and “Destroyed,” with an illustrative example of each as a guideline. TheFIG. 6 example form 400 assigns numerical values of “1”, “2”, “3”, and “4” to the four levels of damage, to better enable user entry of these damage assessment values into theform 408, as will be described. It will be understood that the particular damagelevel assessment guide 420 shown byFIG. 6 is only an example. Other names, numerical values and illustrative examples of damage could be used. Further, it is contemplated that the software displaying the SHELTERdamage assessment form 408 could include additional guidelines for the damagelevel assessment guide 420. For example, a “right click,” other user operated options selector, when a mouse cursor, or other GUI user-movable pointer, is positioned on a specific example damage type, such as 420B “Moderate,” could display an options list allowing the user to select, for example, a longer narrative description. Such “right click” and other types of user-friendly means for accessing user interface options associated with an icon or GUI field are well known in the above-listed pertinent arts. - The
FIG. 6 example SHELTERdamage assessment form 408 includes the following graphical user interface (GUI) data enter fields: TOTAL # RESIDENCES field 422, ESTIMATED PERCENTAGE DAMAGED UNITS fields 424A, 424B, 424C and 424D, for damage levels “1”, “2”, “3” and “4”, respectively, PREDOMINATEBUILDING MATERIALS fields 426A through 426E, and corresponding BUILDINGMATERIAL PERCENTAGE fields 428A through 428E. TheFIG. 4 example form 400 also includes ESTIMATED NUMBER DAMAGEDUNITS fields 430A through 430D as an alternative to the ESTIMATED PERCENTAGE DAMAGED UNITS fields 424A, 424B, 424C and 424D. - Each of the remaining
forms damage assessment form 408, namely guidelines, buttons, and GUI data entry fields for guiding the user, and effectuating his or her entry of information assessing damage of the type that the form is labeled to collect. The forms 402-416 may also include pull-down lists, sub-forms, and assistance files stored in the displaying device, e.g., thefield site 14. Such pull-downs and assistance files are known in the above-listed pertinent arts. - Referring to
FIG. 4 , atblock 106 the user selects an assessment form, such as one of theFIG. 6 damage assessment forms 402-416 by, for example, clicking on the visible top tab and then proceeds to block 108 for collecting damage assessment data. Using theFIG. 6 visible SHELTERdamage assessment form 408 as an example, the user proceeds to enter data into the form Examples are the number of residences at the site of the damage, which the user would enter into the TOTAL # RESIDENCES field 422 and, for each of the damage levels “1”, “2”, “3”, and “4”, the corresponding number of the residential, which the user would enter intofields 430A through 430D. - When the user has completed entry of the data for the
form 408 he or she reviews the entries. If they are satisfactory, the user clicks on the “OK”button 432, which closes the “window,” as the visual display of a form such as 408 is known in the pertinent arts, and stores the entered values. If the entries are not satisfactory, the user either edits the entries or clicks on the CANCELbutton 434. The user then either clicks on one of the remainingforms block 108, or clicks on the SEND tab 430 to transmit or upload the ASSESSMENT file. If the user clicks on the SEND tab 430 the process goes to block 110, where it saves the ASSESSMENT file and transmits a DAMAGE ASSESSMENT report, having the ASSESSMENT file, to the management center. For this example, the management center is the GRTnetwork operations center 10. The ASSESSMENT file includes the GEODATE generated atblock 104, and a USERID data. The USERID data may be prestored in the user's device, such as thefield site 14, or may be entered by the user at thestart block 102. Depending on the specific implementation, the ASSESSMENT file may also include AGENCYID data, which represents the relief agency that the user is associated with. As will be understood from the further detailed description, in reference toFIG. 5 , of an example web application, the GRTnetwork operations center 10 may use the AGENCYID for routing, and for determining the distribution of the ASSESSMENT file. Similar to the USERID, the AGENCYID may be prestored in the user's device, e.g., thefield site 14, or entered by the user during the execution ofblock 102. - The particular operations for carrying out the transmitting, or uploading, of the ASSESSMENT file depend on the particular implementation of the system. For example, referring to
FIG. 1 , if the fieldunit communication network 18 is a satellite phone system, such as INMARSAT, uploading the ASSESSMENT file would typically include the dialing protocol, and formatting the ASSESSMENT file as required by the satellite phone service provided The uploading may be implemented as an e-mail operation, as satellite phone-based e-mail transmission is known in the art. Software for the uploading operations is typically supplied, off-the-shelf, by the satellite phone service provider. - Referring to
FIG. 4 , the depicted blocks are only for purposes of example. Many variations and other design choices can be implemented by persons skilled in the above-listed pertinent arts upon reading this disclosure. Forexample block 110 could be executed, i.e., an ASSESSMENT file transmitted to the GRTnetwork operations center 10 each time the user clicks theOK button 432. Another variation or option is that the damage assessment options form 400, or one or more of the specific damage assessment forms such as 402 through 416, could include a pull-down or other GUI data entry field for entry of a priority code or attribute. In other words, a priority code or attribute could be included whereby the user assigns, by requirement or option, a priority code or attribute to an ASSESSMENT. As will be understood in view of the description in reference toFIG. 5 , such a priority or kind attribute could be used for determining the scope of dissemination of the DAMAGE ASSESSMENT. - Another variation or option for the
FIG. 4 mobile application is that immediately afterblock 104 generates the GEODATA specifying the location of thefield unit 14, a “here I am” type of notice could be uploaded to the GRTnetwork operations center 12, prior to proceeding to theassessment block 106. Such a field unit location notice could, in turn, be immediately forwarded to theclient headquarters 16 of the specific relief agency associated with the sendingfield unit 14. This will be addressed further in the description referencingFIG. 5 of methods and operations carried by the GRTnetwork communications center 10 andGRT data center 12 upon receipt of an ASSESSMENT file. - A still further variation, is that immediately after the
field unit 14 sends a “here I am” type of notice, the GRTnetwork operations center 10 would immediately download information relevant to the user associated with the sendingfield unit 14. As described more fully in reference toFIG. 5 , the information would be based in part on the particular user, as reflected by the USERID, and the relief agency that the user is associated with. - The
FIG. 4 method, as described, uses forms stored in thefield unit 14. As depicted byFIG. 4 , the only communication between thefield unit 14 and the GRTnetwork operations center 10 is the uploading of the DAMAGE ASSESSMENT REPORT atblock 110. One benefit of thisFIG. 4 implementation of uploading damage information is that it typically minimizes bandwidth and channel integrity requirement for the fieldunit communication network 18. An alternative is to structure the communication, in whole or in pan, between thefield units 14 and the GRTnetwork operations center 10 clients in a web-type system, with less than the entire set of assessment forms actually stored in thefield unit 14. User entry of damage assessments, and uploading of the information from each, could be performed in a web-browser mode, or in a remote dial-in session mode. Bother of these remote user access methods are known in the above-listed pertinent arts. This may be preferred for certain implementations. - Referring to
FIG. 6 , an example operation of a block flow for aweb application 200 utilizing, for this example, a system in accordance withFIG. 1 will be described. Referring toFIGS. 1 and 2 , the described operations maybe performed at the GRTnetwork operations center 10 and theGRT data center 12, by operations of theWeb Server application 40, theGIS Application 42, theGRT Application 44 and the RelationalDatabase Management System 46. Referring toFIG. 6 , block 202 represents a start web application that may, for example, be a GRTnetwork operations center 10 receiving a DAMAGE ASSESSMENT REPORT uploaded atblock 110 of theFIG. 4 examplemobile application 100. Theweb application 200 then proceeds to block 204, where the DAMAGE ASSESSMENT REPORT is reviewed. The specific operations performed byblock 204 are, to a substantial extent, either a design choice or are based on requirements specific to the relief agency associated with thefield unit 14 that sent the DAMAGE ASSESSMENT REPORT. TheFIG. 6 web application 200 contemplates the review operations atblock 204 being a combination of automatic review, for template-type qualification criteria such as, for example, required GUI fields being filled out, and review requiring, or allowing for, human judgment. Theblock 204 review decision branch is represented asblock 206. As shown, if the DAMAGE ASSESSMENT REPORT fails the criteria applied atblock 204 the process goes to block 208 and ends. - If the DAMAGE ASSESSMENT REPORT meets the criteria applied at
block 204, and there is no manual override, the process goes to block 210, which decides whether the data included in the DAMAGE ASSESSMENT REPORT is shared with agencies other than the agency associated with thefield unit 14 that sent the report. The sharing decision or rules are not necessarily global with respect to the entire DAMAGE ASSESSMENT REPORT and, instead, sharing may be different with different parts of the report data. The sharing rules are set by the relief agencies and may, for example, be updated by a web session invoked at an agency's respectiveclient headquarter center 16. It is further contemplated that final implementation of a change to the inter-agency sharing rules may require transmission of the proposed change from the GRTnetwork operations center 10 to the proposed receiving agency and receipt of authorization from that agency. - If
block 210 determines the information from the DAMAGE ASSESSMENT REPORT to be not sharable, the process goes to block 212. Blocks 222-226 will be discussed further below. Ifblock 210 determines that the information from the DAMAGE ASSESSMENT REPORT is sharable the process goes to block 214 to incorporate data, or certain fields or portions of the data into the various GIS databases, or user-apparent GIS databases, stored by theGRT date center 12. Referring toFIG. 2 the specific arrangement by which the Backend RelationalDatabase Management System 46 maintains, or can provide, a different GIS database, or apparent GIS database, for each of relief agency, e.g., eachdifferent client headquarters 16, is a design choice. The term “apparent GIS database” is used because the Backend RelationalDatabase Management System 46 may be configured to maintain a plurality of records, each record having fields of, for example, location, date, damage type(s), damage quantity(ies), reporting agency(ies), authorized sharing agencies, a data quality indicator, and other situational facts such as, for example, ongoing armed conflict. To generate an updated map, such as the below-described SITUATIONAL MAP (G, A), where G is an index for geographical area and A is an index for the agency receiving the map, the Backend blocks 42, 44 and 46 may retrieve data for overlays representing all facts from the database that are within or associated with the G geographical area and are (a) authorized for the A agency to see and (b) preselected by the A agency for seeing. It will be understood that the “G” and “A” indices are only for purposes of describing a function ofblocks - Referring again to
FIG. 5 , block 214 incorporates the DAMAGE ASSESSMENT REPORT into theGRT database center 12, under control of the Backend RelationalDatabase Management System 46 and then proceeds to block 216 to generate a new SITUATIONAL MAP (G, A), and to block 218 to transmit an UPDATE REPORT (G, A), using the same G and A indices to represent the geographical area(s) and agency(ies), respectively, to which the UPDATE REPORT will be sent. - The process by which the
field sites 14 receive an UPDATE REPORT is largely a design choice. For example, referring toFIG. 4 , each time a user logs in atblock 102 and thesite 14 transmits a “here I am” notice, thesite 14 may receive all UPDATE REPORTS that the user is authorized to receive. Depending on the implementation, the user may be given a choice to see UPDATE REPORTS that have no information with the respect to the location offield site 14. A variation for the report block 218 ofFIG. 5 is that the user would have to send a “check for updates” request, instead of automatically receiving the update. Still another variation is to send a “check for updates notice” to the persons listed as authorized users of agency's'field sites 14 by, for example, wireless e-mail. These and other implementations for theblock 218 transmission of the UPDATE REPORTS to fieldsites 14 are readily performed by persons skilled in the above-listed pertinent arts. - Block 218 also sends UPDATE REPORTS to the relief agency(ies) at, for example, their respective
client headquarter sites 16. This may be done by, for example, e-mail, with the e-mail having the UPDATE REPORT attached, or by an e-mail notice for the agency(ies) to log into their respective GIS databases and check for updates using, for example, theFIG. 2 viewer/web browser block 52. The process then goes to block 220 and ends. - Referring to
FIG. 5 , ifblock 210 determined that the DAMAGE ASSESSMENT REPORT was not sharable, blocks 212 followed by 222 through 226 are executed much the same asblocks 214 through 220, the only difference being that only one relief agency and one relief agency'sfield sites 14 receive the UPDATE REPORT. -
FIG. 7 is an example display, either on the video display of thecustomer headquarters 16 or the video display of thefield sites 14, as would be seen after receiving an UPDATE REPORT. TheFIG. 7 example uses call-outs that describe, with words, situations at a plurality of geographical locations.FIG. 8 is an example of symbols for use in overlay maps displayed on the video display of thecustomer headquarters 16 or the video display of thefield sites 14, either separate from in conjunction with call-outs as shown byFIG. 7 . - While the present system has been disclosed with reference to certain preferred embodiments, these should not be considered limitations. One skilled in the art will readily recognize that variations of these embodiments are possible, each falling within the scope of the system, and as set forth in the claims below.
Claims (26)
1-6. (canceled)
7. A device for capturing and communicating field assessments, the device comprising:
a data store that stores information including:
a base map corresponding to a geographical area; and
user-selectable field assessment forms;
a user interface that displays at least a portion of the base map and captures field assessments using a selected one of the user-selectable field assessment forms in the data store, each field assessment associated with a location within the geographical area; and
an electronic communication interface for transmitting captured field assessments to a server.
8. The device of claim 7 , further comprising a geolocator interface operable to receive geolocation information for associating field assessments with locations within the geographical area.
9. The device of claim 7 , wherein the electronic communication interface is operable to transmit and receive communications via a satellite.
10. The device of claim 7 , wherein the electronic communication interface is operable to receive one or more user-selectable field assessment forms.
11. The device of claim 7 , wherein the electronic communication interface receives updated situational information, and the user interface is operable to display at least a portion of the updated situational information overlaid on at least a portion of the base map.
12. A server for use in a global relief management system, the server comprising:
a field assessment device communication interface to facilitate receiving field assessments from field assessment devices and to facilitate transmitting update information to field assessment devices;
geographic information system data;
field assessment data, the geographic information system data and the field assessment data updated using received field assessments;
access control information; and
a report generation interface to facilitate access to the geographic information system data and the field assessment data, the report generation interface controlling access to the geographic information system data and the field assessment data using the access control information.
13. The server of claim 12 , wherein the field assessment device communication interface uses a satellite-based communication link.
14. The server of claim 12 , wherein the report generation interface is web-based.
15. The server of claim 12 , wherein the geographic information system data and the field assessment data are stored in a relational database.
16. The server of claim 12 , wherein the report generation interface requires authentication.
17. A data security method in a global relief management system, the data security method comprising:
receiving a field assessment submitted using a field assessment device;
maintaining field assessment access control information; and
controlling dissemination of at least a portion of the received field assessment based on the maintained field assessment access control information.
18. The method of claim 17 , wherein the received field assessment is associated with a first organization, and the maintained field assessment access control information prohibits dissemination of one or more portions of the received field assessment to organizations other than the first organization.
19. The method of claim 17 , wherein the maintained field assessment access control information implements a privilege hierarchy.
20. The method of claim 17 , wherein the received field assessment includes an attribute used in controlling dissemination of at least a portion of the received field assessment.
21. The method of claim 17 , wherein maintaining field assessment access control information includes maintaining access control information defining information sharing between government organizations and non-government organizations.
22. A method for generating organization-specific reports in a global relief management system, the method comprising:
identifying a geographical area;
identifying a requesting organization;
querying a data store for information in the identified geographical area that is accessible by the identified requesting organization;
retrieving information satisfying the query; and
preparing the retrieved information to generate a report.
23. The method of claim 22 , wherein retrieving information satisfying the query includes retrieving geographic information system information, and preparing the retrieved information to generate a report includes creating a map based on the retrieved geographic information system information.
24. The method of claim 22 , further comprising transmitting the generated report.
25. The method of claim 22 , wherein the generated report is a representation of one or more field assessment reports.
26. The method of claim 22 , wherein the generated report includes update information corresponding to the identified geographical area and the identified requesting organization.
27. A method for updating a field assessment device comprising:
determining a geographical location of a field assessment device;
transmitting a message indicating the geographical location of the field assessment device and identifying a user of the field assessment device;
receiving update information in response to the transmitted message, the update information corresponding to the identified user and the indicated geographical location.
28. The method of claim 27 , wherein the geographical location of the field assessment device is determined using a global positioning system receiver.
29. The method of claim 27 , wherein the update information includes a map overlay.
30. The method of claim 27 , wherein the update information includes at least one field assessment form.
31. The method of claim 27 , wherein the update information further includes at least one field assessment.
Priority Applications (1)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US11/878,771 US20080071442A1 (en) | 2004-02-02 | 2007-07-26 | Method and apparatus for global relief management |
Applications Claiming Priority (2)
Application Number | Priority Date | Filing Date | Title |
---|---|---|---|
US10/768,114 US7266558B2 (en) | 2004-02-02 | 2004-02-02 | Method and apparatus for global relief management |
US11/878,771 US20080071442A1 (en) | 2004-02-02 | 2007-07-26 | Method and apparatus for global relief management |
Related Parent Applications (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/768,114 Continuation US7266558B2 (en) | 2004-02-02 | 2004-02-02 | Method and apparatus for global relief management |
Publications (1)
Publication Number | Publication Date |
---|---|
US20080071442A1 true US20080071442A1 (en) | 2008-03-20 |
Family
ID=34807802
Family Applications (2)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/768,114 Expired - Fee Related US7266558B2 (en) | 2004-02-02 | 2004-02-02 | Method and apparatus for global relief management |
US11/878,771 Abandoned US20080071442A1 (en) | 2004-02-02 | 2007-07-26 | Method and apparatus for global relief management |
Family Applications Before (1)
Application Number | Title | Priority Date | Filing Date |
---|---|---|---|
US10/768,114 Expired - Fee Related US7266558B2 (en) | 2004-02-02 | 2004-02-02 | Method and apparatus for global relief management |
Country Status (1)
Country | Link |
---|---|
US (2) | US7266558B2 (en) |
Cited By (1)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110153576A1 (en) * | 2009-12-22 | 2011-06-23 | Daniel Figus | Multi-Client Generic Persistence for Extension Fields |
Families Citing this family (57)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US7266558B2 (en) * | 2004-02-02 | 2007-09-04 | Gray Michael D | Method and apparatus for global relief management |
WO2005094226A2 (en) | 2004-03-04 | 2005-10-13 | United States Postal Service | System and method for providing centralized management and distribution of information to remote users |
US20060212696A1 (en) * | 2005-03-17 | 2006-09-21 | Bustelo Leugim A | Method and system for selective information delivery in a rich client form |
CA2616652A1 (en) * | 2005-07-26 | 2007-02-08 | James H. Johnson, Jr. | Method of community service and disaster relief |
US7546219B2 (en) * | 2005-08-31 | 2009-06-09 | The Boeing Company | Automated damage assessment, report, and disposition |
US20070219813A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Purchase option-based emergency supplies provisioning method |
US20070233501A1 (en) * | 2006-03-17 | 2007-10-04 | Moore Barrett H | Subscription-based private civil security facilitation method |
US20070239480A1 (en) * | 2006-03-30 | 2007-10-11 | Moore Barrett H | Subscription-based catastrophe-triggered medical services facilitation method |
US20070203727A1 (en) * | 2006-02-24 | 2007-08-30 | Moore Barrett H | Emergency supplies pre-positioning and access control method |
US20070219812A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Subscription-based multi-person emergency shelter method |
US20070219810A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Personal profile-based private civil security subscription method |
US20100250352A1 (en) * | 2006-03-17 | 2010-09-30 | Moore Barrett H | System and Method for a Private Civil Security Loyalty Reward Program |
US20070217577A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Private civil defense-themed television broadcasting method |
US20090100772A1 (en) * | 2006-03-17 | 2009-04-23 | Moore Barrett H | Fractionally-possessed underground shelter method and apparatus |
US20070225994A1 (en) * | 2006-03-17 | 2007-09-27 | Moore Barrett H | Method for Providing Private Civil Security Services Bundled with Second Party Products |
US20070225993A1 (en) * | 2006-03-17 | 2007-09-27 | Moore Barrett H | Method for Civilly-Catastrophic Event-Based Transport Service and Vehicles Therefor |
US20070228090A1 (en) * | 2006-03-17 | 2007-10-04 | Seidel Gregory E | Method of Providing Survival Supplies Container with an Illumination Apparatus |
US20080255868A1 (en) * | 2006-03-17 | 2008-10-16 | Moore Barrett H | Subscription-Based Private Civil Security Facilitation Method and Apparatus |
US20070219431A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Method to Facilitate Providing Access to a Plurality of Private Civil Security Resources |
US20070219423A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Privately Provisioned Survival Supplies Content Acquisition Method |
US20070225995A1 (en) * | 2006-03-17 | 2007-09-27 | Moore Barrett H | Method and Security Modules for an Incident Deployment and Response System for Facilitating Access to Private Civil Security Resources |
US20080275308A1 (en) * | 2006-03-17 | 2008-11-06 | Moore Barrett H | Premium-Based Civilly-Catastrophic Event Threat Assessment |
US20070219421A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Privately Provisioned Survival Supplies Delivery Method |
US20070219428A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Method of providing a floating life-sustaining facility |
US20070276681A1 (en) * | 2006-03-17 | 2007-11-29 | Moore Barrett H | Method Of Providing Bearer Certificates For Private Civil Security Benefits |
US20070219424A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Method To Privately Provision Survival Supplies That Include Third Party Items |
US20070215434A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Subscription Based Shuttle Method |
US20070219430A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Electricity Providing Privately Provisioned Subscription-Based Survival Supply Unit Method And Apparatus |
US20070233506A1 (en) * | 2006-03-17 | 2007-10-04 | Moore Barrett H | Privately Managed Entertainment and Recreation Supplies Provisioning Method |
US20070219426A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Subscription-Based Private Civil Security Resource Customization Method |
US20070219420A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Subscription-Based Catastrophe-Triggered Rescue Services Facilitation Method Using Wireless Location Information |
US20070219914A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Document-based civilly-catastrophic event personal action guide facilitation method |
US20080319766A1 (en) * | 2006-03-17 | 2008-12-25 | Moore Barrett H | Subscription-based catastrophe-triggered transport services facilitation method and apparatus |
US20100312722A1 (en) * | 2006-03-17 | 2010-12-09 | Moore Barrett H | Privately Provisioned Sub-Unit-Based Survival Supplies Provisioning Method |
US20110030310A1 (en) * | 2006-03-17 | 2011-02-10 | Moore Barrett H | Subscription-Based Intermediate Short-Term Emergency Shelter Method |
US20070256564A1 (en) * | 2006-05-04 | 2007-11-08 | Moore Barrett H | Positive pressure filtration kit apparatus and method |
US20090112777A1 (en) * | 2006-03-17 | 2009-04-30 | Moore Barrett H | Method of providing variable subscription-based access to an emergency shelter |
US20070219427A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Premium-Based Private Civil Security Policy Methods |
US20090125316A1 (en) * | 2006-03-17 | 2009-05-14 | Moore Barrett H | Rescue container method and apparatus |
US20070214729A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Resource Container And Positioning Method And Apparatus |
US20090321663A1 (en) * | 2006-03-17 | 2009-12-31 | Moore Barrett H | Radiation-blocking bladder apparatus and method |
US20070219429A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Privately Provisioned Interlocking Sub-Unit-Based Survival Supplies Provisioning Method |
US20070219422A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Privately Provisioned Survival Supplies Sub-Unit-Based Delivery Method |
US20070261899A1 (en) * | 2006-03-17 | 2007-11-15 | Moore Barrett H | Subscription-based pre-provisioned towable unit facilitation method |
US20070219814A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Publicly-Funded Privately Facilitated Access to Survival Resources Method |
US20070232220A1 (en) * | 2006-03-17 | 2007-10-04 | Moore Barrett H | Private civil defense-themed broadcasting method |
US20070219425A1 (en) * | 2006-03-17 | 2007-09-20 | Moore Barrett H | Waste Disposal Device |
US20070223658A1 (en) * | 2006-03-17 | 2007-09-27 | Moore Barrett H | Method and Apparatus to Facilitate Deployment of One or More Private Civil Security Resources |
US20080195426A1 (en) * | 2006-03-17 | 2008-08-14 | Moore Barrett H | Subscription-Based Mobile Shelter Method |
WO2008085584A2 (en) * | 2006-10-30 | 2008-07-17 | Moore Barrett H | Subscription-based private civil security facilitation method |
US8069202B1 (en) | 2007-02-02 | 2011-11-29 | Resource Consortium Limited | Creating a projection of a situational network |
US8965681B2 (en) * | 2008-09-03 | 2015-02-24 | Global Relief Technologies, Inc. | Field device communications |
US9167080B2 (en) * | 2009-03-31 | 2015-10-20 | Centurylink Intellectual Property Llc | System and method for providing callers with local time and other information at called locations |
US8666043B2 (en) | 2009-04-08 | 2014-03-04 | Centurylink Intellectual Property Llc | Telephone for providing information associated with a remote geographic location of a called party to a caller |
US20140039937A1 (en) | 2012-08-03 | 2014-02-06 | Cloudbridge, Llc | Insurance Data Management System |
US10504062B2 (en) * | 2013-01-28 | 2019-12-10 | Mike Wilson | Disaster mitigation and recovery system and method |
US10002339B2 (en) * | 2013-07-11 | 2018-06-19 | Fluor Technologies Corporation | Post-disaster assessment systems and methods |
Citations (14)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5815417A (en) * | 1994-08-04 | 1998-09-29 | City Of Scottsdale | Method for acquiring and presenting data relevant to an emergency incident |
US5978804A (en) * | 1996-04-11 | 1999-11-02 | Dietzman; Gregg R. | Natural products information system |
US6023706A (en) * | 1997-07-11 | 2000-02-08 | International Business Machines Corporation | Parallel file system and method for multiple node file access |
US6259972B1 (en) * | 1998-01-16 | 2001-07-10 | Enghouse Systems Usa, Inc. | Method for processing and disseminating utility outage information |
US20020016861A1 (en) * | 1999-04-23 | 2002-02-07 | Adam J. Simonoff | Computer software for converting a general purpose computer network into an interactive communications system |
US20020069312A1 (en) * | 2000-07-10 | 2002-06-06 | Jones Gad Quentin | System and method for the storage, management and sharing of spatial-temporal based information |
US20020138527A1 (en) * | 2001-03-21 | 2002-09-26 | Neider Bell | System and method for a web-based venture reporting |
US20020143469A1 (en) * | 2001-03-30 | 2002-10-03 | Alexander John Franklin | Emergency management system |
US20030009315A1 (en) * | 2001-05-15 | 2003-01-09 | Thomas Paul A. | System for creating measured drawings |
US20040192353A1 (en) * | 2002-07-02 | 2004-09-30 | Charles Mason | Geolocation system-enabled speaker-microphone accessory for radio communication devices |
US20040236620A1 (en) * | 2003-05-19 | 2004-11-25 | Chauhan S. K. | Automated utility supply management system integrating data sources including geographic information systems (GIS) data |
US6961586B2 (en) * | 2000-06-27 | 2005-11-01 | Field Data Management Solutions, Llc | Field assessments using handheld data management devices |
US7043529B1 (en) * | 1999-04-23 | 2006-05-09 | The United States Of America As Represented By The Secretary Of The Navy | Collaborative development network for widely dispersed users and methods therefor |
US7266558B2 (en) * | 2004-02-02 | 2007-09-04 | Gray Michael D | Method and apparatus for global relief management |
Family Cites Families (4)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
DE4318441A1 (en) | 1993-06-03 | 1994-12-08 | Sel Alcatel Ag | Emergency call system |
US5628050A (en) | 1994-12-09 | 1997-05-06 | Scientific And Commercial Systems Corporation | Disaster warning communications system |
US6028514A (en) | 1998-10-30 | 2000-02-22 | Lemelson Jerome H. | Personal emergency, safety warning system and method |
US6526275B1 (en) | 2000-04-24 | 2003-02-25 | Motorola, Inc. | Method for informing a user of a communication device where to obtain a product and communication system employing same |
-
2004
- 2004-02-02 US US10/768,114 patent/US7266558B2/en not_active Expired - Fee Related
-
2007
- 2007-07-26 US US11/878,771 patent/US20080071442A1/en not_active Abandoned
Patent Citations (18)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US5815417A (en) * | 1994-08-04 | 1998-09-29 | City Of Scottsdale | Method for acquiring and presenting data relevant to an emergency incident |
US5978804A (en) * | 1996-04-11 | 1999-11-02 | Dietzman; Gregg R. | Natural products information system |
US6023706A (en) * | 1997-07-11 | 2000-02-08 | International Business Machines Corporation | Parallel file system and method for multiple node file access |
US6259972B1 (en) * | 1998-01-16 | 2001-07-10 | Enghouse Systems Usa, Inc. | Method for processing and disseminating utility outage information |
US20020016861A1 (en) * | 1999-04-23 | 2002-02-07 | Adam J. Simonoff | Computer software for converting a general purpose computer network into an interactive communications system |
US7043529B1 (en) * | 1999-04-23 | 2006-05-09 | The United States Of America As Represented By The Secretary Of The Navy | Collaborative development network for widely dispersed users and methods therefor |
US6961586B2 (en) * | 2000-06-27 | 2005-11-01 | Field Data Management Solutions, Llc | Field assessments using handheld data management devices |
US20020069312A1 (en) * | 2000-07-10 | 2002-06-06 | Jones Gad Quentin | System and method for the storage, management and sharing of spatial-temporal based information |
US20020138527A1 (en) * | 2001-03-21 | 2002-09-26 | Neider Bell | System and method for a web-based venture reporting |
US6868340B2 (en) * | 2001-03-30 | 2005-03-15 | John Franklin Alexander | Emergency management system |
US6574561B2 (en) * | 2001-03-30 | 2003-06-03 | The University Of North Florida | Emergency management system |
US20020143469A1 (en) * | 2001-03-30 | 2002-10-03 | Alexander John Franklin | Emergency management system |
US20030009315A1 (en) * | 2001-05-15 | 2003-01-09 | Thomas Paul A. | System for creating measured drawings |
US7130774B2 (en) * | 2001-05-15 | 2006-10-31 | Metron Media, Inc. | System for creating measured drawings |
US20040192353A1 (en) * | 2002-07-02 | 2004-09-30 | Charles Mason | Geolocation system-enabled speaker-microphone accessory for radio communication devices |
US20040236620A1 (en) * | 2003-05-19 | 2004-11-25 | Chauhan S. K. | Automated utility supply management system integrating data sources including geographic information systems (GIS) data |
US7739138B2 (en) * | 2003-05-19 | 2010-06-15 | Trimble Navigation Limited | Automated utility supply management system integrating data sources including geographic information systems (GIS) data |
US7266558B2 (en) * | 2004-02-02 | 2007-09-04 | Gray Michael D | Method and apparatus for global relief management |
Cited By (3)
Publication number | Priority date | Publication date | Assignee | Title |
---|---|---|---|---|
US20110153576A1 (en) * | 2009-12-22 | 2011-06-23 | Daniel Figus | Multi-Client Generic Persistence for Extension Fields |
US8224828B2 (en) * | 2009-12-22 | 2012-07-17 | Sap Ag | Multi-client generic persistence for extension fields |
US8805864B2 (en) | 2009-12-22 | 2014-08-12 | Sap Ag | Multi-client generic persistence for extension fields |
Also Published As
Publication number | Publication date |
---|---|
US20050171952A1 (en) | 2005-08-04 |
US7266558B2 (en) | 2007-09-04 |
Similar Documents
Publication | Publication Date | Title |
---|---|---|
US7266558B2 (en) | Method and apparatus for global relief management | |
US6868340B2 (en) | Emergency management system | |
US6999876B2 (en) | Modular architecture for rapid deployment and coordination of emergency event field surveillance | |
US10055972B2 (en) | System and method for providing centralized management and distribution of information to remote users | |
US20100328093A1 (en) | Emergency Responder Geographic Information System | |
US20020165732A1 (en) | System and method for automated and interactive scheduling | |
US20090172131A1 (en) | Emergency Information System | |
US20110068915A1 (en) | Geocoded alert system | |
US20120130753A1 (en) | GPS Pathfinder Cell Phone and Method | |
WO2013188762A1 (en) | Gps pathfinder cell phone and method | |
US20090012798A1 (en) | Traveler safety information correlation system and associated methods | |
JP2007102263A (en) | Disaster action support system and management server for the same | |
US20050107028A1 (en) | Integrated communication and geographic positioning system and method of using same | |
US6957250B1 (en) | Map-information providing system using computer network | |
US20020059246A1 (en) | Method of distributing information to emergency personnel | |
EP1241612A1 (en) | Mobile decision support system | |
JP2005122562A (en) | Support system and method in disaster | |
CN101990665B (en) | Landscape/yellow page showing and sharing method and system basen on geography location | |
US20070244981A1 (en) | Disseminating information about security threats | |
KR100815432B1 (en) | System and method for managing business disaster, and medium for storing computer readable program for executing the method | |
JP2002041948A (en) | Emergency information distribution system | |
Werder | Knowledge representation for disaster management | |
WO2002023381A1 (en) | Method and device for distributing information to emergency personnel | |
Seeman et al. | Utility And Contents Of Information Systems To Implement And Manage Next Generation (NG) 911 Under Federal Communications Policies | |
KR20010100426A (en) | Grave management system using satellite and internet |
Legal Events
Date | Code | Title | Description |
---|---|---|---|
AS | Assignment |
Owner name: GLOBAL RELIEF TECHNOLOGIES, LLC, NEW HAMPSHIRE Free format text: ASSIGNMENT OF ASSIGNORS INTEREST;ASSIGNORS:GRAY, MICHAEL D.;PETER, ARTHUR, III;REEL/FRAME:019969/0478 Effective date: 20071015 |
|
AS | Assignment |
Owner name: GLOBAL RELIEF TECHNOLOGIES, INC., NEW HAMPSHIRE Free format text: CHANGE OF NAME;ASSIGNOR:GLOBAL RELIEF TECHNOLOGIES, LLC;REEL/FRAME:020299/0522 Effective date: 20071226 |
|
STCB | Information on status: application discontinuation |
Free format text: ABANDONED -- FAILURE TO RESPOND TO AN OFFICE ACTION |