Disaster response performance management system, disaster response performance management method and program

Abstract

This system provides a disaster response performance management system that can prevent omissions in the completion of response tasks, even if the person responsible for the disaster prevention plan is unresponsive or fails to perform their duties. [Solution] The management server 10 acquires weather information, local government warnings, rainfall sensors 23, water level sensors 24, landslide sensors 25, location information 70, and work information 71, and determines the recipients of notifications and the order of notifications based on the types of corresponding tasks, issuance conditions, responsible person ranking, alternative responsible person candidates, and performance evidence 90 stored in the planning information database 50. The notification control unit 14 sends a notification 80, a re-notification 81, or an escalation notification 82, and the record management unit 15 records the performance evidence 90 and audit logs and outputs a plan deviation alert 83.

Description

Technical Field

[0001] The present invention relates to a disaster response execution management system, a disaster response execution management method, and a program for managing the execution of response tasks based on a disaster prevention plan when a disaster occurs or there is a risk of a disaster. In particular, weather information provided by the Japan Meteorological Agency, local government warnings, rainfall, water levels, sensor information related to landslide disasters, position information of operator terminals, work information, authority information, and danger area information, as well as responses and execution traces obtained from notification targets, types of execution traces associated with response tasks, and based on a predetermined time, control notification targets, notification order, re-notification, escalation, and selection of alternate responsible persons, and further collate the actual notification order, issuance conditions, notification times, and execution trace conditions with the plan information to output a deviation type including at least condition deviation, timing deviation, and execution determination deviation, thereby recording and managing the execution status of response tasks and plan deviations.

Background Art

[0002] In recent years, in local governments, companies, schools, hospitals, and other organizations, it has been common to pre-determine response tasks, issuance conditions, responsible persons, alternate responsible persons, contact order, etc. for each type of disaster in a disaster prevention plan or business continuity plan.

[0003] On the other hand, for typhoons, heavy rain, floods, landslide disasters, etc., technologies have been proposed to notify on-site operators or administrators based on weather information, local government warnings, rainfall, river water levels, and various information related to landslide disasters provided by the Japan Meteorological Agency and others. For example, Patent Document 1 discloses a technology for calculating weather information based on observation data obtained from an observation device and notifying a target person's mobile terminal or the like. Patent Document 2 also discloses a technology for issuing a notification when a reference is exceeded based on rainfall information and river water level information, and notifying the operator of the acquisition status of confirmation notifications from related organizations.

[0004] Furthermore, technologies have been proposed for individually distributing risk information or emergency information based on location information, attribute information, or job title information. For example, Patent Document 3 discloses a technology that uses location information and notification history information to distribute risk information and support safety confirmation. Patent Document 4 also discloses a technology that transmits personalized emergency instructions to each individual's mobile terminal based on job title, experience, location, etc.

[0005] Furthermore, regarding urgent messages, technologies have been proposed that resend them using multiple communication methods until an acknowledgment is received, and if no response is received within a predetermined time, escalate the message to other recipients or other communication channels. For example, Patent Document 5 discloses a technology that escalates an urgent message, including transmissions to multiple devices, multiple media, sequentially or simultaneously, until acknowledgment or approval is received.

[0006] However, the above-mentioned conventional technology is primarily intended for the notification, confirmation of receipt, or confirmation of safety of hazard information or warning information. It does not manage the issuance conditions, response tasks, priority of responsible persons, alternative responsible persons candidates, types of performance evidence, and prescribed time as a whole, as defined in the disaster prevention plan. Based on continuously updated weather information, local government warnings, rainfall, water levels, sensor information related to landslides, location information, work information, authority information, and hazardous area information, as well as the acquired responses and performance evidence, the types of performance evidence associated with response tasks, and prescribed time, it determines the recipients of notifications, the order of notifications, whether or not performance has not been fulfilled, and the alternative responsible persons. Furthermore, it does not compare the actual order of notifications, issuance conditions, notification times, and performance evidence conditions with the plan information to output deviation types, including deviations from conditions, deviations from timing, or deviations from performance judgment.

[0007] Furthermore, conventional technologies still have room for improvement in managing the status of disaster prevention plan implementation chronologically by using performance evidence for each task to determine whether it can actually be performed, and then issuing further notifications or escalating the issue based on the result of that determination, as well as generating audit logs including performance records, reasons for switching to an alternative person in charge, and plan deviation alerts. [Prior art documents] [Patent Documents]

[0008] [Patent Document 1] Japanese Patent Publication No. 2016-080552 [Patent Document 2] Patent No. 6612523 [Patent Document 3] International Publication No. 2016 / 121828 [Patent Document 4] International Publication No. 2018 / 175447 [Patent Document 5] International Publication No. 2014 / 110279 [Overview of the project] [Problems that the invention aims to solve]

[0009] Patent Document 1 discloses a weather information notification system in which a server calculates weather information based on observation data from observation devices installed at multiple observation points, and notifies specific individuals of weather information or warnings on their mobile terminals, smartphones, etc., as needed. In other words, Patent Document 1 is characterized by its ability to individually notify specific individuals of weather events such as localized heavy rain, heavy snow, strong winds, and exceeding standard values ​​for wind speed or rainfall. On the other hand, Patent Document 1 focuses primarily on the notification of weather information itself, and does not manage the correspondence between the response tasks, priority of responsible persons, alternative responsible persons candidates, and types of evidence of performance that are predetermined in the disaster prevention plan, nor does it determine whether the actual performance can be carried out after notification. Therefore, with Patent Document 1, it is difficult to comprehensively manage whether the person in charge actually carried out the planned response after receiving the notification, or who to switch to if the response is not carried out.

[0010] Patent Document 2 discloses a flood warning system that acquires water level information from the Ministry of Land, Infrastructure, Transport and Tourism's Unified River Information System and rainfall information from the Japan Meteorological Agency's ADES system, and notifies river managers of the status of acquisition of confirmation notices indicating that relevant organizations have reviewed the forecast document. In other words, Patent Document 2 is characterized by notifications of exceeding criteria based on rainfall and water level information, and notifications of the status of acquisition of confirmation notices from relevant organizations, and aims to reduce the effort required for river managers to confirm the response status. However, Patent Document 2 only notifies the status of acquisition of confirmation notices for the forecast document, and does not determine non-performance based on performance evidence indicating that individual tasks in the disaster prevention plan have been performed. Furthermore, it does not disclose a configuration for automatically selecting an alternative person in charge based on location information, work information, authority information, or hazardous area information in the event of non-performance.

[0011] Patent Document 3 discloses a risk information distribution device that uses itinerary information, risk information, location information, and notification history information to distribute risk information corresponding to a traveler's current location and future plans, and to support administrators in confirming the safety of travelers. Specifically, Patent Document 3 is characterized by matching location information with risk information, distributing risk information to the necessary recipients, and maintaining an alert distribution history using a notification history information database. However, Patent Document 3 focuses on distributing risk information to travelers and confirming their safety, and does not manage the performance of response tasks using the order of responsible persons, alternative responsible persons candidates, issuance conditions, or types of performance evidence in the organization's disaster prevention plan. Therefore, while Patent Document 3 can confirm safety or distribute information, it is difficult to automatically detect omissions in the implementation of the disaster prevention plan and switch to the next person in line.

[0012] Patent Document 4 discloses an individualized emergency notification system that, after receiving an alarm notification, generates different instructions for each individual based on their position, age, experience, location, and other individual factors, and transmits them to a mobile terminal. In other words, Patent Document 4 is characterized by generating different instructions depending on the position or location and assigning additional actions based on location information as needed. However, Patent Document 4 aims to individualize emergency notifications and does not maintain the order of responsible persons, the order of replacements, the issuance conditions, and the type of evidence of performance as planning information in the disaster prevention plan, determine non-performance based on the response or evidence of performance obtained after notification, or escalate to a replacement responsible person. Therefore, although Patent Document 4 can optimize the content of notifications, it is not sufficient for controlling the performance of the disaster prevention plan and managing deviations from the plan.

[0013] Patent Document 5 discloses interaction control technology that allows for setting interaction rules for each user, such as delivery method, receipt confirmation settings, location information, handling of urgent or immediate messages, and frequency, order, and type of escalation, enabling receipt confirmation and escalation in emergency notifications. It also discloses dynamic segmentation that notifies only a portion of subscribers. In other words, Patent Document 5 is characterized by communication control, receipt confirmation, and narrowing of notification recipients in emergency notifications. However, Patent Document 5 focuses on a control platform for communication or messaging, and does not link and manage the issuance conditions, priority of responsible persons, alternative responsible persons candidates, and types of performance evidence for each response task predefined in the disaster prevention plan. Therefore, even if it is possible to confirm the arrival of notifications or control the notification route with Patent Document 5, it is difficult to manage the implementation of each response task itself, determine non-performance, and select alternative responsible persons.

[0014] Thus, while Patent Document 1 is characterized by notification of weather information, Patent Document 2 by notification of the status of confirmation notification acquisition based on rainfall information and water level information, Patent Document 3 by distribution of risk information and safety confirmation based on location information, Patent Document 4 by individualized instructions according to job title or location, and Patent Document 5 by notification control accompanied by receipt confirmation and escalation, none of these disclose a technology that manages the response tasks, issuance conditions, priority of responsible persons, alternative responsible persons candidates, types of performance evidence and predetermined times predetermined in the disaster prevention plan as a whole, and determines the notified persons, notification order, whether or not performance has not been performed and alternative responsible persons based on sequentially updated weather information, local government warnings, rainfall / water level / sediment disaster sensor information, location information, work information, authority information and danger zone information, as well as acquired responses and performance evidence, types of performance evidence associated with response tasks and predetermined times, and further compares the actual notification order, issuance conditions, notification time and performance evidence conditions with the plan information to output deviation types including condition deviations, timing deviations or performance judgment deviations, and generates performance records, audit logs including reasons for switching to alternative responsible persons and plan deviation alerts.

[0015] The present invention has been made in view of the above problems, and aims to provide a disaster response performance management system, a disaster response performance management method, and a program that, for each response task defined in the disaster prevention plan, determines the recipient of notification, the order of notification, and whether or not the task has been notified based on weather information, local government warnings, rainfall / water level / sediment disaster sensor information, location information, work information, authority information, and danger zone information acquired sequentially, as well as responses and performance evidence acquired from the notified person, the type of performance evidence associated with the response task, and a predetermined time, and if it is determined that the task has not been notified, selects an alternative person in charge to notify, re-notify, or escalate the matter, and further determines the type of deviation, including deviation from conditions, deviation from timing, and deviation from performance judgment, by comparing the actual order of notification, issuance conditions, notification time, and performance evidence conditions with the plan information, and integrally controls the performance record, audit log including the reason for switching to an alternative person in charge, and plan deviation alert, thereby suppressing omissions in the implementation of the disaster prevention plan and enabling more reliable implementation of actual disaster response. [Means for solving the problem]

[0016] To solve the above problems, a disaster response performance management system according to one aspect of the present invention includes: an information acquisition unit that acquires weather information, local government warnings, rainfall sensor information, water level sensor information, landslide sensor information, location information of the person in charge's terminal, work information, authority information and hazardous area information provided by the Japan Meteorological Agency; a planning information storage unit that stores, for each type of disaster, a response task, the conditions for issuing the response task, the order of responsible persons, the candidates for alternative responsible persons, the type of performance evidence, and a predetermined time in association with each type of disaster; and a system that determines the response task to be activated, the notified persons and the notification order based on the acquired information, the planning information, the responses and performance evidence acquired from the notified persons, the type of performance evidence associated with the response task, and the predetermined time, and if the performance evidence set as essential for the response task is not acquired within the predetermined time, The system includes a determination unit that determines whether a task is unfulfilled, including cases where the combination conditions for multiple performance evidence set as mandatory are not met, and for the response task determined to be unfulfilled, selects an alternative person in charge based on at least the location information, work information, authority information, and hazardous area information; a notification control unit that sends a notification, re-notification, or escalation notification to the mobile terminal of the person to be notified according to the determination result; and a record management unit that records an audit log for each response task, including the response and performance evidence obtained from the person to be notified, performance record, and reason for switching to an alternative person in charge, compares the actual notification order, issuance conditions, notification time, and performance evidence conditions with the plan information, determines the type of deviation, including at least condition deviation, timing deviation, and performance judgment deviation, and outputs a plan deviation alert including the said deviation type.

[0017] Here, the determination unit calculates the degree of risk by comparing weather information, local government warnings, and rainfall / water level / landslide disaster sensor information acquired sequentially with the threshold table, based on the threshold table, responsible person order change conditions, and parallel notification conditions stored in the planning information storage unit, and changes the notification order according to the degree of risk, or if the degree of risk is the second stage or higher, it can notify multiple responsible persons in parallel.

[0018] Furthermore, the performance evidence includes at least one of the following: location arrival information, image information, checklist completion information, and sensor information indicating equipment status. The determination unit can determine that a corresponding task is unfulfilled if the performance evidence set as mandatory for the corresponding task is not acquired within a predetermined time, or if the combination conditions of multiple performance evidence set as mandatory are not met.

[0019] Furthermore, the determination unit selects an alternative person responsible for the task determined to be unfulfilled based on at least location information, work information, authorization information, and information on predicted hazardous areas, and the notification control unit can send a re-notification or escalation notification to the alternative person responsible.

[0020] Furthermore, the record management unit records the notification time, re-notification time, escalation time, response content, performance evidence, performance record, and reason for switching to an alternative responsible person as a chronological audit log, and compares the actual notification order, issuance conditions, notification time, and performance evidence conditions with the plan information stored in the plan information database 50 to determine the type of deviation, which includes at least condition deviations, timing deviations, and performance judgment deviations, and can output a plan deviation alert including the said deviation type to the administrator terminal.

[0021] Furthermore, another aspect of the present invention can be realized as a disaster response performance management method and program that causes a computer to perform the functions of each of the above-mentioned parts.

[0022] Further, the determination unit uses at least response history, location information, work information, disaster type, and time zone as feature quantities, and based on a machine learning model learned with past disaster response histories, audit logs, and fulfillment evidence submission histories as learning data, estimates the non-response probability or the fulfillment delay probability. When the non-response probability is greater than or equal to a first threshold α, the notification order is changed. When the non-response probability is greater than or equal to a second threshold β, it is possible to simultaneously notify the candidate for alternate responsible person from the first notification. Further, the determination unit 13 makes a final decision about the output result of the machine learning model after checking the consistency with the rules regarding the order-issuing conditions, responsible person rankings, and candidates for alternate responsible persons stored in the plan information storage unit 12, and can update the machine learning model when adding an audit log or at regular intervals.

Effect of the Invention

[0023] According to the present invention, by integrally processing the response tasks, order-issuing conditions, responsible person rankings, candidates for alternate responsible persons, types of fulfillment evidence, and predetermined times defined in advance in the disaster prevention plan with the meteorological information, local government alerts, rainfall / water level / landslide disaster sensor information, location information, work information, authority information, and danger area information sequentially obtained, as well as the responses and fulfillment evidence obtained from the notification recipients, and the types of fulfillment evidence associated with the response tasks, it is possible to more reliably execute the responses in accordance with the disaster prevention plan in the event of a disaster or when there is a risk of a disaster occurring.

[0024] Also, according to the present invention, not only simple notification arrival or reception confirmation is performed, but also fulfillment evidence such as response and location arrival information, image information, checklist completion information, and sensor information indicating equipment status that is obtained, the fulfillment evidence that is essentially set for the response task, and the combination conditions and predetermined times of a plurality of fulfillment evidences that are essentially set are used to determine non-fulfillment. Therefore, it is possible to accurately grasp whether the response task has actually been carried out.

[0025] Furthermore, according to the present invention, even if the person in charge is unresponsive or there is insufficient evidence of performance, an alternative person in charge can be automatically selected based on location information, work information, authority information, and hazardous area information, and a re-notification or escalation notification can be issued. This helps to prevent delays in response even when the person in charge of the disaster prevention plan is absent, forgotten, or when on-site response is difficult.

[0026] Furthermore, according to the present invention, the notification time, re-notification time, escalation time, response content, performance evidence, performance record, and reason for switching to an alternative responsible person are recorded as a chronological audit log, and the actual notification order, issuance conditions, notification time, and performance evidence conditions are compared with the plan information to determine the type of deviation, which includes at least condition deviations, timing deviations, and performance judgment deviations, and a plan deviation alert including the said deviation type can be generated, thus providing records that are useful for post-disaster response verification, education, planning of recurrence prevention measures, and review of disaster prevention plans.

[0027] Therefore, compared to weather information notification technology such as Patent Document 1, confirmation notification acquisition status notification technology such as Patent Document 2, location information-based risk information distribution technology such as Patent Document 3, personalized emergency notification technology such as Patent Document 4, and notification control technology with receipt confirmation or escalation such as Patent Document 5, the present invention is superior in that it can integrate and realize the implementation control of disaster prevention plans, acquired responses and implementation evidence, implementation evidence set as mandatory for the response task and its combination conditions, non-implementation determination based on predetermined time, selection of alternative responsible persons based on location information, work information, authority information and hazardous area information, recording of audit logs including reasons for switching to alternative responsible persons, and determination of deviation types including condition deviations, timing deviations and implementation determination deviations by matching with plan information. [Brief explanation of the drawing]

[0028] [Figure 1] This is a block diagram showing the overall configuration of a disaster response performance management system according to one embodiment of the present invention. [Figure 2]This is an explanatory diagram showing an example of the data structure of planning information stored in a planning information storage unit according to one embodiment of the present invention. [Figure 3] This flowchart shows the basic processing procedure for a disaster response performance management system according to one embodiment of the present invention. [Figure 4] This flowchart shows an example of the determination process by the determination unit according to one embodiment of the present invention to determine the task to be activated, the person to be notified, and the notification order. [Figure 5] This is a sequence diagram showing the time-series processing of notification, re-notification, and escalation related to one embodiment of the present invention. [Figure 6] This flowchart shows an example of obtaining evidence of performance and determining non-performance in accordance with one embodiment of the present invention. [Figure 7] This flowchart shows an example of the process for selecting an alternative responsible person related to one embodiment of the present invention. [Figure 8] This is an explanatory diagram showing an example of a notification screen and a performance evidence input screen displayed on a terminal of a person in charge according to one embodiment of the present invention. [Figure 9] This is an explanatory diagram showing examples of the performance status list screen, audit log screen, and plan deviation alert screen displayed on the administrator terminal according to one embodiment of the present invention. [Figure 10] This is an explanatory diagram illustrating a specific example of disaster response implementation management during heavy rainfall related to one embodiment of the present invention. [Modes for carrying out the invention]

[0029] <Definition of Terms> In this specification, "failure to perform" means that the performance trails required for the relevant task are not obtained within the specified deadline, or that the conditions for the combination of multiple performance trails required are not met.

[0030] In this specification, "specified time" means the time set in the planning information database 50 or the notification execution instruction for each corresponding task as the response deadline, performance deadline, re-notification deadline, or the start deadline for selecting an alternative person in charge.

[0031] In this specification, "risk level" refers to the stages of disaster risk that the determination unit 13 calculates or classifies in stages by comparing weather information, local government warnings, rainfall information, water level information, landslide-related information, and other disaster-related information with a predetermined threshold table.

[0032] In this specification, "deviation from the plan" means a state in which the order of responsible persons, issuance conditions, notification time, performance evidence conditions, notification order, non-performance determination conditions, or alternative responsible person selection conditions are inconsistent with the plan information stored in the plan information database 50, and includes at least deviations from conditions, deviations from timing, and deviations from performance determination.

[0033] In this specification, "hazardous area information" refers to information indicating areas prone to flooding, areas at risk of sediment-related disasters, areas requiring evacuation, areas that are difficult to pass through, and other areas with a high degree of risk.

[0034] In this specification, "work information" means information indicating whether a person in charge is on duty, on night duty, on vacation, on a business trip, or otherwise available or operational.

[0035] Hereinafter, a disaster response performance management system 1 according to one embodiment of the present invention will be described with reference to the drawings. Figure 1 is a block diagram showing the overall configuration of the disaster response performance management system 1 according to this embodiment.

[0036] As shown in Figure 1, the disaster response performance management system 1 mainly consists of a management server 10, an external information source 20, one or more personnel terminals 30, an administrator terminal 40, a planning information database 50, and an audit log database 60. Each of these components is interconnected via the Internet, a public mobile network, a wireless LAN, a dedicated line, or other communication network.

[0037] The management server 10 is the core device of the disaster response performance management system 1 in this embodiment, and includes an information acquisition unit 11, a planning information storage unit 12, a determination unit 13, a notification control unit 14, a record management unit 15, and a communication unit 16. Each of these units may be implemented, for example, by one or more processors executing a program stored in memory, or as a functional module on a dedicated circuit, virtualization infrastructure, or cloud environment. The management server 10 may be configured as a single physical server, or its functions may be distributed across multiple servers.

[0038] External information sources 20 provide the management server 10 with external information necessary for disaster response, and include, for example, a weather information distribution server 21, a local government warning distribution server 22, a rainfall sensor 23, a water level sensor 24, and a landslide sensor 25. The weather information distribution server 21 distributes weather information, forecast information, warning information, advisory information, and other weather-related information provided by the Japan Meteorological Agency. The local government warning distribution server 22 distributes evacuation orders, evacuation information for the elderly and others, information on the opening of evacuation centers, and other warnings or disaster prevention-related information issued by local governments. The rainfall sensor 23, water level sensor 24, and landslide sensor 25 each generate information on rainfall, water level of rivers or waterways, ground conditions, or landslide risk at observation points, and transmit it to the management server 10.

[0039] The method of providing information from the external information source 20 to the management server 10 is not particularly limited and may include, for example, periodic acquisition via API, push-type distribution, sequential distribution via message queue, file linking, or transmission via sensor gateway. This allows the management server 10 to continuously acquire sequentially updated weather information, local government warnings, rainfall information, water level information, and landslide-related information.

[0040] The responsible person terminal 30 is an information terminal held by the person in charge or their substitute in charge of the disaster prevention plan, and consists of, for example, a smartphone, mobile phone, tablet, notebook computer, or other portable information processing terminal. In this embodiment, the responsible person terminal 30 is exemplified as a first responsible person terminal 31, a second responsible person terminal 32, and a substitute responsible person terminal 33, but the actual configuration is not limited to this, and any number of responsible person terminals 30 can be provided depending on the type of task to be handled or the size of the organization. Each responsible person terminal 30 receives notifications, re-notifications, or escalation notifications from the management server 10, and sends responses, confirmation results, and performance evidence 90 to the management server 10.

[0041] In addition to communication functions, the employee terminal 30 may also be equipped with a location information acquisition function to acquire location information 70, a function to input or receive work information 71 from an external system, an imaging function to acquire image information 92, and a user interface for inputting checklist completion information 93. This allows the employee terminal 30 not only to receive notifications but also to send information to the management server 10 indicating the status of performance, such as whether the employee actually arrived at the site and whether the necessary inspections or work were completed.

[0042] The administrator terminal 40 is an information terminal used by the administrator who oversees the entire disaster response, and consists of, for example, a desktop computer, a notebook computer, or a tablet device. The administrator terminal 40 receives and displays information from the management server 10 regarding ongoing response tasks, notified persons, response status, performance status, audit logs, and plan deviation alerts 83. This allows the administrator to grasp the status of implementation of the disaster prevention plan in real time when a disaster occurs or when there is a risk of a disaster occurring.

[0043] The planning information database 50 is a storage means for holding disaster prevention plans in a machine-readable format, and may be built into the management server 10 or connected to the management server 10 as an external storage device. The planning information database 50 stores, for example, a response task table 51, an issuance condition table 52, a responsible person ranking table 53, a substitute responsible person candidate table 54, and a performance evidence type table 55. This allows the management server 10 to refer to basic information for determining which response tasks should be activated, who should be notified and in what order, and what kind of performance evidence 90 should be obtained for each type of disaster.

[0044] The audit log database 60 is a storage means for chronologically recording information regarding notifications 80, re-notifications 81, escalation notifications 82, responses from responsible persons, performance evidence 90, history of switching to alternative responsible persons, and plan deviation alerts 83. It may be built into the management server 10 or configured as an external storage device. This allows for retrospective verification of the implementation status of the disaster prevention plan, whether there were any deviations, and the response history of each responsible person after a disaster response.

[0045] The communication unit 16 controls communication between the external information source 20, the employee terminal 30, the administrator terminal 40, the planning information database 50, and the audit log database 60. The communication method is not particularly limited, and for example, HTTPS communication, application programming interface communication, email, short message service, push notification, dedicated application communication, and other communication methods can be appropriately adopted. This allows the present invention to reliably deliver notifications to each employee's mobile terminal while utilizing the existing information infrastructure.

[0046] As described above, the disaster response performance management system 1 according to this embodiment has a configuration in which the management server 10 integrally processes disaster-related information acquired sequentially from an external information source 20, disaster prevention plan information stored in the plan information database 50, and location information 70, work information 71, and performance evidence 90 acquired from the person in charge terminal 30. As a result, the disaster response performance management system 1 can integrally realize notification, re-notification, escalation, and performance management in accordance with the disaster prevention plan.

[0047] In this embodiment, a configuration in which the management server 10, the planning information database 50, and the audit log database 60 are interconnected is illustrated. However, these configurations are merely examples, and for instance, the management server 10 may have the planning information database 50 and the audit log database 60 built-in, or the data may be stored on a distributed storage infrastructure in the cloud. Furthermore, the types and number of external information sources 20 can be appropriately changed depending on the type of disaster being targeted, the organization's operational style, or the area of ​​use.

[0048] <Configuration of the information acquisition unit and the information acquired> Next, with reference to Figure 1, the configuration of the information acquisition unit 11 and the information acquired by the management server 10 will be described. The information acquisition unit 11 is a functional unit in the disaster response performance management system 1 that acquires various types of information used for disaster response determination from external information sources 20 and personnel terminals 30, etc.

[0049] The information acquired by the information acquisition unit 11 includes, at a minimum, weather information provided by the Japan Meteorological Agency, local government warnings, rainfall information, water level information, landslide-related information, location information 70 of the personnel terminal 30, work information 71, authority information 72, and hazardous area information 73. The information acquisition unit 11 acquires this information sequentially, converts it into a format usable by the determination unit 13, and stores it in the management server 10, or temporarily stores it in the planning information database 50 or other storage area.

[0050] Weather information includes, for example, rainfall forecasts, actual rainfall, advisories, warnings, special warnings, typhoon information, flood forecasts, landslide warnings, information on linear rainbands, and other various information provided by the Japan Meteorological Agency. The information acquisition unit 11 may acquire this weather information at predetermined intervals by performing external API communication with the weather information distribution server 21, or it may receive it sequentially by push-type distribution from the weather information distribution server 21. The acquisition interval is not particularly limited, but for example, it can be set every tens of seconds, every few minutes, or every time a warning is issued or updated.

[0051] Local government warnings include, for example, evacuation orders, evacuation orders for the elderly and others, information on the opening of evacuation centers, information on road traffic restrictions, information on emergency safety measures, and other disaster prevention-related information issued by local governments. The information acquisition unit 11 can acquire local government warnings from the local government warning distribution server 22 via external APIs, email distribution, push notifications, file linking, and other communication methods. As a result, the information acquisition unit 11 can supply not only Japan Meteorological Agency information but also local government-issued warning information to the judgment unit 13.

[0052] Rainfall information, water level information, and landslide-related information are obtained from rainfall sensor 23, water level sensor 24, and landslide sensor 25, respectively. Rainfall information includes, for example, rainfall per unit time, cumulative rainfall, short-term rainfall, and other observed values ​​related to rainfall. Water level information includes, for example, water levels, flow rates, or information on exceeding warning thresholds in rivers, irrigation canals, retention ponds, or drainage facilities. Landslide-related information includes, for example, ground moisture content, displacement of slopes, risk of collapse, or various information that contributes to landslide warning determination.

[0053] The method of acquiring information from each of the sensors is not particularly limited, and the information acquisition unit 11 can sequentially receive observation information from each of the sensors via a sensor communication network, gateway device, wireless communication device, wired communication device, or monitoring device. For example, the rainfall sensor 23, water level sensor 24, and landslide sensor 25 may transmit observation values ​​at regular intervals, or transmit event information when a threshold is exceeded. The information acquisition unit 11 can receive the observation values ​​or event information and record them in association with the reception time and observation location information.

[0054] Location information 70 is information indicating the current location of the person in charge terminal 30, and includes, for example, GNSS positioning results, base station information, wireless LAN positioning information, and other location identification information. The information acquisition unit 11 may receive location information 70 transmitted from the person in charge terminal 30 at predetermined intervals, or it may request the person in charge terminal 30 to transmit its location after sending a notification 80, a re-notification 81, or an escalation notification 82, and acquire location information 70 as a response. This allows the information acquisition unit 11 to acquire information to determine whether each person in charge is in a position to reach the target facility, evacuation center, river management point, or other site.

[0055] The work information 71 indicates whether the person in charge is currently on duty, on night duty, on leave, or within the designated available time slot. The information acquisition unit 11 may acquire the work information 71 by manual input from the person in charge terminal 30, or it may acquire the work information 71 by external API communication in cooperation with an HR system, attendance management system, shift management system, or other external system. This allows the determination unit 13 to determine the person to be notified or the substitute person in charge, taking into account not only the formal ranking of responsible persons but also their actual availability.

[0056] The authorization information 72 is information indicating the scope of response tasks that each person in charge can perform, the equipment they can operate, the areas they can enter, and other details of their authorization, and is acquired by the information acquisition unit 11. The authorization information 72 may be acquired, for example, from an organization's authorization management system, equipment management system, or user master. This allows the determination unit 13 to select not only the person in charge closest to the site, but also a person in charge who has the authority to legally and actually perform the response task as the person to be notified or the substitute person in charge.

[0057] Hazardous area information 73 is information about areas prone to flooding, areas at risk of sediment-related disasters, areas subject to evacuation, areas that are difficult to pass through, and other areas with a high degree of risk, and is acquired by the information acquisition unit 11. Hazardous area information 73 may be generated based on external information such as hazard map information, area information published by local governments, predicted flood information, sediment-related disaster risk distribution information, or it may be acquired directly from an external system. As a result, the determination unit 13 can compare the location information 70 of the person in charge terminal 30 with the hazardous area information 73 and make a decision to prioritize avoiding persons in charge located within the hazardous area, or to prioritize selecting persons in charge closest to a specific area.

[0058] The information acquisition unit 11 may not only receive the information but also normalize the data format, time format, location representation format, or identifier format, which may differ for each information source. For example, the information acquisition unit 11 may add the acquisition time, information source identifier, target area identifier, and corresponding disaster type to each piece of information, processing it so that the determination unit 13 can easily compare and verify it. Furthermore, the information acquisition unit 11 may merge duplicate information, fill in missing values, exclude outliers, or update to the latest information.

[0059] Furthermore, the acquisition cycle of the information acquisition unit 11 can be set to differ depending on the type of information. For example, weather information and local government warnings may be acquired each time they are updated or every few minutes, rainfall information, water level information, and landslide-related information may be acquired every few tens of seconds or every few minutes, location information 70 may be acquired preferentially and at short intervals for the personnel terminal 30 that has been notified, and work information 71 and authority information 72 may be acquired daily or when changes occur. This makes it possible to collect information necessary for disaster response in a timely manner while suppressing communication load and processing load.

[0060] As described above, the information acquisition unit 11 according to this embodiment is configured to sequentially acquire Japan Meteorological Agency information, local government warnings, rainfall information, water level information, landslide-related information, location information 70, work information 71, authority information 72, and hazardous area information 73 using external API communication, push notifications, sensor communication, and other communication methods. As a result, the determination unit 13 can use the information necessary to determine the persons to be notified, the order of notifications, whether or not they have not been fulfilled, and the alternative person in charge, based on the disaster prevention plan, in accordance with the constantly changing disaster situation.

[0061] The types of information acquired by the information acquisition unit 11, the source of acquisition, the acquisition cycle, and the communication method can be appropriately changed depending on the target organization, region, type of disaster, or implementation environment. For example, in an embodiment for businesses, equipment monitoring information or entry / exit information may be added, and in an embodiment for local governments, evacuation center congestion information or road flooding information may be added. Furthermore, the acquisition conditions for location information 70 or work information 71 from the employee terminal 30 may be changed according to user settings or privacy protection policies.

[0062] <Data structure of the planning information storage unit> Next, with reference to Figures 1 and 2, the configuration of the planning information storage unit 12 and the data structure stored in the planning information database 50 will be described. The planning information storage unit 12 is a functional unit that stores various types of information defined in the disaster prevention plan in a machine-readable format and manages it so that the determination unit 13 can compare it with disaster-related information acquired sequentially.

[0063] In this embodiment, the planning information storage unit 12 refers to or manages the planning information database 50. The planning information database 50 can be implemented by, for example, a relational database, a key-value store, a document-type database, or other storage structure, but it has a configuration that can store, in association with, at least disaster type, response task, issuance conditions, responsible person ranking, alternative responsible person candidate, performance evidence type, parallel notification conditions, and priority change conditions.

[0064] As shown in Figure 2, the planning information database 50 includes, for example, a corresponding task table 51, an order condition table 52, a responsible person ranking table 53, a substitute responsible person candidate table 54, and a performance evidence type table 55. Each of these tables is linked to the others by common identification information, such as a disaster type identifier, a corresponding task identifier, a target area identifier, or a facility identifier, and the determination unit 13 can cross-reference the necessary planning information based on this identification information.

[0065] The response task table 51 is a table that stores the response tasks to be executed for each type of disaster. The response task table 51 stores information such as the type of disaster, the response task identifier, the response task name, the target facility, the target area, the response content, the deadline for execution, the completion criteria, and other information. For example, the type of disaster can be set to heavy rain, flood, landslide, storm, high tide, earthquake, or complex disaster, and for example, the name of the response task can be set to drainage facility inspection, opening of evacuation shelters, confirmation of emergency power supply, slope patrol, river monitoring, or contact with residents.

[0066] The issuance condition table 52 is a table that stores the conditions under which each corresponding task should be activated. The issuance condition table 52 stores, for example, the corresponding task identifier, the type of information to be judged, thresholds, comparison conditions, target area, effective time period, and condition combination information. The type of information to be judged can be set to weather information, local government warnings, rainfall information, water level information, landslide-related information, and other external information. The thresholds can be set to, for example, when hourly rainfall exceeds a predetermined value, when the water level exceeds the warning level, when landslide warning information is issued, or when a local government warning reaches a specific category.

[0067] Furthermore, the issuance condition table 52 may store not only single conditions but also combinations of multiple conditions. For example, it may store conditions for activating a response task when the hourly rainfall in a designated area is above the first threshold and the river water level is above the second threshold, or conditions for activating an on-site confirmation task when a landslide disaster warning is issued and the location of the person in charge is outside the danger zone. In addition, the issuance condition table 52 may include a threshold table for calculating the degree of danger in stages by comparing weather information, local government warnings, rainfall information, water level information, and landslide disaster-related information, as well as parallel notification conditions or priority change conditions according to the increase in the degree of danger, as attribute information. For example, it may store conditions for sequentially issuing notifications when the degree of danger is at stage 1, and for parallel notifications to multiple responsible persons when the degree of danger is at stage 2 or higher.

[0068] The responsible person ranking table 53 is a table that stores the order of those to be notified and the conditions for changing the priority for each response task. The responsible person ranking table 53 stores, for example, the response task identifier, responsible person ranking, person in charge identifier, department in charge, job title, area in charge, normal priority, emergency priority, whether parallel notification is possible, and conditions for changing the priority. Conditions for changing the priority can be set, for example, whether it is nighttime, a holiday, whether the person in charge is in a dangerous area, whether it is outside of working hours, or whether to prioritize a person in charge who has the authority to operate specific equipment. As a result, the determination unit 13 can mechanically determine the notification order after the change, not only based on the normal responsible person ranking but also according to the disaster situation or the status of the person in charge.

[0069] The Alternative Responsibility Candidate Table 54 is a table that stores alternative responsibility candidates that can be used when the responsible person fails to respond, fails to perform, or is unable to perform a task. The Alternative Responsibility Candidate Table 54 stores, for example, the task identifier, candidate rank, responsible person identifier, department, area of ​​responsibility, required authority, required qualifications, working conditions, alternative activation conditions, and switching restriction conditions. Alternative activation conditions can be set, for example, no response within a specified time, no evidence of performance can be obtained, the person is located in a hazardous area, or the person is off duty. This allows the determination unit 13 to select not only the formal next in line, but also an alternative responsibility person who is actually capable of performing the task.

[0070] The performance evidence type table 55 is a table that stores the types of performance evidence 90 to be acquired for each corresponding task. The performance evidence type table 55 stores, for example, the corresponding task identifier, performance evidence type, whether it is required or optional, acquisition deadline, determination conditions, evidence combination conditions, and reconfirmation conditions. For example, performance evidence types can be set to location arrival information 91, image information 92, checklist completion information 93, and equipment status sensor information 94. For example, evidence combination conditions can be set to require both location arrival information 91 and image information 92, and to determine that the task is completed when both are acquired, or to require checklist completion information 93 and equipment status sensor information 94, and to determine that the task is completed when the equipment status sensor information 94 indicates a normal state.

[0071] In addition to the tables mentioned above, the planning information database 50 may also hold common setting information for each type of disaster, target area information, notification template information, or organization-specific setting information. For example, in an embodiment for local governments, it may hold information on evacuation shelters, river areas, and resident notification categories, and in an embodiment for companies, it may hold information on equipment types, manufacturing lines, and operational shutdown procedures. In this way, the planning information database 50 can hold the contents of the disaster prevention plan as a data structure that can be expanded according to the target organization.

[0072] The planning information storage unit 12 not only registers each of the tables during initial setup, but may also update them in accordance with revisions to the disaster prevention plan, organizational changes, personnel transfers, changes in the area of ​​responsibility, or changes in laws or local government standards. For example, the responsible person identifier in the responsible person ranking table 53 can be changed, or the threshold values ​​in the issuance condition table 52 can be updated via the administrator terminal 40. In this way, the planning information database 50 can always be kept with the latest disaster prevention plan content, and the accuracy of the determination unit 13's determination of those to be notified and alternative responsible persons can be improved.

[0073] Furthermore, the planning information storage unit 12 may perform consistency checks on corresponding task identifiers, responsible person identifiers, area identifiers, or facility identifiers to ensure consistency between tables. For example, it can verify whether at least one issuance condition, at least one responsible person, and at least one type of performance evidence are associated with each corresponding task registered in the corresponding task table 51, and can display a warning to the administrator terminal 40 if there are any omissions. This helps to prevent setting errors when making disaster prevention plans machine-readable.

[0074] Thus, the planning information storage unit 12 according to this embodiment is configured to store the disaster prevention plan in the planning information database 50 as a machine-readable data structure including disaster type, response task, issuance conditions, priority of responsible persons, alternative responsible persons candidates, performance evidence type, parallel notification conditions, and priority change conditions. As a result, the determination unit 13 can compare the disaster prevention plan with sequentially acquired weather information, local government warnings, rainfall information, water level information, sediment disaster-related information, location information 70, work information 71, authority information 72, and hazardous area information 73, and automatically determine the recipients of notifications, the order of notifications, whether or not they have not been fulfilled, and the alternative responsible persons.

[0075] <Determination of tasks to be activated and recipients to be notified by the judgment unit> Next, with reference to Figures 1, 3, and 4, the determination process by the determination unit 13 for determining the tasks to be activated and the persons to be notified will be explained. The determination unit 13 is a functional unit that compares external information acquired sequentially by the information acquisition unit 11 with various tables in the planning information database 50 held by the planning information storage unit 12 to determine the corresponding tasks to be activated, the persons to be notified, the notification order, whether parallel notifications are necessary, and whether priority changes are necessary.

[0076] When the determination unit 13 receives, for example, the latest weather information, local government warnings, rainfall information, water level information, landslide-related information, location information 70, work information 71, authority information 72, and hazardous area information 73 from the information acquisition unit 11, it first extracts the target area, target facility, acquisition time, and disaster type contained in this information to identify the area or facility to be determined. This allows the determination unit 13 to determine which area or facility's plan information should be referenced from among the multiple disaster prevention plans stored in the plan information database 50.

[0077] Next, the determination unit 13 refers to the issuance condition table 52 and determines which corresponding task's issuance conditions are met by the acquired external information. For example, if the hourly rainfall in a predetermined area is equal to or greater than the first threshold, the drainage facility inspection task can be activated; if the river water level exceeds the warning level, the river monitoring task can be activated; and if a landslide warning is issued, the slope patrol task can be activated. In addition, if the local government warning reaches a predetermined category, the evacuation center opening task or the resident contact task can be activated. In this way, the determination unit 13 extracts the corresponding task to be activated according to the external information acquired sequentially.

[0078] The determination unit 13 may determine which task to activate based not only on a single piece of information, but also on a combination of multiple pieces of information. For example, it may activate a drainage pump activation confirmation task only when the hourly rainfall is above a predetermined value and the river water level is above a predetermined value, or it may activate an evacuation support task only when a landslide disaster warning is issued and the target area is included in the hazardous area information 73. In this way, the determination unit 13 can use the condition combination information stored in the issuance condition table 52 to make a more appropriate task activation determination according to the disaster situation.

[0079] Once the tasks to be activated are determined, the determination unit 13 refers to the corresponding task table 51 and the responsible person ranking table 53 to extract candidates for notification for each corresponding task. Specifically, the determination unit 13 refers to the responsible person ranking, responsible department, responsible area, and job title information associated with the corresponding task identifier to determine the first responsible person, second responsible person, and other candidates. At this time, the determination unit 13 may refer to the work information 71 to exclude or lower the priority of personnel who are off duty, on vacation, or not on duty from notification.

[0080] Furthermore, the determination unit 13 can narrow down the list of potential notification recipients by referring to location information 70, authority information 72, and hazardous area information 73. For example, it can prioritize personnel located near the target facility or area, exclude personnel who do not have the necessary equipment operation or entry authority for the response task, or lower the priority of personnel located within the hazardous area who would be unable to respond on-site. This allows the determination unit 13 to select notification recipients not only based on the formal ranking of responsible persons in the plan, but also considering the actual feasibility of response.

[0081] The determination unit 13 refers to the parallel notification conditions and priority change conditions stored in the responsible person ranking table 53 and the issuance condition table 52 to decide whether to issue sequential notifications or parallel notifications. For example, if the level of danger is Stage 1, a sequential notification method can be adopted in which a notification 80 is issued only to the first responsible person, and if a response or evidence of performance 90 is not obtained within a predetermined time, a re-notification 81 or escalation notification 82 is issued to the second responsible person. On the other hand, if the level of danger is Stage 2 or higher, or if the local government warning is in a highly urgent category, a parallel notification method can be adopted in which notifications are issued simultaneously to the first and second responsible persons.

[0082] Here, the degree of danger may be calculated in stages by comparing weather information, local government warnings, rainfall information, water level information, and landslide-related information with a predetermined threshold table. For example, the first degree of danger may be set when the rainfall is above the first threshold and the water level is below the warning level, the second degree of danger may be set when the rainfall is above the second threshold or the water level is above the warning level, and the third degree of danger may be set when the local government warning is equivalent to an evacuation order or when landslide warning information is issued. The determination unit 13 can change the number of people to be notified, the order of notifications, and whether or not to issue parallel notifications according to this degree of danger.

[0083] Furthermore, the determination unit 13 may change the notification order according to the type of alarm. For example, in a drainage facility inspection task caused by heavy rain, the facility manager can be given the highest priority; in a river monitoring task caused by rising river levels, the river manager can be given the highest priority; and in a slope patrol task caused by a landslide warning, the slope management manager or evacuation guidance manager can be given the highest priority. In addition, at night or on holidays, the priority order of those responsible can be changed to include the night shift person or the holiday response manager instead of the usual priority order. In this way, the determination unit 13 can dynamically switch the notification order according to the type of alarm, the type of disaster, and the time of day.

[0084] The determination unit 13 may determine the priority of each response task when multiple response tasks are started simultaneously. For example, if an evacuation support task or a resident contact task related to protecting human lives is set to a higher priority than an equipment inspection task, and multiple response tasks are assigned to the same person in charge, the higher priority task can be notified first, followed by the lower priority task. Alternatively, multiple tasks can be notified to the same person in charge at once, and the workload status of that person can be displayed on the administrator terminal 40. This allows the determination unit 13 to rationally control multiple responses during a disaster.

[0085] Furthermore, the determination unit 13 outputs a notification execution instruction to the notification control unit 14 based on the selection result of the person to be notified. This notification execution instruction includes, for example, the corresponding task identifier, the person to be notified identifier, the notification order, whether or not to send parallel notifications, the notification deadline, the response deadline, the required type of performance evidence, and the escalation start conditions. Based on this notification execution instruction, the notification control unit 14 can send a notification 80 to the person in charge terminal 30.

[0086] As shown in Figure 4, the determination process by the determination unit 13 to determine the tasks to be activated and the persons to be notified can be implemented by including, for example, the steps of receiving information to acquire external information, identifying the target area and type of disaster, determining whether the issuance conditions are met, extracting tasks to be activated, determining the persons to be notified based on the order of responsible persons, location information 70, work information 71, authority information 72 and danger zone information 73, selecting sequential notification or parallel notification according to the degree of danger or type of alarm, and outputting a notification execution instruction to the notification control unit 14.

[0087] As described above, the determination unit 13 according to this embodiment can automatically determine which response task to activate, who to notify, whether to use sequential or parallel notifications, and how to change the notification order according to the degree of danger or type of alarm, by comparing the external information acquired sequentially with the issuance conditions, responsible person ranking, parallel notification conditions, and priority change conditions held in the plan information storage unit 12. This makes it possible to flexibly and reliably activate responses based on the disaster prevention plan according to the progress of the disaster.

[0088] <Notification, re-notification, and escalation by the Notification Control Unit> Next, the notification, re-notification, and escalation processing by the notification control unit 14 will be explained with reference to Figures 1 and 5. The notification control unit 14 is a functional unit that, based on the notification execution instruction output from the determination unit 13, performs an initial notification to the responsible person's terminal 30, a re-notification after a predetermined time has elapsed, and an escalation notification to the next person in line or an alternative responsible person in case of no response or failure to perform.

[0089] When the notification control unit 14 receives a notification execution instruction from the determination unit 13, which includes the corresponding task identifier, the notified person identifier, the notification order, whether or not to send parallel notifications, the notification deadline, the response deadline, the required performance evidence type, and the escalation start conditions, it sends a notification 80 to the responsible person terminal 30 based on this instruction. The initial notification 80 is sent, for example, to the first responsible person terminal 31, and notification execution information is also sent to the administrator terminal 40 as needed.

[0090] The contents of the notification 80 include, at a minimum, the name of the response task, the type of disaster, the area or facility, the reason for issuance, the time of notification, the response deadline, the performance deadline, the type of performance evidence 90 required, the reporting destination, and information regarding the response procedure. For example, a notification 80 concerning a drainage facility inspection task during heavy rainfall may include information such as "drainage facility inspection," "target facility A," "hourly rainfall exceeds a specified value," "response deadline is 5 minutes from now," "performance deadline is 15 minutes from now," and "transmit location arrival information 91 and image information 92." This allows the person in charge who receives the notification not only to receive a warning, but also to immediately understand the response to be taken and the necessary reports.

[0091] The notification control unit 14 can use multiple communication paths when sending notifications 80. These communication paths can include, for example, push notifications to a dedicated application, short message service, email, voice calls, chat notifications, or a business messaging platform. The notification control unit 14 may send notifications according to a pre-registered priority communication path for each responsible terminal 30, or it may switch communication paths depending on communication congestion during a disaster, delivery confirmation results, or the terminal status.

[0092] For example, the notification control unit 14 may use push notifications to a dedicated application for the initial notification, and if no confirmation of receipt or response is received within a predetermined time, it may send a re-notification 81 via short message service or email, and if no response is received within a further predetermined time, it may execute an escalation notification 82 using a voice call or another communication route. In this way, the notification control unit 14 can improve the probability of reaching the person in charge by using multiple communication routes in stages or in parallel, without relying on a single communication route.

[0093] When the person in charge terminal 30 receives notification 80, it can accept response input such as "respond," "unable to respond," or "checking." The person in charge terminal 30 can also transmit location arrival information 91, image information 92, checklist completion information 93, or equipment status sensor information 94 as proof of performance 90, according to the request contained in the notification. When the notification control unit 14 receives these responses or proof of performance 90, it hands over the reception time and content to the record management unit 15 and, if necessary, notifies the determination unit 13.

[0094] After sending the notification 80, the notification control unit 14 monitors the response deadline or performance deadline set by the determination unit 13. If a response is not received within the predetermined time, or if a response is received but the necessary performance evidence 90 is not obtained, it can send a re-notification 81. In addition to the same corresponding task information as the initial notification, the re-notification 81 may also include warning information such as "no response," "performance evidence not submitted," or "predetermined time remaining until deadline." This encourages the person in charge to respond or submit a performance report, thereby preventing performance omissions due to forgetting or overlooking the notification.

[0095] Furthermore, if a response or the necessary evidence of performance 90 is not received within a predetermined time after the re-notification 81, the notification control unit 14 may send an escalation notification 82 to the next person in line or an alternative person in charge, based on the determination result of the determination unit 13. The escalation notification 82 may include the content of the task to be handled, the notification history to date, the reason for the lack of response or non-performance, the type of evidence of performance 90 required, and the deadline for alternative action. For example, if there is no response from the first person in charge terminal 31, it may be sent to the second person in charge terminal 32, and if the second person in charge terminal 32 is also unable to respond, it may be sent to the alternative person in charge terminal 33.

[0096] The notification control unit 14 can support not only sequential notification but also parallel notification. For example, if the determination unit 13 instructs parallel notification according to an increase in risk level or alarm type, the notification control unit 14 can simultaneously send a notification 80 to the first responsible terminal 31 and the second responsible terminal 32, and update the notification status of the other when a valid response and proof of performance 90 is obtained from either of the responsible parties. In this case, the notification control unit 14 may also notify the administrator terminal 40 and each responsible party terminal 30 of the status of accepting the task or the status of assigning the task, in order to avoid duplicate responses.

[0097] Furthermore, if the notification control unit 14 detects that the responsible person's terminal 30 is unable to communicate, has lost power, is out of range, or is unreachable, it may automatically select an alternative communication route or notify the determination unit 13 of the unreachable status to prompt the recipient to re-select the recipient. For example, if a push notification is not received within a certain period of time, it can switch to the short message service, and if the short message service is also unreachable, it can switch to a voice call or notification to another terminal. In this way, the notification control unit 14 can re-select a communication route according to the delivery status.

[0098] The notification control unit 14 notifies the record management unit 15 of the destination, transmission time, communication path, reception confirmation result, response content, and number of retransmissions for each of the notifications 80, re-notification 81, and escalation notification 82. As a result, the record management unit 15 records the notification history in chronological order in the audit log database 60, which can be used for generating audit logs and outputting plan deviation alerts 83, as described later.

[0099] As shown in Figure 5, the processing of the notification control unit 14 according to this embodiment can be implemented by including, for example, the steps of: receiving a notification execution instruction from the determination unit 13; sending a notification 80 as an initial notification; monitoring whether a response or proof of performance 90 has been received by the response deadline or performance deadline; sending a re-notification 81 if the proof of performance set as mandatory for the corresponding task is not obtained within a predetermined time, or if the obtained proof of performance 90 does not satisfy the combination conditions of multiple proof of performance set as mandatory; further sending an escalation notification 82 to the next person in line or the substitute person in charge after the determination of non-performance; and outputting each notification result to the record management unit 15.

[0100] As described above, the notification control unit 14 according to this embodiment is configured to perform initial notification to the responsible person's terminal 30, re-notification after a predetermined time has elapsed, escalation notification to the next person in line or an alternative responsible person in case of non-response or non-performance, and the use of multiple communication paths. Since each notification includes information such as the task to be addressed, the deadline, and the necessary evidence of performance 90, it is possible to clearly instruct the responsible person to take action based on the disaster prevention plan, while suppressing notification omissions, response omissions, and performance omissions.

[0101] <Obtaining evidence of performance and determining non-performance> Next, with reference to Figures 1 and 6, the acquisition of performance evidence 90 and determination of non-performance will be explained. In this embodiment, the disaster response performance management system 1 not only obtains simple confirmation of receipt or response content from the person in charge terminal 30, but also acquires performance evidence 90 required for each response task, and is configured to determine whether the response task has been completed or not based on the content of the performance evidence 90.

[0102] When the notification control unit 14 sends a notification 80, a re-notification 81, or an escalation notification 82, the person in charge terminal 30 displays a performance evidence input screen corresponding to the content of the task. The person in charge can send location arrival information 91, image information 92, checklist completion information 93, and other performance evidence 90 through this screen. Furthermore, if the status of the equipment is monitored by external equipment or a sensor device, the information acquisition unit 11 can acquire equipment status sensor information 94 and manage it in association with the corresponding task.

[0103] Location arrival information 91 is information indicating that the person in charge has arrived at the target facility, target area, or on-site inspection point, based on the current location information acquired by the person in charge terminal 30. For example, the person in charge terminal 30 can acquire location information using GNSS positioning results, base station information, or wireless LAN positioning information, and transmit it to the management server 10 along with the corresponding task identifier, acquisition time, and person in charge identifier. The determination unit 13 can compare the location arrival information 91 with the target facility or target area stored in the corresponding task table 51 and determine whether or not the person has reached a predetermined range.

[0104] Image information 92 is a photograph or image data acquired using the imaging function of the operator terminal 30, and is used to indicate the status of the corresponding task, the condition of the equipment, whether there are any abnormalities at the site, and so on. For example, in a drainage equipment inspection task, an image of the condition of the drainage equipment can be transmitted, and in a shelter opening task, an image of the shelter entrance or the arrangement of stockpiled supplies can be transmitted. The image information 92 may also have the time of shooting, the location of shooting, or the identification information of the person in charge added to it as needed. This allows the determination unit 13 to use the image information 92 as reinforcing information to indicate that the target object was actually checked or work was performed after arrival at the site.

[0105] The checklist completion information 93 is information that shows the result of the person in charge entering whether each of the multiple confirmation items or work items pre-set for each task has been completed. For example, in the emergency power supply confirmation task, a checklist can be set that includes items such as "power supply start confirmation," "fuel level confirmation," and "alarm display confirmation." The person in charge terminal 30 can send the checklist completion information 93, which includes the input result for each item, the input time, and the person in charge's identification information, to the management server 10. This allows the judgment unit 13 to understand whether the necessary confirmation items have been individually performed, rather than simply responding with "I will do it."

[0106] The equipment status sensor information 94 is information obtained from sensors, monitoring devices, or equipment management systems installed on the target equipment, and indicates the operating status, alarm status, operation completion status, or normal recovery status of the equipment. For example, the starting status of a drainage pump, the closed status of a water stop plate, the operating status of an emergency generator, or the decrease in the water level inside the facility can be obtained as equipment status sensor information 94. The information acquisition unit 11 can record the equipment status sensor information 94 in association with an equipment identifier, acquisition time, and corresponding task identifier, and supply it to the determination unit 13.

[0107] The planning information storage unit 12 stores the type of performance evidence 90 required, whether it is mandatory or optional, the acquisition deadline, the judgment conditions, and the evidence combination conditions for each corresponding task in the performance evidence type table 55. For example, for the slope patrol task, location arrival information 91 and image information 92 can be set to be mandatory; for the shelter opening task, checklist completion information 93 can be set to be mandatory; and for the drainage equipment inspection task, both image information 92 and equipment status sensor information 94 can be set to be mandatory. In addition, as an evidence combination condition, location arrival information 91 alone may not be considered completed, but rather completed only when combined with image information 92 or checklist completion information 93.

[0108] The determination unit 13 compares the performance evidence 90 obtained via the notification control unit 14 or the information acquisition unit 11 with the requirements stored in the performance evidence type table 55 to determine whether the corresponding task has been completed. Specifically, the determination unit 13 checks the type of the acquired performance evidence 90, the time of acquisition, the target location, the target equipment, and the identification information of the person in charge, and determines whether all the performance evidence 90 required for the corresponding task have been acquired within the predetermined period. In addition, if necessary, the determination unit 13 may not determine that the task has been completed if the location arrival information 91 indicates a location outside the target area, if it is determined that the image information 92 contains an object unrelated to the corresponding task, or if there are uncompleted items remaining in the checklist completion information 93.

[0109] In this case, the determination unit 13 does not determine that the task has been completed solely based on confirmation of receipt, confirmation of read status, or a response of "I will respond" from the person in charge. In other words, in this embodiment, receipt of the notification or expression of intent merely indicates the intention to commence the task or recognition of the notification content, and whether or not the necessary actions have actually been completed is determined based on the acquisition results of the performance evidence 90. This clearly distinguishes between notification confirmation and the completion of actual work, and not only prevents mere omissions in responses, but also enables the detection of actual performance omissions.

[0110] The determination unit 13 can determine that the corresponding task is unfulfilled if the required performance evidence 90 is not obtained within a predetermined time, if the type of performance evidence 90 obtained is insufficient, if the acquisition location does not match the target area, or if the equipment status sensor information 94 has not reached a predetermined normal state. For example, if location arrival information 91 is obtained but image information 92 is not submitted, or if checklist completion information 93 is transmitted but equipment status sensor information 94 indicates an abnormal state, the determination unit 13 can determine that the task is unfulfilled or insufficiently fulfilled.

[0111] If non-performance is determined, the determination unit 13 outputs the determination result to the notification control unit 14, which can then determine whether a re-notification 81 or an escalation notification 82 is necessary. The determination unit 13 also notifies the record management unit 15 of the details of the missing performance evidence 90, the conditions for determining non-performance, and the time of determination. By recording this information in the audit log database 60, the record management unit 15 can later track which performance evidence was missing and at what point the non-performance determination was made.

[0112] On the other hand, the determination unit 13 determines that a task is completed if the performance evidence set as required in the performance evidence type table 55 is acquired within a predetermined time, and the combination conditions for multiple performance evidence set as required are met. The determination result can then be output to the record management unit 15 and the administrator terminal 40. As a result, the administrator terminal 40 can display the progress status of each task, such as not started, in progress, completed, or not yet completed.

[0113] As shown in Figure 6, the acquisition of performance evidence 90 and the non-performance determination process according to this embodiment can be implemented by including, for example, the steps of acquiring performance evidence 90 from the person in charge terminal 30 or external equipment after notification, associating the acquired performance evidence 90 with the corresponding task identifier, identifying the required evidence and acquisition deadline by referring to the performance evidence type table 55, comparing the acquired evidence with the required evidence, determining whether there are any unfulfilled conditions, and outputting the determination result of whether it has been performed or not.

[0114] As described above, the disaster response performance management system 1 according to this embodiment acquires performance evidence 90 such as location arrival information 91, image information 92, checklist completion information 93, and equipment status sensor information 94, and has a configuration that determines whether the performance is not performed or has been performed by comparing it with the type and combination of performance evidence 90 required for each response task, rather than simply confirming receipt. This allows for a highly accurate understanding of whether the person in charge of the disaster prevention plan has actually completed the necessary actions, and can be used to detect performance omissions and for subsequent re-notification or alternative responses.

[0115] <Selection process for alternative person in charge> Next, the process for selecting an alternative person in charge will be described with reference to Figures 1 and 7. In this embodiment, when a determination is made that a task has not been performed or has not been responded to, the determination unit 13 can refer to the alternative person in charge candidate table 54 stored in the planning information database 50 and select an alternative person in charge to perform the task on behalf of the task based on the location information 70, work information 71, authority information 72, and hazardous area information 73 acquired by the information acquisition unit 11.

[0116] A non-response determination refers to a situation where, for example, after a notification 80 or re-notification 81 is sent by the notification control unit 14, the person in charge terminal 30 does not send a receipt confirmation, response, or proof of performance 90 within a predetermined response deadline. Furthermore, a non-performance determination refers to a situation where, as described in "0109" above, the necessary proof of performance 90 is not obtained within a predetermined time, the obtained proof of performance 90 does not meet the required conditions, or the equipment status sensor information 94 does not reach a predetermined state. In addition, the determination unit 13 can start the process of selecting an alternative person in charge if the person in charge sends a response of "unable to respond", the person in charge terminal 30 is in a communication failure state, or it is determined that the person in charge is located in a hazardous area and on-site response is difficult.

[0117] When the determination unit 13 starts the process of selecting a replacement person in charge, it first refers to the replacement person in charge candidate table 54 and, if necessary, the person in charge ranking table 53, and extracts a group of candidates associated with the relevant task. Here, the replacement person in charge candidate table 54 stores candidate ranking, person in charge identifier, department, area in charge, required authority, required qualifications, working conditions, replacement activation conditions, and switching restriction conditions, so the determination unit 13 can generate an initial list of candidates according to the planned replacement ranking. Note that this group of candidates may include not only those who have been registered as replacement persons in advance, but also those ranked next in the person in charge ranking table 53.

[0118] Next, the determination unit 13 refers to the work information 71 for each candidate included in the initial list and determines whether they are currently available to respond. For example, individuals who are off duty, on vacation, on a business trip, or prohibited from engaging in disaster response can be excluded from the candidate list or have their priority lowered. On the other hand, individuals who are on duty, within the emergency mobilization period, or who have been pre-registered as disaster response personnel can maintain or increase their priority. This allows for the exclusion of individuals who, while candidates in the plan, are actually unable to work.

[0119] Furthermore, the determination unit 13 can refer to the location information 70 and the hazardous area information 73 to evaluate the positional relationship between each candidate's current location and the target facility or target area. For example, those who are close to the target facility, have a short estimated arrival time, or are located in an area adjacent to the target area can be given high priority, while those located in flood-prone areas, landslide-prone areas, or other hazardous areas where it is difficult to reach the site can be given low priority or excluded. In addition, if difficulty of passage is predicted based on the hazardous area information 73, the priority may be adjusted not by simple distance, but by considering the presence or absence of an accessible route or the estimated travel time.

[0120] Furthermore, the determination unit 13 refers to the authority information 72 and determines whether each candidate possesses the necessary equipment operation authority, access authority, approval authority, or qualifications to carry out the relevant task. For example, in the task of confirming the start of a drainage pump, only those with equipment operation authority can be kept as candidates; in the task of opening an evacuation center, priority can be given to those with facility unlocking authority or operational responsibility authority; and in the task concerning equipment handling hazardous materials, those without the necessary qualifications can be excluded from the candidates. This ensures that the person selected as the substitute person in charge is actually able to carry out the relevant task lawfully and effectively.

[0121] The determination unit 13 may calculate the suitability of each candidate as a replacement based on the filtering results using the work information 71, location information 70, hazardous area information 73, and authority information 72. For example, the candidate's ranking in the plan, estimated arrival time to the target facility, work availability, whether necessary authority is met, whether hazardous areas can be avoided, and the current response burden can be scored, and candidates can be ranked based on the total score or weighted evaluation value. In this case, the candidate's ranking in the plan is used as the base score, and points are added or subtracted according to the actual feasibility of responding, thereby enabling the selection of a replacement person in a manner that reflects the actual situation while maintaining consistency with the disaster prevention plan.

[0122] The determination unit 13 determines the candidate with the highest priority as the substitute responsible person based on the ranking results and outputs the decision result to the notification control unit 14. The notification control unit 14 can send an escalation notification 82 to the substitute responsible person. This escalation notification 82 may include the content of the task to be handled, the notification history to the original responsible person, the reason for non-response or non-performance, the type of performance evidence 90 required, and the deadline for the substitute's response. This allows the substitute responsible person to understand the circumstances of the handover and immediately begin the necessary actions.

[0123] On the other hand, if no suitable candidates exist as a result of the filtering, or if all extracted candidates are unresponsive or unable to respond, the determination unit 13 may output a plan deviation alert 83 to the administrator terminal 40 and instruct it to notify a higher-level administrator or overall manager. For example, the determination unit 13 may display on the administrator terminal 40 that there is no alternative person responsible for the task, the reason for exclusion, and the missing authority or personnel requirements. This makes it possible for administrators to make manual interventions based on individual judgment in exceptional situations that cannot be handled by a normal disaster prevention plan.

[0124] Furthermore, the determination unit 13 and the record management unit 15 can record the process of selecting a replacement person in the audit log database 60. Specifically, they can record the identification of the task to be selected, the start time of the selection, the reason for the original person's non-response or non-performance, the list of extracted candidates, the reason for exclusion or evaluation result for each candidate, the final selected replacement person, and the notification time in chronological order. This allows for later verification of whether the selection of the replacement person was appropriate and can be used to revise the disaster prevention plan or modify the candidate selection.

[0125] As shown in Figure 7, the process for selecting an alternative person in charge according to this embodiment can be implemented by including, for example, a step of receiving a non-response determination or non-performance determination, a step of extracting a group of candidates from the alternative person in charge candidate table 54 and the person in charge ranking table 53, a step of narrowing down the candidates based on work information 71, location information 70, authority information 72 and hazardous area information 73, a step of evaluating the suitability of each candidate to act as an alternative person in charge, a step of determining the alternative person in charge, and a step of outputting the decision result to the notification control unit 14 and the record management unit 15.

[0126] Thus, according to the alternative person selection process of this embodiment, when a non-performance determination or non-response determination is made, in addition to the planned alternative ranking, an alternative person who can actually respond can be selected based on location information 70, work information 71, authority information 72, and hazardous area information 73. This makes it possible to quickly initiate appropriate alternative responses in accordance with the actual situation even if a person in charge is designated in the disaster prevention plan but is unable to respond, thereby suppressing delays in response during a disaster.

[0127] <Performance records, audit logs, and plan deviation alerts by the Records Management Department> Next, with reference to Figures 1 and 9, the process by which the Record Management Unit 15 generates performance records, audit logs, and plan deviation alerts 83 will be described. The Record Management Unit 15 is a functional unit that receives various event information output from the notification control unit 14, the determination unit 13, and the information acquisition unit 11, records the responses and performance evidence 90 obtained from the person in charge terminal 30 for each corresponding task, generates performance records and audit logs, and generates a plan deviation alert 83 if there is a deviation from the order, conditions, or responsibilities defined in the disaster prevention plan.

[0128] The record management unit 15 can record information about each event in the audit log database 60 whenever an event occurs, such as sending notification 80, sending re-notification 81, sending escalation notification 82, receiving confirmation of receipt from the person in charge's terminal 30, receiving the response content, receiving the performance evidence 90, determining non-performance, selecting an alternative person in charge, and determining performance. This allows for the tracking and preservation of the progress of each response task from the occurrence of a disaster to completion or determination of non-performance.

[0129] The performance record generated by the record management unit 15 includes, for example, the corresponding task identifier, disaster type, target area or facility, time the issuance conditions were met, the notified person identifier, notification time, response content, time of receipt of performance evidence 90, time of determination of completion, time of determination of non-completion, whether a switch to an alternative person in charge occurred, the time of the switch, and the reason for the switch. Furthermore, if necessary, the communication route used, arrival confirmation result, number of retransmissions, whether an administrator intervened, or the details of manual changes may also be included. This makes it possible to systematically maintain the results of the disaster prevention plan's implementation itself as a performance record, rather than merely a notification history.

[0130] The audit log database 60 records individual events constituting the performance record, associated with, for example, an event identifier, event type, time of occurrence, corresponding task identifier, responsible person identifier, target area identifier, and related reason code. Event types can be set to include, for example, initial notification transmission, re-notification transmission, escalation notification transmission, reception confirmation, response commencement response, response impossible, location arrival information 91 reception, image information 92 reception, checklist completion information 93 reception, equipment status sensor information 94 reception, non-performance determination, performance determination, alternative responsible person determination, and plan deviation alert 83 generation.

[0131] The record management unit 15 can generate an audit log by arranging each of the aforementioned events in the order in which they occurred. For example, for a particular response task, by arranging the time when the issuance conditions were met, the time when notification 80 was sent, the time when receipt was confirmed, the content of the response, the time when the re-notification 81 was sent, the time when the escalation notification 82 was sent, the time when each of the performance evidence 90 was received, the time when the non-performance was determined, the time when the alternative person in charge was decided, and the time when the performance was determined to have been completed in chronological order, an audit log can be generated that allows for a quick understanding of how the response task was carried out.

[0132] Furthermore, the record management unit 15 can record not only the notification time, re-notification time, escalation time, and switch time, but also reason information associated with each event. For example, for re-notification 81, the reason for the switch can be recorded as a reason code or explanation, such as "no confirmation of receipt within the response deadline," for escalation notification 82, "insufficient evidence of performance" or "original person in charge is in the hazardous area," and for the switch to an alternative person in charge, "insufficient authority to operate equipment" or "outside of working hours." This makes it possible to objectively verify, after a disaster response, why a different person, rather than the original person in charge according to the disaster prevention plan, took over the response.

[0133] Furthermore, the record management unit 15 can store the performance evidence 90 in association with the audit log. For example, for location arrival information 91, the arrival time and arrival location can be recorded; for image information 92, the time of capture and image identification information can be recorded; for checklist completion information 93, the completion status and input time of each item can be recorded; and for equipment status sensor information 94, the time of change of equipment status and status value can be recorded, each associated with the corresponding task. This allows the implementation status of each corresponding task to be confirmed with actual performance evidence, rather than just textual information, when the audit log is referred to later.

[0134] In addition to generating the audit log, the Record Management Unit 15 can perform a plan deviation determination process to detect deviations from the order, conditions, or responsibilities defined in the disaster prevention plan. Specifically, the Record Management Unit 15 refers to the responsible person ranking table 53, the issuance condition table 52, the alternative responsible person candidate table 54, and the performance evidence type table 55 stored in the plan information database 50, and determines whether the actual notification order, responsible person, issuance time, and the contents of the performance evidence 90 are consistent with the plan information.

[0135] For example, if a task is scheduled to receive an initial notification from the first person responsible, but in reality the initial notification is sent to the second person responsible or an alternate person responsible, the Record Management Unit 15 can determine whether the notification order is consistent with the person responsible priority table 53. In this case, if the change is based on conditions pre-stored in the planning information database 50 as priority change conditions or alternate activation conditions, the Record Management Unit 15 may record the change in the audit log as an acceptable switch and, if necessary, treat it as minor plan deviation information. On the other hand, if the change is not based on predefined conditions, the Record Management Unit 15 can generate a plan deviation alert 83 as an undefined plan deviation.

[0136] Furthermore, if a notification is sent despite the planned issuance conditions not being met, or if a notification is not sent within a predetermined time despite the issuance conditions already being met, the record management unit 15 can generate a plan deviation alert 83 as a condition deviation. For example, if the difference between the time when the hourly rainfall or water level reaches the issuance conditions and the time when the notification 80 is sent exceeds a predetermined time, or if a slope patrol task is initiated while landslide disaster warning information has not yet been issued, this can be recorded as a condition deviation or timing deviation.

[0137] Furthermore, if a performance determination is made despite a lack of performance evidence 90 required by the plan, or if a task is deemed completed based only on evidence that is not actually necessary, the record management unit 15 can generate a plan deviation alert 83 as a deviation from the performance determination. For example, in a drainage equipment inspection task, if both image information 92 and equipment status sensor information 94 are required, but the task is deemed completed based only on image information 92, the determination can be treated as a deviation from the plan.

[0138] When generating a plan deviation alert 83, the record management unit 15 can identify the type of deviation, the corresponding task identifier where the deviation occurred, the person responsible, the time of deviation detection, related events, and the reason for the deviation, and output them to the administrator terminal 40. Examples of deviation types include sequence deviation, assigned task deviation, condition deviation, deadline deviation, performance trail deviation, or manual change deviation. The administrator terminal 40 may display a list of these deviations, color-coded or displaying warnings according to priority or severity.

[0139] Furthermore, the records management unit 15 may determine the severity of the plan deviation alert 83. For example, a change of responsibility based on predefined priority change conditions can be assigned a low severity rating, an unaddressed state due to the lack of a substitute responsible person can be assigned a high severity rating, and the failure to perform a high-priority task related to the protection of human life can be assigned the highest severity rating. This makes it easy for managers to determine which deviations require immediate attention.

[0140] Furthermore, the records management unit 15 can also record the history of manual interventions or exceptional approvals by administrators in the audit log database 60. For example, if an administrator changes the usual priority order of responsible persons and manually notifies a specific person, or if they exceptionally approve a partial deficiency in the performance evidence 90 and treat it as completed, the time of the operation, the content of the operation, the approver's identification information, and the reason can be recorded. This allows for verification of the validity of human interventions in addition to automated processing at a later date.

[0141] As shown in Figure 9, the administrator terminal 40 can display a list of the completion status of each response task, audit log details, and plan deviation alerts 83. For example, the completion status list screen can display the response task name, current person in charge, status, last update time, and whether there is a deviation; the audit log screen can display time-series events; and the plan deviation alert screen can display the deviation type, severity, reason, and recommended action. This allows administrators to grasp the progress of disaster response and deviations from the disaster prevention plan in real time.

[0142] As described above, the record management unit 15 according to this embodiment performs an audit log generation process that records notification time, response content, performance evidence 90, re-notification time, escalation time, reason for switching, etc. in chronological order, and is configured to generate a plan deviation alert 83 when there is a deviation from the order, conditions, or responsibilities defined in the disaster prevention plan. This allows for the preservation of the disaster response implementation status in a manner that can be verified retrospectively, while promptly notifying administrators of deviations from the plan when a disaster occurs, prompting necessary corrective measures or manual intervention.

[0143] <Example of the screen on the employee's terminal> Next, with reference to Figures 1 and 8, examples of screens displayed on the operator terminal 30 will be described. When the operator terminal 30 receives notification 80, re-notification 81, or escalation notification 82, it can display at least a notification reception screen, a corresponding task confirmation screen, a performance trail registration screen, and an incomplete warning screen. These screens may be configured as multiple screens on a dedicated application, or as multiple areas or tabs within a single screen.

[0144] The notification screen displays, for example, the name of the task to be addressed, the type of disaster, the target area or facility, the reason for issuance, the notification time, the response deadline, the performance deadline, and an overview of the required evidence of performance 90. For example, the notification screen for a drainage facility inspection task during heavy rainfall can display information such as "Drainage facility inspection," "Target facility A," "Issued due to exceeding the hourly rainfall limit," "5 minutes remaining until the response deadline," "15 minutes remaining until the performance deadline," and "Submission of location arrival information 91 and image information 92 is required." This allows the person in charge to understand what needs to be done, where, and by when immediately after receiving the notification.

[0145] The notification reception screen may also display an operation section for receiving response input from the person in charge. This operation section may display buttons such as "Respond," "Unable to Respond," or "Checking." If "Respond" is selected, the person in charge terminal 30 sends the response content and response time to the management server 10 and can transition to the task confirmation screen. If "Unable to Respond" is selected, the person in charge terminal 30 can display a reason selection screen or a free-text input field and send reasons such as poor health, being in a remote location, insufficient authority, or other reasons to the management server 10. If "Checking" is selected, it is recorded as a temporarily held response and the remaining time until the response deadline can be continuously displayed.

[0146] The task confirmation screen displays detailed information about the task. For example, it can display the response procedure, details of the target equipment or area, priority actions, precautions, type of required proof of performance 90, contact information, emergency contact information, and remaining time until the deadline. In addition, if necessary, map information, a floor plan of the target facility, identification information of the target equipment, hazardous area information 73, or a summary of the checklist may be displayed. This allows the person in charge to easily confirm the specific details of the response task before heading to the site or after arriving at the site.

[0147] The task confirmation screen may also display the status of the task in question. For example, the current status can be displayed as "Not started," "In transit," "In progress," "Waiting for evidence submission," or "Completion reported." In addition, if parallel notifications have been issued, it may be displayed whether another person is already working on the task, or whether a switch to an alternative person in charge has occurred. This helps to prevent multiple people from working on the same task redundantly, while encouraging collaborative work when necessary.

[0148] The performance evidence registration screen displays an input area for registering performance evidence 90. For example, for location arrival information 91, the system can be configured to acquire and transmit the current location by pressing the "Record Arrival" button. For image information 92, a capture button or image selection button may be displayed to allow the user to take and transmit on-site photos or equipment photos. For checklist completion information 93, a completion check field, an abnormality / absence selection field, or comment input field may be displayed for each confirmation item, allowing the person in charge to input information sequentially. Furthermore, for equipment status sensor information 94, the communication results with external equipment or automatically acquired results may be displayed, allowing the person in charge to confirm the status before performing the transmission operation.

[0149] The performance evidence registration screen may include a display area showing the submission status of the required performance evidence 90. For example, it may display statuses such as "Location arrival information: Submitted," "Image information: Not submitted," "Checklist: In progress," and "Equipment status: Successfully acquired." Furthermore, if a required performance evidence 90 has not been submitted, the missing item may be highlighted, and the system may be prevented from submitting a completion report. This makes it easier for the person in charge to recognize which performance evidence 90 has not been submitted, and makes it easier to avoid a judgment of non-performance due to insufficient evidence.

[0150] The incomplete warning screen is displayed when the response deadline or performance deadline is approaching, or when the necessary performance evidence 90 is missing. For example, it may display warning messages such as "3 minutes remaining until the performance deadline," "Image information has not been submitted," or "There are incomplete items on the checklist," and may also provide warning sounds, vibrations, or color coding as needed. The incomplete warning screen may also display controls such as "Submit now," "Report inability to respond," or "Contact administrator." This helps to alert the person in charge of exceeding the deadline or lacking evidence, thereby preventing missed performances.

[0151] Furthermore, when the employee terminal 30 receives an escalation notification 82, it may display a highlighted screen different from the normal notification screen. For example, it may display that alternative action is required due to the original person in charge's failure to respond or perform, the deadline for the alternative action, the actions already taken, and the details of the missing performance evidence 90. This allows the alternative person in charge to immediately understand the matters that need to be handed over and to begin addressing the missing tasks while avoiding duplicate work.

[0152] Thus, the personnel terminal 30 according to this embodiment can consistently support operations from notification reception to performance evidence registration and completion reporting by displaying a notification reception screen, a corresponding task confirmation screen, a performance evidence registration screen, and an incomplete warning screen, etc. Therefore, through the screen configuration of the personnel terminal 30, the specific manner of terminal operation by the personnel can be clearly defined, while ensuring reliable implementation of responses based on the disaster prevention plan and appropriate collection of performance evidence 90.

[0153] <Example of administrator terminal screen> Next, with reference to Figures 1 and 9, examples of screens displayed on the administrator terminal 40 will be described. Figure 9 shows an example of the performance status list screen, audit log screen, and plan deviation alert display screen, which are among the multiple screens displayed on the administrator terminal 40. The administrator terminal 40 is a terminal for overall control and monitoring of the disaster response performance management system 1, and can display at least the disaster status list screen, the running task list screen, the responsible person response status display screen, the performance status display screen, the audit log screen, and the plan deviation alert display screen. These screens may be displayed as multiple areas within a single dashboard screen, or they may be displayed as individual screens that can be switched between.

[0154] The disaster status list screen displays a list of currently monitored disaster types, affected areas, warning types, risk levels, issuance times, and latest update times. Specifically, for each disaster type, such as heavy rain, floods, and landslides, it can display the affected areas, weather information, local government warnings, rainfall information, water level information, or landslide-related information, as well as whether thresholds have been exceeded. It can also display areas in different colors according to their risk level, with areas experiencing serious disasters being shown at the top. This allows administrators to quickly understand which areas are experiencing high risks for which types of disasters.

[0155] The list of running tasks screen displays a list of currently running response tasks. For example, it can display the task name, disaster type, target facility or area, time the issuance conditions were met, current person in charge, notification status, priority, and completion deadline. In addition, for each response task, it may display the status such as notification not sent, notified, awaiting response, in progress, performance trail being checked, completed, or not yet completed. This allows administrators to immediately understand which response tasks are currently in progress and which tasks are experiencing delays or stagnation.

[0156] The screen displaying the response status of the person in charge shows the response status of the person in charge or their substitute in charge who was notified about each task. For example, it can display the name or identification information of the person who was notified, their responsibility category, notification time, whether or not the notification was received, the content of the response, the number of re-notifications, and whether or not an escalation was carried out. In addition, the response content may be categorized as "to be handled," "unable to handle," "under review," or no response. Furthermore, if multiple persons in charge have been notified in parallel, the response time and acceptance status for each person in charge may also be displayed. This allows administrators to easily understand who has taken on the task, who has not responded, and where escalation is needed.

[0157] The performance status display screen shows the performance evidence 90 and performance judgment results obtained for each corresponding task. For example, it can display whether location arrival information 91 has been submitted, whether image information 92 has been submitted, the input status of checklist completion information 93, the acquisition status of equipment status sensor information 94, and judgment results such as completed, not completed, or insufficiently completed. In addition, if there is a shortage of performance evidence 90, the details of the shortage may be clearly indicated. For example, phrases such as "image information not submitted," "equipment status not confirmed," or "checklist items not completed" can be displayed. This allows administrators to understand not only the response status but also the specific extent to which the work has actually been completed.

[0158] The audit log screen displays events related to each task in chronological order. For example, it can display the time when the order conditions were met, the time when notification 80 was sent, the time when it was received, the content of the response, the time when the re-notification 81 was sent, the time when the escalation notification 82 was sent, the time when the performance evidence 90 was received, the time when the task was determined to be unfulfilled, the time when the alternative person in charge was decided, and the time when the task was determined to be fulfilled, in that order. In addition, information related to the reason for each event, such as the communication path, the reason for the switch, or whether or not there was manual intervention by the administrator may be added. This allows the administrator to track how each task reached its current state and to determine corrective actions as needed.

[0159] The plan deviation alert display screen shows a list of plan deviation alerts 83 generated by the record management unit 15. For example, the deviation type, corresponding task name, responsible person, deviation detection time, severity, and reason for deviation can be displayed. The deviation type may include sequential deviation, assigned deviation, condition deviation, deadline deviation, or performance evidence deviation. In addition, the alerts may be color-coded, flashed, or have a warning sound output depending on their severity. This allows administrators to quickly identify where deviations from the disaster prevention plan have occurred and select cases that require priority intervention.

[0160] The administrator terminal 40 can display the aforementioned screens in an interconnected manner. For example, selecting a specific area displayed on the disaster situation list screen will transition to a screen showing a list of ongoing tasks related to that area. Furthermore, selecting a specific response task will display a detailed screen showing the response status of the person responsible for that response task, its performance status, audit logs, and plan deviation alerts. Through such screen transitions, the administrator can consistently perform tasks ranging from understanding the overall disaster situation to checking the details of individual tasks.

[0161] Furthermore, the administrator terminal 40 may display an operation panel that accepts intervention operations by the administrator as needed. For example, an operation panel may be provided for manually changing the recipient of notifications, changing the order of notifications, executing additional notifications, manually designating an alternate responsible person, approving exceptions, or inputting the status of responses to plan deviation alerts 83. This allows the administrator to intervene manually in a timely manner to maintain overall control, even if the disaster situation changes rapidly or an exceptional situation occurs that cannot be absorbed by the normal disaster prevention plan.

[0162] Furthermore, the administrator terminal 40 may filter the displayed items, display them in order of priority, display them by area, display them by type of disaster, or display them by department in charge. For example, it may extract and display only high-severity plan deviation alerts 83, display only response tasks with approaching deadlines in a list, or display only the response status for a specific area on a map. This allows administrators to quickly grasp the necessary information and perform monitoring and control according to priority, even when many response tasks are progressing simultaneously.

[0163] Thus, the administrator terminal 40 according to this embodiment can support the control and monitoring of the entire disaster response performance management system 1 through the display of a disaster status list, a list of ongoing tasks, the response status of responsible persons, performance status, audit logs, and plan deviation alerts. Therefore, when a disaster occurs or there is a risk of a disaster occurring, the administrator can centrally grasp the disaster status, manage the progress of response tasks, detect omissions in performance, and respond to plan deviations.

[0164] <Specific example of a processing flow> Next, referring to Figure 10, a specific example of the processing flow in the disaster response performance management system 1 according to this embodiment will be described, using the case of a flood risk due to heavy rain as an example. This specific example shows a series of steps from acquiring weather information to initiating response tasks, notifying the person in charge, acquiring performance evidence 90, determining non-performance, switching to an alternative person in charge, and recording audit logs.

[0165] In this specific example, it is assumed that disaster prevention plans for heavy rain or flooding are pre-registered in the planning information database 50. For example, in target area A, the "drainage facility inspection task" is stored in the corresponding task table 51, with the conditions for issuing an alert being that the hourly rainfall is above the first threshold or that the river water level is above the warning level. Furthermore, for the said drainage facility inspection task, the person in charge ranking table 53 is stored as the person in charge of terminal 31 as the first person in charge, and the person in charge of terminal 32 as the second person in charge, and the person in charge of terminal 33 is stored as a candidate for the alternative person in charge table 54. In addition, the performance evidence type table 55 is stored as indicating that location arrival information 91, image information 92, and equipment status sensor information 94 are required as performance evidence 90 for the said drainage facility inspection task.

[0166] First, at time t1, the information acquisition unit 11 acquires weather information from the weather information distribution server 21 indicating that the hourly rainfall in target area A has exceeded a first threshold. Next, at time t2, the information acquisition unit 11 acquires water level information from the water level sensor 24 indicating that the river water level has reached a warning level, and further acquires flood warnings or evacuation information for target area A from the local government warning distribution server 22. This information is stored in the management server 10, associated with the acquisition time, target area identifier, and disaster type.

[0167] The determination unit 13 refers to the issuance condition table 52 based on the hourly rainfall information acquired at time t1 and determines that the conditions for issuing a drainage facility inspection task have been partially met. Then, based on the water level information and local government warnings acquired at time t2, it determines that the level of danger has increased and the conditions for issuing a task have been fully met, and decides to activate the drainage facility inspection task. At this time, the determination unit 13 may plan to sequentially notify the first responsible person before the level of danger increases, but after the level of danger increases, it can determine that both the first responsible person terminal 31 and the second responsible person terminal 32 are to be notified, as the conditions for parallel notification are met.

[0168] The notification control unit 14 sends a notification 80 to the first responsible terminal 31 and the second responsible terminal 32 at time t3 based on the notification execution instruction from the determination unit 13. The notification 80 includes information such as, for example, "Drainage facility inspection task," "Drainage facility B in target area A," "Issued due to exceeding the hourly rainfall limit and rising river water level," "Response deadline is 5 minutes from now," "Completion deadline is 15 minutes from now," and "Submission of location arrival information 91, image information 92, and equipment status sensor information 94 is required." This allows each responsible person to understand the actions to be taken and the content of the necessary evidence of completion 90.

[0169] At time t4, the person in charge of the first responsible terminal 31 responds with "I will respond" via the notification reception screen, and then transmits location arrival information 91 as a result of heading to the site. On the other hand, the person in charge of the second responsible terminal 32 does not receive confirmation of receipt or a response within the response deadline. In this case, the notification control unit 14 records the second responsible terminal 32 as unresponded and manages the first responsible terminal 31 as in a responding state.

[0170] However, even if the performance deadline has passed at time t5, the image information 92 and equipment status sensor information 94 have not been acquired from the first responsible terminal 31. The determination unit 13 refers to the performance evidence type table 55 and confirms that location arrival information 91, image information 92, and equipment status sensor information 94 are essential for the drainage equipment inspection task. Since location arrival information 91 alone does not satisfy the performance requirement, it determines that the drainage equipment inspection task by the person in charge at the first responsible terminal 31 has not been performed. The second responsible terminal 32 is maintained as unresponsive. Thus, in this embodiment, the determination of unperformed tasks is made based on whether the necessary performance evidence 90 is satisfied, rather than simply acknowledging receipt or responding with "we will respond."

[0171] Next, the determination unit 13 refers to the alternative responsibility candidate table 54 and extracts the person in charge of the alternative responsibility terminal 33 as a candidate. Then, it refers to the location information 70, work information 71, authority information 72, and hazardous area information 73 to confirm that the person in charge is relatively close to the target area A, is on duty, has the authority to operate the drainage facility B, and can be safely reached from outside the hazardous area. Based on these evaluation results, the determination unit 13 selects the person in charge of the alternative responsibility terminal 33 as the alternative responsibility and outputs the decision result to the notification control unit 14.

[0172] The notification control unit 14 sends an escalation notification 82 to the alternate responsible person terminal 33 at time t6. In addition to the details of the drainage equipment inspection task, the escalation notification 82 may include handover information such as the fact that only location arrival information 91 has been obtained from the first responsible person terminal 31, and image information 92 and equipment status sensor information 94 have not been submitted, that the second responsible person terminal 32 has not responded, and that an alternate response deadline has been set. This allows the alternate responsible person to understand the tasks that are currently incomplete and to promptly begin the necessary actions.

[0173] At time t7, the person in charge of the alternate responsible person terminal 33 transmits location arrival information 91 after arriving at the site, as well as image information 92 of the state of the drainage facility B, and further transmits to the management server 10 that the equipment status sensor information 94 acquired from the equipment monitoring device indicates that it is operating normally. The determination unit 13 confirms that these performance evidence 90 satisfy the essential conditions stored in the performance evidence type table 55 and determines that the drainage facility inspection task has been completed. Subsequently, the record management unit 15 can register the completed determination result as a performance record and display it on the administrator terminal 40.

[0174] The recording management unit 15 records in chronological order in the audit log database 60 at least the acquisition of information on exceeding the hourly rainfall limit at time t1, acquisition of information on rising river levels and local government warnings at time t2, transmission of notification 80 at time t3, reception of the response of the first person in charge and location arrival information 91 at time t4, the unresponsive status of the second person in charge, the determination of non-performance and unresponsiveness at time t5, selection of an alternative person in charge and transmission of escalation notification 82 at time t6, and reception of location arrival information 91, image information 92, and equipment status sensor information 94 and the determination of performance at time t7. In addition, the reason for switching from the first and second person in charge to an alternative person in charge can be recorded as "insufficient evidence of performance" and "unresponsiveness".

[0175] Furthermore, if the switch to the alternative person in charge conforms to the alternative activation conditions and priority change conditions pre-stored in the alternative person in charge candidate table 54, the record management unit 15 can record the switch as an permitted switch in the audit log. On the other hand, if the switch does not conform to the predefined conditions, or if there is no suitable alternative person in charge, the unit can generate a plan deviation alert 83 and output it to the administrator terminal 40. In this specific example, since the switch to the person in charge of the alternative person in charge terminal 33 is performed based on the plan information, the plan deviation alert 83 may not be generated.

[0176] Thus, according to this specific example, a series of processes, from acquiring weather information and water level information related to heavy rain or flooding, to initiating drainage facility inspection tasks, notifying responsible persons, acquiring performance evidence 90, determining non-performance, switching to alternative responsible persons, and recording audit logs, can be carried out integrally by the disaster response performance management system 1. Therefore, even if the responsible person specified in the disaster prevention plan responds, it will not be determined as completed unless the necessary performance evidence 90 is insufficient, and a switch can be made to an alternative responsible person who is actually able to respond. This suppresses omissions in the implementation of the disaster prevention plan and enables effective disaster response during heavy rain or flooding.

[0177] <Variation> It should be noted that the present invention is not limited to the embodiments and specific examples described above, and various modifications are possible without departing from its essence. For example, the present invention can be applied to local governments, companies, schools, hospitals, and various other organizations, and the type of input information, the content of the corresponding tasks, the type of performance evidence 90, the notification order, or the selection criteria for the substitute responsible person can be appropriately changed depending on the nature of the target organization.

[0178] In the application to local governments, the information acquisition unit 11 may acquire not only weather information, local government warnings, rainfall information, water level information, and landslide-related information, but also information on the status of evacuation center openings, road traffic restriction information, information on evacuees by region, hazard map information, or information transmitted via disaster prevention radio. In this case, the corresponding tasks can be set to include opening evacuation centers, guiding residents to evacuate, checking sluice gates or drainage pump stations, setting sandbags, and patrolling dangerous areas. Furthermore, as evidence of performance 90, evacuation center opening photos, opening checklists, evacuation guidance completion reports, equipment status sensor information 94, or location arrival information 91 indicating arrival at the site can be used.

[0179] In a corporate application, the information acquisition unit 11 may acquire, in addition to weather information and local government warnings, information on the operation of factory equipment, power outage information, emergency power supply status, entry / exit information, manufacturing line stoppage information, storage status information for chemicals or hazardous materials, etc. In this case, the corresponding tasks can be set to include equipment stoppage confirmation, emergency power supply activation confirmation, hazardous material preservation, drainage equipment inspection, employee safety confirmation, or support for decision-making regarding suspension of operations. Furthermore, as evidence of performance 90, equipment stoppage logs, surveillance camera images, equipment status sensor information 94, work checklists, or on-site confirmation photographs can be used.

[0180] In a school-oriented application, the information acquisition unit 11 may acquire information on students, attendance, equipment status for each school building, and the status of the school broadcasting equipment, in addition to weather information, local government warnings, and information on dangerous areas related to school routes or school districts 73. In this case, the corresponding tasks can be set to include student evacuation guidance, school building safety checks, school route inspections, contact with parents, and confirmation of the opening of evacuation sites. Furthermore, the evidence of performance 90 can include information on the completion of roll call for each class, information on arrival at evacuation sites, evacuation guidance completion checklists, school building inspection photos, or equipment status sensor information 94.

[0181] In a hospital application, the information acquisition unit 11 may acquire weather information, local government warnings, emergency power supply status information, medical equipment operation information, staffing information for each ward, patient transport target information, or equipment malfunction information. In this case, the corresponding tasks can be set to include emergency power supply confirmation, ward safety confirmation, patient transport preparation, medical equipment continuous operation confirmation, stockpiled medicine confirmation, or changes to the acceptance system. Furthermore, as evidence of performance 90, information on completion of ward rounds, medical equipment status logs, patient transport checklists, equipment status sensor information 94 indicating the operating status of the emergency power supply, or on-site confirmation image information 92 can be used.

[0182] Thus, the content of the input information and performance evidence 90 may differ for each target organization, and the planning information storage unit 12 can store different response tasks, issuance conditions, responsible person rankings, alternative responsible person candidates, and performance evidence types for each organization or facility. Therefore, the present invention can be applied to various disaster prevention plans or business continuity plans by replacing the necessary input information and performance evidence 90 for each organization while maintaining the same basic configuration.

[0183] Furthermore, while the above embodiment exemplified the weather information distribution server 21, the local government warning distribution server 22, the rainfall sensor 23, the water level sensor 24, and the landslide sensor 25, the external information sources 20 acquired by the information acquisition unit 11 are not limited to these. For example, the acquisition targets may include surveillance camera video analysis results, road flooding detection devices, building tilt detection devices, power outage monitoring devices, equipment management systems, access control systems, attendance management systems, or wide-area disaster information shared by other organizations. Even in this case, the determination unit 13 can use this additional information as issuance conditions, priority change conditions, or alternative responsibility selection conditions.

[0184] Furthermore, the system configuration of the present invention may be either a cloud configuration or an on-premises configuration. For example, the management server 10, the planning information database 50, and the audit log database 60 may be located on a cloud computing environment and made available via the network from the employee terminal 30 and the administrator terminal 40 in a cloud configuration. On the other hand, the server group may be located within a facility such as a municipal government building, corporate facility, school, or hospital, and operated on a closed network or an internal facility network in an on-premises configuration. Alternatively, some information processing functions may be located on the cloud, while sensitive information or audit logs are kept within the facility in a hybrid configuration.

[0185] A cloud-based configuration facilitates centralized management of disaster prevention plans across multiple locations and is suitable for obtaining weather information or local government warnings over a wide area. On the other hand, an on-premise configuration is suitable for integration with on-site equipment, minimizing communication delays, and maintaining sensitive information within the facility. Therefore, the appropriate deployment configuration can be selected according to the target organization's operational policies, communication environment, information management requirements, or equipment configuration.

[0186] Furthermore, the determination unit 13 may also be equipped with an AI determination function in addition to the rule-based determination function. For example, the machine learning model may use at least the time period, type of disaster, location information 70 of the person in charge terminal 30, work information 71, past response rate, and past performance delay rate as features, and be trained using past disaster response history, audit logs, weather trends, response history, and submission history of performance evidence 90 as training data. The determination unit 13 can output the probability of non-response and the probability of performance delay using the machine learning model.

[0187] For example, if the non-response probability calculated by the machine learning model is equal to or greater than the first threshold α, the determination unit 13 may change the normal notification order based on the responsible person ranking table 53. If the non-response probability is equal to or greater than the second threshold β, it may simultaneously notify the alternative responsible person candidates stored in the alternative responsible person candidate table 54 from the time of the initial notification. Furthermore, if the performance delay probability is equal to or greater than a predetermined threshold, the re-notification time may be brought forward, or it may be displayed as a priority confirmation target on the administrator terminal 40. Moreover, the determination unit 13 does not determine the notified persons, notification order, or performance determination based solely on the output results of the machine learning model, but makes a final decision after confirming consistency with the rules regarding the issuance conditions, responsible person ranking, alternative responsible person candidates, and performance evidence types stored in the planning information storage unit 12.

[0188] Furthermore, the machine learning model may be updated when a new audit log is added to the audit log database 60, or at regular intervals such as daily, weekly, or monthly. In this case, the determination unit 13 may evaluate the accuracy of the updated machine learning model based on the most recent disaster response results and apply it as an operational model only if it meets predetermined performance criteria. This enables the disaster response performance management system 1 to maintain auditability and controllability while achieving notification control and alternative responsibility selection that reflects the latest operational results.

[0189] Furthermore, the present invention is not limited to a form used entirely within a single organization, but may also be used in collaboration with multiple organizations. For example, planning information may be shared between local governments and designated evacuation center operators, corporate headquarters and each branch office, school headquarters and each school building, and hospital headquarters and branch offices, and alternative person-in-charge candidates at other locations may be mutually available for specific response tasks. In this case, the alternative person-in-charge candidate table 54 may also include personnel from other organizations or other locations.

[0190] Thus, the present invention can be modified in various ways in terms of the target of application, input information, performance evidence 90, system deployment configuration, and the specific configuration of the judgment logic. Therefore, the present invention is widely applicable to various disaster prevention plans or business continuity plans for local governments, companies, schools, hospitals, and others, and can realize flexible disaster response performance management according to the operational realities of each organization. [Explanation of symbols]

[0191] 1. Disaster Response Performance Management System 10 Management Server 11 Information acquisition department 12. Planning Information Storage Unit 13 Judgment section 14 Notification Control Unit 15 Records Management Department 16 Communications Department 20 External information sources 21 Weather information distribution server 22 Local government warning distribution servers 23 Rain sensor 24 Water level sensors 25. Sediment Disaster Sensor 30. Personnel terminal 31. Primary Responsible Terminal 32 Second Responsible Terminal 33 Alternative Responsible Person Terminal 40 Administrator terminal 50 Planning Information Database 51 Corresponding Task Table 52 Issuance Conditions Table 53. Ranking Table of Responsible Persons 54 Alternative Responsibility Candidate Table 55 Performance Evidence Type Table 60 Audit Log Database 70 Location information 71 Work Information 72 Permissions Information 73. Hazardous Area Information 80 notifications 81 Reminder 82 Escalation Notification 83 Plan Deviation Alert 90 Proof of Performance 91 Location Arrival Information 92 Image Information 93 Checklist Completion Information 94 Equipment Status Sensor Information

Claims

1. An information acquisition unit that acquires one or more of the following from the Japan Meteorological Agency: weather information, local government warnings, rainfall sensor information, water level sensor information, and landslide sensor information, as well as one or more of the following from the location information, work information, authority information, and hazardous area information related to the terminal of the person in charge. A planning information storage unit stores, for each type of disaster, the corresponding response task, the conditions for issuing the response task, the order of responsible persons, the candidates for alternative responsible persons, the type of evidence of performance, and the prescribed time. A determination unit determines the target task, the person to be notified, and the notification order based on the information acquired by the information acquisition unit and the information stored in the planning information storage unit, and determines whether the task is unfulfilled based on the response and proof of performance acquired from the person to be notified, the type of proof of performance associated with the task, and the predetermined time, and selects an alternative person responsible for the task that is determined to be unfulfilled. A notification control unit transmits at least one of the following to the mobile terminal of the person to be notified, depending on the determination result of the determination unit: The recording management unit records the responses, performance evidence, performance records, and audit logs obtained from the notified persons for each corresponding task, compares the actual notification order, issuance conditions, notification time, or performance evidence conditions with the plan information stored in the plan information storage unit to determine whether there is a plan deviation or the type of deviation, and outputs a plan deviation alert. A disaster response performance management system equipped with the following features.

2. The aforementioned planning information storage unit further stores the correspondence between the risk level for each type of disaster and the corresponding task, calculated by comparing weather information, local government warnings, rainfall information, water level information, and landslide-related information with a predetermined threshold table, as well as the conditions for changing the priority of responsible persons and the conditions for parallel notification according to the risk level. The determination unit calculates the degree of risk by comparing the weather information, the local government warning, the rainfall information, the water level information, and the landslide-related information with the threshold table, and changes the notification order according to the degree of risk, or, if the degree of risk is above a predetermined level, notifies multiple responsible persons in parallel. The disaster response performance management system according to claim 1.

3. The performance evidence includes at least one of the following: location arrival information, image information, checklist completion information, and equipment status sensor information. The determination unit determines that a task is unfulfilled if the performance evidence required for that task is not obtained within a predetermined time, or if the obtained performance evidence does not satisfy the conditions associated with that task. The disaster response performance management system according to claim 1.

4. The determination unit determines that a task is unfulfilled if the required proof of performance for that task is not obtained within a specified time, or if the obtained proof of performance does not satisfy the conditions associated with that task. For the task determined to be unfulfilled, the determination unit selects an alternative person responsible based on at least location information, work information, authority information, and hazardous area information. The record management unit records the notification time, re-notification time, escalation time, response content, performance evidence, performance record, and reason for switching to an alternative person in charge as a time-series audit log, and compares it with the plan information stored in the plan information storage unit. If it detects a deviation type including at least a condition deviation, timing deviation, and performance judgment deviation, it outputs the plan deviation alert to the administrator terminal. The disaster response performance management system according to claim 1.

5. The determination unit uses one or more of the following as features: response history, performance evidence submission history, location information, work information, disaster type, and time period. Based on a machine learning model trained using past disaster response history, audit logs, or performance evidence submission history as training data, the probability of non-response or performance delay is estimated. Depending on the probability of non-response or delay in performance, the order of notifications or the ranking of alternative responsible persons will be changed. The disaster response performance management system according to claim 1, wherein the output results of the machine learning model are confirmed to be consistent with the rules regarding issuance conditions, priority of responsible persons, and alternative responsible persons candidates stored in the planning information storage unit before making a final decision.

6. A disaster response performance management method that is performed by a disaster response performance management system, The information acquisition unit of the disaster response performance management system includes the process of acquiring one or more of the following provided by the Japan Meteorological Agency: weather information, local government warnings, rainfall sensor information, water level sensor information, and landslide sensor information, as well as one or more of the following: location information, work information, authority information, and hazardous area information. The disaster response performance management system includes a step in which the determination unit determines the response task to be activated, the person to be notified, and the notification order based on planning information including the issuance conditions defined for each type of disaster, the order of responsible persons, the candidate for the substitute responsible person, the type of performance evidence, and the predetermined time. The notification control unit of the disaster response performance management system sends a notification to the mobile terminal of the person to be notified, and obtains a response and performance record from the mobile terminal of the person to be notified, The determination unit determines whether the task is unfulfilled based on the response and evidence of performance obtained from the notified person, the type of evidence of performance associated with the task, and the predetermined time, and selects an alternative person responsible for the task that has been determined to be unfulfilled. The notification control unit sends a re-notification or escalation notification to the substitute responsible person, The record management unit of the disaster response performance management system records, for each response task, the responses and performance evidence obtained from the notified persons, the performance records and audit logs, and the actual notification order, issuance conditions, notification time, or performance evidence conditions against the plan information to determine whether there is a deviation from the plan or the type of deviation, and outputs a plan deviation alert. Disaster response performance management methods, including those mentioned above.

7. The computer includes information acquisition means for acquiring one or more of the following from the Japan Meteorological Agency: weather information, local government warnings, rainfall sensor information, water level sensor information, and landslide disaster sensor information, as well as one or more of the following from location information, work information, authority information, and hazardous area information; determination means for determining the response task to be activated, the person to be notified, the notification order, whether or not it has not been performed, and the alternative person to be responsible, based on planning information including issuance conditions defined for each type of disaster, priority of responsible person, candidate for alternative responsible person, type of evidence of performance, and predetermined time; notification control means for transmitting at least one of the following from notification, re-notification, or escalation notification according to the determination result; and A program that functions as a record management means for recording responses, performance evidence, performance records, and audit logs obtained from the aforementioned notified persons for each corresponding task, comparing the actual notification order, issuance conditions, notification time, or performance evidence conditions with the plan information to determine whether there is a deviation from the plan or the type of deviation, and outputting a plan deviation alert.

Images