JP7465239B2 - System for arranging supporters for malfunctions and method for arranging supporters for malfunctions - Google Patents

Description

The present invention relates to a system for arranging support personnel to respond to elevator and other lift failures, and a method for arranging support personnel to respond to failures.

Conventionally, in the maintenance of elevators that are composed of multiple devices, a technology has been proposed in which, when a failure occurs in a component device of the elevator, a list of possible devices causing the failure is made up based on the failure state and the error code issued by the elevator itself, and the list is presented to the person responding to the failure (Patent Document 1). In Patent Document 1, similar failures that are highly similar to the local failure state are extracted and compiled from failure history data such as daily failure reports that accumulate error codes and failure states that have occurred in the past, and a list of devices that are likely to be the cause of the failure is made. This aims to quickly restore the failure.

Patent Document 1 also discloses a failure response support method in which workers who have experience responding to the same or similar failure cases in the same or similar model as the support request are selected as support candidates to support on-site workers in responding to the failure, and are assigned to provide the support they are able to provide.

JP 2018-100176 A

However, the time it takes to restore an elevator depends heavily on the skills of the worker. For example, some workers are good at investigating the cause of a failure but not at actually replacing parts or adjusting equipment, while others are not good at investigating the cause but are good at the actual countermeasures. Therefore, even if a worker who has experience dealing with the same or similar failure cases of the same or similar model is selected as a support candidate, there is a problem that, depending on the content of the support, the appropriate support candidate is not necessarily selected. This can result in the total work time related to responding to the failure (failure response time) ultimately being longer than the expected failure response time.

The present invention aims to provide an elevator breakdown supporter arrangement system and breakdown supporter arrangement method that can select more appropriate support candidates.

In order to solve the above problems and achieve the object of the present invention, the failure response supporter arrangement system of the present invention includes a daily failure report management unit, an elevator specification management unit, a standard cause investigation time management unit by equipment, a standard countermeasure work time management unit by equipment, and a skill management unit. The failure response time calculation system of the present invention includes a cause equipment candidate extraction unit, a cause investigation time calculation unit, a countermeasure work time calculation unit, a parts transport time calculation unit, and a supporter arrangement unit. The daily failure report management unit stores past daily failure reports including at least the failure state, the failure causing equipment, the cause investigation time, the countermeasure work time, and the identification number of the elevator. The elevator specification management unit stores specification information of the elevator including at least the identification number, the model, the constituent equipment, and address information of the elevator. The standard cause investigation time management unit by equipment stores standard cause investigation times by elevator model and constituent equipment. The standard countermeasure work time management unit stores standard countermeasure work times by elevator model and constituent equipment. The cause device candidate extraction unit extracts cause device candidates for the occurred failure with a probability from the daily failure reports stored in the daily failure report management unit and the elevator failure state. The cause investigation time calculation unit sets the cause device candidates whose total probability is equal to or greater than a predetermined value as a failure cause device group, and compares each cause device listed in the failure cause device group with the device-specific standard cause investigation time management unit to extract a standard cause investigation time for each cause device, and calculates the total standard cause investigation time for each cause device as the cause investigation time. The countermeasure work time calculation unit compares each cause device listed in the failure cause device group with the device-specific standard countermeasure work time management unit to extract a standard countermeasure work time for each cause device, and calculates the total standard countermeasure work time for each cause device as the countermeasure work time. The supporter arrangement unit selects a cause investigation supporter and/or a countermeasure work supporter from the information stored in the skill management unit according to the countermeasure work time and cause investigation time.

The method for arranging failure response supporters of the present invention extracts candidate devices causing the occurrence of a failure with a probability from the daily failure reports stored in the daily failure report management section and the failure state of the failed elevator. Among the extracted candidate devices causing the failure, those with a total probability equal to or greater than a predetermined value are set as a group of devices causing the failure, and each device causing the failure listed in the group of devices causing the failure is compared with the device-specific standard cause investigation time management section to extract a standard cause investigation time for each device, and the total of the standard cause investigation times for each device causing the failure is calculated as the cause investigation time. Each device causing the failure listed in the group of devices causing the failure is compared with the device-specific standard countermeasure work time management section to extract a standard countermeasure work time for each device causing the failure, and the total of the standard countermeasure work times for each device causing the failure is calculated as the countermeasure work time . From the information stored in the skill management section, a cause investigation supporter and/or a countermeasure work supporter are selected according to the countermeasure work time and cause investigation time.

According to the present invention, when selecting a supporter to assist maintenance personnel working on-site in the event of an elevator breakdown, a more appropriate supporter can be selected, thereby improving the work efficiency in responding to the breakdown.

1 is a configuration diagram of a failure response supporter dispatch system according to an embodiment of the present invention. 1 is an example of information constituting a daily failure report DB. 1 is an example of information constituting a device-specific standard cause investigation time DB. 13 is an example of information constituting a device-specific standard countermeasure work time DB. 4 is an example of information constituting a part information DB. 13 is an example of information constituting a skill DB for maintenance technician X. 13 is an example of information constituting a skill DB for maintenance worker Y. 13 is a diagram showing an example of a causative device of an occurred failure and its probability extracted by a candidate causative device extraction unit; FIG. FIG. 13 is a diagram showing an example of selection criteria for a transportation means selected by a transportation means selection unit. 13 is an example of travel distance and congestion information for each transportation means output by the traffic condition providing system. 4 is a flow chart showing a failure response time calculation method in a failure response time calculation unit. 13 is a flow chart for explaining a method for dispatching a breakdown supporter in the breakdown supporter dispatching system. 13 is a diagram illustrating an example of information transmitted from a failure response information transmission unit to a mobile terminal of a maintenance worker. FIG.

Below, an example of an elevator breakdown supporter dispatching system and breakdown supporter dispatching method according to one embodiment of the present invention will be described with reference to the drawings. Note that the present invention is not limited to the following example. In each of the drawings described below, the same reference numerals are used for common parts.

Figure 1 is a configuration diagram of a failure response supporter dispatch system according to this embodiment. As shown in Figure 1, the failure response supporter dispatch system 100 is composed of an elevator or other lift 1, mobile terminals 5 carried by maintenance personnel 4, cause investigation supporters 7, and countermeasure work supporters 8, a monitoring center 2, and a traffic condition providing system 6.

The elevator 1 is provided with a control panel 11 that controls the operation of the elevator 1, and a remote monitoring device 12. The remote monitoring device 12 is constantly connected to the error code output terminal of the control panel 11, and at least when a malfunction occurs in the elevator 1, it transmits an abnormality signal including the identification number of the elevator 1 and an error code indicating the nature of the malfunction to the monitoring center 2.

The mobile terminal 5 carried by the maintenance worker 4 has a function of transmitting the specification information and fault condition information of the elevator 1 confirmed by the maintenance worker 4 to the monitoring center 2. In addition, the mobile terminals 5 of the maintenance worker 4, the cause investigation supporter 7, and the countermeasure work supporter 8 have a function of receiving fault response information regarding fault response generated by the fault response supporter arrangement system 100 from the monitoring center 2.

The monitoring center 2 has a receiving device 21, an information management unit 20, and an information processing unit 40. The receiving device 21 is connected to the remote monitoring device 12 equipped on the elevator 1 by a dedicated line, an Internet line, other wired transmission line, or a wireless transmission line. The receiving device 21 receives fault status information such as the identification number of the elevator 1 and an abnormality alarm signal including an error code, as well as specification information of the elevator 1, transmitted from the remote monitoring device 12. The receiving device 21 also has a function of receiving, via a mobile terminal 5, information transmitted by telephone from a resident or manager of the building in which the elevator 1 is located, and fault status information and specification information of the elevator 1 confirmed by a maintenance worker 4 dispatched to the site.

The information management unit 20 has an elevator specification database (hereinafter referred to as DB) 23, a daily failure report DB 22, a standard cause investigation time by equipment DB 24, a standard countermeasure work time by equipment DB 25, a parts information DB 26, and a skill DB 45. Details of each part of the information management unit 20 will be described later.

The information processing unit 40 includes a similar failure daily report search unit 27, a candidate causal device extraction unit 28, a cause investigation time calculation unit 29, a countermeasure work time calculation unit 30, a part to be shipped out selection unit 31, a means of transportation selection unit 32, a part transport time calculation unit 33, an automatic shipping unit 34, and a failure response time calculation unit 35. Furthermore, the information processing unit 40 includes a supporter necessity determination unit 36, a supporter arrangement unit 38, and a failure response information transmission unit 37.

The information processing unit 40 compares the elevator 1 specification information and fault condition information received by the receiving device 21 with each database of the information management unit 20, and calculates the time required to investigate the cause and the time required to implement countermeasures. The information processing unit 40 also calculates the part transport time based on the traffic information provided by the traffic condition providing system 6. The detailed processing content of each unit in the information processing unit 40 will be described later.

The traffic condition providing system 6 is operated by an external traffic information company separate from the monitoring center 2, and provides the monitoring center 2 with information on travel times by means of transportation based on location information such as addresses or GPS on mobile devices via an Internet line or the like. In addition, the traffic condition providing system 6 provides the monitoring center 2 with information by means of transportation that takes into account congestion information.

Next, examples of the configuration of the elevator specifications DB 23, daily failure report DB 22, standard cause investigation time by equipment DB 24, standard countermeasure work time by equipment DB 25, parts information DB 26, and skill DB 45 that make up the information management unit 20 will be described. The elevator specifications DB 23, daily failure report DB 22, standard cause investigation time by equipment DB 24, standard countermeasure work time by equipment DB 25, parts information DB 26, and skill DB 45 correspond to the elevator specifications management unit, daily failure report management unit, standard cause investigation time by equipment management unit, standard countermeasure work time by equipment management unit, parts information management unit, and skill management unit of the present invention, respectively.

The elevator specification DB23 is a database that stores information on the identification numbers, models, and specifications of the component equipment of all elevators that are subject to maintenance. The identification numbers are numbers that are individually assigned to each elevator, and are recorded, for example, as "A1234" (see Figure 2).

The daily failure report DB22 is a database in which past daily failure reports, including at least the failure status of the failed elevator, the equipment causing the failure, the time spent investigating the cause, the time spent working on the remedy, and the identification number, are accumulated for each day that a failure occurred. Figure 2 is an example of information that constitutes the daily failure report DB. As shown in Figure 2, the daily failure report DB22 has items such as "daily failure report number," "date and time of failure," "model," "identification number," "error code," "causing equipment," "status at time of failure," "initial confirmation results," "time spent investigating the cause," "time spent working on the remedy," "name of replacement part," and "person responsible for responding to the failure."

The "Daily fault report number" field records the number assigned to each daily fault report. The "Fault date and time" field records the date and time the fault occurred, for example, "December 24, 1999, 14:30". The "Model" field records the model name of the faulty elevator, for example, "EL-2". The "Identification number" field records an identification number given to identify the elevator, for example, "A12345". The "Error code" field records the error code issued by the faulty elevator, for example, "TO1". If no error code was issued, "None" is recorded in the "Error code" field.

The "causing equipment" field records the equipment that caused the failure, such as the "encoder." The "state at time of failure" field records the state of the elevator at the time of the failure; for example, if there is a step between the landing floor position and the car's stopping position, it is recorded as "step," and if an abnormal sound is generated, it is recorded as "abnormal sound." The "initial confirmation results" field records the initial information confirmed by the maintenance staff on-site at the time of the failure; for example, if the car stops at an intermediate floor, it is recorded as "stopped at intermediate floor," and if the power is turned off, it is recorded as "power loss," etc.

The "cause investigation time" field records the time it took the maintenance staff to investigate the cause on-site, for example, "10 minutes." Here, cause investigation refers to the work of investigating the equipment causing the failure in detail based on the failure state, as well as investigating parts that need to be replaced, and is the work carried out prior to countermeasure work such as part replacement or part adjustment.

The "Countermeasure Work Time" field records the time it took for the maintenance staff to carry out countermeasure work such as part replacement on-site, and is recorded as "15 minutes," for example. Countermeasure work here refers to work to restore the elevator, such as replacing or adjusting parts in the equipment that caused the failure, and is work that is carried out after an investigation into the cause has been conducted.

The "Name of replaced part" field records the name of the part that was replaced, such as "Encoder A." The "Person who responded to the malfunction" field records the name of the maintenance worker who performed the work to restore the broken elevator on-site, in a format that allows the maintenance worker to be identified, such as "Maintenance worker A."

In this way, each item recorded in the daily failure report DB22 is categorized and stored in a form that allows filtering and aggregation. Maintenance personnel who have responded to a failure can register these daily failure report DB22 at any time from their respective mobile terminals. Note that the "failure state" of the present invention refers to a failure state that can be recognized from an error code and/or a failure state confirmed by a maintenance personnel.

The equipment-specific standard cause investigation time DB24 is a database that stores the standard cause investigation time for responding to a failure by model and component equipment of the elevator 1. Figure 3 is an example of information that constitutes the equipment-specific standard cause investigation time DB24. As shown in Figure 3, the equipment-specific standard cause investigation time DB24 has items such as "model," "causing equipment," and "standard cause investigation time." The items "model" and "causing equipment" are the same as the items "model" and "causing equipment" in the daily failure report DB22.

In the "Standard cause investigation time" field, the standard time required to investigate the cause of a breakdown by elevator 1 model and by the device causing the breakdown is recorded, for example, as "10 minutes." The standard cause investigation time is, for example, the average or median calculated for each model of causing device stored in the daily breakdown report DB22, and is composed of statistically calculated values.

The equipment-specific standard countermeasure work time DB25 is a database that stores standard countermeasure work times for responding to failures by model and component equipment of the elevator 1. Figure 4 is an example of information that constitutes the equipment-specific standard countermeasure work time DB25. As shown in Figure 4, the equipment-specific standard countermeasure work time DB25 has items such as "model," "causing equipment," and "standard countermeasure work time." The items "model" and "causing equipment" are the same as the items "model" and "causing equipment" in the daily failure report DB22.

In the "Standard countermeasure work time" field, the standard countermeasure work time required to respond to a failure is recorded for each model of elevator 1 and the equipment causing the failure, and is recorded as "15 (minutes)", for example. The standard countermeasure work time is, for example, the average or median calculated for each model of causing equipment stored in the daily failure report DB, and is composed of statistically calculated values. The standard countermeasure work time may also be composed of a time estimated based on a standard part replacement procedure manual that has been created in advance.

The parts information DB26 is a database that stores parts information for each model and component device of the elevator 1, and inventory information for each parts storage base. FIG. 5 is an example of information that constitutes the parts information DB26. As shown in FIG. 5, the parts information DB has items such as "model", "causing device", "weight", "packaging size", and "inventory information". The items "model" and "causing device" are the same as the items "model" and "causing device" in the daily failure report DB22. Note that the "causing device" in FIG. 5 is the part to be shipped out. The parts information DB is collated with information on the model and device that can be linked from the identification information of the elevator 1, and is used to determine the size of the parts group that need to be replaced and from which base the parts group should be transported to the elevator 1 that has broken down.

The "Weight" field records the weight of the part to be shipped, for example, "0.3 kg". The "Package Size" field records the size of the part to be shipped when it is packed for transportation, for example, "15 x 15 x 5 cm". The "Inventory Information" field records the storage base (address) of each part to be shipped and the number stored at that storage base, for example, "Parts Center (Area A) 1,000 units, Branch Office (Area B) 3 units, Sales Office A (Area C) 2 units, Sales Office B (Area D) 1 unit", etc.

Skill DB45 is a database that stores the skill information of all registered maintenance personnel, the current location of each maintenance personnel, and the work status of each maintenance personnel. Figures 6 and 7 are examples of the information that constitutes skill DB45 for each maintenance personnel. Figure 6 shows the skill information, current location, and work status of maintenance personnel X, and Figure 7 shows the skill information, current location, and work status of maintenance personnel Y.

As shown in Figures 6 and 7, in the skill DB 45, data is managed for each holder, and each data is composed of items such as "model," "part," "work content," "location," and "status."

The "Model" field records the model name of an elevator on which the owner has previously performed work to respond to a malfunction, for example, "Model A," "Model B," etc., so that the model can be identified. Then, for each model, the fields "Part" and "Work content" are recorded.

The "Part" item indicates the part of the elevator where the maintenance worker dealt with the malfunction, and each part of the elevator is recorded, such as "machine" or "inside the tower."

The "Work content" item records the "number of times" that a maintenance worker has performed each type of work when responding to a failure, and a "rank" that indicates the skill level. Work content is categorized as "cause investigation," "repair," and "adjustment," and the "number of times" that a maintenance worker has performed the corresponding item is updated as needed depending on the type of work performed. In addition, the "rank" item records a rank according to the number of times of experience, for example, if the "number of times" is 10 or more, an A is recorded, if it is 6 to 9 times, and if it is 5 times or less, a C is recorded.

The "Location" field records the current location of the maintenance worker, for example, "Office" or "Building A" along with address information. The "Status" field records the current work status of the maintenance worker, for example, "Waiting" or "Working", etc.

For example, maintenance worker X shown in Figure 6 is recorded as having more experience with "cause investigation" than with other countermeasure tasks such as "repair" and "adjustment," and his skill level is also recorded as being higher for "cause investigation" than for "repair" and "adjustment." In other words, it can be seen that maintenance worker X is skilled at cause investigation and has the skill of investigating causes. In addition, the skill DB 45 records that maintenance worker X is currently waiting in the office.

On the other hand, maintenance worker Y shown in Figure 7 is recorded as having more experience with countermeasure work such as "repair" and "adjustment" than he has experienced "cause investigation", and his skill level is also recorded as being higher for "repair" and "adjustment" than for "cause investigation". In other words, it can be seen that maintenance worker Y is skilled at countermeasure work and has the skill of being good at countermeasure work. In addition, the skill DB 45 records that maintenance worker Y is currently working in Building A.

The "rank" of skill level is determined by the number of times it has been performed, but because the difficulty of each task varies, an accurate skill level cannot be recorded based on the number of times it has been performed alone. Therefore, for highly difficult tasks, the weight of the points is increased compared to less difficult tasks, and this weighting is reflected in the number of times it has been performed, allowing the skills of maintenance personnel to be evaluated appropriately. Furthermore, although not shown in Figures 6 and 7, it is also possible to change the weighting of the points depending on the date and time of the task, such as by increasing the weighting of the points for the most recent task day, so that the most recent task content can be reflected in the next task.

The information management unit 20 manages the above-mentioned databases and updates them as needed.

2. Configuration of the information processing unit and a method for arranging a failure supporter Next, the configuration of each unit of the information processing unit 40 of the monitoring center 2 in this embodiment will be described in detail together with an explanation of the method for arranging a failure supporter in this embodiment. Note that the contents of each process of the information processing unit 40 described below are automatically executed by software using, for example, a CPU (Central Processing Unit).

First, when a malfunction occurs in the elevator 1, the receiving device 21 of the monitoring center 2 receives malfunction information including the identification number of the elevator 1 and the malfunction status. This malfunction information includes an error code issued by the elevator 1 itself, as well as information from a phone call from a resident or manager, or information from the mobile terminal 5 of a maintenance worker 4 dispatched to the site.

For example, when a malfunction occurs in elevator 1, maintenance worker 4 is dispatched to the site where the malfunction occurred and checks the malfunction condition. Maintenance worker 4 uses mobile terminal 5 to transmit the identification number of the elevator where the malfunction occurred, specification information such as the model, and malfunction condition information to monitoring center 2. Then, when the receiving device 21 in monitoring center 2 receives the malfunction information, it inputs the malfunction information to similar malfunction daily report search unit 27.

On the other hand, when an error code issued by the elevator 1 itself is input to the receiving device 21, the receiving device 21 inputs the error code and specification information including the identification number of the elevator 1 that issued the error code to the similar malfunction daily report search unit 27. Also, when the receiving device 21 receives malfunction information by phone from a resident or manager, the receiving device 21 inputs the malfunction information and specification information including the identification number of the elevator 1 to the similar malfunction daily report search unit 27.

The similar failure daily report search unit 27 checks the identification number of the failed elevator 1 against the elevator specification DB 23 to obtain specifications such as the model of the failed elevator 1 and the part model of the component equipment. Furthermore, the similar failure daily report search unit 27 searches and extracts failures similar to the occurred failure (similar failures) from the failure daily report DB 22 using the model of the elevator 1 and failure state information such as error codes and malfunction events as search conditions. If the similar failure daily report search unit 27 determines that there is no similar failure, it determines that there is no point in using past similar cases to investigate the cause of the failure, and the similar failure daily report search unit 27 reports this to a support center (not shown). When the support center is notified, the specialized engineer and the on-site maintenance staff 4 directly communicate with each other to investigate the cause of the failure.

Next, if a failure condition similar to the occurred failure condition is found in the past daily failure reports, the candidate cause device extraction unit 28 tabulates the extracted daily failure reports by failure causing device. Furthermore, the candidate cause device extraction unit 28 calculates the ratio by failure causing device using the number of extracted similar daily failure reports as the denominator and the tabulated failure causing device as the numerator, and outputs the ratio as the probability that the device is the cause of the occurred failure. In other words, the candidate cause device extraction unit 28 extracts candidate cause devices for the occurred failure with a probability.

Figure 8 is a diagram showing an example of the causative equipment and its probability extracted by the candidate causative equipment extraction unit 28. As shown in Figure 8, the candidate causative equipment extraction unit 28 calculates the probability for each causative equipment, such as "40%" for the causative equipment being an "encoder" and "20%" for the causative equipment being a "positect." The results calculated by the candidate causative equipment extraction unit 28 are sent to the cause investigation time calculation unit 29, the countermeasure work time calculation unit 30, and the part to be shipped selection unit 31.

The cause investigation time calculation unit 29 determines, for example, a group of multiple cause devices with probabilities calculated by the candidate cause device extraction unit 28, starting from the most probable and adding up to 70%, as a group of failure cause devices. The cause investigation time calculation unit 29 then compares the multiple cause devices listed in the group of failure cause devices with the standard cause investigation time by device DB 24, extracts the standard cause investigation time for each cause device, and calculates the total time. The cause investigation time calculation unit 29 stores the total time as the cause investigation time required to investigate the cause of the failure that has occurred.

On the other hand, the countermeasure work time calculation unit 30, like the cause investigation time calculation unit 29, determines multiple causing devices with probabilities calculated by the cause device candidate extraction unit 28, starting from the highest probability and adding them up to 70%, as a group of causing devices causing the failure. Then, the countermeasure work time calculation unit 30 compares the causing devices listed in the group of causing devices with the device-specific standard countermeasure work time DB 25, extracts the standard countermeasure work time for each causing device, and calculates the total time. The countermeasure work time calculation unit 30 stores the total time as the countermeasure work time required for the countermeasure work (parts replacement, adjustment) for the failure that has occurred.

The shipping target part selection unit 31, like the cause investigation time calculation unit 29 and the countermeasure work time calculation unit 30, determines multiple causing equipment with probabilities calculated by the cause equipment candidate extraction unit 28 as a group of fault causing equipment, adding up the number of causing equipment with the highest probability up to 70%. Then, the shipping target part selection unit 31 checks the causing equipment listed in the group of fault causing equipment against the elevator specification DB 23 and the part information DB 26, and extracts candidate parts that are likely to be required for repair (replacement) and adjustment of the faulty causing equipment as parts to be shipped. Then, the shipping target part selection unit 31 stores the parts to be shipped.

Furthermore, the outgoing part selection unit 31 stores the part type and part size and weight of the outgoing part managed in the part information DB 26 for the selected outgoing part. The outgoing part selection unit 31 also selects and stores a part storage base (address) from which the part can be shipped based on the inventory status of the part storage bases in various locations. If there are multiple part storage bases from which the part can be shipped, the outgoing part selection unit 31 selects multiple part storage bases as candidate locations for the part storage base.

Next, the transportation means selection unit 32 automatically selects and stores candidates for transportation means for the parts to be shipped selected by the parts to be shipped selection unit 31 based on the weight and size (packaging size) of each part to be shipped. FIG. 9 is a diagram showing an example of the selection criteria for the transportation means selected by the transportation means selection unit 32. For example, if the total weight of the parts to be shipped is less than 10 kg, the transportation means is a car, motorcycle, or bicycle, if it is 10 kg or more and less than 20 kg, a car or motorcycle, and if it is 20 kg or more, a car is selected. In addition, regarding the size of the packaged parts to be shipped, if it is less than 30 x 30 x 30 cm, a car, motorcycle, or bicycle is selected, if it is 30 x 30 x 30 cm or more and less than 50 x 50 x 50 cm, a car or motorcycle is selected, and if it is 50 x 50 x 50 cm or more, a car is selected. In this way, the transportation means selection unit 32 also selects possible candidates for transportation means according to the weight and size of each part to be shipped.

Next, the parts transport time calculation unit 33 inputs the address of the broken elevator 1, the address of the parts storage base for the parts to be shipped selected by the parts to be shipped selection unit 31, and the transport means selected by the transport means selection unit 32 to the external traffic condition providing system 6. The address of the broken elevator 1 is stored in the parts transport time calculation unit 33 and input to the traffic condition providing system 6 after being compared with the elevator specification DB 23.

When there are multiple parts storage bases selected by the delivery target parts selection unit 31, the parts transport time calculation unit 33 inputs multiple candidate parts storage base locations to the traffic condition providing system 6. Similarly, when multiple candidate transport means are selected by the transport means selection unit 32, the parts transport time calculation unit 33 inputs multiple transport means to the traffic condition providing system 6.

The traffic condition providing system 6 sets the address of the input parts storage base as the starting point and the address of the broken elevator 1 as the destination point, and inputs additional information such as travel time and traffic congestion information for each transportation means to the parts transport time calculation unit 33.

Figure 10 is an example of travel distance and congestion information for each transportation means output by the traffic condition providing system 6. The traffic condition providing system 6 calculates the travel distance from the address of the parts storage base location and the broken elevator 1, and outputs the travel distance and congestion information for each transportation means. Also, when there are multiple candidate parts storage bases, the travel distance and congestion information is output for each parts storage base.

The parts transport time calculation unit 33 selects and stores a combination of parts storage base and transportation means that allows transportation in the shortest travel time based on the travel distance and accompanying information such as congestion information output by the traffic condition providing system 6, and further stores the travel time as the parts transport time. The parts transport time calculation unit 33 then transmits information on the selected parts storage base, transportation means, and parts transport time to the automatic warehouse removal unit 34.

The automatic retrieval unit 34 specifies the parts storage base and transportation means selected by the parts transport time calculation unit 33, and automatically arranges for the retrieval of the parts to be retrieved. The retrieval arrangements from the automatic retrieval unit 34 are made, for example, by sending a notification of parts retrieval from the receiving device 21 to the selected parts storage base. This causes the transportation of the parts to be retrieval to begin from the parts storage base specified by the automatic retrieval unit 34 using the specified transportation means.

Next, the failure response time calculation unit 35 calculates the failure response time from the cause investigation time calculated by the cause investigation time calculation unit 29, the countermeasure work time calculated by the countermeasure work time calculation unit 30, and the part transport time calculated by the part transport time calculation unit 33. The failure response time is the total time from the start of cause investigation to the completion of countermeasure work (recovery work) for the failed elevator 1.

Figure 11 is a flow diagram showing a failure response time calculation method in the failure response time calculation unit 35. As shown in Figure 11, the cause investigation time calculated by the cause investigation time calculation unit 29 is first input to the failure response time calculation unit 35 (step S351). Here, the cause investigation time for the causative device with a total probability of failure cause of 70% is input.

Next, the countermeasure work time calculated by the countermeasure work time calculation unit 30 is input to the failure response time calculation unit 35 (step S352). Here, the countermeasure work time for the causative devices with a total probability of failure cause of 70% is input.

Next, the part transport time calculated by the part transport time calculation unit 33 is input to the failure response time calculation unit 35 (step S353). Here, the part transport time of the candidate part for the causative device with a total probability of the failure cause of 70% is input.

Next, the failure response time calculation unit 35 compares the cause investigation time with the parts transport time (step S354). If the answer is "YES" in step S354, that is, if it is determined that the cause investigation time is shorter than the parts transport time, the sum of the parts transport time and the countermeasure work time is calculated as the failure response time (step S356). That is, in this case, the total failure response time is calculated taking into account that even when the cause investigation is completed, there is still time until the parts arrive.

On the other hand, if step S356 returns "NO," i.e., if it is determined that the cause investigation time is longer than the parts transport time, the sum of the cause investigation time and the countermeasure work time is calculated as the failure response time (step S355). That is, in this case, the total failure response time is calculated taking into account that the necessary parts have arrived at the site before the cause investigation is completed.

In this way, the failure response time calculation unit 35 can calculate a more accurate failure response time by considering the relationship between the overlapping parts of the cause investigation time, the countermeasure work time, and the part transport time. The failure response time calculated as shown in FIG. 11 is then input to the maintenance personnel arrangement unit 41 and the supporter necessity determination unit 36.

The maintenance worker arrangement unit 41 arranges for a maintenance worker when a maintenance worker has not yet been arranged at the site. For example, after a malfunction of the elevator 1 occurs, if the malfunction condition is entered into the similar malfunction daily report search unit 27 from an error code issued by the elevator 1 itself or information from a resident or manager, a maintenance worker 4 may not yet be arranged at the site. In this case, the maintenance worker arrangement unit 41 arranges for the maintenance worker 4. For example, if the malfunction information entered into the similar malfunction daily report search unit 27 was entered from the maintenance worker's mobile terminal 5, it is determined that the maintenance worker has already arrived at the site, and the maintenance worker arrangement unit 41 does not arrange for a maintenance worker.

The maintenance worker dispatching unit 41 compares the model of the faulty elevator 1 and the faulty equipment listed in the faulty equipment group with the skills DB 45, and selects as maintenance worker candidates those with the skills to handle the fault of the faulty equipment listed in the faulty equipment group. In addition, based on the address information of the elevator 1 and the current location information of the maintenance worker candidates, for example, the maintenance worker candidate who can arrive at the site the soonest is dispatched as the maintenance worker.

When a maintenance worker is selected by the maintenance worker dispatching unit 41, the maintenance worker 4's mobile terminal 5 is contacted via the failure response information transmitting unit 37 and the receiving device 21, which will be described later. The maintenance worker 4 inputs whether or not he/she can be dispatched to the mobile terminal 5, and if possible, moves to the site and starts work. The response from the mobile terminal 5 of the maintenance worker 4 regarding whether or not he/she can be dispatched is input to the maintenance worker dispatching unit 41 via the receiving device 21.

On the other hand, if the maintenance worker dispatching unit 41 receives input from the dispatched maintenance worker 4 that the dispatch is not possible, or if it determines that there is no response from the dispatched maintenance worker 4 for a certain period of time, the maintenance worker dispatching unit 41 refers to the skill DB 45 and dispatches the next maintenance worker 4 determined to be suitable from among the maintenance worker candidates. The maintenance worker dispatching unit 41 continues to dispatch the maintenance worker 4 until the dispatch of the maintenance worker 4 is possible.

The supporter necessity determination unit 36 determines whether or not it is necessary to arrange for a supporter based on the inputted failure response time. A supporter refers to a maintenance worker who supports the work of the maintenance worker working on-site. The supporter necessity determination unit 36 determines that a supporter is not necessary if the failure response time is less than a predetermined time, for example, three hours. If the supporter necessity determination unit 36 determines that a supporter is not necessary, it transmits various information extracted in each process to the failure response information transmission unit 37 without arranging for a supporter.

On the other hand, if the time required to respond to the failure is a predetermined time, for example, 3 hours or more, the supporter necessity determination unit 36 determines that supporter is needed and transmits the determination result to the supporter arrangement unit 38.

The supporter arrangement unit 38 arranges an appropriate supporter according to the time required for investigating the cause and the time required for implementing countermeasures. Figure 12 is a flow chart for explaining the method for arranging a failure response supporter in the failure response supporter arrangement system of this embodiment.

When the supporter necessity determination unit 36 determines that a supporter is necessary, the flow in FIG. 12 starts in the supporter arrangement unit 38. In this embodiment, when the failure response time is 3 hours or more, the supporter arrangement unit 38 arranges a supporter.

The supporter arrangement unit 38 first determines whether the cause investigation time and the countermeasure work time are both 90 minutes or more (step S381). If the answer is "YES" in step S381, that is, if the cause investigation time and the countermeasure work time are both 90 minutes or more, the supporter arrangement unit 38 selects and arranges a cause investigation skill holder and a countermeasure work skill holder from the skill DB 45 as supporters (step S387). In this embodiment, an example of a cause investigation skill holder is maintenance worker X shown in FIG. 6, and an example of a countermeasure work skill holder is maintenance worker Y shown in FIG. 7.

If the answer is "NO" in step S381, i.e., if either the cause investigation time or the countermeasure work time is less than 90 minutes, it is determined whether only the cause investigation time is 90 minutes or more (step S382). If the answer is "YES" in step S382, i.e., if only the cause investigation time is 90 minutes or more, the support person arrangement unit 38 selects a person with cause investigation skills from the skill DB 45 as a support person and arranges for them (step S386).

On the other hand, if the answer is "NO" in step S382, i.e., if the cause investigation time is less than 90 minutes, it is next determined whether only the countermeasure work time is 90 minutes or more (step S383). If the answer is "YES" in step S383, i.e., if the countermeasure work time is 90 minutes or more, the support person arrangement unit 38 selects a person with countermeasure work skills from the skill DB 45 as a supporter and arranges them (step S385).

On the other hand, if the answer is "NO" in step S383, i.e., if the countermeasure work time is less than 90 minutes, the part transport time will be too long, and the support worker arrangement unit 38 will determine that it is not necessary to arrange for a support worker (step S384).

Here, the procedure for selecting a cause investigation skill holder and/or a countermeasure work skill holder in steps S387, S386, and S385 will be described. When selecting a cause investigation skill holder, the supporter arrangement unit 38 selects, from the skill DB 45, a maintenance worker (cause investigation skill holder) who has a higher rank in the number of times of experience in cause investigation for the model of the failed elevator 1 and the causative device as the cause investigation supporter. For example, maintenance worker X, who has the work experience shown in FIG. 6, has a higher cause investigation rank than maintenance worker Y, who has the work experience shown in FIG. 7. Therefore, in this case, maintenance worker X is selected as the cause investigation supporter.

When arranging a cause investigation supporter 7, it is preferable to select the cause investigation skill holder with the shortest travel time based on the address of the broken elevator 1 and the current location of the cause investigation skill holder. This allows the cause investigation to begin at an earlier stage. Therefore, when there are multiple cause investigation skill holders, the supporter arrangement unit 38 selects the cause investigation skill holder with the shortest travel time as the cause investigation supporter 7.

When selecting a countermeasure work skill holder, the supporter arrangement unit 38 selects, from the skill DB 45, a maintenance worker (countermeasure work skill holder) who has a higher rank in the number of times of experience with countermeasure work such as repair and adjustment for the model of the faulty elevator 1 and the causative device, as the countermeasure work supporter. For example, maintenance worker Y, who has the work experience shown in FIG. 7, has a higher rank in countermeasure work than maintenance worker X, who has the work experience shown in FIG. 6. Therefore, in this case, maintenance worker Y is selected as the countermeasure work supporter.

Countermeasure work is started after the cause investigation and parts transportation are completed. For this reason, it is preferable to select as the countermeasure work assistant 8 the countermeasure work skill holder with the highest skill level for countermeasure work from among the countermeasure work skill holders who can arrive before the countermeasure work starts. In other words, when selecting a countermeasure work assistant 8, the assistant arrangement unit 38 selects the countermeasure work skill holder with the highest level from among multiple countermeasure work skill holders who can arrive at the site by a specified time. This can improve the efficiency of the countermeasure work.

When a cause investigation supporter and/or countermeasure work supporter is selected in the supporter arrangement unit 38, the selection result is transmitted to the mobile terminal 5 of the selected cause investigation supporter 7 and/or countermeasure work supporter 8 via the failure response information transmission unit 37 and the receiving device 21. The selected cause investigation supporter 7 and/or countermeasure work supporter 8 inputs whether or not they will be dispatched in response to the received support request from their own mobile terminal 5 and transmits this to the monitoring center 2. The whether or not they will be dispatched transmitted to the monitoring center 2 is input to the supporter arrangement unit 38.

If the selected cause investigation supporter 7 and/or countermeasure work supporter 8 are unable to be dispatched, the supporter arrangement unit 38 again selects a cause investigation supporter 7 and/or countermeasure work supporter 8. In this case, the selection is again performed by excluding the maintenance personnel who were unable to be dispatched, by comparing the model of the broken elevator 1 and the causative device with the necessary support content against the skill DB 45, and selecting a new cause investigation supporter 7 and/or countermeasure work supporter 8.

In addition, if the selected cause investigation supporter 7 and/or countermeasure work supporter 8 are working at another site, they may not be able to operate from the mobile terminal 5. Therefore, if there is no response from the cause investigation supporter 7 and/or countermeasure work supporter 8 to a request for support for a certain period of time, the supporter arrangement unit 38 determines that the selected cause investigation supporter 7 and/or countermeasure work supporter 8 cannot be dispatched. In this case, excluding the maintenance personnel who could not be dispatched, the model and causative device of the broken elevator 1 and the necessary support content are again compared with the skill DB 45, and a new cause investigation supporter 7 and/or countermeasure work supporter 8 is selected.

Next, in steps S387 and S386, if a person with cause investigation skills is selected and arranged as a cause investigation supporter 7, the supporter arrangement unit 38 determines whether the cause investigation supporter 7 arranged before the start of the cause investigation can arrive at the site (step S388).

In step S388, the arrival time of the arranged cause investigation supporter 7 at the site is calculated from the location information of the arranged cause investigation supporter 7, the current work status of the arranged cause investigation supporter 7, and the means of transportation, and is used for the judgment. If the judgment in step S388 is "YES", that is, if it is judged that the cause investigation supporter 7 can arrive before the cause investigation begins, the supporter arrangement unit 38 sends a command to wait for the arrival of the cause investigation supporter 7 to the maintenance worker 4 at the site (step S390).

On the other hand, if the result of step S388 is "NO," that is, if it is determined that the cause investigation supporter 7 cannot arrive before the cause investigation begins, the supporter arrangement unit 38 switches the cause investigation support to remote rear support (step S389). In this case, the arranged cause investigation supporter 7 may be requested to respond by telephone, etc., or a maintenance worker capable of rear support may be arranged as a new cause investigation supporter 7. In the case of rear support, there is no need to take into account the current location of a cause investigation skill holder when selecting a cause investigation supporter 7.

In this manner, the supporter arrangement unit 38 selects and arranges for the cause investigation supporter 7 and/or countermeasure work supporter 8. Information output from the supporter arrangement unit 38 is sent via the failure response information transmission unit 37 and the receiving device 21 to the on-site maintenance worker 4 and the mobile terminal 5 of the relevant cause investigation supporter 7 and/or countermeasure work supporter 8.

The failure response information transmission unit 37 transmits various information extracted and stored by the information processing unit 40 to the mobile terminal 5 of the maintenance personnel 4 and the corresponding cause investigation supporter 7 and/or countermeasure work supporter 8 via the receiving device 21. FIG. 13 shows an example of information transmitted by the failure response information transmission unit 37 to the mobile terminal 5 of the maintenance personnel 4 and the corresponding cause investigation supporter 7 and/or countermeasure work supporter 8. For example, as shown in FIG. 13, the failure response information transmission unit 37 transmits a group of candidates for the equipment causing the failure, the probability that each equipment is the cause of the failure, inventory information, parts information, the cause investigation time, the countermeasure work time, the parts transport time (arrival time), and the supporter arrangement status. The maintenance personnel 4 and the corresponding cause investigation supporter 7 and/or countermeasure work supporter 8 start work at the site based on the information transmitted to the mobile terminal 5.

After completing their work, the maintenance personnel 4 can update the daily failure report DB by inputting a daily failure report from their mobile terminal 5. In addition, after completing their work, the maintenance personnel 4 and the corresponding cause investigation supporter 7 and/or countermeasure work supporter 8 input information about the model of equipment on which the maintenance work was performed, the device causing the problem, and the work content from their respective mobile terminals 5. This updates the skill DB 45 of the maintenance personnel who performed the maintenance work.

In this embodiment, when cause investigation support is required, a person with cause investigation skills who is good at cause investigation is selected as the cause investigation supporter, and when countermeasure work support is required, a person with countermeasure work skills who is good at countermeasure work is selected and arranged as the countermeasure work supporter. This allows more suitable maintenance personnel to be dispatched to the site as supporters, improving work efficiency.

In addition, in this embodiment, when the failure response time calculation unit 35 calculates the failure response time, if a maintenance worker has not yet been dispatched to the site, the model of the failed elevator and the device causing the failure can be checked against the skill DB 45, and an appropriate maintenance worker can be selected and dispatched. This allows for more appropriate selection of maintenance workers to work on site, improving work efficiency.

In addition, in this embodiment, the time required to investigate the cause of the failure to identify the cause of the failure is calculated separately from the time required to take corrective action such as adjusting the equipment causing the failure and replacing parts. Then, based on the relationship between the time required to investigate the cause, the time required for corrective action, and the time required to transport parts, the failure response time required from the start of the investigation into the cause to the completion of the corrective action (recovery work) is calculated. As a result, if there is an overlap between the time required to investigate the cause and the time required to transport parts, this overlapping time is not included in the failure response time, so an accurate failure response time can be obtained. This makes it possible to accurately determine whether or not backup is required, such as arranging for support personnel, and improves the efficiency of elevator recovery.

In addition, in this embodiment, candidate causative devices are extracted with a probability, and the candidate causative devices whose total probability is equal to or greater than a predetermined value are regarded as a group of causative devices, and the time required to investigate the cause, the time required to take countermeasures, and the time required to transport parts for the group of causative devices can be estimated. This allows maintenance personnel to be notified of the candidate causative devices in advance before they start an on-site cause investigation, and allows the transportation of parts required for adjusting or replacing the parts of the candidate causative devices to be started. As a result, the time required to respond to a failure can be shortened.

In this embodiment, when extracting a group of fault-causing devices, one or more fault-causing devices that add up to 70% of the probability from highest to lowest are selected as the group of fault-causing devices, but this ratio is just an example and can be changed as appropriate. Also, in this embodiment, an example is shown in which a cause investigation assistant and/or a countermeasure work assistant are selected one by one as needed, but a configuration in which multiple assistants are arranged depending on the difficulty of the work content is also possible.

In this embodiment, the fault response supporter dispatch system 100 is configured by elevators or other elevators, mobile terminals carried by maintenance personnel, a monitoring center, and a traffic condition providing system, but is not limited to this. The present invention only requires a configuration that can realize the configuration of the information management unit and information processing unit configured in the monitoring center.

The above-mentioned embodiment has been described in detail to clearly explain the present invention, and is not necessarily limited to having all of the configurations described. For example, it is possible to replace part of the configuration of the embodiment with another configuration, and it is also possible to add another configuration to the configuration of the embodiment. It is also possible to add, delete, or replace part of the configuration of the embodiment with another configuration.

1...Elevator, 2...Monitoring center, 4...Maintenance staff, 5...Mobile terminal, 6...Traffic condition information system, 11...Control panel, 12...Remote monitoring device, 20...Information management department, 21...Receiving device, 23...Elevator specification DB, 22...Daily failure report DB, 23...Elevator specification DB, 24...Standard cause investigation time by equipment DB, 25...Standard countermeasure work time by equipment DB, 26...Parts information DB, 45...Skill DB, 27...Search for similar daily failure reports 28...candidate causal device extraction unit, 29...cause investigation time calculation unit, 30...countermeasure work time calculation unit, 31...delivery target part selection unit, 32...transportation means selection unit, 33...parts transport time calculation unit, 34...automatic delivery unit, 35...fault response time calculation unit, 36...assistant necessity determination unit, 37...fault response information transmission unit, 38...assistant arrangement unit, 40...information processing unit, 41...maintenance worker, arrangement unit 100...fault response supporter arrangement system

Claims (10)

A system for dispatching support personnel to assist with breakdowns that occur in elevators and escalators, the system collating past daily breakdown reports to calculate a breakdown response time, and dispatching support personnel to assist on-site maintenance personnel in accordance with the breakdown response time,
a daily failure report management unit that accumulates past daily failure reports regarding failures occurring in elevators, the past daily failure reports including at least a failure state, a device causing the failure, a cause investigation time, a countermeasure work time, and an identification number of the elevator;
an elevator specification management unit in which specification information of an elevator, including at least an identification number, a model, a component device, and address information of the elevator, is stored;
A device-specific standard cause investigation time management department that accumulates standard cause investigation times for each elevator model and component device;
an equipment-specific standard countermeasure work time management unit that accumulates standard countermeasure work times for each elevator model and each component device;
a skill management unit that accumulates information on skills possessed by each maintenance worker at least related to elevator maintenance work;
a cause device candidate extraction unit that extracts cause device candidates of the occurring failure with a probability from the daily failure reports accumulated in the daily failure report management unit and the failure state of the failed elevator;
a cause investigation time calculation unit which sets, among the cause device candidates extracted by the cause device candidate extraction unit, cause device candidates whose sum of the probabilities is equal to or greater than a predetermined value as a failure cause device group, compares each cause device listed in the failure cause device group with the device-specific standard cause investigation time management unit, extracts the standard cause investigation time for each cause device, and calculates the total of the standard cause investigation times for each cause device as a cause investigation time;
a countermeasure work time calculation section for comparing each of the cause devices listed in the failure cause device group with the device-specific standard countermeasure work time management section to extract the standard countermeasure work time for each of the cause devices and for calculating a total of the standard countermeasure work times for each of the cause devices as a countermeasure work time;
a supporter arrangement unit that selects a maintenance worker having cause investigation skills as a cause investigation supporter and/or a maintenance worker having cause investigation skills as a cause investigation supporter from information accumulated in the skill management unit according to the cause investigation time and the cause investigation time;
A system for dispatching support personnel to handle breakdowns. and a parts transport time calculation unit that calculates a parts transport time based on the address of a parts storage base where parts necessary to deal with the failure of each of the failure causing devices in the failure causing device group are stored, the address of the elevator where the failure has occurred, and traffic information input from outside.
2. The system for dispatching a troubleshooting support person according to claim 1. 2. The failure response supporter dispatching system according to claim 1, wherein, when the countermeasure work time and the cause investigation time are longer than a predetermined time, the supporter dispatching unit selects, from the information accumulated in the skill management unit, a maintenance worker who has the cause investigation skill as the cause investigation supporter, and selects a maintenance worker who has the countermeasure work skill as the countermeasure work supporter. The failure response supporter dispatching system of claim 1, wherein the supporter dispatching unit selects a maintenance worker who possesses the cause investigation skills as the cause investigation supporter from information accumulated in the skill management unit when only the cause investigation time is longer than a predetermined time. 2. The fault response supporter dispatching system according to claim 1, wherein the supporter dispatching unit selects, from information accumulated in the skill management unit, a maintenance worker who has the countermeasure work skills as the countermeasure work supporter when only the countermeasure work time is longer than a predetermined time. The failure response supporter dispatching system of claim 3 or 4 , wherein when the supporter dispatching unit selects the cause investigation supporter, the unit calculates the travel time of the maintenance personnel who possess the cause investigation skill from the address information of the broken elevator and the current location of the maintenance personnel who possess the cause investigation skill, and selects the maintenance personnel who possess the cause investigation skill and has the shortest travel time as the cause investigation supporter. 6. The failure response supporter dispatching system of claim 5, wherein when the supporter dispatching unit selects the countermeasure work supporter, the supporter dispatching unit calculates the travel time of the maintenance worker who possesses the countermeasure work skill from the address information of the broken elevator and the current location of the maintenance worker who possesses the countermeasure work skill, and selects as the countermeasure work supporter the maintenance worker who possesses the countermeasure work skill and has the highest skill level among the maintenance workers who possess the countermeasure work skill and can arrive by a specified time. 3. The failure response supporter dispatching system according to claim 2, further comprising a failure response time calculation unit that calculates the sum of the part transport time and the countermeasure work time as the failure response time when the cause investigation time is shorter than the part transport time, and calculates the sum of the cause investigation time and the countermeasure work time as the failure response time when the cause investigation time is longer than the part transport time. A supporter necessity determination unit is provided for determining whether or not a supporter needs to be arranged based on the failure response time calculated by the failure response time calculation unit.
9. The system for dispatching a troubleshooting support person according to claim 8. a daily failure report management unit that accumulates past daily failure reports regarding failures occurring in elevators, the past daily failure reports including at least a failure state, a device causing the failure, a cause investigation time, a countermeasure work time, and an identification number of the elevator;
an elevator specification management unit in which specification information of an elevator, including at least an identification number, a model, a component device, and address information of the elevator, is stored;
A device-specific standard cause investigation time management department that accumulates standard cause investigation times for each elevator model and component device;
an equipment-specific standard countermeasure work time management unit that accumulates standard countermeasure work times for each elevator model and each component device;
A failure response supporter dispatching system including a skill management unit that accumulates, for each maintenance worker, at least information on skills possessed by the maintenance worker regarding maintenance work for an elevator,
extracting, with a probability, possible causative devices of the occurring failure from the daily failure reports stored in the daily failure report management unit and the failure state of the failed elevator;
Among the extracted cause device candidates, those with the sum of the probabilities equal to or greater than a predetermined value are set as a failure cause device group, and each cause device listed in the failure cause device group is collated with the device-specific standard cause investigation time management unit to extract the standard cause investigation time for each cause device, and the total of the standard cause investigation times for each cause device is calculated as the cause investigation time; each cause device listed in the failure cause device group is collated with the device-specific standard countermeasure work time management unit to extract the standard countermeasure work time for each cause device, and the total of the standard countermeasure work times for each cause device is calculated as the countermeasure work time;
a cause investigation supporter and/or a countermeasure work supporter is selected from the information stored in said skill management unit according to said countermeasure work time and said cause investigation time.

Images