JP2016057842A - Disaster countermeasure support system - Google Patents

Abstract

PROBLEM TO BE SOLVED: To provide a disaster countermeasure support system capable of promptly issuing operating instructions against disaster with high reliability.SOLUTION: A disaster countermeasure support system comprises: a disaster countermeasure support server; and at least one portable terminal which can recognize a current position and can be connected to the disaster countermeasure support server through a communication line. The disaster countermeasure support server has: priority determination means which determines the priority of a report with respect to operation instructions when receiving a report of an occurrence of disaster from at least one portable terminal; and a database which stores information on the received report and the priority determined by the priority determination means. The priority determination means decides the priority of the disaster in accordance with reliability weighting coefficient acquisition means which acquires a weighting coefficient varied depending on reliability of a person who reports, and human suffering weighting coefficient acquisition means which acquires the weighting coefficient varied depending on added information on human suffering received together with the report.SELECTED DRAWING: Figure 16b

Description

  The present invention relates to a disaster response support system that supports a response to occurrence of a disaster when a disaster occurs including an artificial disaster such as a fire or an accident or a natural disaster such as an earthquake or a flood.

  As a support device in the event of a disaster, Patent Document 1 describes a support device that supports decision making so that each department of a local government or response organization can quickly and accurately respond to a disaster such as a natural disaster or a sudden accident. ing.

  In this support device, the input of disaster information at the time of a disaster is received, based on the disaster prevention plan rules stored in advance, and the received disaster information and the history information that is the history of decision making actually executed since the disaster occurred. Thus, decision support information is created, decision support information as a candidate for making a decision is output, and an actual decision input by a decision maker is received. When creating this decision support information, the authenticity of the disaster information is determined, and the decision support information is generated according to the determination result.

JP-A-10-334078

  However, according to the support system described in Patent Document 1, for example, when the report of the occurrence of an earthquake is from a citizen, it is determined as uncertain information. For example, if volcanic information is not from a volcano observatory but from citizens, it is judged as incorrect information and it is only displayed as uncertain information, and such notification is used to create decision support information. Is not considered.

  For this reason, there is a possibility of being closest to the disaster at the time of the disaster, and the report of citizens and volunteers with a much larger number of people will not be considered in determining the importance of the disaster, so it is highly reliable and quick It was difficult to determine the occurrence of a disaster.

  Accordingly, it is an object of the present invention to provide a disaster response support system that can quickly and highly reliably provide work instructions for disasters by taking into account reports from citizens or volunteers.

  According to the present invention, a disaster response support system includes a disaster response support server and at least one portable terminal that can recognize the current position and can be connected to the disaster response support server via a communication line. Yes. When the disaster response support server receives a disaster occurrence report from at least one mobile terminal, the priority determination unit that determines the priority of the report regarding the work instruction, and the received report information and the priority determination unit determine And a database for storing the priority information. The priority determination means includes a reliability weighting coefficient acquisition means for obtaining a weighting coefficient according to the reliability determined based on the reporter of the report, and a weighting coefficient according to additional information on the presence or absence of human damage received together with the report. Refers to the human damage weighting coefficient acquisition means for obtaining the secondary disaster weighting coefficient acquisition means for obtaining the weighting coefficient according to the additional information on the possibility of the secondary disaster received together with the report, and the disaster location information received together with the report. And a non-corresponding number of weighting coefficient acquisition means for obtaining a weighting coefficient according to the number of unacknowledged reports received from the occurrence of a disaster, a reliability weighting coefficient acquisition means, a human damage weighting coefficient acquisition means, The disaster priority is determined according to the weighting coefficient acquired by the secondary disaster weighting coefficient acquisition means and the unsupported number of weighting coefficient acquisition means. It has been.

  If the priority of the notification related to the work instruction is determined and the priority information and the notification information are stored in the database of the disaster response support server, the work instruction corresponding to the disaster is issued with reference to the priority. be able to. In particular, in the present invention, a weighting coefficient is obtained according to the reliability determined based on the reporter (higher reliability (for example, 3), lower reliability (for example, 1), and lower reliability). Intermediate (for example, 2), the weighting coefficient is calculated according to additional information on the presence or absence of human damage (very large if there is human damage (for example, 10), small if there is no human damage) (For example, 1), if it is unknown, the weighting coefficient is an intermediate weight (for example, 6). The weighting coefficient is obtained according to the additional information of the possibility of the secondary disaster (if there is a possibility of the secondary disaster, it is large ( For example, 3) If there is no possibility of a secondary disaster, it is small (eg, 1), if it is unknown, the intermediate (eg, 2) weighting coefficient), depending on the number of cases that do not correspond to the report of disaster occurrence Find weighting factor (not supported) If the number of cases is 10 or more, the weighting coefficient is large (for example, 3), small if the number of unsupported cases is 0 to 5 (for example, 1), and if the number of unsupported cases is 6 to 9, the weighting coefficient is intermediate (for example, 2). And priorities of disasters are determined according to the obtained weighting factors. In this way, the weighting coefficient is determined according to the reliability, human damage, the possibility of secondary disaster, and the number of unsupported cases, and the priority of the notification regarding the work instruction is determined according to the determined weighting coefficient. Therefore, it is possible to make an accurate priority determination, and without ignoring reports from citizens or volunteers, the priority of reports regarding work orders is determined taking these into consideration, so work orders for disasters Can be performed quickly and with high reliability.

  In the present specification, the “mobile terminal” refers to a smartphone, a mobile phone, a PDA (personal digital assistant), a portable tablet, a portable personal computer, other small portable computers, a cellular phone, and the like.

  The priority determination unit of the disaster response support server further includes a type determination unit that determines whether or not a predetermined type is included in the additional information indicating the report type received together with the report. The determination result of the type determination unit The disaster priority is preferably determined according to the following. In this case, it is more preferable that the priority determination unit is configured to have a high priority when the type determination unit determines that a predetermined type is included in the notification type. For example, when a predetermined priority type such as “fire damage” or “road damage” is included, it is determined that the priority is high only. For this reason, it is possible to take a very quick response to the notification.

  Whether the reporter is a local government employee, etc., whether the reporter is a citizen, etc., but there are other reports with similar disasters and close to the location where the disaster occurred No, whether the whistleblower is a citizen, etc., but it is a disaster of the same type, and whether there are other reports by local government officials etc. that are close to the location of the disaster, and the whistleblower is a citizen, etc. In addition, it is preferable that the reliability is determined in accordance with whether or not other notifications near the disaster occurrence position are a predetermined number or more.

  In this specification, “local government officials” refers to employees of local governments (local public organizations), other public officials (for example, employees of the National Police Agency, Fire Department, Defense Agency, etc.), or equivalent persons In this case, it is assumed that the person who can correctly determine the occurrence of a disaster is referred to. Furthermore, persons other than “local government staff”, for example, citizens, volunteers, or anonymous persons shall be referred to as “citizens etc.”.

  The at least one portable terminal is configured to transmit a still image and / or a moving image taken with respect to the occurred disaster to the disaster response support server together with the report, and the disaster response support server receives the report information and the received still image. It is also preferable that the image and / or the moving image is stored in a database.

  It is also preferable that the at least one portable terminal is configured to transmit the additional information input by voice input to the disaster response support server together with the report.

  At least one mobile terminal is configured to acquire map information around a disaster occurrence location from a map delivery service site that delivers map information, and display the location of the disaster occurrence on a map based on the acquired map information. It is also preferable.

  The disaster response support server further includes a first local government terminal that is operated by a local government staff or the like, and the priority determination means of the disaster response support server receives a report of the occurrence of a disaster from the first local government terminal. It is also preferable that the priority is determined when the priority is determined and the determined priority is stored in the database.

  A second local government terminal connected to the disaster response support server and operated by a local government staff or the like is further provided. The second local government terminal reports information and priority information stored in the database of the disaster response support server. It is also preferable that the disaster response support server is configured to store the work instruction information related to the disaster transmitted from the second local government terminal in the database.

  The disaster response support server further includes a third local government terminal connected to the disaster response support server and operated by a local government employee or the like. The disaster response support server receives the work instruction information and the priority information stored in the database from the third local government. It is also preferable that the work progress information transmitted to the terminal and indicating the work progress status is received from the third local government terminal and stored in the database.

  A fourth local government terminal connected to the disaster response support server and operated by a local government staff or the like is further provided. The fourth local government terminal is a map around the location of the disaster occurrence from a map distribution service site that distributes map information. Acquire information, acquire report information, priority information, work instruction information and work progress information from the database of the disaster response support server, and on the map based on the acquired map information, the acquired report information, priority information, work instructions It is also preferable to be configured to display information and work progress information.

  The disaster response support server database includes a production database that stores information for providing disaster response support in production and a training database that stores information for providing disaster response support through training. The support server performs processing using information stored in the production database when performing processing in the production mode, and performs processing using information stored in the training database when performing processing in the training mode. It is also preferable to be configured to do so.

  According to the present invention, it is possible to make an accurate priority determination, and without ignoring notifications from citizens or volunteers, the priority of notifications regarding work instructions is determined in consideration of these. Can be quickly and highly reliable.

It is a block diagram which shows roughly the system configuration | structure in one Embodiment of the disaster response support system of this invention. It is a block diagram which shows roughly the structure of the smart phone in the disaster response support system of FIG. It is a flowchart which shows roughly the processing flow by the side of the smart phone by the smart phone application (henceforth an application) of FIG. It is a flowchart which shows roughly the processing flow by the side of the smart phone by the smart phone application of FIG. It is a figure which shows an example of the screen displayed on a display by implementing the notification process flow of FIG. 3a and 3b. It is a figure which shows an example of the screen displayed on a display by implementing the notification process flow of FIG. 3a and 3b. It is a figure which shows an example of the screen displayed on the display at the time of implementing the notification process flow of FIG. 3a and 3b. It is a figure which shows an example of the screen displayed on the display at the time of implementing the notification process flow of FIG. 3a and 3b. It is a figure which shows an example of the screen displayed on a display by implementing the notification process flow of FIG. 3a and 3b. It is a figure which shows an example of the screen displayed on a display by implementing the notification process flow of FIG. 3a and 3b. It is a figure which shows an example of the screen displayed on a display by implementing the notification process flow of FIG. 3a and 3b. It is a flowchart which shows roughly the processing flow by the side of the server by the application of the smart phone of FIG. It is a flowchart which shows roughly the processing flow of the notification (and instruction | indication) Web system by the side of the 1st local government terminal in the disaster response support system of FIG. It is a flowchart which shows roughly the processing flow of the notification (and instruction | indication) Web system by the side of the 1st local government terminal in the disaster response support system of FIG. It is a figure which shows an example of the screen displayed on the display at the time of implementing the notification process flow of FIG. 12a and 12b. It is a figure which shows an example of the screen displayed on the display at the time of implementing the notification process flow of FIG. 12a and 12b. It is a figure which shows an example of the screen displayed on the display at the time of implementing the notification process flow of FIG. 12a and 12b. It is a flowchart which shows roughly the priority determination processing flow of the disaster response support server in the disaster response support system of FIG. It is a flowchart which shows roughly the priority determination processing flow of the disaster response support server in the disaster response support system of FIG. It is a flowchart which shows roughly the processing flow of the instruction | indication Web system by the side of the 2nd local government terminal in the disaster response support system of FIG. It is a figure which shows an example of the screen displayed on the display at the time of implementing the instruction | indication processing flow of FIG. It is a figure which shows an example of the screen displayed on the display at the time of implementing the instruction | indication processing flow of FIG. It is a flowchart which shows roughly the processing flow of the 4th local government terminal side whole condition grasping | ascertainment Web system in the disaster response support system of FIG. It is a figure which shows an example of the screen displayed on a display by implementing the processing flow of the whole condition grasping | ascertainment Web system of FIG. It is a figure which shows an example of the screen displayed on a display by implementing the processing flow of the whole condition grasping | ascertainment Web system of FIG.

  FIG. 1 schematically shows the system configuration of an embodiment of the disaster response support system of the present invention, and FIG. 2 schematically shows the configuration of a smartphone in the disaster response support system of FIG.

  For example, this embodiment is a disaster that responds to a major storm such as a fire, tsunami, flood, typhoon, heavy rain, tornado, landslide, landslide, earthquake, major accident, terrorism, or other major disaster. It relates to a response support system.

  In this embodiment, a smartphone is used as an example of a portable terminal of the disaster response support system. However, a mobile phone, a personal information terminal, a PDA, a portable tablet, a portable personal computer, and other small portable devices can be used instead of the smartphone. A computer, a mobile phone, or the like may be used.

  In FIG. 1, 10 is a citizen (citizen, volunteer or anonymous person) or a local government employee (local government (local public organization) staff, other public servants (for example, staff of the National Police Agency, Fire Department or Defense Agency), Alternatively, a smartphone that is an example of a portable terminal possessed by a person corresponding to this and who can determine whether or not a correct disaster has occurred can be connected to the smartphone 10 via a communication network. A disaster response support server on the cloud, 12 is a map distribution service site (for example, GEOSPACE CDS) that can be connected to the smartphone 10 and the disaster response support server 11 via a communication network, and 13 always transmits GPS satellite radio waves. Multiple GPS satellites, 14 are operated by city hall staff, which is an example of local government staff A first local government terminal that is a notification (and instruction) Web system installed at a city hall, and a second instruction web system that is operated by a city hall staff, which is an example of a local government staff, and that is installed at a city hall. A municipal office terminal, 16 is a third municipal terminal, which is a work Web system installed in the city office operated by a working group of a city office staff, which is an example of a municipal staff, and 17 is a city office staff, which is an example of a municipal staff The fourth local government terminal, which is an overall situation grasping Web system operated by the staff of the countermeasure headquarters and installed in the city hall, is shown. In addition, although the single smart phone 10 is shown by the figure, in the disaster response assistance system of this embodiment, the some smart phone 10 is actually provided.

  The smartphone 10 is preinstalled with a disaster reporting application and is initially set. The smartphone 10 can receive satellite radio waves from a plurality of GPS satellites 13 to recognize the current position, and can acquire the current position and its surrounding map information and address information from the map distribution service site 12. It has become.

  The disaster response support server 11 stores a server main body 11a, a production database (production DB) 11b for storing information for performing disaster response support by actual operation, and information for performing disaster response support by training. A training database (training DB) 11c is provided and installed on the cloud. This disaster response support server 11 is also preinstalled with a disaster reporting application. The disaster response support server 11 is connected to the smartphone 10, the first local government terminal 14, the second local government terminal 15, the third local government terminal 16, and the fourth local government terminal 17 via a communication network, and a map. It is possible to acquire the current position of the smartphone 10 and map information and address information around it from the distribution service site 12.

  When the first local government terminal 14 receives a report of the occurrence of a disaster by telephone, fax, e-mail, or direct visit of citizens or local government staff, the city office staff inputs the report information, and further, instruction information and request It is a general computer device of a desktop type or a notebook type configured to acquire determination information and transmit the information to the disaster response support server 11 via a communication network.

  The second local government terminal 15 receives the priority information and work progress information of the report relating to the work instruction from the disaster response support server 11 via the communication network, and responds to the disaster via the communication network using the instruction information input by the city hall staff. It is a general desktop or notebook computer device configured to transmit to the support server 11.

  The third local government terminal 16 receives the priority information and the work instruction information from the disaster response support server 11 via the communication network, and transmits the response execution response and the work progress information input by the city hall staff of the work team via the communication network. This is a general desktop or notebook computer device configured to transmit to the disaster response support server 11.

  In order for the fourth local government terminal 17 to receive report information, priority information, work instruction information and work progress information from the disaster response support server 11 via the communication network at the countermeasure headquarters, This is a general computer device of a desktop type or a notebook type that displays acquired report information, priority information, work instruction information, and work progress information on a map.

  The smartphone 10 is configured as shown in FIG. 2 on the hardware. That is, a CPU (central processing unit) including a multi-core and a cache, a GPU (graphic processing unit), a memory controller, a peripheral device controller, and a display controller are generally connected to the application processor 10a and the application processor 10a. A DRAM (Dynamic Random Access Memory) 10b constituting the main memory and the application processor 10a are connected to the flash memory 10c storing the operation system (OS) and application programs, and the application processor 10a. A baseband processor 10d, a radio unit 10e connected to the baseband processor 10d, and an antenna 10f connected to the radio unit 10e A power / audio LSI (semiconductor integrated circuit) chip 10g connected to the application processor 10a and the baseband processor 10d, a battery 10h connected to the power / audio LSI chip 10g, and a power / audio LSI chip 10g A speaker 10i connected to the application processor 10a, a touch panel display 10j connected to the application processor 10a, a GPS chip 10k connected to the application processor 10a, and a camera, wireless, etc. connected to the application processor 10a. And a peripheral device 101 including a LAN, Bluetooth (registered trademark) “Bluetooth”, sensors, and the like.

  The CPU provided in the application processor 10a is configured to execute an application program stored in the flash memory 10c according to a basic program such as an OS or a boot program to perform the processing of this embodiment. The CPU is configured to control the operation of the application processor 10a.

  The DRAM 10b is used as a main memory, and is configured to temporarily store programs and data transferred from the flash memory 10c. The DRAM 10b is also used as a work area for temporarily storing various data during program execution. As will be described later, the CPU cache is also used for the same purpose.

  In the smartphone 10 having such a configuration, the application processor 10a first secures a program storage area, a data storage area, and a work area in the DRAM 10b, and loads the program and data from the flash memory 10c. Store in the storage area and data storage area. Next, the following processing flow is executed based on the program stored in the program storage area. Note that the application processor 10a may directly fetch a program and data from the flash memory 10c, and execute the following processing flow based on this program.

  3a and 3b schematically show a processing flow on the smartphone side by the application of the smartphone 10 of FIG. 2, and FIGS. 4, 5, 6, 7, 8, 9 and 10 show this processing flow. An example of a screen displayed on the display 10j of the smartphone 10 when the notification process flow is performed is shown.

  When a disaster occurs and the user (reporter) activates this application to report it (step S1), the application processor 10a displays a login screen on the display 10j (step S2).

  FIG. 4 shows an example of the login screen 40 displayed on the display 10j in this case. On this screen, a user ID input column 41, a password input column 42 for the smartphone 10 and a login for selecting “production mode” used in a disaster or “training mode” used in normal training. A mode selection field 43 and a login button 44 are displayed.

  When the user of the smartphone 10 installs and initializes the disaster report application, the name, address, telephone number, classification of whether the person is a citizen or the like, a user ID and a password are provided. It shall be set. It may be anonymous.

  After entering the user ID and password and selecting the login mode, tapping (depressing) the login button 44 performs authentication and checks whether the selected login mode is available. 5 is displayed (step S3).

  On the main menu screen 50, a photo shooting button 51 for shooting a still image, a video shooting button 52 for shooting a moving image, and a list of notification information that could not be transmitted due to network failure are displayed. Map for use when the user wants to check the transmission list button 53 and the damage situation around the current position or to send an additional image or video to the report information already registered in the disaster response support server 11 An information display button 54 and a password change button 55 are displayed.

  The user (reporter) selects an operation by tapping any button on the main menu screen 50 (step S4). When the photograph shooting button 51 is tapped, a shooting waiting screen 60 shown in FIG. 6A is displayed.

  The camera shutter button 61 is tapped on this screen to take a still image of the disaster site (step S5). If the return button 62 is tapped, the process returns to the main menu screen 50 (FIG. 5) in step S3. When shooting is completed, a shooting completion screen 60 'shown in FIG. 6B is displayed. When the re-shoot button 64 is tapped on this screen, the screen returns to the shooting wait screen 60 shown in FIG. 6A, and another shooting can be performed.

  When the transmission button 63 is tapped on the photographing completion screen 60 ′ shown in FIG. 6B, the additional information selection input screen 70 shown in FIG. 7A is displayed when the reporter is a local government employee or the like. The additional information selection input screen 70 includes a disaster name selection field 71, a secondary disaster possibility selection field 72, a report type selection field 73, a human damage presence / absence selection field 74, and a request determination request presence / absence. Selection field 75, disaster situation voice memo button 76, and OK button 77 are displayed. A reporter who is a local government employee or the like selects and inputs additional information on the additional information selection input screen 70 (step S6). That is, in step S6, the name of the disaster is selected, the possibility of a secondary disaster is selected, the report type is selected, the presence or absence of human damage is selected, and the presence or absence of a request determination request is selected.

  Here, the disaster name is selected by selecting what disaster name the current report is based on, eg, “2014 Typhoon No. 6”. This disaster name can be registered on the Web system side. You may choose disaster names that have not ended. The possibility of secondary disasters is “Yes (residential densely populated area)”, “Yes (neighboring hopping)”, “Yes (having facilities handling gas nearby)”, “Yes (facility handling dangerous goods nearby) Select from “Yes”, “Yes (has facilities handling poisonous and deleterious substances in the vicinity)”, “Yes (others)”, “Unknown”, and “No”. The types of reports are “Building damage”, “Fire damage”, “Road damage”, “Bridge damage”, “River damage”, “Dambling damage”, “Sabo damage”, “Water damage”, “Telephone damage” , “Electricity damage”, “Gas damage”, “Railway damage”, “School damage”, “Hospital damage”, “Cleaning facility damage”, “Port / fishing port damage”, “Ship (port and river) damage”, “ Select from “Ship (sea) damage”, “Other damage”, “Prefectural building damage”, “Volunteer needs”. The selection of presence or absence of human damage is selected from “Yes”, “No”, and “Unknown”. The presence / absence of a request determination request is selected from “present (insufficient staff)”, “present (insufficient technology)”, “present (insufficient goods)”, and “absent”.

  When the transmission button 63 is tapped on the photographing completion screen 60 ′ shown in FIG. 6B, the additional information selection input screen 70 ′ shown in FIG. Is done. This additional information selection / input screen 70 'corresponds to a screen in which the selection column 75 for the presence / absence of a request determination request in the additional information selection / input screen 70 of FIG.

  Next, it is selected whether or not to give a voice memo (step S7). When giving a voice (in the case of YES), the voice memo button 76 is tapped and a memo is recorded by voice (step S8). When the voice memo button 76 is tapped, a recording dialog shown in FIG. 7C is displayed, and a cancel button 78 and a stop button 79 are displayed. If the cancel button 78 is tapped, the voice recording is canceled, and if the stop button 79 is tapped, the voice recording is stopped.

  When the recording of the voice memo is finished and when it is selected that no voice is given in step S7 (in the case of NO), the OK button 77 is tapped.

  When the OK button 77 is tapped, it is determined whether or not the smartphone 10 can be connected to the Internet (step S9). If it can be connected (in the case of YES), satellite radio waves from a plurality of GPS satellites 13 are received. The latest current position information is acquired, and the login mode, the acquired position information, the captured still image information, and the additional information are transmitted to the disaster response support server 11 (step S10). When it is not possible to connect to the Internet (in the case of NO), the latest current position information is acquired by receiving satellite radio waves from a plurality of GPS satellites 13, the acquired position information, captured still image information, and additional information Is stored as untransmitted information in the smartphone 10 (step S11).

  Thereafter, the user logs out and stops the application (step S12).

  On the other hand, when the moving image shooting button 52 is tapped in step S4 for selecting an operation, a moving image shooting waiting screen 80 shown in FIG. 8A is displayed.

  The video button 81 is tapped on this screen, and a moving image of the disaster site is photographed and recorded (step S13). If the return button 82 is tapped, the process returns to the main menu screen 50 (FIG. 5) in step S3. During shooting, a shooting screen 80 'shown in FIG. 8B is displayed. If the stop button 84 is tapped on this screen, the recording is stopped. When the shooting is completed, a shooting completion screen 80 ″ shown in FIG. 8C is displayed. When the reshoot button 85 is tapped on this screen, the screen returns to the video shooting waiting screen 80 shown in FIG. It is possible to shoot again.

  When the transmission button 83 is tapped on the photographing completion screen 80 ″ shown in FIG. 8C, when the reporter is a local government employee or the like, an additional information selection input screen 70 shown in FIG. 7A is displayed. The information selection input screen 70 includes a disaster name selection field 71, a secondary disaster possibility selection field 72, a notification type selection field 73, a human damage presence / absence selection field 74, and a work request for notification. A selection column 75 indicating whether or not there is a request for request determination including a determination as to whether or not to perform a disaster, a voice memo button 76 of a disaster situation, and an OK button 77. A reporter who is a local government employee or the like displays this additional information. Additional information is selected and input on the selection input screen 70 (step S14), that is, in step S14, a disaster name is selected, a possibility of a secondary disaster is selected, a report type is selected, and human damage is Select whether or not to request Select the presence or absence of, and then tap the OK button 77.

  When the transmission button 83 is tapped on the photographing completion screen 80 ″ shown in FIG. 8C, the additional information selection input screen 70 ′ shown in FIG. This additional information selection input screen 70 'corresponds to a screen in which there is no selection column 75 for presence / absence of a request determination request in the additional information selection input screen 70 of FIG.

  In the case of moving image shooting, voice memos cannot be assigned, so when the selection input of additional information is completed and the OK button 77 is tapped in step S14, the process proceeds to step S9, and thereafter the processing as described above is performed.

  If the unsent list display button 53 is tapped in step S4 for selecting an operation, an unsent list screen 90 shown in FIG. 9A is displayed (step S15).

  On this unsent list screen 90, a thumbnail 91 of unsent still images, an unsent video 92, a back button 93, and a confirm button 94 are displayed. Furthermore, the shooting date and time of each still image and moving image is displayed.

  On this unsent list screen 90, the still images 91a and 91b and the moving image 92a to be transmitted to the disaster response support server 11 are selected as shown in the unsent list selection screen 90 'in FIG. When is tapped, the still images 91 a and 91 b and the moving image 92 a are transmitted to the disaster response support server 11. Actually, the process proceeds to step S9, and thereafter, the processing as described above is performed. If the return button 93 is tapped on the unsent list screen 90 or the unsent list selection screen 90 ', the process returns to the main menu screen 50 (FIG. 5) in step S3.

  In step S4 for selecting an operation, if it is desired to confirm the damage situation around the current position or if it is desired to send an additional image or video to the report information already registered in the disaster response support server 11, the map information When the display button 54 is tapped, satellite radio waves from a plurality of GPS satellites 13 are received, and the latest current position information of the smartphone 10 is acquired. Further, the current position and its surrounding map information and addresses from the map distribution service site 12. Information is acquired (step S16).

  Further, report information around the current position is acquired from the disaster response support server 11 and displayed as an icon on the map (step S17).

  Thereby, the electronic map screen 100 shown in FIG. 10A is displayed on the display 10j of the smartphone 10. The electronic map screen 100 further includes a return button 101, a scroll button 102 that is used when the map is scrolled or enlarged / reduced, and a position that is used when information related to icons on the map is displayed in a balloon. A search button 103 and an electronic map / aerial photo switching button 104 are displayed. The acquired current position is displayed at the center of the map, and the report information of the peripheral area 105 is displayed as an icon. FIG. 21b described later shows icons displayed on the map.

  If the return button 101 is tapped on the electronic map screen 100, the screen returns to the main menu screen 50 (FIG. 5) in step S3. When the electronic map / aerial photograph switching button 104 is tapped, an aerial photograph screen 100 ′ shown in FIG. 10B is displayed.

  When an arbitrary icon is tapped on the electronic map screen 100, a balloon 106 indicating notification information related to the icon is displayed on the screen as shown in FIG. 10C (step S18). If the icons overlap, a list is displayed as shown in FIG.

  A report button 106a is displayed in the balloon 106. By tapping the report button 106a, a report method selection dialog as shown in FIG. 10E is displayed. In this dialog, a photo report button 107, a moving image report button 108, and a cancel button 109 are displayed. When the user (reporter) taps one of the buttons, a reporting method is selected (step S19). This reporting process is performed when an additional still image or moving image is registered in the notification information already registered in the disaster response support server 11.

  If a still image has been added to the report information already registered in the disaster response support server 11, the photograph report button 107 in the report method selection dialog is tapped. As a result, as in the case of step S5 described above, the shooting wait screen 60 shown in FIG. 6A is displayed.

  The camera shutter button 61 is tapped on this screen to take a still image of the disaster site (step S20). When shooting is completed, a shooting completion screen 60 'shown in FIG. 6B is displayed. When the re-shoot button 64 is tapped on this screen, the screen returns to the shooting wait screen 60 shown in FIG. 6A, and another shooting can be performed.

  Next, it is selected whether or not to give a voice memo (step 21). When giving a voice (in the case of YES), a voice memo button 76 on the voice memo input screen 70 ″ shown in FIG. 7D is tapped to record a voice memo (step S22). 7C, a recording dialog shown in FIG. 7C is displayed, and a cancel button 78 and a stop button 79 are displayed.Tap the cancel button 78 to cancel voice recording, and tap the stop button 79 to record voice. Stopped.

  When the recording of the voice memo is completed and when it is selected not to add the voice in step S21 (in the case of NO), if the OK button 77 is tapped, the process proceeds to step S9, and thereafter the processing as described above is performed.

  FIG. 11 schematically shows a processing flow on the server side by the smartphone application of FIG. The disaster response support server 11 executes the process shown in FIG.

  First, the report information transmitted from the smartphone 10 via the Internet is received (step S31).

  Next, it is determined whether or not the received report information is a report, that is, whether the report information is a “report” or a “report” for adding information to the report (step S32).

  If it is “notification” (in the case of YES), it is determined whether or not the received notification information includes location information (disaster location information) of the smartphone 10 (step S33). When the position information is included (in the case of YES), the priority of the notification information, which will be described in detail later with reference to FIGS. 16a and 16b, is performed (step S34). When the location information is not included (in the case of NO), the location information of the disaster is set to a fixed coordinate set in advance, for example, the location coordinate of the municipal office of the local government using this disaster response support system (Step S35), the priority determination process of Step S34 is performed.

  Next, it is determined whether or not the login mode is the “main operation mode”, that is, the “main operation mode” or the “training mode” (step S36). When it is in “production mode” (in the case of YES), the report information, position information, and priority are registered in the production DB 11b (step S37), and still images, videos, and voice memos are also linked to this report information. In addition, it is registered in the production DB 11b (step S38). On the other hand, in the case of “training” mode instead of “production mode” (in the case of NO), notification information, position information, and priority are registered in the training DB 11c (step S39), and still images, videos, A voice memo is also associated with this report information and registered in the training DB 11c (step S40).

  In step S32, when the report information is not “report” but “report” (in the case of NO), whether or not the login mode is “production mode”, that is, “production mode” or “training mode”. Is determined (step S41). If it is in “production mode” (in the case of YES), additional report information (follow-up information) is registered in the production DB 11b (step S42), and still images, videos, and voice memos are also linked to this report information. In addition, it is registered in the production DB 11b (step S43). On the other hand, when the “training” mode is selected instead of the “production mode” (in the case of NO), additional report information (follow-up information) is registered in the training DB 11c (step S44), and still images, videos, A voice memo is also associated with this report information and registered in the training DB 11c (step S45).

  If the password change button 55 is tapped in step S4 for selecting an operation, a password change dialog (not shown) is displayed, the password is changed (step S24), and if an OK button (not shown) is tapped, the process returns to the operation selection process in step S4. .

  FIGS. 12a and 12b schematically show the processing flow of the notification (and instruction) Web system on the first local government terminal 14 side in the disaster response support system of FIG. 1, and FIGS. The example of the screen displayed on the display of the 1st local government terminal 14 when implementing a processing flow is shown.

  The process flow shown in FIGS. 12a and 12b is a case where a disaster notification process, an instruction process for responding to the disaster, and a request determination process are performed. As shown in FIG. When only the disaster notification process is performed, the process of steps S57 to S60 is removed, and the process of steps S66 and S68 is a process of registering the report information in the production DB or the training DB.

  First, when the city hall staff activates the browser of this report (and instruction) Web system (step S51), a login screen is displayed on the display of the first local government terminal 14 by the browser (step S52).

  FIG. 13 shows an example of the login screen 130 displayed on the display in this case. On this screen, the user ID input field 131 and password input field 132 of this terminal, and a login mode selection for selecting “working mode” used at the time of disaster or “training mode” used in normal training. A column 133, a login button 134, and a password change button 135 are displayed.

  In addition, the user of this 1st local government terminal 14 shall set that this user is a local government employee etc., a user ID, and a password, when installing and initializing the disaster report application. . When changing the password, the password change button 135 is tapped to perform a predetermined password change procedure.

  After entering the user ID and password and selecting the login mode, tapping the login button 134 performs authentication and checks whether the selected login mode can be used, and then shown in FIG. The main menu screen 140 is displayed (step S53).

  The main menu screen 140 includes a disaster name management button 141 for displaying a disaster name list screen for registering a disaster name used when a new disaster occurs, and a report for displaying a report instruction registration screen. Notification instruction to display or hide the instruction registration (new) button 142a, the correspondence status browsing / registration button 142b for displaying the correspondence status browsing / registration screen, and the correspondence registration (new) button 142c for displaying the correspondence registration (new) screen Corresponding button 142, resident announcement button 143 for displaying the resident announcement list screen, liaison conference / headquarters conference button 144 for displaying the liaison conference list screen, prefecture report button 145 for displaying the prefecture report list screen, and a person requiring assistance Supporter name list button 146 for displaying the list list screen, and disaster / disaster certificate issue button 147 for displaying the disaster / disaster certificate list screen , It is displayed and the map information button 148 to display the map screen in a separate window.

  Next, it is determined whether or not to register a disaster name (step S54). When the city hall staff determines that a new disaster has occurred when they receive a report on the occurrence of a disaster by telephone, fax, e-mail, or direct visit by citizens or local government staff, and tap the disaster name management button 141 (YES ), It is possible to register, modify, delete or view the disaster name and disaster occurrence period in the production DB 11b or the training DB 11c of the disaster response support server 11 (step S55).

  After the disaster name and disaster occurrence period are registered, corrected, deleted or viewed in step S55, or when no disaster name is registered in step S54 (in the case of NO), the disaster response instruction is displayed on the main menu screen 140 of FIG. When the button 142 is tapped and the displayed notification instruction registration (new) button 142a is tapped, a notification instruction registration screen 150 shown in FIG. 15 is displayed.

  On this report instruction registration screen 150, a registration button for checking input contents and registering report information, instruction information, request determination information, and image information in the production DB 11b or the training DB 11c of the disaster response support server 11 151, a disaster name selection field for selecting a disaster name for notification, instruction, and image information (in the initial state, the disaster name registered and corrected in step S55 is displayed) 152, and all input items related to the notification information A clear button 153a for report information to be initialized, a dialog for selecting a report type (fire damage, building damage), and a report type selection field 153b for displaying the name of the selected report type, Select the presence / absence of damage from “Yes”, “None”, “Unknown”, and the selection field 153c for the presence / absence of human damage and the address of the disaster occurrence location. An address selection and input field 153d for selecting a prefecture name, a city name, a town name, and a street name) or a map (designating a position from a map) and inputting a text; and a map thumbnail image field 153e of an occurrence location address; Reporter date / time selection field 153f, reporter name (if anonymous) check field 153g, and reporter classification selection field for selecting whether the reporter is a citizen or local government employee (classification) 153h, input the contents of the report, and if volunteer needs are selected, the report name input field 153i in which the item name is changed to volunteer needs, and the possibility of a secondary disaster is selected, and if necessary, a secondary disaster Select the possibility of secondary disaster and input field 153j for text input of the possibility of disaster, and select the type of disaster awareness such as telephone, fax, email, or direct visit A notification type selection field 153k to perform, a reporter telephone number input field 153l for inputting a reporter telephone number, an instruction information clear button 154a for initializing an input item of instruction information, and an organization name to which an instruction is issued An instruction destination organization selection column 154b for displaying a selection screen in dialog and displaying a selected organization name, an instruction content column 154c for inputting instruction content, and an instruction for adding, modifying and deleting an instruction destination and instruction content And a correction field 154d, an image registration button 155a for designating a file and registering an image file such as a still image and a moving picture associated with the report, and an image registration number display field 155b for displaying the number of registered images The request determination information clear button 156a for initializing the input items of the request determination information and the request determination request for selecting “Yes” or “No” for the request determination request. A non-selection field 156b and a request determination request content input field 156c for inputting the reason for the request determination request and the current state are displayed.

  When the city hall staff makes selections and inputs based on the received notification information on the notification instruction registration screen 150 and taps the registration button 151, these are stored in the production DB 11b or the training DB 11c of the disaster response support server 11. Registration is performed (step S56).

  Next, it is determined whether or not the instruction information is registered (step S57). The city hall staff determines whether or not to give an instruction based on the report information shown on the response status browsing / registration screen 180 shown in FIG. When issuing an instruction, when the city hall staff taps the registration button 151 in the state where the organization name to which the instruction is issued and the instruction content (instruction information) are input on the notification instruction registration screen 150 shown in FIG. (In the case of YES), the instruction information is stored and registered in the production DB 11b or the training DB 11c of the disaster response support server 11 (step S58).

  After registering the instruction information in step S58, or if it is determined not to issue an instruction and the instruction information is not registered in step S57 (in the case of NO), whether or not a work request is made for the notification, etc. It is determined whether or not a request determination including the superior's determination is requested (step S59). The city hall staff determines whether or not to make a request for a request to ask the superior to make a decision based on the notification information shown on the response status browsing / registration screen 180 shown in FIG. When submitting a request determination request, on the notification instruction registration screen 150 shown in FIG. 15, with the presence of the request determination request, the reason for the request determination request and the current state (request determination information) being entered, When the registration button 151 is tapped (in the case of YES), the request determination information is stored and registered in the production DB 11b or the training DB 11c of the disaster response support server 11 (step S60).

  After request registration information is registered in step S60 or when request determination is not requested in step S59 (NO), it is determined whether or not to register an image file at the disaster site (step S61). When registering an image file of a disaster site, the city hall staff presses the image registration button 155a in the state where the image file of the disaster site such as a still image or video exists on the notification instruction registration screen 150 shown in FIG. When tapped (in the case of YES), these image files are stored and registered in the production DB 11b or the training DB 11c of the disaster response support server 11 (step S62).

  After registering the image file in step S62, or when not registering the image file in step S61 (in the case of NO), the notification information priority determination process described in detail later with reference to FIGS. 16a and 16b is performed. Performed (step S63).

  Next, position information corresponding to the “location address” of the disaster in the report information is acquired from the map distribution service site 12 (step S64).

  Next, it is determined whether or not the login mode is “main operation mode”, that is, “main operation mode” or “training mode” (step S65). In the case of “live operation mode” (in the case of YES), report information, instruction information, request determination information, and priority are registered in the live operation DB 11b (step S66). The image information is also associated with these pieces of information and registered in the production DB 11b (step S67). On the other hand, when the mode is not the “production mode” but the “training” mode (in the case of NO), the notification information, the request determination information, and the priority are registered in the training DB 11c (step S68), and further, the disaster site is stopped. Image information such as pictures and videos is also registered in the training DB 11c in association with these information (step S69).

  Thereafter, the user logs out (step S70).

  FIGS. 16a and 16b schematically show the priority determination processing flow of the disaster response support server 11 in the disaster response support system of FIG. Step S34 in FIG. 11 and step S63 in FIG. 12b) will be described.

  First, the “notification type” item registered in the production DB 11b or the training DB 11c of the disaster response support server 11 includes predetermined priority types such as “fire damage” and “road damage”, for example. It is determined whether or not there is (step S71). However, the predetermined type to be prioritized can be changed in the system setting.

  If such a predetermined priority type is included (in the case of YES), the priority is determined as “high” only (step S84), and this determination process is terminated.

  If such a priority type is not included in the “Notification Type” (in the case of NO), weighting by the reliability of the whistleblower, weighting by the presence or absence of human damage, possible secondary disaster Existence of existence ("Yes (residential densely populated area)", "Yes (neighborhood present)", "Yes (neighboring facilities with gas handling)", "Yes (neighboring facilities handling dangerous goods)", "Yes" (We have facilities that handle poisonous and deleterious substances in the vicinity), “Yes (others)” and weighting by the number of unsupported reports (number of report information whose response status is “Notify” and “Instructed”) Done.

  Weighting according to the reporter's reliability is performed as follows. First, it is determined whether or not the reporter is a local government employee or the like, that is, whether or not the reporter is a local government employee or the like (step S72). When the reporter is a local government employee or the like (in the case of YES), it is determined that the reliability is “high” (step S73). If the whistleblower is not a local government employee (in the case of NO), that is, if it is a citizen, volunteer, or anonymous, whether there is a report of the same type of disaster and a position close to this report (within a radius of 100 m) Is determined (step S74). When such a report does not exist (in the case of NO), it is determined that the reliability is “low” (step S75). If there is such a report (in the case of YES), it is determined whether there is a report from a local government employee or the like in addition to the current report (step S76). (If it is the same type of disaster and there is a report at a location close to the current report (within a radius of 100 m), and there is a report from a local government employee, etc. (in the case of YES), the reliability is determined as “high”. (Step S73). When there is no report from a local government employee or the like (in the case of NO), the number of reports from citizens or the like is determined (step S77). (If there is a report of the same type of disaster and a location close to the current report (within a radius of 100 m) and the number of reports from citizens is 10 or more, the reliability is determined as “high”. (Step S73). (If there is a report of the same type of disaster and a location close to the current report (within a radius of 100 m), and the number of reports from citizens, etc. is less than 10, the reliability is determined as “medium”. (Step S78). The radius threshold and the number of notifications described above can be changed in the system settings.

  Next, branching is performed according to the reliability determined in this way (step S79), and a weighting coefficient is obtained. When the reliability is “high”, the weighting coefficient is set to “3”, when the reliability is “medium”, the weighting coefficient is set to “2”, and when the reliability is “low”, the weighting coefficient is “1”. Set to This weighting coefficient can be changed in the system settings.

  Weighting according to the presence or absence of human damage is performed as follows. Branches according to the presence or absence of human damage (step S80), and a weighting coefficient is obtained. The weighting factor is set to “10” for human damage “Yes”, the weighting factor is set to “6” for human damage “Unknown”, and the weighting factor is set to “No” for human damage. Set to “1”. This weighting coefficient can be changed in the system settings.

  Weighting according to the possibility of a secondary disaster is performed as follows. Branches according to the possibility of a secondary disaster (step S81), and a weighting coefficient is obtained. When the possibility of secondary disaster is “Yes”, the weighting factor is set to “3”, and when the probability of secondary disaster is “Unknown”, the weighting factor is set to “2”, and the possibility of secondary disaster In the case of “None”, the weighting coefficient is set to “1”. This weighting coefficient can be changed in the system settings.

  Weighting by the number of unsupported reports is performed as follows. The process branches according to the number of unsupported reports (step S82), and a weighting coefficient is obtained. When the number of unsupported reports is “10”, the weighting coefficient is set to “3”. When the number of unsupported reports is “6 to 9”, the weighting coefficient is set to “2”. When the number of reports is “0-5”, the weighting coefficient is set to “1”. The above-described weighting coefficient and the threshold for the number of unsupported notifications can be changed in the system settings.

  After obtaining the weighting coefficients as described above, the sum of the weighting coefficients is calculated, and the process branches according to the comparison between the sum and the threshold value (step S83), and the priority is determined. That is, when the calculated sum of the weighting coefficients is “10 to 19”, the priority is determined as “high” (step S84), and when the calculated sum of the weighting coefficients is “7 to 9”, the priority “ When the sum of the calculated weighting coefficients is “4-6”, the priority is determined as “low” (step S86), and the priority determination process is terminated. Note that the above-described priority threshold value can be changed in the system settings.

  FIG. 17 schematically shows a processing flow of the instruction Web system on the second local government terminal 15 side in the disaster response support system of FIG. 13, FIG. 14, FIG. 18 and FIG. 19 show an example of a screen displayed on the display of the second local government terminal 15 when this instruction processing flow is executed.

  Note that the processing flow shown in FIG. 17 is modification of the instruction information, which is shown in FIG. 15 in order to register the instruction information regarding the notifications already registered in the processing flow of FIGS. 12a and 12b. The instruction information is corrected not on the notification instruction registration screen 150 but on the instruction correction screen 190 shown in FIG.

  First, when the city hall staff activates the browser of this instruction Web system (step S91), a login screen shown in FIG. 13 is displayed on the display of the second local government terminal 15 by the browser (step S92). After entering the user ID and password and selecting the login mode, tapping the login button 134 performs authentication and checks whether the selected login mode can be used, and then shown in FIG. The main menu screen 140 is displayed (step S93).

  The operations in the login process (step S92) and the menu display process (step S93) are the same as those in FIG.

  On the main menu screen 140 shown in FIG. 14, when the city hall employee taps the response status browsing / registration button 142b, the response status browsing / registration screen 180 shown in FIG. 18 showing a list of reports is displayed (step S94). .

  On the response status browsing / registration screen 180, a list area 181a and a tree screen 181b are displayed for all information related to disaster names. On the tree screen 181b, various buttons including the “hier organization button” and the “other organization button” in the upper hierarchy are hierarchically displayed. The “own organization button” is used to display all information instructed to the logged-in user's organization related to the disaster name in the list area 181a. You can check the instructions sent to the organization. In addition, for example, a “notification button” for displaying all information whose response status related to the disaster name is “report” in the list area 181a, and all information whose response status related to the disaster name is “instructed” is displayed in the list area 181a. “Instructed button” for displaying in the list area, “Working button” for displaying all information in which the response status regarding the disaster name is “working” in the list area 181a, and the response status regarding the disaster name is “work completed” A “work completion button” for displaying all the information in the list area 181a, a “completion button” for displaying all information in which the response state related to the disaster name is “complete” in the list area 181a, etc. are displayed. . On the response status browsing / registration screen 180, a search condition display button 182a for switching display / non-display of the search condition area 182 and a disaster name selection field 182b for selecting a disaster name to be searched are displayed. The By designating search conditions in this search condition area 182, a desired report can be searched. The list of reports is displayed in different colors according to the corresponding status of “Notification”, “Instructed”, “Work in progress”, “Work completed” and “Completed” so that the status can be understood at a glance. Has been made.

  In the displayed search condition area 182, a notification type selection screen is popped up by tapping an icon, a notification type selection and display field 182 c for selecting and displaying a notification type (fire damage, building damage, etc.), and an icon Tap to pop up the accepted organization selection screen, select the accepted organization selection and display field 182d to specify and display the organization that received the report, and tap the icon to pop up the corresponding organization selection screen. Corresponding organization selection and display column 182e for designating and displaying an organization, correspondence status selection column 182f for selecting a correspondence status to be searched (report, instructed, working, completed, completed, etc.), and tap an icon By popping up the screen to specify the address of the disaster location by selecting, address selection and display column to select and display the address 82g, command table case classification selection field 182h for selecting the report information case classification (firefighting normal, earthquake and flood damage, hold, city hall department) acquired from the command base linkage function to be searched, and the report to be searched The notification period designation field 182i for designating the start date and time and the end date and time, the search button 182j for executing the search with the search item and displaying the list, and the input value of the search item in the initial display state And a clear button 182k for display.

  In the list area 181a of the correspondence status browsing / registration screen 180, a file dialog installed in the browser is displayed, a file output icon 183a for outputting an Excel file, and a report for displaying a report instruction corresponding detail screen. ID column 183b and report type / damage type display column for displaying the report type / report type of the report information / the damage type of the response information (if the response status is reported or instructed, search from the report type and working In the case of work completion or completion, search from the report type and damage type and display the result), the disaster name display column that displays the disaster name of the corresponding report information, and the latest update of the report instruction information or response information An update date / time display field for displaying the date / time, a report date / time display field for displaying the report date / time of the report information, a human damage display field for displaying the presence / absence of human damage in the report information, A priority display field for displaying the calculated priority of the report information, a disaster place display field for displaying the address where the report information occurred, a reception organization name display field for displaying the organization to which the user who registered the report information belongs Corresponding organization name display field for displaying the instruction destination of the instruction information, response status display field for determining and displaying the organization and status (notifying, instructed, working, completed or completed) for the notification information, and request determination Displayed is a request determination display field for displaying the status (request request not possible, request request is being requested, request requested), and a corresponding registration button 183c for displaying a corresponding registration screen 185 for registering contents corresponding to the instruction. Is done.

  When the city hall staff taps the report ID column 183b of the report to be displayed in the list area 181a of the response status browsing / registration screen 180, the report instruction response detail screen 184 is displayed (step S95). On the report instruction response detail screen 184, the report content, instruction content, request determination request content, and response implementation content can be confirmed. In addition, escalation (judgment request, approval, return) to superiors is possible.

  When the already-registered report information or the like is corrected, the city hall staff taps an instruction correction button (not shown) on the report instruction corresponding detail screen 184 to display the instruction correction screen 190 shown in FIG. .

  The instruction correction screen 190 includes a registration button 191 for registering the input contents of this screen in the production DB 11b or the training DB 11c of the disaster response support server 11, and a disaster name button 192 for displaying a disaster name related to the corresponding information. And the instruction information clear button 193a for initializing the input items to the initial screen display state, and the organization selection screen is popped up by tapping the icon, and the corresponding organization selection is specified and displayed. And the display field 193b, the instruction content field 193c for inputting the instruction content to the organization, the instruction addition button 193d for adding the instruction destination / instruction content being input to the list, and the organization selected on the organization selection screen Instruction destination display field 193e for displaying information, instruction content input field 193f for registering instruction contents to the organization, and corresponding contents added to the list A copy button 193g for displaying a copy of the information in the input field, a correction button 193h for displaying the corresponding content information added to the list in the input field, a delete button 193i for deleting the instruction destination and instruction content of the corresponding line, and this screen A registration button 193j for registering the input content of the system in the production DB 11b or the training DB 11c of the disaster response support server 11 is displayed.

  The staff of the city hall corrects the organization that issues the instruction, the instruction content (instruction information) on this instruction correction screen 190, and taps the registration button 191, so that the corrected instruction information is put into the production DB 11b of the disaster response support server 11. Alternatively, it is registered in the training DB 11c (step S96). Here, it is determined whether or not the login mode is “main operation mode”, that is, “main operation mode” or “training mode” (step S97). ), When it is in “production mode” (in the case of YES), the corrected instruction information is registered in the production DB 11b (step S98). On the other hand, if the “training” mode is selected instead of the “full operation mode” (NO), the corrected instruction information is registered in the training DB 11c (step S99).

  Thereafter, the user is logged out (step S100), and the instruction Web system process is terminated.

  On the other hand, the staff of the city hall of the working group displays the response status browsing / registration screen 180 shown in FIG. 18, for example, stored in the production DB 11b of the disaster response support server 11 in the third municipality terminal 16 shown in FIG. By displaying and tapping the own organization button, the report information including the priority information and the work instruction information addressed to the own organization can be acquired and the work can be performed. Furthermore, by transmitting the response execution response and the work progress information regarding the work instruction to the disaster response support server 11, it can be stored and registered in the production DB 11b.

  FIG. 20 schematically shows a processing flow of the overall situation grasping Web system on the fourth municipality terminal 17 side in the disaster response support system of FIG. 21a and 21b show an example of a screen displayed on the display of the fourth local government terminal 17 when this processing flow is executed.

  For example, in the disaster countermeasure headquarters provided at the city hall, the fourth local government terminal 17 receives notification information including priority information, work instruction information, and work progress information from the disaster response support server 11 and grasps the overall situation. Is provided to do.

  First, when the city hall staff activates the browser of the overall grasp Web system (step S101), the login screen shown in FIG. 13 is displayed on the display of the fourth local government terminal 17 by the browser (step S102). After entering the user ID and password and selecting the login mode, tapping the login button 134 performs authentication and checks whether the selected login mode can be used, and then shown in FIG. The main menu screen 140 is displayed (step S103).

  The operations in the login process (step S102) and the menu display process (step S103) are the same as those in FIG. 12a and FIG.

  When the city hall staff taps the map information button 148 on the main menu screen 140 shown in FIG. 14, a map is displayed on a separate screen (step S104), and map information is acquired (step S105) on this map. By displaying, the map screen 210 shown in FIG. 21a is displayed.

  The map screen 210 includes a disaster name display field 211 for displaying a disaster name related to the icon displayed on the map, and a period from the disaster occurrence date to the disaster end date of the disaster name selected on the disaster name selection screen. An information acquisition period display field 212 to be displayed, an update button 213 for updating to the latest information for displaying the target information (icon) on the map on the date specified in the information acquisition period, and an update interval time for updating the map information An update interval selection field 214 for selecting (1 minute, 10 minutes, 30 minutes, 60 minutes), an address search button 215 for displaying an address search panel, and information on icons in the range by specifying a range of icons. When searching for a list, an area search button 216 for setting an area search mode on the map, an aerial photo / electronic map switching button 217 for switching the map between an aerial photo and an electronic map, A close button 218 for closing the FIG screen 210, an icon display switching section 219 is displayed.

  In the icon display switching field 219, whether or not to display an icon of report request information, whether or not to display a report icon of a different color in the report request information (only report, instructed), and different report request information. Whether to display the color human damage icon (working, work completed, completed), whether to display the building damage icon (working, work completed, completed) of different colors in the report request information Whether to display a civil engineering damage icon (working, work completed, completed) in different colors in the request information or a fire damage icon (working, work completed, completed) in different colors in the report request information No, whether to display lifeline damage icons (different from work, work completed, completed) in different colors of report request information, other damage icons of different colors in report request information During operation, the work completed, whether or not to display the complete), in different colors of a plurality damage icons (work report request information, task completion, switches whether to display the complete) is.

  The icon displayed on the map screen 210 is a response status (progress status) corresponding to the report as shown in FIG. 21b, and the display color is changed depending on the report, instructed, working, completed, and completed. Each display color is shaded according to the priority.

  Furthermore, the number of unsupported reports for each town is represented by a circle area of a different color. For example, in a circle area 220 represented by a blue fill, if the number of unsupported reports in that town is 1 to 5, for example, a circle area 221 represented by a yellow fill has 6 to 9 unsupported reports in that town. In the case of a case, for example, a circular area 222 represented by a red fill indicates a case where the number of unsupported notifications in the town is 10 cases. When the number of unsupported reports in the town is 0, it is represented by a circle area without coloring. By looking at the map screen 210, it is possible to grasp at a glance the end state of damage, and it is possible to easily and instantly grasp which town the resources should be concentrated on. The color and the number of unsupported notifications described above can be changed in the system settings.

  Next, it is determined whether or not the login mode is “main operation mode”, that is, “main operation mode” or “training mode” (step S106). If it is in “production mode” (in the case of YES), the location of the report information registered in the production DB 11b is mapped and displayed on the map (step S107). On the other hand, when the “training” mode is selected instead of the “production mode” (in the case of NO), the position of the report information registered in the training DB 11c is mapped and displayed on the map (step S108). The city hall staff and the disaster countermeasure headquarters staff can easily grasp the overall situation regarding the disaster by looking at the map screen 210.

  Thereafter, the user logs out (step S109), and the overall grasp Web system process is terminated.

  As described above in detail, according to the present embodiment, the weighting coefficient is obtained according to the reliability determined based on the reporter (higher reliability (for example, 3), lower reliability) (for example, lower). 1) If the reliability is intermediate, the intermediate (for example, 2) weighting coefficient is used, and the weighting coefficient is obtained according to the additional information on the presence or absence of human damage (if there is human damage, it is very large (for example, 10) If there is no human damage, the weighting coefficient is small (eg, 1), and if it is unknown, the weighting coefficient is intermediate (eg, 6). The weighting coefficient is obtained according to additional information on the possibility of secondary disaster (2 If there is a possibility of the next disaster (for example, 3), if there is no possibility of the second disaster (for example, 1), if it is unknown, use the intermediate weight (for example, 2). Depending on the number of unsupported cases The weighting coefficient is determined (large if the number of unsupported cases is 10 or more (for example, 3), small if the number of unsupported cases is 0 to 5 (for example, 1), or if the number of unsupported cases is 6 to 9). In the middle (for example, 2), the disaster priority is determined according to the obtained weighting factors. In this way, the weighting coefficient is determined according to the reliability, human damage, the possibility of secondary disaster, and the number of unsupported cases, and the priority of the notification regarding the work instruction is determined according to the determined weighting coefficient. Therefore, it is possible to make an accurate priority determination, and without ignoring reports from citizens or volunteers, the priority of reports regarding work orders is determined taking these into consideration, so work orders for disasters Can be performed quickly and with high reliability. In addition, since it is configured to have a high priority when it is determined that the priority type such as “fire damage”, “road damage”, etc. is included in the notification type, Can respond very quickly.

  All the embodiments described above are illustrative of the present invention and are not intended to be limiting, and the present invention can be implemented in other various modifications and changes. Therefore, the scope of the present invention is defined only by the claims and their equivalents.

10 Smartphone 10a Application processor 10b DRAM
10c Flash memory 10d Baseband processor 10e Radio unit 10f Antenna 10g Power supply / audio LSI chip 10h Battery 10i Speaker 10j Touch panel display 10k GPS chip 10l Peripheral device 11 Disaster response support server 11a Server body 11b Production DB
11c Training DB
12 Map distribution service site 13 GPS satellite 14 1st local government terminal 15 2nd local government terminal 16 3rd local government terminal 17 4th local government terminal 40, 130 Login screen 41, 131 ID input field 42, 132 Password input field 43 133 Login mode selection field 44, 134 Login button 50 Main menu screen 51 Photo shooting button 52 Movie shooting button 53 Unsent list button 54 Map information display button 55, 135 Password change button 60 Waiting for shooting screen 60 'Shooting completion screen 61 Camera Shutter button 62, 82, 93, 101 Return button 63, 83 Send button 70, 70 'Additional information selection input screen 71 Disaster name selection field 72 Secondary disaster possibility selection field 73, 153b Notification type selection field 74, 153c Human damage Selection field 75 Selection field for request judgment request 76 Voice memo button 77 OK button 78 Cancel button 79, 84 Stop button 80 Movie shooting standby screen 80 'Shooting screen 80 "Shooting completion screen 81 Video button 85 Reshoot button 90 Not yet Transmission list screen 90 ′ Unsent list selection screen 91 Thumbnail of unsent still image 92 Unsent movie 94 Confirm button 91a, 91b Still image 92a Movie 94 Confirm button 100 Electronic map screen 102 Scroll button 103 Location search button 104 Electronic map / aviation Photo switch button 105 Peripheral area 106 Balloon 106a Report button 107 Photo report button 108 Movie report button 109 Cancel button 140 Main menu screen 141 Disaster name management button 142 Report instruction response button 142a Report instruction registration (new) button 142b Correspondence status browsing / registration button 142c Correspondence registration (new) button 143 Resident announcement button 144 Liaison conference / headquarters conference button 145 Prefectural report button 146 Supporter list button 147 Issuance of disaster / disaster certificate Button 148 Map information button 150 Report instruction registration screen 151, 191 Registration button 152 Disaster name selection field 153a, 154a, 156a, 182k Clear button 153b Report type selection field 153d Address selection and input field 153e Map thumbnail image field 153f Report date / time selection field 153g Reporter name input field 153h Reporter classification selection field 153i Report content input field 153j Secondary disaster possibility selection and input field 153k Awareness type selection field 153l Caller telephone number input field 154b Pointee organization selection field 154 Instruction content field 154d Instruction addition / modification field 155a Image registration button 155b Image registration number display field 156b Request judgment request presence / absence selection field 156c Request judgment request content input field 180 Correspondence status browsing / registration screen 181a List area 181b Tree screen 182 Search conditions Area 182a Search condition display button 182b Disaster name selection column 182c Report type selection and display column 182d Accepted organization selection and display column 182e Corresponding organization selection and display column 182f Corresponding situation selection column 182g Address selection and display column 182h Command stand case classification selection column 182i Report period designation field 182j Search button 183a File output icon 183b Report ID field 183c Correspondence registration button 184 Report instruction correspondence detail screen 185 Correspondence registration screen 190 Instruction correction screen 192 Disaster name button 193a Instruction information clear button 193b Corresponding organization selection and display field 193c Instruction contents field 193d Instruction addition button 193e Instruction destination display field 193f Instruction contents input field 193g Copy button 193h Modify button 193i Delete button 193j Registration button 210 Map screen 211 Disaster name display Field 212 Information acquisition period display field 213 Update button 214 Update interval selection field 215 Address search button 216 Area search button 217 Satellite / electronic map switching button 218 Close button 219 Icon display switching field 220, 221, 222 Circle area

Claims (12)

A disaster response support server, and at least one portable terminal capable of recognizing a current position and connected to the disaster response support server via a communication line;
The disaster response support server, when receiving a disaster occurrence report from the at least one portable terminal, priority determination means for determining a priority of a report regarding a work instruction, the received report information and the priority A database for storing information on the priority determined by the determination means,
The priority determination means is weighted according to the reliability weighting coefficient acquisition means for obtaining a weighting coefficient according to the reliability determined based on the reporter of the report, and additional information on the presence or absence of human damage received together with the report. Human damage weighting coefficient acquisition means for obtaining a coefficient, secondary disaster weighting coefficient acquisition means for obtaining a weighting coefficient according to additional information on the possibility of a secondary disaster received together with the report, and the position of the disaster received together with the report An unsupported number of weighting coefficient acquisition means for obtaining a weighting coefficient according to the number of cases in which a report of occurrence of a disaster has been received with reference to information, and the reliability weighting coefficient acquisition means, the human damage According to the weighting coefficient acquired by the weighting coefficient acquisition means, the secondary disaster weighting coefficient acquisition means, and the unsupported number of weighting coefficient acquisition means Disaster support system, characterized by being configured to determine the priority of harm.   The priority determination means of the disaster response support server further includes type determination means for determining whether or not a predetermined type is included in the additional information indicating the report type received together with the report. The disaster response support system according to claim 1, wherein the disaster priority is determined according to a determination result of the means.   The said priority determination means is comprised so that it may be set as a high priority, when the said classification discrimination means discriminate | determines that the predetermined classification is contained in the said report classification. Disaster response support system.   The reliability weighting coefficient acquisition means of the priority determination means determines whether or not the reporter is a local government employee or the like, or other report that is a disaster of the same type but close to the disaster occurrence position. The reporter is a citizen, etc., but it is a disaster of the same type, and whether there is another report by a local government employee, etc. who is near the location of the disaster, and the reporter is a citizen, etc. Any one of claims 1 to 3, wherein the reliability is determined according to whether or not other notifications having the same disaster occurrence position are more than a predetermined number. The disaster response support system according to claim 1.   The at least one mobile terminal is configured to transmit a still image and / or a moving image taken with respect to the disaster that has occurred to the disaster response support server together with the notification, and the disaster response support server 5. The disaster response support system according to claim 1, wherein the information and the received still image and / or moving image are stored in the database. 6.   The said at least 1 portable terminal is comprised so that the said additional information input by audio | voice input may be transmitted to the said disaster response support server with the said report, The any one of Claim 1 to 5 characterized by the above-mentioned. Disaster response support system according to item.   The at least one mobile terminal acquires map information around the location of the disaster occurrence from a map distribution service site that distributes map information, and displays the location of the disaster occurrence on a map based on the acquired map information The disaster response support system according to any one of claims 1 to 6, wherein the disaster response support system is configured.   A first local government terminal connected to the disaster response support server and operated by a local government staff or the like is further provided, and the priority determination means of the disaster response support server detects a disaster occurrence from the first local government terminal. The disaster response support according to any one of claims 1 to 7, wherein when receiving a report, the priority is determined, and the determined priority is stored in the database. system.   A second local government terminal connected to the disaster response support server and operated by a local government staff, etc., wherein the second local government terminal includes notification information stored in the database of the disaster response support server; It is configured to display a list of priority information, and the disaster response support server is configured to store work instruction information related to a disaster transmitted from the second local government terminal in the database. The disaster response support system according to any one of claims 1 to 8, wherein   The disaster response support server further includes a third local government terminal connected to the disaster response support server and operated by a local government staff, etc., and the disaster response support server stores the work instruction information and priority information stored in the database. The work progress information transmitted to a third local government terminal and indicating work progress status is received from the third local government terminal and stored in the database. Disaster response support system.   A fourth local government terminal connected to the disaster response support server and operated by a local government staff or the like is further provided, and the fourth local government terminal receives a location of the disaster from a map distribution service site that distributes map information. Acquire surrounding map information, acquire report information, priority information, work instruction information and work progress information from the database of the disaster response support server, and the acquired report information on a map based on the acquired map information The disaster response support system according to claim 10, configured to display priority information, work instruction information, and work progress information.   The database of the disaster response support server includes a production database that stores information for performing disaster response support by actual operation, and a training database that stores information for performing disaster response support by training, The disaster response support server performs processing using information stored in the production database when processing in the production mode, and information stored in the training database when processing in the training mode. The disaster response support system according to any one of claims 1 to 11, wherein the system is configured to perform processing by using a computer.