CN113396119B

CN113396119B - Failure support device, computer-readable recording medium, and failure support method

Info

Publication number: CN113396119B
Application number: CN201980091076.0A
Authority: CN
Inventors: 西出恭平; 伏见涉
Original assignee: Mitsubishi Electric Corp
Current assignee: Mitsubishi Electric Corp
Priority date: 2019-02-14
Filing date: 2019-02-14
Publication date: 2022-11-29
Anticipated expiration: 2039-02-14
Also published as: CN113396119A; WO2020165982A1; JPWO2020165982A1; JP6833152B2; KR20210101327A; TWI742398B; TW202030687A; KR102362933B1

Abstract

A history extraction unit (12) acquires a fault code (050) from an elevator control device (500), extracts a plurality of fault records (32 a) having the same fault code as the fault code (050) from a fault history DB (32), and generates frequency information (12 a). A combining unit (13) acquires a failure handling process (31 a) having the same failure code as the failure code (050) from a failure handling process DB (31) in which the failure handling process (31 a) is registered, and combines the number of records corresponding to the cause of the count information (12 a) with the same process cause as the cause of the count information (12 a) among the process causes included in the failure handling process (31 a). A process changing unit (14) exchanges the order of the processes included in the failure handling process (31 a) according to the number of records associated with the process causes, and outputs a failure handling process (31 a-1) in which the order of the processes is exchanged.

Description

Failure support device, computer-readable recording medium, and failure support method

Technical Field

The invention relates to a failure support device, a computer-readable recording medium, and a failure support method.

Background

The following methods exist in the prior art: when an elevator has a failure, a previous failure case is searched for a failure countermeasure in order to shorten the recovery time (for example, patent document 1).

However, as in the case of substrate replacement, there is a trouble countermeasure in which the work process is determined, that is, the voltage is measured first, then the connection confirmation of the wiring is confirmed, and then the substrate replacement is performed. In the prior art, the fault handling determined in the work process cannot be flexibly adapted.

In addition, since the conventional technique does not consider the work position, there is a possibility that trouble handling is provided in the order of on-car, pit, and on-car. Such failure handling may generate travel time and cause waste.

Documents of the prior art

Patent document

Patent document 1: japanese patent No. 5820072

Disclosure of Invention

Problems to be solved by the invention

An object of the present invention is to provide a device and a method for presenting a trouble handling process that can flexibly adapt to trouble handling determined in a work process.

Means for solving the problems

The fault assistance device of the present invention includes:

an extraction unit that acquires a fault code identifying the content of a fault of a device from a control device that controls the device, extracts a plurality of records including the same fault code as the acquired fault code from a record storage device having the plurality of records including the fault code and the cause of the fault, and generates count information in which the number of records is associated with each cause;

a combining unit that acquires the trouble handling process including the same trouble code as the acquired trouble code from a process storage device in which a plurality of trouble handling processes including the trouble code, a plurality of processes that are continuously performed and in which the order is interchangeable when the plurality of processes are continuously performed, and a plurality of trouble handling processes indicating process causes of trouble causes corresponding to the respective processes are registered, and that combines the number of records of the record corresponding to the cause included in the count information with the process cause that is the same as the cause included in the count information among the process causes included in the trouble handling process; and

and an interchanging unit that interchanges the order of the steps whose order is interchangeable according to the number of records associated with the process cause, and outputs the failure handling procedure in which the order of the steps is interchanged.

ADVANTAGEOUS EFFECTS OF INVENTION

According to the failure support device of the present invention, it is possible to present a failure handling process that can flexibly adapt to failure handling determined in the work process.

Drawings

Fig. 1 is a diagram of embodiment 1, and is a diagram showing functional blocks of a failure support apparatus 100.

Fig. 2 is a diagram of embodiment 1, and is a diagram showing a hardware configuration of the failure support apparatus 100.

Fig. 3 is a diagram of embodiment 1, and is a timing chart for explaining the operation of the failure support apparatus 100.

Fig. 4 is a diagram of embodiment 1, and is a diagram showing a failure handling process 31a.

Fig. 5 is a diagram of embodiment 1, and shows a format of the failure log 32a.

Fig. 6 is a diagram of embodiment 1, and is a diagram showing failure log information 32b including a plurality of failure logs 32a.

Fig. 7 is a diagram of embodiment 1, and schematically shows a state of a fault record in which the fault code 032=001 is extracted in fig. 6.

Fig. 8 is a diagram of embodiment 1, showing the count information 12a.

Fig. 9 is a diagram of embodiment 1, and shows a state in which the process changing unit 14 has exchanged the process 83 for the substrate a and the process 84 for the substrate B in the failure handling process 31a.

Fig. 10 is a diagram of embodiment 1, and is a diagram showing a failure handling process 601.

Fig. 11 is a diagram of embodiment 1, and is a diagram showing a failure handling process 602.

Fig. 12 is a diagram of embodiment 1, and is a diagram showing a failure handling process 603.

Fig. 13 is a diagram of embodiment 1, and is a diagram showing a failure handling process 604.

Fig. 14 is a diagram of embodiment 1, and is a diagram showing a failure handling process 605.

Fig. 15 is a diagram of embodiment 1, and is a diagram showing model installation information 33a included in the elevator specification DB 33.

Fig. 16 is a diagram of embodiment 1, and shows the binding information 35.

Fig. 17 is a diagram of embodiment 1, and shows an extraction result extracted from the binding information 35.

Fig. 18 is a diagram of embodiment 1, and shows extraction results of records having different causes.

Fig. 19 is a diagram of embodiment 1, and is a diagram showing a configuration in which the function of the failure support apparatus 100 is realized by hardware.

Detailed Description

Hereinafter, embodiments of the present invention will be described with reference to the drawings. In the drawings, the same or corresponding portions are denoted by the same reference numerals. In the description of the embodiments, the same or corresponding portions are appropriately omitted or simplified.

(1) Hereinafter, the failure handling process database 31, the failure history database 32, and the elevator specification database 33 are referred to as a failure handling process DB 31, a failure history DB32, and an elevator specification DB 33, respectively. The failure coping process DB 31 holds a failure coping process 31a. The failure history DB32 holds failure log information 32b. The elevator specification DB 33 stores elevator specifications.

(2) Hereinafter, a fault code will occur. The fault code described in the fault-coping process 31a, the fault code issued by the elevator control device 500, and the fault code included in the fault record 32a. These failure codes are referred to as failure code 031, failure code 050, and failure code 032, respectively. The trouble code is a code for identifying the contents of the trouble. The fault codes are the same, which means that the fault contents are the same. If the example is performed, when the failure code 031= [001] and the failure code 050= [001], the content of the failure in the failure handling process 31a is the same as the content of the failure in the elevator control device 500.

(3) Hereinafter, the failure cause corresponding to each step of the failure handling process 31a is referred to as a process cause. The cause described in the failure record 32a is abbreviated as a cause.

(4) Hereinafter, the interface is referred to as IF.

Embodiment mode 1

A failure support device 100 according to embodiment 1 will be described with reference to fig. 1 to 15.

* Description of the Structure

Fig. 1 shows the functional blocks of the fault assistance device 100.

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

The fault assistance device 100 is a computer. The fault assist apparatus 100 has a processor 10, and has other hardware such as a main storage device 20, an auxiliary storage device 30, an input IF 40, an output IF 50, and a communication IF 60. The processor 10 is connected to and controls other hardware via signal lines 70.

The failure support apparatus 100 includes, as functional elements, a registration receiving unit 11, a history extracting unit 12, a combining unit 13, and a process changing unit 14. The history extraction unit 12 is an extraction unit. The process changing section 14 is an interchanging section.

The functions of the registration reception unit 11, the history extraction unit 12, the coupling unit 13, and the process change unit 14 are realized by the failure support program 101.

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

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

The auxiliary storage device 30 is a storage device that stores data in a nonvolatile manner. A specific example of the auxiliary storage device 30 is an HDD (Hard Disk Drive). The auxiliary storage device 30 may be a portable recording medium such as an SD (registered trademark) memory card, a NAND flash memory, a flexible Disk, an optical Disk, a compact Disk, a blu-ray (registered trademark) Disk, or a DVD (Digital Versatile Disk). The auxiliary storage device 30 stores a failure handling procedure DB 31, a failure history DB32, an elevator specification DB 33, and a failure auxiliary program 101. Data such as the failure handling procedure DB 31, the failure history DB32, the elevator specification DB 33, and the failure support program 101 may be stored in another device such as a cloud server, and may be acquired from the other device by the failure support device 100. The auxiliary storage device 30 is a record storage device, a process 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 a keyboard is connected and from which data is input.

The output IF 50 is a port that connects various devices and outputs data to the various devices by the processor 10. In fig. 2, a display device 300 is connected to the output IF 50.

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

The processor 10 loads the failure assistance program 101 from the auxiliary storage device 30 to the main storage device 20, and reads in and executes the failure assistance program 101 from the main storage device 20. The main storage device 20 stores not only the failure support program 101 but also an OS (Operating System). The processor 10 executes the failure assistant program 101 while executing the OS.

The fault assist device 100 may also have a plurality of processors in place of the processor 10. The plurality of processors share the execution of the fault assistant program 101. Each processor is a device that executes the failure support program 101 in the same manner as the processor 10. Data, information, signal values, and variable values utilized, processed, or output by the fault assist program 101 are stored in registers or caches within the primary storage 20, the secondary storage 30, or the processor 10.

The trouble support program 101 is a program for causing a computer to execute each process, or each step, in which the "section" of the registration receiving section 11, the history extracting section 12, the coupling section 13, and the process changing section 14 is replaced with the "process", "procedure", or "step".

The failure support method is a method in which the failure support device 100 as a computer executes the failure support program 101. The failure support program 101 may be provided by being stored in a computer-readable recording medium, or may be provided as a program product.

* Description of actions

Fig. 3 is a timing chart illustrating the operation of the failure support apparatus 100. The operation of the failure support apparatus 100 will be described with reference to fig. 3. The operation of the failure support device 100 corresponds to a failure support method. The operation of the failure support device 100 corresponds to the processing of the failure support program.

< step S11 >

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

Fig. 4 shows a failure handling process 31a. When registering the trouble handling process 31a, the manager 210 determines whether or not the process setting can be switched in order.

The registration reception unit 11 sets "interchangeable" designated as an interchangeable process in the trouble handling process 31a.

The registration receiving unit 11 receives an interchangeable process setting instruction, sets an interchangeable process instructed by the setting instruction in the trouble handling process 31a, and registers the trouble handling process 31a in the process storage device. In the fault assist device 100, the process storage device is the secondary storage device 30. In fig. 4, the interchangeable processes are

processes

83, 84. The failure handling process 31a of fig. 4 is explained. The failure handling procedure 31a is information that the administrator 210 registers to the registration receiving unit 11 using the input device 200. The failure handling process 31a has a failure code 031 and a plurality of steps 81 to 84 to be executed continuously. In the failure handling process 31a, there are

steps

83 and 84 that can be sequentially changed when continuously performed in steps 81 to 84. Steps 81 to 84 are steps. The failure handling process 31a includes a process cause and a treatment indicating a failure cause corresponding to each process.

(1) In step 81, it is determined whether or not the voltage is normal. If yes, the process proceeds to step 82. If "no", it is determined whether or not improvement has been achieved by power supply reconnection, and if "no", the process proceeds to step 82, and if "yes", the cause of the power supply failure is obtained.

(2) In step 82, it is determined whether or not the wiring is normal. If yes, the process proceeds to step 83. If "no", the process cause of the lead failure can be obtained.

(3) In step 83, the improvement result of the substrate a is judged. In the case of no, the process proceeds to step 84. In the case of "yes", the cause of the process for the failure of the substrate a can be obtained.

(4) In step 84, the improvement result of the substrate B is judged. In the case of "no", a process cause of unknown cause can be obtained. If "yes", the cause of the step of the failure of the substrate B can be obtained.

< step S12 >

The elevator control device 500 outputs a failure code 050 when a failure occurs.

< step S13 >

The history extraction unit 12 acquires a fault code identifying the content of a fault of a device from a control device that controls the device. In addition, an elevator is an example of the apparatus. An elevator control device is an example of a control device. The history extraction unit 12 extracts a plurality of records including the same fault code as the acquired fault code from a record storage device having a plurality of records including the fault code and the cause of the fault, and generates the number-of-times information in which the number of records is associated with each cause.

The details are as follows. In step S13, the history extraction unit 12 extracts the fault log 32a having the fault code 032 matching the fault code 050 from the fault history DB32 having the previous fault history. A fault record is a record that contains a fault code and the cause of the fault.

Fig. 5 shows the format of the fault record 32a. The failure log 32a includes items of a building, a number, a failure code 032, and a procedure. The building means a building provided with an elevator. The elevator number indicates the elevator number, i.e., the car. The fault code 032 is as described above. The handling indicates the cause XX in the failure and the handling of YY for the cause. The failure is caused by a failure of the circuit board, and the circuit board is replaced.

Fig. 6 shows failure log information 32b including a plurality of failure logs 32a. The failure history DB32 stores failure record information 32b.

< step S14 >

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

Fig. 7 schematically shows a state of a fault record in which the fault code 032= [001] is extracted in fig. 6. The building and the airplane of each failure record 32a are omitted. As can be seen from fig. 7, there is a fault log 32a having the same fault code 032 but a different cause. In fig. 7, when the number of failure records 32A is counted for each cause, the number of records of the cause 11A is 3, and the number of records of the cause 12A is 1.

Fig. 8 shows the count information 12a. The frequency information 12a stores a fault code 032. The frequency information 12a is information indicating a result of counting the number of the failure records 32a for each cause of the failure records 32a by the history extraction unit 12. The number-of-times information 12a in fig. 8 shows that 10 fault records 32a are caused by a power failure, 40 fault records 32a are caused by a lead failure, 5 fault records 32a are caused by a defect in the substrate a, and 50 fault records 32a are caused by a defect in the substrate B. The history extraction unit 12 sends the count information 12a to the coupling unit 13.

< step S15 >

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

< step S16 >

The coupling unit 13 acquires a trouble countermeasure process including the same trouble code as the trouble code acquired from the control device from the auxiliary storage device 30 as a process storage device. The combining unit 13 combines the number of records of the record corresponding to the cause included in the count information with the same process cause as the cause included in the count information among the process causes included in the acquired failure handling process.

The details are as follows. In step S16, the coupling unit 13 couples the process cause (fig. 4) described in the extracted failure handling procedure 31a and the cause of the count information 12a. That is, the combination refers to associating the same process cause as the cause of the count information 12a among the process causes described in the failure handling process 31a, with the same count. Here, the number-of-times information 12a is set to fig. 8, and the failure handling procedure 31a acquired by the coupling unit 13 from the failure handling procedure DB 31 is set to the failure handling procedure 31a of fig. 4. In this example, the bonding section 13 associates the count 10 with the failure of the power supply in the failure handling process 31a, the count 40 with the failure of the lead in the failure handling process 31a, the count 5 with the failure of the substrate a in the failure handling process 31a, and the count 50 with the failure of the substrate B in the failure handling process 31a.

The coupling unit 13 also displays the process cause, which is described in the count information 12a but is not registered in the failure handling procedure 31a acquired in step S15, on the display device 300, and notifies the administrator 210 of the process cause. Alternatively, the information may be transmitted to an administrator terminal device, not shown, which the administrator 210 has. As an example the following are the cases: the cause of the count information 12a (fig. 8) is a substrate C defect, and the process cause of the failure handling process 31a acquired in step S15 is no substrate C defect. The administrator 210 determines whether or not addition is necessary, and revises the fault handling process 31a of the fault code 031= [001].

In this way, when there is no process corresponding to the cause included in the acquired failure handling process 31a, the coupling unit 13 issues a warning. The manner of issuing the warning as described above may be any manner, such as displaying the warning on the display device, or transmitting the warning to the administrator terminal device.

The coupling unit 13 transmits the failure handling process 31a to which the cause of the count information 12a is coupled to the process changing unit 14.

< step S17 >

The procedure changing unit 14 as an interchanging unit interchanges the sequence of the procedure with the interchangeable procedure according to the number of records associated with the procedure cause, and outputs a failure handling procedure in which the sequence of the procedure is interchanged. In addition, the manner of outputting the failure handling process may be any manner. The failure handling process may be transmitted to the maintenance terminal, may be stored in the cloud server, may be stored in the auxiliary storage device 30, or may be displayed on the display device 300.

In step S17, the process changing unit 14 refers to the number of process causes in the failure handling process 31a to which the cause of the number-of-times information 12a is coupled, and thereby interchanges the interchangeable processes.

The description will be given by taking fig. 4 as an example. In the case of the reason for combining the frequency information 12a, the number of counts of the process reasons in fig. 4 is the number shown in fig. 8. As shown in fig. 4, the process 83 for substrate a and the process 84 for substrate B are interchangeable. The number of counts of the process cause corresponding to the process 83 of the substrate a is 5, and the number of counts of the process cause corresponding to the process 84 of the substrate B is 50. That is, the number of times of counting in the process 84 for the substrate B is larger than that for the substrate a, which means that the number of failures of the substrate B is larger than that for the substrate a. Therefore, the process changing unit 14 changes the failure handling process 31a by exchanging the process 83 for the substrate a and the process 84 for the substrate B with each other so that the process 84 for the substrate B is performed before the process 83 for the substrate a in the failure handling process 31a shown in fig. 4.

Fig. 9 shows a failure handling process 31a-1 in which the process modifying unit 14 has exchanged the process 83 for the substrate a and the process 84 for the substrate B in the failure handling process 31a.

< step S18 >

In step S18, the process changer 14 transmits the changed failure handling process 31a-1 in which the process 83 for the substrate a and the process 84 for the substrate B are exchanged to the maintenance terminal 400.

< step S19 >

In step S19, the maintenance person 410 performs a procedure based on the failure handling process 31a-1. The maintenance person 410 uses the maintenance terminal 400 to register a record in the form of a fault record 32a with the fault history DB32, the fault record 32a containing the treatment and the cause as the implementation result, and containing the building, the car, and the fault code.

< modification 1>

Fig. 10 and 11 show the state before the process changing unit 14 changes the failure handling process. Modification example 1 of embodiment 1 will be described with reference to fig. 10 and 11. In modification 1, the process changing unit 14 further exchanges the process with another process by referring to the tools corresponding to the respective processes of the failure handling process 601. Each of the steps 81 to 84 for forming the step group corresponds to a tool used in the step. The procedure changing unit 14 as an interchanging unit interchanges the order of the

steps

83 and 84 based on the order of the tool determined by the plurality of steps 81 to 84 to be continuously performed.

The following is a detailed description.

Fig. 10 shows a failure handling process 601 used in modification 1. The process changing unit 14 obtains the failure handling process 601 in step S17. The failure handling procedure 601 receives registration in step S11. The failure handling process 601 is registered in the same manner as the failure handling process 31a (step S11). The failure handling processes 602 to 605 described below are also registered in the same manner as the failure handling process 31a, and are acquired by the process changing unit 14 in step S17. In the failure handling process 601 in fig. 10, tools are handled in each step. The voltage checking step 81 corresponds to the tool T1. The process 82 of confirming the wiring corresponds to the tool T2. The step 83 of checking the substrate a corresponds to the tool T3. The step 84 of checking the substrate B corresponds to the tool T3. The correspondence between the process and the tool is described in the failure handling process 601 which the process changing unit 14 acquires from the coupling unit 13. In the failure handling process 601 of fig. 10, if the number-of-times information 12a to be combined is the number-of-times information 12a of fig. 8, the process changing unit 14 exchanges the process 83 of checking the substrate a and the process 84 of checking the substrate B. This is because the tools of the process 83 and the process 84 are the same tool T3.

Fig. 11 shows a failure handling process 602 used in modification 1. In the failure handling process 602 of fig. 11, tools are assigned to each process. In the failure handling process 602 in fig. 11, the number of times is 10 times, 40 times, 45 times, and 50 times, respectively, based on the number-of-times-of-combination information 12a. In this example, the process changing unit 14 determines that the process 83 for checking the substrate a and the process 84 for checking the substrate B are not to be interchanged. This is because the tool T3 corresponding to the step 82 of checking the wiring is the same as the tool T3 corresponding to the step 83 of checking the substrate a, and the difference between the number of times of the step 83 of checking the substrate a and the number of times of the step 84 of checking the substrate B is small. That is, the number of times of the

steps

83 and 84 is not so different, and therefore the effect of interchanging is poor. On the other hand, since the same tool is used for the

steps

82 and 83, it is preferable to avoid the step 83 and the step 84. The process changing unit 14 digitizes the difference in the number of times between the

steps

83 and 84, digitizes the effect of continuous use of the tool by using the same tool for the

steps

82 and 83, and determines not to interchange the

steps

83 and 84 based on these numerical values.

< modification 2>

Modification 2 of embodiment 1 will be described with reference to fig. 12 and 13. Fig. 12 and 13 show the state before the process changing unit 14 changes the failure handling process. In modification 1, a tool is associated with each step. In modification 2, each step corresponds to a work place where the step is provided. Each of the steps 81 to 84 forming the step group corresponds to a work place. The procedure changing unit 14 as a interchanging unit interchanges the order of the

processes

83 and 84 based on the order of the work place determined by the plurality of processes 81 to 84 to be continuously performed.

The following is a detailed description. In fig. 12 and 13, the work place is referred to as a place P1. The smaller the numerical difference, the closer the work place is. Modification 2 is a configuration in which the tool of modification 1 is used as a work place. In modification 2, the process changing unit 14 further refers to the locations P corresponding to the respective processes of the failure handling process 603 to exchange the processes. The locations P1, P2, and … are identical in number, and thus represent identical locations.

Fig. 12 shows a failure handling procedure 603 obtained in step S17 by the procedure changing unit 14 of modification example 2. In the failure coping process 603 in fig. 12, a work place is associated with each step. The voltage checking step 81 corresponds to the place P1. The step 82 of checking the wiring corresponds to the location P2. The step 83 of confirming the substrate a corresponds to the place P3. The step 84 of confirming the substrate B corresponds to the presence position P4. The correspondence between the process and the location is described in the failure handling process 603 obtained by the process changing unit 14 from the coupling unit 13. In the failure handling process 603 in fig. 12, if the number-of-times information 12a to be combined is the number-of-times information 12a in fig. 8, the process changing unit 14 exchanges the process 83 of checking the substrate a and the process 84 of checking the substrate B. This is because the work sites of the

steps

83 and 84 are close to each other.

Fig. 13 shows a failure handling procedure 604 acquired by the procedure changing unit 14 in step S17 in modification 2. In the failure handling process 604 of fig. 13, each step corresponds to a work place. In the failure handling process 604 of fig. 13, the number of times is 10 times, 40 times, 45 times, and 50 times, respectively, based on the number-of-times-of-combination information 12a. In this example, the process changing unit 14 determines that the step 83 of checking the substrate a and the step 84 of checking the substrate B are not to be interchanged. This is because the working place corresponding to step 83 is place P3, the working place corresponding to step 84 is place P9, and the difference between the number of

steps

83 and 84 is small. That is, the number of times of the

steps

83 and 84 is not so different, and therefore, the effect of the interchange is poor. On the other hand, the work places in the

steps

83 and 84 are the places P3 and P9, and there is a difference of 9 to 3=6. The process changing unit 14 digitizes the difference in the number of times between the

steps

83 and 84, and then, based on the difference "6" between the work places between the

steps

83 and 84, it is determined that the

steps

83 and 84 are not to be interchanged based on the other evaluation value.

< modification 3>

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

Fig. 14 shows a failure handling process 605 acquired by the process changing unit 14 in step S17. The steps 81 to 84 of the trouble countermeasure process 605 correspond to the number of times, the tool, and the work place. The process changing unit 14 performs the exchange of the interchangeable process by using the number of times, the tool, and the work place.

* Description of effects of embodiment 1

(1) The trouble assisting apparatus 100 can flexibly adapt to the trouble handling specified in the work process because the process changing unit 14 changes the process of the trouble handling process.

(2) The process changing unit 14 changes the process of the failure handling process in accordance with the tool corresponding to the process of the failure handling process. Therefore, the failure coping process can be made efficient.

(3) The process changing unit 14 changes the process of the failure handling process in accordance with the work place corresponding to the process of the failure handling process. Therefore, the failure coping process can be made efficient.

(4) The registration receiving unit 11 receives the setting of the interchangeable process. Therefore, the failure assist device 100 can provide a failure coping process capable of flexibly adapting to the failure coping for which the working process has been determined.

< modification 4>

The modification 4 is a configuration using model information of the elevator specification DB 33. In modification 4, the elevator control device 500 outputs the model of the elevator in addition to the fault code.

The history extraction unit of modification 4 refers to model installation information indicating correspondence between a model of the device and an installation location of the device, and extracts a plurality of records including a fault code identical to the fault code acquired from the control device and an installation location corresponding to the model identical to the model acquired from the control device from among the plurality of records included in the record storage device. The history extraction unit generates count information for each of the extracted reasons included in the extracted plurality of records.

The details are as follows.

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

Fig. 15 shows model installation information 33a of the elevator specification DB 33. The model setting information 33a has columns of buildings, numbers, and models. Each row of the model setting information 33a is a model setting record 33b. Buildings and elevator trains are installation sites for elevators as equipment. For example, the model 1, the number 1, and the model a in the model setting record 33b at the uppermost stage indicate that the model of the number 1 of the building 1 is "a". The plurality of records of the failure log information 32b shown in fig. 6 include installation places of elevators such as buildings and elevator cars.

The operation of the history extracting unit 12 in modification 4 will be described below.

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

(2) When the failure code 050= [001] is acquired, the history extraction unit 12 combines the model setting information 33a in fig. 15 and the failure log information 32b in fig. 6 to generate the combination information 35.

Fig. 16 shows the binding information 35. The binding information 35 is composed of a plurality of binding records 35a. The combination information 35 is combined via "building and number" of the trouble record information 32b and the model setting information 33a. The connection information 35 is a state in which a model column is added to the right column of the failure log information 32b.

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

Fig. 17 shows a result of the history extraction unit 12 extracting the fault code 050= [001] from the combination information 35 and recording the combination of the model a. The history extraction unit 12 generates, as the frequency information, the number corresponding to the largest number of reasons for each of the reasons included in the extracted plurality of records, in accordance with the number of extracted records. In the example of fig. 17, the history extraction unit 12 associates the number 3 of the combination records with the cause 11A, and generates the number 3 as the frequency information. Further, the history extraction unit 12 extracts, from the combination information 35, a combination record having the same fault code 050 as the fault code received from the elevator control device 500 and having the same model as the model received from the elevator control device 500. Therefore, in the examples other than fig. 17, even if the trouble code and model are the same as the trouble code and model received from the elevator control device 500, a record having a different "cause" may be extracted.

Fig. 18 shows a state in which the lowest record having a different "cause" is also extracted. In fig. 18, the frequency information of the cause 11A is 3, and the frequency information of the cause 12A is 1. In this case, the history extraction unit 12 adopts the maximum number-of-times information "3". Since the connection information 35 in fig. 16 is information obtained by adding a model column to the failure log information 32b in fig. 6, the extraction of the log from the connection information 35 is the same as the extraction of the failure log from the failure log information 32b.

(4) The following processing after generating the count information is the same as the sequence of fig. 3.

In modification 4, since the history extraction unit 12 extracts the fault record of the same model as the model of the elevator in which the fault occurred, the fault handling operation can be performed more efficiently when the model has characteristics for each model.

< supplement of hardware architecture >

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

Fig. 19 shows a configuration in which the function of the failure support apparatus 100 is realized by hardware. The electronic circuit 90 in fig. 19 is a dedicated electronic circuit that realizes the functions of the registration accepting unit 11, the history extracting unit 12, the combining unit 13, the procedure changing unit 14, the main storage device 20, the auxiliary storage device 30, the input IF 40, the output IF 50, and the communication IF 60. The electronic circuit 90 is connected to a signal line 91. Specifically, the electronic circuit 90 is a single circuit, a composite 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 apparatus 100 may be implemented by 1 electronic circuit, or may be implemented by a plurality of electronic circuits in a distributed manner. In addition, a part of the 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.

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

Although embodiment 1 and the modification have been described above, 1 of embodiment 1 including the modification may be partially implemented. Alternatively, 2 or more of embodiment 1 including the modification may be partially combined and implemented. The present invention is not limited to embodiment 1, and various modifications can be made as necessary.

Description of the reference symbols

031: a fault code; 032: a fault code; 050: a fault code; 10: a processor; 11: a registration receiving unit; 12: a history extraction unit; 12a: frequency information; 13: a bonding section; 14: a process change unit; 20: a main storage device; 30: a secondary storage device; 31: a fault handling process DB;31a: a fault handling process; 32: a failure history DB;32a: recording faults; 32b: fault record information; 33: an elevator specification DB;33a: machine type setting information; 33b: machine type setting record; 35: combining the information; 35a: combining records; 40: inputting IF;50: outputting the IF;60: a communication IF;70: a signal line; 81. 82, 83, 84: a step (2); 90: an electronic circuit; 91: a signal line; 100: a failure assist device; 101: a fault assist routine; 200: an input device; 210: a manager; 300: a display device; 400: maintaining the terminal; 410: maintenance personnel; 500: an elevator control device; 601. 602, 603, 604, 605: and (5) a fault handling process.

Claims

1. A fault assistance device, wherein the fault assistance device has:

an extraction unit that acquires a fault code identifying a fault content of a device from a control device that controls the device, extracts a plurality of records including the same fault code as the acquired fault code from the plurality of records in a record storage device having the plurality of records including the fault code and a cause of the fault, and generates count information in which the number of records is associated with each cause;

2. The fault assist device of claim 1,

each process of the set of processes corresponds to a tool to be used,

the interchanging unit interchanges the order of the steps, which can be interchanged, based on the order of the tool determined based on the plurality of steps to be continuously performed.

3. The fault assistance apparatus according to claim 1 or 2,

each process of the process group corresponds to a working place,

the interchanging unit interchanges the order of the steps, the order of which is interchangeable, based on the order of the work place determined based on the plurality of steps to be continuously performed.

4. The fault assistance apparatus according to any one of claims 1 to 3,

the joining unit issues a warning when the process corresponding to the cause included in the frequency information does not exist in the acquired failure handling process.

5. The failure assist device according to any one of claims 1 to 4,

the failure support apparatus further includes a registration receiving unit that receives an instruction to set an interchangeable process, sets the interchangeable process instructed by the instruction to the failure handling process, and registers the failure handling process in the process storage device.

6. The fault assistance apparatus according to any one of claims 1 to 5,

the plurality of records possessed by the record storage means include an installation place of the device,

the extraction unit acquires a model of the device from the control device, extracts a plurality of records including the same fault code as the acquired fault code and the installation location corresponding to the model of the device from the plurality of records in the record storage device by referring to model installation information indicating the model of the device and the correspondence between the model and the installation location of the device, and generates the count information for the number of extracted records corresponding to each of the causes included in the plurality of extracted records.

7. The fault assistance apparatus according to any one of claims 1 to 6,

the apparatus is an elevator.

8. A computer-readable recording medium in which a failure assist program is recorded, wherein the failure assist program causes a computer to execute:

an extraction process of acquiring a fault code for identifying a fault content of a device from a control device for controlling the device, extracting a plurality of records including the same fault code as the acquired fault code from the plurality of records of a record storage device including the fault code and a cause of the fault, and generating count information in which the number of records is associated with each cause;

a combination process of acquiring the trouble handling process including the same trouble code as the acquired trouble code from a process storage device in which a plurality of trouble handling processes including the trouble code, a plurality of processes that are continuously performed and in which the order is interchangeable when the plurality of processes are continuously performed, and a plurality of trouble handling processes indicating process causes of trouble causes corresponding to the respective processes are registered, and combining the number of records of the record corresponding to the cause included in the number-of-times information with the process cause that is the same as the cause included in the number-of-times information among the process causes included in the trouble handling process; and

and an interchange process of interchanging the order of the steps whose order is interchangeable, based on the number of records associated with the process cause, and outputting the failure handling procedure in which the order of the steps is interchanged.

9. A fault assistance method in which, in a fault assistance system,

the computer acquires a fault code for identifying the content of a fault in a device from a control device for controlling the device, extracts a plurality of records including the same fault code as the acquired fault code from the plurality of records in a record storage device having the plurality of records including the fault code and the cause of the fault, and generates count information indicating the number of records corresponding to each cause,

the computer acquires the trouble handling process including the same trouble code as the acquired trouble code from a process storage device in which a plurality of trouble handling processes including the trouble code, a plurality of processes that are continuously performed and in which the order is interchangeable when the plurality of processes are continuously performed, and a plurality of trouble handling processes indicating process causes of trouble causes corresponding to the respective processes are registered, and combines the number of records of the record corresponding to the cause included in the count information with the process causes that are the same as the cause included in the count information among the process causes included in the trouble handling process,

the computer interchanges the order of the processes whose order is interchangeable based on the number of records associated with the process cause, and outputs the failure handling process in which the order of the processes is interchanged.