Worker assignment management system and method

Abstract

To provide a technology for assisting efficient deployment of workers.SOLUTION: A failure database, a worker resource database, and worker failure type mapping data are stored. On the basis of the databases and data, a repair time scenario is created and recorded in a scenario database in association with a combination of site identifying information and worker identifying information. In the scenario, a repair time indicating a time that takes for a worker identified by the worker identifying information to repair a failure at a site indicated by the site identifying information is recorded. On the basis of the repair time scenario in the scenario database, failure allocation is planned indicating allocation of the workers for the failure at each site.SELECTED DRAWING: Figure 2

Description

Technical Field

[0001] The present disclosure relates to a technique for managing the allocation of workers for repairing failures that occur in a system equipped with facilities arranged at each location.

Background Art

[0002] In recent years, power systems can maintain a stable power supply against influences within the assumed range, such as normal weather changes. However, on the other hand, when there are unexpected events such as typhoons, earthquakes, floods, and wildfires, failures may occur in the facilities, resulting in long-term power outages. Therefore, in a power system, when a failure occurs, it is required to quickly and surely restore the power supply. This ability to repair from a failure is called resilience.

[0003] A power system consists of various components such as high-voltage transmission lines, substations, high-voltage transformers, voltage regulators, isolation switches, and towers, and the power from the power plant is supplied to consumers through the components arranged at each location. It is unknown which location and what kind of failure will occur due to an event such as a disaster, and failures may occur at multiple locations simultaneously. To quickly repair a power system, it is important for workers with appropriate skills to perform the repair work appropriately.

[0004] Patent Document 1 discloses a system restoration operation procedure creation system that creates and outputs operation procedures for devices such as circuit breakers and disconnectors to repair a failed power system. The system restoration operation procedure creation system of Patent Document 1 includes a model base in which a power system model at the time of an accident is formed, and a rule base consisting of restoration knowledge considering possible operations of individual circuit breakers. Inference is performed on the power system model using the restoration knowledge, and after the operation procedure of the device, which is the inference result, is confirmed as a possible operation procedure on the power system model, the operation procedure is output. This makes it possible to quickly and automatically create a restoration operation procedure regardless of the skill level of the operator.

Prior Art Documents

Patent Documents

[0005] [Patent Document 1] Japanese Patent Application Publication No. 06-165378 [Overview of the project] [Problems that the invention aims to solve]

[0006] The technology disclosed in Patent Document 1 makes it possible to quickly and automatically create repair operation procedures, which is expected to facilitate the maintenance and management of power systems. However, Patent Document 1 does not take into account the efficient deployment of workers to various locations for repairs.

[0007] One of the purposes of this disclosure is to provide technology that helps to efficiently deploy workers. [Means for solving the problem]

[0008] A worker assignment management system according to one aspect of the present disclosure is a worker assignment management system for managing the assignment of workers to repair a fault that has occurred in a system equipped with equipment located at each location, and comprises a storage device for storing data and programs, and a processing device for executing the programs using the data.

[0009] The storage device stores: a fault database which records information regarding the occurrence of a fault of a particular fault type at a location indicated by the location identification information, associated with a combination of location identification information and fault type; a worker resource database which records worker types that correspond to fault types that can be repaired, associated with worker identification information; and worker fault type mapping data which records information regarding the time required for a worker identified by the worker identification information to repair a fault of a particular fault type, associated with a combination of worker identification information and fault type.

[0010] Based on the fault database, the worker resource database, and the worker fault type mapping data, the processing device creates a repair time scenario in the scenario database, which records the time required for a worker identified by the worker identification information to repair a fault at a location indicated by the location identification information, in association with a combination of location identification information and worker identification information. Based on the repair time scenario in the scenario database, the processing device plans a fault assignment that indicates the assignment of workers to faults at each location. [Effects of the Invention]

[0011] According to one aspect of this disclosure, it is possible to support the efficient deployment of workers in repairing faults that occur in the power system. [Brief explanation of the drawing]

[0012] [Figure 1] This is a block diagram of a fault repair management system according to an embodiment. [Figure 2] This is a block diagram of a repair worker allocation management system according to an embodiment. [Figure 3] This is a sequence diagram illustrating an example of information transmission and reception between devices in a repair management system. [Figure 4] This is a sequence diagram showing the hierarchical repair process at a location where multiple failures occurred. [Figure 5] This figure shows an example of a fault database. [Figure 6] This figure shows an example of a worker resource database. [Figure 7] This figure shows an example of a worker disability type map database. [Figure 8] This is a diagram showing an example of an area database. [Figure 9] This figure shows an example of a point-to-point route database. [Figure 10] Flowchart of the planning phase process. [Figure 11]It is a flowchart showing the processing of the planning phase. [Figure 12] It is a diagram showing a repair time matrix representing an example scenario. [Figure 13] It is a diagram showing a repair time matrix representing an example scenario. [Figure 14] It is a diagram showing a movement time matrix representing an example scenario. [Figure 15] It is a diagram showing a movement time matrix representing an example scenario. [Figure 16] It is a flowchart showing the processing of the first example in the execution phase. [Figure 17] It is a flowchart showing the processing of the second example in the execution phase. [Figure 18] It is a flowchart showing the processing of the third example in the execution phase. [Figure 19] It is a flowchart showing the processing of the fourth example in the execution phase. [Figure 20] It is a diagram showing an example of a user interface. [Figure 21] It is a diagram showing an example of a user interface. [Figure 22] It is a diagram showing an example of a user interface. [Figure 23] It is a diagram showing an example of a user interface.

Modes for Carrying Out the Invention

[0013] Hereinafter, embodiments of the present invention will be described with reference to the drawings.

[0014] FIG. 1 is a block diagram of a failure repair management system according to the present embodiment.

[0015] A fault repair management system is a computer system that manages the allocation of workers to repair faults that occur in a power system where various components are located at different points. In this embodiment, a power system is used as an example. Components of a power system include high-voltage transmission lines, substations, high-voltage transformers, voltage regulators, isolation switches, towers, etc. These components are located at multiple different locations. Electricity from power plants is supplied to consumers through these various components.

[0016] Furthermore, depots equipped with workers and resources are set up at various locations to maintain and manage the various components of the power system. There are several types of workers, and workers are classified into types based on the tasks they can perform. Resources include the personnel, vehicles, and equipment necessary for workers to carry out equipment repair work.

[0017] When a power grid failure occurs, workers travel from the depot to the site of the equipment failure to perform repair work. Failures can occur at multiple locations, or multiple failures can occur at a single location. Workers may visit each location sequentially to perform the work. In cases where multiple complex failures occur simultaneously at various locations, it is crucial to efficiently utilize the limited number of workers to repair the failures.

[0018] The repair management system 110 plans which workers will be assigned to which locations when a power system failure occurs, and also dynamically updates the worker assignments if deviations from the plan occur during the actual execution of the work.

[0019] As shown in Figure 1, the repair management system 110 includes a repair worker deployment management system 100, a communication system 104, and a fault detection system 106. The communication system 104 and the fault detection system 106 are connected to the repair worker deployment management system 100 via a network 108. An operation terminal 102 is connected to the repair worker deployment management system 100. The repair worker deployment management system 100, the fault detection system 106, the communication system 104, and the operation terminal 102 may be geographically dispersed.

[0020] The operating terminal 102 is a computer equipped with input devices for operators to input information, such as a keyboard, mouse, touchscreen, microphone, or other devices, and an optional output device that outputs information regarding the operation of the repair worker placement management system 100.

[0021] Network 108 includes a mobile phone network, the Internet, any suitable local area network (LAN), metropolitan area network (MAN), or wide area network (WAN), and is a wired or wireless public or private network. Network 108 may be composed of a combination of multiple types of networks.

[0022] The communication system 104 is a communication system that includes multiple information terminals (not shown) carried by workers who go to various locations to repair faults. The information terminals are capable of wired or wireless communication and can transmit information to other information terminals and / or the repair worker deployment management system 100 via the network 108, and can receive information from other information terminals and / or the repair worker deployment management system 100 via the network 108. The information terminals are, for example, laptop computers, desktop computers, smartphones, integrated messaging devices, and tablet terminals. The communication system 104 may be configured as a subnetwork connected to the network 108.

[0023] The fault detection system 106 consists of multiple computers (not shown) and sensors (not shown) structured in a subnetwork. The sensors measure the status of equipment at each location, and the computers use a fault detection algorithm to calculate the probability of a fault existing at each location based on the measurement data, and send a fault notification to the repair worker deployment management system 100. The multiple computers of the fault detection system 106 may be geographically centralized or distributed.

[0024] Figure 2 is a block diagram of the repair worker allocation management system according to this embodiment.

[0025] The repair worker allocation management system 100 is a device having a network interface 200, a controller 202, an external memory 204, and an internal memory 206. The network interface 200, the controller 202, the external memory 204, and the internal memory 206 are interconnected via a data bus 208. The repair worker allocation management system 100 may be configured as, for example, a server.

[0026] The internal memory 206 stores the worker resource database 211, area database 212, worker fault type map database 213, fault database 214, inter-point route database 215, output schedule 216, constraint database 217, and scenario database 218. The worker resource database 211, area database 212, worker fault type map database 213, fault database 214, inter-point route database 215, output schedule 216, constraint database 217, and scenario database 218 will be described later.

[0027] The network interface 200 transmits and receives information with other systems via wired or wireless communication over the network 108.

[0028] The controller 202 is a CPU (Central Processing Unit) that reads and executes software programs (not shown) located in the internal memory 206.

[0029] External memory 204 is a reading and writing device for recording media such as Hard Disc Drives (HDDs), Solid State Drives (SSDs), storage systems, Integrated Circuit (IC) cards, Secure Digital (SD) cards, memory cards, and optical recording media (Compact Discs (CDs), Digital Versatile Discs (DVDs)).

[0030] Furthermore, the repair worker allocation management system 100 may also have an input device (not shown) and an output device (not shown). The input device, like the operation terminal 102, provides an interface for receiving information into the repair worker allocation management system 100. The output device, like the operation terminal 102, provides an interface for outputting information from the repair worker allocation management system 100.

[0031] Figure 3 is a sequence diagram illustrating an example of information transmission and reception between devices in a repair management system.

[0032] The repair worker allocation management system 100 is pre-configured by operators such as repair work managers who input data S300 from the operation terminal 102. The configured data S300 includes a worker resource database 211, an area database 212, a worker fault type map database 213, a point-to-point route database 215, and a constraint database 217.

[0033] Subsequently, fault detection data S302 is input to the repair worker deployment management system 100 from the fault detection system 106. Fault detection data S302 is information about a fault in the power system detected by the fault detection system 106. From this fault detection data S302, it is possible to determine the location where the fault occurred and the type of fault that occurred. In addition, fault detection data S302 includes, as an example, information on the probability that a fault has occurred. Fault detection data S302 is recorded in the fault database 214.

[0034] The repair worker deployment management system 100 executes the output schedule creation process S310 for the planning phase after acquiring all input information. The planning phase is the stage in which each worker is initially assigned to each location when a failure occurs in the power system and workers are to be dispatched to each location. The output schedule creation process S310 for the planning phase takes data S300 and failure detection data S302 as input and creates an output schedule S304 that shows the schedule for each worker who will perform the work to repair the failure, and is implemented by an optimization program. In some cases, the schedule may be such that one worker sequentially repairs failures at multiple locations. Each worker's schedule may include information on the order of the failures to be repaired, the time when the repair of each failure is expected to be completed, the time when they are expected to arrive at each failure location, and the resources required to repair all failures. Details of the output schedule creation process S310 for the planning phase will be described later.

[0035] The output schedule S304 created by the repair worker allocation management system 100 is recorded as output schedule 216 within the repair worker allocation management system 100 and transmitted to the communication system 104. The communication system 104 transmits the schedules of each worker included in the output schedule S304 to the respective worker's information terminal. Alternatively, the information terminals of all workers may be notified of the schedules of all workers.

[0036] Each worker visits their assigned location and performs repair work to fix the fault according to their own schedule. However, work and movement do not always progress according to schedule. If a worker's progress deviates from the schedule due to any factor, the worker can request a schedule change from the repair worker deployment management system 100. In this case, the worker sends a schedule change request S306 to the repair worker deployment management system 100 via an information terminal. The schedule change request S306 includes the worker's current location, the degree of deviation from the expected schedule, and related information.

[0037] Upon receiving a schedule change request S306, the repair worker deployment management system 100 executes the output schedule creation process S312 in the execution phase. The execution phase is the stage in which the assignment of each location to each worker is changed after the dispatch of workers to each location has begun. There are various reasons why a schedule change request S306 is issued. The output schedule creation process S312 in the execution phase for schedule change requests S306 due to various reasons will be described later.

[0038] After the output schedule creation process S312 in the execution phase, the repair worker allocation management system 100 transmits a new output schedule S308 to the communication system 104. The schedules for each worker in the output schedule S308 may be the same as or different from the schedule created in the planning phase. The new schedule may be sent to all workers, or it may be sent only to workers whose schedules have changed.

[0039] Figure 4 is a sequence diagram showing the hierarchical repair process at a location where multiple failures occurred.

[0040] Here, at a certain point, faults of type F11, F12, and F13 have occurred. It is also possible that multiple faults of the same type have occurred. Fault F11 needs to be repaired as quickly as possible, first and foremost, followed by fault F12, and then fault F13. It is not possible to repair two or more faults in parallel.

[0041] Furthermore, it is assumed that fault type F11 will be repaired by the worker with worker ID C11, fault type F12 will be repaired by the worker with worker ID C22, and fault type F13 will be repaired by the worker with worker ID C33.

[0042] Therefore, in the illustrated example, worker ID C22 will begin repairing fault type F12 only after worker ID C11 has finished repairing fault type F11. Even if worker ID C22 arrives at the location before the repair of fault type F11 is complete, worker ID C22 will wait until worker ID C11 has finished repairing fault type F11.

[0043] Figure 5 shows an example of a fault database.

[0044] The fault database 214 records fault detection data S302 from the fault detection system 106. The fault database 214 is configured to record information regarding the occurrence of a fault of a particular type at a location indicated by the location identification information, in association with a combination of fault type 500 and location identification information 502.

[0045] Fault type 500 is provided to the repair worker deployment management system 100 by the fault detection system 106 as part of the fault detection data S302. All possible fault types that may exist in the power system are defined as fault type 500. "F1", "F2", "F3", and "FL" are examples of fault type 500.

[0046] Location identification information 502 defines all locations that are geographically separated from each other. Location identification information 502 may include identification information for locations that are free from obstacles. Location identification information 502 may include the locations of all depots. "L1", "L2", "L3", and "LN" are examples of location identification information 502.

[0047] Each entry corresponding to a combination of fault type 500 and location identification information 502 stores information representing the probability that the fault indicated by fault type 500 has occurred at the location indicated by location identification information 502.

[0048] Figure 6 shows an example of a worker resource database.

[0049] The worker resource database 211 is provided from the operation terminal 102 before executing the output schedule creation process S310 for the worker allocation planning phase. The worker resource database 211 registers the worker type 602, starting point 604, ending point 606, resources 608, and average speed 610, associated with the worker ID 600 that identifies each worker.

[0050] The worker ID 600 contains an identifier that uniquely identifies each worker. "C1", "C2", "C3", and "CK" are examples of worker IDs. The worker type 602 contains a type of worker that can be uniquely associated with a fault type 500. Only workers of a specific worker type can perform the work of repairing a fault of a specific fault type. "001", "002", and "003" are examples of values ​​for worker type 602. Multiple worker IDs can have the same worker type 602. For example, if two workers have the same worker type 602, those workers can repair the same fault of fault type 500.

[0051] The departure point 604 is set with location identification information for the point from which the worker first departs in schedule S304. "LN" and "L(N-1)" are examples of values ​​for departure point 604. Departure point 604 is, for example, a depot. Multiple workers can depart from the same departure point 604. The end point 606 is set with location identification information for the point from which the worker last arrives in schedule S304. "LN" and "L(N-1)" are examples of values ​​for end point 606. End point 606 is, for example, a depot. Multiple workers can end at the same end point 606. A worker has a schedule with a departure point 604 and an end point 606, and the end point 606 may or may not be the same as the departure point 604.

[0052] Resource 608 contains the resources that can be used by the worker assigned to that worker ID. Resource 608 may include the number of auxiliary personnel, the type of vehicle, the type of equipment based on the worker type 602, etc. "R1", "R2", "R3", and "R4" represent the resources assigned to workers "C1", "C2", "C3", and "C4", respectively. Workers with the same worker type 602 may or may not have the same resources in resource 608.

[0053] The average speed 610 is set to the average speed related to the movement of workers. Figure 6 shows "30", "18", and "45" as examples of values ​​for the average speed 610.

[0054] Figure 7 shows an example of a worker fault type map database. The worker fault type map database 213 is provided from the operation terminal 102 before executing the output schedule creation process S310 in the planning phase. The worker fault type map database 213 is a database that has entries corresponding to combinations of worker ID 702 and fault type 700. The combination of fault type 700 and worker ID 702 defines all fault types that all workers of worker ID can repair. Therefore, fault type 700 may match fault type 500, or it may be a subset of fault type 500. The worker indicated by worker ID 702 is exactly the same as the worker indicated by worker ID 600. Each entry corresponding to the combination of worker ID 702 and fault type 700 shows the average time required for that worker to repair the fault of that fault type. The average time is the value obtained by multiplying a predetermined unit time by its integer. The unit time is not particularly limited, but may be, for example, 5 minutes, 10 minutes, or 15 minutes, and can be set by the operator from the operation terminal 102. The value of each entry in Figure 7 is a positive integer. The information to be registered in the worker injury type map database 213 is provided from the operation terminal 102 before the execution of the output schedule creation process S310 in the planning phase.

[0055] Figure 8 shows an example of an area database.

[0056] The area database 212 is provided in advance from the operation terminal 102 before the calculation of the output schedule creation process S310 for the worker deployment planning phase. The area database 212 registers the power load capacity 802, priority 804, and inclusion points 806, associated with the area name 800. The area name is set to a name that uniquely identifies each area in the power system. Generally, the power system is divided into multiple areas. Figure 8 shows "Area_A", "Area_B", and "Area_C" as examples of area name 800.

[0057] The power load capacity 802 is set to the maximum power load value that can be handled in the area specified by the area name. If there are no faults in the area, the area can be supplied with power equal to the power load capacity 802. The power load capacity 802 is expressed in units such as kilowatts. The larger the value of the power load capacity 802, the more power load can be handled in the area.

[0058] Priority 804 is assigned a value that represents the urgency of restoring the outage in that area. A higher priority value for 804 means that the outage in that area needs to be restored as soon as possible. For example, the priority of an area may be determined based on the importance of the power load required to provide services within that area. In the example in Figure 8, since "Area_A" and "Area_B" have a higher priority 804 than "Area_C", schedule S304 requires specifying the order of worker repair work and movement so that "Area_A" and "Area_B" are repaired before "Area_C". Also, if two areas have the same priority 804, the area with the higher power load capacity 802 should be prioritized for repair.

[0059] The enclosed point 806 is defined as a group of points that exist within that area. In the example in Figure 8, the area "Area_A" contains points "L1" and "L2".

[0060] Figure 9 shows an example of an inter-point route database. The inter-point route database 215 is provided by the operator from the operation terminal 102 before executing the output schedule creation process S310 of the planning phase.

[0061] The inter-point route database 215 shows the distance of a route (the number on the right) and the probability that the route is passable (the number on the left) for a route between two points indicated by point identification information. For example, the entry corresponding to row "L1" and column "L2" shows that the distance between point "L1" and point "L2" is "0.8km" and the probability that the route from point "L1" to point "L2" is usable is "0.9". The probability that the route is usable can be determined based on additional information, such as adverse weather events. Alternatively, the probability that the route is usable can be determined from sensor information measured by the sensors of the fault detection system 106. Note that the entry corresponding to row "L1" and column "L1" is set to "0". This indicates that there is no route between the same points or that workers will not go to the same location.

[0062] Figures 10 and 11 are flowcharts showing the processing of the planning phase.

[0063] The process shown in flowchart F1218 is also referred to as the output schedule creation process S310 in the planning phase in Figure 3.

[0064] In step F1200, the repair worker allocation management system 100 generates S1 scenarios (repair time scenarios) that create repair times for each worker and each fault location. S1 is defined by the operator from the operation terminal 102. For example, S1 may be determined depending on the total number of fault locations, the type of fault that occurred, the number of workers performing repairs on the faults, and the number of different worker types among the workers performing the repairs.

[0065] To create S1 scenarios, Monte Carlo sampling can be used, or a probability distribution function using a point-to-point route database and a worker resource database can be used.

[0066] Figures 12 and 13 show repair time matrices representing example scenarios. Figures 12 and 13 show two scenarios generated by step F1200. In step F1200, the repair worker allocation management system 100 uses the fault database 214, the worker resource database 211, and the worker fault type map database 213 to generate a repair time matrix for each scenario. Here, as an example, the repair time listed in each entry of the repair time matrix is ​​represented by an integer. The repair time is obtained by multiplying a predetermined unit time by an integer value. The unit time is not particularly limited, but may be, for example, 5 minutes, 10 minutes, or 15 minutes, and can be set by the operator from the operation terminal 102.

[0067] In the example of Scenario 1, it is shown that a worker with worker ID "C1" repairs a fault at location identifier "L2" in "3" units of time. In the example of Scenario 2, it is shown that a worker with worker ID "C1" repairs a fault at location identifier "L2" in "4" units of time.

[0068] As described above, the repair worker allocation management system 100 creates a repair time matrix for each scenario based on the fault database 214, the worker resource database 211, and the worker fault type map database 213. As described above using Figure 5, each entry in the fault database 214 records the probability that a fault has occurred, so the fault database 214 contains uncertainty about the existence of faults. This uncertainty is provided by the fault detection system 106. Also, as described above using Figure 7, the worker fault type map database 213 records the average time required for a worker to repair a fault, but since a worker may not actually be able to repair the fault in that average time, the worker fault type map database 213 contains uncertainty about the repair time. The repair worker allocation management system 100 generates multiple scenarios with varying repair times by using a function that takes these uncertainties as input and outputs multiple repair times with varying values. Monte Carlo sampling can be used as this function. Alternatively, a probability distribution function using the fault database 214, the worker resource database 211, and the worker fault type map database 213 can also be used.

[0069] In step F1200, the repair worker deployment management system 100 does not estimate the repair time for all combinations of workers and fault locations, but instead creates multiple (S1) scenarios (travel time scenarios) to be used in the planning phase F1218 described later.

[0070] In step F1202, the repair worker deployment management system 100 generates S2 scenarios for each worker, creating travel times for the routes between each fault location. S2 is defined by the operator from the operation terminal 102. For example, S2 may be determined depending on the total number of fault locations, the type of fault that occurred, the number of workers performing the fault repair, and the number of worker types among the workers performing the fault repair.

[0071] Furthermore, Monte Carlo sampling can be used to create S2 scenarios, and a probability distribution function using a point-to-point route database and a worker resource database can also be used.

[0072] Figures 14 and 15 show travel time matrices representing an example scenario. Figures 14 and 15 show two scenarios generated by step F1202. In step F1202, the repair worker deployment management system 100 uses the inter-point route database 215 and the worker resource database 211 to generate travel time matrices for each scenario for each worker. The travel time matrix contains the travel time between any two points for a given worker. S2 of these travel time matrices are created for each worker. These S2 travel time matrices are then created for each worker.

[0073] Here, as an example, the travel time listed in each entry of the travel time matrix is ​​represented by an integer. The travel time is obtained by multiplying a predetermined unit time by an integer value. The unit time is not particularly limited, but may be, for example, 5 minutes, 10 minutes, or 15 minutes, and can be set by the operator from the operation terminal 102.

[0074] In the example of Scenario 11, it is shown that a worker with worker ID "C1" takes "5" units of time to move from location identifier "L1" to location identifier "L2". In the example of Scenario 12, it is shown that a worker with worker ID "C1" takes "8" units of time to move from location identifier "L1" to location identifier "L2".

[0075] As described above, the repair worker deployment management system 100 creates a travel time matrix for each scenario for each worker based on the inter-point route database 215 and the worker resource database 211.

[0076] As described above using Figure 9, each entry in the inter-point route database 215 records the probability that the route is passable. Therefore, the inter-point route database 215 contains uncertainty about whether the route is passable. This uncertainty arises when the condition of the road structure after bad weather occurs is unknown. Also, as described above using Figure 6, the worker resource database 211 records the average speed at which workers move, but workers do not necessarily move at that average speed. Therefore, the worker resource database 211 contains uncertainty about the speed of movement. The repair worker deployment management system 100 generates multiple scenarios with varying travel times by using a function that takes these uncertainties as input and outputs multiple travel times with varying values. Monte Carlo sampling can be used as this function. Alternatively, a probability distribution function using the inter-point route database 215 and the worker resource database 211 can also be used.

[0077] In step F1202, the repair worker deployment management system 100 does not estimate the travel time required for all workers to move between all two points, but rather creates multiple (S2) scenarios to be used in the planning phase F1218 described later.

[0078] In step F1204, the repair worker deployment management system 100 stores data for all scenarios created in steps F1200 and F1202 in the scenario database 218. Step F1204 stores data for (S1 × S2) combinations of scenarios. The scenario database 218 stores a repair time matrix and a travel time matrix for all workers. Hereinafter, a scenario may mean one that includes a travel time matrix showing the travel time required for all workers to travel between any two points, and the generated repair time matrix.

[0079] In step F1206, the repair worker assignment management system 100 assigns each fault at each location to each worker by solving an optimization problem that minimizes the total time, which is the sum of the repair time and travel time, for all workers assigned to repair the fault, based on S1 repair time scenarios and S2 travel time scenarios.

[0080] In this case, for example, in a combination of S1 × S2 scenarios, a fault of a certain type at a certain location is assigned to only one worker, and in a combination of S1 × S2 scenarios, multiple workers of the same worker type are not assigned to the same location. The optimization problem is solved by minimizing the total repair time and travel time for all workers in a combination of S1 × S2 scenarios, with the fault assignment to workers as the decision variable.

[0081] The constraint that each fault of a particular type at a given location can only be assigned to one worker means that two or more workers cannot be assigned to repair the same fault of the same type at the same location. If there is one or more faults of a particular type, only one worker can repair that fault at a single location. This constraint must be satisfied in all combinations of the S1 x S2 scenarios.

[0082] Furthermore, the constraint that multiple workers of the same worker type cannot be assigned to a common location fault means that two or more workers of the same worker type 602 will not move to the same location, or that in a combination of S1 and S2 scenarios, workers of the same worker type 602 will not cross paths between locations.

[0083] The above optimization problem can be solved in several ways. For example, the optimization problem can be solved using stochastic mixed-integer linear programming (SMILP) by representing the decision variable as a binary variable that is "1" if a worker is assigned an obstacle at a certain location and "0" if they are not assigned an obstacle.

[0084] In step F1208, the repair worker assignment management system 100 determines whether the travel time between any two points assigned to each worker exceeds a predetermined travel time threshold. If the travel time between two points assigned to a worker exceeds the threshold, that worker will be assigned a fault at a geographically distant location; therefore, a condition is in place to prevent such an assignment. The travel time threshold may be set by the operator from the operation terminal 102. Alternatively, the travel time threshold may be defined as a percentage of the travel time.

[0085] In step F1208, the repair worker deployment management system 100 proceeds to step F1210 if the travel time between any two points for all workers is less than or equal to the travel time threshold, and returns to step F1200 if the travel time between any two points for any worker exceeds the travel time threshold.

[0086] In step F1210, the repair worker allocation management system 100 evaluates whether the relationship between a worker and the fault assigned to that worker is appropriate. The repair worker allocation management system 100 determines whether all workers have sufficient resources to repair all faults assigned to them.

[0087] All resources required for each fault assigned to a worker are totaled and compared to the resources available to that worker. The resources available to each worker are recorded in the worker resource database 211, entry 608.

[0088] The repair worker assignment management system 100 confirms the fault assignment to the workers (fault assignment) and proceeds to step F1212 if all workers have sufficient resources to repair all faults assigned to them, and returns to step F1200 if any worker does not have sufficient resources to repair any of the faults assigned to them.

[0089] In step F1212, the repair worker deployment management system 100 calculates the order in which each worker will visit the fault locations assigned to them. Each worker will depart from their respective starting point, visit each assigned fault location sequentially, and finally arrive at the ending point. The starting and ending points for each worker can be obtained from the starting point 604 and ending point 606 of the worker resource database 211 shown in Figure 6.

[0090] The repair worker deployment management system 100 determines the visit order by solving an optimization problem. In this example, the objective function of the optimization problem is the expected value of the power load capacity recovered during the recovery period for all combinations of the S1 × S2 scenarios. The recovery period is the time from when the first worker leaves the starting point until the last worker arrives at the ending point. The time required for each worker from leaving the starting point to arriving at the ending point can be determined by accumulating the repair time for each fault and the travel time between the two points. The decision variables should be determined so as to minimize the value of the objective function described above. The decision variables are the order in which each worker visits the fault locations.

[0091] The constraints on the optimization problem are as follows:

[0092] First, one constraint is that all workers must visit only the locations of the faults assigned to them in the fault assignment calculated in step F1206 and confirmed in step F1210. This constraint must be satisfied in all S1 x S2 scenario combinations generated from step F1204. If there are multiple faults at a single location, all faults must be repaired through all S1 x S2 scenario combinations according to a predetermined hierarchical fault repair sequence. An example of hierarchical fault repair is shown in Figure 4. The hierarchical fault repair sequence may be defined in the fault database 214 and extracted from the fault database 214 as needed.

[0093] Another constraint is that faults at locations within high-priority areas should be repaired preferentially, i.e., before faults at locations within low-priority areas. The geographical area covered by the repair worker deployment management system 100 is divided into multiple areas, with one or more locations within each area. Each area has a predetermined priority for fault repair. Therefore, all locations within the same area have the same priority.

[0094] Another constraint is that, if there are multiple areas with equal priority, faults at locations within the area with a larger power load capacity will be repaired with priority over faults at locations within the area with a smaller power load capacity.

[0095] This optimization problem can be solved in several ways. For example, the problem can be solved using stochastic mixed-integer linear programming (SMILP) by representing the decision variable as a binary variable that is "1" if the worker takes a path from one point to another, and "0" if they do not.

[0096] Furthermore, when solving the optimization problem described above, an upper limit may be set on the recovery period. The upper limit on the recovery period may be set by the operator from the operation terminal 102.

[0097] In step F1214, the repair worker deployment management system 100 checks whether the waiting time for all workers, based on fault assignments and visit order, is less than or equal to the waiting time threshold. For example, if there are multiple faults at one location, fault repairs are carried out in a hierarchical order, so workers may need to wait until they are ready to begin their own repair work. The repair worker deployment management system 100 refers to the fault repair and inter-location travel schedules of workers assigned to faults that require repair work in a hierarchical order, calculates the expected waiting time from when the worker is ready to begin their work until the work of other workers that are prerequisites for the worker to begin their work is completed, and compares this waiting time with the waiting time threshold. The waiting time threshold may be defined by time or by a percentage of the worker's working time.

[0098] If the total waiting time of all workers is below the waiting time threshold, the repair worker placement management system 100 determines the visit order of all workers, stores the schedule based on fault assignment and visit order as output schedule 216 in the internal memory 206, and notifies the workers stationed at each depot via the communication system 104. On the other hand, if the waiting time of any worker exceeds the waiting time threshold, the repair worker placement management system 100 proceeds to step F1216.

[0099] In step F1216, the repair worker allocation management system 100 receives instructions from the operator via the operation terminal 102 to change fault assignments and / or visit order, and changes the fault assignments and / or visit order according to the instructions. This change in fault assignments and / or visit order may include changing the departure point 604 or destination point 606 of any worker in the worker resource database 211, or changing the resource 608. After changing the fault assignments and / or visit order, the repair worker allocation management system 100 returns to step F1200.

[0100] Once each worker's schedule is created through the planning phase processing shown in flowchart F1218, each worker begins repairing the fault according to their respective schedule. As each worker repairs the fault and moves between locations according to their schedule, deviations from the plan may occur. In such cases, the repair worker allocation management system 100 receives requests for schedule changes from workers and responds by dynamically updating the schedule in the execution phase.

[0101] There are various factors that can cause changes to a worker's schedule. The main factors are as follows: First, new problems may arise during the execution of the schedule. Second, delays in repair work by workers may occur. Third, delays in workers' movement between locations may occur. Fourth, workers may be unable to move between locations due to road closures, etc. Fourth, workers' equipment may malfunction. Fourth, workers may run out of resources and require additional resources. These factors have a significant impact on the execution of the schedule planned in the planning phase. In the execution phase, it is possible to take these various factors into consideration and make optimal changes to the worker's schedule accordingly.

[0102] The following are examples of how to address the main factors that cause changes in workers' schedules.

[0103] Figure 16 is a flowchart showing the processing of the first example of the execution phase.

[0104] The process shown in flowchart F1300 is due to the occurrence of a new failure. This is to accommodate the changes.

[0105] In step F1302, the repair worker deployment management system 100 receives an update request from the communication system 104. For example, this request refers to the appearance of one or more new faults at a certain location. This means that workers need to repair these newly reported faults. Several workers will be assigned to the newly reported faults.

[0106] In step F1304, the repair worker deployment management system 100 updates the fault database 214 by incorporating the type of fault and the location where the fault occurred. In step F1306, the repair worker deployment management system 100 prompts the operator to check the status of the scheduled plan via the user interface.

[0107] In step F1308, the repair worker deployment management system 100 begins updating the fault assignment and visit sequence plan. Here, all routes already traveled by workers are removed from the fault assignment and visit sequence plan. Additionally, faults whose status has already changed from "unrepaired" to "repaired" are removed from the fault assignment and visit sequence plan. The fault assignment and visit sequence update should only target locations of faults that have not yet been repaired, and should ensure that workers follow the same routes they started traveling to before the current time step.

[0108] In step F1310, the repair worker deployment management system 100 selects a set of workers who are near the location of the newly occurring fault. A worker's proximity to the fault location is determined by the time it takes for the worker to arrive at that location (arrival time). The set may include workers whose arrival time is shorter than a threshold set by the operator.

[0109] In step F1312, the repair worker assignment management system 100 performs the resolution of a set of faults that should be repaired by the selected set of workers. The set of faults includes faults that were originally assigned to the workers included in the selected set, as well as newly occurring faults.

[0110] The following constraints must be met when resolving a series of issues, including newly occurring ones:

[0111] Each "unrepaired" fault is repaired by only one worker. Workers of the same worker type will not repair faults at the same location. If multiple faults exist at a single location, all of them are repaired according to a predefined hierarchical order. Faults in higher-priority areas are repaired first, followed by faults in lower-priority areas, and then faults in areas of the same priority but with smaller power load capacity. These constraints are met while maximizing the power load capacity restored during the recovery period.

[0112] The optimization problem in step F1312 can be solved in several ways. For example, mixed-integer linear programming (MILP) can be used to maximize the power load capacity to be restored during the recovery period, in accordance with the aforementioned constraints.

[0113] After step F1312 is completed, the repair worker deployment management system 100 completes execution phase F1300 and transmits the schedule based on the resulting fault assignment and visit order to the communication system 104 via the network 108.

[0114] Figure 17 is a flowchart showing the processing of the second example of the execution phase.

[0115] In step F1402, the repair worker deployment management system 100 receives an update request from the communication system 104. For example, this request refers to an update regarding a delay from one worker. This means that the worker can report if a delay is expected or has already occurred in repairing the fault and / or traveling between locations. This, in turn, results in a change to the worker's schedule.

[0116] In step F1404, the repair worker allocation management system 100 prompts the operator to confirm the validity of the request. The operator can then decide whether to accept or reject the request. Alternatively, the repair worker allocation management system 100 may pre-set a delay time threshold and accept the request if the delay time notified in the request exceeds that threshold.

[0117] If the request is not sufficiently valid, the repair worker allocation management system 100 terminates the execution phase in step F1430. In that case, the repair worker allocation management system 100 sends a message to the communication system 104 indicating that the request is rejected. On the other hand, if the request meets the criteria for schedule update, the repair worker allocation management system 100 proceeds to step F1406.

[0118] In step F1406, the repair worker allocation management system 100 retrieves the status of the worker's schedule. Next, the repair worker allocation management system 100 proceeds to step F1408. The process in step F1408 is the same as the process in F1308.

[0119] In step F1410, the repair worker allocation management system 100 initializes the parameters used for processing the execution phase. These parameters include counter P1, selection set size P2, and timer P3. Counter P1 is an upper limit set by the operator to limit the number of calculations. The execution phase is the process of finding the optimal alternative schedule for the workers and therefore needs to be completed very quickly. Selection set size P2 is the size of the set of fault locations and is set by the operator. Timer P3 is an upper limit that limits the calculation time for the execution phase and is pre-set by the operator.

[0120] In step F1412, the repair worker allocation management system 100 selects P2 locations from the fault locations assigned to the worker who requested the schedule update. The P2 locations are selected based on their proximity to the fault location that caused the delay (delay origin).

[0121] This proximity can be determined by the shortest time required to travel from the point of delay. To determine the routes to and from such P2 locations, remove all routes to selected locations from the fault assignment and visit sequence plan, and modify the routes to and from the remaining unselected locations. In other words, the number of locations will be N0-P2.

[0122] The repair worker deployment management system 100 attempts to re-select routes to and from the two selected locations P2. The process in step F1414 is the same as the process in step F1212 described above.

[0123] In step F1418, the repair worker deployment management system 100 determines whether the value of the objective function found in step F1414 is greater than the best value up to that point. The objective function of the optimization problem is the power load capacity to be restored during the recovery period for a set of P2 locations.

[0124] If the currently selected set of P2 locations has a better objective function value, in step F1416, the repair worker deployment management system 100 stores the updated route schedule in the output schedule 216. If the currently selected set of P2 locations is inappropriate, that is, if the value of the objective function obtained from P2 locations is less than or equal to the best value obtained so far, the repair worker deployment management system 100 proceeds to step F1422.

[0125] In steps F1422 and F1424, the repair worker allocation management system 100 updates the value of counter P1. In this example, since counter P1 is set to an upper limit to limit the number of times, the repair worker allocation management system 100 subtracts 1 from the value of counter P1.

[0126] In step F1426, the repair worker allocation management system 100 compares the time elapsed since the start of processing in this execution phase (elapsed time) with the time set in timer P3 (set time). If the elapsed time exceeds the set time of P3, the repair worker allocation management system 100 transmits the last recorded schedule to the communication system 104 in step F1428. Also in step F1426, the repair worker allocation management system 100 proceeds to step F1428 if the selection set size P2 becomes equal to the total number of "unrepaired" fault locations N0.

[0127] In step F1426, if the elapsed time is less than or equal to the set time of P3, and the selected set size P2 is not equal to N0, the repair worker allocation management system 100 updates the selected set size P2 by increasing it by 1 in step F1420, and returns to step F1412.

[0128] Figure 18 is a flowchart showing the processing of the third example of the execution phase.

[0129] In step F1502, the repair worker deployment management system 100 receives an update request from the communication system 104. This request is for an update regarding a blocked and impassable route between points.

[0130] In step F1504, the repair worker deployment management system 100 updates the route information corresponding to the route associated with the mentioned location where the route has been blocked.

[0131] The processing from step F1506 onwards is the same as the processing from step F1406 onwards shown in Figure 17, except for step F1512.

[0132] In step F1512, the repair worker deployment management system 100 selects P2 locations based on their distance from the location where the path is blocked. To determine the routes to and from these P2 locations, all routes to the selected locations are removed from the fault assignment and visit sequence plan, and the routes to and from the remaining unselected locations are modified. Thus, the number of locations becomes N0-P2.

[0133] Figure 19 is a flowchart showing the processing of the fourth example of the execution phase.

[0134] In step F1502, the repair worker allocation management system 100 receives an update request from the communication system 104. This request involves updating the details of some equipment or adding workers to the database, which will modify the worker resource database 211.

[0135] In step F1604, the repair worker allocation management system 100 updates the worker resource database 211, such as adding or deleting workers, according to the request.

[0136] The processes in steps F1606, F1608, and F1610 are the same as the processes in steps F1506, F1508, and F1510 shown in Figure 18.

[0137] In step F1612, the repair worker deployment management system 100 randomly selects P2 locations from N0 locations. To determine the routes to and from these P2 locations, all routes to the selected locations are removed from the fault assignment and visit sequence plan, and the routes to and from the remaining unselected locations are modified. In other words, the number of locations becomes N0-P2. The processing from step F1614 onward is the same as the processing from step F1514 onward shown in Figure 18.

[0138] Figures 20 to 23 show examples of user interfaces. Figure 20 shows a user interface that displays the recovery status of an area. Figure 21 shows a user interface that displays the recovery status of power load capacity. Figure 22 shows a user interface that displays the fault repair status at each location. Figure 23 shows a user interface that displays the repair status of each fault at a location.

[0139] As shown in Figure 20, the repair worker deployment management system 100 displays the status of fault repair in each area during the execution phase on the area repair status screen. This displays information acquired from the communication system 104 in real time. When each worker completes the repair of a fault, they input this information via their information terminal. The input information is notified to the repair worker deployment management system 100 and reflected on the screen display.

[0140] Operators can constantly monitor the progress of the planned schedule on this screen. The area repair status screen displays, for each area, the number of locations that have been repaired, the total number of locations with problems, and the percentage of locations that have been repaired relative to the total number of locations, as of the current time step. The total number of locations with problems is a constant value, and as the time step progresses, the number of repaired locations increases until the repair completion rate reaches 100%.

[0141] As shown in Figure 21, the repair worker deployment management system 100 displays the degree of recovery of the total power load capacity across all areas relative to the time step in a graph on the power recovery status screen. As the time step progresses, the area below the graph curve increases. This displays information acquired from the communication system 104 in real time. When each worker completes the repair of a fault, they input this information via their information terminal. The input information is notified to the repair worker deployment management system 100 and reflected on the screen display.

[0142] When the restored power load capacity reaches 100%, it means that power supply has been restored to all areas of the power grid. When power supply is restored to an area, the area under the curve increases according to the power load capacity of that area.

[0143] As shown in Figure 22, the repair worker deployment management system 100 displays the status of each location in a specific area at the current time step of the execution phase, the number of faults that have been repaired, and the total number of faults that occurred, on the repair status screen for each location. As the time step progresses, the number of repaired faults increases. This is an immediate display of information obtained from the communication system 104. When each worker finishes repairing a fault, they input this information via their information terminal. The input information is notified to the repair worker deployment management system 100 and reflected on the screen display. Note that the total number of faults at a given location may change depending on the requests in the execution phase.

[0144] For example, when an operator selects a specific area from the area repair status screen in Figure 20, the repair status screen for the locations in that selected area is displayed. In the example in Figure 22, the area Area_A is selected, and the status of locations L1 and L2 within that area is displayed.

[0145] As shown in Figure 23, the repair worker deployment management system 100 displays the progress of fault recovery at a specific point in the current time step during the execution phase on the fault recovery status screen.

[0146] For example, when an operator selects a location from the repair status screen shown in Figure 22, the repair worker deployment management system 100 displays the fault repair status screen for the selected location. In the example in Figure 23, the fault repair status screen for location L1 is displayed.

[0147] The screen in Figure 23 displays the expected status, actual status, and assigned workers for each fault. The expected status is the status of the fault at the current time step, determined by the planning or execution phase. The actual status is the actual status of the fault obtained from the communication system 104. The assigned workers indicate the workers assigned to the fault recovery work by the repair worker allocation management system 100.

[0148] The status of a fault can be fixed, being fixed, or not fixed. An operator can, for example, detect a discrepancy between the expected status and the actual status and request processing of the execution phase by pressing the "Execute Plan" button.

[0149] The embodiments described above include the following; however, the embodiments described above are not limited to those described below.

[0150] (Item 1) A worker assignment management system for managing the assignment of workers to repair faults occurring in a system equipped with equipment located at each location, comprising a storage device for storing data and programs, and a processing device for executing the programs using the data, wherein the storage device includes a fault database which records information on the occurrence of faults of a particular type at a location indicated by the location identification information, associated with a combination of location identification information and fault type, a worker resource database which records worker types that correspond to fault types of faults that can be repaired, associated with worker identification information, and a worker resource database which records worker types that correspond to fault types of faults that can be repaired, associated with a combination of worker identification information and fault type The processing device stores worker fault type mapping data, which contains information about the time required for a worker identified by the identification information to repair a fault of that type. Based on the fault database, worker resource database, and worker fault type mapping data, the processing device creates a repair time scenario in the scenario database, which records the time required for a worker identified by the worker identification information to repair a fault at a location indicated by the location identification information, in association with a combination of location identification information and worker identification information. Based on the repair time scenario in the scenario database, the processing device plans a fault assignment that indicates the assignment of workers to faults at each location.

[0151] This will help support the efficient deployment of workers.

[0152] (Item 2) In the worker assignment management system described in item 1, the storage device further stores an inter-point route database in which route distances indicating the distance of the route connecting two points for each combination of two points from a plurality of points are recorded, and the worker resource database further records average speeds indicating the average speed at which a worker identified by the worker identification information moves, in association with the worker identification information, and the processing device, based on the inter-point route database and the worker resource database, creates a travel time scenario for each worker, recording the travel time indicating the time required to travel the route connecting the two points for each combination of two points, and further records it in the scenario database, and plans the fault assignment based on the repair time scenario and the travel time scenario in the scenario database.

[0153] This allows for the efficient deployment of workers, taking travel time into consideration.

[0154] (Item 3) In the worker assignment management system described in item 2, the worker resource database further records, in association with the worker identification information, the starting point from which the worker identified by the worker identification information departs and the ending point to which the worker finally arrives after completing the repair of the assigned fault. For areas containing one or more points, a priority for fault repair and a power load capacity indicating the power that can be supplied to the load when there are no faults in the area are pre-set. The processing device defines the recovery period as the time from when the first worker departs the starting point until the last worker arrives at the ending point, prioritizes repairing faults at points in the high-priority area, and solves an optimization problem to maximize the power load capacity restored during the recovery period in combination of the repair time scenario and the travel time scenario, and plans a visit sequence indicating the order in which each worker will visit the fault locations assigned to them from the starting point to arrive at the ending point.

[0155] This allows us to determine not only the assignment of obstacles to workers, but also the order in which they should visit the locations of the assigned obstacles.

[0156] (Item 4) In the worker assignment management system described in item 3, the processing device receives requests for changes resulting from the execution of the fault assignment and visit sequence planning, reflects the changes in the fault database and the inter-site route database, creates a repair time scenario based on the fault database, the worker resource database and the worker fault type mapping data, creates a travel time scenario for each worker based on the inter-site route database and the worker resource database, and updates the fault assignment and visit sequence based on the repair time scenario and the travel time scenario.

[0157] This allows for correction of deviations from the plan during work, enabling efficient deployment of workers.

[0158] (Item 5) In the worker assignment management system described in item 4, the request for change includes any of the following: the occurrence of a new fault, a delay in repair work, a disruption of a route, or the addition of necessary workers.

[0159] (Item 6) In the worker assignment management system described in item 4, the processing device updates the fault assignment and visit order so as to prioritize repairing faults at locations in the high-priority area, and among areas with the same priority, to prioritize repairing faults in areas with a higher power load capacity.

[0160] This allows for prioritizing the restoration of power to areas with high priority and high power load capacity, thereby minimizing service degradation.

[0161] (Item 7) In the worker assignment management system described in item 4, the processing device, in planning the fault assignment, creates a plurality of repair time scenarios with varying repair times, creates a plurality of travel time scenarios with varying travel times, and plans the fault assignment by solving an optimization problem that minimizes the total time of repair time and travel time in each combination of the repair time scenario and the travel time scenario.

[0162] This makes it possible to create a robust plan for allocations that is resistant to future changes.

[0163] (Item 8) In the worker assignment management system described in item 7, the processing device acquires a failure probability as failure detection data, which indicates the probability that a failure of a certain type has occurred at a location indicated by the location identification information, in association with a combination of location identification information and failure type, and records it as the failure database. Based on the failure database and the worker failure type mapping data, the processing device creates the multiple repair time scenarios by varying the repair times.

[0164] This allows for the creation of robust plans that are resistant to uncertainty regarding the occurrence of failures.

[0165] (Item 9) In the worker assignment management system described in item 7, the storage device stores, as the inter-point route database, the route distance, which indicates the distance of the route connecting the two points, and the passability probability, which indicates the probability that the route is passable, for each combination of two points from among a plurality of points. The processing device, based on the inter-point route database and the worker resource database, creates multiple travel time scenarios for each worker, recording the travel time, which indicates the time required to travel along the route connecting the two points, by varying the travel time based on the passability probability.

[0166] This allows for the creation of robust plans that are resistant to uncertainties regarding route travel.

[0167] (Item 10) In the worker assignment management system described in item 3, the processing device creates a schedule of the worker's work and movement based on the fault assignment and the visit order plan, and transmits the schedule to the worker's information terminal.

[0168] (Item 11) In the worker assignment management system described in item 10, the processing device receives the change request from the information terminal carried by the worker, updates the worker's work and travel schedule based on the fault assignment and visit order updated in response to the change request, and transmits the schedule to the information terminal.

[0169] The embodiments of the present invention described above are illustrative for the purpose of explaining the invention and are not intended to limit the scope of the invention to those embodiments only. Those skilled in the art can implement the present invention in various other forms without departing from the scope of the invention. [Explanation of symbols]

[0170] 100…Repair worker deployment management system, 102…Operation terminal, 104…Communication system, 106…Fault detection system, 108…Network, 110…Repair management system, 200…Network interface, 202…Controller, 204…External memory, 206…Internal memory, 208…Data bus, 211…Worker resource database, 212…Area database, 213…Worker fault type map database, 214…Fault database, 215…Inter-point route database, 216…Output schedule, 217…Constraint database, 218…Scenario database, 500…Fault type, 502…Location identification information, 600…Worker ID, 602…Worker type, 604…Starting point, 606…Ending point, 608…Resource, 610…Average speed, 700…Fault type, 702…Worker ID, 800…Area name, 802…Power load capacity, 804…Priority, 806…Inclusion point

Claims

1. A worker assignment management system that manages the assignment of workers to repair faults occurring in a system equipped with equipment located at each point, A storage device for storing data and programs, The system includes a processing unit that executes the program using the aforementioned data, The storage device stores: a fault database which records information regarding the occurrence of a fault of a particular fault type at a location indicated by the location identification information, associated with a combination of location identification information and fault type; a worker resource database which records worker types that correspond to fault types that can be repaired, associated with worker identification information; and worker fault type mapping data which records information regarding the time required for a worker identified by the worker identification information to repair a fault of a particular fault type, associated with a combination of worker identification information and fault type. The aforementioned processing apparatus is Based on the fault database, the worker resource database, and the worker fault type mapping data, a repair time scenario is created and recorded in the scenario database. This scenario records the repair time, which indicates the time required for a worker identified by the worker identification information to repair a fault at a location indicated by the location identification information, in association with a combination of location identification information and worker identification information. Based on the repair time scenarios in the aforementioned scenario database, a fault assignment is planned that indicates the allocation of workers to faults at each location. Worker assignment management system.

2. The storage device further stores an inter-point route database in which, for each combination of two points from among the multiple point identification pieces, the route distance indicating the distance of the route connecting the two points is recorded. The worker resource database further records the average speed, which indicates the average speed at which the worker identified by the worker identification information moves, in association with the worker identification information. The aforementioned processing apparatus is Based on the aforementioned inter-point route database and the aforementioned worker resource database, for each worker, a travel time scenario is created that records the travel time required to travel along the route connecting the two points for each combination of two points, and this scenario is further recorded in the aforementioned scenario database. The fault assignment is planned based on the repair time scenario and travel time scenario in the aforementioned scenario database. The worker assignment management system according to claim 1.

3. The worker resource database further records, in association with the worker identification information, the departure point from which the worker identified by the worker identification information departs, and the final destination to which the worker arrives after completing the repair of the assigned fault. For an area containing one or more locations, a priority for fault repair and a power load capacity indicating the power that can be supplied to the load when there are no faults in that area are predetermined. The processing device defines the recovery period as the time from when the first worker departs the starting point until the last worker arrives at the ending point, prioritizes repairing faults at locations in the high-priority area, and solves the optimization problem of maximizing the power load capacity restored during the recovery period in combination of the repair time scenario and the travel time scenario, and plans a visit sequence that indicates the order in which each worker will visit the fault locations assigned to them from the starting point until they arrive at the ending point. The worker assignment management system according to claim 2.

4. The processing device receives requests for changes resulting from the execution of fault assignment and visit sequence planning, and reflects the changes in the fault database and the inter-point route database. Based on the aforementioned fault database, worker resource database, and worker fault type mapping data, a repair time scenario is created. Based on the aforementioned inter-point route database and the aforementioned worker resource database, a travel time scenario is created for each worker. Based on the repair time scenario and the travel time scenario, update the fault assignment and the visit order. The worker assignment management system according to claim 3.

5. The aforementioned change requests include any of the following: the occurrence of a new fault, delays in repair work, disruption of the route, or the need for additional personnel. The worker assignment management system according to claim 4.

6. The processing device updates the fault assignment and visit order so as to prioritize repairing faults at locations in the high-priority area, and among areas with the same priority, to prioritize repairing faults in areas with a higher power load capacity. The worker assignment management system according to claim 4.

7. The aforementioned processing apparatus is In the aforementioned fault allocation plan, Create multiple repair time scenarios with varying repair times, Create multiple travel time scenarios with varying travel times, The fault assignment is planned by solving an optimization problem that minimizes the total time of repair and travel in each combination of the repair time scenario and the travel time scenario. The worker assignment management system according to claim 4.

8. The aforementioned processing apparatus is The system acquires fault detection data, which indicates the probability that a fault of a particular type has occurred at a location indicated by the location identification information, in association with a combination of location identification information and fault type, and records this data in the fault database. Based on the fault database and the worker fault type mapping data, the repair times are varied to create the multiple repair time scenarios. The worker assignment management system according to claim 7.

9. The storage device stores, as the inter-point route database, a route distance indicating the distance of the route connecting two points and a passability probability indicating the probability that the route is passable for each combination of two points from among a plurality of points. The processing device, based on the inter-point route database and the worker resource database, creates multiple travel time scenarios for each worker, each recording the travel time required to travel along the route connecting the two points, with the travel time varying based on the passability probability. The worker assignment management system according to claim 7.

10. The processing device creates a schedule of the worker's work and movement based on the fault assignment and the visit sequence plan, and transmits the schedule to the worker's information terminal. The worker assignment management system according to claim 3.

11. The aforementioned processing apparatus is The worker receives a request for change from the information terminal he carries, Based on the updated fault assignments and visit order in response to the request for the aforementioned change, the schedule for the worker's work and travel is updated, and the schedule is transmitted to the information terminal. The worker assignment management system according to claim 10.

12. A worker assignment management method for managing the assignment of workers to repair a fault occurring in a system equipped with equipment located at various points, using a computer having a storage device for storing data and programs and a processing device for executing the programs using the data, The storage device stores: a fault database which records information regarding the occurrence of a fault of a particular fault type at a location indicated by the location identification information, associated with a combination of location identification information and fault type; a worker resource database which records worker types that correspond to fault types that can be repaired, associated with worker identification information; and worker fault type mapping data which records information regarding the time required for a worker identified by the worker identification information to repair a fault of a particular fault type, associated with a combination of worker identification information and fault type. The aforementioned processing apparatus Based on the fault database, the worker resource database, and the worker fault type mapping data, a repair time scenario is created and recorded in the scenario database. This scenario records the repair time, which indicates the time required for a worker identified by the worker identification information to repair a fault at a location indicated by the location identification information, in association with a combination of location identification information and worker identification information. Based on the repair time scenarios in the aforementioned scenario database, a fault assignment is planned that indicates the allocation of workers to faults at each location. Worker assignment and management method.

Images