JP7792886B2 - Evacuation Information Management System - Google Patents

Description

This disclosure relates to an evacuation information management system.

Patent Document 1 discloses a system for creating a plan for evacuating nearby residents to a distant evacuation shelter in the event of a nuclear facility disaster. Evacuation shelters for nearby residents are located tens to hundreds of kilometers away from the nuclear facility, and evacuees often evacuate via (1) an indoor evacuation site, (2) an evacuation exit inspection site, (3) an evacuation transit point, and then (4) the evacuation shelter. Traditionally, evacuees' information has often been managed by having them enter their personal information at each of the sites (1) through (4). However, this method does not allow for information sharing between venues. Therefore, a system is being considered in which computer terminals are installed at each venue, the terminals at each venue are connected to a disaster response headquarters server via a network, and evacuee information entered at each venue is sent to the disaster response headquarters server. However, large-scale communication disruptions are possible during a disaster, and if a failure occurs in the network connecting the venues and the disaster response headquarters, sharing evacuation status information becomes difficult.

In addition, (2) at the inspection site when evacuating, the need for inspection of passengers will depend on the contamination level of the vehicle, and the contamination level of the representative passenger will determine the need for inspection of other passengers. Vehicle contamination inspections and resident contamination inspections are separated for the purpose of accident prevention, etc., and it is necessary to link and manage the sharing of information between vehicles and passengers.

The system described in Patent Document 1 creates a plan to transport evacuees from (1) to (2) using a first vehicle and a plan to transport evacuees from (2) to (4) using a second vehicle in order to efficiently evacuate evacuees, but does not mention managing information about evacuees.

Japanese Patent Application Laid-Open No. 2021-12424

There is a need for an information management system that can manage information about evacuees in a shareable manner, even if communication failure occurs during a disaster.

This disclosure provides an evacuation information management system that can solve the above problems.

The evacuation information management system disclosed herein includes a first terminal device provided in a first venue where evacuees are staying, a second terminal device provided in a second venue where the evacuees will move from the first venue to stay next, and a server device connected to the first terminal device and the second terminal device via a network, wherein the first terminal device includes a first storage unit that stores a resident database, a first resident ID issuing unit that issues a resident ID including identification information of the first venue and information that distinguishes the evacuees from other evacuees, a first resident ID registration unit that associates the resident ID with personal information of the evacuees and registers them in the resident database stored in the first storage unit, a first resident ID output unit that outputs the resident ID in a manner that the evacuees can take it with them, a first synchronization unit that determines whether the network is capable of communication, and a first communication unit, and the second terminal device includes a second storage unit that stores the resident database and a first resident ID issuing unit that issues a resident ID that includes identification information of the first venue and information that distinguishes the evacuees from other evacuees a second resident ID acquisition unit that acquires the resident ID acquired by the second acquisition unit and the identification information of the second venue in association with each other and registers them in the resident database stored in the second storage unit; a second synchronization unit that determines whether the network is capable of communication; and a second communication unit. The server device comprises a server storage unit that stores the resident database, a server resident ID registration unit that associates the resident ID, the personal information, and the identification information of the second venue in the resident database and registers them in the resident database, and a server communication unit. When the first synchronization unit determines that the network is capable of communication, the first communication unit transmits the resident ID and the personal information registered in the resident database stored in the first storage unit to the server device, and the server communication unit receives the transmitted resident ID and the personal information. The server resident ID registration unit associates the resident ID and the personal information with each other and registers them in the resident database stored in the server storage unit. the second communication unit transmits the resident ID and identification information of the second venue registered in the resident database stored in the second storage unit to the server device when the second synchronization unit determines that communication is possible over the network, the server communication unit receives the transmitted resident ID and identification information of the second venue, the server resident ID registration unit associates the resident ID with the identification information of the second venue and registers them in the resident database stored in the server storage unit , the first terminal device has a first vehicle ID issuing unit that issues a vehicle ID including the identification information of the first venue and information that distinguishes a vehicle in which the evacuee is riding from other vehicles, and an occupant ID in which information that distinguishes the evacuee from other evacuees riding in the vehicle is added to the vehicle ID, a first vehicle ID registration unit that associates the vehicle ID with the occupant ID and registers them in the vehicle database stored in the first storage unit, and a The system further includes a first vehicle ID output unit that outputs the resident ID and the occupant ID in a manner that the evacuee can carry it with them, and a first code information acquisition unit that acquires the resident ID output by the first resident ID output unit, and the vehicle ID and the occupant ID output by the first vehicle ID output unit, wherein when the first code information acquisition unit acquires the resident ID, the vehicle ID, and the occupant ID, the first vehicle ID registration unit rewrites the occupant ID registered in the vehicle database in association with the vehicle ID to the resident ID, and when the first code information acquisition unit determines that the network is capable of communication, the first communication unit transmits the vehicle ID and the resident ID registered in the vehicle database stored in the first memory unit to the server device, the server communication unit receives the transmitted vehicle ID and resident ID, and the server resident ID registration unit associates the vehicle ID and the resident ID and registers them in the vehicle database stored in the server memory unit.

The above-mentioned evacuation information management system allows evacuees' information to be managed in a shareable manner, even if communication failure occurs during a disaster.

1 is a schematic diagram illustrating an example of an evacuation route and evacuation information management system according to an embodiment. FIG. 1 is a schematic diagram illustrating an example of the configuration of an evacuation inspection site according to an embodiment. 1 is a functional block diagram illustrating an example of an evacuation information management system according to an embodiment. FIG. 2 is a diagram illustrating an example of a vehicle DB according to the embodiment. FIG. 2 is a diagram illustrating an example of an evacuee DB according to the embodiment. 10 is a flowchart illustrating an example of a synchronization process according to the embodiment. 1 is a diagram illustrating an example of a hardware configuration of an evacuation information management system according to an embodiment.

<Embodiment>
(overview)
Hereinafter, the method for managing and sharing evacuation information according to the present disclosure will be described with reference to the drawings.
FIG. 1 is a schematic diagram illustrating an example of an evacuation route and evacuation information management system according to an embodiment.
When a disaster occurs at nuclear facility P, evacuees 6 living in the vicinity temporarily evacuate to indoor evacuation venue 1 to reduce exposure to radioactive materials present outdoors. Indoor evacuation venue 1 is, for example, a community center or a school. The evacuees 6 then board vehicles 7 and head to evacuation/exit inspection venue 2, where they are inspected for radioactive materials adhering to their vehicles. Once it is confirmed that the level of contamination of the evacuees 6 and their vehicles 7 is within an acceptable range, they are permitted to move to a distant evacuation shelter 4. Because evacuation shelter 4 is far away, the evacuees 6 and their vehicles 7 travel to evacuation shelter 4 via evacuation route 3 on the way. The evacuees do not necessarily move in the following order: indoor evacuation venue 1, evacuation/exit inspection venue 2, evacuation route 3, and evacuation shelter 4. For example, a person may move from their home to the evacuation inspection site 2, evacuation route 3, and evacuation shelter 4 in this order without passing through the indoor evacuation site 1, or may avoid the evacuation inspection site 2 due to congestion, or may move to the evacuation shelter 4 without passing through the evacuation route 3, or may evacuate to the home of a relative or other person instead of the evacuation shelter 4, or may pass through multiple indoor evacuation sites 1 and evacuation routes 3. The evacuation information management system 100 illustrated in FIG. 3 manages information on evacuees 6 and vehicles 7 (e.g., information on which evacuees 6 are staying at which site, which evacuees 6 are in which vehicles 7, and the route they are taking to the evacuation shelter 4), and enables the information to be shared among terminals provided at the indoor evacuation site 1, evacuation inspection site 2, evacuation route 3, and evacuation shelter 4, as well as a server 50 provided at the disaster response headquarters 5.

<System configuration of indoor evacuation venue 1>
As shown in FIG. 1 , the indoor evacuation site 1 is equipped with one or more terminals 10 and one or more routers 11. The terminals 10 are connected to a reader 12 for reading barcodes and QR codes (registered trademark) and a printer 13 for printing barcodes and other data. The indoor evacuation site 1 may also be equipped with a storage device (not shown). The router 11 is, for example, a wireless router. The terminals 10 and the router 11 form a local network. If an evacuee 6 who has evacuated to the indoor evacuation site 1 has a mobile device 60 such as a smartphone, the mobile device 60 can be connected to the local network through settings. As shown in FIG. 3 , the terminals 10 are connected to a wide-area network (NW) such as the Internet, a carrier network, or a cellular network. As long as there is no communication failure in the wide-area network (NW), the terminals 10 can communicate with a server 50 in the disaster response headquarters 5.

(Functions and configuration of terminal 10)
The functions and configuration of the terminal 10 will be described with reference to Fig. 3. Fig. 3 is a functional block diagram showing an example of an evacuation information management system. The terminal 10 includes an input receiving unit 101, a code information management unit 102, a DB management unit 103, a DB synchronization unit 104, an output unit 105, a storage unit 106, and a communication unit 107.
The input receiving unit 101 receives input of settings and instruction operations from staff at the indoor evacuation venue 1 .
The code information management unit 102 issues a resident ID, which is identification information for the evacuee 6. The resident ID is issued for each evacuee 6 and is composed of, for example, the "venue ID of indoor evacuation venue 1" + a "serial number." The code information management unit 102 generates resident code information such as a two-dimensional barcode or QR code (registered trademark). The resident code information includes the resident ID or the resident ID and the history of the evacuation facility, etc., of the evacuee 6. The code information management unit 102 acquires the resident code information read by the reading device 12 and extracts the resident ID and the history of the evacuation facility, etc., from the resident code information. The resident ID does not have to be composed of the "venue ID of indoor evacuation venue 1" + a "serial number," as long as it includes information that identifies the indoor evacuation venue 1 and information that distinguishes the evacuee 6 from other evacuees 6.

The DB management unit 103 registers the resident ID and personal information of the evacuees 6, history of evacuation facilities, etc. in a resident database (hereinafter referred to as the resident DB). The DB management unit 103 also reads information about the evacuees 6 from the resident DB using the resident ID as a key. An example of the layout of the resident DB is shown in Figure 4.
The DB synchronization unit 104 determines whether communication is possible over the wide area network NW connecting the terminal 10 and the server 50, and if communication is possible, synchronizes the information registered in the resident DB (the resident DB is registered, for example, in the memory unit 106 or a storage device not shown) present on the local network constructed in the indoor evacuation venue 1 with the information registered in the resident DB stored in the server 50 of the disaster response headquarters 5. Because communication failures may occur in the event of a disaster, information on evacuees 6 who have evacuated to the indoor evacuation venue 1 is temporarily stored in the resident DB on the local network, and when communication is possible, this information is sent to the server 50 to share the information.
The output unit 105 displays the information registered in the resident DB on a display device, and outputs the resident code information in a format that can be carried by the evacuees 6. For example, the output unit 105 prints image data including the resident code information on paper using the printer 13, or outputs the image data to the mobile terminal 60 via the communication unit 107.
The storage unit 106 stores a resident DB, the venue ID of the indoor evacuation venue 1, and the like.
The communication unit 107 communicates with other devices and has a communication module for a local network established in the indoor evacuation venue 1 and a communication module for a wide area network NW such as the Internet.

(Processing upon arrival at the first indoor evacuation site 1)
When the evacuee 6 arrives at the indoor evacuation venue 1, a staff member at the indoor evacuation venue 1 inputs the evacuee 6's personal information and the like into the terminal 10. The evacuee 6 may operate his/her mobile terminal 60 to connect to the local network, input the personal information and the like into the mobile terminal 60, and transmit the input information to the terminal 10. The input receiving unit 101 acquires the input or transmitted personal information and the like. When the personal information and the like is input or transmitted to the terminal 10, the output unit 105 displays the input information and the like on the display device. After the staff member confirms the displayed information, he/she instructs the terminal 10 to register the input information. The code information management unit 102 then issues a resident ID. The resident ID consists of the "venue ID + serial number" of the indoor evacuation venue 1. Assuming the venue ID is "A1" and the serial number is a four-digit number starting with 0001, the first evacuee 6 to register their personal information at the indoor evacuation venue 1 is issued a resident ID of "A10001," and the second evacuee 6 is issued a resident ID of "A10002." The DB management unit 103 associates the issued resident ID with the entered personal information and records it in a resident DB on the local network. The resident DB is pre-registered in the memory unit 106 or the memory unit 106 of another terminal 10 connected to the local network or in an external storage device. For example, the DB management unit 103 registers the information of the evacuee 6 in the fields shown in FIG. 4 , including "Resident ID,""Name,""Address,""TelephoneNumber,""Indoor Evacuation Location," and "Indoor Evacuation Location Start Time." The DB management unit 103 also registers "ON" in the "Non-Shared Flag" field shown in FIG. 4 . The non-shared flag being ON indicates that the data is not shared with the server 50. When the DB management unit 103 registers the personal information of the evacuee 6 in the resident DB, the output unit 105 outputs resident code information. For example, the code information management unit 102 generates resident code information such as a two-dimensional barcode or QR code (registered trademark) that encodes the resident ID, and the output unit 105 prints the generated resident code information on paper using the printer 13. The paper on which the resident code information is printed is handed to the evacuee 6. Also, for example, the output unit 105 transmits image data of the resident code information to the mobile terminal 60 of the evacuee 6 via the communication unit 107. The output resident code information is used when the evacuee 6 moves to the next venue. Also, for example, the evacuee 6 measures their body temperature periodically. An attendant inputs the body temperature of the evacuee 6 into the terminal 10 and instructs registration. The DB management unit 103 registers the input body temperature in the resident DB. Periodically measured body temperatures are registered in the "body temperature while sheltering indoors-1" to "body temperature while sheltering indoors-n" fields of the resident database.

(Processing when moving indoor evacuation venue 1)
There are multiple indoor evacuation venues 1 in the vicinity of the nuclear facility P, and evacuees 6 may move between indoor evacuation venues 1. In this case, the evacuees 6 present a piece of paper with resident code information printed on it or a mobile terminal 60 displaying the resident code information at the indoor evacuation venue 1 from which they are moving. A staff member at the venue from which they are moving reads the resident code information using a reading device 12. The code information management unit 102 acquires the resident code information, extracts the resident ID, and outputs it to the DB management unit 103. The DB management unit 103 references the resident DB using the extracted resident ID as a key and registers the current time in the "indoor evacuation location end time" field of the corresponding data (record). Once the evacuation time has been registered, the evacuees 6 move to the next indoor evacuation venue 1. The evacuees 6 present a piece of paper with resident code information printed on it or a mobile terminal 60 displaying the resident code information at the indoor evacuation venue 1 to which they are moving. A staff member at the venue to which they are moving reads the resident code information using a reading device 12. The code information management unit 102 acquires resident code information, extracts the resident ID, and outputs it to the DB management unit 103. The DB management unit 103 references the resident DB using the resident ID as a key, reads out personal information of the evacuee 6, and outputs it to the output unit 105. The output unit 105 displays the information read out from the resident DB on a display device. An attendant confirms the information of the newly arrived evacuee 6. The evacuee 6 also measures his/her body temperature. The attendant inputs the evacuee 6's body temperature into the terminal 10 and instructs it to be registered. The DB management unit 103 updates the information of the evacuee 6 registered in the resident DB. For example, the DB management unit 103 registers the ID of the destination indoor evacuation venue 1 in the "venue number""1" of the resident DB illustrated in FIG. 4, and registers the current time in the "arrival time" and the body temperature of the evacuee 6 measured at "body temperature - 1." If evacuee 6 subsequently measures his/her temperature at the venue to which he/she is moving, that information is registered in the resident database under "Temperature -2" to "Temperature -k" as the "1st" entry. Also, when evacuee 6 leaves indoor evacuation venue 1, the time of departure is registered as the "Departure Time" as the "1st" entry in the resident database. The information registered in the "venue number,""arrivaltime," and "departure time" in the resident database is the history of the evacuation facility, etc.

If the resident ID of the evacuee 6 who has moved from another location is not registered in the resident DB existing on the local network of the destination, the DB management unit 103 newly registers the resident ID extracted from the code information in the resident DB. At this time, registration of the evacuee 6's personal information can be omitted. The personal information registered at the indoor evacuation site 1 where the evacuee 6 first evacuated is also registered in the resident DB of the other indoor evacuation site 1 via the disaster response headquarters server 50 through the synchronization process described below, provided there is no communication failure. If there is a communication failure, the synchronization process is not performed, resulting in a situation where the personal information of the evacuee 6 is not registered in the resident DB of the other indoor evacuation site 1. In such a case, only the key resident ID is registered in the local resident DB, and only information that should be registered at the indoor evacuation site 1 (e.g., evacuation facility history, regularly measured body temperature, etc.) is registered. Eventually, when communication over the wide area network NW is restored, synchronization with the server 50 is performed, and the personal information entered at the other site is updated. When the DB management unit 103 registers the information of the evacuee 6 in the resident DB, the output unit 105 prints the resident code information, including the resident ID and history of evacuation facilities, on paper using the printer 13, or transmits it to the mobile terminal 60 via the communication unit 107. The paper with the printed resident code information is handed to the evacuee 6. The resident code information, including the resident ID and history of evacuation facilities, is used when the evacuee 6 moves to the next venue. The resident code information is updated every time the evacuee 6 moves to a different venue (movement of venues is not limited to movement between indoor evacuation venues 1, but also includes movement from indoor evacuation venue 1 to evacuation exit inspection venue 2, movement from evacuation exit inspection venue 2 to evacuation route 3, and movement from evacuation route 3 to evacuation shelter 4). For example, if evacuee 6 was assigned a resident ID of "A10001" at indoor evacuation venue 1 where he or she first evacuated, and then moved to indoor evacuation venue 1 with venue ID = A2, and then moved to indoor evacuation venue 1 with venue ID = A3, resident code information including, for example, "A10001-A2-A3" would be output at indoor evacuation venue 1 with venue ID = A3.

<System configuration of evacuation inspection site 2>
Evacuees 6 who temporarily evacuate to the indoor evacuation site 1 board vehicles 7 and travel to a distant evacuation shelter 4. The vehicles 7 may be private cars or buses provided by local governments or other organizations. An evacuation/exit inspection site 2 is located along the route of the evacuees 6, where radioactive materials attached to the vehicles 7 and the evacuees 6 are inspected to determine whether they are within acceptable limits. A plurality of evacuation/exit inspection sites 2 are located approximately 30 km away from the nuclear facility P. As shown in FIG. 1 , the evacuation/exit inspection site 2 is provided with a plurality of terminals 20 and one or more routers 21. The terminals 20 are connected to a reader 22 for reading various code information and a printer 23 for printing the various code information. The evacuation/exit inspection site 2 may also be provided with a storage device (not shown). The router 21 is, for example, a wireless router. The plurality of terminals 20 and the router 21 form a local network. If an evacuee 6 who arrives at the evacuation inspection site 2 has a mobile terminal 60, the mobile terminal 60 can be connected to a local network by setting it up. In addition, the multiple terminals 20 are connected to a wide area network such as the Internet, a carrier network, or a cellular network, and can communicate with the server 50 of the disaster response headquarters 5 as long as there is no communication failure in the network.

(Functions and configuration of terminal 20)
The functions and configuration of the terminal 20 will be described with reference to Figure 3. As will be described next with reference to Figure 2, the evacuation inspection site 2 is provided with multiple areas for different purposes, and a terminal 20 is provided in each area for inputting necessary information, etc. The functions required for each area differ, and not all of the functions described below are necessarily required for each area. Here, the functions and configuration when the terminal 20 has all the functions will be described. The terminal 20 includes an input receiving unit 201, a code information management unit 202, a DB management unit 203, a DB synchronization unit 204, an output unit 205, a memory unit 206, a communication unit 207, and an inspection certificate issuance unit 208.
The input receiving unit 201 receives input of settings and instruction operations from staff in each area.
The code information management unit 202 issues resident IDs, generates resident code information, and extracts the resident ID and history of evacuation facilities, etc. from the resident code information read by the reading device 22. A resident ID is issued to an evacuee 6 who arrives directly at the evacuation/exit inspection site 2 without passing through the indoor evacuation site 1. The resident ID is composed of the "site ID of the evacuation/exit inspection site 2" plus a "serial number." For an evacuee 6 who has already been assigned a resident ID at the indoor evacuation site 1, new resident code information is generated to which the "site ID of the evacuation/exit inspection site 2" is added as a history of evacuation facilities, etc. In addition, the code information management unit 202 issues vehicle IDs, issues occupant IDs, associates occupant IDs with resident IDs, acquires vehicle code information including the vehicle ID read by the reading device 12, and generates vehicle code information. A vehicle ID is issued for each vehicle 7 and is composed of, for example, the "site ID of the evacuation/exit inspection site 2" plus a "serial number." If the venue ID is "B1" and the serial number is a four-digit number starting with 0001, then the first vehicle 7 to undergo inspection at the evacuation/exit inspection venue 2 will be issued a vehicle ID of, for example, "B10001", and the second vehicle 7 will be issued a vehicle ID of "B10002". The vehicle ID does not have to be composed of "venue ID of evacuation/exit inspection venue 2" + "serial number", as long as it contains information identifying the vehicle as the evacuation/exit inspection venue 2 and information distinguishing the vehicle 7 from other vehicles 7. An occupant ID is issued to each evacuee 6 boarding a vehicle 7, and is composed of, for example, "vehicle ID" + "serial number". For example, if the vehicle ID is "B10001" and three evacuees 6 are on board the vehicle, the first person will be issued an occupant ID "B10001-1," the second person will be issued an occupant ID "B10001-2," and the third person will be issued an occupant ID "B10001-3." The occupant ID is issued for convenience in order to smoothly carry out inspection processes, etc. at the evacuation inspection site 2, and will later be linked to the resident ID. The occupant ID does not have to be composed of "vehicle ID" + "serial number," as long as it includes, for example, information identifying which vehicle 7 it is and information distinguishing between the evacuees 6 on board the vehicle 7, and may be, for example, "vehicle ID" + A, B, C, ..., etc.

The DB management unit 203 registers the resident ID and personal information of evacuee 6, the history of evacuation facilities, the contamination status of evacuee 6, and so forth in the resident DB. The DB management unit 203 also reads information about evacuee 6 from the resident DB using the resident ID as a key. The DB management unit 203 also registers the vehicle ID, occupant ID, the contamination status of vehicle 7, and so forth in the vehicle database (hereinafter referred to as the vehicle DB). The DB management unit 103 also reads information about vehicle 7 from the vehicle DB using the vehicle ID as a key. An example of the layout of the vehicle DB is shown in Figure 5.

The DB synchronization unit 204 determines whether the wide area network NW connecting the terminal 20 and the server 50 is capable of communication, and if communication is possible, synchronizes the information registered in the resident DB and vehicle DB existing on the local network of the evacuation inspection site 2 with the information registered in the resident DB and vehicle DB stored in the server 50.
The output unit 205 displays the information registered in the resident DB and the vehicle DB on a display device, prints the resident code information on paper using the printer 23, and outputs it to the mobile terminal 60 via the communication unit 207. The output unit 205 also outputs vehicle code information, which is an encoded version of the vehicle ID, in a format that can be brought by the evacuees 6. For example, the output unit 205 prints it on paper using the printer 23, and outputs it to the mobile terminal 60 via the communication unit 207.
The memory unit 206 stores a resident database, a vehicle database, the site ID of the evacuation inspection site 2, and the like.
The communication unit 207 communicates with other devices. The communication unit 207 has a communication module for a local network established within the evacuation/exit inspection site 2 and a communication module for a wide area network NW such as the Internet.
The inspection certificate issuing unit 208 issues an inspection certificate certifying that the amount of radioactive material adhering to the vehicle 7 and the evacuees 6 aboard the vehicle 7 is within an acceptable range. For example, the inspection certificate issuing unit 208 prints an inspection certificate on paper using the printer 23, which prints the time of passage. Alternatively, the inspection certificate issuing unit 208 may output digital data of the inspection certificate to the mobile terminal 60 via the communication unit 207. Alternatively, the inspection certificate issuing unit 208 may transmit the vehicle ID and other information, such as flag information indicating that the vehicle 7 with that vehicle ID has been inspected, to the server 50 via the communication unit 207, and manage the fact that the inspection has been completed in the server 50.

Next, referring to Figure 2, the processing at the evacuation/exit inspection site 2 will be described. As shown in Figure 2, the evacuation/exit inspection site 2 includes a preparation area 2a, a pre-inspection area 2b, a gate monitor inspection area 2c, a confirmation inspection (before) area 2d, a simple decontamination area 2e, a confirmation inspection (after) area 2f, a resident inspection area 2g, a vehicle storage area 2h, and an inspection certificate issuance area 2i, with terminals 20 provided in each area. The terminals 20 in each area will be referred to as terminals 20a-20i. The functions of terminal 20a will be described as input reception unit 201a, code information management unit 202a, etc. The same applies to the other terminals 20b-20i. When it is not necessary to distinguish between terminals 20a-20i, they will be referred to as terminal 20. Terminals 20a-20i are all connected to a local network established at the evacuation/exit inspection site 2.

The following is a general description of the inspection process at the evacuation/exit inspection site 2. Vehicles 7 and evacuees 6 aboard vehicles 7 first pass through the preparation area 2a and receive vehicle code information, including a vehicle ID. Next, vehicles 7 enter the pre-inspection area 2b, where they are inspected to determine whether the vehicle's 7 wipers are contaminated. If the wipers are not contaminated, the vehicle 7 moves to the gate monitor inspection area 2c, where they are inspected to determine whether the vehicle's 7 tires are contaminated. If the tires are not contaminated, the vehicle 7 moves to the inspection certificate issuance area 2i, and the evacuees 6 receive their inspection certificates before heading to the evacuation route 3.

If the wipers or tires are contaminated, the vehicle 7 moves to the confirmation inspection (before) area 2d and undergoes a confirmation inspection to determine whether there is any contamination or to identify in detail the locations where radioactive material has adhered. If the confirmation inspection shows no contamination, the vehicle 7 moves to the inspection certificate issuance area 2i, receives an inspection certificate, and heads to the evacuation route point 3.

If the confirmation inspection in the confirmation inspection (pre-inspection) area 2d reveals contamination, the vehicle 7 moves to the simple decontamination area 2e, where it is decontaminated. Furthermore, one representative from among the evacuees 6 aboard the vehicle 7 moves to the resident inspection area 2g to be inspected for contamination. After decontamination, the vehicle 7 moves to the confirmation inspection (post-inspection) area 2f to be inspected for contamination removal. If it is confirmed that the decontaminated vehicle 7 is free of contamination, and the representative is also free of contamination, the representative boards the decontaminated vehicle 7, moves to the inspection certificate issuance area 2i, receives the inspection certificate, and heads to the evacuation route point 3. Alternatively, text data or an image of the inspection certificate may be sent to the mobile device 60 of the evacuee 6, or flag information indicating that the inspection has been completed may be sent to the server 50. At a later venue, the evacuee 6 may display an image of the inspection certificate on their mobile device 60, or may confirm by querying the server 50 from a terminal at the venue they are moving to.

If the representative is contaminated, all other passengers will be tested for contamination in the resident testing area and decontaminated as necessary. Once it is confirmed that the decontaminated vehicle 7 is free of contamination and the passenger testing and decontamination are complete, the passengers and vehicle 7 will move to the inspection certificate issuance area 2i, receive an inspection certificate, and head to evacuation station 3.

If it is confirmed in the post-contamination inspection area 2f that contamination remains in the decontaminated vehicle 7, the vehicle 7 will be moved to the vehicle storage area 2h, and the occupants will board a separately prepared vehicle with an inspection certificate issued, and depart the evacuation exit inspection site 2, heading for the evacuation stop 3.

(Processing in the preparation area)
When the vehicle 7 arrives at the evacuation inspection site 2, an attendant in the preparation area 2a inputs the vehicle 7's license plate information, the number of occupants, and other information into the terminal 20a. The evacuees 6 aboard the vehicle 7 may operate their own mobile terminals 60 to connect to the local network, input the license plate information, the number of occupants, and other information into the mobile terminals 60, and transmit the input information to the terminal 20a (as will be described later, the evacuees 6 may also input their resident IDs along with the license plate information into the mobile terminals 60 themselves). When a disaster occurs at a nuclear facility, the number of people to be evacuated can reach hundreds of thousands, resulting in a large number of evacuees 6 flocking to the inspection site. If an attendant inputs individual vehicle information, the inspection site will become congested, resulting in delays in inspection and evacuation. Having the evacuees 6 input vehicle information and other information into their own mobile terminals 60 reduces the burden on the attendant and enables efficient inspection and evacuation. The input receiving unit 201a acquires the input or transmitted information. When license plate information and the like is input or transmitted to terminal 20a, output unit 205a displays the input information on a display device. An attendant confirms the displayed information and instructs terminal 20a to register the license plate information and the like. Then, code information management unit 202a issues a vehicle ID and an occupant ID. DB management unit 203a associates the issued vehicle ID and occupant ID with the input license plate information and registers them in a vehicle DB. The vehicle DB is pre-registered in memory unit 206a or the memory unit 206 of another terminal 20 or a storage device (not shown), and is accessible from terminals 20 within the local network. For example, DB management unit 203a registers the issued vehicle ID, license plate information, number of occupants, issued occupant ID, and current time in the fields "Vehicle ID,""VehicleNumber,""Number of Occupants,""OccupantID-1" to "Occupant ID-n" (n is the number of occupants), and "Entry Time" shown in FIG. 5, respectively. In addition, the DB management unit 203a registers "ON" in the "non-sharing flag" field shown in FIG. 5. When the DB management unit 203a registers the information of the vehicle 7 to be inspected in the vehicle DB, the output unit 205a outputs the vehicle ID and the occupant ID. For example, the output unit 205a prints vehicle code information including the vehicle ID on paper using the printer 23. The paper on which the vehicle code information is printed is given to the passenger (representative). In addition, for example, the output unit 205a generates image data of the vehicle code information including the vehicle ID and transmits the image data to the mobile terminal 60 via the communication unit 207a. In addition, the output unit 205a prints occupant code information including the occupant ID on paper using the printer 13. The paper on which the occupant code information is printed is given to each passenger. The output vehicle code information and occupant code information are used when the vehicle 7 moves to each area. In addition, the DB management unit 203a registers the issued vehicle ID in the pre-inspection list. The pre-inspection list is a list of vehicle IDs of the vehicles 7 to be inspected in the pre-inspection area 2b. The pre-inspection list is registered in advance in the storage unit 206 in which the vehicle DB is registered, for example.

(Processing in the pre-inspection area)
At the pre-inspection area 2b to which the evacuee 6 is to be transferred, the evacuee 6 presents a piece of paper on which the vehicle code information is printed or a mobile terminal 60 displaying the vehicle code information. An attendant at the pre-inspection area 2b reads the vehicle code information using a reader 22b. The code information management unit 202b acquires the vehicle code information, extracts a vehicle ID from the vehicle code information, and outputs the information to the DB management unit 203b. The DB management unit 203b references the vehicle DB using the vehicle ID as a key, reads information about the vehicle 7, and outputs the information to the output unit 205b. The DB management unit 203b also checks whether the vehicle ID is registered in the pre-inspection list and outputs the check result to the output unit 205b. The output unit 205b displays the license plate information, number of occupants, whether the vehicle is registered in the pre-inspection list, and other information read from the vehicle DB on the display device of the terminal 20b. Alternatively, even if the evacuee 6 does not provide the vehicle code information, the output unit 205b reads the vehicle ID registered in the pre-inspection list and the license plate information associated therewith from the vehicle DB and displays them on the display device of the terminal 20b. After the staff member confirms that the displayed information is correct, he or she inputs the results of the pre-inspection (whether the wipers are contaminated or not) into the terminal 20b. The input receiving unit 201b acquires the results of the pre-inspection and outputs the acquired inspection results to the DB management unit 203b. If the inspection result shows contamination, the DB management unit 203b registers the vehicle ID in the confirmation inspection (pre) list. If the inspection result shows no contamination, the DB management unit 203b registers the vehicle ID in the gate monitor inspection list. These inspection lists are pre-registered, for example, in the storage unit 206 in which the vehicle DB is registered.

(Processing in the gate monitor inspection area)
At the gate monitor inspection area 2c to which the evacuee 6 is to be transferred, the evacuee 6 presents a piece of paper on which the vehicle code information is printed or a mobile terminal 60 displaying the vehicle code information. An attendant at the gate monitor inspection area 2c reads the vehicle code information using a reader 22c. The code information management unit 202c acquires the vehicle code information, extracts a vehicle ID from the vehicle code information, and outputs the information to the DB management unit 203c. The DB management unit 203c references the vehicle DB using the vehicle ID as a key, reads information about the vehicle 7, and outputs the information to the output unit 205c. The DB management unit 203c also checks whether the vehicle ID is registered in the gate monitor inspection list and outputs the check result to the output unit 205c. The output unit 205c displays the license plate information, number of occupants, whether the vehicle is registered in the gate monitor inspection list, and other information read from the vehicle DB on the display device of the terminal 20c. Alternatively, even if the evacuee 6 does not provide the vehicle code information, the output unit 205c may read the vehicle ID registered in the gate monitor inspection list and the license plate information associated therewith from the vehicle DB and display them on the display device of the terminal 20c. After the staff member confirms that the displayed information is correct, they input the inspection results (whether the tires are contaminated or not) into the terminal 20c. The input receiving unit 201c acquires the results of the pre-inspection and outputs the acquired inspection results to the DB management unit 203c. If the inspection results show contamination, the DB management unit 203c registers the vehicle ID in the confirmation inspection (pre) list. If the inspection results show no contamination, the DB management unit 203c registers the vehicle ID in the inspection certificate issuance list. These inspection lists are pre-registered, for example, in the storage unit 206 in which the vehicle DB is registered. Furthermore, if the inspection result shows no contamination, the DB management unit 203c registers "0" (not subject to inspection) in "Occupant Inspection FLG-1" to "Occupant Inspection FLG-n" (n is the number of passengers) in the vehicle DB.

(Processing in the pre-inspection area)
The evacuee 6 presents a piece of paper on which the vehicle code information is printed or a mobile terminal 60 displaying the vehicle code information in the (pre-confirmation inspection) area 2d at his/her destination. An attendant in the (pre-confirmation inspection) area 2d reads the vehicle code information using a reader 22d. The code information management unit 202d acquires the vehicle code information, extracts a vehicle ID from the vehicle code information, and outputs it to the DB management unit 203d. The DB management unit 203d references the vehicle DB using the vehicle ID as a key, reads information about the vehicle 7, and outputs it to the output unit 205d. The DB management unit 203d also checks whether the vehicle ID is registered in the (pre-confirmation inspection) list and outputs the check result to the output unit 205d. The output unit 205d displays the license plate information, number of occupants, whether the vehicle is registered in the (pre-confirmation inspection) list, and other information read from the vehicle DB on the display device of the terminal 20d.
Alternatively, even if the evacuee 6 does not provide vehicle code information, the output unit 205d may read the vehicle ID and associated license plate information registered in the (pre-confirmation inspection) list from the vehicle DB and display them on the display device of the terminal 20d. After confirming that the displayed information is correct, the staff member inputs the inspection results (contamination detection locations and dose rate) into the terminal 20d. The input receiving unit 201d acquires the results of the (pre-confirmation inspection) and outputs the acquired confirmation inspection results to the DB management unit 203d. If the confirmation inspection results in contamination, the DB management unit 203d registers the corresponding input information in the vehicle DB fields shown in FIG. 5, such as "Number of Contamination Detection Locations,""Detection Location -1" to "Detection Location -m," and "Contamination Level -1" to "Contamination Level -m" (where m is the number of contamination detection locations). Furthermore, if the confirmation inspection results in contamination, the DB management unit 203d registers the vehicle ID in the simplified decontamination list. If the result of the confirmation inspection is that there is no contamination, the DB management unit 203d registers the vehicle ID in the inspection certificate issuance list. These inspection lists are, for example, pre-registered in the storage unit 206 in which the vehicle DB is registered. Furthermore, if the result of the confirmation inspection is that there is contamination, the staff member uses the reading device 22d to read a paper on which is printed the occupant code information of one representative occupant among the occupants of the vehicle 7. Alternatively, if a resident ID is registered in association with the vehicle information when the vehicle information of the vehicle 7 is registered, the representative may present the resident code information (resident code information displayed on paper or on the mobile terminal 60). The DB management unit 203d registers "1" (under inspection) in the "occupant inspection FLG-N" (N is the occupant ID extracted from the occupant code information) in the vehicle DB. Furthermore, if the result of the confirmation inspection is that there is no contamination, the DB management unit 203d registers "0" (not subject to inspection) in "Occupant Inspection FLG-1" to "Occupant Inspection FLG-n" (n is the number of passengers) in the vehicle DB.

(Processing in simple decontamination area)
At the simplified decontamination area 2e to which the evacuee 6 is to be transferred, the evacuee 6 presents a piece of paper on which the vehicle code information is printed or a mobile terminal 60 displaying the vehicle code information. An attendant at the simplified decontamination area 2e reads the vehicle code information using a reader 22e. The code information management unit 202e acquires the vehicle code information, extracts a vehicle ID from the vehicle code information, and outputs the information to the DB management unit 203e. The DB management unit 203e references the vehicle DB using the vehicle ID as a key, reads out information about the vehicle 7, and outputs the information to the output unit 205e. The DB management unit 203e also checks whether the vehicle ID is registered in the simplified decontamination list and outputs the check result to the output unit 205e. The output unit 205e displays the license plate information, number of occupants, whether the vehicle is registered in the simplified decontamination list, and other information read from the vehicle DB on the display device of the terminal 20e. Alternatively, even if the evacuee 6 does not provide the vehicle code information, the output unit 205e may read the vehicle ID registered in the simplified decontamination list and the license plate information associated therewith from the vehicle DB and display them on the display device of the terminal 20e. After confirming that the displayed information is correct, the staff member performs decontamination by referring to the displayed content ("Detection Location -1" to "Detection Location -m" and "Contamination Level -1" to "Contamination Level -m" read from the vehicle DB). When decontamination is complete, the staff member inputs this information into the terminal 20e. The input receiving unit 201e acquires the input indicating the completion of decontamination and outputs it to the DB management unit 203e. The DB management unit 203e registers the vehicle ID in the confirmation inspection (post) list. The confirmation inspection (post) list is, for example, pre-registered in the storage unit 206 in which the vehicle DB is registered.

(Processing in the post-inspection area)
The evacuee 6 presents the destination confirmation inspection (post) area 2f, a piece of paper on which the vehicle code information is printed, or a mobile terminal 60 displaying the vehicle code information. An attendant in the confirmation inspection (post) area 2f reads the vehicle code information using a reader 22f. The code information management unit 202f acquires the vehicle code information, extracts the vehicle ID from the vehicle code information, and outputs it to the DB management unit 203f. The DB management unit 203f references the vehicle DB using the vehicle ID as a key, reads information about the vehicle 7, and outputs it to the output unit 205f. The DB management unit 203f also checks whether the vehicle ID is registered in the confirmation inspection (post) list and outputs the check result to the output unit 205f. The output unit 205f displays the license plate information, number of occupants, whether the vehicle is registered in the confirmation inspection (post) list, and other information read from the vehicle DB on the display device of the terminal 20f. Alternatively, even if the evacuee 6 does not provide the vehicle code information, the output unit 205f may read the vehicle ID and associated license plate information registered in the (post) confirmation inspection list from the vehicle DB and display them on the display device of the terminal 20f. After confirming that the displayed information is correct, the staff member conducts a confirmation inspection and inputs the inspection results (decontaminated areas and post-decontamination dose rates) into the terminal 20f. The input receiving unit 201f acquires the results of the (post) confirmation inspection and outputs them to the DB management unit 203f. For example, the DB management unit 203f registers the corresponding input information in the fields shown in FIG. 5, such as "Number of Contamination Detected Locations,""Detection Locations -1" to "Detection Locations -m," and "Contamination Levels -1" to "Contamination Levels -m" (where m is the number of contamination detected locations). Furthermore, if the results of the (post) confirmation inspection indicate contamination, the DB management unit 203f registers the vehicle ID in the vehicle storage list. If the decontamination results in no contamination, the DB management unit 203f registers the vehicle ID in an inspection certificate issuance list. These inspection lists are registered in advance in the storage unit 206 in which the vehicle DB is registered, for example.

(Processing in the vehicle storage area)
In the vehicle storage area 2h, an attendant operates the terminal 20h to display the vehicle storage list and vehicle information (license plate information) of the vehicle whose vehicle ID is registered in the vehicle storage list. These processes are executed by the DB management unit 203h and the output unit 205h. The attendant checks the license plate of the vehicle 7 transported to the vehicle storage area 2h to ensure there are no errors. The attendant operates the terminal 20h to register the evacuee 6 in the bus evacuee list. The input reception unit 201h accepts this operation. The DB management unit 203h then registers the occupant ID associated with the vehicle ID of the transported vehicle 7 in the bus evacuee list. The bus evacuee list is registered in advance, for example, in the storage unit 206 in which the vehicle DB is registered.

(Processing in resident testing area)
In the resident inspection area 2g, the evacuee 6 (representative) presents a paper on which resident code information is printed or a mobile terminal 60 displaying the resident code information. An attendant in the resident inspection area 2g reads the resident code information using a reading device 22g. The code information management unit 202g acquires the resident code information, extracts a resident ID from the resident code information, and outputs it to the DB management unit 203g. If the evacuee 6 arrives directly at the evacuation inspection site 2 without passing through the indoor evacuation site 1, the evacuee 6 may not have a paper on which the resident code information is printed. In this case, the code information management unit 202g issues a resident ID and outputs the resident code information using a process similar to that described in "Processing when arriving at the first indoor evacuation site 1." In addition, the evacuee 6 (representative) presents a paper on which vehicle code information is printed or a mobile terminal 60 displaying the vehicle code information in the resident inspection area 2g. An attendant reads the vehicle code information using a reading device 22g. The code information management unit 202g acquires the vehicle code information, extracts the vehicle ID from the vehicle code information, and outputs it to the DB management unit 203g. Furthermore, the evacuee 6 (representative) presents a piece of paper on which the occupant code information is printed in the resident inspection area 2g. The attendant reads the occupant code information using the reading device 22g. The code information management unit 202g acquires the occupant code information, extracts the occupant ID from the occupant code information, and outputs it to the DB management unit 203g. The DB management unit 203g reads the vehicle DB using the vehicle ID as a key, and overwrites the value of the field in which the occupant ID read using the reading device 22g is stored, among the "occupant ID-1" to "occupant ID-n" fields of the record corresponding to the vehicle ID, with the resident ID read using the reading device 22g. This associates the vehicle ID and resident ID for the representative. Furthermore, the attendant inspects the representative's contamination status. The staff member inputs the inspection results (contaminated location and dose rate) into terminal 20g. Input reception unit 201g acquires the inspection results and outputs them to DB management unit 203g. If the inspection results indicate contamination, DB management unit 203g registers the corresponding input information in the "Number of Contaminated Locations,""ContaminatedLocation-1" to "Contaminated Location-j," and "Contamination Level-1" to "Contamination Level-j" (where j is the number of contaminated locations) in the resident DB shown in FIG. 4.

If a communication failure prevents synchronization with server 50 and the representative's resident ID is not registered in the resident DB, DB management unit 203g registers new data in the resident DB using the representative's resident ID as a key, and registers the inspection results in the "Number of Contaminated Locations," "Contaminated Locations -1" to "Contaminated Locations -j," and "Contamination Level -1" to "Contamination Level -j" fields of the newly registered data. Furthermore, if the resident code information includes not only the resident ID but also a history of evacuation facilities, etc., DB management unit 203g registers the IDs of venues visited in the "Venue Number" of the newly added data to the resident DB, and registers the ID of evacuation/exit inspection venue 2 in the "K"th (K is the smallest unregistered number between 1 and L) "Venue Number" in the resident DB, and the current time, etc., in the "Arrival Time" (the addition of the ID of evacuation/exit inspection venue 2, etc., as a history of evacuation facilities, etc., is performed even if the resident ID is registered in the resident DB). In addition, appropriate information is also registered in the "Safe Iodine Aversion," "Safe Iodine Possession," and "Time of Taking Safe Iodine" fields of the resident DB. If the test results in contamination, the DB management unit 203g registers the resident ID in the confirmation test simplified decontamination list. If the test results in no contamination, the DB management unit 203g registers the resident ID in the inspection record issuance list. These inspection lists are pre-registered, for example, in the storage unit 206 where the vehicle DB is registered. Furthermore, if the test results in no contamination, the DB management unit 203g registers "2" (inspection completed (no contamination)) in the "Occupant Inspection FLG-N" (N is the occupant ID number) of the vehicle DB.

If contamination is found, the representative undergoes decontamination and a post-decontamination confirmation inspection, and a "Post-decontamination contamination level -1" to "Post-decontamination contamination level -j" is registered in the representative's data in the resident database. Furthermore, if the contamination is removed by decontamination, "3" (inspection completed (decontamination completed)) is registered in the "occupant inspection FLG-N" in the vehicle database. If the contamination is not removed by decontamination, "4" (inspection completed (proceed to treatment)) is registered in the "occupant inspection FLG-N" in the vehicle database. Furthermore, if the contamination is removed by decontamination, the representative's resident ID is registered in the inspection record issuance list. If the contamination is not removed, the representative's resident ID is registered in the treatment processing list. The treatment processing list is pre-registered, for example, in the storage unit 206 where the vehicle database is registered.

If the representative is determined to be contaminated, the other passengers are also tested for contamination, and if they are, decontamination and confirmation testing are performed. For example, when an attendant enters the passenger ID or resident ID of the representative determined to be contaminated into terminal 30g, input reception unit 301g acquires this information and searches the vehicle DB to identify the vehicle ID of the vehicle in which the representative is riding and the resident IDs of the other passengers. Output unit 305g outputs the identified vehicle's vehicle ID, vehicle information, and the resident IDs of the other passengers to the display device. The attendant identifies the vehicle in which the other passengers are riding and guides them from the vehicle to the testing site for testing. In this case, the same processing is performed on the other passengers as on the representative. As a result, the resident IDs are registered in the "Occupant ID-1" to "Occupant ID-n" fields in the vehicle DB, and the vehicle ID and resident ID are associated for all evacuees 6 aboard vehicle 7. The "Occupant Inspection FLG-1" to "Occupant Inspection FLG-n" fields in the vehicle DB are registered with values 0 through 4, and the "All Occupant Inspection FLG" is registered with values 0 (no decontamination), 1 (representative decontamination), or 2 (decontamination completed). For each evacuee, the "Number of Contaminated Locations," "Contaminated Location -1" to "Contaminated Location -j," "Contamination Level -1" to "Contamination Level -j," and "Post-Decontamination Contamination Level -1" to "Post-Decontamination Contamination Level -j" are registered as necessary in the resident DB. Depending on the contamination and decontamination status, the resident ID of each evacuee 6 is registered in the inspection record issuance list or the treatment processing list. If the occupant ID is registered in the bus evacuee list, the DB management unit 203g may rewrite the occupant ID registered in the bus evacuee list with the corresponding resident ID. Evacuees 6 registered in the treatment processing list are transported to a medical institution or other facility for treatment. Evacuees 6 registered on the inspection record issuance list will move to the inspection certificate issuance area 2i along with the decontaminated vehicle 7. When the vehicle 7 is transported to the vehicle storage area 2h, evacuees 6 registered on the inspection record issuance list will move to the inspection certificate issuance area 2i.

(Processing in the inspection certificate issuing area)
The evacuee 6 presents a paper on which the vehicle code information is printed or a mobile terminal 60 displaying the vehicle code information at the inspection certificate issuance area 2i to which he or she is to be moved. An attendant at the inspection certificate issuance area 2i reads the vehicle code information using a reader 22i. The code information management unit 202i acquires the vehicle code information, extracts a vehicle ID from the vehicle code information, and outputs it to the DB management unit 203i. The DB management unit 203i references the vehicle DB using the vehicle ID as a key, reads out information about the vehicle 7, and outputs it to the output unit 205f. The DB management unit 203i also checks whether the vehicle ID is registered in the inspection certificate issuance list and outputs the confirmation result to the output unit 205i. The DB management unit 203i also checks whether the occupant ID (resident ID) is registered in the inspection record issuance list and outputs the confirmation result to the output unit 205i. The output unit 205i displays on the display device of the terminal 20i, information such as license plate information, the number of passengers, and whether or not the vehicle 7 is registered in the inspection certificate issuance list and the inspection record issuance list, which are read from the vehicle DB. When the staff member confirms from the displayed information that the radioactive materials adhering to the vehicle 7 and its passengers are within the allowable range, the staff member operates the terminal 20i to permit passage. For example, if the vehicle 7 is determined to be uncontaminated in the pre-confirmation inspection area, or if the vehicle 7 is determined to be contaminated but the absence of contamination is confirmed after decontamination of the vehicle 7, and the inspection of the passengers is completed and the absence of contamination is confirmed or medical treatment has been decided (decontamination has not sufficiently reduced the contamination), the staff member operates the terminal 20i to permit passage. The input receiving unit 201f receives this operation and instructs the inspection certificate issuing unit 208i to issue an inspection certificate or send inspection completion flag information to the server 50. The inspection certificate issuing unit 208i issues an inspection certificate (paper or image) or sends inspection completion flag information, etc. The output unit 305i also issues resident code information to each passenger (evacuee 6). The resident code information includes the site ID of the evacuation exit inspection site 2, which indicates that the evacuee 6 has passed through the evacuation exit inspection site 2. The evacuee 6 receives the inspection certificate and resident code information, boards the vehicle 7 or a bus arranged by the local government or other organization, and heads to the evacuation stop 3. When an attendant permits passage, the DB management unit 203i registers the current time in the "exit time" field of the vehicle DB. In addition, appropriate information is also registered in the "boarding point,""name of person in charge," and "contact information" fields of the vehicle DB. In addition, the DB management unit 203i registers the time of departure of the evacuee 6 in the "K"th "departure time" field of the resident DB.

At the evacuation inspection site 2, a process is performed in one of the areas to associate vehicle IDs with resident IDs. In other words, the occupant IDs recorded in the vehicle database are rewritten to resident IDs. As explained above, if contamination is detected in vehicle 7, there is an opportunity to check resident code information during the process of inspecting the occupants for contamination. Therefore, for at least the representative, the representative's resident ID is associated with the vehicle ID in which the representative is riding. Furthermore, if contamination is detected in the representative, the resident IDs and vehicle IDs of the remaining occupants are also associated. However, if no contamination is detected in vehicle 7, the vehicle moves to the inspection certificate issuance area 2i without an opportunity to check the occupants' resident code information, and therefore the vehicle ID and occupant's resident ID are not associated. This makes it impossible to determine which evacuees 6 are riding in which vehicles 7. Therefore, for example, a staff member at the inspection certificate issuance area 2i can determine whether vehicle IDs and resident IDs are associated by checking the information registered in the vehicle database under "passenger ID-1" through "passenger ID-n." For example, if serial numbers are registered for "passenger ID-1" through "passenger ID-n," the system determines that the vehicle ID and the resident ID of the passenger are not associated, and requests each passenger of vehicle 7 to submit their resident code information and passenger code information, and further requests the vehicle code information of vehicle 7. The staff member uses the reading device 23i to read the resident code information and passenger code information of each passenger, as well as the vehicle code information. Using the read information, the DB management unit 203i rewrites the passenger IDs of "passenger ID-1" through "passenger ID-n" in the vehicle DB with the corresponding resident ID. This associates the vehicle ID with the resident ID. Furthermore, when the resident DB is accessed, the ID of the evacuation inspection venue 2 is also added as a history of evacuation facilities, etc. This allows the resident DB to register the fact that the evacuee 6 stopped at the evacuation inspection venue 2 and the time of this visit. Note that the association of vehicle IDs with resident IDs may be performed appropriately in any area other than the inspection certificate issuing area 2i. Testing sites are often crowded, and staff are often too busy to perform complicated tasks. By finding spare time to link vehicle IDs with resident IDs, it is possible to reduce the effort required to link vehicle information with occupant information without interfering with the testing or causing staff any trouble.

The vehicle ID and resident ID may also be associated by registering the resident ID at the same time as registering vehicle information such as license plate information and the number of passengers. For example, when vehicle 7 arrives at evacuation/exit inspection site 2, evacuee 6 inputs the resident IDs of all passengers into mobile terminal 60 along with information such as the vehicle's license plate. Mobile terminal 60 transmits the input information to terminal 20a. The input reception unit 201a acquires the transmitted information, and output unit 205a displays the input information on the display device. The staff member checks the displayed information and instructs terminal 20a to register the license plate information, etc. The code information management unit 202a then issues a vehicle ID. The DB management unit 203a associates the issued vehicle ID with the resident ID entered into mobile terminal 60 and the license plate information, etc., and registers them in the vehicle DB. The resident IDs of the evacuees 6 aboard the vehicle 7 are registered in the fields "Occupant ID-1" to "Occupant ID-n" shown in Figure 5, instead of the occupant IDs.

Furthermore, if the occupants of vehicle 7 arrive directly at evacuation inspection site 2 without passing through indoor evacuation site 1, they will not have been assigned a resident ID. In this case, for example, the resident ID may be issued and personal information may be registered in inspection certificate issuing area 2i, and the vehicle ID and resident ID may be associated, or the resident ID may be issued and personal information may be registered during an inspection in another area. The resident ID issuance process is the same as the process described in "Processing when arriving at the first indoor evacuation site 1."

<System configuration of Evacuation Station 3>
After receiving an inspection certificate at the evacuation inspection site 2, an evacuee 6 moves to a shelter 4 via an evacuation route 3. As shown in FIG. 1 , the evacuation route 3 is provided with one or more terminals 30 and one or more routers 31. A barcode reader 32 for reading QR codes (registered trademark) and a printer 33 are connected to the terminal 30. The router 31 is, for example, a wireless router, and the terminal 30 and the router 31 form a local network. If an evacuee 6 who has evacuated to the evacuation route 3 has a mobile terminal 60, the mobile terminal 60 can be connected to the local network. Furthermore, as shown in FIG. 3 , the terminal 30 is connected to a wide area network NW, and can communicate with a server 50 of a disaster response headquarters 5 unless a communication failure occurs.

(Functions and configuration of terminal 30)
The functions and configuration of the terminal 30 will be described with reference to FIG. 3 . The terminal 30 includes an input reception unit 301, a code information management unit 302, a DB management unit 303, a DB synchronization unit 304, an output unit 305, a memory unit 306, and a communication unit 307. The input reception unit 301 receives setting inputs and instruction operation inputs from staff at the evacuation center 3. The code information management unit 302 generates resident code information and extracts a resident ID, evacuation facility history, etc. from the resident code information read by the reading device 32. The DB management unit 303 registers the body temperature, evacuation facility history, etc. of the evacuees 6 in the resident DB. The DB management unit 303 also reads information about the evacuees 6 from the resident DB. The DB synchronization unit 304 determines whether the wide area network NW connecting the terminal 30 and the server 50 is capable of communication, and if communication is possible, synchronizes the information registered in the resident DB present on the local network of the evacuation site 3 with the information registered in the resident DB stored in the server 50 of the disaster response headquarters 5. The output unit 305 displays the information registered in the resident DB on a display device, prints image data including resident code information on paper using the printer 33, or outputs it to the mobile terminal 60 via the communication unit 307. The memory unit 306 stores the resident DB, the venue ID of the evacuation site 3, etc. The communication unit 307 communicates with other devices. The communication unit 307 has a communication module for a local network established within the indoor evacuation site 1 and a communication module for a wide area network NW such as the Internet.

(Processing at Evacuation Station 3)
When evacuee 6 arrives at evacuation route 3, a staff member uses reader 32 to read the resident code information. Using the same process as above, DB management unit 303 registers the venue ID of evacuation route 3, the current time, and the temperature of evacuee 6 in the "K"th (K is the smallest unregistered number among 1 to L) "venue number,""arrivaltime," and "body temperature - 1" fields of the resident DB on the local network. When evacuee 6 departs evacuation route 3, output unit 305 outputs the resident code information, which includes the resident ID and a history of evacuation facilities, etc., and evacuee 6 receives the resident code information and moves to evacuation shelter 4. For example, if the resident ID assigned to evacuee 6 at indoor evacuation venue 1 where he or she first evacuated is "A10001," and the evacuee moves from there to indoor evacuation venue 1 with venue ID = A2, then to evacuation exit inspection venue 2 with venue ID = B1, and then to evacuation waypoint 3 with venue ID = C1, resident code information including "A10001-A2-B1-C1" will be output. The time that evacuee 6 departs will be registered as the "Kth""departuretime" in the resident DB on the local network.

<System configuration of shelter 4>
Evacuees 6 who depart from evacuation route 3 move to evacuation shelter 4. As shown in FIG. 1 , evacuation shelter 4 is provided with one or more terminals 40 and one or more routers 41. Terminal 40 is connected to a reader 42 for reading barcodes and QR codes (registered trademark), and a printer 43. Router 41 is, for example, a wireless router, and terminal 40 and router 41 form a local network. If evacuees 6 who move to evacuation shelter 4 have mobile terminals 60, they can connect the mobile terminals 60 to the local network. Furthermore, as shown in FIG. 3 , terminal 40 is connected to wide area network NW, and can communicate with server 50 of disaster response headquarters 5 unless a communication failure occurs.

(Functions and configuration of terminal 40)
The functions and configuration of the terminal 40 will be described with reference to FIG. 3 . The terminal 40 includes an input reception unit 401, a code information management unit 402, a DB management unit 403, a DB synchronization unit 404, an output unit 405, a memory unit 406, and a communication unit 407. The input reception unit 401 receives setting inputs and instruction operation inputs from staff at the evacuation shelter 4. The code information management unit 402 generates resident code information and extracts a resident ID, evacuation facility history, etc. from the resident code information read by the reading device 42. The DB management unit 403 registers the body temperature, evacuation facility history, etc. of the evacuee 6 in the resident DB. The DB management unit 403 also reads information about the evacuee 6 from the resident DB. The DB synchronization unit 404 determines whether the wide area network NW connecting the terminal 40 and the server 50 is capable of communication, and if communication is possible, synchronizes the information registered in the resident DB present on the local network of the evacuation shelter 4 with the information registered in the resident DB stored in the server 50 of the disaster response headquarters 5. The output unit 405 displays the information registered in the resident DB on a display device, prints image data including resident code information on paper using the printer 33, or outputs it to the mobile terminal 60 via the communication unit 407. The memory unit 406 stores the resident DB, the venue ID of the evacuation stop 3, etc. The communication unit 407 communicates with other devices. The communication unit 407 has a communication module for a local network established in the evacuation shelter 4 and a communication module for a wide area network NW such as the Internet.

(Processing at Shelter 4)
When the evacuee 6 arrives at the evacuation shelter 4, a staff member reads the resident code information using the reader 42. By the same process as above, the DB management unit 403 adds information such as "venue number,""arrivaltime," and "body temperature - 1" to the "K"th entry (K is the smallest unregistered number among 1 to L) in the resident DB on the local network. For example, if evacuee 6 is assigned a resident ID of "A10001" at indoor evacuation venue 1 where he or she first evacuates, and then moves from there to indoor evacuation venue 1 with venue ID = A2, then to evacuation exit inspection venue 2 with venue ID = B1, then to evacuation route point 3 with venue ID = C1, and then to evacuation shelter 4 with venue ID = D1, then "A10001" will be registered as the "resident ID" in the resident DB for evacuation shelter 4, "A2" will be registered as the "first""venuenumber,""B1" will be registered as the "second""venuenumber,""C1" will be registered as the "third""venuenumber," and "D1" will be registered as the "fourth""venuenumber."

<System configuration of Disaster Countermeasures Headquarters 5>
The disaster response headquarters 5 is provided with a server 50. The server 50 is connected to the wide area network NW, and can send and receive data to and from the terminals 10 to 40 at each venue unless a communication failure occurs.

(Functions and configuration of server 50)
The functions and configuration of the terminal 40 will be described with reference to FIG. 3 . The server 50 includes an input receiving unit 501, a DB management unit 502, a DB synchronization unit 503, an output unit 504, a memory unit 505, and a communication unit 506. The input receiving unit 501 receives setting inputs and instruction operation inputs from staff at the disaster response headquarters 5. The DB management unit 502 reads various information from the resident DB and the vehicle DB. The DB synchronization unit 503 synchronizes information registered in the resident DB and the vehicle DB provided at the disaster response headquarters 5 with information registered in the resident DB provided at the indoor evacuation venue 1, the resident DB and the vehicle DB provided at the evacuation exit inspection venue 2, the resident DB provided at the evacuation route 3, and the resident DB provided at the evacuation shelter 4. The output unit 504 displays the information registered in the resident DB and the vehicle DB on a display device. The memory unit 505 stores the resident DB, the vehicle DB, etc. The communication unit 506 communicates with other devices. The resident DB and vehicle DB may be stored in a storage device provided in the disaster response headquarters 5 or in a server or storage device on a so-called cloud, instead of in the server 50.

(Synchronization processing)
Next, the synchronization process will be described with reference to Fig. 6. Fig. 6 is a flowchart showing an example of the synchronization process according to the embodiment.
Each of the terminals 10 to 40 executes the following process. Here, the terminal 20 will be used as an example for explanation.
The DB synchronization unit 204 of the terminal 20 determines whether a predetermined confirmation timing has arrived (step S1). If it is not the confirmation timing (step S1; No), the terminal 20 waits until the confirmation timing arrives. If the confirmation timing arrives (step S1; Yes), the DB synchronization unit 204 checks the communication status with the server 50 (whether communication is possible over the wide area network NW) (step S2). If it is determined that communication is not possible (step S3; No), the processing from step S1 is repeated.

If communication is determined to be possible (Step S3; Yes), the DB synchronization unit 204 extracts data with the non-shared flag set to "ON" from the data registered in the resident database on the local network of the evacuation/exit inspection site 2 and transmits the extracted data to the server 50 via the communication unit 207 (Step S4). In the server 50, the DB synchronization unit 503 acquires the transmitted data via the communication unit 506 and registers the transmitted data in the resident database of the disaster response headquarters 5 (Step S5). If an evacuee 6 with a certain resident ID travels through multiple sites, the resident ID of the transmitted data may already be registered in the resident database of the disaster response headquarters 5. In such a case, the DB synchronization unit 503 may register the transmitted data only in unregistered fields in the resident database of the disaster response headquarters 5. For example, if an evacuee 6 travels through indoor evacuation site 1 and evacuation/exit inspection site 2, the data registered in the resident database at indoor evacuation site 1 may already be registered in the server 50 through synchronization processing. In such a case, the DB synchronization unit 503 registers only the information newly added to the resident DB at the evacuation/exit inspection venue 2 (for example, the "venue number," "arrival time," "departure time," and "body temperature -1" in the resident DB data for the evacuee 6) in the resident DB of the disaster response headquarters 5. When the data registration is complete, the server 50 sends a completion notification to the terminal 20. In the terminal 20 that received the completion notification, the DB synchronization unit 204 accesses the resident DB and updates the non-sharing flag for the sent data to "OFF" (step S6).

Similarly, the DB synchronization unit 204 extracts data with the non-sharing flag set to "ON" from the data registered in the vehicle DB on the local network of the evacuation exit inspection site 2, and transmits this data to the server 50 via the communication unit 207 (step S4). In the server 50, the DB synchronization unit 503 acquires the data transmitted via the communication unit 506 and registers the transmitted data in the vehicle DB of the disaster response headquarters 5 (step S5). In the terminal 20, the DB synchronization unit 204 accesses the vehicle DB and updates the non-sharing flag of the transmitted data to "OFF" (step S6).

The DB synchronization unit 204 also queries the data of evacuees 6 who are registered in the resident DB on the server 50 side but not in the local resident DB, for example by transmitting the resident ID registered in the resident DB on the local network of the evacuation exit inspection site 2 to the server 50 via the communication unit 207 (step S7). The DB synchronization unit 503 of the server 50 reads the unregistered data from the resident DB on the server 50 side and transmits it to the terminal 20 via the communication unit 506. In the terminal 20, the DB synchronization unit 204 acquires the data transmitted via the communication unit 207 and registers the unregistered data in the resident DB on the local network (step S8).

Similarly, the DB synchronization unit 204 queries the data of vehicle 7 that is registered in the vehicle DB on the server 50 side but not in the local vehicle DB, for example by transmitting the vehicle ID registered in the vehicle DB on the local network of the evacuation exit inspection site 2 to the server 50 via the communication unit 207 (step S7). The DB synchronization unit 503 of the server 50 reads the unregistered data from the vehicle DB on the server 50 side and transmits it to the terminal 20 via the communication unit 506. In the terminal 20, the DB synchronization unit 204 acquires the data transmitted via the communication unit 207 and registers the unregistered data in the vehicle DB on the local network (step S8).

In addition, in preparation for cases such as when a failure occurs in server 50 or when wide area network NW does not fully recover, each of terminals 10-40 may be configured to have the same functions as server 50, and each of terminals 10-40 may be configured to function as both terminal and server 50 as appropriate. For example, terminal 20 may function as both terminal 20 and server 50, and the above-mentioned synchronization process may be performed between terminal 20 and terminals 10, 30, and 40 to share information.

(effect)
As described above, according to this embodiment, when an evacuee 6 traveling through multiple venues (indoor evacuation venue 1, evacuation/exit inspection venue 2, evacuation route 3, and evacuation shelter 4) arrives at a venue, information about the evacuee 6 (e.g., address, name, temperature), including the IDs of the venues the evacuee 6 has passed through, is registered in a resident database provided for each venue. Then, through a synchronization process with the server 50 of the disaster response headquarters 5, the server 50 and the resident databases provided on the terminals 10-40 at each venue are synchronized. This allows the latest information about the evacuee 6 to be recorded on one of the terminals 10-40, even in the event of a communication failure. After the communication failure is restored, information about the evacuee 6's evacuation facility history, etc., can be shared. Furthermore, at the evacuation/exit inspection venue 2, a vehicle ID and an occupant ID are issued, and the vehicle 7 is inspected and decontaminated. Then, the resident ID of the occupant (evacuee 6) is associated with the occupant ID, and the vehicle ID of the vehicle 7 and the occupant's resident ID are registered in the vehicle database as appropriate. This allows the information on vehicles 7 and evacuees 6 to be linked and managed without interfering with work at the evacuation inspection site 2, which requires complex operations such as the need for inspection changing depending on the contamination status of the vehicle and the representative, and the vehicle contamination inspection being separated from the resident contamination inspection.

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

Programs for implementing all or part of the functions of terminals 10-40, server 50, and mobile terminal 60 may be recorded on a computer-readable recording medium, and the programs recorded on the recording medium may be loaded into a computer system and executed to perform processing by each functional unit. Here, "computer system" includes hardware such as the OS and peripheral devices. Furthermore, if a WWW system is used, "computer system" also includes the homepage provision environment (or display environment). Furthermore, "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 a computer system. Furthermore, if this program is distributed to computer 900 via a communication line, computer 900 that receives the program may load the program into main storage device 902 and execute the above-mentioned processing. Furthermore, the program may be designed to implement part of the above-mentioned functions, or may be capable of implementing the above-mentioned functions in combination with programs already stored in the computer system.

As described above, several embodiments of the present disclosure have been described. However, all of these embodiments are presented as examples and are not intended to limit the scope of the invention. These embodiments may be embodied in a variety of other forms, and various omissions, substitutions, and modifications may be made without departing from the spirit of the invention. These embodiments and their variations are included within the scope of the invention and its equivalents as set forth in the claims, as well as within the scope and spirit of the invention.

<Additional Notes>
The evacuation information management system described in each embodiment can be understood, for example, as follows.

(1) The evacuation information management system according to the first aspect comprises a first terminal device installed in a first venue where evacuees are staying, a second terminal device installed in a second venue where the evacuees will move from the first venue and stay next, and a server device connected to the first and second terminal devices via a network, wherein the first terminal device comprises a first memory unit that stores a resident database (resident DB), a first resident ID issuing unit that issues a resident ID including identification information for the first venue and information that distinguishes the evacuees from other evacuees, and a server device that associates the resident ID with the personal information of the evacuees. the second terminal device includes a first resident ID registration unit that associates the resident ID with the identification information of the second venue and registers it in the resident database, a first resident ID output unit that outputs the resident ID in a manner that the evacuee can carry it, a first synchronization unit that determines whether the network is capable of communication, and a first communication unit; and the second terminal device includes a second storage unit that stores the resident database, a second resident ID acquisition unit that acquires the resident ID brought by the evacuee, a second resident ID registration unit that associates the resident ID acquired by the second acquisition unit with identification information of the second venue and registers them in the resident database, and a second synchronization unit that determines whether the network is capable of communication. the server device comprises a server storage unit that stores the resident database, a server resident ID registration unit that associates the resident ID, the personal information, and identification information of the second venue and registers them in the resident database, and a server communication unit, and when the first synchronization unit determines that the network is communicable, the first communication unit transmits the resident ID and the personal information registered in the resident database stored in the first storage unit to the server device, and the server communication unit receives the transmitted resident ID and the personal information and performs the server resident ID registration. The second synchronization unit associates the resident ID with the personal information and registers it in the resident database stored in the server storage unit, and when the second synchronization unit determines that the network is capable of communication, the second communication unit transmits the resident ID and identification information of the second venue registered in the resident database stored in the second storage unit to the server device, the server communication unit receives the transmitted resident ID and identification information of the second venue, and the server resident ID registration unit associates the resident ID with the identification information of the second venue and registers them in the resident database stored in the server storage unit.

When the first terminal device cannot communicate with the server device, the first terminal device manages evacuee information; when communication becomes possible, the first terminal device sends evacuee information to the server device, and the server device stores the evacuee information. This makes it possible to share information between the first terminal device and the server device. When an evacuee stays at the first venue, a resident ID including identification information for the first venue is issued and the evacuee is asked to carry it; when the evacuee moves to the second venue, information with the second venue ID added to the resident ID is registered on the second terminal. This makes it possible to manage facilities, etc. to which evacuees move. When the second terminal device cannot communicate with the server device, the second terminal device manages evacuee information; when communication becomes possible, the second terminal device sends evacuee information to the server device, and the server device stores the evacuee information. This makes it possible to share information between the second terminal device and the server device.

The first and second venues are, for example, indoor evacuation venue 1 where the person first evacuates and indoor evacuation venue 1 where the person then stays. Alternatively, the first and second venues are, for example, indoor evacuation venue 1 where the person first evacuates and evacuation exit screening venue 2 where the person then arrives. Alternatively, the first and second venues are, for example, indoor evacuation venue 1 where the person first evacuates and evacuation stop 3 where the person then stays (if evacuation exit screening venue 2 is avoided) or evacuation shelter 4 (if evacuation exit screening venue 2 and evacuation stop 3 are avoided).

(2) The evacuation information management system according to the second aspect is the evacuation information management system of (1), wherein the first communication unit receives, from the server device, identification information of the second venue associated with the resident ID registered in the resident database stored in the server storage unit when the first synchronization unit determines that the network is capable of communication; the first resident ID registration unit registers the identification information of the second venue in the resident database stored in the first storage unit in association with the resident ID; the second communication unit receives, from the server device, the personal information associated with the resident ID registered in the resident database stored in the server storage unit when the second synchronization unit determines that the network is capable of communication; and the second resident ID registration unit registers the personal information in the resident database stored in the second storage unit in association with the resident ID.

When communication between the first terminal device and the server device becomes possible, information about the evacuees is sent from the server device to the first terminal device, and the information about the evacuees is stored in the first terminal device. When communication between the second terminal device and the server device becomes possible, information about the evacuees is sent from the server device to the second terminal device, and the information about the evacuees is stored in the second terminal device. This allows information about the evacuees to be shared between the first terminal device, the second terminal device, and the server device.

(3) The evacuation information management system according to the third aspect is the evacuation information management system of (1) to (2), further comprising a third terminal device provided in a third venue where the evacuee will stay after staying in the second venue, wherein the third terminal device has a third memory unit that stores the resident database, a third resident ID acquisition unit that acquires the resident ID brought by the evacuee and identification information of venues other than the first venue where the evacuee has stayed, and associates the resident ID acquired by the third resident ID acquisition unit with the identification information of the other venues and registers them in the resident database stored in the third memory unit. The device includes a third resident ID registration unit, a third synchronization unit that determines whether the network is capable of communication, and a third communication unit. When the third synchronization unit determines that the network is capable of communication, the third communication unit transmits the resident ID and identification information of the other venue registered in the resident database stored in the third memory unit to the server device. The server communication unit receives the transmitted resident ID and identification information of the other venue. The server resident ID registration unit associates the resident ID with the identification information of the other venue and registers them in the resident database stored in the server memory unit.

When an evacuee moves to the third venue, information that adds the ID of the second venue and the ID of the third venue to the resident ID is registered on the third terminal. This makes it possible to manage the facilities to which the evacuee moves. When communication between the third terminal device and the server device is not possible, the third terminal device manages the evacuee information, and when communication becomes possible, the third terminal device sends the evacuee information to the server device, which stores the evacuee information. This makes it possible to share information between the third terminal device and the server device.

The first, second, and third venues are, for example, indoor evacuation venue 1 where people first evacuate, indoor evacuation venue 1 where people then stay, and evacuation exit inspection venue 2. Alternatively, the first, second, and third venues are, for example, indoor evacuation venue 1 where people first evacuate, evacuation exit inspection venue 2, and evacuation stop 3 or evacuation shelter 4. Alternatively, the first, second, and third venues are, for example, indoor evacuation venue 1 where people first evacuate, evacuation stop 3 (if evacuation exit inspection venue 2 is avoided), and evacuation shelter 4 (if evacuation exit inspection venue 2 and evacuation stop 3 are avoided).

(4) The evacuation information management system according to the fourth aspect is the evacuation information management system of (1) to (2), wherein the first terminal device includes a first vehicle ID issuing unit that issues a vehicle ID including identification information for the first venue and information that distinguishes the vehicle in which the evacuee is riding from other vehicles, and an occupant ID in which information that distinguishes the evacuee from other evacuees riding in the vehicle is added to the vehicle ID, a first vehicle ID registration unit that associates the vehicle ID and the occupant ID and registers them in a vehicle database (vehicle DB) stored in the first storage unit, a first vehicle ID output unit that outputs the vehicle ID and the occupant ID in a manner that the evacuee can take with them, and a first resident ID output unit that outputs the resident ID output by the first resident ID output unit, and the vehicle ID and the occupant ID output by the first vehicle ID output unit. and a first code information acquisition unit that acquires the resident ID, the vehicle ID, and the occupant ID. When the first code information acquisition unit acquires the resident ID, the vehicle ID, and the occupant ID, the first vehicle ID registration unit rewrites the occupant ID registered in the vehicle database in association with the vehicle ID to the resident ID. When the first synchronization unit determines that the network is capable of communication, the first communication unit transmits the vehicle ID and the resident ID registered in the vehicle database stored in the first memory unit to the server device. The server communication unit receives the transmitted vehicle ID and resident ID, and the server resident ID registration unit associates the vehicle ID and the resident ID and registers them in the vehicle database stored in the server memory unit.

If the first venue is an evacuation/exit inspection venue (for example, if evacuees travel directly from their homes to the evacuation/exit inspection venue), the first terminal device can manage information about the vehicle the evacuees are riding in in a vehicle database, and associate the vehicle information with information about the evacuees riding in that vehicle, which is managed in the resident database. When communication between the first terminal device and the server device becomes possible, the first terminal device sends vehicle information to the server device, and the server device stores the vehicle information. This allows information about the vehicle the evacuees are riding in to be shared between the first terminal device and the server device.

(5) The evacuation information management system of the fifth aspect is the evacuation information management system of (1) to (2), wherein the first terminal device further includes a first vehicle ID issuing unit that issues a vehicle ID including identification information of the first venue and information that distinguishes the vehicle in which the evacuee is riding from other vehicles, a first code information acquisition unit that acquires the resident ID, and a first vehicle ID registration unit that associates the resident ID and the vehicle ID and registers them in a vehicle database stored in the first memory unit, and when the first synchronization unit determines that the network is capable of communication, the first communication unit transmits the vehicle ID and the resident ID registered in the vehicle database stored in the first memory unit to the server device, the server communication unit receives the transmitted vehicle ID and the resident ID, and the server resident ID registration unit associates the vehicle ID and the resident ID and registers them in the vehicle database stored in the server memory unit.
By registering the resident ID when issuing the vehicle ID, the vehicle ID and resident ID may be associated and registered in the vehicle DB without using the occupant ID.

(6) The evacuation information management system according to the sixth aspect is the evacuation information management system of (1) to (2), wherein the second terminal device includes: a second vehicle ID issuing unit that issues a vehicle ID including identification information for the second venue and information that distinguishes the vehicle in which the evacuee is riding from other vehicles; an occupant ID in which information that distinguishes the evacuee from other evacuees riding in the vehicle is added to the vehicle ID; a second vehicle ID registration unit that associates the vehicle ID and the occupant ID and registers them in a vehicle database stored in the second storage unit; a second vehicle ID output unit that outputs the vehicle ID and the occupant ID in a manner that the evacuee can take with them; and a second vehicle ID output unit that outputs the resident ID output by the first resident ID output unit, and the vehicle ID and the occupant ID output by the second vehicle ID output unit. The system further includes a second code information acquisition unit that acquires the resident ID, the vehicle ID, and the occupant ID. When the second code information acquisition unit acquires the resident ID, the vehicle ID, and the occupant ID, the second vehicle ID registration unit rewrites the occupant ID registered in the vehicle database in association with the vehicle ID to the resident ID. When the second synchronization unit determines that the network is capable of communication, the second communication unit transmits the vehicle ID and the resident ID registered in the vehicle database stored in the second memory unit to the server device. The server communication unit receives the transmitted vehicle ID and resident ID. The server resident ID registration unit associates the vehicle ID and the resident ID and registers them in the vehicle database stored in the server memory unit.

If the second venue is an evacuation/exit inspection venue (when evacuees move from one indoor evacuation venue to an evacuation/exit inspection venue), the second terminal device manages information about the vehicles in which evacuees are riding in a vehicle database, and the vehicle information can be associated with information about the evacuees riding in those vehicles managed in the resident database. When communication between the second terminal device and the server device becomes possible, the second terminal device sends vehicle information to the server device, which stores the vehicle information. This allows information about the vehicles in which evacuees are riding to be shared between the second terminal device and the server device.

(7) The seventh aspect of the evacuation information management system is the evacuation information management system of (1) to (2), wherein the second terminal device further includes a second vehicle ID issuing unit that issues a vehicle ID including identification information for the second venue and information that distinguishes the vehicle in which the evacuee is riding from other vehicles, a second code information acquisition unit that acquires the resident ID, and a second vehicle ID registration unit that associates the resident ID and the vehicle ID and registers them in a vehicle database stored in the second memory unit, and when the second synchronization unit determines that the network is capable of communication, the second communication unit transmits the vehicle ID and the resident ID registered in the vehicle database stored in the second memory unit to the server device, the server communication unit receives the transmitted vehicle ID and the resident ID, and the server resident ID registration unit associates the vehicle ID and the resident ID and registers them in the vehicle database stored in the server memory unit.
By registering the resident ID when issuing the vehicle ID, the vehicle ID and resident ID may be associated and registered in the vehicle DB without using the occupant ID.

(8) The evacuation information management system according to the eighth aspect is the evacuation information management system of (3), wherein the third terminal device includes: a third vehicle ID issuing unit that issues a vehicle ID including identification information for the third venue and information that distinguishes the vehicle in which the evacuee is riding from other vehicles; and an occupant ID in which information that distinguishes the evacuee from other evacuees riding in the vehicle is added to the vehicle ID; a third vehicle ID registration unit that associates the vehicle ID and the occupant ID and registers them in a vehicle database stored in the third memory unit; a third vehicle ID output unit that outputs the vehicle ID and the occupant ID in a manner that the evacuee can take with them; and a third vehicle ID output unit that acquires the resident ID brought by the evacuee and the vehicle ID and the occupant ID output by the third vehicle ID output unit. The system further includes a third code information acquisition unit, and when the third code information acquisition unit acquires the resident ID, the vehicle ID, and the occupant ID, the third vehicle ID registration unit rewrites the occupant ID registered in the vehicle database in association with the vehicle ID to the resident ID, and when the third synchronization unit determines that the network is capable of communication, the third communication unit transmits the vehicle ID and the resident ID registered in the vehicle database stored in the third memory unit to the server device, the server communication unit receives the transmitted vehicle ID and resident ID, and the server resident ID registration unit associates the vehicle ID and the resident ID and registers them in the vehicle database stored in the server memory unit.

If the third venue is an evacuation/exit inspection venue (if evacuees travel to the evacuation/exit inspection venue via multiple indoor evacuation venues), the third terminal device manages information about the vehicles in which evacuees are riding in a vehicle database, and the vehicle information can be associated with information about the evacuees riding in that vehicle, which is managed in the resident database. When communication between the second terminal device and the server device becomes possible, the second terminal device sends vehicle information to the server device, and the server device stores the vehicle information. This allows information about the vehicles in which evacuees are riding to be shared between the third terminal device and the server device.

(9) The evacuation information management system of the ninth aspect is the evacuation information management system of (3), wherein the third terminal device further includes a third vehicle ID issuing unit that issues a vehicle ID including identification information for the third venue and information that distinguishes the vehicle in which the evacuee is riding from other vehicles, a third code information acquisition unit that acquires the resident ID, and a second vehicle ID registration unit that associates the resident ID and the vehicle ID and registers them in a vehicle database stored in the third memory unit, and when the third synchronization unit determines that the network is capable of communication, the third communication unit transmits the vehicle ID and the resident ID registered in the vehicle database stored in the third memory unit to the server device, the server communication unit receives the transmitted vehicle ID and the resident ID, and the server resident ID registration unit associates the vehicle ID and the resident ID and registers them in the vehicle database stored in the server memory unit.
By registering the resident ID when issuing the vehicle ID, the vehicle ID and resident ID may be associated and registered in the vehicle DB without using the occupant ID.

(10) The evacuation information management system according to the tenth aspect is an evacuation information management system according to any one of (1) to (9), further comprising a list registration unit that registers the vehicle ID of the vehicle or the evacuee ID of the evacuee in inspection list information for the next inspection to be conducted on the vehicle or the evacuee based on the results of an inspection to determine whether radioactive materials are attached to the vehicle or the evacuee, and an inspection list information output unit that outputs the inspection list information.
Vehicle IDs and evacuee IDs are automatically registered in the inspection list information. Staff at each inspection location can compare the vehicle in front of them with the vehicle information assigned with the vehicle ID registered in the inspection list information, and if the vehicle is registered in the inspection list information, they can carry out an inspection, but if not, they can decide not to inspect it. This reduces the workload of staff.

(11) The evacuation information management system according to the eleventh aspect is an evacuation information management system according to any one of (1) to (10), further comprising an inspection target output unit that outputs the vehicle ID of the vehicle in which the evacuee is riding and the resident IDs of other evacuees riding in the vehicle when an inspection of the evacuee to determine whether radioactive material is attached to the evacuee results in the presence of radioactive material.
This means that if contamination is confirmed during a representative inspection, all passengers will be subject to inspection, and it will be possible to quickly determine which vehicle the passenger subject to inspection was in.

(12) The evacuation information management system according to the twelfth aspect is an evacuation information management system according to any one of (1) to (11), further comprising an inspection certificate issuing unit that issues an inspection certificate only if, as a result of inspecting the vehicle or the evacuee to determine whether radioactive material is attached to the vehicle or the evacuee, it is confirmed that the radioactive material attached to the vehicle or the evacuee is within an acceptable range.
This makes it possible to control the system so that vehicles are not allowed to pass unless the inspection of people who require inspection has been completed.

1... Indoor evacuation venue 2... Inspection venue when evacuation and exiting the area 3... Evacuation route 4... Evacuation shelter 5... Disaster response headquarters 6... Evacuee 7... Vehicle 10, 20, 30, 40... Terminal 11, 21, 31, 41... Router 12, 22, 32, 42... Reading device 13, 23, 33, 43... Printer 50... Server 60... Mobile terminal 101, 201, 301, 401, 501... Input reception unit 102, 20 2, 302, 402... Code information management unit 103, 203, 303, 403, 502... DB management unit 104, 204, 304, 404, 503... DB synchronization unit 105, 205, 305, 405, 504... Output unit 106, 206, 306, 406, 505... Storage unit 107, 207, 307, 407, 506... Communication unit 208... Inspection certificate issuing unit 900... Computer 901... CPU
902: Main storage device 903: Auxiliary storage device 904: Input/output interface 905: Communication interface

Claims (12)

An evacuation information management system comprising: a first terminal device provided in a first venue where evacuees will stay; a second terminal device provided in a second venue where the evacuees will stay after staying at the first venue; and a server device connected to the first terminal device and the second terminal device via a network,
The first terminal device
a first storage unit that stores a resident database;
a first resident ID issuing unit that issues a resident ID including identification information of the first venue and information that distinguishes the evacuee from other evacuees;
a first resident ID registration unit that associates the resident ID with personal information of the evacuee and registers the association information in the resident database stored in the first storage unit;
a first resident ID output unit that outputs the resident ID in a manner that the evacuee can take with them;
a first synchronization unit that determines whether the network is available for communication;
a first communication unit,
The second terminal device
a second storage unit that stores the resident database;
a second resident ID acquisition unit that acquires the resident ID brought by the evacuee;
a second resident ID registration unit that associates the resident ID acquired by the second resident ID acquisition unit with the identification information of the second venue and registers them in the resident database stored in the second storage unit;
a second synchronization unit that determines whether the network is available for communication;
a second communication unit,
The server device
a server storage unit that stores the resident database;
a server resident ID registration unit that associates the resident ID, the personal information, and the identification information of the second venue and registers them in the resident database stored in the server storage unit;
a server communication unit;
the first communication unit transmits the resident ID and the personal information registered in the resident database stored in the first storage unit to the server device when the first synchronization unit determines that the network is communicable;
The server communication unit receives the transmitted resident ID and the personal information,
the server resident ID registration unit associates the resident ID with the personal information and registers them in the resident database stored in the server storage unit;
When the second synchronization unit determines that the network is communicable, the second communication unit transmits to the server device the resident ID and identification information of the second venue, which are registered in the resident database stored in the second storage unit;
The server communication unit receives the transmitted resident ID and the identification information of the second venue,
the server resident ID registration unit associates the resident ID with the identification information of the second venue and registers them in the resident database stored in the server storage unit ;
The first terminal device
a first vehicle ID issuing unit that issues a vehicle ID including identification information of the first venue and information for distinguishing the vehicle in which the evacuee is riding from other vehicles, and an occupant ID that adds information for distinguishing the evacuee from other evacuees riding in the vehicle to the vehicle ID;
a first vehicle ID registration unit that associates the vehicle ID with the occupant ID and registers them in a vehicle database stored in the first storage unit;
a first vehicle ID output unit that outputs the vehicle ID and the occupant ID in a manner that the evacuee can take with them;
a first code information acquisition unit that acquires the resident ID output by the first resident ID output unit, and the vehicle ID and the occupant ID output by the first vehicle ID output unit;
Furthermore,
When the first code information acquisition unit acquires the resident ID, the vehicle ID, and the occupant ID, the first vehicle ID registration unit rewrites the occupant ID registered in the vehicle database in association with the vehicle ID to the resident ID,
the first communication unit transmits the vehicle ID and the resident ID registered in the vehicle database stored in the first storage unit to the server device when the first synchronization unit determines that communication is possible over the network;
The server communication unit receives the transmitted vehicle ID and the transmitted resident ID,
the server resident ID registration unit associates the vehicle ID with the resident ID and registers them in the vehicle database stored in the server storage unit;
Evacuation information management system. An evacuation information management system comprising: a first terminal device provided in a first venue where evacuees will stay; a second terminal device provided in a second venue where the evacuees will stay after staying at the first venue; and a server device connected to the first terminal device and the second terminal device via a network,
The first terminal device
a first storage unit that stores a resident database;
a first resident ID issuing unit that issues a resident ID including identification information of the first venue and information that distinguishes the evacuee from other evacuees;
a first resident ID registration unit that associates the resident ID with personal information of the evacuee and registers the association information in the resident database stored in the first storage unit;
a first resident ID output unit that outputs the resident ID in a manner that the evacuee can take with them;
a first synchronization unit that determines whether the network is available for communication;
a first communication unit,
The second terminal device
a second storage unit that stores the resident database;
a second resident ID acquisition unit that acquires the resident ID brought by the evacuee;
a second resident ID registration unit that associates the resident ID acquired by the second resident ID acquisition unit with the identification information of the second venue and registers them in the resident database stored in the second storage unit;
a second synchronization unit that determines whether the network is available for communication;
a second communication unit,
The server device
a server storage unit that stores the resident database;
a server resident ID registration unit that associates the resident ID, the personal information, and the identification information of the second venue and registers them in the resident database stored in the server storage unit;
a server communication unit;
the first communication unit transmits the resident ID and the personal information registered in the resident database stored in the first storage unit to the server device when the first synchronization unit determines that the network is communicable;
The server communication unit receives the transmitted resident ID and the personal information,
the server resident ID registration unit associates the resident ID with the personal information and registers them in the resident database stored in the server storage unit;
When the second synchronization unit determines that the network is communicable, the second communication unit transmits to the server device the resident ID and identification information of the second venue, which are registered in the resident database stored in the second storage unit;
The server communication unit receives the transmitted resident ID and the identification information of the second venue,
the server resident ID registration unit associates the resident ID with the identification information of the second venue and registers them in the resident database stored in the server storage unit ;
The first terminal device
a first vehicle ID issuing unit that issues a vehicle ID including identification information of the first venue and information that distinguishes the vehicle in which the evacuees board from other vehicles;
a first code information acquisition unit that acquires the resident ID;
a first vehicle ID registration unit that associates the resident ID with the vehicle ID and registers them in a vehicle database stored in the first storage unit;
Furthermore,
the first communication unit transmits the vehicle ID and the resident ID registered in the vehicle database stored in the first storage unit to the server device when the first synchronization unit determines that communication is possible over the network;
The server communication unit receives the transmitted vehicle ID and the transmitted resident ID,
the server resident ID registration unit associates the vehicle ID with the resident ID and registers them in the vehicle database stored in the server storage unit;
Evacuation information management system. An evacuation information management system comprising: a first terminal device provided in a first venue where evacuees will stay; a second terminal device provided in a second venue where the evacuees will stay after staying at the first venue; and a server device connected to the first terminal device and the second terminal device via a network,
The first terminal device
a first storage unit that stores a resident database;
a first resident ID issuing unit that issues a resident ID including identification information of the first venue and information that distinguishes the evacuee from other evacuees;
a first resident ID registration unit that associates the resident ID with personal information of the evacuee and registers the association information in the resident database stored in the first storage unit;
a first resident ID output unit that outputs the resident ID in a manner that the evacuee can take with them;
a first synchronization unit that determines whether the network is available for communication;
a first communication unit,
The second terminal device
a second storage unit that stores the resident database;
a second resident ID acquisition unit that acquires the resident ID brought by the evacuee;
a second resident ID registration unit that associates the resident ID acquired by the second resident ID acquisition unit with the identification information of the second venue and registers them in the resident database stored in the second storage unit;
a second synchronization unit that determines whether the network is available for communication;
a second communication unit,
The server device
a server storage unit that stores the resident database;
a server resident ID registration unit that associates the resident ID, the personal information, and the identification information of the second venue and registers them in the resident database stored in the server storage unit;
a server communication unit;
the first communication unit transmits the resident ID and the personal information registered in the resident database stored in the first storage unit to the server device when the first synchronization unit determines that the network is communicable;
The server communication unit receives the transmitted resident ID and the personal information,
the server resident ID registration unit associates the resident ID with the personal information and registers them in the resident database stored in the server storage unit;
When the second synchronization unit determines that the network is communicable, the second communication unit transmits to the server device the resident ID and identification information of the second venue, which are registered in the resident database stored in the second storage unit;
The server communication unit receives the transmitted resident ID and the identification information of the second venue,
the server resident ID registration unit associates the resident ID with the identification information of the second venue and registers them in the resident database stored in the server storage unit ;
The second terminal device
a second vehicle ID issuing unit that issues a vehicle ID including identification information of the second venue and information for distinguishing the vehicle in which the evacuee is riding from other vehicles, and an occupant ID that adds information for distinguishing the evacuee from other evacuees riding in the vehicle to the vehicle ID;
a second vehicle ID registration unit that associates the vehicle ID with the occupant ID and registers them in a vehicle database stored in the second storage unit;
a second vehicle ID output unit that outputs the vehicle ID and the occupant ID in a manner that the evacuee can take with them;
a second code information acquisition unit that acquires the resident ID output by the first resident ID output unit and the vehicle ID and the occupant ID output by the second vehicle ID output unit;
Furthermore,
When the second code information acquisition unit acquires the resident ID, the vehicle ID, and the occupant ID, the second vehicle ID registration unit rewrites the occupant ID registered in the vehicle database in association with the vehicle ID to the resident ID,
the second communication unit transmits the vehicle ID and the resident ID registered in the vehicle database stored in the second storage unit to the server device when the second synchronization unit determines that communication is possible over the network;
The server communication unit receives the transmitted vehicle ID and the transmitted resident ID,
the server resident ID registration unit associates the vehicle ID with the resident ID and registers them in the vehicle database stored in the server storage unit;
Evacuation information management system. An evacuation information management system comprising: a first terminal device provided in a first venue where evacuees will stay; a second terminal device provided in a second venue where the evacuees will stay after staying at the first venue; and a server device connected to the first terminal device and the second terminal device via a network,
The first terminal device
a first storage unit that stores a resident database;
a first resident ID issuing unit that issues a resident ID including identification information of the first venue and information that distinguishes the evacuee from other evacuees;
a first resident ID registration unit that associates the resident ID with personal information of the evacuee and registers the association information in the resident database stored in the first storage unit;
a first resident ID output unit that outputs the resident ID in a manner that the evacuee can take with them;
a first synchronization unit that determines whether the network is available for communication;
a first communication unit,
The second terminal device
a second storage unit that stores the resident database;
a second resident ID acquisition unit that acquires the resident ID brought by the evacuee;
a second resident ID registration unit that associates the resident ID acquired by the second resident ID acquisition unit with the identification information of the second venue and registers them in the resident database stored in the second storage unit;
a second synchronization unit that determines whether the network is available for communication;
a second communication unit,
The server device
a server storage unit that stores the resident database;
a server resident ID registration unit that associates the resident ID, the personal information, and the identification information of the second venue and registers them in the resident database stored in the server storage unit;
a server communication unit;
the first communication unit transmits the resident ID and the personal information registered in the resident database stored in the first storage unit to the server device when the first synchronization unit determines that the network is communicable;
The server communication unit receives the transmitted resident ID and the personal information,
the server resident ID registration unit associates the resident ID with the personal information and registers them in the resident database stored in the server storage unit;
When the second synchronization unit determines that the network is communicable, the second communication unit transmits to the server device the resident ID and identification information of the second venue, which are registered in the resident database stored in the second storage unit;
The server communication unit receives the transmitted resident ID and the identification information of the second venue,
the server resident ID registration unit associates the resident ID with the identification information of the second venue and registers them in the resident database stored in the server storage unit ;
The second terminal device
a second vehicle ID issuing unit that issues a vehicle ID including identification information of the second venue and information that distinguishes the vehicle in which the evacuees board from other vehicles;
a second code information acquisition unit that acquires the resident ID;
a second vehicle ID registration unit that associates the resident ID with the vehicle ID and registers them in a vehicle database stored in the second storage unit;
Furthermore,
the second communication unit transmits the vehicle ID and the resident ID registered in the vehicle database stored in the second storage unit to the server device when the second synchronization unit determines that communication is possible over the network;
The server communication unit receives the transmitted vehicle ID and the transmitted resident ID,
the server resident ID registration unit associates the vehicle ID with the resident ID and registers them in the vehicle database stored in the server storage unit;
Evacuation information management system. When the first synchronization unit determines that the network is communicable, the first communication unit receives, from the server device, identification information of the second venue associated with the resident ID registered in the resident database stored in the server storage unit;
The first resident ID registration unit associates the identification information of the second venue with the resident ID and registers it in the resident database stored in the first storage unit;
the second communication unit receives, when the second synchronization unit determines that the network is communicable, from the server device the personal information associated with the resident ID registered in the resident database stored in the server storage unit;
The second resident ID registration unit associates the personal information with the resident ID and registers it in the resident database stored in the second storage unit.
5. The evacuation information management system according to claim 1. a third terminal device provided in a third venue where the evacuees will stay after staying in the second venue,
The third terminal device
a third storage unit that stores the resident database;
a third resident ID acquisition unit that acquires the resident ID brought by the evacuee and identification information of venues other than the first venue where the evacuee has stayed;
a third resident ID registration unit that associates the resident ID acquired by the third resident ID acquisition unit with the identification information of the other venue and registers them in the resident database stored in the third storage unit;
a third synchronization unit that determines whether the network is available for communication;
a third communication unit,
When the third synchronization unit determines that the network is communicable, the third communication unit transmits to the server device the resident ID and identification information of the other venue, which are registered in the resident database stored in the third storage unit;
The server communication unit receives the transmitted resident ID and the identification information of the other venue,
the server resident ID registration unit associates the resident ID with the identification information of the other venue and registers them in the resident database stored in the server storage unit;
5. The evacuation information management system according to claim 1. An evacuation information management system comprising: a first terminal device provided in a first venue where evacuees will stay; a second terminal device provided in a second venue where the evacuees will stay after staying at the first venue; a third terminal device provided in a third venue where the evacuees will stay after staying at the second venue; and a server device connected to the first terminal device, the second terminal device, and the third terminal device via a network,
The first terminal device
a first storage unit that stores a resident database;
a first resident ID issuing unit that issues a resident ID including identification information of the first venue and information that distinguishes the evacuee from other evacuees;
a first resident ID registration unit that associates the resident ID with personal information of the evacuee and registers the association information in the resident database stored in the first storage unit;
a first resident ID output unit that outputs the resident ID in a manner that the evacuee can take with them;
a first synchronization unit that determines whether the network is available for communication;
a first communication unit,
The second terminal device
a second storage unit that stores the resident database;
a second resident ID acquisition unit that acquires the resident ID brought by the evacuee;
a second resident ID registration unit that associates the resident ID acquired by the second resident ID acquisition unit with the identification information of the second venue and registers them in the resident database stored in the second storage unit;
a second synchronization unit that determines whether the network is available for communication;
a second communication unit,
The third terminal device
a third storage unit that stores the resident database;
a third resident ID acquisition unit that acquires the resident ID brought by the evacuee and identification information of venues other than the first venue where the evacuee has stayed;
a third resident ID registration unit that associates the resident ID acquired by the third resident ID acquisition unit with the identification information of the other venue and registers them in the resident database stored in the third storage unit;
a third synchronization unit that determines whether the network is available for communication;
a third communication unit,
The server device
a server storage unit that stores the resident database;
a server resident ID registration unit that associates the resident ID, the personal information, and the identification information of the second venue and registers them in the resident database stored in the server storage unit;
a server communication unit;
the first communication unit transmits the resident ID and the personal information registered in the resident database stored in the first storage unit to the server device when the first synchronization unit determines that the network is communicable;
The server communication unit receives the transmitted resident ID and the personal information,
the server resident ID registration unit associates the resident ID with the personal information and registers them in the resident database stored in the server storage unit;
When the second synchronization unit determines that the network is communicable, the second communication unit transmits to the server device the resident ID and identification information of the second venue, which are registered in the resident database stored in the second storage unit;
The server communication unit receives the transmitted resident ID and the identification information of the second venue,
the server resident ID registration unit associates the resident ID with the identification information of the second venue and registers them in the resident database stored in the server storage unit ;
When the third synchronization unit determines that the network is communicable, the third communication unit transmits to the server device the resident ID and identification information of the other venue, which are registered in the resident database stored in the third storage unit;
The server communication unit receives the transmitted resident ID and the identification information of the other venue,
the server resident ID registration unit associates the resident ID with the identification information of the other venue and registers them in the resident database stored in the server storage unit;
The third terminal device
a third vehicle ID issuing unit that issues a vehicle ID including identification information of the third venue and information for distinguishing the vehicle in which the evacuee is riding from other vehicles, and an occupant ID that adds information for distinguishing the evacuee from other evacuees riding in the vehicle to the vehicle ID;
a third vehicle ID registration unit that associates the vehicle ID with the occupant ID and registers them in a vehicle database stored in the third storage unit;
a third vehicle ID output unit that outputs the vehicle ID and the occupant ID in a manner that the evacuee can take with them;
a third code information acquisition unit that acquires the resident ID brought by the evacuee and the vehicle ID and the occupant ID output by the third vehicle ID output unit;
Furthermore,
When the third code information acquisition unit acquires the resident ID, the vehicle ID, and the occupant ID, the third vehicle ID registration unit rewrites the occupant ID registered in the vehicle database in association with the vehicle ID to the resident ID,
the third communication unit transmits the vehicle ID and the resident ID registered in the vehicle database stored in the third storage unit to the server device when the third synchronization unit determines that communication is possible over the network;
The server communication unit receives the transmitted vehicle ID and the transmitted resident ID,
the server resident ID registration unit associates the vehicle ID with the resident ID and registers them in the vehicle database stored in the server storage unit;
Evacuation information management system. An evacuation information management system comprising: a first terminal device provided in a first venue where evacuees will stay; a second terminal device provided in a second venue where the evacuees will stay after staying at the first venue; a third terminal device provided in a third venue where the evacuees will stay after staying at the second venue; and a server device connected to the first terminal device, the second terminal device, and the third terminal device via a network,
The first terminal device
a first storage unit that stores a resident database;
a first resident ID issuing unit that issues a resident ID including identification information of the first venue and information that distinguishes the evacuee from other evacuees;
a first resident ID registration unit that associates the resident ID with personal information of the evacuee and registers the association information in the resident database stored in the first storage unit;
a first resident ID output unit that outputs the resident ID in a manner that the evacuee can take with them;
a first synchronization unit that determines whether the network is available for communication;
a first communication unit,
The second terminal device
a second storage unit that stores the resident database;
a second resident ID acquisition unit that acquires the resident ID brought by the evacuee;
a second resident ID registration unit that associates the resident ID acquired by the second resident ID acquisition unit with the identification information of the second venue and registers them in the resident database stored in the second storage unit;
a second synchronization unit that determines whether the network is available for communication;
a second communication unit,
The third terminal device
a third storage unit that stores the resident database;
a third resident ID acquisition unit that acquires the resident ID brought by the evacuee and identification information of venues other than the first venue where the evacuee has stayed;
a third resident ID registration unit that associates the resident ID acquired by the third resident ID acquisition unit with the identification information of the other venue and registers them in the resident database stored in the third storage unit;
a third synchronization unit that determines whether the network is available for communication;
a third communication unit,
The server device
a server storage unit that stores the resident database;
a server resident ID registration unit that associates the resident ID, the personal information, and the identification information of the second venue and registers them in the resident database stored in the server storage unit;
a server communication unit;
the first communication unit transmits the resident ID and the personal information registered in the resident database stored in the first storage unit to the server device when the first synchronization unit determines that the network is communicable;
The server communication unit receives the transmitted resident ID and the personal information,
the server resident ID registration unit associates the resident ID with the personal information and registers them in the resident database stored in the server storage unit;
When the second synchronization unit determines that the network is communicable, the second communication unit transmits to the server device the resident ID and identification information of the second venue, which are registered in the resident database stored in the second storage unit;
The server communication unit receives the transmitted resident ID and the identification information of the second venue,
the server resident ID registration unit associates the resident ID with the identification information of the second venue and registers them in the resident database stored in the server storage unit ;
When the third synchronization unit determines that the network is communicable, the third communication unit transmits to the server device the resident ID and identification information of the other venue, which are registered in the resident database stored in the third storage unit;
The server communication unit receives the transmitted resident ID and the identification information of the other venue,
the server resident ID registration unit associates the resident ID with the identification information of the other venue and registers them in the resident database stored in the server storage unit;
The third terminal device
a third vehicle ID issuing unit that issues a vehicle ID including identification information of the third venue and information that distinguishes the vehicle in which the evacuees board from other vehicles;
a third code information acquisition unit that acquires the resident ID brought by the evacuee;
a second vehicle ID registration unit that associates the resident ID with the vehicle ID and registers them in a vehicle database stored in the third storage unit;
Furthermore,
the third communication unit transmits the vehicle ID and the resident ID registered in the vehicle database stored in the third storage unit to the server device when the third synchronization unit determines that communication is possible over the network;
The server communication unit receives the transmitted vehicle ID and the transmitted resident ID,
the server resident ID registration unit associates the vehicle ID with the resident ID and registers them in the vehicle database stored in the server storage unit;
Evacuation information management system. a list registration unit that registers the vehicle ID of the vehicle or the evacuee ID of the evacuee in inspection list information for the next inspection to be conducted on the vehicle or the evacuee based on the results of an inspection of the vehicle in which the evacuee is riding or the evacuee to determine whether radioactive materials are attached to the vehicle or the evacuee;
an examination list information output unit that outputs the examination list information;
The evacuation information management system according to claim 1 , further comprising: an inspection target output unit that, when the inspection result indicates that radioactive materials are attached to the evacuees as a result of inspecting the evacuees to see if they have radioactive materials attached, outputs the vehicle ID of the vehicle in which the evacuees are riding and the resident IDs of the other evacuees riding in the vehicle;
The evacuation information management system according to claim 1 , further comprising: an inspection certificate issuing department that issues an inspection certificate only if it is confirmed that the radioactive material adhering to the vehicle or the evacuee is within an acceptable range as a result of inspecting the vehicle or the evacuee to see if any radioactive material is adhering to the vehicle or the evacuee;
The evacuation information management system according to claim 1 , further comprising: An evacuation information management system comprising: a first terminal device provided in a first venue where evacuees will stay; a second terminal device provided in a second venue where the evacuees will stay after staying at the first venue; and a server device connected to the first terminal device and the second terminal device via a network,
The first terminal device
a first storage unit that stores a resident database;
a first resident ID issuing unit that issues a resident ID including identification information of the first venue and information that distinguishes the evacuee from other evacuees;
a first resident ID registration unit that associates the resident ID with personal information of the evacuee and registers the association information in the resident database stored in the first storage unit;
a first resident ID output unit that outputs the resident ID in a manner that the evacuee can take with them;
a first synchronization unit that determines whether the network is available for communication;
a first communication unit,
The second terminal device
a second storage unit that stores the resident database;
a second resident ID acquisition unit that acquires the resident ID brought by the evacuee;
a second resident ID registration unit that associates the resident ID acquired by the second resident ID acquisition unit with the identification information of the second venue and registers them in the resident database stored in the second storage unit;
a second synchronization unit that determines whether the network is available for communication;
A second communication unit;
an inspection target output unit that outputs the vehicle ID of the vehicle in which the evacuee is riding and the resident IDs of other evacuees riding in the vehicle when the inspection result indicates that radioactive materials are attached to the evacuee as a result of inspecting whether radioactive materials are attached to the evacuee;
Equipped with
The server device
a server storage unit that stores the resident database;
a server resident ID registration unit that associates the resident ID, the personal information, and the identification information of the second venue and registers them in the resident database;
a server communication unit;
the first communication unit transmits the resident ID and the personal information registered in the resident database stored in the first storage unit to the server device when the first synchronization unit determines that the network is communicable;
The server communication unit receives the transmitted resident ID and the personal information,
the server resident ID registration unit associates the resident ID with the personal information and registers it in the resident database stored in the server storage unit;
When the second synchronization unit determines that the network is communicable, the second communication unit transmits to the server device the resident ID and identification information of the second venue, which are registered in the resident database stored in the second storage unit;
The server communication unit receives the transmitted resident ID and the identification information of the second venue,
The server resident ID registration unit associates the resident ID with the identification information of the second venue and registers them in the resident database stored in the server storage unit.
Evacuation information management system.