JP2023103702A - Computer system and allocation method for business in response to disaster - Google Patents

Abstract

To support cooperation of operations between organizations in a disaster.SOLUTION: A computer system is connected to terminals managed by a plurality of organizations executing businesses in response to disasters, and the terminals transmit the site information on a site of the disaster and the activity information on at least one of the executed businesses. The computer system includes the steps of: specifying a state of the site based on the site information; specifying the allocation work required to be executed based on the state of the site; grasping an activity state of the organization based on the activity information; determining the organization capable of executing the allocation work based on the activity state of the organization; and transmitting the execution request of the determined organization allocation work.SELECTED DRAWING: Figure 1

Description

TECHNICAL FIELD The present invention relates to a technique for supporting smooth inter-organizational cooperation at a disaster response site where a plurality of vertically divided organizations participate in operations when a disaster occurs.

Many organizations carry out a wide range of activities during a disaster. In order to improve the efficiency of activities during a disaster, it is necessary to share the status of the organization that is conducting the activity and the information that the organization possesses among the organizations, and to grasp the overall picture of the activity from the shared information.

However, since the organization that carries out the activities is a vertical organization, it is difficult to grasp the status of other organizations and to cooperate with other organizations. In addition, the functions (resources) required for different purposes, such as support for medical activities, clearing roads, and support for the supply of goods, differ depending on the purpose, and the state of the organization changes from moment to moment. situation may occur. As mentioned above, due to insufficient cooperation between organizations, it is later discovered that the work is not being carried out, and the response is delayed.

Techniques described in Patent Literature 1 and Patent Literature 2 are known as techniques for solving the above-described problems.

In Patent Document 1, "In order to distribute information necessary for decision-making from the decision-making support device 101 to various terminals (130, 140, 150, 160) via the network 129, an event that causes decision-making is detected by the event management unit 109, task (business) assignment and information to be notified according to the event are stored in each information managed by the information correlation management unit 111 according to the event (and the situation accompanying it) It describes "determining using the correlation" and "distributing the determined information to various terminals via the interface unit 117".

In Patent Document 2, "At the time of new and related forms, the crisis response business management support server SV generates a record ID that identifies a task, a task ID (Task-ID) that identifies a group of tasks, and a related Generates an ID (Org-ID) that indicates the relationship with the task that is the source of the request when issuing a request, and layer information that indicates the generation of each task in the task group in a hierarchical manner, and adds this to the request information. are stored in the activity log storage unit 32. Then, when displaying a list of the tasks for each task group, the task response statuses are arranged in chronological order and displayed. degree is calculated, and the calculated bottleneck degree is added to the task data list and displayed."

JP 2013-088829 A JP 2016-224671 A

The technology described in Patent Literature 1 does not take into consideration whether or not work can be performed in a chaotic site. The technology described in Patent Literature 2 is based on the premise that each organization reports on the work it is doing. However, depending on the situation at the site, it may not be possible to report. The work that is not reported is highly urgent and should be managed by the system.

In this way, the prior art does not assume that reports regarding assignment work and non-regular work performed according to the site will be missing, and will not function properly if information is missing.

An object of the present invention is to grasp the situation of the site from information that can be obtained in pieces from the site, and to plan the tasks to be assigned to each organization, thereby supporting the coordination of tasks between organizations in the event of a disaster.

A representative example of the invention disclosed in the present application is as follows. That is, a computer system including at least one computer having a processor, a storage device connected to the processor, and a network interface connected to the processor, and a terminal managed by a plurality of organizations that execute tasks against disasters. , the terminals of the plurality of organizations transmit site information related to the site of the disaster and activity information related to at least one of the work performed, and the at least one computer performs site information based on the acquired site information. Identify the state, identify the assignment work that needs to be performed based on the identified site state, grasp the activity state of the plurality of organizations based on the acquired activity information, and determine the status of the plurality of organizations. An organization capable of executing the assigned task is determined based on the activity status, and a request for performing the assigned task is sent to the determined organization.

According to the present invention, on-site conditions can be grasped based on information that can be obtained in pieces from the on-site, and assignment of tasks to organizations can be planned. As a result, it is possible to support coordination of operations between organizations in the event of a disaster. Problems, configurations, and effects other than those described above will be clarified by the following description of the embodiments.

1 is a diagram illustrating an example of a system configuration of Example 1; FIG. 2 is a diagram illustrating an example of the hardware configuration of the business management support device of Example 1; FIG. 4 is a diagram showing an example of the data structure of business issuance condition information of Example 1. FIG. 4 is a diagram showing an example of the data structure of business manual information in Example 1. FIG. 4 is a diagram illustrating an example of the data structure of possessed resource information in Example 1. FIG. 4 is a diagram showing an example of the data structure of organization management information of Example 1. FIG. 4 is a diagram showing an example of the data structure of object management information of Example 1. FIG. FIG. 2 is a diagram illustrating correspondence relationships among task issuing condition information, task manual information, possessed resource information, organization management information, and object management information according to the first embodiment; FIG. 10 is a diagram showing an example of the data structure of accuracy calculation logic information according to the first embodiment; 4 is a diagram showing an example of the data structure of messages accumulated by the messaging system of embodiment 1; FIG. 4 is a diagram showing an example of the data structure of messages accumulated by the messaging system of embodiment 1; FIG. 4 is a diagram showing an example of the data structure of messages accumulated by the messaging system of embodiment 1; FIG. 4 is a diagram showing an example of the data structure of messages accumulated by the messaging system of embodiment 1; FIG. 4 is a diagram showing an example of the data structure of site state information in Example 1. FIG. FIG. 3 is a diagram showing an example of the data structure of assigned work information in Example 1; 4 is a diagram illustrating an example of the data structure of estimated work information in Example 1; FIG. 7 is a flowchart illustrating an example of site state confirmation processing executed by a state monitoring unit of the business management support device of the first embodiment; 8 is a flowchart illustrating an example of processing executed by an allocation unit according to the first embodiment; 8 is a flowchart illustrating an example of processing executed by an allocation unit according to the first embodiment; 7 is a flow chart illustrating an example of processing executed by an allocation work management unit according to the first embodiment; 7 is a flowchart illustrating an example of processing executed by an estimating unit according to the first embodiment; 7 is a flowchart illustrating an example of processing executed by an estimation work management unit according to the first embodiment; 4 is a diagram showing an image of internal processing of the business management support device according to the first embodiment; FIG. 4 is a diagram showing the flow of messages between the business management support device and the messaging system of Example 1; FIG. FIG. 5 is a diagram illustrating an example of a screen presented on the terminal of Example 1;

Hereinafter, embodiments of the present invention will be described with reference to the drawings. However, the present invention should not be construed as being limited to the contents of the examples described below. Those skilled in the art will easily understand that the specific configuration can be changed without departing from the idea or gist of the present invention.

In the configurations of the invention described below, the same or similar configurations or functions are denoted by the same reference numerals, and overlapping descriptions are omitted.

The notations such as “first”, “second”, “third”, etc. in this specification and the like are attached to identify the constituent elements, and do not necessarily limit the number or order.

The position, size, shape, range, etc. of each component shown in the drawings may not represent the actual position, size, shape, range, etc. in order to facilitate understanding of the invention. Therefore, the present invention is not limited to the positions, sizes, shapes, ranges, etc. disclosed in the drawings and the like.

FIG. 1 is a diagram showing an example of the system configuration of the first embodiment. FIG. 2 is a diagram illustrating an example of the hardware configuration of the business management support device 100 according to the first embodiment.

As shown in FIG. 1, the system comprises a business management support device 100, a messaging system 101, and a terminal 102. FIG. A business management support device 100 , a messaging system 101 , and a terminal 102 are interconnected via a network 105 .

The terminal 102 is a terminal managed by an organization that conducts business in the event of a disaster. The terminal 102 is, for example, a personal computer, a smart phone, or the like. FIG. 1 shows terminals 102 of three organizations. Note that the present invention is not limited to the type and number of terminals 102 . The terminal 102 has a function of registering in the messaging system 101 information on active/inactive states, activity logs such as communication with other terminals 102, information on disaster situations, and the like. Also, the terminal 102 can acquire a message from the messaging system 101 and transmit a response message corresponding to the acquired message to the messaging system 101 .

The messaging system 101 is a system that implements a message queue. The messaging system 101 holds and relays information between the business management support device 100 and the terminal 102 as messages.

The messaging system 101 has a message input/output unit 140 and manages a site status queue 150 , an organization status queue 151 , an assigned task queue 152 and an estimated task queue 153 .

The site status queue 150 includes information about site conditions, such as weather and river conditions (e.g., flooding of rivers), lifeline conditions (e.g., power outages), medical facility conditions, and scale and extent of damage. Store message 1000 (see FIG. 10A). Organization status queue 151 stores messages 1010 (see FIG. 10B) containing information about the activity status of the organization. The assigned work queue 152 accumulates messages 1020 (see FIG. 10C) including information on work requested by the work management support device 100 . The estimated work queue 153 accumulates messages 1030 (see FIG. 10D) containing information about work that is estimated by the work management support device 100 to be performed by any organization.

The message input/output unit 140 registers messages in each queue and reads messages from each queue. When accumulating messages in the queue, the message input/output unit 140 converts information received from the terminal 102 or the like into a message in a predetermined format, and registers the message.

(Example 1) When a table containing 100 entries consisting of "road name" and "passability status" is received from the terminal 102, the message input/output unit 140 receives the time at which the table was sent, the "road name , and 100 messages 1000 composed of 'passability status' are generated and registered in the field status queue 150 . Note that in the above example, data in table format is converted into a message, but the present invention is not limited to this. The data format of the received information may be JSON format, XML format, or the like.

(Example 2) From the terminal 102, 100 entries consisting of a "medical facility name" field and 30 fields representing states such as "power status", "water supply status", and "clothes holding status" are generated. When receiving a table for storing 30 messages, the message input/output unit 140 generates 30 messages 1000 including field values of each state for one entry. The message input/output unit 140 registers 3000 messages 1000 in the field status queue 150 . Note that in the above example, data in table format is converted into a message, but the present invention is not limited to this. The data format of the received information may be JSON format, XML format, or the like.

(Example 3) The message input/output unit 140 checks the communication status of the terminal 102 or whether or not there is a response, generates a message 1010 including the confirmation result, and registers the message in the organizational status queue 151 .

The business management support device 100 grasps the situation of the site based on the information acquired from the terminal 102 via the messaging system 101, and estimates the business that may be performed. In addition, the business management support device 100 grasps the state of the organization based on the information acquired from the terminal 102 via the messaging system 101, identifies the business that needs to be performed, and determines the organization that requests the implementation of the business. and requests the organization to carry out the work via the messaging system 101 .

The business management support device 100 is, for example, a computer having a hardware configuration as shown in FIG. The business management support device 100 has a processor 201 , a main storage device 202 , a secondary storage device 203 and a network interface 204 . The business management support device 100 may have an input device and an output device.

The processor 201 executes programs stored in the main memory device 202 . The processor 201 operates as a functional unit (module) that implements a specific function by executing processing according to a program. In the following description, when processing is described with a functional unit as the subject, it means that the processor 201 is executing a program that implements the functional unit.

The main storage device 202 is a memory or the like, and stores programs executed by the processor 201 and data used by the programs. The secondary storage device 203 is a HDD (Hard Disk Drive), an SSD (Solid State Drive), or the like, and permanently stores data. The programs and data stored in the main storage device 202 may also be stored in the secondary storage device 203 . In this case, processor 201 reads programs and data from secondary storage device 203 and loads them into main storage device 202 . A network interface 204 communicates with other devices over a network.

The processor 201 of this embodiment operates as a task allocation unit 110 , a task estimation unit 111 , a state monitoring unit 112 and a manual selection unit 113 . The main storage device 202 of this embodiment contains task issuing condition information 130, task manual information 131, possessed resource information 132, organization management information 133, object management information 134, probability calculation logic information 135, site state information 136, assigned task information. 137 and estimated business information 138 are stored.

The task issuing condition information 130 stores information for specifying task execution conditions and tasks. The details of the data structure of the task issuing condition information 130 will be described with reference to FIG.

The business manual information 131 stores business manuals. A business manual is information that describes the organization and functions that carry out business. As will be described later, the work manual information 131 stores a work manual for each type of disaster. Details of the data structure of the work manual information 131 will be described with reference to FIG.

The owned resource information 132 stores information about resources used for business owned by the organization. Details of the data structure of the possessed resource information 132 will be described with reference to FIG.

The organization management information 133 stores information about organizations belonging to the organization category. The details of the data structure of the organization management information 133 will be explained using FIG.

The object management information 134 stores information about objects belonging to the object category. The details of the data structure of the object management information 134 will be explained using FIG.

The probability calculation logic information 135 stores information on the logic for calculating the probability representing the plausibility of the estimated business. The details of the data structure of the accuracy calculation logic information 135 will be explained using FIG.

Site state information 136 stores messages 1000 received via site state queue 150 . The details of the data structure of the site state information 136 will be described with reference to FIG.

The assigned work information 137 stores information about the work requested by the work management support device 100 to be performed. The details of the data structure of the assigned work information 137 will be described with reference to FIG.

The estimated work information 138 stores information related to work estimated by the work management support device 100 . The details of the data structure of the estimated work information 138 will be explained using FIG.

The task assignment unit 110 identifies tasks that need to be performed according to the site conditions, and assigns the tasks to organizations capable of performing the tasks. In this embodiment, the business management support device 100 does not actively allocate the business, but requests the organization to implement the business via the message queue. The execution of duties is entrusted to the judgment of the organization. The work allocation unit 110 includes an allocation unit 120 and an allocation work management unit 121 . The allocation unit 120 specifies the work and requests the organization to carry out the work. The allocation task management unit 121 monitors the progress of the task requested to be performed, and requests the task to be performed again if the task has not been executed.

The task estimation unit 111 estimates tasks that may have been performed on site. The work estimation unit 111 includes an estimation unit 122 and an estimation work management unit 123 . The estimating unit 122 estimates work that may have been performed on site. The estimation task management unit 123 monitors the execution result of the estimation task and calculates the accuracy of the estimation task.

The state monitoring unit 112 monitors messages accumulated in the field state queue 150 , the organizational state queue 151 , the assigned work queue 152 , and the estimated work queue 153 . The status monitoring unit 112 registers the message 1000 registered in the field status queue 150 by the organization in the site status information 136, registers the message 1020 registered in the assigned task queue 152 by the organization in the assigned task information 137, The message 1030 registered in the estimated work queue 153 is registered in the estimated work information 138 . The status monitoring unit 112 identifies the status of the site based on the site status information 136, and assigns and estimates work according to the status of the site. Also, the state monitoring unit 112 registers messages in each queue via the message input/output unit 140 .

The manual selection unit 113 selects a business manual to be used from among the business manuals stored in the business manual information 131 . The manual selection unit 113 may automatically determine the work manual based on the content of the message 1000 stored in the field status queue 150, or may determine the work manual based on the input of the user who operates the work management support device 100. good too. The manual selection unit 113 may dynamically switch the work manual to be used according to the site conditions.

For example, if a message 1000 meaning "typhoon approaching" is stored, a work manual for wind and flood damage is selected, and if a message 1000 meaning "earthquake occurs" is stored, a work manual for earthquake disaster is selected. selected. Further, when the update frequency of the field status queue 150 is low, the manual selection unit 113 determines that it is normal time, and selects a work manual for normal time.

As for each function unit of the business management support apparatus 100, a plurality of function units may be combined into one function unit, or one function unit may be divided into a plurality of function units for each function.

Note that the functional units of the business management support device 100 may be implemented using a computer system including a plurality of computers. In this case, the functional units may be distributed in each computer.

FIG. 3 is a diagram showing an example of the data structure of the business issuance condition information 130 according to the first embodiment.

The job issuing condition information 130 stores a table 300 as shown in FIG. Table 300 stores entries including site conditions 301 and objectives 302 . There is one entry for the issuance conditions of one transaction. It should be noted that the fields included in the entry are just examples and are not limited to these.

The site status 301 is a field group that stores information about the site status corresponding to the job execution conditions, and includes an object category 311 and a condition 312 . The object category 311 is a field that stores an object category for identifying the type of site. Condition 312 is a field that stores the status of objects belonging to the object category. If the state of the object satisfies the conditions stored in condition 312, the transaction will be performed. Objective 302 is a field that stores the objective of improving site conditions.

Note that the job issuing condition information 130 may store a table 300 for each type of disaster. The information stored in the job issuing condition information 130 may be in a data format other than the table format.

FIG. 4 is a diagram showing an example of the data structure of the work manual information 131 of the first embodiment.

The work manual information 131 stores a table 400 as shown in FIG. 4 for each type of disaster. Table 400 stores entries including purpose 401 , effect 402 , business 403 , organizational category 404 , and function 405 . There is one entry for one purpose. It should be noted that the fields included in the entry are just examples and are not limited to these.

Purpose 401 is the same field as Purpose 302 . The effect 402 is a group of fields that store information about the effect of business execution, and includes an object category 411 and a change 412 . Object Category 411 is the same field as Object Category 311 . A change 412 is a field that stores the change of the object due to the execution of the work.

A task 403 is a field for storing tasks to be performed to achieve a purpose. One or more tasks exist for one purpose. One entry includes lines each composed of a task 403, an organization category 404, and a function 405, as many as the number of tasks. The organization category 404 is a field that stores categories of organizations that can carry out business. A function 405 is a field for storing the functions necessary for executing the business.

Information stored in the work manual information 131 may be in a data format other than the table format.

FIG. 5 is a diagram showing an example of the data structure of the possessed resource information 132 of the first embodiment.

The owned resource information 132 stores a table 500 as shown in FIG. Table 500 stores entries including organization 501 and function 502 . There is one entry for one organization. It should be noted that the fields included in the entry are just examples and are not limited to these.

Organization 501 is a field for storing organization identification information. A function 502 is a group of fields that store information on resources for each function required for executing business. Functions 502 include fields such as route 511, transport 512, vehicle removal 513, decision 514, and report 515, for example. Each field stores a resource that implements a function. The route 511 stores roads, rivers, airports, etc., which are used for transportation of goods or movement of support units and which are managed by the organization. Transport 512 stores ambulances, helicopters, and the like used for transport and managed by the organization.

Note that the owned resource information 132 may store a table 500 for each type of disaster. Information stored in the owned resource information 132 may be in a data format other than the table format.

FIG. 6 is a diagram showing an example of the data structure of the organization management information 133 of the first embodiment.

The organization management information 133 stores a table 600 as shown in FIG. Table 600 stores entries including organization category 601 and organization 602 . There is one entry for each organizational category. It should be noted that the fields included in the entry are just examples and are not limited to these.

Organization Category 601 is the same field as Organization Category 404 . Organization 602 is a field that stores organizations belonging to the organization category. Organization 602 contains as many rows as there are organizations.

If there is only one organization belonging to the category of organization, the category of organization and the organization are assumed to match. Information stored in the organization management information 133 may be in a data format other than the table format.

FIG. 7 is a diagram showing an example of the data structure of the object management information 134 according to the first embodiment.

The object management information 134 stores a table 700 as shown in FIG. Table 700 stores entries including object category 701 and object 702 . There is one entry for one object category. It should be noted that the fields included in the entry are just examples and are not limited to these.

Object Category 701 is the same field as Object Category 311 . An object 702 is a field that stores objects belonging to the object category. The object 702 contains as many rows as there are objects.

Note that the entry may include fields for storing location information (eg, longitude and latitude) of roads, shelters, ports, and the like. Information stored in the object management information 134 may be in a data format other than the table format.

FIG. 8 is a diagram for explaining the correspondence relationship among the task issuing condition information 130, task manual information 131, possessed resource information 132, organization management information 133, and object management information 134 of the first embodiment.

When the state monitoring unit 112 detects that the state of "prefectural road A" has changed from "passable" to "passable", the state monitoring unit 112 refers to the object management information 134 based on the object "prefectural road A". , it can be grasped that the object category "road" has become "impassable". Furthermore, the state monitoring unit 112 refers to the work issuing condition information 130 and determines that it is necessary to carry out the work for achieving the "opening of the road". As shown in FIG. 8, the status monitoring unit 112 performs task assignment or task estimation by following links of task issuing condition information 130, task manual information 131, organization management information 133, and possessed resource information 132. FIG.

When the state monitoring unit 112 detects that the state of "prefectural road A" has changed from "passable" to "passable", the state monitoring unit 112 refers to the object management information 134 based on the object "prefectural road A". , it can be understood that the object category "road" has become "passable". Furthermore, the status monitoring unit 112 can grasp that the work for achieving the "opening of the road" has been carried out through the work manual information 131. FIG.

FIG. 9 is a diagram showing an example of the data structure of the accuracy calculation logic information 135 of the first embodiment.

The accuracy calculation logic information 135 stores a table 900 as shown in FIG. The table 900 stores entries including accuracy calculation conditions 901 and accuracy 902 . There is one entry for one condition. It should be noted that the fields included in the entry are just examples and are not limited to these.

The accuracy calculation condition 901 is a field that stores accuracy calculation conditions. The accuracy 902 is a field that stores the accuracy when the condition set in the accuracy calculation condition 901 is satisfied. Although four types of accuracy are defined in this embodiment, the number of accuracy may be three or less, or may be more than four.

Information stored in the accuracy calculation logic information 135 may be in a data format other than the table format.

In addition to the table 900, the accuracy calculation logic information 135 also includes information on formulas for calculating integrated accuracy. A formula is given, for example, by formula (1). Here, n _i represents the number of estimation jobs with certainty i (i is 1, 2, 3, 4), and w _i represents the weight.

With w ₁ , w ₂ , w ₃ , and w ₄ all set to 1, there are three estimated tasks with different “notifying organization”, “time”, and “object” but with the same “task category”. When there is one estimation task with a value of "1" and two estimation tasks with an accuracy of "2", the total accuracy is 3 as shown in equation (2).

The value of _wi is determined by the degree of cooperation, that is, how carefully the organization managed by the business management support device 100 responds to the business.

(Setting method 1) When reliable reporting is expected, set w1 to ₁ , _w2 to 2, _w3 to 3, and _w4 to 4. By increasing the weight of an estimated task with a high degree of accuracy, an estimated task related to a task for which the result of estimation by the task estimation unit 111 matches the task assigned by the task allocation unit 110 is emphasized.

(Setting method 2) If the organization is not cooperative and reliable reporting cannot be expected, even if the estimation result of the business estimation unit 111 is slightly wrong, the accuracy of the estimation increases by increasing the number of estimations. There is expected. Therefore, it may be optimal to set w ₁ , w ₂ , w ₃ , and w ₄ all to 1 and treat low-probability estimation tasks the same as high-probability estimation tasks.

If Ministry A carries out work and there are three estimation works with an accuracy of "4", the total accuracy of setting method 1 is 12 as shown in equation (3), and the total accuracy of setting method 2 is the equation It becomes 3 as shown in (4).

If Ministry B carries out the work, and there are five estimation jobs with an accuracy of "1" and two estimation jobs with an accuracy of "3", the overall accuracy of setting method 1 is shown in formula (5). Thus, the total accuracy of setting method 2 is 7 as shown in equation (6).

Therefore, in the case of setting method 2, it is highly likely that Ministry B performed the estimation work, and in the case of setting method 1, it means that the possibility that Ministry A performed the estimation work is high.

10A, 10B, 10C, and 10D are diagrams showing an example of the data structure of messages accumulated by the messaging system 101 of the first embodiment.

Messages stored in messaging system 101 include at least one key-value pair.

A message 1000 shown in FIG. 10A is a message stored in the site status queue 150, and includes "time", "object", and "status" as keys. The key "object" is the type of site, and the "state" is the state of the site.

A message 1010 shown in FIG. 10B is a message stored in the organization status queue 151, and includes "time", "organization", "status", and "communication partner" as keys. The key "organization" is the organization that registered the message, the key "state" is the state of the organization, and the key "communication party" is the party with which the organization is communicating.

A message 1020 shown in FIG. 10C is a message stored in the assigned task queue 152, and has keys of "time", "purpose", "task", "object", "requesting organization", "status", and "update including “person”. The key "purpose" is the purpose of improving the site conditions, the key "work" is the work to be performed, the key "requesting organization" is the organization that requests the work to be performed, and the "status" is the work implementation status. and the "updated by" is the subscriber of the message.

A message 1030 shown in FIG. 10D is a message stored in the estimated work queue 153, and has keys of "time", "purpose", "work", "object", "function", "implementation organization", and "accuracy". , and “notified organizations”. The key "time" is the estimated time period during which the work was performed, the key "purpose" is the purpose of improving the site conditions, the "work" is the estimated work, and the key "function" is the execution of the work. The key "performing organization" is the organization that is presumed to have performed the work, the key "accuracy" is the accuracy of the estimated work, and the "notifying organization" is the organization that notified the completion of the work. be.

FIG. 11 is a diagram showing an example of the data structure of the site state information 136 according to the first embodiment.

The field state information 136 stores a table 1100 as shown in FIG. Table 1100 stores entries including time 1101 , object 1102 , and state 1103 . There is one entry for one message 1000 .

A time 1101 is a field that stores the value of the key “time” of the message 1000 . An object 1102 is a field that stores the value of the key 'object' of the message 1000 . A state 1103 is a field that stores the value of the key “state” of the message 1000 .

Information stored in the field state information 136 may be in a data format other than the table format.

The state monitoring unit 112 acquires the message 1000 when it detects that the new message 1000 has been registered in the site state queue 150 . The state monitoring unit 112 refers to the field state information 136 and searches for an entry in which the value of the key “object” of the acquired message 1000 is stored in the object 1102 . If the corresponding entry does not exist, the status monitoring unit 112 adds an entry to the field status information 136 and sets the value of each key included in the message 1000 in each field of the added entry. If the corresponding entry exists, the state monitoring unit 112 sets the values of the key “time” and the key “state” included in the message 1000 to the time 1101 and state 1103 of the entry. Thereby, the business management support device 100 can grasp the latest state of each site.

FIG. 12 is a diagram showing an example of the data structure of the assigned work information 137 of the first embodiment.

The assigned work information 137 stores a table 1200 as shown in FIG. Table 1200 stores entries including time 1201 , purpose 1202 , task 1203 , object 1204 , requesting organization 1205 , status 1206 , and updater 1207 . There is one entry for one message 1020 .

A time 1201 is a field that stores the value of the key “time” of the message 1020 . Purpose 1202 is a field that stores the value of the key “purpose” of message 1020 . A business 1203 is a field that stores the value of the key “business” of the message 1020 . An object 1204 is a field that stores the value of the key 'object' of the message 1020 . A requesting organization 1205 is a field that stores the value of the key “requesting organization” of the message 1020 . State 1206 is a field that stores the value of the key “state” of message 1020 . An updated by 1207 is a field that stores the value of the key “updated by” of the message 1020 .

The information stored in the assigned work information 137 may be in a data format other than the table format.

The state monitoring unit 112 acquires the message 1020 when it detects that the new message 1020 has been registered in the assigned task queue 152 . The status monitoring unit 112 refers to the assigned task information 137 and searches for an entry in which the combination of the values of the task 1203 and the object 1204 matches the combination of the values of the key “task” and the key “object” of the message 1020 . If the corresponding entry does not exist, the state monitoring unit 112 adds an entry to the assigned work information 127 and sets the value of each key included in the message 1020 in each field of the added entry. If the corresponding entry exists, the status monitoring unit 112 adds the key "time", the key "requesting organization", the key Set the value of "state" and key "updated by". Thereby, the business management support device 100 can grasp the latest implementation status of the business for which implementation is requested.

FIG. 13 is a diagram illustrating an example of the data structure of estimated work information 138 according to the first embodiment.

The estimated work information 138 stores a table 1300 as shown in FIG. Table 1300 includes Task 1301 , Object 1302 , Purpose 1303 , Time 1304 , Performing Organization 1305 , Function 1306 , Probability 1307 , and Notification Organization 1308 .

A business 1301 is a field that stores the value of the key “business” of the message 1030 . An object 1302 is a field that stores the value of the key 'object' of the message 1030 . Purpose 1303 is a field that stores the value of the key “purpose” of message 1030 . A time 1304 is a field that stores the value of the key “time” of the message 1030 . Implementation organization 1305 is a field that stores the value of the key “implementation organization” of message 1030 . Capability 1306 is a field that stores the value of the key “capability” of message 1030 . Confidence 1307 is a field that stores the value of the message 1030 key “confidence”. Notification Organization 1308 is a field that stores the value of the key “Notification Organization” of message 1030 .

The state monitoring unit 112 acquires the message 1030 when it detects that a new message 1030 has been registered in the estimated job queue 153 . The state monitoring unit 112 refers to the estimated task information 138 and searches for an entry in which the combination of the values of the task 1301 and the object 1302 matches the combination of the values of the key “task” and the key “object” of the message 1030 . If the corresponding entry does not exist, the state monitoring unit 112 adds an entry to the estimated work information 138 and sets the value of each key included in the message 1030 in each field of the added entry. Note that the accuracy 1307 is set to “1”. If a corresponding entry exists, the state monitoring unit 112 sets the values of the key "time" and the key "implementation organization" included in the message 1030 to the time 1304 and implementation organization 1305 of the entry. Thereby, the business management support device 100 can grasp the latest execution state of the estimated business.

FIG. 14 is a flowchart for explaining an example of site state confirmation processing executed by the state monitoring unit 112 of the business management support device 100 of the first embodiment.

The state monitoring unit 112 starts monitoring the message queue after the business management support device 100 is activated. In monitoring the site status queue 150, the following processing is periodically executed. Note that the execution cycle can be set arbitrarily. For example, if the execution cycle is 1 minute and the count starts at 18:00, the status monitoring unit 112 refers to the site status queue 150 at 18:01, and the field status queue 150 is registered between 18:00 and 18:01. It is determined whether or not there is a message 1000 that has been received.

The state monitoring unit 112 determines whether or not the new message 1000 is registered in the site state queue 150 (step S101).

If the new message 1000 is not registered, the status monitor 112 continues monitoring the site status queue 150 .

If the new message 1000 is registered, the processes from step S102 onward are executed. Note that the processing from step S102 onward is executed for one new message 1000. FIG. In other words, when there are a plurality of new messages 1000, the processes from step S102 onward are executed for each message 1000. FIG.

The state monitoring unit 112 refers to the site state information 136, stores the value of the key 'object' of the new message 1000 in the object 1102, and stores the value of the key 'state' of the new message 1000 in the state 1103. An entry is searched (step S102), and it is determined whether or not the entry exists (step S103). If an entry exists, there is a high possibility that work has already been carried out according to the site conditions, so work is estimated. On the other hand, if the entry does not exist, there is a high possibility that the work corresponding to the situation at the site has not been performed, and therefore a work execution request is made.

If the entry exists, the state monitoring unit 112 refers to the work manual information 131, searches for work that can be done (step S104), and determines whether or not there is work that can be done (step S105).

Specifically, the state monitoring unit 112 refers to the object management information 134 based on the value of the key "object" of the message 1000, and converts the value into an object category. The status monitoring unit 112 determines whether or not there is an executable task by comparing the value of the object category and the key “status” with the value of the effect 402 of each entry in the table 400 . It is assumed that information defining relationships between states and state changes exists in advance.

If there is no work that can be performed, the status monitor 112 continues monitoring the site status queue 150 .

If there is work that can be performed, the status monitoring unit 112 generates an estimated work message 1030 based on the entry retrieved in step S104 (step S106), and calls the work estimation unit 111 (step S107). After that, the status monitoring unit 112 continues monitoring the site status queue 150 .

Specifically, the state monitoring unit 112 acquires the value of the business 403 of the entry searched in step S104. Status monitor 112 generates message 1030 for each value (each task). The value of the purpose 401 of the entry is set to the key "Purpose" of the message 1030, the value of the job 403 is set to the key "Business", and the value of the function 405 is set to the key "Function". The key "time", the key "implementation organization", and the key "probability" of the message 1030 are blank. The state monitoring unit 112 calls the business estimation unit 111 and outputs a message 1030 .

If the entry does not exist in step S103, the state monitoring unit 112 refers to the job issuance condition information 130, searches for work that can be performed (step S108), and determines whether or not there is work that can be performed (step S108). step S109).

Specifically, the state monitoring unit 112 refers to the object management information 134 based on the value of the key "object" of the message 1000, and converts the value into an object category. The status monitoring unit 112 compares the value of the object category and the key “status” with the value of the field status 301 of the table 300 to determine whether or not there is an executable task.

If there is no work that can be performed, the status monitor 112 continues monitoring the site status queue 150 .

If there is work that can be executed, the status monitoring unit 112 generates a message 1020 of the allocated work based on the entry retrieved in step S105 (step S110), and calls the work allocation unit 110 (step S111). After that, the status monitoring unit 112 continues monitoring the site status queue 150 .

Specifically, the state monitoring unit 112 acquires the value of the purpose 302 of the entry searched in step S108. The status monitoring unit 112 refers to the work manual information 131 and searches for an entry in which the acquired value is stored in the purpose 401 . The status monitoring unit 112 acquires the value of the task 403 of the retrieved entry. The status monitor 112 generates a message 1020 for each value (each task). The value of the entry purpose 401 is set to the key "purpose" of the message 1020, the value of the task 403 is set to the key "business", and the value of the key "object" of the message 1000 is set to the key "object". The value of the key "notifying organization" of the message 1000 is set to the key "requesting organization". The key "state" and the key "updated by" of the message 1020 are blank. The status monitoring unit 112 calls the job assignment unit 110 and outputs a message 1020 .

Next, processing executed by the task assignment unit 110 will be described with reference to FIGS. 15A, 15B, and 16. FIG.

15A and 15B are flowcharts illustrating an example of processing executed by the allocation unit 120 according to the first embodiment.

When called by the state monitoring unit 112, the allocation unit 120 executes processing described below.

The allocation unit 120 acquires the message 1020 output by the state monitoring unit 112 (step S201). The allocation unit 120 sets the organization corresponding to the key "requesting organization" of the message 1020 as the target organization.

The allocation unit 120 checks the status of the target organization (step S202), and determines whether or not the target organization can perform the task corresponding to the message 1020 (step S203).

Specifically, the assigning unit 120 refers to the organization status queue 151, and the value of the target organization is stored in the key "organization", and the value of the key "time" is included in the time range a certain time before the current time. Search for the message 1010 that is The range of time to search can be arbitrarily set to 1 minute, 30 minutes, 1 hour, or the like. If message 1010 does not exist, allocation unit 120 determines that the target organization can perform the task. If the value of the key "state" of the retrieved message 1010 is "communication blocked" or "no response", etc., the assigning unit 120 determines that the target organization cannot perform the task.

If the target organization can perform the work corresponding to the message 1020, the allocation unit 120 sets the target organization to the key "requesting organization" of the message 1020 (step S211), and assigns the entry corresponding to the message 1020 to the allocation work information 137. (step S213). After that, the allocation unit 120 terminates the processing.

If the target organization cannot perform the work corresponding to the message 1020, the allocation unit 120 refers to the estimated work information 138, searches for an estimated work having the same content as the work corresponding to the message 1020 (step S204), It is determined whether or not there is an estimated task having the same content as the corresponding task (step S205).

Specifically, the assignment unit 120 determines that the combination of the values of the task 1301 and the purpose 1303 matches the combination of the values of the key "task" and the key "purpose" of the message 1020, and the key "time" of the message 1020. The value of is included in the time range corresponding to time 1304 is retrieved.

If there is no presumed task having the same content as the task corresponding to the message 1020, the assigning unit 120 sets the key "requesting organization" of the message 1020 to "all organizations" (step S212), and the entry corresponding to the message 1020 is added to the assigned work information 137 (step S213). After that, the allocation unit 120 terminates the processing.

If there is an estimated task with the same content as the task corresponding to the message 1020, the assigning unit 120 generates a list of organizations based on the retrieved entries (step S206), and selects one organization from the list. , the organization is set as the target organization (step S207).

The following methods are conceivable as a method of selecting an organization.
(Selection method 1) Random (Selection method 2) In descending order of overall accuracy

The allocation unit 120 checks the status of the target organization (step S208), and determines whether or not the target organization can perform the task corresponding to the message 1020 (step S209). The processes of steps S208 and S209 are the same as the processes of steps S202 and S203.

If the target organization can perform the work corresponding to the message 1020, the allocation unit 120 sets the target organization to the key "requesting organization" of the message 1020 (step S211), and assigns the entry corresponding to the message 1020 to the allocation work information 137. (step S213). After that, the allocation unit 120 terminates the processing.

If the target organization cannot perform the task corresponding to the message 1020, the allocation unit 120 determines whether or not there is an unprocessed organization in the list (step S210).

If there is an unprocessed tissue in the list, the allocation unit 120 returns to step S207 and performs similar processing.

If there is no unprocessed organization in the list, the assigning unit 120 sets the key "requesting organization" of the message 1020 to "all organizations" (step S212), and adds the entry corresponding to the message 1020 to the assigned work information 137. Add (step S213). After that, the allocation unit 120 terminates the processing.

FIG. 16 is a flowchart for explaining an example of processing executed by the allocation work management unit 121 of the first embodiment.

After the operation management support device 100 is activated, the allocation operation management unit 121 starts monitoring the allocation operation information 137 . In monitoring the assigned work information 137, the following processes are periodically executed. Note that the reference cycle can be set arbitrarily. For example, the period is 10 minutes.

The allocated work management unit 121 refers to the allocated work information 137 and determines whether or not there is work that has not been executed (step S301).

Specifically, the assigned work management unit 121 determines whether or not there is a work whose state 1206 is “unfinished” for a certain period of time from the value of the time 1201 . The fixed time can be set arbitrarily, such as 12 hours.

If there is no unexecuted work, the allocated work management unit 121 continues monitoring the allocated work information 137 .

If there is a job that has not been executed, the assigned job management unit 121 calls the assigning unit 120 and notifies it of the entry information corresponding to the job (step S302). After that, the allocated work management unit 121 continues monitoring the allocated work information 137 . As a result, the work that has not been executed is re-requested.

Next, processing executed by the business task estimation unit 111 will be described with reference to FIGS. 17 and 18. FIG.

FIG. 17 is a flowchart illustrating an example of processing executed by the estimation unit 122 according to the first embodiment.

The estimating unit 122, when called by the state monitoring unit 112, executes processing described below.

The estimation unit 122 acquires the message 1030 output by the state monitoring unit 112 (step S401). The estimation unit 122 sets the organization corresponding to the key “implementation organization” of the message 1030 as the target organization.

The estimating unit 122 checks the status of the target organization (step S402), and determines whether or not the target organization can perform the task corresponding to the message 1030 (step S403).

The processing of step S402 is the same as the processing of step S202. The process of step S403 may be the same as the process of step S203, or may be the following process. The estimating unit 122 refers to the estimated work information 138 and determines whether there is an entry in the function 1306 in which the value of the key “function” of the message 1030 is set. If the entry does not exist, the estimator 122 determines that the target organization can perform the task.

If the target organization can perform the task corresponding to the message 1030, the estimation unit 122 sets the target organization to the key "implementation organization" of the message 1030 (step S409), and adds the entry corresponding to the message 1030 to the estimated task information 138. (step S411). After that, the estimation unit 122 terminates the process.

If the target organization cannot perform the task corresponding to the message 1030, the estimating unit 122 refers to the owned resource information 132, extracts organizations having functions necessary for performing the task, and generates a list of organizations (step S404).

Specifically, the estimation unit 122 compares the function 502 of each entry in the table 500 with the key "function" of the message 1030, thereby extracting an organization that has the function required to carry out the work.

The estimating unit 122 selects one organization from the list of organizations and sets the selected organization as the target organization (step S405).

The estimation unit 122 checks the status of the target organization (step S406), and determines whether or not the target organization can perform the task corresponding to the message 1020 (step S407). The processing of steps S406 and S407 is the same as the processing of steps S402 and S403.

If the target organization can perform the task corresponding to the message 1030, the estimation unit 122 sets the target organization to the key "implementation organization" of the message 1030 (step S409), and adds the entry corresponding to the message 1030 to the estimated task information 138. (step S411). After that, the estimation unit 122 terminates the process.

If the target organization cannot perform the task corresponding to the message 1030, the estimation unit 122 determines whether or not there is an unprocessed organization in the list (step S408).

If there is an unprocessed tissue in the list, the estimation unit 122 returns to step S405 and performs similar processing.

If there is no unprocessed organization in the list, the estimation unit 122 sets the key "implementation organization" of the message 1030 to blank (step S410), and adds an entry corresponding to the message 1030 to the estimated work information 138 ( step S411). After that, the estimation unit 122 terminates the process.

FIG. 18 is a flowchart illustrating an example of processing executed by the estimation work management unit 123 of the first embodiment.

The estimated work management unit 123 starts monitoring the estimated work information 138 after the work management support device 100 is activated. In monitoring the estimated work information 138, the following processes are periodically executed. Note that the reference cycle can be set arbitrarily. For example, the period is 10 minutes.

The estimated work management unit 123 refers to the estimated work information 138 and determines whether or not there is an updated entry (step S501). Note that updating by the estimation work management unit 123 is not targeted.

If there is no updated entry, the estimated work management unit 123 continues monitoring the estimated work information 138 .

If there is an updated entry, the estimated work management unit 123 refers to the allocated work information 137, searches for the entry of the allocated work corresponding to the updated entry (step S502), and finds the allocated work corresponding to the estimated work. exists (step S503).

Specifically, the estimated work management unit 123 matches the value of the work 1203 to the value of the work 1301 of the updated entry, matches the value of the requesting organization 1205 to the value of the performing organization 1305 of the updated entry, In addition, the entry included in the time range stored in the time 1304 of the entry whose time stored in the time 1201 has been updated is searched.

If there is no allocated work corresponding to the estimated work, the estimated work management unit 123 continues monitoring the estimated work information 138 .

If there is an assigned task corresponding to the estimated task, the estimated task management unit 123 updates the accuracy 1307 of the updated entry based on the accuracy calculation logic information 135 (step S504).

FIG. 19 is a diagram showing an image of internal processing of the business management support device 100 of the first embodiment.

The status monitoring unit 112 acquires the message 1000 from the site status queue 150, refers to the task issuing condition information 130 based on the key "object" of the message 1000, and searches for an entry that matches the site status. If there is such an entry, status monitoring unit 112 generates assignment task message 1020 based on the entry and outputs it to assignment unit 120 . If the corresponding entry does not exist, the status monitoring unit 112 acquires an entry whose value of the object 1102 matches the value of the key “object” of the message 1000 from the field status information 136 . The state monitoring unit 112 refers to the work manual information 131 based on the combination of the values of the object 1102 and the state 1103 of the acquired entry, and acquires an entry of an executable work. State monitoring unit 112 generates message 1030 based on the obtained entry and outputs it to estimating unit 122 .

When receiving the message 1020 from the state monitoring unit 112, the allocation unit 120 checks based on the organization state queue 151 whether the organization can carry out the work. If the organization can carry out the work, the allocation unit 120 adds an entry corresponding to the message 1020 to the allocated work information 137 . If the organization cannot perform the task, the allocation unit 120 refers to the estimated task information 138 and searches for an estimated task with the same content. Furthermore, the allocation unit 120 determines whether or not the organization can perform the estimation task based on the organizational state queue 151 and the probability calculation logic information 135, and if the organization can perform the estimation task, the key " "Requesting organization" is rewritten, and an entry corresponding to the message 1020 is added to the allocated work information 137.

The allocated work management unit 121 monitors the allocated work information 137 and outputs an entry corresponding to the work to the allocation unit 120 when there is work that has not been performed for a certain period of time. The allocation unit 120 executes the processing shown in FIGS. 15A and 15B, updates the key “requesting organization” of the message 1020, and adds an entry corresponding to the message 1020 to the allocation work information 137. FIG.

When receiving the message 1030 from the state monitoring unit 112, the estimating unit 122 checks based on the organizational state queue 151 whether the organization can carry out the task. If the organization can perform the task, the estimation unit 122 adds an entry corresponding to the message 1030 to the estimated task information 138 . If the organization cannot perform the task, the estimation unit 122 identifies an organization having the necessary functions to perform the task based on the owned resource information 132, and determines whether the organization can perform the task based on the organization status queue 151. Check if you can. If the organization can perform the task, the estimation unit 122 rewrites the value of the key “implementation organization” of the message 1030 and adds an entry corresponding to the message 1030 to the estimated task information 138 .

The estimated work management unit 123 monitors the estimated work information 138, and if there is an updated entry, refers to the allocated work information 137 and searches for the allocated work corresponding to the entry (estimated work). If there is an assigned task corresponding to the entry, the estimated task management unit 123 calculates the accuracy based on the accuracy calculation logic information 135 and rewrites the value of the accuracy 1307 of the entry.

FIG. 20 is a diagram showing the flow of messages between the business management support device 100 and the messaging system 101 of the first embodiment. FIG. 21 is a diagram illustrating an example of a screen presented on the terminal 102 according to the first embodiment.

First, screens presented on the terminal 102 will be described. A screen 2100 as shown in FIG. 21 is presented to terminal 102 by messaging system 101 .

Screen 2100 includes display columns 2101 , 2102 , 2103 , 2104 , and 2105 and operation column 2106 .

A display column 2101 is a column for displaying a task (assigned task) that the organization corresponding to the terminal 102 is requested to perform. A display column 2102 is a column for displaying a task (assigned task) whose implementation is requested to an organization different from the organization corresponding to the terminal 102 . A display field 2103 is a field for displaying a task (estimated task) that is presumed to have been performed by the organization corresponding to the terminal 102 . A display field 2104 is a field for displaying work (estimated work) that is presumed to have been performed by an organization different from the organization corresponding to the terminal 102 . A display column 2105 is a column for displaying details of the assigned work or the estimated work. The operation field 2106 is a field for selecting various operations.

A user operating the terminal 102 can check the assigned work and estimated work of the own organization and other organizations by viewing the display fields 2101, 2102, 2103, and 2104. FIG. When confirming the details of the assigned work, the user selects the work displayed in the display column 2101 or the display column 2102 . As a result, the details of the selected assignment work are displayed in the display field 2105. FIG. When confirming the details of the estimated work, the user selects the work displayed in the display field 2103 or the display field 2104 . As a result, details of the selected estimation work are displayed in the display field 2104 .

The user selects “edit” in the operation column 2106 when editing the assigned work or the estimated work. When editing an assigned task, the display in the display field 2104 transitions to a state in which the requesting organization, status, updater, etc. can be edited. When editing the estimated task, the display in the display field 2104 transitions to a state in which the time, organization, accuracy, etc. can be edited. The user edits the value and presses the send button in the operation field 2106 . This will update the message.

The user selects “Generate task” in the operation column 2106 when generating a message regarding the assigned task, and selects “Generate estimated task” in the operation column 2106 when generating a message regarding the estimated task. A display field 2104 displays a template for generating a message for an assignment task or an estimated task. The user enters values in the template and presses a send button in the operation field 2106. FIG. This will register the message in the message queue.

When a message 1000 is registered in the site state queue 150 by an organization, the state monitoring unit 112 acquires the message 1000 via the message input/output unit 140 and registers an entry corresponding to the message 1000 in the site state information 136. .

When an entry is registered in the assigned work information 137 , the status monitoring section 112 generates a message 1020 from the entry and transmits it to the message input/output section 140 . The message input/output unit 140 registers the message 1020 in the assigned job queue 152 .

When any organization updates the key “state” of message 1020 from “uncompleted” to “completed” via screen 2100 , state monitoring unit 112 receives updated message 1020 via message input/output unit 140 . , and registers an entry corresponding to the message in the assigned business information 137 .

When an entry is registered in the estimated work information 138 , the state monitoring section 112 generates a message 1030 from the entry and transmits the message 1030 to the message input/output section 140 . The message input/output unit 140 registers the message 1030 in the estimated work queue 153 .

When any organization updates the key "status", key "implementation organization", key "accuracy", etc. of message 1030 via screen 2100, status monitoring unit 112 via message input/output unit 140, Obtain the updated message 1030 and register the entry corresponding to the message in the estimated work information 138 .

As described above, according to the first embodiment, the work management support device 100 grasps the state of the work site and the work that may be executed based on the information that can be obtained fragmentarily from the work site. Can plan and request work to be assigned to As a result, it becomes possible to smoothly coordinate operations between organizations in the event of a disaster, and it is possible to realize speedier and more efficient activities in the event of a disaster.

Next, Example 2 will be described. In the second embodiment, part of the processing performed by the estimation unit 122 is different. The second embodiment will be described below, focusing on the differences from the first embodiment.

The system configuration, hardware configuration, and software configuration of the second embodiment are the same as those of the first embodiment. In the second embodiment, part of the processing performed by the estimation unit 122 is different. Specifically, the determination method in step S403 is different.

(Determination method 1) The estimation unit 122 determines whether or not the organization can perform the work based on the registration status of the information to be registered in the site status queue 150 of each organization. For example, when an organization that normally registers information on medical facilities in the field status queue 150 at one-hour intervals does not register information on medical facilities during an arbitrary time period, the estimation unit 122 registers It is determined that some kind of trouble has occurred in the organization and the business cannot be carried out.

(Determination method 2) The estimation unit 122 determines whether or not the organization can carry out the work based on the contact person of the organization. For example, a message to the effect that Ministry A has implemented the task of "determining the opening location" is registered in the assigned task queue 152, and during the time period during which the task was being performed, Ministries A and B were closely contacted. If so, the estimating unit 122 determines that there is a high possibility that the "vehicle removal" task was performed by Ministry B.

In this way, the accuracy of estimation can be improved by combining information used for processing.

In addition, the present invention is not limited to the above-described embodiments, and includes various modifications. Further, for example, the above-described embodiments are detailed descriptions of the configurations for easy understanding of the present invention, and are not necessarily limited to those having all the described configurations. Moreover, it is possible to add, delete, or replace a part of the configuration of each embodiment with another configuration.

Further, each of the above configurations, functions, processing units, processing means, and the like may be realized by hardware, for example, by designing them in an integrated circuit. The present invention can also be implemented by software program code that implements the functions of the embodiments. In this case, a computer is provided with a storage medium recording the program code, and a processor included in the computer reads the program code stored in the storage medium. In this case, the program code itself read from the storage medium implements the functions of the above-described embodiments, and the program code itself and the storage medium storing it constitute the present invention. Examples of storage media for supplying such program code include flexible disks, CD-ROMs, DVD-ROMs, hard disks, SSDs (Solid State Drives), optical disks, magneto-optical disks, CD-Rs, magnetic tapes, A nonvolatile memory card, ROM, or the like is used.

Also, the program code that implements the functions described in this embodiment can be implemented in a wide range of programs or scripting languages such as assembler, C/C++, perl, Shell, PHP, Python, and Java (registered trademark).

Furthermore, by distributing the program code of the software that implements the functions of the embodiment via a network, it can be stored in storage means such as a hard disk or memory of a computer, or in a storage medium such as a CD-RW or CD-R. Alternatively, a processor provided in the computer may read and execute the program code stored in the storage means or the storage medium.

In the above-described embodiments, the control lines and information lines indicate those considered necessary for explanation, and not all control lines and information lines are necessarily indicated on the product. All configurations may be interconnected.

100 business management support device 101 messaging system 102 terminal 105 network 110 business allocation unit 111 business estimation unit 112 status monitoring unit 113 manual selection unit 120 allocation unit 121 allocation business management unit 122 estimation unit 123 estimated business management unit 127 allocation business information 130 business Issuing condition information 131 Work manual information 132 Possessed resource information 133 Organization management information 134 Object management information 135 Accuracy calculation logic information 136 Site state information 137 Assigned work information 138 Estimated work information 140 Message input/output unit 150 Site state queue 151 Organizational state queue 152 Assignment task queue 153 Estimation task queue 201 Processor 202 Main storage device 203 Secondary storage device 204 Network interface

A representative example of the invention disclosed in the present application is as follows. That is, a computer system including at least one computer having a processor, a storage device connected to the processor, and a network interface connected to the processor, and a terminal managed by a plurality of organizations that execute tasks against disasters. and the terminals of the plurality of organizations transmit site information about the site of the disaster and activity information about at least one of the work performed , and the computer system transmits first data including the state of the site and business purpose The at least one computer holds job issuing condition information to be stored and job manual information to store second data including the business purpose, the job, and the resources necessary for the execution of the job, and the at least one computer stores the acquired site information identify the status of the site based on, identify the assignment work that needs to be performed based on the identified status of the site, and grasp the activity status of the plurality of organizations based on the acquired activity information; determining an organization capable of executing the assigned task based on the activity status of the plurality of organizations; transmitting a request to perform the assigned task to the determined organization; One computer identifies the work purpose corresponding to the identified site condition based on the work issuance condition information, and executes the work corresponding to the identified work purpose based on the work manual information. , as the assigned work .

Claims (8)

A computer system including at least one computer having a processor, a storage device connected to the processor, and a network interface connected to the processor,
Connect with terminals managed by multiple organizations that carry out work in response to disasters,
The terminals of the plurality of organizations transmit site information about the site of the disaster and activity information about at least one of the work performed,
The at least one calculator comprises:
Identifying the state of the site based on the acquired site information,
identifying assignments that need to be performed based on the identified site conditions;
grasping the activity status of the plurality of organizations based on the acquired activity information;
determining an organization capable of executing the assigned task based on the activity status of the plurality of organizations;
A computer system characterized by transmitting a request for implementation of the assignment work to the determined organization. A computer system according to claim 1,
holding work issuance condition information storing first data including site conditions and work purpose, and work manual information storing second data including work purpose, work, and resources necessary for executing work;
The at least one calculator comprises:
identifying the business purpose corresponding to the identified site condition based on the business issuance condition information;
A computer system, wherein the business corresponding to the specified business purpose is specified as the assigned business based on the business manual information. A computer system according to claim 2,
holding owned resource information for managing resources owned by the plurality of organizations;
The second data includes business effects,
The at least one calculator comprises:
When the site information related to the same site as the site of the received site information has already been received, referring to the work manual information, the specified state of the site and the state of the work included in the second data Based on the result of comparison with the effect, identify the work corresponding to the site condition as an estimated work,
Based on the owned resource information, identify the organization that has the resources necessary to perform the estimation work,
grasping the activity status of the organization based on the activity information of the identified organization;
Identifying an organization that may be performing the inferred work based on the activity status of the identified organization;
correlating and recording the putative work and the organization identified;
calculating an index for evaluating the execution performance of the estimated work by the identified organization;
A computer system, wherein an organization capable of executing the assignment work is determined based on the index and the activity status of the plurality of organizations. A computer system according to claim 3,
A computer system, wherein the at least one computer and the terminals of the plurality of organizations transmit and receive information via message queues. A method of allocating a task to cope with a disaster executed by a computer system, comprising:
The computer system is
at least one computer having a processor, a storage device connected to the processor, and a network interface connected to the processor;
Connect with terminals managed by multiple organizations that carry out work in response to disasters,
The terminals of the plurality of organizations transmit site information about the site of the disaster and activity information about at least one of the work performed,
The method of allocating work in response to the disaster is as follows:
a first step in which the at least one computer identifies a site condition based on the acquired site information;
a second step in which the at least one calculator identifies assignments that need to be performed based on the identified site conditions;
a third step in which the at least one computer grasps the activity status of the plurality of organizations based on the acquired activity information;
a fourth step in which the at least one computer determines an organization capable of executing the assigned task based on the activity status of the plurality of organizations;
and a fifth step in which the at least one computer transmits a request to implement the allocated work to the determined organization. A method for allocating work in response to a disaster according to claim 5,
The computer system includes task issuance condition information storing first data including site conditions and task objectives, and task manual information storing second data including task objectives, tasks, and resources necessary for performing tasks. , and hold
The second step includes
a step in which the at least one computer identifies the business purpose corresponding to the identified site condition based on the business issuance condition information;
the at least one computer identifying the task corresponding to the specified task purpose as the assigned task based on the task manual information. Allocation method. A method for allocating work in response to a disaster according to claim 6,
the computer system holds owned resource information for managing resources owned by the plurality of organizations;
The second data includes business effects,
The method of allocating work in response to the disaster is as follows:
When the at least one computer has already received the site information related to the same site as the site information received, the work manual information is referred to, and the specified state of the site and the second identifying a task corresponding to the site condition as an estimated task based on a result of comparison with the effect of the task included in the data;
a step in which the at least one computer identifies the organization having resources necessary for performing the estimation task based on the owned resource information;
a step in which the at least one computer grasps the activity status of the identified organization based on the activity information of the organization;
the at least one computer identifying an organization that may be performing the estimation task based on the activity status of the identified organization;
the at least one computer correlating and recording the estimated work and the identified organization;
the at least one calculator calculating an index for evaluating the execution performance of the inferred task by the identified organization;
In the fourth step, the at least one computer determines an organization capable of executing the assigned work based on the index and the activity status of the plurality of organizations. method of allocating work to be done. A method for allocating work in response to a disaster according to claim 7,
A method of allocating work in response to a disaster, wherein the at least one computer and the terminals of the plurality of organizations transmit and receive information via message queues.

Images