Evacuation management system and evacuation management method

Abstract

To provide an evacuation management system which can acquire and manage information of evacuees attending an evacuation-exit-time inspection, without causing delay in inspection or evacuation.SOLUTION: An evacuation management system for managing information of evacuees arriving at a venue for contamination inspection at a nuclear disaster time, issues an evacuee ID for each evacuee arriving at the venue, and outputs the ID onto a prescribed medium. After the evacuees completes the contamination inspection and departs from the venue, the evacuation management system reads, by using a terminal device, the evacuee IDs outputted onto the media, and instructs registration of the evacuee IDs and the evacuee information of the evacuee corresponding to the evacuee IDs. An evacuation information management server registers the evacuee information in association with the evacuee IDs in an evacuee database, according to the instruction.SELECTED DRAWING: Figure 1

Description

[Technical Field]

[0001] The present disclosure relates to an evacuation management system and an evacuation management method. [Background technology]

[0002] When evacuations occur after a nuclear disaster and the release of radioactive materials, evacuation inspections are conducted. Evacuation inspections are conducted to ensure that the amount of radioactive material adhering to evacuees' clothing and vehicles is below the standard level when residents within an Urgent Protection Action Planning Zone (UPZ) move to evacuation shelters outside the UPZ. If the level is below the standard level, evacuation to the evacuation shelter is permitted; if the level is above the standard level, decontamination is required before evacuation. Evacuation inspections aim to minimize health damage by quickly decontaminating evacuees who have been exposed to radiation. Hereinafter, evacuation inspections are sometimes referred to as contamination inspections. Contamination inspections take approximately five minutes per person. Because the impact of a nuclear disaster is widespread, the number of evacuees (e.g., tens of thousands or more) can be large. When the number of evacuees exceeds tens of thousands, contamination inspections take time, which can hinder evacuation. Therefore, the Cabinet Office's contamination testing policy stipulates that contamination testing should first be conducted on vehicles carrying residents, and only for vehicles in which contamination is confirmed should contamination testing be conducted on residents. Furthermore, for resident contamination testing, a representative resident should be tested first, and only if contamination is confirmed should all passengers be tested. After contamination is confirmed in a vehicle, the representative resident should be tested away from the vehicle to prevent accidents such as contact between the resident or the inspection officer and the vehicle. If contamination is confirmed in the representative resident, the officer will guide other residents waiting in the vehicle to the inspection. If the relationship between the vehicle and the resident resident is unknown, the officer may take too long to guide the passengers or may make mistakes, such as directing residents in unrelated vehicles to the inspection. Thus, in contamination testing, the results of vehicle and resident inspections may need to be shared and coordinated. However, coordination between resident and vehicle contamination testing becomes essential when contamination is confirmed in a vehicle, a representative inspection is required, and then contamination is confirmed in the representative resident. In this case, the passenger must be inspected, but since the passenger is in the vehicle (vehicle inspection location), the resident inspection location will ask the representative about the vehicle they are in, and this will be communicated to the vehicle inspection location, which will then search the vehicle and instruct the passenger to undergo inspection.However, if a release of radioactive materials is anticipated, instructions to take shelter indoors will be issued, so it is highly likely that residents are not contaminated. For this reason, in reality, the majority of vehicles subject to inspection do not require coordination between vehicle inspections and resident inspections. If vehicle contamination is not confirmed, or if the vehicle is contaminated but the representative is not, contamination inspections can be carried out even if the relationship between the resident and the vehicle is unknown. Therefore, for example, it would take a long time to register the information of tens of thousands of residents and vehicles, and it would be inefficient to spend such a huge amount of time and effort registering the information of all residents and vehicles.

[0003] To address these issues, the operation of a system in which residents themselves register information about evacuees in advance before evacuation orders are issued is being considered. However, even if such a system is operated, not everyone will necessarily register the necessary information. When residents who have not registered their evacuation information in advance arrive at the contamination testing site, they will have to register their evacuation information at the testing site. Furthermore, if the information registered in advance changes (e.g., a change of surname due to marriage, a change of residence due to moving, etc.), it will be necessary to change the registered information at the testing site, which is likely to cause delays and confusion in contamination testing and evacuations.

[0004] Patent Document 1 discloses a system in which an IC card recording evacuee information is distributed to each evacuee, and when each individual enters or leaves an evacuation shelter, the information on each IC card is read by a portable information terminal installed at the shelter and recorded in a database. By referencing the database, the shelter manager can grasp the number of evacuees the shelter is accommodating and the status of each evacuee's entry and exit. However, in order to apply the method of Patent Document 1 to a nuclear disaster, tens of thousands of IC cards recording evacuee information must be prepared in advance, which is a significant burden. [Prior art documents] [Patent documents]

[0005] [Patent Document 1] Patent No. 6839129 Summary of the Invention [Problem to be solved by the invention]

[0006] To provide a system capable of acquiring and managing information on evacuees who have come for inspection when leaving an evacuation area without causing delays in inspection or evacuation.

[0007] The present disclosure provides an evacuation management system and an evacuation management method that can solve the above problems. [Means for solving the problem]

[0008] The evacuation management system disclosed herein is an evacuation management system that manages information of evacuees who have arrived at an inspection site where inspections are conducted in the event of a nuclear disaster, and includes a pre-registration server, an evacuation information management server, and a terminal device, wherein the pre-registration server includes a pre-registration database in which evacuee information including the names and residential areas of the evacuees is registered, the evacuation information management server includes an ID issuing unit that issues an evacuee ID for each evacuee who has arrived at the inspection site, an output unit that outputs the issued evacuee ID to a predetermined medium, an evacuee database that stores the evacuee ID and the evacuee information of the evacuee in association with each other, and a registration unit that registers the evacuee ID and the evacuee information of the evacuee in the evacuee database in association with each other, and the terminal device The device is equipped with a reading unit that reads the evacuee ID output to the medium, an instruction unit that instructs the registration of the evacuee information of the evacuee corresponding to the evacuee ID, and a reception unit that accepts the input of the evacuee information, and when the instruction unit of the terminal device instructs the registration of the evacuee information related to the evacuee ID read by the reading unit, the registration unit of the evacuation information management server registers the evacuee information registered in the pre-registration database in the evacuee database for evacuees whose evacuee information is registered in the pre-registration database, and registers the evacuee information received by the reception unit of the terminal device in the evacuee database for evacuees whose evacuee information is not registered in the pre-registration database.

[0009] The evacuation management method disclosed herein is an evacuation management method for managing information on evacuees who have arrived at an inspection site where an inspection is to be conducted in the event of a nuclear disaster, and includes the steps of an evacuation information management server issuing an evacuee ID to each evacuee who has arrived at the inspection site, outputting the issued evacuee ID to a predetermined medium, reading the evacuee ID output to the medium using a terminal device in a situation that does not impede the progress of the inspection or the evacuation of the evacuees, and issuing an instruction to register evacuee information including the name and residential area of ​​the evacuee corresponding to the read evacuee ID, and the evacuation information management server issuing an instruction to register the evacuee information based on the instruction. and a step of registering the evacuee ID of the evacuee and the evacuee information of the evacuee in an evacuee database in association with each other. In the registering step, the evacuation information management server registers the evacuee information registered in the pre-registration database in the evacuee database for the evacuee whose information is registered in a pre-registration database in which evacuee information including the evacuee's name and residential area is registered, and registers the evacuee information inputted by the terminal device in the evacuee database for the evacuee whose information is not registered in the pre-registration database. [Effects of the Invention]

[0010] According to the above-described evacuation management system and evacuation management method, it is possible to acquire and manage information on evacuees who have come for evacuation evacuation inspections without causing delays in inspections or evacuation. [Brief explanation of the drawings]

[0011] [Figure 1] 1 is a diagram illustrating an example of an evacuation management system according to an embodiment. [Figure 2] FIG. 10 is a diagram illustrating an example of operation at an examination site according to the embodiment. [Figure 3] FIG. 1 is a first diagram showing an example of a vehicle information table according to the embodiment. [Figure 4] FIG. 1 is a first diagram showing an example of a resident information table according to the embodiment. [Figure 5]10 is a flowchart illustrating an example of a registration process of evacuation information according to the embodiment. [Figure 6] 10 is a flowchart illustrating an example of a process for associating a vehicle ID with a resident ID according to the embodiment. [Figure 7] FIG. 2 is a second diagram showing an example of a vehicle information table according to the embodiment. [Figure 8] FIG. 2 is a second diagram showing an example of a resident information table according to the embodiment. [Figure 9] 1 is a diagram illustrating an example of a hardware configuration of an evacuation management system according to an embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0012] <Embodiment> (overview) The evacuation management system 1 of this embodiment will be described below with reference to the drawings. FIG. 1 is a diagram illustrating an example of an evacuation management system according to an embodiment. The evacuation management system 1 includes a pre-registration server 10, an evacuation information management server 20, a mobile device 30 owned by an evacuee 3, a mobile device 40 owned by an officer 4 at an inspection site who will conduct an inspection at the time of evacuation, a terminal device 41 and a printer 42 installed at the inspection site, and a mobile device 50 owned by an officer 5 at a waypoint or evacuation shelter to which the evacuee 3 will be directed after passing through the inspection site. Each of the pre-registration server 10, the evacuation information management server 20, the mobile devices 30-50, and the terminal device 41 has a communication means and is communicatively connected via a network NW. While only one mobile device 30-50 is shown in the figure, multiple mobile devices may be provided. The evacuee 3 travels from the location where he or she took shelter indoors before the evacuation to the evacuation shelter via the inspection site in a vehicle 2. However, there may be two or more evacuees 3 traveling in the vehicle 2. Not all evacuees 3 need have a mobile device 30; some evacuees 3 may not have a mobile device 30.

[0013] Here, we will explain the evacuation procedures in the event of a nuclear disaster, with reference to Figures 1 and 2. When a nuclear disaster occurs, residents within the UPZ area are required to take shelter indoors. The UPZ area is defined as an area approximately 5 to 30 km from a nuclear facility. Subsequently, when radioactive materials begin to be released, evacuation areas and evacuation dates and times are identified, and residents are instructed to move to designated evacuation shelters at a specific time on a specific day for each area. Residents within the UPZ area follow these instructions and board vehicle 2 to the designated evacuation shelter. However, before leaving the UPZ area, they must undergo a contamination test. After the contamination test, vehicle 2 is allowed to move to the evacuation shelter after it is confirmed that the amount of radioactive material adhering to the clothing of evacuees 3 and vehicle 2 is below the standard value. At the contamination test site, vehicles 2 waiting for testing may line up, requiring long wait times. This may result in evacuees 3 bypassing the testing site to evacuate. After undergoing a contamination inspection, the evacuees 3 are given a certificate certifying that the amount of radioactive material adhering to their vehicles 2 and the like is below the standard value. This certificate allows the evacuees 3 to be accepted at the evacuation shelter with peace of mind. However, because evacuees 3 who evacuate without undergoing a contamination inspection do not have the certificate, confusion arises at the evacuation shelter regarding the acceptance of the evacuees 3. To solve this problem, it is necessary to alleviate congestion at contamination inspection sites and reduce the time required for contamination inspections. Various methods can be considered to reduce the time required for contamination inspections, such as increasing the number of equipment and inspectors used for the inspections. However, one of the causes of congestion at inspection sites and long inspection times is the process of registering the personal information of the evacuees 3. Conventionally, information about the evacuees 3 is often registered at the inspection site, which is one of the causes of congestion. Therefore, this embodiment provides a method for reducing the effort and time required for information registration.

[0014] FIG. 2 shows the operational flow of the contamination inspection site in this embodiment. When vehicle 2 arrives at the gate of the inspection site, an ID (identification information) is issued for each vehicle 2 and evacuee 3, and a piece of paper with the ID printed on it is handed to evacuee 3. First, a contamination inspection of vehicle 2 is conducted. If the vehicle inspection results in "no contamination," evacuee 3 receives a certificate, leaves the inspection site, and heads to an evacuation shelter. Before arriving at the evacuation shelter, evacuee 3 inputs evacuee information into mobile terminal 30 and registers it in evacuation information management server 20. Information on evacuee 3 and vehicle 2 is registered in evacuation information management server 20 in association with the ID handed to them at the inspection site. By operating in this way so that information registration is performed after departure from the inspection site, it is possible to prevent evacuee 3 from staying at the inspection site for a long time due to information registration, which would otherwise cause the inspection site to become congested.

[0015] If the vehicle inspection results in a "contaminated" result, a contamination test is conducted on the representative. At this time, staff member 4 associates vehicle 2 with evacuee 3 riding in vehicle 2. Specifically, the staff member reads the IDs of vehicle 2 and evacuee 3 from the paper on which their IDs are printed, and associates the vehicle's ID with the occupant's ID. This is because the contamination test for the representative is conducted at a location away from vehicle 2. If the representative is found to be "contaminated," the remaining evacuees 3 must be guided from vehicle 2 to the inspection site. However, if the location of vehicle 2 in which the representative was riding and the number of other evacuees 3 riding with him are unknown, it can take a long time to inspect the remaining evacuees 3, or the staff member may mistakenly guide unrelated evacuees 3 to inspection. If the representative's contamination test results in a "not contaminated" result, vehicle 2 is decontaminated as necessary. Evacuee 3 receives a certificate and departs the inspection site to head to an evacuation shelter. In this case, registering information after departure from the inspection site can prevent congestion at the inspection site due to information registration. If the representative is found to be "contaminated," the vehicle 2 the representative was riding in and the other evacuees 3 riding with him are identified from the information relating to the association between the previously traveled vehicle and the evacuees, and the remaining evacuees 3 are inspected. This makes it possible to avoid prolonged contamination inspections. In this case, necessary decontamination, etc. is carried out depending on the inspection results of the other evacuees 3. After decontamination, the evacuees 3 receive a certificate and depart the inspection site to head to an evacuation shelter. In this case, too, by registering information after departing from the inspection site, congestion at the inspection site due to information registration can be prevented. The evacuation management system 1 provides a mechanism that enables vehicle information and evacuee information to be registered in association with the vehicles 2 and evacuees 3 that arrive at the contamination inspection site after departing from the contamination inspection site. Below, we will explain the functions of each component of the evacuation management system 1, assuming the above operation.

[0016] The pre-registration server 10 is a server for the evacuees 3 to register evacuee information for identifying the evacuees 3, such as their own names and residential areas, and vehicle information, such as the license plate of their own vehicles 2 (vehicles to be used for evacuation), before an evacuation order is issued. By registering the evacuee information in advance, the evacuees 3 do not need to register evacuee information, vehicle information, etc., at the time of evacuation. The pre-registration server 10 includes a registration unit 11 and a pre-registration database 12. The registration unit 11 registers information for identifying the evacuee 3, such as the name and residential area of ​​the evacuee 3 (referred to as evacuee information), and information for identifying the vehicle 2, such as the license plate of the vehicle 2 (referred to as vehicle information), in the pre-registration database 12. The evacuee 3 inputs the evacuee information and vehicle information into the mobile terminal 30, which then transmits the information to the pre-registration server 10. A dedicated application for registering the evacuee information, etc. may be installed on the mobile terminal 30, or the pre-registration server 10 may be configured to allow the evacuee information, etc. to be registered from a web registration screen. The registration unit 11 acquires the transmitted evacuee information and vehicle information via communication means and registers them in the pre-registration database 12. The pre-registration database 12 stores evacuee information and vehicle information. For example, the evacuee information is registered in the pre-registration database 12 in association with the ID of the evacuee 3, and the vehicle information is registered in the pre-registration database 12 in association with the ID of the vehicle 2. The ID of the evacuee 3 registered in the pre-registration database 12 is different from the evacuee ID issued at the inspection site. The ID of the vehicle 2 registered in the pre-registration database 12 is different from the vehicle ID issued at the inspection site.

[0017] The evacuation information management server 20 is a server for managing information on vehicles 2 that have undergone contamination inspection at an inspection site and information on evacuees 3 traveling in the vehicles 2. Regardless of whether evacuee information has been pre-registered in the pre-registration server 10, information on evacuees 3 that have undergone inspection at an inspection site is registered in the evacuation information management server 20, and information on evacuees 3 that do not undergo inspection is not registered in the evacuation information management server 20. The evacuation information management server 20 includes an ID issuing unit 21, a control unit 22, and an evacuation information database 23. The ID issuing unit 21 issues a vehicle ID, which is identification information indicating that the vehicle 2 has arrived at the inspection site, to each vehicle 2 that has arrived at the inspection site. For example, the ID issuing unit 21 issues a vehicle ID consisting of "the ID of the inspection site (for example, "A" if the inspection site is A) + a code representing the vehicle (for example, "C") + a serial number (for example, 00001, 00002, etc.)". In addition, the ID issuing unit 21 issues a resident ID, which is identification information indicating that the evacuee 3 has arrived at the inspection site, to each evacuee 3 riding in the vehicle 2 that has arrived at the inspection site. For example, the ID issuing unit 21 issues a resident ID consisting of "the ID of the inspection site (for example, "A" if the inspection site is A) + a serial number (for example, 00001, 00002, etc.)".

[0018] The control unit 22 transmits the vehicle ID and resident ID issued by the ID issuing unit 21 to the terminal device 41 at the inspection site. For example, the vehicle ID and resident ID are converted into a QR code (registered trademark) by the terminal device 41, printed on paper by the printer 42, and handed to the evacuee 3 who has arrived at the inspection site. Alternatively, the terminal device 41 may transmit electronic data of the vehicle ID and resident ID via a communication means to the mobile terminal 30 of the evacuee 3 who has arrived at the inspection site. When the ID issuing unit 21 issues a vehicle ID and a resident ID when the vehicle 2 arrives at the inspection site, the control unit 22 registers the vehicle ID and the resident ID in the evacuation information database 23. At this time, only the vehicle ID and the resident ID are registered in the evacuation information database 23, and no evacuee information or vehicle information is registered. The evacuee information and vehicle information are input by the evacuee 3 to the mobile terminal 30 at any time that does not interfere with the progress of the evacuation inspection or evacuation (for example, after leaving the inspection site). Then, the control unit 22 associates the vehicle ID with the vehicle information of the vehicle 2 corresponding to the vehicle ID, and registers the association in the evacuation information database 23. The control unit 22 also associates the resident ID with the evacuee information of the evacuee 3 corresponding to the resident ID, and registers the association in the evacuation information database 23. The control unit 22 also reads out the vehicle information and evacuee information from the evacuation information database 23 and transmits them to the mobile terminal 50 or the like.

[0019] The evacuation information database 23 is a database for registering vehicle information of the vehicles 2 that have arrived at the inspection site and evacuee information of the evacuee 3. For example, the evacuation information database 23 includes a vehicle table and an evacuee table.

[0020] An example of a vehicle table is shown in FIG. 3. The vehicle table has fields such as "Vehicle ID," "Vehicle Number," "Number of Occupants," "Resident ID," and "Inspection Results." The "Vehicle ID" field stores the vehicle ID issued by the ID issuing unit 21, the "Vehicle Number" field stores the license plate information of vehicle 2, the "Number of Occupants" field stores the number of evacuees 3 riding in vehicle 2, the "Resident ID" field stores the resident IDs of evacuees 3 riding in vehicle 2, and the "Inspection Results" field stores the results of the contamination inspection for vehicle 2. The vehicle table shown in FIG. 3 illustrates an example of registered information when vehicle 2 arrives at the inspection site and the vehicle ID is issued, and the vehicle ID is registered by the control unit 22. As shown in the figure, only the vehicle ID "AC0001" is registered in the vehicle table. Note that the "Vehicle Number," "Number of Occupants," "Resident ID," and "Inspection Results" in the vehicle table shown in FIG. 3 are examples of vehicle information.

[0021] An example of the evacuee table is shown in FIG. 4. The evacuee table has fields such as "evacuee ID," "name," "residential district," and "test results." The evacuee table may also have fields such as telephone number, email address, and date of birth. The "evacuee ID" field stores the evacuee ID issued by the ID issuing unit 21, the "name" field stores the name of the evacuee 3, the "residential district" field stores the address or district of the evacuee 3 (for example, the district or postal code corresponding to the postal code of the address of the evacuee 3), and the "test results" field stores the results of the contamination test for the evacuee 3. The vehicle table shown in FIG. 4 illustrates an example of registered information when the evacuee ID is registered by the control unit 22 when the evacuee 3 arrives at the testing site in a vehicle 2 and is issued a evacuee ID. As shown in the figure, only vehicle IDs "A0001" and "A0002" are registered in the vehicle table. Note that the "name," "residential district," and "test results" in the evacuee table shown in FIG. 4 are examples of evacuee information. Evacuation information includes vehicle information and evacuee information. When two evacuees 3 arrive at inspection site A in one vehicle 2, a vehicle ID is issued to the vehicle 2, and a resident ID is issued to each of the two evacuees 3, and the information shown in Figures 3 and 4 is registered in the evacuation information database 23.

[0022] The mobile terminal 30 is a mobile terminal such as a smartphone owned by the evacuee 3. The mobile terminal 30 includes means for reading an evacuee ID and a vehicle ID (for example, a QR code (registered trademark) reader including a camera and software for reading QR codes (registered trademark)), means for accepting input of vehicle information of the vehicle 2 in which the evacuee 3 rides and evacuee information of the evacuee 3, and means for instructing that the read evacuee ID and the accepted vehicle information be associated and registered in the evacuation information database 23, and means for instructing that the read vehicle ID and the accepted vehicle information be associated and registered in the evacuation information database 23. If the evacuee 3 has previously registered evacuee information in the pre-registration database 12, the evacuee information can be registered in the evacuation information database 23 by omitting input of the evacuee information and copying the evacuee information registered in the pre-registration database 12.

[0023] FIG. 5 shows an example of the evacuee information registration process. The evacuee 3 inputs a command to start the evacuee information registration process into the mobile terminal 30. Then, the mobile terminal 30 activates a QR code (registered trademark). The mobile terminal 30 reads the resident ID from a piece of paper on which a QR code (registered trademark) including the resident ID is printed (step S1). The mobile terminal 30 displays on the display whether or not the evacuee information has been pre-registered, and asks the evacuee 3 whether or not the evacuee 3 has pre-registered. The evacuee 3 inputs whether or not the evacuee 3 has pre-registered into the mobile terminal 30. If the evacuee 3 has pre-registered (step S2; Yes), the evacuee 3 inputs the ID of the evacuee 3 registered in the pre-registration database 12 into the mobile terminal 30. The mobile terminal 30 acquires the pre-registered ID (step S3). The mobile terminal 30 transmits the resident ID read in step S1 and the ID at the time of pre-registration acquired in step S2 to the evacuation information management server 20, and instructs the evacuee information to be registered. In response to this instruction, the control unit 22 in the evacuation information management server 20 refers to the pre-registration database 12 using the ID used at the time of pre-registration and acquires the evacuee information of the evacuee 3 from the pre-registration database 12 (step S4). The control unit 22 uses the resident ID read in step S1 to refer to the evacuee table ( FIG. 4 ) in the evacuation information database 23 and registers the “name” and “residential district” acquired from the pre-registration database 12 as the “name” and “residential district” of the data (record) in which the resident ID is registered (step S5). This allows the evacuee information to be registered in the evacuation information database 23 without having to be entered. Note that if the pre-registered evacuee information is stored in the mobile terminal 30, the evacuee information may be transmitted from the mobile terminal 30 to the evacuation information management server 20 and registered in the evacuation information database 23, rather than being acquired from the pre-registration database 12. If there is no pre-registration (step S2; No), the mobile terminal 30 requests the evacuee 3 to enter the evacuee information (step S6). The evacuee 3 inputs the evacuee information into the mobile terminal 30. The mobile terminal 30 acquires the input evacuee information (step S7).The mobile terminal 30 transmits the resident ID read in step S1 and the evacuee information acquired in step S7 to the evacuation information management server 20, and instructs the server to register the evacuee information. Based on this instruction, the control unit 22 in the evacuation information management server uses the transmitted resident ID to refer to the evacuee table (FIG. 3) in the evacuation information database 23, and identifies the data (record) in which the resident ID is registered. The control unit 22 registers the "name" and "residential district" transmitted from the mobile terminal 30 in the "name" and "residential district" of the identified data (step S8). Here, the registration of evacuee information has been described with reference to FIG. 5, but the same applies to the registration of vehicle information.

[0024] Using the mobile terminal 30, the evacuee 3 registers his or her own evacuee information and vehicle information in the pre-registration database 12 in a situation that does not impede the progress of the contamination inspection or the evacuation of other evacuees. For example, after completing the contamination inspection and departing from the inspection site, the evacuee 3 may temporarily stop in a location that will not cause inconvenience to others and register the information, or may register the information while waiting during the contamination inspection. Furthermore, when the evacuee 3 instructs the mobile terminal 30 to register the evacuee information, the mobile terminal 30 may output a message on its display, such as "Please confirm that the situation will not impede the progress of the contamination inspection or evacuation," to prompt the evacuee 3 to confirm whether the situation is appropriate for registering the evacuee information. Alternatively, the mobile terminal 30 may incorporate a control that compares the location information of the mobile terminal 30 with the location information of the inspection site and allows the registration of the evacuee information only if the two are more than a predetermined distance apart. Note that, among the tables illustrated in Figures 3 and 4, the "inspection results" may be registered by the inspection site staff member 4 and cannot be registered from the evacuee 3's mobile terminal 30. Furthermore, in order to respect the disaster situation (no time to register, poor communication conditions, dead battery of mobile terminal 30, etc.) and the thoughts of evacuees 3 (for example, not wanting to register evacuee information that could lead to personal identification, etc.), registration of evacuee information and vehicle information is not mandatory. In other words, the evacuation management system 1 allows evacuees to complete their journey to evacuation shelters with the registered information shown in Figs. 3 and 4 as an example.

[0025] The mobile terminal 40 is a mobile terminal such as a smartphone owned by the staff member 4 at the inspection site. The mobile terminal 40 has the same functions as the mobile terminal 30 described above. For example, if the evacuee 3 does not have the mobile terminal 30, the staff member 4 can use the mobile terminal 40 to register the evacuee 3's evacuation information, etc. However, since registering information by the staff member 4 would hinder the progress of the contamination inspection, it is desirable for the evacuee 3 to perform the registration work in a situation where they do not hinder the contamination inspection or evacuation. One registration work that the staff member 4 performs using the mobile terminal 40 is to associate a vehicle ID with a resident ID. For example, if the staff member 4 determines that vehicle 2 is "contaminated," the staff member 4 collects a piece of paper from the evacuee 3 in vehicle 2 on which a QR code (registered trademark) of the vehicle ID and a piece of paper on which a QR code (registered trademark) of the resident ID of each evacuee 3 are printed, and reads each QR code. The staff member 4 then uses the mobile terminal 40 to associate the vehicle ID with the resident ID. An example of the association process is shown in FIG. 6.

[0026] First, the attendant 4 reads the vehicle ID using the mobile terminal 40 (step S11). Next, the attendant 4 inputs the number of occupants into the mobile terminal 40. The mobile terminal 40 acquires the number of occupants (step S12). The mobile terminal 40 requests the input of resident IDs for the number of occupants (step S13). The attendant 4 reads resident IDs for the number of occupants using the mobile terminal 40 (step S14). The mobile terminal 40 transmits the vehicle ID read in step S11 and the resident IDs for the number of occupants read in step S14 to the evacuation information management server 20, and instructs the server 20 to associate and register the vehicle ID and the resident ID. In the evacuation information management server 20, the control unit 22 uses the transmitted vehicle ID to refer to the vehicle table (FIG. 3) in the evacuation information database 23 based on this instruction, and identifies the data (record) in which the transmitted vehicle ID is registered. The control unit 22 registers the resident ID transmitted together with the vehicle ID in the "resident ID" field of the vehicle table (step S15). This completes the association of the resident ID with the vehicle ID. For example, if the representative's contamination test results in "contamination," the attendant 4 reads the QR code of the evacuee ID owned by the representative using the mobile terminal 40 and queries the evacuation information management server 20. The control unit 22 of the evacuation information management server 20 searches the vehicle table, identifies the evacuee IDs of the remaining occupants who will be riding in the same vehicle 2, and transmits the identified evacuee IDs and the vehicle ID of the vehicle 2 in which the evacuee will be riding to the mobile terminal 40. This enables the attendant 4 to identify the evacuee IDs of the remaining occupants who will be subject to the contamination test, and the vehicle ID of the vehicle 2 in which the remaining occupants are waiting.

[0027] Furthermore, the attendant 4 may input the inspection results of the vehicle inspection, the representative inspection, and the remaining occupant inspection from the mobile terminal 40 and register them in the evacuation information database 23. For example, if the vehicle inspection results in "contamination," the attendant 4 reads the QR code (registered trademark) of the vehicle ID and inputs "Vehicle inspection: contaminated" into the mobile terminal 40. The mobile terminal 40 transmits the vehicle ID and "Vehicle inspection: contaminated" to the evacuation information management server 20. The evacuation information management server 20 references the vehicle table, identifies the data in which the transmitted vehicle ID is registered, and registers "contaminated" in the "inspection results" of the identified data. The same applies when the vehicle inspection results in "no contamination" or when contamination inspections are conducted on the representative and other occupants. Furthermore, when decontamination of the vehicle 2 is completed, the attendant 4 reads the QR code (registered trademark) of the vehicle ID and inputs "decontaminated." Then, by a similar process, "decontaminated" is registered in the "inspection results" of the vehicle table. By registering the inspection results in this manner, even if an evacuee 3 who has completed the inspection loses their certificate, for example, they can refer to the evacuation information database 23 to confirm that they have undergone the inspection and that the inspection results show no contamination ("not contaminated" or "decontaminated"). To save time and effort, the inspection results may be registered only if "contaminated," and if no contamination is found, the "inspection results" may be left blank. Furthermore, in addition to or instead of information such as contamination or no contamination, the inspection date and time may be registered in the "inspection results" of the evacuation information database 23 (vehicle table and evacuee table).

[0028] An example of a vehicle table after vehicle information registration is shown in Figure 7. In the data for vehicle ID "AC00001," only "XXXXX1" is registered as the "Vehicle Number" and "No Contamination" is registered as the "Inspection Result." This is because vehicle 2 with vehicle ID "AC00001" was not contaminated, so the vehicle ID was not associated with the resident ID. In the data for vehicle IDs "AC00002" and "BC00001," information is registered for the "Number of Occupants" and resident ID in addition to the "Inspection Result."

[0029] An example of an evacuee table after evacuee information has been registered is shown in Figure 8. In the data for resident ID "A00001," information is registered for "Name" and "Residential District," but "Test Results" remains blank. This is because no contamination was found during the vehicle inspection, and the person left the testing site without undergoing testing. The same is true for resident ID "A00002," who is riding in the same vehicle.

[0030] The mobile terminal 50 is a mobile terminal such as a smartphone owned by the evacuation center staff member 5. The mobile terminal 50 includes a means for reading a resident ID and a vehicle ID from a piece of paper on which a QR code (registered trademark) is printed that the evacuee 3 possesses, and a means for using the read IDs to refer to the evacuation information database 23 and acquire the name of the evacuee 3, information on the license plate of the vehicle 2, and the results of a contamination test. For example, the staff member 5 uses the mobile terminal 50 to read the QR code (registered trademark) of the vehicle ID and transmits the read vehicle ID to the evacuation information management server 20 to instruct the server 20 to provide information about the vehicle 2 indicated by the vehicle ID. In the evacuation information management server 20, the control unit 22 uses the transmitted vehicle ID to refer to the evacuation information database 23 and identifies data in which information about the vehicle ID is registered. The control unit 22 reads out information for each item shown in FIG. 7 from the identified data and transmits it to the mobile terminal 50. The mobile terminal 50 outputs the transmitted information to a display unit. The staff member 5 can refer to the information output on the display unit to check whether there are any errors in the vehicle 2, whether there are any errors in the number of occupants, whether the vehicle has undergone inspection, etc. The same process can also be used to check evacuee information. This makes it possible to check the information on the evacuees 3 and vehicle 2 to be accepted and the results of the inspection, regardless of the certificate issued at the contamination inspection site.

[0031] (effect) In the past, when a person who had not registered their evacuee information in advance arrived at a contamination inspection site, they had to register their evacuee information, etc., at the gate of the inspection site, causing congestion at the gate. In contrast, according to this embodiment, media with QR codes for resident IDs and vehicle IDs printed on them are distributed at the contamination inspection site, regardless of whether or not they had registered their information in advance. The resident IDs and vehicle IDs printed on the distributed media are used to register evacuee information and vehicle information at a time and location that does not interfere with contamination inspections or evacuation. For evacuees who have pre-registered, the pre-registered evacuee information and vehicle information are copied and registered in association with the resident ID and vehicle ID issued at the inspection site. This enables contamination inspections and evacuations to be carried out without the need for registration of evacuee information, etc., becoming a bottleneck, even in emergencies.

[0032] The above embodiment is merely an example. For example, the resident ID and the like may not be printed on paper but may be transmitted to the mobile terminal 30 in the form of electronic data, or may be transmitted to the mobile terminal 30 as ID information such as "A00001" without being encoded. Furthermore, the terminal device 41 may not be provided, and the resident ID and the like may be transmitted directly from the evacuation information management server 20 to the mobile terminal 30. Furthermore, for example, the pre-registration server 10 and the evacuation information management server 20 may be implemented in the same device, or the ID issuing unit 21 may be provided in the terminal device 41.

[0033] FIG. 9 is a diagram showing an example of the hardware configuration of an evacuation management system according to an embodiment. The computer 900 includes a CPU 901, a main storage device 902, an auxiliary storage device 903, an input / output interface 904, and a communication interface 905. The above-described pre-registration server 10, evacuation information management server 20, mobile terminals 30 to 50, and terminal device 41 are implemented in the computer 900. The above-described functions are stored in the auxiliary storage device 903 in the form of a program. The CPU 901 reads the program from the auxiliary storage device 903, loads it into the main storage device 902, and executes the above-described processing in accordance with the program. The CPU 901 also allocates a memory area in the main storage device 902 in accordance with the program. The CPU 901 also allocates a memory area in the auxiliary storage device 903 for storing data being processed in accordance with the program.

[0034] A program for implementing all or part of the functions of the pre-registration server 10, the evacuation information management server 20, the mobile terminals 30-50, and the terminal device 41 may be recorded on a computer-readable recording medium, and the program may be loaded into a computer system and executed to perform processing by each functional unit. The term "computer system" as used herein includes hardware such as an OS and peripheral devices. Furthermore, if a WWW system is used, the term "computer system" also includes a homepage provision environment (or display environment). Furthermore, the term "computer-readable recording medium" refers to portable media such as CDs, DVDs, and USBs, as well as storage devices such as hard disks built into the computer system. Furthermore, if the program is distributed to the computer 900 via a communication line, the computer 900 that receives the program may load the program into the main storage device 902 and execute the above-described processing. Furthermore, the program may be for implementing part of the above-described functions, or may be capable of implementing the above-described functions in combination with a program already stored in the computer system.

[0035] As described above, several embodiments according to the present disclosure have been described, but all of these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments can be implemented in various other forms, and various omissions, substitutions, and modifications can be made without departing from the spirit of the invention. These embodiments and their modifications are included in the scope of the invention and its equivalents as defined in the claims, as well as in the scope and spirit of the invention.

[0036] <Additional Notes> The evacuation management system and evacuation management method described in each embodiment can be understood, for example, as follows.

[0037] (1) An evacuation management system according to a first aspect is an evacuation management system that manages information on evacuees who arrive at an inspection site during a nuclear disaster, and includes a pre-registration server, an evacuation information management server, and a terminal device. The pre-registration server includes a pre-registration database in which evacuee information including the names and residential areas of the evacuees is registered. The evacuation information management server includes an ID issuing unit that issues an evacuee ID to each evacuee who arrives at the inspection site, an output unit that outputs the issued evacuee ID to a predetermined medium, an evacuee database that stores the evacuee ID and the evacuee information of the evacuee in association with each other, and a registration unit that registers the evacuee ID and the evacuee information of the evacuee in association with each other in the evacuee database. The terminal device: The device is equipped with a reading unit that reads the evacuee ID output to the medium, an instruction unit that instructs the registration of the evacuee information of the evacuee corresponding to the evacuee ID, and a reception unit that accepts the input of the evacuee information, and when the instruction unit of the terminal device instructs the registration of the evacuee information related to the evacuee ID read by the reading unit, the registration unit of the evacuation information management server registers the evacuee information registered in the pre-registration database in the evacuee database for evacuees whose evacuee information is registered in the pre-registration database, and registers the evacuee information received by the reception unit of the terminal device in the evacuee database for evacuees whose evacuee information is not registered in the pre-registration database. This will allow information on evacuees arriving at the testing site to be collected and managed without causing delays in testing or evacuation.

[0038] (2) A second aspect of the evacuation management system is the evacuation management system of (1), wherein the pre-registration server registers, in the pre-registration database, vehicle information for identifying the vehicle used by the evacuee for evacuation in addition to the evacuee information, and the evacuation information management server further includes a vehicle database that stores the vehicle ID and the vehicle information in association with each other; The ID issuing unit issues a vehicle ID for each vehicle that arrives at the inspection site, the output unit outputs the issued vehicle ID to a specified medium, the registration unit registers the vehicle ID and the vehicle information in association with each other in the vehicle database, and in the terminal device, the reading unit reads the vehicle ID output to the medium, the instruction unit instructs the registration of the vehicle information corresponding to the vehicle ID, the reception unit accepts the input of the vehicle information, and when the instruction unit instructs the registration of the vehicle information related to the vehicle ID read by the reading unit, the registration unit registers the vehicle information registered in the pre-registration database in the vehicle database for vehicles whose vehicle information is registered in the pre-registration database, and registers the vehicle information accepted by the reception unit of the terminal device in the vehicle database for vehicles whose vehicle information is not registered in the pre-registration database. This will allow information on vehicles arriving at the inspection site to be obtained and managed without causing delays in inspection or evacuation.

[0039] (3) The third aspect of the evacuation management system is the evacuation management system of (2), wherein the vehicle database stores the evacuee ID of the evacuee riding in the vehicle corresponding to the vehicle ID in association with the vehicle ID, and when the inspection result indicates that the vehicle is contaminated, the reading unit reads the vehicle ID and the evacuee ID of the evacuee riding in the vehicle corresponding to the vehicle ID, and the registration unit records the vehicle ID read by the reading unit and the evacuee ID read by the reading unit in association with each other in the vehicle database. This reduces delays in inspection caused by not knowing the relationship between the vehicle 2 and the evacuees 3 on board.

[0040] (4) The evacuation management system according to the fourth aspect is the evacuation management system of (3), wherein the vehicle database stores the inspection results for the vehicle corresponding to the vehicle ID in association with the vehicle ID, and when the inspection result indicates that the vehicle is contaminated, the reading unit reads the vehicle ID, the reception unit accepts the input of the inspection result, and the registration unit records the vehicle ID read by the reading unit and the inspection result accepted by the reception unit in association with each other in the vehicle database. This allows the results of contamination inspection of vehicle 2 to be recorded.

[0041] (5) The fifth aspect of the evacuation management system is an evacuation management system according to (1) to (2), wherein the evacuee database stores the results of a contamination test for the evacuee corresponding to the evacuee ID in association with the evacuee ID, and when the test result indicates that the evacuee is contaminated, the reading unit reads the evacuee ID, the reception unit accepts the input of the test result, and the registration unit records the evacuee ID read by the reading unit and the test result accepted by the reception unit in association with each other in the evacuee database. This allows the results of contamination testing of evacuees 3 to be recorded.

[0042] (6) The evacuation management system according to the sixth aspect is the evacuation management system of (5), further comprising a confirmation terminal device installed at a location where the evacuees arrive after the inspection site, the confirmation terminal device comprising a reading unit that reads the evacuee ID output to the medium, an acquisition unit that acquires the inspection results recorded in the evacuee database in correspondence with the read evacuee ID, and an output unit that outputs the acquired inspection results. This allows the results of the contamination test for evacuee 3 to be confirmed at the evacuation shelter.

[0043] (7) The evacuation management system according to the seventh aspect is the evacuation management system of (4), further comprising a confirmation terminal device installed at a location where the evacuees arrive after the inspection site, the confirmation terminal device comprising a reading unit that reads the vehicle ID output to the medium, an acquisition unit that acquires the inspection results recorded in the vehicle database in correspondence with the read vehicle ID, and an output unit that outputs the acquired inspection results. This allows the results of the contamination inspection of vehicle 2 to be checked at the evacuation shelter.

[0044] (8) The evacuation management system according to the eighth aspect is an evacuation management system according to any one of (1) to (7), wherein the instruction unit of the terminal device instructs the registration of the evacuee information in a situation that does not hinder the progress of the inspection or the evacuation of the evacuees. This will allow information on evacuees arriving at the testing site to be collected and managed without causing delays in testing or evacuation.

[0045] (9) An evacuation management method according to a ninth aspect is an evacuation management method for managing information on evacuees who have arrived at an inspection site where an inspection is to be conducted in the event of a nuclear disaster, the method comprising the steps of an evacuation information management server issuing an evacuee ID to each evacuee who has arrived at the site, outputting the issued evacuee ID to a predetermined medium, and using a terminal device in a situation that does not impede the progress of the inspection or the evacuation of the evacuees, reading the evacuee ID output to the medium and issuing an instruction to register the evacuee information of the evacuee corresponding to the read evacuee ID, and the evacuation information management server, based on the instruction, and a step of registering the evacuee ID of the evacuee and the evacuee information of the evacuee in an evacuee database in association with each other. In the step of registering, the evacuation information management server registers the evacuee information registered in the pre-registration database in the evacuee database for the evacuee whose information is registered in a pre-registration database in which evacuee information including the evacuee's name and residential area is registered, and registers the evacuee information inputted by the terminal device in the evacuee database for the evacuee whose information is not registered in the pre-registration database. [Explanation of symbols]

[0046] 1. Evacuation Management System 2. Vehicle 3...evacuee 4,5...Staff 10. Pre-registration server 11. Registration Department 12. Pre-registration database 20. Evacuation information management server 21. ID Issuance Department 22 Control section 23 Evacuation Information Database 30, 40, 50... Mobile devices 41 Terminal device 42 Printer 900···Computer 901 CPU 902...Main memory 903...Auxiliary storage device 904 Input / Output Interface 905···Communication Interface

Claims

1. An evacuation management system for managing information of evacuees who arrive at an inspection site where an inspection is performed in the event of a nuclear disaster, comprising: a pre-registration server; an evacuation information management server; and a terminal device; The pre-registration server, A pre-registration database containing information on evacuees, including their names and residential areas; Equipped with The evacuation information management server includes: an ID issuing unit that issues a refugee ID to each of the evacuees who arrive at the inspection site; an output unit that outputs the issued evacuee ID to a predetermined medium; a refugee database that stores the refugee ID and the refugee information of the refugee in association with each other; a registration unit that registers the evacuee ID of the evacuee and the evacuee information of the evacuee in the evacuee database in association with each other; Equipped with The terminal device A reading unit that reads the evacuee ID output to the medium; An instruction unit that instructs registration of the evacuee information of the evacuee corresponding to the evacuee ID; A reception unit that receives input of the evacuee information; Equipped with When the instruction unit of the terminal device instructs the registration of the evacuee information related to the evacuee ID read by the reading unit, The registration unit of the evacuation information management server For the evacuees whose evacuee information is registered in the pre-registration database, the evacuee information registered in the pre-registration database is registered in the evacuee database; For the evacuees whose evacuee information is not registered in the pre-registration database, the evacuee information received by the reception unit of the terminal device is registered in the evacuee database. Evacuation management system.

2. In the pre-registration server, In addition to the evacuee information, vehicle information for identifying a vehicle used by the evacuee for evacuation is registered in the pre-registration database, The evacuation information management server includes: a vehicle database that stores the vehicle ID and the vehicle information in association with each other; Further equipped with The ID issuing unit issues a vehicle ID for each vehicle that arrives at the inspection site, The output unit outputs the issued vehicle ID to a predetermined medium, The registration unit registers the vehicle ID and the vehicle information in the vehicle database in association with each other, In the terminal device, The reading unit reads the vehicle ID outputted to the medium, The instruction unit instructs registration of the vehicle information corresponding to the vehicle ID, The reception unit receives an input of the vehicle information, When the instruction unit instructs the registration of the vehicle information related to the vehicle ID read by the reading unit, The registration unit is For the vehicle whose vehicle information is registered in the pre-registration database, registering the vehicle information registered in the pre-registration database in the vehicle database; For the vehicle whose vehicle information is not registered in the advance registration database, the vehicle information accepted by the acceptance unit of the terminal device is registered in the vehicle database. The evacuation management system according to claim 1 .

3. the vehicle database stores the evacuee ID of the evacuee who rides in the vehicle corresponding to the vehicle ID in association with the vehicle ID; If the inspection result indicates that the vehicle is contaminated, The reading unit reads the vehicle ID and the evacuee ID of the evacuee who gets into the vehicle corresponding to the vehicle ID, The registration unit associates the vehicle ID read by the reading unit with the evacuee ID read by the reading unit and records them in the vehicle database. The evacuation management system according to claim 2.

4. the vehicle database stores the inspection results of the inspection for the vehicle corresponding to the vehicle ID in association with the vehicle ID; If the inspection result indicates that the vehicle is contaminated, The reading unit reads the vehicle ID, The reception unit receives an input of the test result, The registration unit associates the vehicle ID read by the reading unit with the inspection result accepted by the acceptance unit and records them in the vehicle database. The evacuation management system according to claim 2 or 3.

5. the evacuee database stores the test results of the test on the evacuee corresponding to the evacuee ID in association with the evacuee ID; If the test result indicates that the evacuees are contaminated, The reading unit reads the evacuee ID, The reception unit receives an input of the test result, The registration unit associates the evacuee ID read by the reading unit with the test result accepted by the acceptance unit and records them in the evacuee database. The evacuation management system according to claim 1 or 2.

6. The evacuees are further provided with a confirmation terminal device installed at a location where the evacuees arrive after the inspection site, The confirmation terminal device is A reading unit that reads the evacuee ID output to the medium; an acquisition unit that acquires the inspection results recorded in the refuge database in association with the read refugee ID; an output unit that outputs the acquired inspection results; The evacuation management system according to claim 5 .

7. The evacuees are further provided with a confirmation terminal device installed at a location where the evacuees arrive after the inspection site, The confirmation terminal device is A reading unit that reads the vehicle ID outputted to the medium; an acquisition unit that acquires the inspection result recorded in the vehicle database in association with the read vehicle ID; an output unit that outputs the acquired inspection results; The evacuation management system according to claim 4 .

8. The instruction unit of the terminal device instructs the registration of the evacuee information in a situation that does not hinder the progress of the inspection or the evacuation of the evacuee. The evacuation management system according to claim 1 .

9. An evacuation management method for managing information on evacuees who arrive at an inspection site where an inspection is performed during a nuclear disaster, comprising: An evacuation information management server issues an evacuee ID to each of the evacuees who arrive at the inspection site; outputting the issued evacuee ID to a predetermined medium; a step of reading the evacuee ID outputted to the medium using a terminal device in a situation that does not impede the progress of the inspection or the evacuation of the evacuee, and instructing the registration of evacuee information including the name and residential area of ​​the evacuee corresponding to the read evacuee ID; The evacuation information management server registers the evacuee ID of the evacuee and the evacuee information of the evacuee in a evacuee database in association with each other based on the instruction; having In the step of registering, the evacuation information management server, for an evacuee whose information is registered in a pre-registration database in which evacuee information including the name and residential area of ​​the evacuee is registered, registers the evacuee information registered in the pre-registration database in the evacuee database, and, for an evacuee whose information is not registered in the pre-registration database, registers the evacuee information inputted by the terminal device in the evacuee database; Evacuation management methods.

Images