JP7510311B2 - Disaster response support method and disaster response support system - Google Patents

Description

The present invention relates to a disaster response support method and a disaster response support system.

When a large-scale disaster occurs and damages roads in a region, road restoration work places a heavy burden on the affected local governments and public organizations, who are already busy dealing with a wide variety of other disaster countermeasures. Depending on the extent of the damage, it may be difficult to carry out restoration work.

On the other hand, roads in the affected areas tend to see a sudden increase in traffic during disasters, such as for rescuing disaster victims and transporting supplies to evacuation facilities. Therefore, the importance of roads in disaster-stricken areas is often higher than usual.

There is therefore existing technology that examines the impact of such road damage. For example, an object-oriented computer program (see Patent Document 1) has been proposed that aims to simulate the impact of partial disruption of a transportation network on a local community.

This technology is characterized by treating the nodes as objects on a mesh structure consisting of multiple nodes that represent intersections or relay points, etc., and paths that represent paths without branching from node to node, and by using inter-object communication to simultaneously find multiple optimal radial routes from any one node to all other nodes.

JP 2004-341794 A

Conventional technology does not fully consider the fact that damage and recovery status from a disaster can change over time, nor does it adequately take into account the amount and importance of supplies being transported in disaster-stricken areas. As a result, it is not possible to provide information that contributes to appropriate road recovery plans and supply delivery plans overall.

The object of the present invention is to provide technology that can respond to changes in the situation in disaster-stricken areas and efficiently provide appropriate information that will contribute to planning road restoration and material transportation in those areas.

The disaster response support method of the present invention, which solves the above-mentioned problems, includes a process in which an information processing device stores information on each supply and demand base of materials, information on the importance of the materials, and information on a road network in a region including each of the supply and demand bases in a storage device, and estimates a delivery route for the materials connecting the supply and demand bases based on the location of each base indicated by the information on each base and the information on the road network, a process for specifying a delivery amount of the materials to be delivered between the bases at a predetermined time based on a transition schedule of each state of the material supply or demand over time at each base indicated by the information on each base, the transition schedule being determined based on the time elapsed since the time of the disaster, the process for obtaining information on areas damaged by the disaster in the road network from a predetermined external device that manages disaster information, and a process for narrowing down target roads including the damaged areas among the roads in the delivery route, and the above process. The system executes a process of determining a recovery priority for the target road based on each piece of information, including the length of the target road based on information on the road network, the delivery volume of the materials identified based on information on the cargo to be transported on the target road, and the importance of the materials, and a process of outputting recommended information for the delivery route of the materials in an output form corresponding to the recovery priority.The system is characterized in that it executes a process of identifying the content of the disaster at each base based on disaster occurrence information indicating the type and scale of the disaster in each area and the location of each base, obtained from the external device as information on the damaged area, and predicting future state transitions in a time series based on the content of the disaster and the transition schedule at each base, and estimating the supply or demand state of materials at each base based on the operating status of each base at a specified point in time based on the results of the prediction .

The disaster response support system of the present invention includes a storage device that stores information on each supply and demand base of materials, information on the importance of the materials, and information on a road network in a region including each of the supply and demand bases, a process for estimating a delivery route for the materials connecting the supply and demand bases based on the location of each base indicated by the information on each base and the information on the road network, a process for specifying a delivery amount of the materials to be delivered between the bases at a predetermined time based on a transition schedule of each state of the material supply or demand over time at each base indicated by the information on each base, the transition schedule being determined based on the time elapsed since the time of the disaster, a process for acquiring information on areas damaged by the disaster in the road network from a predetermined external device that manages disaster information, a process for narrowing down target roads that include the damaged areas among the roads on the delivery route, and, with respect to the target roads, The system executes a process of determining a recovery priority based on each piece of information, namely, the length of the target road based on information on the road network, the delivery volume of the materials identified based on information on the cargo to be transported on the target road, and the importance of the materials, and a process of outputting recommended information for the delivery route of the materials in an output form corresponding to the recovery priority.The system includes a process of identifying the content of the disaster at each base based on disaster occurrence information indicating the type and scale of the disaster in each area and the location of each base, obtained from the external device as information on the damaged area, and predicting future state transitions in time series based on the content of the disaster at each base and the transition schedule, and a calculation device that estimates the supply or demand state of materials at each base based on the operating status of each base at a specified time based on the results of the prediction .

The present invention makes it possible to respond to changes in the situation in disaster-stricken areas and efficiently provide appropriate information that contributes to planning road restoration and material transportation in those areas.

1 is a diagram illustrating an example of the configuration of a disaster response support system according to an embodiment of the present invention. 10 is a diagram showing an example of a data configuration of a supply facility information table according to the embodiment; FIG. FIG. 4 is a diagram illustrating an example of a data configuration of a demand base information table according to the present embodiment. FIG. 4 is a diagram showing an example of a data configuration of a road information table according to the embodiment; 4 is a diagram showing an example of a data configuration of a material information table according to the embodiment; FIG. 5 is a diagram illustrating an example of a data configuration of a state information table according to the present embodiment. FIG. 4 is a diagram illustrating an example of a data configuration of a state transition information table according to the present embodiment. FIG. 11 is a diagram illustrating an example of a data configuration of an alert threshold information table according to the present embodiment. FIG. 5 is a diagram illustrating an example of a data configuration of an output threshold information table according to the embodiment. FIG. 4 is a diagram illustrating an example of a data configuration of a disaster information table according to the embodiment. FIG. 5 is a diagram illustrating an example of a data configuration of an inventory information table according to the present embodiment. FIG. 11 is a diagram showing an example of a data configuration of a required material quantity information table according to the present embodiment. FIG. 4 is a diagram showing an example of a data configuration of a transportation information table according to the embodiment; FIG. 4 is a diagram showing an example of a data configuration of a cargo information table according to the embodiment; FIG. FIG. 2 is a diagram illustrating an example of a data configuration of a road restoration plan information table according to the embodiment. FIG. 4 is a diagram illustrating an example of a data configuration of a road information table of the shortest route according to the embodiment. 10 is a diagram illustrating an example of a data configuration of a departure point/destination information table of the shortest route according to the embodiment. FIG. 4 is a diagram illustrating an example of a data configuration of a road restoration priority information table according to the embodiment. FIG. FIG. 2 is a diagram showing an example of a flow of a disaster response support method in the present embodiment. FIG. 2 is a diagram showing an example of a flow of a disaster response support method in the present embodiment. FIG. 4 is a diagram showing an example of a recommended screen for roads in the present embodiment. FIG. 11 is a diagram showing an example of a route recommendation screen in the present embodiment.

<System configuration example>
An embodiment of the present invention will be described in detail below with reference to the drawings. Fig. 1 is a diagram showing an example of a network configuration including a disaster response support system 100 according to the present embodiment. The disaster response support system 100 shown in Fig. 1 is a computer system capable of responding to changes in the situation in a disaster-stricken area and efficiently providing appropriate information that contributes to plans for road restoration and material transportation in the area.

Specifically, for example, a system is envisioned that collects various information on disaster-stricken areas, combines and analyzes that information, and provides information that contributes to road restoration and delivery plans to facilitate the transport of goods to disaster-stricken areas. However, the present invention is not limited to this embodiment, and the present invention is applicable to any situation in which information is provided to facilitate the transport of goods to disaster-stricken areas.

The disaster response support system 100 illustrated in FIG. 1 has a central control device 130, a main memory device 110, an auxiliary memory device 120, a communication device 131, and an input/output device 132. These are interconnected by a bus.

The auxiliary storage device 120 is composed of a non-volatile storage device such as a hard disk drive (HDD) or a solid state drive (SSD). This auxiliary storage device 120 stores a master database 121, a collection/estimation database 122, a database of results of calculations of other systems 123, and a priority storage database 124.

The main memory 110 is composed of a volatile memory device such as a RAM (Random Access Memory) and stores programs. When the programs are executed by the central control device 130, functions such as a data collection unit 111, a data estimation unit 112, a priority determination unit 113, an other system calculation result acquisition unit 114, and a distribution unit 115 are implemented. Hereinafter, when the subject is described as "XX unit", it is assumed that the central control device 130 reads each program from the auxiliary storage device 120, loads it into the main memory device 110, and then realizes the function of each program (described in detail below).

The disaster response headquarters system 150, the disaster information sharing system 151, the road restoration planning system 160, and the shortest route search system 161, which are devices that can be connected to the disaster response support system 100 described above via the communication line 140, are general-purpose computers.

Of these, the Disaster Management Headquarters System 150 is a system that collects and analyzes the situation in disaster-stricken areas and provides support for taking countermeasures. It operates in the local governments of disaster-stricken areas that take the lead in taking countermeasures, or within the government in the case of a large-scale disaster that spans multiple regions.

This disaster control headquarters system 150 operates as a separate system for each local government and each relevant government ministry or agency, but it may also be a system shared by local governments in multiple regions, or a system shared by multiple government ministries and agencies. It may also be a system shared by one or more local governments and one or more government ministries and agencies.

Next, the disaster information sharing system 151 is a system that provides disaster information such as earthquake intensity and road damage conditions to the disaster response support system 100.

In addition, the road restoration planning system 160 is a system for collecting information on road passability and damage status, and planning the order and timing of restoration based on these conditions.It is a system that provides road restoration plans to the disaster response support system 100 and accepts requests for road restoration.

The shortest route search system 161 is a system for searching for the shortest route by inputting the starting point, the destination, and constraints regarding the availability of roads. This shortest route search system 161 is a system that receives information on roads that cannot be used due to damage caused by a disaster from the disaster response support system 100, and provides the disaster response support system 100 with the shortest route from the starting point to the destination.

This shortest route search system 161 may utilize an existing tool that deals with mathematical programming problems. The functionality of this shortest route search system 161 may also be provided in the disaster response support system 100.

In addition, various networks can be used for the communication line 140, such as a LAN (Local Area Network), a dedicated line, a WAN (Wide Area Network), a power line network, a wireless network, a public line network, a mobile phone network, and a satellite communication line. When using a public line or other public communication line, a virtual private network (VPN) technology can be used to conceal the contents of the communication and create a pseudo-dedicated line.

1, the disaster response support system 100 is assumed to perform input and output independently, but it may be connected to another terminal (e.g., a terminal of a user who uses the functions of the disaster response support method) via a communication line 140, and information may be input and output by an input/output device of that terminal. Also, the disaster response support system 100 may be a subsystem of the disaster countermeasure headquarters system 150 or the disaster information sharing system 151.
<Data structure example>
Here, the database will be described in detail. Examples of tables included in the master database 121 are shown in Figures 2A, 2B, 2C, 2D, 3A, 3B, 4A, and 4B.

The master database 121 stores data such as the locations of supply facilities such as manufacturer warehouses, data such as the locations of supply demand bases such as regional supply bases, disaster evacuation shelters, and disaster prevention bases, data on road networks such as major roads, and attribute data for each item of supplies supplied by the government to disaster-stricken areas in the event of a disaster.

In addition, the master database 121 stores data showing the state of the disaster-stricken areas after the disaster occurs, and data showing how the state of the disaster-stricken areas will change in the future.

Furthermore, the master database 121 stores threshold data for determining whether a delay in the transportation of goods is occurring, and threshold data for classifying the levels of recommended data when the disaster response support system 100 outputs the recommended data.

The master database 121 is composed of a supply facility information table 200 (Figure 2A), a demand base information table 210 (Figure 2B), a road information table 220 (Figure 2C), a material information table 230 (Figure 2D), a status information table 300 (Figure 3A), a status transition information table 310 (Figure 3B), an alert threshold information table 400 (Figure 4A), and an output threshold information table 410 (Figure 4B).

2A stores data on the locations of supply facilities such as manufacturer warehouses, etc. This data is registered by users such as the administrator of the disaster response support system 100 based on the results of investigations conducted before a disaster occurs.

The supply facility information table 200 is composed of a supply facility ID 201 that uniquely identifies a supply facility, a name 202, and the latitude 203 and longitude 204 of the location. The key for identifying each record is the supply facility ID 201.

Of these, supply facility ID 201 is an identifier for uniquely identifying a manufacturer's factory, manufacturer's warehouse, wholesale warehouse, retail warehouse, retail store, etc. that can become a supply facility for goods in the event of a disaster. Name 202 indicates the name of the supply facility. Latitude 203 indicates the latitude information of the location of the supply facility. Furthermore, longitude 204 indicates the longitude information of the location of the supply facility.

The demand base information table 210 illustrated in FIG. 2B stores data on the locations of supply demand bases, such as wide-area supply bases, evacuation centers, hospitals, and residences. This data is registered by users, such as disaster response support managers, based on the results of surveys conducted before a disaster occurs.

This demand base information table 210 is composed of a demand base ID 211, a name 212, a latitude 213, a longitude 214, and a note 215. The key for identifying each record is the demand base ID 211.

Of the above, the demand base ID 211 is an identifier for uniquely identifying wide-area supply bases and the like established by prefectures as intermediate bases for supplying supplies to evacuation centers in need during disasters. Other bases that require supplies during disasters may include hospitals, evacuation centers, residences, and the like.

Furthermore, name 212 indicates the name of the demand base. Latitude 213 indicates the latitude information of the location of the demand base. Longitude 214 indicates the longitude information of the location of the demand base. Notes 215 may store information for distinguishing the demand base, such as whether the demand base is a disaster demand base or a demand base for normal business that is not related to disasters (such as a retail store), or if there is no need to distinguish, no data may need to be stored.

The road information table 220 shown in FIG. 2C stores data on road networks such as main roads. This data is registered by the user based on the results of surveys conducted before a disaster occurs. The registered data may also be data from existing map information.

This road information table 220 is composed of a road ID 221, a name 222, a latitude (start point) 223, a longitude (start point) 224, a latitude (end point) 225, a longitude (end point) 226, a distance 227, and a road width level 228. The key for identifying each record is the road ID 221.

Of the above, road ID 221 is an identifier for uniquely identifying a road for transporting supplies in the event of a disaster. It may be possible to limit the roads to a certain portion, such as to only target main roads.

In addition, name 222 indicates the name of the road. Latitude (start point) 223 indicates the latitude information of the location of the road's end point. Longitude (start point) 224 indicates the longitude information of the end point of the road's location. Latitude (end point) 225 indicates the latitude information of the location of the other end point of the road. Longitude (end point) 227 indicates the longitude information of the location of the other end point of the road.

Further, distance 227 indicates the length of the road. Width level 228 indicates the level of the width of the road. For example, the road may be divided into two levels, with 4m or less being narrow and 4m or more being wide, or may be divided into multiple levels, such as level 1 for 4m or less, level 2 for 4m or more, level 3 for two lanes, and level 4 for more than that.

The supplies information table 230 shown in FIG. 2D stores attribute data for each item of supplies that will be supplied by the government to disaster-stricken areas when a disaster occurs. This data is defined by the user based on existing knowledge, such as past disaster experiences and related literature.

The material information table 230 is composed of an item ID 231, a name 232, a category 233, an importance level 234, and notes 235. The key for identifying each record is the item ID 231.

Of these, item ID 231 is an identifier for uniquely identifying the item of supplies supplied by the government to disaster-stricken areas in the event of a disaster. Name 232 indicates the name of the item. Classification 233 is a classification item for classifying the type of item, such as food, medical supplies, clothing, etc.

In addition, importance 234 indicates the importance of the item. For example, food and medical supplies are directly related to maintaining the lives of disaster victims and therefore have a high importance, whereas clothing is not necessarily directly related to maintaining life and therefore may have a low importance. Food that can be preserved may be of high importance, whereas food that cannot be preserved may be of medium importance.

In addition, notes 235 may store information necessary to determine the importance (necessary/not necessary for life support, can be preserved/cannot be preserved) and the importance 234 may be determined based on this, or the reason for determining the importance may simply be stored, or no data may be stored if not particularly required.

The state information table 300 shown in FIG. 3A stores data indicating the state of the disaster-stricken area after the disaster. This data is defined by the user based on existing knowledge, such as past disaster experiences and related literature.

The state information table 300 is composed of a state ID 301, a disaster type 302, a disaster scale 303, a target 304, and a state 305. The key for identifying each record is the state ID 301.

This status ID 301 is an identifier that uniquely identifies information indicating the type of disaster (earthquake, typhoon, etc.), a numerical value indicating the scale of the disaster (seismic intensity for an earthquake, wind speed for a typhoon, etc.), and the object whose status is being grasped (supply facility, demand base, etc.).

Disaster type 302 indicates the type of disaster, such as earthquake, typhoon, etc. Disaster scale 303 indicates the scale of the disaster in numerical form, such as seismic intensity for an earthquake, or wind speed for a typhoon. Target 304 indicates targets whose status needs to be grasped from moment to moment because their status may change due to a disaster, such as supply facilities and demand bases for goods. Status 305 indicates what percentage of stock a supply facility can supply compared to its normal stock amount, what percentage of demand a demand base can expect compared to its expected demand amount, etc.
3B , data indicating how states transition is performed is stored in the state transition information table 310. This data is defined by the user based on existing knowledge, such as past disaster experiences and related literature.

The state transition information table 310 includes a transition source state ID 311 and a transition destination state ID 312.
12, a transition time 313, and a transition probability 314. The keys for identifying each record are a transition source state ID 311, a transition destination state ID 312, and a transition time 313.

Like state ID 301, source state ID 311 is an identifier that is uniquely identified by the type of disaster, the scale of the disaster, and the subject whose state is to be understood, and is an identifier that indicates the original state before the state transition.

The transition destination state ID 312 is an identifier similar to the transition destination state ID 311 and state ID 301, and is an identifier indicating the state to which the state transitions after the transition time has elapsed. The transition time 313 indicates the time elapsed from the transition source state to the transition destination state. The transition probability 314 indicates the probability that the state will transition from the transition source state to the transition destination state after the transition time has elapsed.

The alert threshold information table 400 shown in FIG. 4A stores threshold data for determining whether a delay in the transportation of goods is occurring. This data is defined by the user based on existing knowledge, such as past disaster experiences and related literature.

This alert threshold information table 400 is composed of an alert threshold ID 401, a type 402, and a threshold 403. The key for identifying each record is the alert threshold ID 401. The alert threshold ID 401 is an identifier for uniquely identifying the threshold for determining whether a delay in material transport is occurring.

Type 402 indicates the target of threshold setting, such as "time" indicating the deviation from the scheduled arrival time of the supplies, "quantity" indicating the deviation from the scheduled quantity, and "importance" indicating the importance of the scheduled arrival supplies. When setting the threshold, alert threshold ID 401 may be specified and only one record from this may be used, or these records may be combined with an AND condition, an OR condition, or a combination of an AND condition and an OR condition may be used as the condition. Threshold 403 indicates a numerical value set as the threshold corresponding to type 402.

In addition, the output threshold information table 410 illustrated in FIG. 4B stores threshold data for classifying the recommended data output by the disaster response support system 100 into levels. This data is defined by the user based on existing knowledge, such as past disaster experiences and related literature.

The output threshold information table 410 is composed of an output threshold ID 411, a priority threshold 412, and an output level 413. The key for identifying each record is the output threshold ID 411. The output threshold ID 411 is an identifier for uniquely identifying the threshold for classifying and outputting the recommended data output by the disaster response support system 100 according to the accuracy of the data.

The priority threshold 412 indicates a numerical value set as a threshold for the road restoration priority calculated by the disaster response support system 100. The output level 413 is used to classify the recommendation level of the roads and routes to be used for transporting goods, and the recommendation level is determined by the priority threshold 412.

5, 6A, 6B, 6C, and 6D show examples of tables contained in the collection/estimation database 122. In the collection/estimation database 122, data collected from the disaster area and data estimated based on the data collected from the disaster area are stored as data indicating the situation in the disaster area.

The collection/estimation database 122 is made up of a disaster information table 500 (FIG. 5A), an inventory information table 600 (FIG. 6A), a required material quantity information table 610 (FIG. 6B), a transportation information table 620 (FIG. 6C), and a cargo information table 630 (FIG. 6D).

The disaster information table 500 shown in FIG. 5 stores data related to the seismic intensity of earthquakes. This seismic intensity information table 210 stores data distributed from the disaster information sharing system 151, for example.

This disaster information table 500 is composed of a mesh ID 501, date and time 502, disaster type 503, disaster scale 504, and collection flag 505. The keys for identifying each record are the mesh ID 501, date and time 502, and disaster type 503. The mesh ID 501 is an identifier for uniquely identifying an area affected by a disaster.

Date and time 502 indicates the date and time when the damage was observed. Disaster type 503 indicates the type of disaster, such as earthquake, typhoon, etc. Disaster scale 504 indicates the scale of the disaster numerically, such as seismic intensity for an earthquake, or wind speed for a typhoon, etc.

The collection flag 505 is a flag that indicates whether the data in this record is the data observed in the disaster area and collected by the disaster response support system 100, or whether it is data estimated by the disaster response support system 100. For example, the value is "1" for collected data and "0" for estimated data.

6A stores inventory data of supply facilities. This inventory information table 600 is composed of a supply facility ID 601, date and time 602, item ID 603, inventory quantity 604, operation status 605, and collection flag 606. The keys for identifying each record are the supply facility ID 601, date and time 602, and item ID 603. Like the supply facility ID 201, the supply facility ID 601 is an identifier for uniquely identifying a manufacturer's factory, manufacturer's warehouse, wholesaler's warehouse, retailer's warehouse, retail store, etc. that can become a supply facility for supplies in the event of a disaster.
The date and time 602 indicates the date and time when the inventory information was observed or estimated. The item ID 603, like the item ID 231, is an identifier for uniquely identifying the item of goods to be supplied by the government to a disaster-stricken area in the event of a disaster.

Furthermore, inventory quantity 604 indicates the inventory quantity of each item of material at the supply facility. Operation status 605 indicates the percentage of inventory that the supply facility can supply. Collection flag 606, like collection flag 505, is a flag that indicates whether the data of this record is the actual data observed in the disaster area and collected by disaster response support system 100, or whether it is data estimated by disaster response support system 100.

The material requirement information table 610 shown in FIG. 6B stores data on the required amount of materials at the demand base. This material requirement information table 610 is composed of a demand base ID 611, a date and time 612, an item ID 613, a required amount 614, and a collection flag 615.

The keys for identifying each record are a demand base ID 611, a date and time 612, and an item ID 613. Like the demand base ID 211, the demand base ID 611 is an identifier for uniquely identifying wide-area supply bases set up by prefectures as intermediate bases for supplying supplies to evacuation centers in need during disasters.

The date and time 612 indicates the date and time when the required amount was observed or estimated. The item ID 613, like the item ID 231, is an identifier for uniquely identifying the item of goods to be supplied by the government to a disaster-stricken area in the event of a disaster.

Furthermore, the required quantity 614 indicates the required quantity of supplies at the demand base. The collection flag 615, like the collection flag 505, is a flag that indicates whether the data in this record is the actual data observed in the disaster area and collected by the disaster response support system 100, or whether it is data estimated by the disaster response support system 100.

The transport information table 620 illustrated in FIG. 6C stores data on the transport of goods from the supply facility to the demand base, including all transport data other than cargo. This transport information table 620 is composed of a transport reservation ID 621, a transport source ID 622, a transport destination ID 623, a scheduled departure date and time 624, a scheduled arrival date and time 625, a transport completion date and time 626, a collection flag 627, and notes 628.

The key for identifying each record is the transport reservation ID 621. The transport reservation ID 621 is an identifier for uniquely identifying the transport data of materials from the supply facility to the demand base. An identifier is assigned when it is confirmed that materials will be transported, and the record is not deleted but remains even if the transport is canceled before completion.

The source ID 622 indicates the identifier of the supply facility from which the goods are transported, and like the supply facility ID 201, is an identifier that uniquely identifies a manufacturer's factory, manufacturer's warehouse, wholesaler's warehouse, retailer's warehouse, retail store, etc. that can serve as a supply facility for goods in the event of a disaster.

Destination ID 623 indicates the identifier of the demand base to which the goods are to be delivered, and like demand base ID 211, is an identifier for uniquely identifying wide-area supply bases set up by prefectures as intermediate bases for supplying goods to evacuation centers in need during disasters.

Scheduled departure date and time 624 indicates the date and time of transportation start that was determined when it was confirmed that the goods would be transported. Scheduled arrival date and time 625 indicates the date and time of transportation end that was determined when it was confirmed that the goods would be transported. Transportation completion 626 is a flag that indicates that transportation of goods has been completed. For example, it is set to "1" when transportation is completed, "0" when transportation is in progress, and "-1" when transportation has been canceled by the shipper or the like.

Similarly to collection flag 505, collection flag 627 is a flag that indicates whether the data in this record is the data observed in the disaster area and collected by disaster response support system 100, or whether it is data estimated by disaster response support system 100.

In addition, notes 628 may store information related to the shipper of the shipment (government procurement/municipal procurement/regular private business), or no data may need to be stored if there is no need to distinguish between shippers.

The cargo information table 630 shown in FIG. 6D stores cargo data from the transport data of goods from the supply facility to the demand base. This cargo information table 630 is composed of a transport reservation ID 631, an item ID 632, a transport amount 633, and a collection flag 634.

The key for identifying each record is the transport reservation ID 631. Like the transport reservation ID 621, the transport reservation ID 631 is an identifier for uniquely identifying the transport data of materials from the supply facility to the demand base. Like the item ID 231, the item ID 632 is an identifier for uniquely identifying the type of material supplied by the government to a disaster-stricken area in the event of a disaster, and indicates the type of material to be transported from the supply facility to the demand base.

Furthermore, the transport volume 633 indicates the quantity of goods transported from the supply facility to the demand base. The collection flag 634, like the collection flag 505, is a flag that indicates whether the data of this record is the actual data observed in the disaster area and collected by the disaster response support system 100, or whether it is data estimated by the disaster response support system 100.

Next, Figures 7A and 7B show an example of the other system calculation result database 123. In the other system calculation result database 123, road restoration plans planned by the road restoration planning system 160 and the shortest route from the starting point to the destination searched by the shortest route search system 161 are stored as calculation results from other systems.

This other system calculation result database 123 is composed of a road restoration plan information table 700 (Figure 7A), a shortest route road information table 710 (Figure 7B), and a shortest route departure point/destination information table 720 (Figure 7C).

The road recovery plan table 700 shown in FIG. 7A stores data on recovery plans for road networks, such as trunk roads, that have been affected by disasters. This road recovery plan table 700 is composed of a road ID 701, a planned recovery start date and time 702, a planned recovery end date and time 703, and recovery completion 704.

The keys for identifying each record are the road ID 701, the planned recovery start date and time 702, and the planned recovery end date and time 703. Like the road ID 221, the road ID 701 is an identifier for uniquely identifying a road for transporting supplies in the event of a disaster. It is also possible to limit the roads to a certain portion, such as only targeting main roads.

The planned restoration start date and time 702 indicates the date and time when road restoration will begin, which was determined when a road restoration plan was drawn up and finalized. The planned restoration end date and time 703 indicates the date and time when road restoration will end, which was determined when a road restoration plan was drawn up and finalized. Restoration completion 704 is a flag indicating that the road restoration plan has actually been completed. For example, if restoration has been completed, it is set to "1," and if restoration has not yet been completed, it is set to "0."

The shortest route road information table 710 shown in FIG. 7B stores data on the transportation route from the supply facility to the demand base. This shortest route road information table 710 is composed of a route ID 711, a sequence 712, and a road ID 713.

The keys for identifying each record are the route ID 711 and the sequence 712. The route ID 711 is an identifier for uniquely identifying the shortest transportation route from the supply facility to the demand base. The roads in the transportation route may be limited to a portion of roads, such as trunk roads.

Order 712 indicates the order in which road ID 713 is used among the roads on the shortest transportation route. Road ID 713, like road ID 221, is an identifier for uniquely identifying a road for transporting supplies in the event of a disaster, and indicates the identifier of the road used on the transportation route.

The shortest route departure point/destination information table 720 shown in FIG. 7C stores data on the transportation route from the supply facility to the demand base. This shortest route departure point/destination information table 720 is composed of a route ID 721, departure point latitude 722, departure point longitude 723, arrival point latitude 724, and arrival point longitude 725.

The key for identifying each record is route ID 721. Like route ID 711, route ID 721 is an identifier for uniquely identifying the shortest transportation route from the supply facility to the demand base.

Furthermore, departure latitude 722 indicates the latitude information of the supply facility that is the departure point. Departure longitude 723 indicates the longitude information of the supply facility that is the departure point. Arrival latitude 724 indicates the latitude information of the demand base that is the arrival point. Arrival longitude 725 indicates the longitude information of the demand base that is the arrival point.

The road restoration priority information table 800 shown in FIG. 8 stores restoration priority data for roads such as trunk roads that have been affected by disasters. This road restoration priority information table 800 is composed of a road ID 801, a restoration priority 802, and a restoration priority order 803.

The key for identifying each record is the road ID 801. Like the road ID 221, the road ID 801 is an identifier for uniquely identifying a road that has been affected by a disaster and cannot be used for transporting goods. It may also be possible to limit the roads to a certain portion, such as only targeting main roads.

Moreover, the restoration priority 802 indicates the restoration priority of the road calculated by the disaster response support system 100. The restoration priority order 803 indicates the order in which the restoration priority of the road is arranged in descending order.
<Disaster response support method flow: Main flow>
The actual procedure of the disaster response support method in this embodiment will be described below with reference to the drawings. The various operations corresponding to the disaster response support method described below are realized by a program that the disaster response support system 100 reads into a memory or the like and executes. This program is composed of codes for performing the various operations described below.

FIG. 9 shows an example of the overall process from detecting a disaster to completing the determination of the road restoration priority, and FIG. 10 shows a detailed process example for determining the road restoration priority. The process of registering data in the master database 121 is performed by the user prior to the series of processes in FIG. 9 and FIG. 10 (process S900 to process S907, process S1000 to process S1009).

Figure 9 shows an example of the flow of the disaster response support method of this embodiment, which is a diagram showing an example of the overall processing flow from detecting a disaster to completing the determination of road restoration priority.

First, in step S900, the central control device 130 of the disaster response support system 100 starts the processing flow, for example, upon arrival of a predetermined time or receiving a user instruction, and proceeds to step S901.

In process S901, the data collection unit 111 collects disaster occurrence information at the time of the disaster occurrence, such as the earthquake's seismic intensity, from the disaster information sharing system 151 via the communication device 131. The collected disaster occurrence information is stored in the disaster information table 500 of the collection/estimation database 121.

When storing information in the disaster information table 500 described above, the data collection unit 111 stores the date and time when the disaster occurrence information was observed in date and time 502, stores the type of disaster in the disaster occurrence information in type 503, stores numerical data on the scale of the observed disaster in disaster scale 504, and stores the number "1" in collection flag 505 to indicate that data observed in the disaster area has been collected rather than estimated data, and then proceeds to process S902.

In process S902, the data collection unit 111 collects inventory information of supplies at supply facilities, information on the required amount of supplies at demand bases, transportation information of supplies from the supply facilities to the demand bases, and cargo information from the disaster response headquarters system 150 and the disaster information sharing system 151 via the communication device 131, stores the collected information in the collection/estimation database 122, and proceeds to process S903.

When inventory information of materials at a supply facility is stored in the inventory information table 600 of the collection/estimation database 122, the supply facility ID where the inventory information was observed is stored in supply facility ID 601, the date and time of observation is stored in date and time 602, the identifier of the item in the inventory information is stored in item ID 603, the observed inventory quantity is stored in inventory quantity 604, the operating status indicating the percentage of inventory that the supply facility can supply is stored in operating status 605, and the number "1" is stored in collection flag 606 to indicate that observed data has been collected rather than estimated data.

When storing information on the required quantity of materials at a demand base in the material required quantity information table 610 of the collection/estimation database 122, the demand base ID where the required quantity information was observed is stored in the demand base ID 611, the date and time of observation is stored in the date and time 612, the identifier of the item of the required quantity information is stored in the item ID 613, the observed required quantity is stored in the required quantity 614, and the number "1" is stored in the collection flag 615 to indicate that observed data has been collected rather than estimated data.

When storing information on the transportation of goods from a supply facility to a demand base in the transportation information table 620 of the collection/estimation database 122, the identifier assigned when it was confirmed that the goods would be transported is stored in the transportation reservation ID 621, the identifier of the supply facility from which the goods were transported is stored in the transportation source ID 622, the identifier of the demand base to which the goods were transported is stored in the transportation destination ID 623, the date and time of the start of the transportation determined when it was confirmed that the goods would be transported is stored in the scheduled departure date and time 624, the date and time of the end of the transportation determined when it was confirmed that the goods would be transported is stored in the scheduled arrival date and time 625, when the transportation of the goods is actually completed, a "1" indicating the completion of the transportation is stored in the transportation completion 626, and the number "1" is stored in the collection flag 625 to indicate that observed data has been collected rather than estimated data, and when storing information related to the shipper of the transportation, "government procurement" is stored in the remarks 628 if the shipper is the government, "municipal procurement" is stored if the shipper is a local government, or "normal private business" is stored if the shipper is a company.

When storing cargo information in the cargo information table 630 of the collection/estimation database 122, the same one stored in the transport reservation ID 621 is stored in the transport reservation ID 631, the identifier of the item of the material to be transported from the supply facility to the demand base is stored in the item ID 632, the quantity of the material to be transported from the supply facility to the demand base is stored in the transport quantity 633, and the number "1" is stored in the collection flag 634 to indicate that observed data has been collected rather than estimated data.

In process S903, the data estimation unit 112 acquires data for the supply facility information table 200, the demand base information table 210, the state information table 300, and the state transition information table 310 from the master database 121, acquires data for the disaster information table 500 from the collection/estimation database 122, estimates stock information for supplies at supply facilities and required quantity information for supplies at demand bases based on this data, stores/overwrites the estimated information in the stock information table 600 and required quantity information table 610 of the collection/estimation database 122, and proceeds to process S904.

Specifically, the data estimation unit 112 first searches for the supply facility ID 201 in the supply facility information table 200 from the supply facility ID 601 in the inventory information table 600, and obtains the latitude 203 and longitude 204. The data estimation unit 112 searches for the mesh ID that includes this latitude 203 and longitude 204 in the mesh ID 501 in the disaster information table 500.

Next, the data estimation unit 112 calculates the disaster type 503 and the disaster scale 504 of the record searched above.
From 04, the disaster type 302 and disaster scale 303 in the state information table 300 are searched, and among them, those for which the target 304 is "supply facility" are identified.

The data estimation unit 112 searches for the state ID 301 of the identified record using the source state ID 311 in the state transition information table 310, and obtains all of the values of the destination state ID 312, transition time 313, and transition probability 314 for the corresponding source state ID 311.

In this, the data estimation unit 112 searches for the source state ID 311 of the first state transition, and from that point onwards, predicts future state transitions in time series using the destination state ID 312, transition time 313 and transition probability 314. The state 305 of the state ID 301 that matches the destination state ID 312 in each of these time series indicates the operating state of the "supply facility" at that time.

The data estimation unit 112 calculates the expected value of the operating state by multiplying the operating state by the transition probability, estimates inventory information for materials at the supply facility based on the expected value of the operating state, and stores/overwrites the inventory information table 600 in the collection/estimation database 122.

At that time, the data estimation unit 112 stores/overwrites the time point on the time series at which the inventory information was estimated in date/time 602, stores/overwrites the operation status, which indicates the percentage of the inventory that the supply facility can supply, as the expected value of the operation status, in operation status 605, and stores/overwrites the value "0" in collection flag 606 to indicate that the data is estimated.

Similarly, for demand bases, the data estimation unit 112 processes the target 304 by replacing "supply facility" with "demand base" and predicts future state transitions in a time series. Based on this operating state, the data estimation unit 112 collects information on the required amount of materials at the demand base and stores/overwrites this information in the required amount information table 610 of the estimation database 122.

At that time, the data estimation unit 112 stores/overwrites the time point on the time series when the required amount information was estimated in date/time 602, interprets a value indicating the percentage of the required amount required at the demand base as equivalent to the operating state, multiplies the required amount 614 by this value, stores/overwrites the result in required amount 614, and stores/overwrites the numerical value "0" in collection flag 615 to indicate that the data is estimated. Note that the state transition may be predicted using a Markov chain.

In process S904, the priority determination unit 113 obtains data from the alert threshold information table 400 and the material information table 230 from the master database 121, obtains data from the transport information table 620 from the collection/estimation database 122, and determines whether a delay in material transport is occurring based on these.

In the above-mentioned judgment, the priority determination unit 113 compares the expected arrival date and time 625 in the transportation information table 620 with the current time, and extracts records in which the expected arrival date and time 625 exceeds the current time and the transportation completion flag 626 is "0", indicating that the item is in transportation.

The priority determination unit 113 also extracts the excess time from the scheduled arrival date and time 625, the transport volume 633 of the transport reservation ID 631 that matches the transport reservation ID 621, and the importance 234 of the item ID 230 that matches the item ID 632, and compares the excess time, transport volume 633, and importance 234 with the threshold 403 of the item that matches the type 402 in the alert threshold information table 400.

If the result of the above comparison exceeds the threshold value 430, the priority determination unit 113 determines that a delay in material transportation is occurring, and proceeds to process S905. On the other hand, if the result of the above comparison does not exceed the threshold value 430, the priority determination unit 113 determines that a delay in material transportation is not occurring, and returns to process S902.

In process S905, the priority determination unit 113 determines the priority of the road restoration (described in detail below), and the process proceeds to process S906.

In process S906, the priority determination unit 113 accepts an operation to continue/end the process from the user via the input/output terminal 132. Note that it is also possible to accept only an operation to end the process from the user, with the default being to continue the process. If the process is to continue, the process returns to process S902. If the process is to end the process, the process proceeds to process S907.

In process S907, the central processing unit 130 ends the entire process flow from detecting the occurrence of a disaster to completing the determination of the restoration priority of roads.
<Disaster response support flow: Determining recovery priorities>
FIG. 10 is a diagram showing an example of a flow of the disaster response support method of this embodiment, and is a diagram showing an example of a detailed process flow for determining the restoration priority of a road.

In this case, in process S1000, the central control device 130 of the disaster response support system 100 receives the determination result of the above-mentioned process S904, starts a process flow for determining the road restoration priority (detailed flow of process S905), and proceeds to process S1001.

In process S1001, the priority determination unit 113 calls the other system calculation result acquisition unit 114, which collects information on the road restoration plan from the road restoration plan system 160 via the communication device 131, stores it in the road restoration plan information table 700 in the other system calculation result database 123, and proceeds to process S1002.

When storing this information, in restoration completion 704, a "0" is stored for roads that are to be restored, and a "1" is stored for roads that have already been restored. For roads that have not suffered any damage and have no restoration plans, no record exists. Alternatively, records may be prepared for roads that have not suffered any damage, and a different value such as "-1" may be stored in this field.

In process S1002, the priority determination unit 113 calls the other system calculation result acquisition unit 114, which acquires the shortest route from the supply facility to the demand base from the shortest route search system 161 via the communication device 131 by specifying the latitude and longitude of the supply facility as the departure point and the demand base as the destination, and stores this in the road information table 710 for the shortest route in the other system calculation result database 123, and proceeds to process S1003.

In process S1003, the priority determination unit 113 extracts roads that have been damaged by the disaster and are on the shortest route. Specifically, the priority determination unit 113 extracts roads that have been damaged and will be restored by using road IDs 701 for which the restoration completion 704 in the road restoration plan table 700 is "0". Next, in order to limit the roads to those included in the route from the supply facility to the demand base, the priority determination unit 113 limits the road IDs 701 to those that match the road IDs 713 included in the route IDs 711 in the road information table 710 of the shortest route. If the limited road IDs 701 exist, the process proceeds to process S1004. If the limited road IDs 701 do not exist, the process proceeds to process S1009.

In process S1004, the priority determination unit 113 determines the roads extracted and limited in process S1003 as the roads to be subject to restoration priority determination, and proceeds to process S1005.

In process S1005, the priority determination unit 113 determines the priority of road restoration. Specifically, the priority determination unit 113 obtains the "distance" of the road ID 701 from the distance 227 of the road information table 220 of the master database 121. Next, the priority determination unit 113 determines the supply facility ID 201 of the departure point from the departure latitude 722 and departure longitude 723 of the route 721 that matches the route 711 including the road ID 713 that matches the road 701 ID, using the latitude 203 and longitude 204 of the supply facility information table 200 of the master database 121, and determines the demand base ID 211 of the arrival point from the arrival latitude 724 and arrival longitude 725, using the latitude 213 and longitude 214 of the demand base information table 210.

The priority determination unit 113 searches the transportation information table 620 in the collection/estimation database 122 for a transportation source ID 622 that matches the supply facility ID 201 and a transportation destination ID 623 that matches the demand base ID 211, and extracts those for which the transportation completion 626 is "0" and which are still in transportation, thereby narrowing down the transportation reservation IDs 621 that are a combination of the aforementioned supply facility ID 201 and demand base ID 211 and are in transportation.

The priority determination unit 113 then obtains the transport volume 633 from the reservation ID 631 in the cargo information table 630 that matches the transport reservation ID 621, and determines it as the "transport volume." The priority determination unit 113 also searches for the importance 234 from the item ID 231 in the material information table 230 in the master database 121 that matches the item ID 632, and determines it as the "importance" of the material being transported.

The priority determination unit 113 multiplies the distance, transportation volume, and importance values obtained here to determine the restoration priority of the road. When performing this multiplication, the priority determination unit 113 may calculate the total of each item and then multiply them, or may calculate the average of each item and then multiply them, or may calculate either the total or the average for each item and then multiply them together. At this time, the road width level 228 may also be added as an item to be multiplied.

After determining the road recovery priority as described above, the priority determination unit 113 stores the determined recovery priority 802 in the recovery priority information table 800 of the road in the priority storage database 124 as the recovery priority 802, and stores the road ID 701 in the road ID 801 in a form linked to the recovery priority. After storing all the recovery priorities 802, the priority determination unit 113 compares and ranks the recovery priorities 802, stores the rank as the recovery priority order 803, and proceeds to processing S1006.

In process S1006, the priority determination unit 113 obtains the output threshold information table 410 from the master database 121, and obtains the road restoration priority information table 800 from the priority storage database 124. The output threshold ID 411 to be used from the output threshold information table 410 may be set in advance by the user in the disaster response support system 100, or may be set by the user at any time via the input/output device 132.

Here, the priority determination unit 113 assigns an output level 413 to the road ID 801 whose recovery priority 802 in the road recovery priority information table 800 is equal to or greater than the priority threshold 412 in the output threshold information table 410, and proceeds to process S1007. Note that if multiple output levels 413 are assigned to the same road ID 801, the maximum output level 413 is assigned. Through this process, the output level for each road ID is determined.

In process S1007, the priority determination unit 113 calls the distribution unit 115, which outputs the road network for each output level to the input/output terminal 132, and the process proceeds to process S1008. In addition, the road network for each output level and the priority order is output to the road restoration planning system 160 as the priority order of road restoration requests from the perspective of material transportation, and the process proceeds to process S1008.

When outputting to the input/output terminal 132, the distribution unit 115 sets the base road network in advance as map data or the like, and displays roads that do not have a restoration plan listed in the road restoration priority information table 800 as roads with the highest probability of being usable as undamaged roads, and roads with restoration plans are displayed as damaged roads, and the way in which the probability is displayed is changed according to the output level for each road.

Alternatively, the distribution unit 115 may separately obtain probe information, which is the record of cars passing through the area after the disaster, from a car navigation service provider's system or the like, and perform the same processing (displaying roads with the probe information as the most likely roads) by treating roads with the probe information as roads that were not damaged by the disaster.

In process S1008, the priority determination unit 113 calls the distribution unit 115, which outputs information on the recommended delivery route to the input/output terminal 132, and the process proceeds to process S1009.

Specifically, for transportation in the transportation information table 620 of the collection/estimation database 122 where the value in the transportation completion 626 column indicates "0" (in transportation), the distribution unit 115 sets the supply facility with the transportation source ID 622 as the departure point and the demand base with the transportation destination ID 623 as the destination.

The distribution unit 115 also queries the shortest route search system 161 for the shortest route for the above-mentioned combination of departure point and destination, imposing a condition that roads with an output level equal to or higher than the output level previously set by the user be used for transportation, among the output levels allocated in process S1006.

In addition, the distribution unit 115 acquires the shortest route searched by the shortest route search system 161 and outputs this shortest route to the input/output terminal 132 as a recommended route for delivery.

In process S1009, the central processing unit 130 ends the process flow for determining the road restoration priority.

Next, examples of the output screens of the road recommendation screen output to the input device 132 in process S1007 of FIG. 10 and the route recommendation screen output to the input device 132 in process S1008 are shown.

Figure 11A is an example of a road recommendation screen 1100. The road recommendation screen 1100 shown in Figure 11A is a screen that recommends roads that are likely to be usable for transporting goods as roads to be used for delivery, and is a screen that is useful for delivery planning. This screen is displayed on the input/output device 132 of the disaster response support system 100.

The road recommendation screen 1100 shown in FIG. 11A is composed of a warehouse 1101, a base 1102, a recommended road network 1104, road damage α 1105, road damage β 1106, and a legend 1107. The warehouse 1101 indicates a supply facility, and in this example, there are three facilities: Warehouse A, Warehouse B, and Warehouse C.

Base 1002 indicates a demand base, and in this example there are three bases: base a, base b, and base c. Recommended road network 1104 indicates roads that are likely to be usable for transporting goods. The way in which roads are displayed changes depending on the degree of certainty that they can be used.

Road damage α1105 indicates the location where road damage has occurred. Road damage β1106 similarly indicates the location where road damage has occurred. In this example, road damage α1105 is considered to have a higher possibility of recovery than road damage β1106.

The legend 1107 shows how to view the recommended road network 1104, and in this example, the likelihood of using the roads is displayed in three levels of certainty. However, other display methods may be used if they are capable of displaying the recommended roads.

Figure 11B is an example of a route recommendation screen 1110. The route recommendation screen 1110 shown in Figure 11B is a screen that recommends delivery routes using roads that are highly likely to be usable, and is a screen that is useful for delivery planning. This screen is displayed on the input/output device 132 of the disaster response support system 100.

The route recommendation screen 1110 shown in FIG. 11B is composed of a warehouse 1111, a base 1112, a road network 1113, a route 1114, road damage α 1115, road damage β 1116, and a legend 1117. The screen is the same as FIG. 11A except for the road network 1113, the route 1114, and the legend 1117.

That is, warehouse 1111 indicates a supply facility. Base 1002 indicates a demand base. Road damage α1115 and road damage β1116 indicate locations where road damage has occurred, and road damage α1115 has a higher probability of recovery than road damage β1116.

On the other hand, road network 1113 shows all roads that can be envisioned in the delivery plan. However, it also includes roads that cannot be used due to damage caused by disasters. Route 1114 shows the delivery route when using roads that are likely to be usable for transporting goods. The delivery route includes roads that are currently unusable due to road damage and whose future restoration is not guaranteed, but which have a high possibility of being restored.

The legend 1117 shows how to view the recommended road network 1114, and in this example, it displays all roads that can be envisaged in the delivery plan and the recommended delivery route among them. However, other display methods may be used if it is possible to display the recommended delivery route using other display methods.

The above describes in detail the best mode for carrying out the present invention, but the present invention is not limited to this, and various modifications are possible without departing from the spirit of the present invention.

This embodiment makes it possible to respond to changes in the situation in disaster-stricken areas and efficiently provide appropriate information that contributes to planning road restoration and material transportation in those areas.

The description in this specification makes clear at least the following. That is, in the disaster response support method of this embodiment, the information processing device may identify the details of the disaster at each base based on the information on the damaged area and the location of each base, predict future state transitions in time series based on the details of the disaster at each base and the transition schedule, and estimate the state of supply or demand for materials at each base based on the results of the prediction and the operating status of each base at a specified time.

This makes it possible to efficiently estimate the state transition of supply and demand for materials at each base from a chronological perspective since the occurrence of the disaster. In turn, it becomes possible to more efficiently provide appropriate information that responds to changes in the situation in the disaster-stricken area and contributes to planning road restoration and material transportation in that area. Furthermore, in the disaster response support method of this embodiment, when the information processing device narrows down the target roads, it may specify the shortest route between the bases based on the location information, not the information of each base, and specify the road that is the shortest route and includes the damaged area as the target road.

This makes it possible to efficiently and accurately identify roads to be considered and apply them to subsequent processing, and ultimately to more efficiently provide appropriate information that contributes to road restoration and material transportation planning in the affected areas in response to changes in the situation in the affected areas.

In addition, in the disaster response support system of this embodiment, the computing device may identify the details of the disaster at each base based on the information on the damaged areas and the location of each base, and predict future state transitions in time series based on the details of the disaster at each base and the transition schedule, and estimate the state of supply or demand for materials at each base based on the results of the prediction and the operating status of each base at a specified time.

In addition, in the disaster response support system of this embodiment, the computing device may, when narrowing down the target roads, identify the shortest route between the bases based on the location information, not on the information of each base, and determine the road that is the shortest route and includes the damaged area as the target road.

100 Disaster response support system 110 Main memory device 111 Data collection unit 112 Data estimation unit 113 Priority determination unit 114 Other system calculation result acquisition unit 115 Distribution unit 120 Auxiliary memory device 121 Master database 122 Collection/estimation database 123 Other system calculation result database 124 Priority storage database 130 Central control device 131 Communication device 132 Input/output device 140 Communication line 150 Disaster countermeasure headquarters system 151 Disaster information sharing system 160 Road restoration planning system 161 Shortest route search system

Claims (4)

An information processing device,
storing information on each supply and demand base of a commodity, information on the importance of the commodity, and information on a road network in a region including each supply and demand base in a storage device;
the process of estimating a delivery route for the materials connecting the supply and demand bases based on the location of each base indicated by the information on each base and information on the road network; the process of specifying a delivery amount of the materials to be delivered between the bases at a predetermined time based on a transition schedule of each state of the supply or demand of the materials over time at each base indicated by the information on each base; the process of acquiring information on damaged areas in the road network from a predetermined external device that manages disaster information; the process of narrowing down target roads including the damaged areas among each road on the delivery route; the process of determining a recovery priority for the target road based on each piece of information including the length of the target road based on the information on the road network, the delivery amount of the materials specified based on information on the cargo transported on the target road, and the importance of the materials; and the process of outputting recommended information on the delivery route for the materials in an output form corresponding to the recovery priority ,
a process of identifying the content of the disaster at each base based on disaster occurrence information indicating the type and scale of the disaster in each region and the location of each base, which is obtained from the external device as information on the damaged area, and predicting future state transitions in time series based on the content of the disaster at each base and the transition schedule; and estimating the state of supply or demand for materials at each base based on the operating status of each base at a specified time based on the results of the prediction;
A disaster response support method comprising: The information processing device,
In the process of narrowing down the target roads, the shortest route between the bases is identified based on the location information, not the information of each base, and the road that is the shortest route and includes the damaged area is identified as the target road.
The disaster response support method according to claim 1 . a storage device for storing information on each supply and demand base of a commodity, information on the importance of the commodity, and information on a road network in an area including each supply and demand base;
A process of estimating a delivery route for the materials connecting the supply and demand bases based on the location of each base indicated by the information on each base and information on the road network; a process of specifying a delivery amount of the materials to be delivered between the bases at a predetermined time based on a transition schedule of each state of the supply or demand of the materials over time at each base indicated by the information on each base; a process of acquiring information on areas damaged by the disaster in the road network from a predetermined external device that manages disaster information; a process of narrowing down target roads that include the damaged areas among each road in the delivery route; and a process of, with respect to the target roads, determining the length of the target road based on the information on the road network and information on the cargo to be transported on the target road. a process of determining a recovery priority based on information on the delivery volume of the material and the importance of the material, and a process of outputting recommended information on the delivery route of the material in an output form according to the recovery priority , wherein the process of specifying the content of the disaster at each base based on disaster occurrence information indicating the type and scale of the disaster in each region and the location of each base, obtained from the external device as information on the damaged area, and predicting future state transitions in time series based on the content of the disaster at each base and the transition schedule; and a calculation device that estimates the state of supply or demand of materials at each base based on the operating status of each base at a specified time based on the results of the prediction.
A disaster response support system comprising: The computing device,
In the process of narrowing down the target roads, the shortest route between the bases is specified based on the location information, not on the information of each base, and the road that is the shortest route and includes the damaged area is set as the target road.
4. The disaster response support system according to claim 3 .

Images