KR20210101327A - Failure support device, failure support program stored in recording media and failure support method - Google Patents

Abstract

The history extraction unit 12 obtains a failure code 050 from the elevator control device 500 and extracts a plurality of failure records 32a having the same failure code as the failure code 050 from the failure history DB 32 . to generate the number of times information 12a. The coupling unit 13 acquires a failure response sequence 31a having the same failure code as the failure code 050 from the failure response sequence DB 31 in which the failure response sequence 31a is registered, and the failure response sequence 31a ), the number of records of records corresponding to the cause of the number information 12a is combined with the same process cause as the cause of the number information 12a. The order change unit 14 replaces the order of the steps included in the failure coping procedure 31a based on the number of records associated with the process cause, and outputs a failure coping procedure 31a-1 in which the order of the steps is replaced. do.

Description

Failure support device, failure support program, and failure support method

The present invention relates to a failure support device, a failure support program, and a failure support method.

In the prior art, when an elevator breaks down, in order to shorten the recovery time, there is a method of retrieving past failure cases to obtain a failure response (for example, Patent Document 1).

However, as in the case of replacing the substrate, there is a failure response in which the operation sequence is determined, such as first measuring the voltage, then confirming the connection of the wiring, and then replacing the substrate. In the prior art, it was not possible to flexibly adapt to the failure response in which the work order was fixed.

Further, since the prior art does not consider the working position, it is possible to provide a failure response in the same order as on the cage, on the pit, and on the cage. Response to these failures results in travel time wasted.

[Patent Document 1] Japanese Patent No. 5820072

An object of the present invention is to provide an apparatus and method for suggesting a failure response sequence that can be flexibly adapted to a failure response in which the operation sequence is determined.

The failure support device of the present invention comprises:

Acquire a fault code for identifying the fault content of the device from a control device that controls the device, and from a record storage device having a plurality of records including the fault code and a cause of the fault, the fault code identical to the acquired fault code an extracting unit for extracting a plurality of the records including

The fault code, a group of processes having a plurality of sequentially executed steps and in which there is an interchangeable step in the sequence when the plurality of steps are continuously performed, and a process cause indicating a cause of a failure associated with each step The failure response sequence including the same failure code as the acquired failure code is acquired from the sequence storage device in which a plurality of failure response sequences are registered, and the number of times information among the process causes included in the failure response sequence has a combining unit for combining the number of records of the record corresponding to the cause of the number information with the process cause such as the cause;

A replacement unit that replaces the sequence of the process in which the sequence can be replaced, based on the number of records coupled to the process cause, and outputs the failure response sequence in which the sequence of the process is replaced

to provide

According to the failure support apparatus of the present invention, it is possible to present a failure response sequence that can be flexibly adapted to a failure response in which the operation sequence is determined.

1 is a diagram of the first embodiment, and is a diagram showing functional blocks of a failure support apparatus 100 .
FIG. 2 is a diagram of the first embodiment, and is a diagram showing a hardware configuration of the failure support apparatus 100 .
Fig. 3 is a diagram of the first embodiment, and is a flowchart for explaining the operation of the failure support device 100;
Fig. 4 is a diagram of the first embodiment, showing a failure response procedure 31a.
Fig. 5 is a diagram of the first embodiment, showing the format of the failure record 32a.
Fig. 6 is a diagram of the first embodiment, showing failure record information 32b formed from a plurality of failure records 32a.
FIG. 7 is a diagram of the first embodiment, and schematically shows a state in which a failure record with a failure code (032) = 001 is extracted with respect to FIG. 6;
Fig. 8 is a diagram of the first embodiment, showing the number of times information 12a.
9 is a diagram of the first embodiment, showing a state in which the process 83 of the substrate A and the process 84 of the substrate B are replaced by the order change unit 14 in the failure response procedure 31a. am.
10 is a diagram of the first embodiment, and is a diagram showing a failure response procedure 601 .
11 is a diagram of the first embodiment, and is a diagram showing a failure response procedure 602 .
12 is a diagram of the first embodiment, and is a diagram showing a failure response procedure 603 .
13 is a diagram of the first embodiment, and is a diagram showing a failure response procedure 604 .
14 is a diagram of the first embodiment, and is a diagram showing a failure response procedure 605 .
15 : is a figure of Embodiment 1, and is a figure which shows the model installation information 33a which elevator specification DB33 has.
FIG. 16 is a diagram of the first embodiment, and shows the combination information 35 .
17 is a diagram of the first embodiment, and is a diagram showing an extraction result from the combined information 35 .
Fig. 18 is a diagram of the first embodiment, showing an extraction result in which records having different causes are also extracted.
19 is a diagram of the first embodiment, and is a diagram showing a configuration in which a function of the failure support device 100 is realized by hardware.

EMBODIMENT OF THE INVENTION Hereinafter, embodiment of this invention is described using drawings. In addition, in each figure, the same code|symbol is attached|subjected to the same or corresponding part. In the description of the embodiment, the description is appropriately omitted or simplified about the same or corresponding parts.

(1) In the following, the failure response sequence database 31, the failure history database 32 and the elevator specification database 33 are, respectively, the failure response sequence DB 31, the failure history DB 32, and the elevator specification DB ( 33). The failure response procedure DB 31 stores the failure response procedure 31a. The failure history DB 32 stores failure record information 32b. The elevator specification DB 33 stores elevator specifications.

(2) In the following, a fault code appears. The failure code includes a failure code described in the failure response procedure 31a, a failure code generated by the elevator control device 500, and a failure code possessed by the failure record 32a. These fault codes are denoted by a fault code 031 , a fault code 050 , and a fault code 032 , respectively. The fault code is a code for identifying the contents of the fault. The same fault code indicates that the fault content is the same. For example, when the failure code 031 = [001] and the failure code 050 = [001], the failure contents of the failure response procedure 31a and the failure contents of the elevator control device 500 are the same.

(3) Hereinafter, a failure cause corresponding to each step of the failure response procedure 31a is expressed as a process cause. The cause described in the failure record 32a is simply indicated as a cause.

(4) Hereinafter, the interface is denoted as IF.

(Embodiment 1)

A failure support apparatus 100 according to the first embodiment will be described with reference to FIGS. 1 to 15 .

***Description of configuration***

1 shows a functional block of the failure support apparatus 100 .

2 shows a hardware configuration of the failure support apparatus 100 .

The failure support device 100 is a computer. The failure support device 100 includes a processor 10 , and also includes other devices such as a main memory device 20 , an auxiliary storage device 30 , an input IF 40 , an output IF 50 and a communication IF 60 . hardware is provided. The processor 10 is connected to other hardware via a signal line 70, and controls these other hardware.

The failure support apparatus 100 includes a registration accepting unit 11 , a history extracting unit 12 , a combining unit 13 , and an order changing unit 14 as functional elements. The history extraction unit 12 is an extraction unit. The order change unit 14 is a replacement unit.

The functions of the registration accepting unit 11 , the history extracting unit 12 , the combining unit 13 , and the order changing unit 14 are realized by the failure support program 101 .

The processor 10 is a device that executes the failure support program 101 . The failure support program 101 is a program for realizing the functions of the registration accepting unit 11 , the history extracting unit 12 , the combining unit 13 , and the order changing unit 14 . The processor 10 is an IC (Integrated Circuit) that performs arithmetic processing. Specific examples of the processor 10 are a CPU (Central   Processing Unit), DSP (Digital   Signal Processor), and GPU (Graphics   Processing Unit).

The main memory device 20 is a memory device. Specific examples of the main memory device 20 are SRAM (Static Random Access Memory) and DRAM (Dynamic Random Access Memory). The main memory 20 holds the operation result of the processor 10 .

The auxiliary storage device 30 is a storage device for non-volatile storage of data. A specific example of the auxiliary storage device 30 is a Hard Disk Drive (HDD). In addition, the auxiliary storage device 30 is a SD (registered trademark) (Secure Digital) memory card, NAND flash, flexible disk, optical disk, compact disk, Blu-ray (registered trademark) disk, DVD (Digital Versatile Disk) such as A transportable recording medium may be used. The auxiliary storage device 30 stores a failure response procedure DB 31 , a failure history DB 32 , an elevator specification DB 33 , and a failure support program 101 . In addition, data such as the failure response sequence DB 31 , the failure history DB 32 , the elevator specification DB 33 , and the failure support program 101 are stored in other devices such as a cloud server and the failure support device 100 . may be obtained from another device. The auxiliary storage device 30 is a record storage device, a sequence storage device, and an elevator specification storage device.

The input IF 40 is a port to which an input device 200 such as a mouse or keyboard is connected, and data is inputted from each device.

The output IF 50 is a port to which various devices are connected and data is output by the processor 10 to the various devices. In FIG. 2 , the display device 300 is connected to the output IF 50 .

The communication IF 60 is a communication port for the processor to communicate with other devices. In FIG. 2 , the maintenance terminal 400 and the elevator control device 500 are connected to the communication IF 60 .

The processor 10 loads the failure support program 101 from the auxiliary storage device 30 into the main memory device 20 , and reads and executes the failure support program 101 from the main memory device 20 . In the main memory device 20, not only the failure support program 101 but also an OS (Operating System) is stored. The processor 10 executes the failure support program 101 while executing the OS.

The failure support apparatus 100 may include a plurality of processors replacing the processor 10 . These plurality of processors share execution of the failure support program 101 . Each processor, like the processor 10 , is a device that executes the failure support program 101 . Data, information, signal values, and variable values used, processed, or output by the failure support program 101 are stored in the main memory device 20 , the auxiliary memory device 30 , or a register or cache memory device in the processor 10 . do.

The failure support program 101 changes "part" of the registration reception unit 11, the history extraction unit 12, the coupling unit 13 and the order change unit 14 to "process", "sequence" or "process" A program that causes a computer to execute each process, each sequence, or each process.

In addition, the failure support method is a method performed when the failure support apparatus 100 which is a computer executes the failure support program 101 . The failure support program 101 may be stored and provided in a computer-readable recording medium, or may be provided as a program product.

***Description of action***

3 is a sequence for explaining the operation of the failure support apparatus 100 . An operation of the failure support apparatus 100 will be described with reference to FIG. 3 . The operation of the failure support apparatus 100 corresponds to a failure support method. In addition, the operation of the failure support apparatus 100 corresponds to the processing of the failure support program.

<Step S11>

In step S11 , the manager 210 registers the failure response procedure 31a in the registration reception unit 11 using the input device 200 such as a keyboard or mouse. The registration accepting unit 11 accepts registration of the failure response procedure 31a. The manager 210 registers the failure response procedure 31a for each failure code 031 . The registration accepting unit 11 stores the failure response procedure 31a in the failure response procedure DB 31 .

4 shows a failure response procedure 31a. The manager 210 sets whether or not the order replacement is possible with respect to the process at the time of registration of the failure response procedure 31a.

The registration accepting unit 11 sets the replacement possibility of the process designated as interchangeable in the failure response procedure 31a.

The registration accepting unit 11 receives a setting instruction for a replaceable process, sets the replaceable process indicated by the setting instruction in the failure response sequence 31a, and registers the failure response sequence 31a in the sequence storage device. . In the failure support device 100 , the sequence storage device is the auxiliary storage device 30 . In FIG. 4 , the interchangeable steps are steps 83 and 84 . The failure response procedure 31a of FIG. 4 will be described. The failure response procedure 31a is information that the manager 210 registers in the registration reception unit 11 using the input device 200 . The failure response procedure 31a includes a failure code 031 and a plurality of steps 81 to 84 that are continuously executed. In the failure response procedure 31a, there are steps 83 and 84 in which the sequence can be exchanged when continuously implemented from the step 81 to the step 84. Steps 81 to 84 are steps. The failure response procedure 31a includes process causes and measures indicating the failure causes associated with each process.

(1) In step 81, it is determined whether the voltage is normal. If yes, processing proceeds to step 82 . If 'No', it is determined whether improvement is achieved by re-powering the power supply. If 'No', the process proceeds to step 82. If 'Yes', the process cause of power failure is obtained.

(2) In step 82, it is determined whether the wiring is normal. If yes, the process proceeds to step 83 . If 'No', the process cause of lead wire failure is obtained.

(3) In step 83, the improvement result of the board|substrate A is judged. If no, processing proceeds to step 84 . In the case of 'Yes', the process cause of the defect of the substrate A is obtained.

(4) In the process 84, the improvement result of the board|substrate B is judged. If 'no', an unknown process cause is obtained. In the case of 'Yes', the process cause of the defect of the substrate A is obtained.

<Step S12>

The elevator control device 500 outputs a failure code 050 in case of failure.

<Step S13>

The history extracting unit 12 acquires a failure code for identifying the content of the failure of the apparatus from the control device that controls the apparatus. Also, an elevator is an example of a device. An elevator control device is an example of a control device. The history extraction unit 12 extracts, from the record storage device having a plurality of records including the failure code and the cause of the failure, a plurality of records containing the same failure code as the obtained failure code, and calculates the number of records for each cause. Generates information on the number of times matched.

Specifically, it is as follows. In step S13, the history extraction unit 12 extracts a failure record 32a having a failure code 032 matching the failure code 050 from the failure history DB 32 having a past failure history. A fault record is a record containing the fault code and the cause of the fault.

5 shows the format of the failure record 32a. The failure record 32a has each item of a building, a unit unit, a failure code 032, and an action. Building represents a building in which an elevator is installed. The exhalation represents the exhalation of the elevator, that is, the cage. The fault code 032 is the same as described above. The processing refers to the cause of XX in the failure and the action YY for the cause. The cause of the failure is a defective circuit board, and the action is to replace the circuit board.

6 shows failure record information 32b composed of a plurality of failure records 32a. The failure record information 32b is stored in the failure history DB 32 .

<Step S14>

In step S14, the history extraction unit 12 counts the number of failure records for each cause of the extracted failure records 32a.

FIG. 7 schematically shows a state in which a failure record of failure code 032 = [001] is extracted with respect to FIG. 6 . The items of the building and unit of each failure record 32a are abbreviate|omitted. As can be seen from FIG. 7 , even if the failure code 032 is the same, there are failure records 32a with different causes. In Fig. 7, when the number of failure records 32a is counted for each cause, there are three records of cause 11A and one record of cause 12A.

8 shows the number of times information 12a. A failure code 032 is described in the number of times information 12a. The number of times information 12a is information indicating a result of the history extracting unit 12 counting the number of failure records 32a for each cause of the failure records 32a. In the failure record 32a of Fig. 8, there are 10 failure records 32a caused by a defective power supply, 40 failure records 32a due to a defective lead wire, and 40 failure records 32a due to a failure of the board A. It shows that there are 5 failure records 32a and 50 failure records 32a caused by the failure of the board B. The history extracting unit 12 sends the number of times information 12a to the combining unit 13 .

<Step S15>

The coupling unit 13 acquires, from the failure response procedure DB 31 , a failure response procedure 31a having the same failure code 031 as the failure code 032 described in the number information 12a.

<Step S16>

The coupling unit 13 acquires, from the auxiliary storage device 30, which is a sequence storage device, a fault response sequence including the same fault code as the fault code acquired from the control device. The combining unit 13 combines the number of records of records corresponding to the cause of the number information with the same process cause as the cause of the number information among the process causes included in the acquired failure response sequence.

Specifically, it is as follows. In step S16, the combining unit 13 combines the process cause (FIG. 4) described in the extracted failure response procedure 31a and the cause of the number information 12a. That is, the combination means that the number of times of the same cause is associated with the same process cause as the cause of the number information 12a among the process causes described in the failure response procedure 31a. Here, it is assumed that the number of times information 12a is that of FIG. 8 , and the failure response procedure 31a obtained by the coupling unit 13 from the failure response procedure DB 31 is the failure response procedure 31a of FIG. 4 . In this example, the coupling unit 13 associates the number of times 10 with the power failure in the failure response procedure 31a, associates the number 40 with the failure of the lead wire in the failure response procedure 31a, and the failure response procedure 31a. The number 5 corresponds to the failure of the substrate A of

In addition, the coupling unit 13 displays, on the display device 300, the cause of the process that is described in the number information 12a but is not registered in the failure response procedure 31a obtained in step S15, whereby the manager 210 notify to Alternatively, the data may be transmitted to an unillustrated manager terminal device possessed by the manager 210 . An example is a case where there is a defect in the substrate C as the cause of the number of times information 12a (Fig. 8), and there is no defect in the substrate C as the cause of the process in the failure response procedure 31a obtained in step S15. The manager 210 determines whether the addition is necessary, and revises the failure response procedure 31a of the failure code 031 = [001].

In this way, the coupling unit 13 generates a warning when a process corresponding to the cause of the number information 12a does not exist in the acquired failure response procedure 31a. In the form of generating the warning as described above, the warning may be displayed on the display device or transmitted to the manager terminal device, and any form may be used.

The coupling unit 13 sends to the order changing unit 14 a failure response procedure 31a in which the cause of the number information 12a is combined to the order changing unit 14 .

<Step S17>

The order change unit 14, which is a replacement unit, replaces the order of the processes in which the order can be replaced based on the number of records associated with the process cause, and outputs a failure response order in which the order of the processes is replaced. In addition, any form of outputting the failure response procedure may be used. The failure response procedure may be transmitted to the maintenance terminal, and the failure response procedure may be stored in the cloud server, stored in the auxiliary storage device 30 , or displayed on the display device 300 .

In step S17, the sequence change unit 14 replaces the replaceable process by referring to the number of process causes in the failure response sequence 31a in which the causes of the number information 12a are combined.

4 will be described as an example. When the causes of the number information 12a are combined, the number of times that each process cause of FIG. 4 is counted is the number shown in FIG. 8 . As shown in FIG. 4, the process 83 of the board|substrate A and the process 84 of the board|substrate B are interchangeable. The number of times to count the process causes corresponding to the process 83 of the substrate A is 5, and the number of times to count the process causes corresponding to the process 84 of the substrate B is 50 times. That is, the number of times of counting the steps 84 of the substrate B is greater than that of the substrate A, but this means that the number of failures of the substrate B is higher than that of the substrate A. Accordingly, the order change unit 14 replaces the process 83 of the substrate A and the process 84 of the substrate B with respect to the failure response procedure 31a of FIG. 4 , and the process 84 of the substrate B is changed to the substrate A The failure response sequence 31a is changed to be performed before the step 83 of

9 shows a failure response procedure 31a-1 in which the process 83 of the substrate A and the process 84 of the substrate B are replaced by the order change unit 14 in the failure response procedure 31a.

<Step S18>

In step S18 , the order change unit 14 transmits to the maintenance terminal 400 the post-change failure response procedure 31a - 1 in which the process 83 of the substrate A and the process 84 of the substrate B are exchanged.

<Step S19>

In step S19, the maintenance person takes action based on the failure response procedure 31a-1. The maintenance worker uses the maintenance terminal 400 to register a record in the failure history DB 32 in the form of a failure record 32a including the building, unit unit, and failure code, along with measures and causes that are implementation results. .

<Modification 1>

10 and 11 are states before the order change unit 14 changes the failure response order. Modification 1 of Embodiment 1 will be described with reference to FIGS. 10 and 11 . In the first modification, the procedure change unit 14 also refers to the tool corresponding to each step of the failure response procedure 601 and replaces the steps. Each process of the process 81 to the process 84 forming a process group corresponds to the tool used in the process. The order change unit 14, which is a replacement unit, replaces the order of the steps 83 and 84 in which the order can be replaced based on the order of the tools determined from the plurality of steps 81 to 84 that are continuously performed.

It will be described in detail below.

Fig. 10 is a failure response procedure 601 used in the first modification. The failure response procedure 601 is acquired by the order change unit 14 in step S17. The failure response procedure 601 accepts registration in step S11. The failure response procedure 601 is registered similarly to the failure response procedure 31a (step S11). The failure response procedures 602 to 605 described below are also registered in the same manner as the failure response procedure 31a, and the procedure change unit 14 acquires them in step S17. In the failure response procedure 601 of FIG. 10 , the tool corresponds to each process. The tool T1 corresponds to the step 81 of confirming the voltage. The tool T2 responds to the process 82 of confirming a connection. The tool T3 respond|corresponds to the process 83 of confirming the board|substrate A. The tool T3 respond|corresponds to the process 84 of confirming the board|substrate B. Correspondence between the process and the tool is described in the failure response procedure 601 obtained by the order changing unit 14 from the engaging unit 13 . In the failure response procedure 601 of FIG. 10 , if the combined number information 12a is the number information 12a of FIG. 8 , the order change unit 14 confirms the substrate A and the processing 83 of confirming the substrate B The process 84 is replaced. This is because the tools in the steps 83 and 84 are the same tool T3.

11 is a failure response procedure 602 used in the first modification. In the failure response procedure 602 of FIG. 11 , the tool corresponds to each process. Moreover, in the failure response procedure 602 of FIG. 11, the number of times is 10 times, 40 times, 45 times, and 50 times, respectively, according to the combined number information 12a. In this example, the order change unit 14 determines that the process 83 of confirming the substrate A and the process 84 of confirming the substrate B are not interchanged. This means that the tool T3 corresponding to the step 82 of confirming the connection and the tool T3 corresponding to the step 83 of confirming the substrate A are the same, and the number of times of the step 83 of confirming the substrate A and the substrate B It follows that the difference in the number of times of the step 84 of confirming is small. That is, since there is no difference in the number of times of the steps 83 and 84, the replacement effect is low. On the other hand, since the process 82 and the process 83 use the same tool, the effect of not replacing the process 83 and the process 84 is high. The order change unit 14 digitizes the difference in the number of times between the steps 83 and 84, and quantifies the effect of continuous use of the tool by using the same tool in the steps 82 and 83. Then, based on these numerical values, it is determined that the steps 83 and 84 are not interchanged.

<Modification 2>

A second modification of the first embodiment will be described with reference to FIGS. 12 and 13 . 12 and 13 are states before the order change unit 14 changes the failure response order. In the modified example 1, a tool respond|corresponds to each process. In the second modification, each process corresponds to the work place of the process. Each process from the process 81 to the process 84 constituting the process group corresponds to the work place. The order change unit 14, which is a replacement unit, replaces the order of the steps 83 and 84 in which the order can be exchanged based on the order of the work place determined from the plurality of steps 81 to 84 that are continuously performed.

It will be described in detail below. In Figs. 12 and 13, the work place is indicated as the place P1. The smaller the difference between the numbers, the closer the work place is. Modification 2 is a configuration in which the tool of Modification 1 serves as a work place. In the second modification, the procedure change unit 14 also refers to the location P corresponding to each step of the failure response procedure 603 and replaces the steps. Place P1, Place P2, ... indicate the same place if the numbers are the same.

12 is a failure response procedure 603 obtained in step S17 by the procedure change unit 14 of the second modification. In the failure response procedure 603 of FIG. 12 , the work place corresponds to each process. The place P1 corresponds to the step 81 of confirming the voltage. The place P2 responds to the process 82 of confirming a connection. The place P3 corresponds to the process 83 of confirming the board|substrate A. The place P4 corresponds to the process 84 of confirming the board|substrate B. Correspondence between the process and the tool is described in the failure response procedure 603 obtained by the order changing unit 14 from the engaging unit 13 . In the failure response procedure 603 of FIG. 12 , if the combined number information 12a is the number information 12a of FIG. 8 , the order change unit 14 performs the step 83 of confirming the substrate A and the substrate B The checking step 84 is replaced. This is because the working places of the process 83 and the process 84 are close.

Fig. 13 is a failure response procedure 604 obtained by the procedure change unit 14 in step S17 in the second modification. In the failure response procedure 604 of FIG. 13 , the work place corresponds to each process. Moreover, in the failure response procedure 604 of FIG. 13, the number of times is 10 times, 40 times, 45 times, and 50 times, respectively, according to the combined number information 12a. In this example, the order change unit 14 determines that the process 83 of confirming the substrate A and the process 84 of confirming the substrate B are not interchanged. In this case, the work place corresponding to the step 83 is the place P3, the work place corresponding to the step 84 is the place P9, and the difference between the number of the steps 83 and the number of the steps 84 is small. follow That is, since there is not much difference in the number of steps 83 and 84, the replacement effect is low. On the other hand, the working places of the process 83 and the process 84 are the places P3 and P9, and there is a difference of 9-3=6. The order change unit 14 digitizes the difference in the number of times between the steps 83 and 84, and digitizes it as a separate evaluation value based on the difference “9” between the work places of the steps 83 and 84 . Then, based on these numerical values, it is determined that the steps 83 and 84 are not interchanged.

<Modification 3>

Modification 3 is a configuration in which the order change unit 14 considers both the tool and the work place.

Fig. 14 shows a failure response procedure 605 that the procedure change unit 14 acquires in step S17. The number of times, the tool, and the work place correspond to each of the steps 81 to 84 of the failure response procedure 605 . The order change unit 14 performs replacement of the replaceable process by using the number of times, the tool, and the work place.

***Description of the effect of Embodiment 1 ***

(1) The failure support apparatus 100 can flexibly respond to a failure response in which the operation sequence is determined by replacing the steps in the failure response sequence by the sequence change unit 14 .

(2) The order change unit 14 replaces the process of the failure response order based on the tool corresponding to the process of the failure response order. Accordingly, it is possible to increase the efficiency of the failure response procedure.

(3) The order change unit 14 replaces the process of the failure response order based on the work place corresponding to the process of the failure response order. Accordingly, it is possible to increase the efficiency of the failure response procedure.

(4) The registration accepting unit 11 accepts the setting of a replaceable process. Accordingly, the failure support apparatus 100 may provide a failure response sequence capable of flexibly responding to a failure response in which the operation sequence is determined.

<Modification 4>

Modified example 4 is a structure using the information of the model which elevator specification DB33 has. In the fourth modification, the elevator control device 500 outputs the model of the elevator in addition to the failure code.

The history extracting unit of Modification Example 4 refers to the model installation information indicating the correspondence between the device model and the installation location of the device, so that the same fault code as the fault code acquired from the control device and the same model as the model acquired from the control device correspond to A plurality of records including an installation location are extracted from among a plurality of records included in the record storage device. The history extractor generates count information by matching the number of extracted records for each cause included in the plurality of extracted records.

Specifically, it is as follows.

Modification Example 4 will be described with reference to FIGS. 6 and 15 .

15 shows the model installation information 33a that the elevator specification DB 33 has. Model installation information (33a) has a column of the building, machine and machine. The building where each row of the model installation information 33a is the model installation record 33b and the column of the machine|unit are installation places of the elevator which is an apparatus. For example, building 1, unit 1, and model A in the uppermost model installation record 33b indicate that the model of unit 1 of building 1 is "A". The plurality of records of the failure record information 32b shown in Fig. 6 include buildings and installation places of elevators such as units.

Hereinafter, the operation of the history extracting unit 12 in Modification Example 4 will be described.

(1) The history extraction unit 12 acquires a failure code 050 = [001] from the elevator control device 500 .

(2) When the failure code (050) = [001] is obtained, the history extraction unit 12 combines the model installation information 33a of FIG. 15 and the failure record information 32b of FIG. 6 to obtain combined information 35 ) is created.

16 shows the combination information 35 . The combination information 35 consists of a plurality of combination records 35a. The combination information 35 is combined via the "building and unit" of the failure record information 32b and the model installation information 33a. The combination information 35 is a state in which the column of the model is added to the superiority and inferiority of the failure record information 32b.

(3) The history extraction unit 12 extracts, from the combination information 35, a plurality of combined records 35a of the same model having the acquired failure code 050 = [001]. 17 shows the extraction result of the combined record 35a by the history extraction unit 12. In FIG.

Fig. 17 shows the result of extracting the combination record of the model A and the failure code failure code (050) = [001] from the combination information 35 by the history extracting unit 12 . The history extracting unit 12 associates the number of extracted records for each cause included in the plurality of extracted records, and generates the number of causes to which the largest number corresponds as the number of times information. In the example of Fig. 17, the history extracting unit 12 associates the cause 11A with 3, which is the number of combined records, and generates this 3 as the number of times information. In addition, the history extraction unit 12 has the same fault code as the fault code 050 received from the elevator control device 500 from the combination information 35 , and the same as the model received from the elevator control device 500 . Extracts a combined record with a model. Therefore, in the example other than FIG. 17, even if the failure code and model are the same as the failure code and model received from the elevator control device 500, a record with a different "cause" may be extracted.

Fig. 18 shows a state in which the lowest record with a different &quot;cause&quot; is also extracted. In Fig. 18, the number information of cause 11A is 3, and the number information of cause 12A is 1. In this case, the history extracting unit 12 employs the maximum number of times information "3". In addition, since the combination information 35 of FIG. 16 is information obtained by adding a model column to the failure record information 32b of FIG. 6, extracting a record from the combination information 35 is a failure record from the failure record information 32b. is the same as extracting

(4) The processing of the transition after generation of the number of times information is the same as the procedure in FIG. 3 .

In the modified example 4, since the history extraction part 12 extracts the failure record of the same model as the model of the malfunctioning elevator, when there is a characteristic for each model, a failure response operation can be implemented more efficiently.

<Supplement of hardware configuration>

In the failure support apparatus 100 of FIG. 2 , the function of the failure support apparatus 100 is realized by software, but the function of the failure support apparatus 100 may be implemented by hardware.

19 shows a configuration in which the function of the failure support device 100 is realized by hardware. The electronic circuit 90 of FIG. 19 includes a registration accepting unit 11, a history extracting unit 12, a combining unit 13 and an order changing unit 14, a main memory device 20, an auxiliary memory device 30, and an input. It is a dedicated electronic circuit that realizes the functions of the IF 40 , the output IF 50 , and the communication IF 60 . The electronic circuit 90 is connected to the signal line 91 . Specifically, the electronic circuit 90 is a single circuit, a complex circuit, a programmed processor, a parallel programmed processor, a logic IC, a GA, an ASIC, or an FPGA. GA is an abbreviation for Gate　Array. ASIC is an abbreviation of Application　Specific　Integrated　Circuit. FPGA is an abbreviation for Field-Programmable 　 Gate Array. The functions of the components of the failure support device 100 may be realized by one electronic circuit, or may be realized by being dispersed in a plurality of electronic circuits. In addition, some functions of the components of the failure support apparatus 100 may be realized by an electronic circuit, and the remaining functions may be realized by software.

Each of the processor 10 and the electronic circuit 90 is also referred to as a processing circuit. In the failure support apparatus 100, the functions of the registration accepting unit 11, the history extracting unit 12, the combining unit 13, and the order changing unit 14 may be realized by a processing circuit. Alternatively, the registration accepting unit 11, the history extracting unit 12, the combining unit 13 and the order changing unit 14, the main memory device 20, the auxiliary storage device 30, the input IF 40, the output IF ( 50) and the functions of the communication IF 60 may be realized by a processing circuit.

As mentioned above, although Embodiment 1 and a modification were demonstrated, you may implement one of Embodiment 1 including a modification partially. Alternatively, two or more of Embodiment 1 including modified examples may be partially combined and implemented. In addition, this invention is not limited to Embodiment 1, Various changes are possible as needed.

031: Fault code 032: Fault code
050: Fault code 10: Processor
11: registration reception unit 12: history extraction unit
12a: count information 13: coupling part
14: sequence change unit 20: main memory device
30: auxiliary storage device 31: failure response sequence DB
31a: Failure response sequence 32: Failure history DB
32a: failure record 32b: failure record information
33: Elevator specification DB 33a: Model installation information
33b: Model installation record 35: Combination information
35a: Combine Record 40: Input IF
50: output IF 60: output IF
70: signal lines 81, 82, 83, 84: process
90: electronic circuit 91: signal line
100: trouble support device 101: trouble support program
200: input device 210: manager
300: display device 400: maintenance terminal
410: maintenance man 500: elevator control device
601, 602, 603, 604, 605: Troubleshooting sequence

Claims (9)

Acquire a failure code for identifying the failure content of the apparatus from a control device for controlling the apparatus, and from among the plurality of records in a record storage device having a plurality of records including the failure code and a cause of the failure, the obtained failure code an extracting unit for extracting a plurality of the records including the same fault code as
Includes the fault code, a group of processes having a plurality of sequentially performed steps and a process in which the sequence can be replaced when the plurality of steps are continuously performed, and a process cause indicating a cause of a failure associated with each step. Acquires the failure response sequence including the same fault code as the acquired fault code from a sequence storage device in which a plurality of fault response sequences are registered, and information on the number of times among the process causes included in the fault response sequence a combining unit for combining the number of records of the record corresponding to the cause of the number information with the process cause that is the same as the cause having the cause;
Based on the number of records coupled to the process cause, a replacement unit for replacing the sequence of the processes in which the sequence can be replaced, and outputting the failure response sequence with the replacement of the sequence of the processes;
Fault support device. The method of claim 1,
Each process in the process group corresponds to the tool used,
The replacement unit is configured to replace the order of the process in which the order can be exchanged based on the order of the tool determined from the plurality of processes performed continuously.
Fault support device. 3. The method according to claim 1 or 2,
Each process in the process group corresponds to the work place,
The replacement unit is configured to replace the order of the process in which the order can be exchanged based on the order of the work place determined from the plurality of processes performed consecutively.
Fault support device. 4. The method according to any one of claims 1 to 3,
The coupling unit generates a warning when the process corresponding to the cause of the number information does not exist in the acquired failure response sequence.
Fault support device. 5. The method according to any one of claims 1 to 4,
The failure support apparatus receives a setting instruction of a replaceable process, sets the replaceable process indicated by the setting instruction in the failure response order, and registers the failure response order in the sequence storage device. to have more wealth
Fault support device. 6. The method according to any one of claims 1 to 5,
the plurality of records included in the record storage device includes an installation location of the device;
The extraction unit,
Acquiring the model of the device from the control device, referring to model installation information indicating correspondence between the model of the device and the installation location of the device, the fault code identical to the acquired fault code and the same model as the acquired model A plurality of records including the corresponding installation location are extracted from among the plurality of records of the record storage device, and the number of extracted records is associated with each cause included in the extracted plurality of records. generating count information
Fault support device. 7. The method according to any one of claims 1 to 6,
The device is an elevator
Fault support device. on the computer,
Acquire a failure code for identifying the failure content of the apparatus from a control device for controlling the apparatus, and from among the plurality of records in a record storage device having a plurality of records including the failure code and a cause of the failure, the obtained failure code Extraction processing for extracting a plurality of the records including the same fault code as
Includes the fault code, a group of processes having a plurality of sequentially performed steps and a process in which the sequence can be replaced when the plurality of steps are continuously performed, and a process cause indicating a cause of a failure associated with each step. Acquires the failure response sequence including the same fault code as the acquired fault code from a sequence storage device in which a plurality of fault response sequences are registered, and information on the number of times among the process causes included in the fault response sequence combining processing of combining the number of records of the record corresponding to the cause of the number information with the process cause identical to the cause having;
Replacement processing for replacing the sequence of the processes in which the sequence can be replaced, based on the number of records combined with the cause of the process, and outputting the failure response sequence in which the sequence of the processes is replaced
A fault support program that runs computer,
Acquire a failure code for identifying the failure content of the apparatus from a control device for controlling the apparatus, and from among the plurality of records in a record storage device having a plurality of records including the failure code and a cause of the failure, the obtained failure code extracting a plurality of the records including the same fault code as
Includes the fault code, a group of processes having a plurality of sequentially performed steps and a process in which the sequence can be replaced when the plurality of steps are continuously performed, and a process cause indicating a cause of a failure associated with each step. Acquires the failure response sequence including the same fault code as the acquired fault code from a sequence storage device in which a plurality of fault response sequences are registered, and information on the number of times among the process causes included in the fault response sequence combining the number of records of the record corresponding to the cause of the number information with the process cause that is the same as the cause of having;
based on the number of records coupled to the process cause, replacing the sequence of the process in which the sequence can be replaced, and outputting the failure response sequence in which the sequence of the process is replaced
How to support a breakdown.

Images