JP2007102263A - Disaster action support system and its management server - Google Patents

Abstract

An appropriate disaster action manual can be presented for each user in consideration of disaster types as well as user attributes.
A user database DB1 storing user attribute information such as a user's department name and job title, an organization database DB2 storing organization attribute information such as a structure of an organization and a disaster countermeasure headquarters, and the user The disaster action manual database DB3 is stored which stores disaster action manuals prepared in advance according to the attributes of the organization, the attributes of the organization, and the disaster type. In response to a distribution request from the electronic terminals TM1 to TMn, the management server SV1 corresponds to the department name and job title of the requesting user from the disaster action manual database DB3, and further corresponds to the disaster type. The action manual is read and distributed to the requesting electronic terminal.
[Selection] Figure 1

Description

  The present invention relates to a disaster action support system and its management server that support user actions and related organization operations based on action standards when a disaster such as an earthquake occurs.

  The Disaster Countermeasures Basic Law states: “To protect the lives, bodies and property of national professors and people from disasters, establish necessary systems through the national government, local governments and other public institutions, and clarify the responsibilities. Along with the creation of disaster prevention plans, disaster prevention, disaster emergency measures, financial restoration measures for disaster recovery and disaster prevention, and other necessary disaster countermeasures, we will establish and promote comprehensive and systematic disaster prevention administration. It aims to contribute to maintaining social order and ensuring public welfare. "

  In accordance with the Disaster Countermeasures Basic Law, the Central Disaster Prevention Council has prepared a disaster prevention basic plan. Each prefecture has a regional disaster prevention plan, and designated government agencies have disaster prevention work plans. In addition, the establishment of an emergency response headquarters is obligatory, and various procedures such as operating guidelines for disaster response headquarters are established by prefectures and designated administrative agencies. In the disaster management headquarters operation guidelines, etc., the division of roles according to the level of the disaster, priorities when unable to gather, details of work in charge, communication system, etc. are shown. In addition, various actions to be taken by each staff member, fire brigade, flood control team, and residents in accordance with established policies are described in various disaster prevention manuals such as disaster action manuals.

  On the other hand, national and local governments are promoting digitalization of disaster prevention radio, expansion of various radio facilities, enhancement of optical fiber networks, etc., in order to smoothly transmit information even in the event of a disaster. In addition, many systems for sharing information for efficiently linking national government ministries and agencies, between national governments and local governments, and between local governments have been studied (for example, see Non-Patent Document 1). ). However, in the event of an emergency, the input work is a heavy burden, and there are many cases where it is not utilized as expected.

http://www.bousaihaku.com/cgi-bin/hp/index2.cgi?ac1=B414&ac2=B41404&ac3=3606&Page=hpd2_view

  By the way, the action manual at the time of disaster is generally written for all employees and employees, so there are only a part of the description of the work in charge and contact information for each individual at the time of disaster . For this reason, even if each person in charge tries to refer to the manual by paying attention only to the relevant part of the person in charge, the person in charge is often a paper medium, and the search takes time. Also, even if all character information is digitized and searched by keywords, etc., the same words are written in various places in the manual, so it takes time to reach the part you really want to refer to, or search The skill for is required. In addition, the duties and necessary contact information that individuals are responsible for in the event of a disaster are often determined by the departments and positions of employees, employees, and the priority of the person who should play the role when acting on behalf. It is common that it is defined.

  Therefore, it can be said that it is easier to use a manual for the contact system in which the contents of work in charge and necessary contact information are customized according to the staff who uses it, the department to which the employee belongs, and the role. In addition, in the event of a disaster, there is a high possibility that staff members or employees who cannot gather as prescribed in advance will also appear, and even contact may not be possible.

  Since the disaster response headquarters needs to be set up within 30 minutes to 2 hours after the disaster occurs, it will be set up only by staff and employees who can gather at the headquarters within this time. At this time, although the priority order of which staff and employee is responsible for which position is determined, the structure of the disaster response headquarters and the communication system are likely to be different from those of disaster drills. Therefore, even during the confusion at the time of gathering, there is an urgent need for a mechanism to support the disaster response headquarters so that they can quickly reorganize the initial response structure and contact system and act flexibly according to the situation.

  On the other hand, national and local government officials are obligated to confirm the status of damage and report it when it arrives at the disaster response headquarters if there is a damage location during the gathering at the time of the disaster. The report forms described in many manuals include a method of submitting the confirmation date and time, the location of the disaster, the name of the person who confirmed the disaster, the situation of the disaster, etc., on the form.

  However, in the disaster response headquarters where various information is complicated, a lot of ingenuity is required in order to categorize such information according to time series or disaster classification and to transmit it to the responsible department. Also, in principle, paper reports in the prescribed format are often used for reporting. In addition, if a disaster occurs in the department to which you belong at a business trip destination or travel destination, you may gather at a nearby branch office or office, but you may not know the contact information or location is there.

  The present invention has been made paying attention to the above circumstances, and its purpose is to be able to present an appropriate disaster action manual for each user in consideration of disaster types as well as user attributes. It is to provide a disaster action support system and its management server.

  To achieve the above object, the present invention provides a user database for managing attribute information of a plurality of users, an organization database for managing attribute information of organizations to be managed in association with the attribute information of the users, Disaster action manual database storing disaster action manuals created in advance for each of the user attribute information, organization attribute information, and disaster information, a management server connectable to these databases, and the management server In the disaster action support system comprising a plurality of electronic terminals accessible to the user, the management server causes the user attribute corresponding to the user database and organization database in response to a request from the electronic terminal. Information and organization attribute information are searched, and the retrieved user attribute information and organization attribute information are generated. On the basis of the information representing the disaster, read the disaster another disaster action manual corresponding to the requesting user from the disaster action manual database. Then, the read disaster action manual is distributed to the requesting electronic terminal.

  Therefore, according to the present invention, in the event of a disaster, for each user, the user attributes such as the department or position to which the user belongs, the organization attributes such as the organization structure and the contact system to which the user belongs, and the type and scale of the disaster The disaster action manual corresponding to the disaster information is distributed. In other words, a disaster manual specific to each user is presented. Therefore, each user can clearly and quickly grasp the procedures and contents of the disaster response work to be performed by each user.

  In addition, the present invention collects information on the gathering status of users at the time of a disaster, and includes information on the gathering status collected and disaster countermeasure team organization rule information determined in advance based on the attribute information of the organization. At the same time, create a system communication table for the disaster response team composed of the users who have gathered. And it is further characterized by further providing a function of distributing the prepared disaster countermeasure team system communication table to the electronic terminals used by the gathered users.

  Therefore, by providing such a function, when a disaster occurs, a disaster response team with an initial action system is automatically formed according to the gathering status of the user, and the information is notified to the gathering person. For this reason, the disaster countermeasure team and the participants who make up this team can start work quickly and reliably.

  Further, the present invention transmits, to each of the plurality of electronic terminals, a means for accepting input of information indicating a disaster situation on the gathering route by the user, and information representing the disaster situation on the inputted gathering route to the management server. Means. On the other hand, the management server aggregates the information indicating the damage status on the gathering route transmitted from the plurality of electronic terminals and the information indicating the damage status on the received gathering route. And a means for creating status report data.

  Therefore, the damage status on the route where each user gathers at the gathering location is collected by the management server, and based on this, the damage status report data is created. For this reason, for example, in the disaster countermeasure headquarters, it is possible to quickly grasp the disaster situation such as the disaster area and its scale before organizing the disaster countermeasure team and sending the investigation personnel.

  Furthermore, according to the present invention, the management server determines the disaster area based on the information indicating the disaster situation on the gathering route received from the electronic terminal. Then, the disaster countermeasure team or user in charge of the determined disaster area is selected, and the prepared disaster situation report data is distributed to the electronic terminal used by the selected disaster countermeasure team or user. It is characterized by doing.

  If it does in this way, the report data of the disaster situation for every disaster area will be automatically distributed to the disaster countermeasure team or user with high relation with the disaster area concerned. For this reason, the disaster countermeasure team or the user can quickly grasp and respond to, for example, the disaster situation in the area that he / she should have jurisdiction over.

Furthermore, the present invention is an optimum method for acquiring information representing positions of a plurality of electronic terminals in a management server, and for a user existing at the position to move to a meeting place based on the obtained information representing the position. Calculate the route. Then, the information representing the calculated optimum route is distributed to the corresponding electronic terminal.
Therefore, each user can grasp his / her own gathering place and the optimum gathering route, so that he / she can quickly and reliably gather at an appropriate gathering place. This is particularly effective when the user is in a place unfamiliar with geography, such as a business trip destination or a travel destination.

  In short, according to the present invention, it is possible to provide a disaster action support system capable of presenting appropriate work for each user in consideration of user attributes, organization attributes, and disaster situations.

Embodiments of the present invention will be described below with reference to the drawings.
(First embodiment)
FIG. 1 is a schematic configuration diagram showing a first embodiment of a disaster action support system according to the present invention.
This system includes a management server SV1, and a user database DB1, an organization database DB2, and a disaster action manual database DB3 connected to the management server SV1. A plurality of electronic terminals TM1 to TMn used by the user can be connected to the management server SV1 via the communication network NW.

  The user database DB1 stores user attribute information including departments and contact information in association with user identification information (user ID). In the organization database DB2, information representing the organization configuration and communication system of the entire organization to be managed is stored in association with the user's title. In the disaster action manual database DB3, information on the work contents in charge, the work flow in charge, and the communication system at the time of a disaster for each user is stored separately for each disaster type and disaster scale.

  The management server SV1 includes a database management function, a disaster action manual creation function, and a disaster action manual distribution control function as control functions according to the present invention. The database management function registers, updates, and deletes attribute information for the databases DB1 and DB2. The disaster action manual creation function creates a disaster action manual organized by disaster type and disaster scale according to each user's department and position, and the prepared disaster action manual is the above disaster action manual Store in database DB3. The disaster action manual distribution control function corresponds to the disaster action manual corresponding to the department and position of the requesting user according to the distribution request from the electronic terminals TM1 to TMn and corresponding to the disaster type and the disaster scale. Read from the disaster action manual database DB3 and distribute to the requesting electronic terminal.

  The electronic terminals TM1 to TMn are composed of, for example, a mobile phone, a PDA (Personal Digital Assistant) or a notebook personal computer, and include an attribute information registration control function and a manual acquisition control function as control functions according to the present invention. The attribute information registration control function transmits user attribute information including the user's department and contact information to the management server SV1 via the communication network NW, and stores it in the user database DB1. It also has an attribute information update / deletion request function associated with a change or retirement. The manual acquisition control function transmits a distribution request including information necessary for authentication such as a user ID to the management server SV1, and receives a disaster action manual addressed to itself from the management server SV1.

  The management server SV1 is provided with a recording medium input / output unit (memory card slot) SR. A storage medium MC such as a memory card is detachably inserted into the recording medium input / output unit SR. The storage medium MC is used when information is transferred between the user's electronic terminal TM0 and the management server SV1 without using the communication network NW. The management server SV1 receives the user's information from the storage medium MC. The attribute information is read and stored in the user database DB1. At the same time, a disaster action manual for users is provided to the electronic terminal TM0 via the storage medium MC.

  The communication network NW includes, for example, an IP (Internet Protocol) network represented by the Internet and a plurality of access networks for accessing the IP network. As the access network, for example, a DSL (Digital Subscriber Line) or a wired subscriber network using an optical transmission line, a CATV (Cable Television) network, a wireless LAN (Local Area Network), a mobile communication network, or a dedicated line network is used.

Next, the operation of the disaster action support system configured as described above will be described. FIG. 2 is a flowchart showing the control procedure and control contents of the management server SV1, which is the central presence of this system.
(1) Initial setting of the management server SV1
First, in step S21, the management server SV1 classifies the disaster behavior manuals digitized in text format for each disaster type, and adds a tag or table name for recognizing the disaster type to the disaster behavior manual. Save in database DB3. At this time, the data classified for each disaster type can be converted and saved in a format such as HTML (Hypertext Markup Language) or XML (Extensive Markup Language) that has high compatibility with other software and applications. .

  Next, in step S22, the disaster headquarters installation standards, the outline of the administrative work of each team in the countermeasure headquarters, the contact system, the business flow, and the business content are extracted from the data classified in step S21. Are stored in the disaster action manual database DB3. In step S23, the five items of data extracted in step S22 are classified into workplace units such as each responsible department or each responsible section, and the classified data is stored in the disaster action manual database DB3.

  Further, in step 4, the data classified in step S23 is classified for each responsible post and stored in the disaster action manual database DB3. In both step S22 and step S23, when information is classified, a tag, a table name, or the like is added to enable information retrieval or the like.

  FIG. 3 shows an example of the configuration of disaster action manuals classified by performing the processing from step S21 to step S24. That is, as shown in the figure, the manuals M1, M2, etc. after classification correspond to each position, and the disaster headquarters installation standards, jurisdiction, and communication system are classified according to the type of disaster such as earthquakes, tsunamis, storms and floods, and volcanoes. , Business flow, and data of 5 items consisting of business contents are classified and associated with each other.

  Next, in step 5, the management server SV1 stores user attribute information including each user's user ID, user name, department name, job title, contact information, and route of collection in the user database DB1. The user attribute information storage process is performed by acquiring the user attribute information from the user's electronic terminals TM1 to TMn via the communication network NW or by reading the user attribute information from the storage medium MC.

  FIG. 4 is a diagram showing the association between the user database DB1 and the organization database DB2. That is, the department name and position of the user attribute information stored in the user database DB1, and the organization structure chart and the disaster countermeasure headquarter organization chart stored in the organization database DB2 are stored in a mutually associated state. The

(2) Distribution of disaster action manuals
On the other hand, in the user's electronic terminals TM1 to TMn, an initial setting process and a disaster action manual acquisition process are performed as follows. FIG. 5 is a flowchart showing the control procedure and control contents.

  In the electronic terminals TM1 to TMn, first, in step S51, registration processing of user attribute information including a user ID, a user name, a department name, a title, a contact information, a collection route, a password for authentication and biometric information is performed. . This registration process may be performed by a user's manual input operation, but attribute information created in advance in a personal computer or the like may be copied. The user attribute information registered in this manner is transferred to the management server SV1 via the communication network NW or the storage medium MC as described above, and registered in the user database DB1.

  Next, in step S52, the electronic terminals TM1 to TMn access the management server SV1 via the communication network NW or the storage medium MC. In step S53, information necessary for authentication, such as a user ID and password, is sent to the management server SV1 based on the user attribute information registered in step S51. The management server SV1 compares the authentication information sent from the electronic terminals TM1 to TMn with the user attribute information registered in the user database DB1, thereby determining the validity of the requesting electronic terminal. As a result of this determination, when the validity of the requesting electronic terminal is confirmed, the right to access the disaster action manual database DB3 is given to the electronic terminal.

  In step S54, the electronic terminals TM1 to TMn which have obtained the access right transmit information representing the department and title in the user attribute information to the management server SV1. On the other hand, the management server SV1 searches the disaster action manual database DB3 from the user database DB1 and the organization database DB2 based on the information indicating the department and position of the user sent from the electronic terminal. Search for the information you need. Based on the retrieved information, a disaster action manual corresponding to the user's department and job title and corresponding to the disaster type is read from the disaster action manual database DB3. Then, the read disaster behavior manual is downloaded via the communication network NW, or written in the storage medium MC to be distributed to the electronic terminal.

  FIG. 6 is a diagram showing the association between the user database DB1 and the disaster action manual database DB3. The department name and position of the user database DB1 and the manual of the disaster action manual database DB3 correspond to each other. Saved as attached.

  FIG. 7 shows an example of a disaster action manual displayed on the display screen when a mobile phone is used as an electronic terminal. As shown in FIG. 7, on the display screen of the electronic terminal, an action manual at the time of a disaster including the outline of the administrative work, the contact system, the work flow, and the work content is displayed for each disaster type according to the department and position of the user. Is displayed. The operation at the time of contact can be simplified by linking the contact system table with the telephone book.

  Further, as shown in FIG. 7, a disaster type selection menu may be displayed so that the menu desired by the user can be selected. In this way, the selected menu is sent from the electronic terminal to the management server SV1, and on the other hand, the disaster action manual relating to the corresponding disaster type is read from the disaster action manual database DB3 and requested from the management server SV1. Downloaded to the original electronic terminal. Therefore, even when a plurality of types of disasters are simultaneously or induced, the user can acquire and check the disaster action manual corresponding to each disaster type.

  As described above, in the first embodiment, the user database DB1 that stores user attribute information such as the user's department name and job title, and the organization attribute information such as the structure of the organization and the disaster countermeasure headquarters are stored. An organization database DB2 and a disaster action manual database DB3 storing disaster action manuals prepared in advance according to the user attributes, organization attributes, and disaster types are provided. In response to a distribution request from the electronic terminals TM1 to TMn, the management server SV1 corresponds to the department name and job title of the requesting user from the disaster action manual database DB3, and further corresponds to the disaster type. The action manual is read and distributed to the requesting electronic terminal.

  Therefore, when a disaster occurs, a disaster action manual corresponding to the department or title to which the user belongs, the organization and communication system of the organization to which the user belongs, and the disaster type or scale is distributed. In other words, a disaster action manual unique to each user is presented. Therefore, each user can clearly and quickly grasp the procedures and contents of the disaster response work to be performed by each user.

(Second Embodiment)
In the second embodiment of the present invention, information representing the gathering status is collected from each user's electronic terminal and stored in the gathering status database. Then, based on the information that represents the status of each user's gathering, the disaster response headquarters organization table and communication system table for the initial response system composed only of the attendees are created, and the corresponding user's electronic It is intended to be distributed to terminals.

FIG. 8 is a diagram used for explaining the configuration and operation of the disaster action support system according to the second embodiment of the present invention.
This system includes a gathering situation database DB4 and a headquarter organization database DB5 in addition to a user database DB1, an organization database DB2, and a disaster action manual database DB3.

  In the gathering status database DB4, information representing the gathering status of the users collected from the electronic terminals TM1 to TMn of each user is stored. The headquarters organization database DB5 stores headquarters organization rule information that defines the priority order of each job in the disaster countermeasure headquarters that is prescribed for the department and position that normally belongs. FIG. 9 shows an example of the headquarter organization rule information.

  The management server SV2 includes a gathering status collection control function, an initial action system organization processing function, and an initial action system distribution control function as control functions according to the present invention. The gathering status collection control function collects information representing the gathering status from each user's electronic terminals TM1 to TMn and stores it in the gathering status database DB4. At this time, in addition to the information indicating the gathering status, information indicating the safety confirmation may be collected and stored.

  The initial organization organization processing function completed the gathering based on the information representing the gathering status of each user stored in the gathering situation database DB4 and the headquarters organization rule information stored in the headquarters organization database DB5. Prepare the disaster response headquarters organization table and communication system table for the initial response system consisting only of users.

  The initial action system distribution control function is provided through the communication network NW together with the business manual read from the disaster action manual database DB3, the disaster response headquarters organization table and the contact system chart of the initial action system created by the initial action system organization processing function. Deliver to the corresponding user's electronic terminal.

Next, the operation of the system configured as described above will be described.
In the electronic terminals TM1 to TMn, as shown in FIG. 8, a confirmation menu for completion of the meeting and a safety confirmation menu are displayed in step S81. When the user arrives at the determined meeting place, the user selects and inputs the completion of the gathering on the confirmation screen. At the same time, the safety confirmation result of the family is input. The input collection confirmation information and safety confirmation information are stored in the memories in the electronic terminals TM1 to TMn.

  In this state, when the management server SV2 sends a request for sending the gathering status to the electronic terminals TM1 to TMn of each user, the gathering confirmation information and the safety information are sent from the electronic terminals TM1 to TMn to the management server SV2 via the communication network NW. Confirmation information is sent. The management server SV2 stores the gathering confirmation information and the safety confirmation information sent from the electronic terminals TM1 to TMn in the gathering situation database DB4.

  The collection confirmation information and the safety confirmation information may be collected via the storage medium MC without going through the communication network NW. In addition, when there is another system for managing the gathering status and safety information, the gathering confirmation list and safety confirmation information are not collected from the electronic terminals TM1 to TMn, and the attendee list is obtained from the other system. You may make it preserve | save in the gathering status database DB4.

  Next, in step S82, the management server SV2 completes the gathering according to the headquarters organization rule information registered in the headquarters organization database DB5 and the information representing the gathering status of each user stored in the gathering status database DB4. Prepare a disaster response headquarters system table and a communication system table for the initial response system consisting of only personnel. Then, the prepared disaster response headquarters system table and communication system table are communicated to the corresponding user's electronic terminal, together with a business manual that indicates the assigned duties and positions of the disaster response headquarters assigned to each participant. Deliver via the network NW.

  On the other hand, in step S83, the electronic terminals TM1 to TMn receive the disaster response headquarter organization table, the communication system table, and the business manual distributed from the management server SV2, store them in the internal memory, and show them in FIG. As shown on the display screen. The disaster response headquarter system table, the communication system table, and the business manual of the initial system may be imported into the electronic terminals TM1 to TMn via the storage medium MC.

  As described above, according to the second embodiment, the disaster countermeasure headquarters system and the communication system are automatically organized according to the gathering situation at the time of a disaster and distributed to the gathered users. For this reason, the disaster countermeasure team and the participants who make up this team can start work quickly and reliably.

(Third embodiment)
In the third embodiment of the present invention, each electronic terminal is provided with a function for a user to input information indicating the damage status on the gathering route, and the damage situation on the gathering route input using this function. Is sent to the management server. On the other hand, the management server receives the information representing the damage status on the above gathering route from each electronic terminal and creates the report data of the disaster status by distributing it, and distributes this report data to the related departments in the disaster area. It is a thing.

FIG. 10 is a diagram showing the configuration of the electronic terminal of the disaster action support system according to the third embodiment of the present invention, and FIG. 11 is a diagram used for explaining the configuration of the system and its operation.
The electronic terminals TM1 to TMn include a gathering route registration control function, a disaster situation input control function, and a disaster situation notification control function as functions according to the present invention.

  The gathering route registration control function reads map data including the gathering place determined as the place of residence of the user from the internal memory or the storage medium MC or downloads it from the management server SV3 and displays it on the display screen. In FIG. 5, the gathering route designated by the user's pointer movement operation is recognized. Then, the information of the recognized gathering route is transmitted to the management server SV3. The management server SV3 receives the information representing the user's gathering route sent from the electronic terminals TM1 to TMn and stores it in the database. Information representing this gathering route can be downloaded from the management server SV3 and displayed on the display screen of the electronic terminal in response to a request from the electronic terminals TM1 to TMn.

  The damage status input control function is a function that allows the user to input the damage status including the damage location on the route, the location, and the degree of damage when the user gathers while checking the damage status on the route. It is. The disaster point input means can be realized by a simple interface without displaying a detailed topography or a map by using a kilometer post display or the like if it is a river or a road. For example, as shown in FIG. 10, a river or a road is represented by a single line, and the corresponding kilometer post is scrolled to be selected, or a numerical value may be directly input.

  For information on the details of the damage situation, for example, input methods such as importance, damage location, damage contents, etc., a pull-down menu is displayed and the user can select the appropriate one from this menu, or the user can operate by key operation. A method of inputting as text data is conceivable. The inputted disaster spot can be displayed on a map or displayed in a list by selecting and displaying a confirmation screen.

  The disaster status notification control function transfers information representing the disaster status input by the disaster status input control function to the management server SV3 via the communication network NW or the storage medium MC. In this case, the information to be transferred may be only information indicating the disaster situation, but may be transmitted in a state added to the map information or the like.

  In addition, the electronic terminals TM1 to TMn also have a function of digitizing and transmitting a handwritten memo describing the disaster situation and confirmation information. For example, as shown in step S111 of FIG. 11, a sheet that is color-coded according to the classification of river information, road information, port information, etc. is prepared, and the user writes disaster information or confirmation information on this sheet. Then, the paper is imaged by the digital cameras of the electronic terminals TM1 to TMn, and the captured image data is sent from the electronic terminals TM1 to TMn to the management server SV3 via the communication network NW or the storage medium MC.

  On the other hand, the following processing is performed in the management server SV3. That is, first, in step S112, information representing the disaster situation and image data of handwritten memos are collected from the electronic terminals TM1 to TMn, respectively. The collected information on the disaster situation and the image data of the handwritten memo are stored in the disaster situation database DB6 of the management server SV3 in association with the confirmation date and information on the user (confirmation / registrant).

  Next, in step S113, the information on the disaster situation stored in the disaster situation database DB6 is edited into a report in a predetermined format prescribed by each organization and printed out on a paper medium or the like. At the same time, in step S114, the stored information on the disaster situation is classified by the disaster spot and the disaster part, or the image data of the handwritten memo is classified based on the color of the paper. Then, the information indicating the classified damage situation is distributed to the related organizations in the disaster countermeasure headquarters in charge of the damaged point and the damaged item for each damaged point and the corresponding item.

  In the management server SV3, the information indicating the disaster situation may be posted on a common electronic bulletin board as shown in FIG. In this way, it is possible to share the information indicating the disaster situation among all the departments. In addition, it is also possible to represent a disaster spot by position information (latitude and longitude) acquired by a GPS receiver, and to display the position information on map data.

  As described above, according to the third embodiment, the disaster situation on the route where each user gathers at the gathering location is collected in the management server SV3, and the report data of the disaster situation is created based on this. . For this reason, for example, in the disaster countermeasure headquarters, it is possible to quickly grasp the disaster situation such as the disaster area and its scale before organizing the disaster countermeasure team and sending the investigation personnel.

  In addition, the report data of the disaster status for each disaster area and disaster item is automatically distributed to the disaster countermeasure team or the user who is highly related to the disaster area and the disaster item. For this reason, the disaster countermeasure team or the user can quickly grasp and respond to, for example, the disaster situation in the area that he / she should have jurisdiction over.

(Fourth embodiment)
In the fourth embodiment of the present invention, in the management server, information representing the positions of a plurality of electronic terminals is acquired, and based on the information representing the acquired positions, users existing at the positions are used as gathering locations. The optimum route for moving is calculated. Then, the information representing the calculated optimum route is distributed to the corresponding electronic terminal.

  FIG. 12 is a schematic configuration diagram showing a fourth embodiment of the disaster action support system according to the present invention. In this system, a plurality of electronic terminals TM11, TM12,... Can be connected to the management server SV4 via a private network PNW. Each of the electronic terminals TM11, TM12,... Is provided with position detectors P11, P12,. These position detectors P11, P12,... Use, for example, a GPS (Global Positioning System) receiver. If the private network PNW has a function of managing the positions of the electronic terminals TM11, TM12,..., This position management function can be used instead.

  A meeting place database DB7, a meeting route database DB8, and an action guideline database DB9 are connected to the management server SV4. In the gathering place database DB7, information on the gathering place of the organization is stored. The gathering route database DB8 stores gathering route information including geographical information. The action guideline database DB9 stores information related to action guidelines at business trip destinations, travel destinations, and the like.

  In addition, the management server SV4 includes a gathering route calculation unit RT. The gathering route calculation unit RT obtains the current position information of the electronic terminals TM11, TM12,... And based on the obtained current position information and information stored in the gathering location database DB7 and the gathering route database DB8. , The optimum gathering route of the user who possesses the electronic terminals TM11, TM12,.

Next, the operation of the system configured as described above will be described using the electronic terminal TM11 as an example. FIG. 13 is a sequence diagram showing control procedures and control contents of the management server SV4 and the electronic terminal TM11 in this system.
In step S131, the electronic terminal TM11 detects its current position (latitude and longitude) from the position detector P11. In step S132, in accordance with the user's operation, a distribution request for action guideline information including a meeting route map and a contact method for the nearest meeting place is transmitted to the management server together with the detected current position information.

  On the other hand, first in step S133, the management server SV4 searches the meeting place database DB7 for the nearest meeting place having jurisdiction over the location of the electronic terminal TM11 in response to the distribution request from the electronic terminal TM11. Next, in step S134, an optimum route for traveling from the current location of the electronic terminal TM11 to the searched location is calculated with reference to the information stored in the route database DB8. In step S135, the calculated route map to the meeting place is distributed to the requesting electronic terminal TM11 together with the action guideline information including the contact method read from the action guideline database DB9.

  In step S136, the electronic terminal TM11 receives the gathering route map to the gathering place and the action guideline information distributed from the management server SV4 and stores them in the internal memory or the storage medium MC. When the user performs a display operation in this state, the stored gathering route map and action guide information are read and displayed. Further, when the gathering route map and the action guideline information include audio data and moving image data, the audio data and moving image data are reproduced.

  As described above, according to the fourth embodiment, for example, when a disaster occurs in the department to which a user belongs at a business trip destination or a travel destination, the user can quickly set his / her meeting place and the optimum gathering route. It is possible to accurately and accurately grasp, and thereby it is possible to quickly and reliably gather at an appropriate meeting place. In addition, even after the gathering, it is possible to promptly and accurately perform contact and rescue instructions based on the action guideline information.

(Other embodiments)
The type and configuration of the electronic terminal, the configuration and control procedure and content of the management server, the configuration of the disaster action manual, and the like can be variously modified and implemented without departing from the gist of the present invention.
In short, the present invention is not limited to the above-described embodiments as they are, and can be embodied by modifying the components without departing from the scope of the invention in the implementation stage. Moreover, various inventions can be formed by appropriately combining a plurality of constituent elements disclosed in the above embodiments. For example, some components may be deleted from all the components shown in each embodiment. Furthermore, you may combine suitably the component covering different embodiment.

BRIEF DESCRIPTION OF THE DRAWINGS The schematic block diagram which shows 1st Embodiment of the disaster action support system concerning this invention. The flowchart which shows the initial setting control procedure of the management server used with the action support system at the time of a disaster shown in FIG. 1, and its content. The figure which shows the mode of the information classification of the disaster action manual database used with the disaster action support system shown in FIG. The figure for demonstrating the correlation with the user database and organization database which are used with the disaster action support system shown in FIG. The flowchart which shows the initial setting control procedure of the electronic terminal used in the action support system at the time of a disaster shown in FIG. 1, and its content. The figure for demonstrating the correlation with the user database and disaster action manual database which are used with the disaster action support system shown in FIG. The figure which shows the example of a display of the disaster action manual in the electronic terminal used with the disaster action support system shown in FIG. The figure used for description of the structure and operation | movement of a disaster action support system concerning the 2nd Embodiment of this invention. The figure which shows an example of the headquarters organization rule information used with the system shown in FIG. The figure for demonstrating 3rd Embodiment of the action support system at the time of a disaster concerning this invention. The figure which shows the procedure which reports the information on the disaster situation collected during the gathering and shares information with related departments, and the contents. The schematic block diagram which shows 4th Embodiment of the action support system at the time of a disaster concerning this invention. The flowchart which shows the control procedure of the management server and electronic terminal which are used with the system shown in FIG. 12, and the content.

Explanation of symbols

  SV1 to SV4 ... management server, TM0 to TMn, TM10 to TM12 ... electronic terminal, NW ... communication network, DB1 ... user database, DB2 ... organization database, DB3 ... disaster action manual database, DB4 ... gathering situation database, DB5 ... Headquarters organization database, DB6 ... disaster situation database, MC ... recording medium, SR ... recording medium input / output unit, P11, P12 ... position detection unit, PNW ... private network, RT ... gathering route calculation unit.

Claims (10)

A user database that manages attribute information of multiple users;
An organization database for managing the attribute information of the organization to be managed in association with the attribute information of the user;
A disaster action manual database that stores a disaster action manual created in advance for each of the attribute information of the user, the attribute information of the organization, and information representing the situation of the disaster;
A management server connectable to each of the user database, organization database and disaster action manual database;
A plurality of electronic terminals respectively used by the plurality of users and accessible to the management server;
The management server
In response to a request from the electronic terminal, a means for retrieving the user attribute information and organization attribute information from the user database and organization database,
Based on the information indicating the situation of the disaster, the attribute information of the searched user and the attribute information of the organization, the disaster behavior for each disaster corresponding to the requesting user from the disaster behavior manual database Means for reading the manual,
A disaster action support system comprising: means for delivering the read disaster action manual to the requesting electronic terminal. A gathering situation database for storing disaster countermeasure team organization rule information determined in advance based on the attribute information of the organization,
The management server
Means for collecting information on the gathering status of the plurality of users when a disaster occurs;
Means for creating a disaster response team system communication table composed of the collected users based on the collected status information and the stored disaster response team organization rule information;
The disaster action support system according to claim 1, further comprising means for distributing the created disaster response team system communication table to the electronic terminals used by the gathered users. Each of the plurality of electronic terminals is
Means for accepting input of information representing the disaster situation on the gathering route by the user;
Means for inputting, to the management server, information representing a disaster situation on the input gathering route,
The management server
Means for receiving information representing a disaster situation on the gathering route transmitted from the plurality of electronic terminals;
The disaster action support system according to claim 1, further comprising means for totalizing information indicating the damage status on the received gathering route to create damage status report data. The management server
Means for determining the disaster area based on the information indicating the disaster situation on the received gathering route;
Means for selecting a disaster countermeasure team or a user who is in charge of the determined disaster area, and delivering the created disaster situation report data to an electronic terminal used by the selected disaster countermeasure team or user The disaster action support system according to claim 3, further comprising: The management server
Means for obtaining information representing positions of the plurality of electronic terminals;
Based on the information representing the acquired position, means for calculating an optimum route for the user existing at the position to move to the meeting place;
The disaster action support system according to claim 1, further comprising means for distributing information representing the calculated optimum route to a corresponding electronic terminal. A user database that manages attribute information of a plurality of users, an organization database that manages attribute information of organizations to be managed in association with the attribute information of users, attribute information of users, and attribute information of organizations And can be connected to the disaster action manual database that stores disaster action manuals created in advance for each information indicating the situation of the disaster, and can access the plurality of electronic terminals used by the plurality of users. Management server,
In response to a request from the electronic terminal, a means for retrieving the user attribute information and organization attribute information from the user database and organization database,
Based on the information indicating the situation of the disaster, the attribute information of the searched user and the attribute information of the organization, the disaster behavior for each disaster corresponding to the requesting user from the disaster behavior manual database Means for reading the manual,
Means for delivering the read disaster action manual to the requesting electronic terminal. Means for collecting information on the gathering status of the user in the event of a disaster;
System communication of the disaster response team composed of the gathered users based on the collected information on the gathering status and the disaster countermeasure team organization rule information predetermined based on the attribute information of the organization A means of creating a table;
7. The management server according to claim 6, further comprising means for distributing the created system table of the disaster countermeasure team to the electronic terminals used by the gathered users. Means for collecting, from the plurality of electronic terminals, information representing a disaster situation on the gathering route;
The management server according to claim 6, further comprising means for totalizing information representing the disaster situation on the collected route to create disaster situation report data. Means for determining the disaster area based on the information indicating the disaster situation on the received gathering route;
Means for selecting a disaster countermeasure team or a user who is in charge of the determined disaster area, and delivering the created disaster situation report data to an electronic terminal used by the selected disaster countermeasure team or user The management server according to claim 8, further comprising: Means for obtaining information representing positions of the plurality of electronic terminals;
Based on the information representing the acquired position, means for calculating an optimum route for the user existing at the position to move to the meeting place;
The management server according to claim 6, further comprising means for distributing information representing the calculated optimum route to a corresponding electronic terminal.

Images