Information processing device, method, program and system
The management system addresses the challenge of inconsistent evacuee reporting by enabling mode-switched reporting through a shelter terminal and local government terminal, ensuring accurate and timely information management for evacuation centers.
Patent Information
- Application Number
- JP2024210704
- Authority / Receiving Office
- JP · JP
- Patent Type
- Patents
- Current Assignee / Owner
- Filing Date
- 2024-12-03
- Publication Date
- 2025-12-02
- Estimated Expiration
- 2044-12-03
AI Technical Summary
Existing systems face challenges in accurately managing information about the status of evacuation shelters, particularly in reporting the number of evacuees, which is often done manually and inconsistently by local government officials, making it difficult to manage evacuation centers effectively.
A management system that includes a shelter terminal and a local government terminal, utilizing a processor to execute a program for storing and transmitting a report with the number of evacuees, distinguishing between manually entered and tallied numbers, and enabling identification of the reporting mode (approximate or list-based) to ensure accurate reporting.
Enables appropriate management of evacuation shelter information by allowing switching between manual and list-based reporting modes, ensuring accurate and timely reporting of evacuee numbers, thereby facilitating better management of evacuation centers.
Smart Images

Figure 0007778326000001_ABST
Abstract
Description
[Technical Field]
[0001] The present disclosure relates to an information processing device, a method, a program, and a system. [Background technology]
[0002] When a disaster occurs and a shelter is opened, the situation at the shelter must be reported to the local government promptly. For example, Patent Document 1 discloses a calculation device that transmits a response request to terminals in the shelter and calculates the number of terminals that have transmitted the request as the number of evacuees in the shelter. [Prior art documents] [Patent documents]
[0003] [Patent Document 1] International Publication No. 2022 / 065462 Summary of the Invention [Problem to be solved by the invention]
[0004] Information on the situation at evacuation centers is generally reported by those who manage the centers (such as local government officials) via telephone or email, making it difficult for local governments to properly manage information at evacuation centers.
[0005] The purpose of this disclosure is to appropriately manage information indicating the status of evacuation shelters. [Means for solving the problem]
[0006] In order to solve the above problem, one aspect of the present disclosure provides a program for causing a computer including a processor and a memory to execute the program, which causes the processor to execute a storage step of storing a list of evacuees and a transmission step of transmitting a report including evacuation shelters and the number of evacuees to a server, wherein the transmission step transmits the report in a manner that enables identification of whether the number of evacuees included in the report is the number of evacuees tallied in the list of evacuees. [Effects of the Invention]
[0007] According to one aspect of the present disclosure, information indicating the status of an evacuation shelter can be appropriately managed. [Brief explanation of the drawings]
[0008] [Figure 1] FIG. 1 is a diagram illustrating an overview of a management system 1. [Figure 2] FIG. 1 is a hardware configuration diagram of a management system 1. [Figure 3] FIG. 2 is a functional block diagram of the management system 1. [Figure 4] 10 is a flowchart showing the processing steps performed by the evacuation shelter terminal 20 to tally up evacuees by status in the evacuee list 241. [Figure 5] 10 is a flowchart showing a processing procedure in which the evacuation shelter terminal 20 transmits a report to the management server 10. [Figure 6] FIG. 10 is a diagram showing an example of an image displayed until the evacuation shelter terminal 20 transmits a report. [Figure 7] FIG. 10 is a diagram showing an example of a report display screen of the local government terminal 30. [Figure 8] FIG. 2 is a diagram showing an example of a graph displayed by the management system 1. DETAILED DESCRIPTION OF THE INVENTION
[0009] Hereinafter, embodiments of the present disclosure will be described with reference to the drawings. Identical components will be described with the same reference numerals. Note that the following embodiments do not limit the technology of the present disclosure, and not all of the combinations of features described in the embodiments are necessarily essential to solving the above problems.
[0010] [First embodiment] In the first embodiment, a management system is described that tallyes the number of evacuees taking refuge at evacuation shelters and manages information on the evacuation shelter situation including the number of evacuees, and distinguishes between the number of evacuees tallied from the evacuation shelter list and the number of evacuees manually entered.
[0011] <Configuration example of management system 1> The configuration of the management system 1 of the first embodiment will be described. Fig. 1 is a diagram showing an overview of the management system 1 of the first embodiment. As shown in Fig. 1, the management system 1 includes a management server 10, an evacuation shelter terminal 20, and a local government terminal 30.
[0012] The management server 10 is a server that receives information from the evacuation shelter terminal 20 and the local government terminal 30 and performs processing related to the management of the received information. The management server 10 is connected to one or more evacuation shelter terminals 20 and one or more local government terminals 30 via a network N.
[0013] The shelter terminal 20 is a terminal for use by the staff and officers who operate the shelter, local residents who support the shelter operation, and the like (hereinafter referred to as the shelter operator). A shelter is a facility where disaster victims and others take refuge for a certain period of time after a disaster occurs. Examples of the shelter terminal 20 include personal computers and mobile terminals (smartphones, tablet terminals, laptop computers, etc.). The shelter terminal 20 is placed within the shelter (for example, at the entrance or in the operation area of the shelter) or carried by the shelter operator.
[0014] The local government terminal 30 is a terminal managed by the local government to which the evacuation shelter belongs. A local government is a public organization that is authorized to exercise self-governance. Examples of local governments include basic local governments and regional local governments. Examples of the local government terminal 30 include a personal computer and a mobile terminal.
[0015] For example, the local government terminal 30 is a terminal used by an employee of a prefectural office that has jurisdiction over an evacuation shelter. For example, an employee of a prefectural office that has jurisdiction over an evacuation shelter uses the local government terminal 30 not at the evacuation shelter but at the prefectural office or a disaster response headquarters.
[0016] <Hardware configuration of management system 1> FIG. 2 is a hardware configuration diagram of the management system 1. The management server 10 is an information processing device, and can be a general-purpose server computer, a personal computer, or the like. It is also possible to configure the management server 10 using multiple computers. As shown in FIG. 2, the management server 10 physically includes one or more CPUs (Central Processing Units) 110, which are processors, a communication unit 140 such as a communication interface for communicating with memory 120, storage 130, and network N, an input unit 150, and a display unit 160. The hardware components of the management server 10 are connected to each other via a bus.
[0017] The CPU 110 executes programs (described below) stored in advance in the storage 130, causing each piece of hardware to operate under the control of the CPU 110 and realizing each function of the management server 10. The memory 120 temporarily stores programs loaded from the storage 130 and provides a work area for the CPU 110. The memory 120 also temporarily stores various data generated while the CPU 110 is executing the programs. The memory 120 includes, for example, a random access memory (RAM) and a read-only memory (ROM). The storage 130 stores various programs. The storage is, for example, a hard disk drive (HDD) or a solid state drive (SSD). The communication unit 140 transmits and receives various data to and from an external information processing device via a network. The communication may be performed either wired or wirelessly, and any communication protocol may be used as long as mutual communication is possible.
[0018] The input unit 150 has an input device that receives inputs from various operations on the management server 10 and transmits information related to the inputs to the CPU 110. The input device is realized by a touch panel, a mouse, a keyboard, a microphone, etc., and has a function that allows input of text, etc. The display unit 160 has an output device that outputs the processing results of the CPU 110. The output device is a display, a speaker, etc. Note that the input unit 150 and the display unit 160 may be integrated as an input device and an output device, such as a touch panel display.
[0019] The shelter terminal 20 is an information processing device. The hardware configuration of the shelter terminal 20, including a CPU 210, a memory 220, a storage 230, a communication unit 240, an input unit 250, and a display unit 260, is the same as the CPU 110, the memory 120, the storage 130, the communication unit 140, the input unit 150, and the display unit 160 of the management server 10, respectively, and therefore will not be described.
[0020] The local government terminal 30 is an information processing device. The hardware configuration of the local government terminal 30, including a CPU 310, a memory 320, a storage 330, a communication unit 340, an input unit 350, and a display unit 360, is the same as the CPU 110, the memory 120, the storage 130, the communication unit 140, the input unit 150, and the display unit 160 of the management server 10, respectively, and therefore a description thereof will be omitted.
[0021] <Functional configuration of management system 1> 3 is a functional block diagram of the management system 1. The functional configuration of the management server 10 will be described first. The management server 10 includes a storage unit 11, a communication control unit 12, and a management unit 13 as software modules executed by the CPU 110 (functions configured by various programs deployed in the internal memory of the CPU 110). For convenience of description below, these modules may be described as the main operating units, but because it is the CPU 110 that actually executes these modules, the CPU 110 may also be the main operating unit.
[0022] The storage unit 11 stores a shelter table 111, a local government account table 112, and reports (not shown) received from the shelter terminal 20.
[0023] The shelter table 111 is a data set that stores information registered from the local government terminal 30. As an example, one record in the shelter table 111 is information that associates a shelter ID, a shelter name, an address, a corresponding local government, a capacity limit, and opening information.
[0024] "Shelter ID" is identification information for uniquely identifying a shelter. "Shelter name" is information indicating the name of the shelter. "Address" is information indicating the address of the shelter. "Responding municipality" is information indicating the local government where the disaster response headquarters is located or the regional municipality where the disaster response headquarters is located. "Capacity" is information indicating the number of evacuees that can be accommodated at the shelter. "Opening status" is information indicating whether the shelter is open or not.
[0025] The local government account table 112 is a data set that stores information about the accounts of local government employees who can view evacuation shelter information. As an example, one record in the local government account table 112 is information that associates a user ID (identification), an email address, login information, and scope of authority.
[0026] "User ID" is identification information that uniquely identifies a user ID. "Email address" is an ID number that indicates the destination of an email on a network or the Internet. "Login information" is information that indicates the information required to log in. An example of login information is a password. "Scope of authority" is information that indicates the scope of access authority. If the user is an employee involved only in the operation of a specific evacuation shelter, an example of the scope of authority would be a specific evacuation shelter. If the user is an employee in charge of the disaster response headquarters, an example of the scope of authority would be all evacuation shelters to which the user belongs.
[0027] The communication control unit 12 controls the communication operation executed by the communication unit 140. The communication control unit 12 controls the communication unit 140 to receive various information from one or more shelter terminals 20 and one or more local government terminals 30. The communication control unit 12 controls the communication unit 140 to transmit various information to one or more shelter terminals 20 and one or more local government terminals 30.
[0028] The management unit 13 updates various pieces of information held by the storage unit 11 based on at least one of the information received by the communication unit 140 and the information input by the input unit 150 .
[0029] Next, we will explain the functional configuration of the shelter terminal 20. The shelter terminal 20 has a communication control unit 21, a display control unit 22, a reception unit 23, a memory unit 24, and a counting unit 25. Each function or process of the shelter terminal 20 is realized by a CPU 210 provided in the shelter terminal 20 executing various programs.
[0030] The communication control unit 21 controls the communication operation executed by the communication unit 240. For example, the communication control unit 21 controls the communication unit 140 to receive various information from the management server 10 and transmit various information to the management server 10.
[0031] The display control unit 22 controls the display unit 260 so as to generate and display a GUI (Graphical User Interface) screen based on screen data for a GUI that has been saved in advance.
[0032] The reception unit 23 receives input from the user of the evacuation shelter terminal 20 via the input unit 250. The reception unit 23 also receives various instructions from the management server 10 via the communication unit 240.
[0033] The memory unit 24 holds an evacuee list table 241. The evacuee list table 241 is a data set that stores information indicating those who have evacuated to an evacuation shelter and have been accepted for admission to the evacuation shelter. Examples of the evacuee list table 241 include a handwritten evacuee list that has been digitized, and evacuee lists that have been electronically created in various formats. The evacuee list table 241 may be updated at a fixed frequency, or may be updated when an evacuee is accepted for admission. Note that the evacuee list table 241 may be accumulated and stored from oldest to newest without being updated. As an example, one record in the evacuee list table 241 is information that associates a name, address, telephone number, and status.
[0034] "Name" is information indicating a person's name written in kanji, hiragana, or katakana. "Address" is information indicating the location where each person lives. "Telephone number" is information indicating a landline or mobile phone number. "Status" is information indicating the evacuation status of an evacuee. Examples of status include admitted, temporarily returning home, discharged, evacuated at home, and staying in a car.
[0035] The counting unit 25 counts the number of evacuees for each registered status based on the evacuee list 241. Hereinafter, the counting of the evacuee list 241 by the counting unit 25 is referred to as "automatic counting." Note that the counting unit 25 may count the number of evacuees for other attributes of the evacuee list 241 other than the status.
[0036] Next, the functional configuration of the local government terminal 30 will be described. The local government terminal 30 has a communication control unit 31, a display control unit 32, a reception unit 33, a memory unit 34, and a counting unit 35. Each function or process of the local government terminal 30 is realized by the CPU 310 provided in the local government terminal 30 executing various programs. As the functional configuration of the local government terminal 30, the communication control unit 31, the display control unit 32, the reception unit 33, the memory unit 34, and the counting unit 35 are similar to the communication control unit 21, the display control unit 22, the reception unit 23, the memory unit 24, and the counting unit 25 of the evacuation shelter terminal 20, respectively, and therefore description thereof will be omitted. As the evacuee list table 341 is similar to the evacuee list table 241, description thereof will be omitted.
[0037] <Counting of evacuee lists> FIG. 4 is a flowchart showing the processing steps performed by the shelter terminal 20 to tally up the evacuee list 241 by status. When a previously downloaded application is launched, the shelter terminal 20 executes the following tallying process. For example, the following tallying process is executed at a fixed frequency (every hour, for example). Note that the shelter terminal 20 may also execute the following tallying process when a web application (an application that runs on a web server and uses a web browser as a client) is launched.
[0038] In S401, the counting unit 25 reads the evacuee list 241 held by the memory unit 24. In S402, the counting unit 25 identifies a status to be counted from among the statuses that can be registered. For example, the counting unit 25 identifies one of: admitted, temporarily returned home, discharged, evacuated at home, and staying in a car. In S403, the counting unit 25 counts the number of evacuees on the evacuee list 241 who correspond to the status identified in S402. For example, if "admitted" is identified in S402, the counting unit 25 counts the number of evacuees registered on the evacuee list 241 who correspond to the status of "admitted."
[0039] If the number of evacuees has not been counted for all the statuses (S404: NO), the counting unit 25 performs the operations of S402 and S403 again. On the other hand, if the number of evacuees has been counted for all the statuses (S404: YES), the counting unit 25 ends the counting process.
[0040] <Report sending process> 5 is a flowchart showing the processing steps performed by the shelter terminal 20 to transmit a report to the management server 10. When a previously downloaded application is launched, the shelter terminal 20 executes the following transmission process. Note that the shelter terminal 20 may also execute the following transmission process when a web application is launched.
[0041] In S501, the display control unit 22 controls the display unit 260 to display a report screen. Fig. 6(a) is a diagram showing an example of the report screen of the shelter terminal 20. For example, when an application of the shelter terminal 20 is started, the display control unit 22 controls the display unit 260 to display a report screen for the shelter corresponding to the logged-in account.
[0042] The reporting screen includes the name of the corresponding evacuation shelter, a GUI that allows selection of the input method for the number of evacuees, and a report creation button. Here, as examples of input methods, either an approximate calculation mode or a list mode can be selected. The approximate calculation mode is a mode in which the reception unit 23 accepts the input of the number of evacuees via the input unit 250, and the number of evacuees is obtained by the evacuation shelter operator directly entering the numbers. The list mode is a mode in which the number of evacuees is obtained by the calculation process of the calculation unit 25, calculated on the evacuation shelter list 241. Whether the number of evacuees is input using the approximate calculation mode or the list mode is selected by the staff operating the evacuation shelter. The approximate calculation mode is an example of the first mode. The list mode is an example of the second mode.
[0043] In S502, the reception unit 23 receives a report creation instruction input via the input unit 250. For example, the report creation instruction is input by pressing a report creation button on the report screen. At this time, the staff member selects the rough estimate mode or the list mode.
[0044] If the approximate estimation mode is selected (S503: YES), in S504 the display control unit 22 controls the display unit 260 to display a report creation screen. Fig. 6(b) is a diagram showing an example of the report creation screen of the evacuation shelter terminal 20. The report refers to a report that summarizes, for example, various information input on the report creation screen or various information compiled by the evacuee list 241.
[0045] The report creation screen includes a field for manually inputting the estimated number of people, a GUI that allows the user to explain the surrounding conditions, a GUI that allows the user to input essential supplies, a submit button, etc. The estimated number of people is the number of evacuees roughly calculated by evacuation center staff or the like. Note that in addition to or instead of the manual input field for the estimated number of people, a GUI that allows the user to select a certain number range using a pull-down menu may be included. Examples of GUIs that allow the user to explain the surrounding conditions include a GUI that allows the user to select road conditions from "passable," "traffic jammed," and "impassable," and a manual input field that allows the user to supplement other conditions, such as fire conditions, with text. Note that the GUI that allows the user to explain the surrounding conditions may include landslide conditions, building collapse conditions, etc. An example of a GUI that allows the user to input essential supplies is a manual input field for the supply of supplies that are in short supply.
[0046] In S505, the reception unit 23 receives input of pressing the send button via the input unit 250. In S506, the communication control unit 21 controls the communication unit 240 to send a report to the management server 10, which includes information indicating the selected mode (approximate mode, list mode) in addition to the information input on the report creation screen in S504 or S507. In other words, the communication control unit 21 controls the communication unit 240 to send the report to the management server 10 in such a way that it is possible to identify whether the number of evacuees included in the report is the number of evacuees tallied in the evacuee list 241.
[0047] If the rough estimation mode is not selected (S503: NO, if the list mode is selected), in S507 the display control unit 22 controls the display unit 260 to display a report creation screen. Fig. 6(c) is a diagram showing an example of the report creation screen of the evacuation shelter terminal 20.
[0048] The report creation screen includes a GUI showing the number of evacuees admitted to evacuation shelters, a GUI that allows the user to explain the surrounding conditions, a GUI that allows the user to input essential supplies, a send button, etc. The number of evacuees admitted to evacuation shelters is information that indicates the number of evacuees tallied in the evacuee list 241 during the tallying process. Note that the number of evacuees is not limited to the number of evacuees admitted to evacuation shelters, and the number of evacuees with each status (returning home temporarily, leaving the shelter, staying at home, staying in a car) may also be displayed. In this embodiment, the number of evacuees displayed in the list mode cannot be modified. The GUI that allows the user to explain the surrounding conditions and the GUI that allows the user to input essential supplies are the same as the GUI that allows the user to explain the surrounding conditions and the GUI that allows the user to input essential supplies on the report input screen of S504, and therefore their explanation will be omitted.
[0049] When the send button on the report creation screen in S507 is pressed, the same operations as those in S505 to S507 are performed, and therefore a description thereof will be omitted.
[0050] <Report notification processing> The communication control unit 12 of the management server 10 controls the communication unit 140 to receive the report from the evacuation shelter terminal 20. Thereafter, the communication control unit 12 controls the communication unit 140 to notify the local government terminal 30 of the received report or to send the report to a destination registered in advance.
[0051] It should be noted that notification to the local government terminal 30 is not a required configuration, and when an employee of the disaster response headquarters or the like logs in to the local government terminal 30, the local government terminal 30 can simply display the latest report (the report with the date closest to the time of viewing) for evacuation shelters that the employee has permission to view, or display content that has been reported in the past.
[0052] <Report display screen> When a local government employee logs into the system via the local government terminal 30, the employee can view the latest report content sent from evacuation shelters belonging to the local government on the local government terminal 30. FIG. 7(a) is a diagram showing an example of a display screen of a report acquired by the local government terminal 30 in list mode. The report display screen includes the name of the evacuation shelter, a message indicating that the evacuees list 241 is the number of evacuees compiled, the number of evacuees compiled by the evacuees list 241 (number of evacuees by status), and the date and time the report was received. FIG. 7(b) is a diagram showing an example of a display screen of a report acquired by the local government terminal 30 in approximate mode. The report display screen includes the name of the evacuation shelter, a message indicating that the number of evacuees has been entered (an estimated number of evacuees), the number of evacuees entered, and the date and time the report was received.
[0053] Although the example of the report display screen shows only the number of evacuees, it may also be configured to display information about shortages of supplies and road conditions included in the report.
[0054] <Summary of the First Embodiment> Immediately after a disaster occurs, when an evacuation center first opens, it is expected that the center staff and evacuees will be confused and will not have the capacity to properly admit evacuees. For example, when evacuees arrive at the evacuation center, they may be guided into the center in order, and the center may start accepting evacuees later, or the center may start accepting evacuees from the beginning, but may have to wait inside the center because a large number of citizens have evacuated at once.
[0055] The process of counting the number of evacuees based on the evacuation list is not difficult in itself. However, it is difficult to accurately count the number of evacuees until evacuees are accepted or the evacuation list is ready. For example, when an evacuation shelter first opens, many evacuees may evacuate to the shelter at the same time. Before evacuees begin to be accepted, the number of evacuees on the evacuation list will be zero. Therefore, it is inappropriate to send a report containing the number of evacuees counted on the evacuation list. Thus, when an evacuation shelter first opens, the approximate number of evacuees entered manually is often more accurate than the number of evacuees counted on the evacuation list.
[0056] On the other hand, once the number of evacuees admitted to the shelter has stabilized, it is easier and more accurate to compile a list of evacuees rather than manually inputting an approximate number of evacuees each time. Therefore, the management system 1 according to the first embodiment can switch between an approximate calculation mode and a list mode for reporting. Therefore, the management system 1 can send appropriate information (reports) according to the situation at the evacuation shelter.
[0057] Furthermore, the management system 1 according to the first embodiment includes in the report whether the number of evacuees was acquired in the approximate calculation mode or the list mode. Therefore, the management system 1 according to the first embodiment transmits the report in a manner that allows identification of whether the number of evacuees included in the report is the number of evacuees compiled from the evacuee list. Therefore, the management system 1 is able to determine whether the number of evacuees included in the report is a highly accurate figure. A user of the management system 1 can select either the approximate calculation mode, which uses manual input, or the list mode, which compiles the evacuee list, to submit a report. Furthermore, for the party receiving the report, it is also important to know how the number of evacuees was entered. For example, switching from the approximate calculation mode to the list mode indicates that reception operations have stabilized.
[0058] <Modification of the first embodiment> In the above embodiment, the approximate calculation mode and the list mode can be selected on the reporting screen of the evacuation shelter terminal 20, and information indicating which mode was selected is reported together with the number of evacuees. As a method other than mode switching, there is also a method of accepting manual overwriting.
[0059] Specifically, the display control unit 22 of the shelter terminal 20 generates and displays a report creation screen including a text box for inputting the number of evacuees. When displaying the report creation screen, the display control unit 22 of the shelter terminal 20 displays the number of evacuees compiled from the latest list by default in the text box for inputting the number of evacuees. The display control unit 22 displays the number of evacuees in the text box in a rewritable manner, so that the evacuation shelter operator operating the shelter terminal 20 can rewrite the number of evacuees. When the reception unit 23 receives input by pressing the send button, the communication control unit 21 determines whether the number of evacuees entered on the report creation screen matches the latest number of evacuees compiled by the compilation unit 25, and controls the communication unit 240 to send a report to the management server 10, including information on whether the number of evacuees included in the report is consistent with the compilation result, in accordance with the information entered on the report creation screen.
[0060] In this method, even if the number of evacuees has actually been overwritten, it will be identified as the counted result if it matches the counted result.If the number is the same as the counted result but has been manually entered, and it is better to identify that it was manually entered (rather than as the counted result), the report may be sent with information indicating whether the number of evacuees initially displayed (counted result) has been overwritten.
[0061] [Second embodiment] In this embodiment, the shelter terminal 20 also accepts evacuees entering the shelter, and a case will be described in which the shelter terminal 20 creates a list of evacuees 241. Note that the same components as those in the first embodiment are assigned the same numbers, and descriptions thereof will be omitted.
[0062] When an evacuee enters the shelter, the reception unit 23 reads the evacuee's Individual Number and receives the evacuee's personal information using the input unit 250. For example, the input device of the input unit 250 is realized by an IC card reader or the like, and has a function to input card information, etc. The personal information received by the reception unit 23 is registered in the evacuee list 241 each time.
[0063] Furthermore, the reception unit 23 may receive personal information from information transmitted from the evacuee's terminal when the evacuee enters the shelter, using the input unit 250. In this case, when a specific URL (Uniform Resource Locator) is read on the evacuee's terminal, the evacuee can input personal information (such as name, age, and address), and by pressing a registration button, the information may be transmitted from the evacuee's terminal to the shelter terminal 20.
[0064] The counting unit 25 executes a process of counting the evacuee list 241 at a fixed frequency. The counting unit 25 also varies the frequency of counting the evacuee list 241 depending on the time elapsed since the opening of the evacuation shelter. For example, the day the evacuation shelter is opened is set as the first day of the disaster, and the counting unit 25 executes the counting process every hour for one week after the disaster, and executes the counting process once a day from the eighth day onwards. In addition to the periodic counting process, the counting process may be started via the reception unit 23 in response to an operation by the evacuation shelter operator. As in the second embodiment, by registering the information received when entering a shelter in a list of evacuees, the number of evacuees can be grasped and reported more simply.
[0065] [Third embodiment] In this embodiment, a case will be described in which an evacuation center staff member manually sends a report including the input number of evacuees to the management server 10, and the management system 1 automatically sends a report including the number of evacuees tallied from the evacuee list 241 to the management server 10. In this case, the management system 1 further displays a graph showing the transition of the input number of evacuees and the transition of the number of evacuees tallied from the evacuee list 241. Note that the same components as in the first embodiment are assigned the same numbers, and their explanations will be omitted.
[0066] Each time the evacuation shelter terminal 20 tally the evacuee list 241, it automatically transmits a report including the number of evacuees compiled in the evacuee list 241 to the management server 10. Regardless of whether the report is automatically transmitted in association with the tally, the evacuation shelter operator manually transmits a report including the number of evacuees to the management server 10 using the evacuation shelter terminal 20. The management server 10 stores the received reports. The management server 10 stores both manually transmitted reports including the number of evacuees and automatically transmitted reports including the number of evacuees.
[0067] <Graph generation process> In this embodiment, the evacuation shelter terminal 20 and the local government terminal 30 are capable of displaying the transition in the number of evacuees in a graph using the display control unit 22 or the display control unit 32. The process of generating a graph showing the transition in the number of evacuees sent manually and the transition in the number of evacuees sent automatically will be described. The process of generating the graph is performed by the local government terminal 30. Note that the process of generating the graph may be performed by at least either the management server 10 or the evacuation shelter terminal 20.
[0068] The display control unit 32 in the municipal terminal 30 executes a graph generation process as follows. First, the display control unit 32 sets the target evacuation shelter for which a graph is to be generated. The display control unit 32 then queries the management server 10 to acquire from the management server 10 all manually transmitted report information and automatically transmitted information on the number of evacuees for the identified evacuation shelter during its opening period, including the present. The display control unit 32 in the municipal terminal 30 references the report information acquired from the management server 10 and generates a graph with the date and time on the horizontal axis and the number of evacuees on the vertical axis. Specifically, the display control unit 32 first plots the number of evacuees (estimated number of evacuees) included in the report after the evacuation shelter is opened. The display control unit 32 then plots the count results (number of evacuees: number of people with an evacuated status) of the evacuation shelter list automatically transmitted after the evacuation shelter is opened as a broken line. As a result, the municipal terminal 30 generates a graph showing the transition of the number of evacuees reported manually and the transition of the number of evacuees on the automatically transmitted evacuation shelter list 241.
[0069] FIG. 8 is a diagram showing an example of a graph displayed on the local government terminal 30 in the management system 1. The display control unit 32 controls the display unit 360 to display the generated graph. As shown in FIG. 8, immediately after the evacuation shelter is opened, the number of registered evacuees is zero, while the number of reported evacuees is several, which indicates that evacuated citizens are inside the evacuation shelter but registration of evacuee information on the evacuation shelter list has not yet begun. At some point, registration of evacuees on the evacuation shelter list begins, and after a certain period of time (in this case, around 5:00 p.m. on September 1st), the reported number of evacuees matches the automatically transmitted number of evacuees, indicating that admission of all evacuees to the evacuation shelter (registration on the evacuation shelter list) has been completed.
[0070] It should be noted that if the frequency of the list counting performed by the counting unit 25 in the evacuation shelter terminal 20 is changed, the number of plots in the graph will also change.
[0071] <Summary of the third embodiment> The management system 1 according to the third embodiment displays a graph showing the trend in the number of evacuees included in manually transmitted reports and the trend in the number of evacuees automatically transmitted by compiling the evacuee list 241. When the operation of accepting evacuees becomes stable, the degree of discrepancy between the trend in the reported number of evacuees and the trend in the compiled number of evacuees becomes smaller. Therefore, a user of the management system 1 can understand whether the evacuation center is operating smoothly based on the degree of discrepancy. In addition, a user of the management system 1 can understand the frequency of reports from the evacuation center. Furthermore, a user of the management system 1 can collect as much information as possible from the evacuation center even if there are no or infrequent reports due to chaos at the evacuation center.
[0072] As described above, the technology of the present disclosure can be realized by supplying a program that realizes one or more functions of the above-described embodiments to a system or device via a network or a storage medium, and having one or more processors in the computer of the system or device read and run the program. Alternatively, the technology may be realized by a circuit that realizes one or more functions.
[0073] The present disclosure is not limited to the above-described embodiments and includes various modifications. For example, the above-described embodiments have been described in detail to clearly explain the present disclosure, and it is not necessary to include all of the described configurations. Furthermore, a part of one embodiment can be replaced with a configuration of another embodiment. Furthermore, a configuration of another embodiment can be added to a configuration of one embodiment. Furthermore, a part of the configuration of each embodiment can be added to, deleted from, or substituted for a part of the configuration of another embodiment.
[0074] <Additional Notes> The matters described in the above embodiments will be supplemented below. (Appendix 1) A program to be executed by a computer having a processor and a memory, the program causing the processor to: a storage step for storing a list of evacuees; a sending step of sending a report including the evacuation shelter and the number of evacuees to a server; Execute The transmitting step transmits the report in a manner that enables identification of whether the number of evacuees included in the report is the number of evacuees tallied from the evacuee list. program. (Appendix 2) In the transmission step, a first mode is switched between using a manually input number of evacuees as the number of evacuees and a second mode is switched between using a number of evacuees tallied from the evacuee list as the number of evacuees, and the report is made to include information on which mode the number of evacuees included in the report was obtained from. The program described in Appendix 1. (Appendix 3) displaying a graph showing the transition of the number of evacuees obtained in the first mode and the transition of the number of evacuees obtained in the second mode; The program described in Appendix 2. (Appendix 4) causing the processor to further execute a counting step of counting the number of evacuees from the evacuee list; A program according to any one of appendices 1 to 3. (Appendix 5) In the counting step, the number of evacuees is counted from the evacuee list at a frequency according to the elapsed time since the opening of the evacuation shelter. The program described in Appendix 4. (Appendix 6) a means for maintaining a list of evacuees; a transmitting means for transmitting a report including the evacuation shelter and the number of evacuees to a server; and The transmitting means transmits the report in a manner that enables identification of whether the number of evacuees included in the report is the number of evacuees compiled in the evacuee list. Information processing device. (Appendix 7) A method executed by a computer having a processor and a memory, the method comprising: a storage step for storing a list of evacuees; a sending step of sending a report including the evacuation shelter and the number of evacuees to a server; Run The transmitting step transmits the report in a manner that enables identification of whether the number of evacuees included in the report is the number of evacuees compiled in the evacuee list. method. (Appendix 8) a means for maintaining a list of evacuees; a transmitting means for transmitting a report including the evacuation shelter and the number of evacuees to a server; Equipped with The transmitting means transmits the report in a manner that enables identification of whether the number of evacuees included in the report is the number of evacuees compiled in the evacuee list. system. [Explanation of symbols]
[0075] 10 Management Server 20 Evacuation shelter terminal 30 Local Government Terminals 241 Evacuee list
Claims
1. A program to be executed by a computer having a processor and a memory, the program causing the processor to: a storage step for storing a list of evacuees; a sending step of sending a report including the evacuation shelter and the number of evacuees to the server; The transmission step is a program that includes identification information in the report indicating whether the number of evacuees included in the report is a number of evacuees entered manually or a number of evacuees compiled from the evacuee list.
2. The program described in claim 1, wherein in the transmission step, switching is performed between a first mode in which the number of evacuees is manually entered, and a second mode in which the number of evacuees compiled from the evacuee list is used, and the report includes information on which mode the number of evacuees included in the report was obtained from.
3. The program according to claim 2 , further comprising: displaying a graph of the transition in the number of evacuees obtained in the first mode and the transition in the number of evacuees obtained in the second mode.
4. 3. The program according to claim 1, further causing the processor to execute a counting step of counting the number of evacuees from the evacuee list.
5. 5. The program according to claim 4, wherein in the counting step, the number of evacuees is counted from the evacuee list at a frequency according to the elapsed time since the evacuation shelter was opened.
6. a means for maintaining a list of evacuees; a transmitting means for transmitting a report including the evacuation shelter and the number of evacuees to the server; The transmitting means is an information processing device that transmits the report together with identification information indicating whether the number of evacuees included in the report is a number of evacuees manually entered or a number of evacuees compiled from the evacuee list.
7. A method executed by a computer having a processor and a memory, the method comprising: a storage step for storing a list of evacuees; a sending step of sending a report including the evacuation shelter and the number of evacuees to a server; The transmission step includes transmitting identification information in the report indicating whether the number of evacuees included in the report is a number of evacuees manually entered or a number of evacuees compiled from the evacuee list.
8. a means for maintaining a list of evacuees; a transmitting means for transmitting a report including the evacuation shelter and the number of evacuees to the server; The system includes identification information in the report indicating whether the number of evacuees included in the report is a number of evacuees manually entered or a number of evacuees compiled from the evacuee list.
Citation Information
Patent Citations
Refuge place management system
JP1998334146A
Disaster evacuation guide and safety information confirmation system and wireless terminal management device
JP2006139324A
Evacuation support apparatus, evacuation support system, evacuation support method, and program
JP2024049436A
Shelter management system and shelter management method
WO2018163822A1
Calculation device, calculation system, calculation method, and storage medium
WO2022065462A1