Passenger transport equipment maintenance system
Through the application of information collection and machine learning model between the elevator fault processing terminal and the fault diagnosis server, high accuracy prediction of elevator fault components and time points is achieved, the problem of low accuracy of fault prediction in the prior art is solved, and the maintenance efficiency and user experience of elevators are improved.
Patent Information
- Application Number
- JP2024564921
- Authority / Receiving Office
- JP · JP
- Patent Type
- Applications
- Current Assignee / Owner
- Priority Date
- 2023-11-02
- Filing Date
- 2024-02-21
- Publication Date
- 2025-05-13
- Estimated Expiration
- 2044-02-21
AI Technical Summary
The existing preventive maintenance technology has low accuracy in predicting elevator failures and cannot be widely used, resulting in short downtime during elevator failures but greater impact.
A maintenance system is designed that collects fault processing results, including fault components and error code information, on the fault processing terminal, and inputs them into the fault diagnosis server. The server uses machine learning models, combined with fault history information, to predict possible future fault components and fault time points, and transmits and displays the prediction results to the fault diagnosis terminal.
By extracting the fault interval information of each component, it can accurately predict the possible failure time points in the future, and then carry out maintenance work in advance to improve the availability and safety of the elevator.
Smart Images

Figure 2025515093000001_ABST
Abstract
Description
[Technical field]
[0001] The present invention relates to a maintenance system for passenger transport equipment capable of predicting failures. [Background technology]
[0002] 2. Description of the Related Art Generally, various types of high-rise buildings constructed for residential, office, commercial, and other purposes are equipped with elevator systems to allow passengers entering and exiting the building to move smoothly between floors.
[0003] An elevator system includes an elevator car that moves up and down along a hoistway formed vertically inside a building to transport passengers with passengers inside the car, a motor unit that generates a predetermined power, a mechanical unit that is equipped with a hoist and the like and moves the elevator car to a corresponding floor according to the passenger's operation of a button, and an elevator control unit that controls the mechanical unit according to the passenger's operation of a button and controls the elevator car so that it can operate smoothly and stably.
[0004] On the other hand, when an elevator device breaks down, even if the breakdown is diagnosed remotely, elevator maintenance personnel will be dispatched to the site to repair the breakdown only after the breakdown has occurred, and passengers will not be able to use the elevator during the time it takes to repair it. Especially in today's situation where there are many high-rise buildings, even a short downtime can be a major inconvenience to users, so predicting elevator breakdowns is very important.
[0005] Due to this trend, there has been active research and development in recent years into predictive maintenance technology for predicting elevator failures.
[0006] This predictive maintenance technology collects information on elevator operating conditions and predicts the occurrence of breakdowns through machine learning and other learning methods. It is extremely important in that it can prevent operational interruptions due to elevator breakdowns and minimize maintenance time.
[0007] However, the current predictive maintenance technologies are not widely used due to their low accuracy, and there is an urgent need to develop technologies that can improve their accuracy.
[0008] (Prior art) Korean Patent No. 10-1775529 Summary of the Invention [Problem to be solved by the invention]
[0009] The present invention has been invented to solve the problems of the prior art, and an object of the present invention is to provide a maintenance system for passenger transportation equipment that can predict future failures with high accuracy based on past failure history information. [Means for solving the problem]
[0010] The present invention provides a maintenance system for a passenger transport device, comprising: a repair terminal carried by a repair worker and configured to input a failure processing result including information on a failed part and an error code after failure processing is completed; and a failure diagnosis server that collects and stores the failure processing results inputted at the repair terminal, and applies the stored failure processing results together with information on a time of failure occurrence to a machine learning model to predict a failed part that may fail in the future and a time of failure occurrence, wherein the repair terminal receives and displays a failure prediction result from the failure diagnosis server.
[0011] In this case, the fault diagnosis server may include a processing result storage unit that collects the fault processing results and stores them together with fault occurrence time information; and a calculation unit that applies the faulty part and error code information of the fault processing results and the fault occurrence time information of each faulty part to a machine learning model to predict faulty parts that may fail in the future and the time when the fault will occur.
[0012] In addition, the processing result storage unit classifies the failure processing results collected from the repair terminal by failed part and stores them in order according to the time of failure occurrence, and the calculation unit calculates a failure occurrence time interval for each failed part stored in the processing result storage unit, and applies each failed part, error code information, and the failure occurrence time interval for each failed part to a machine learning model to predict the time when a future failure may occur for each failed part.
[0013] In addition, the fault diagnosis server collects and stores error code information of the passenger transport device from a passenger transport device control panel and diagnoses the cause of the fault based on the collected error code information, and the repair terminal is connected to the fault diagnosis server so that the error code information stored in the fault diagnosis server and the diagnosis result for the cause of the fault can be transferred and displayed.
[0014] In addition, the fault diagnosis server further includes an error code storage unit that chronologically arranges and stores error code information of the passenger transportation device collected from the passenger transportation device control panel, and classifies and stores the information into one time series data group for every preset reference time interval; and a diagnosis unit that analyzes corresponding error code information for each time series data group stored in the error code storage unit and diagnoses a cause of fault for the time series data group, and the calculation unit can apply the faulty parts, corresponding error code information, and fault occurrence time information calculated through the diagnosis result of the diagnosis unit to a machine learning model to predict faulty parts that may fail in the future and the time when the fault will occur.
[0015] In addition, the calculation unit can integrate the failure prediction result using the failure processing result of the repair terminal device and the failure prediction result using the diagnosis result of the diagnosis unit to calculate one failure prediction result for a faulty part that may fail in the future and the time point at which the failure will occur.
[0016] Meanwhile, the present invention provides a control method for a passenger transport device maintenance system including a repair terminal and a fault diagnosis server, comprising the steps of: inputting fault processing results including faulty part and error code information into the repair terminal; collecting and storing the fault processing results input into the repair terminal through the fault diagnosis server; applying the fault processing results stored in the fault diagnosis server together with fault occurrence time information to a machine learning model to predict faulty parts that may fail in the future and the time of fault occurrence through the fault diagnosis server; and transmitting and displaying the fault prediction results of the fault diagnosis server through the repair terminal.
[0017] In this case, the step of collecting and storing through the fault diagnosis server may include collecting fault processing results from the repair terminal, classifying the collected fault processing results by faulty part, and storing them in order of fault occurrence time, and the step of predicting through the fault diagnosis server may include a step of calculating a fault occurrence time interval for each faulty part stored in the fault diagnosis server; and a step of applying each faulty part, error code information, and fault occurrence time interval for each faulty part stored in the processing result storage unit to a machine learning model to predict a time when a fault may occur for each faulty part in the future. Effect of the Invention
[0018] According to the present invention, a failure occurrence time interval is extracted for each failed part based on past failure history information, and based on this, a future failure occurrence time point can be predicted for each failed part.
[0019] In addition, by predicting the time when a failure may occur in the future, repair work can be carried out in advance before a failure occurs, thereby improving the convenience and safety of using the passenger transportation device. [Brief description of the drawings]
[0020] FIG. 1 is a diagram conceptually illustrating the overall configuration of an elevator maintenance system according to one embodiment of the present invention.
[0021] FIG. 2 is a conceptual diagram illustrating the overall configuration of an elevator maintenance system according to still another embodiment of the present invention.
[0022] FIG. 3 is a block diagram functionally illustrating the configuration of a fault diagnosis server and a repair terminal of an elevator maintenance system according to an embodiment of the present invention.
[0023] 4 and 5 are diagrams illustrating an example of a method of connecting a repair terminal to a fault diagnosis server and a method of displaying a fault diagnosis result in an elevator maintenance system according to an embodiment of the present invention.
[0024] FIG. 6 is a diagram illustrating an example of a form of error code information displayed on a repair terminal according to an embodiment of the present invention.
[0025] FIG. 7 is a diagram illustrating an example of a method for displaying a fault diagnosis result in a repair terminal according to an embodiment of the present invention.
[0026] FIG. 8 is a diagram illustrating an example of a basic information input screen on a processing result input screen of a repair terminal according to an embodiment of the present invention.
[0027] FIG. 9 is a diagram illustrating an example of a part selection input screen in a selection input screen of a processing result input screen according to an embodiment of the present invention.
[0028] FIG. 10 is a diagram illustrating an example of an additional selection input screen in the selection input screen of the processing result input screen according to an embodiment of the present invention.
[0029] FIG. 11 is a diagram illustrating an example of an error code selection input screen in the selection input screen of the processing result input screen according to an embodiment of the present invention.
[0030] FIG. 12 is an operational flow diagram illustrating a failure prediction method for an elevator maintenance system according to one embodiment of the present invention along an operational flow. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS
[0031] Hereinafter, preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. First, when referring to components in each drawing, it should be noted that the same components have the same reference numerals as much as possible even if they are shown in different drawings. In addition, when describing the present invention, detailed descriptions of related known configurations or functions are omitted if it is determined that such descriptions may change the gist of the present invention.
[0032] First, the passenger transport device according to the present invention includes elevators, escalators, and moving walkways, and the following description will be based on elevators.
[0033] FIG. 1 is a diagram conceptually illustrating the overall configuration of an elevator maintenance system according to one embodiment of the present invention, and FIG. 2 is a diagram conceptually illustrating the overall configuration of an elevator maintenance system according to another embodiment of the present invention.
[0034] The elevator maintenance system according to one embodiment of the present invention includes a fault diagnosis server 500 that collects error code information from an elevator control panel 100 and diagnoses the cause of the fault, and a repair terminal 600 that is connected to the fault diagnosis server 500 and receives and displays the error code information and fault diagnosis results.
[0035] First, looking at the overall system configuration, an elevator may include a control panel 100 that controls the operation state of the elevator. The control panel 100 may receive signals related to elevator operation state information. The control panel may receive various fault occurrence signals. The elevator operation state information and fault occurrence signals may be generated by a number of sensors installed in the elevator. The control panel 100 may receive the elevator operation state information and fault occurrence signals through these sensors. Such a control panel 100 may receive and store signals related to the elevator operation state and faults. When a fault occurrence signal is generated, the control panel 100 may generate an error code matching the fault occurrence signal.
[0036] The operation status signal and error code information may be transmitted in real time to the central management server 400 through the communication unit 200. As shown in Fig. 1, the communication unit 200 may communicate with the central management server 400 through a modem 310 to transmit the operation status signal and error code information. As shown in Fig. 2, in the case where a separate monitoring panel is present, the communication unit 200 may communicate with the central management server 400 through a monitoring panel server 320 to transmit the corresponding information.
[0037] The central management server 400 can transmit the received information to a separate fault diagnosis server 500. The fault diagnosis server 500 can receive the operation status signal and the error code information. The fault diagnosis server 500 can be applied as a cloud server and can be connected to the repair terminal 600 through an internet network. The elevator operation status information and the error code information received by the fault diagnosis server 500 can be transmitted to the repair terminal 600. In the repair terminal 600, a user can access the fault diagnosis server 500 through an application program and receive the elevator operation status information and the error code information. In addition, the fault diagnosis server 500 can analyze the received error code information to analyze the cause of the fault. The fault diagnosis server 500 can derive a diagnosis result of the cause of the fault. The fault diagnosis result derived in this way can be provided to the repair terminal 600 through the application program of the repair terminal 600.
[0038] When a fault signal is generated in an elevator or a fault report is received, a repair worker may be selected according to the maintenance system. The selected repair worker may be provided with basic information about the elevator. The basic information about the elevator provided to the repair worker may include the fault report status or basic specifications of the elevator, etc.
[0039] In the elevator maintenance system according to an embodiment of the present invention, the error code and the fault diagnosis result can be transferred to the repair terminal through the fault diagnosis server 500. The repair worker can prepare the necessary parts and equipment before dispatching. This can shorten the time required for troubleshooting and makes troubleshooting easier.
[0040] The detailed configuration of an elevator maintenance system according to an embodiment of the present invention will be described in more detail below.
[0041] FIG. 3 is a block diagram functionally illustrating the configuration of a fault diagnosis server and a repair terminal in an elevator maintenance system according to one embodiment of the present invention. FIG. 4 and FIG. 5 are diagrams illustratively illustrating a fault diagnosis server connection method and a fault diagnosis result display method in a repair terminal in an elevator maintenance system according to one embodiment of the present invention. FIG. 6 is a diagram illustratively illustrating the form of error code information displayed on a repair terminal according to one embodiment of the present invention.
[0042] The elevator maintenance system according to an embodiment of the present invention may include the fault diagnosis server 500 and the repair terminal 600 as described above.
[0043] The fault diagnosis server 500 can collect and store elevator error code information from the elevator control panel 100 and diagnose the cause of the fault based on the collected error code information. The repair terminal 600 can connect to the fault diagnosis server 500 and receive and display the error code information and the diagnosis result for the cause of the fault stored in the fault diagnosis server 500.
[0044] The fault diagnosis server 500 may include a first communication unit 501a, an error code storage unit 502, a diagnosis unit 503, and a second communication unit 501b. In addition, the fault diagnosis server 500 may further include a processing result storage unit 510 and a calculation unit 520 as shown in FIG 3, which will be described later.
[0045] The first communication unit 501a receives error code information recorded in the elevator control panel 100 in real time. As described above, the error code information recorded in the elevator control panel 100 is transferred to the central management server 400, and the first communication unit 501a communicates with the central management server 400 and can receive the error code information from the central management server 400. In addition, the first communication unit 501a can receive elevator operation status information in addition to the error code information recorded in the elevator control panel 100. For example, the first communication unit 501a can receive general elevator operation status information such as elevator speed, floor number, door operation status, and detection signals of various sensors. In particular, the first communication unit 501a can receive various information such as elevator operation status change information at the time when an error code is generated.
[0046] The error code storage unit 502 may store error code information received through the first communication unit 501a, elevator operation status information, etc. The diagnosis unit 503 may diagnose a cause of a malfunction by analyzing the error code information stored in the error code storage unit 502. The diagnosis unit 503 may diagnose a cause of a malfunction when an information request signal is received from the repair terminal 600.
[0047] The second communication unit 501b can communicate with the repair terminal 600 and receive an information request signal from the repair terminal 600. The second communication unit 501b can transmit error code information stored in the error code storage unit 502 and a fault diagnosis result derived by the diagnosis unit 503 to the repair terminal 600. The second communication unit 501b can also transmit various types of information, such as elevator operation status information, stored in the error code storage unit 502, to the repair terminal 600.
[0048] The fault diagnosis server 500 can collect error codes recorded in the elevator control panel 100 and elevator operation status information through the first communication unit 501a and store them in the error code storage unit 502. When the fault diagnosis server 500 receives an information request signal from the repair terminal 600, the fault diagnosis server 500 can diagnose the cause of the fault for the error code through the diagnosis unit 503. In addition, the fault diagnosis server 500 can transmit error code information, fault diagnosis results, elevator operation status information, etc. to the repair terminal 600.
[0049] The repair terminal 600 may refer to a terminal capable of wireless communication carried by a repair worker. The repair terminal 600 may include an input unit 603, a display unit 602, a terminal communication unit 601, and a control unit 604.
[0050] The input unit 603 may be formed in the repair terminal 600 so that a repair worker can perform an input operation. The input unit 603 may be formed in the repair terminal 600 in a touch operation manner through a touch panel or in various forms such as a separate physical button.
[0051] The display unit 602 can display error code information, fault diagnosis results, elevator operation status information, etc., transferred from the fault diagnosis server 500. The display unit 602 can be formed on a display screen formed in the repair terminal 600.
[0052] The terminal communication unit 601 communicates with the second communication unit 501b of the fault diagnosis server 500 to transmit information request signals, etc. to the fault diagnosis server 500, and can receive error code information, fault diagnosis results, elevator operation status information, etc. from the fault diagnosis server 500.
[0053] The control unit 604 can control the operation of the input unit 603, the display unit 602, and the terminal communication unit 601 of the repair terminal 600. When a repair worker generates an input signal through the input unit 603, the control unit 604 can control the operation to transmit an information request signal corresponding to the input signal to the fault diagnosis server 500 through the terminal communication unit 601. In response to the transmission of the information request signal, error code information, fault diagnosis results, elevator operation status information, etc. can be received from the fault diagnosis server 500 through the terminal communication unit 601. The control unit 604 can control the operation to display the error code information, fault diagnosis results, elevator operation status information, etc. received from the fault diagnosis server 500 on the display unit 602.
[0054] When an elevator fault signal is generated, a repair worker is selected, and basic information on the corresponding elevator can be provided to the selected repair worker through the repair terminal 600. In one embodiment of the present invention, error code information and fault diagnosis results can be additionally transferred to the repair terminal 600 through the fault diagnosis server 500.
[0055] In this case, in one embodiment of the present invention, a confirmation request notification message requesting the repair worker to confirm the fault diagnosis result may be transmitted to the repair terminal 600 of the repair worker as shown in Fig. 4. The confirmation request notification message may include a web link address CL of the fault diagnosis server where the fault diagnosis result can be confirmed. The confirmation request notification message may be transmitted to the mobile phone or repair terminal of the repair worker by SMS transmission method as shown in Fig. 4.
[0056] A connection input signal for the web link address CL may be generated when the repair worker touches the web link address CL included in the confirmation request notification message in the SMS format. The control unit 604 may transmit an information request signal corresponding to the web link address CL to the fault diagnosis server 500 in response to the connection input signal. The control unit 604 may control an operation to display the error code information and the fault diagnosis result received from the fault diagnosis server 500 on the display unit 602 in response to the transmission of the information request signal.
[0057] That is, the repair worker can access the fault diagnosis server 500 by touching the web link address CL of the confirmation request notification message transmitted to the repair terminal 600, and can check the error code, the fault diagnosis result, and the like.
[0058] Meanwhile, as shown in Fig. 5, the repair worker may be configured to connect to the fault diagnosis server through a separate repair management program installed in the repair terminal. For example, a connection button CB may be formed in the repair management program of the repair terminal. When the repair worker touches the connection button CB, a connection input signal to the fault diagnosis server 500 may be generated. The control unit 604 may transmit an information request signal corresponding to the connection button CB to the fault diagnosis server 500 in accordance with the connection input signal, and may control an operation such that the error code information and the fault diagnosis result received from the fault diagnosis server 500 are displayed on the display unit 602 in accordance with the transmission of the information request signal.
[0059] That is, the repair worker can connect to the fault diagnosis server 500 and check the error code, fault diagnosis result, etc. by touching the connection button CB formed in the repair management program of the repair terminal 600. At this time, the connection button CB may be formed in the form of a button on which a message such as "connect fault diagnosis" is displayed, as shown in FIG.
[0060] In the repair management program, when checking the past fault handling results, if the repair worker wants to check the fault information such as the past error code information for the corresponding elevator for reference, the repair worker can check the past error code information and fault diagnosis results through the connection button CB. In other words, in the repair management program, the repair worker can touch the connection button CB at any time according to the need of the repair worker. This can improve the consistency of the repair work and can be used as reference information for the repair work by newcomers.
[0061] In summary, when an elevator malfunction occurs, basic information about the elevator is transmitted to the repair terminal of the selected repair worker, and at the same time, a confirmation request for the elevator's error code and the malfunction diagnosis result is transmitted. This can be done in the form of a short message. When a connection input signal is generated through the link address CL included in the short message or the connection button CB of the repair management program, an information request signal is transmitted to the malfunction diagnosis server 500, and the error code and the malfunction diagnosis result are received from the malfunction diagnosis server 500 and can be displayed on the display unit 602 of the repair terminal 600.
[0062] Therefore, a repair worker can check the error code and fault diagnosis results of the elevator before being dispatched to the fault site, and can prepare the necessary parts, equipment, etc. in advance before being dispatched.
[0063] Meanwhile, the error code storage unit 502 of the fault diagnosis server 500 can chronologically arrange and store the error code information received through the first communication unit 501a. The error code storage unit 502 can classify and store one time series data group for each preset reference time interval. The diagnosis unit 503 can analyze the corresponding error code information for each time series data group stored in the error code storage unit 502 and diagnose the cause of a fault for the time series data group.
[0064] 4 and 5, a first output screen 610 having an error code display area 611 where error code information is displayed and a diagnosis result display area 612 where a fault diagnosis result is displayed may be formed on the display unit 602 of the repair terminal 600. At least one error code may be displayed in the error code display area 611 in chronological order and classified and displayed for one time series data group classified by the fault diagnosis server 500. That is, one time series data group may be displayed in one error code display area 611. At this time, one diagnosis result display area 612 may be formed to correspond to one error code display area 611 so that a fault diagnosis result is displayed for each time series data group.
[0065] 6, each error code information displayed in the error code display area 611 includes an error code name EN, an error code occurrence time ET, and elevator operation status information ED at the time the error code occurs. In addition, activation information EA of the corresponding error code may also be displayed.
[0066] For example, the error code name EN indicates the type of error code and may be displayed as "ER_HUP_BTN_JAM", and the time ET at which the error code occurred may be displayed in the lower area. Also, the elevator operation status information ED at the time the error code occurred may display the floor number, current speed / maximum speed (illustrated in FIG. 6 as 3rd floor, current speed 0 / maximum speed 120), etc. Also, the error code activation information EA indicates whether the error code is currently activated or deactivated, and as shown in FIG. 6, when "OFF" is displayed, it can be seen that the error code is currently deactivated.
[0067] With this structure, when a repair worker connects to the fault diagnosis server 500 through the repair terminal 600, the repair terminal 600 displays error code information and fault diagnosis information for the corresponding elevator on its screen. At this time, the error code information displays the error code name, the time of occurrence, and the elevator's operating status information, so that the repair worker can check basic operating status information for the elevator in addition to the fault diagnosis result provided by the fault diagnosis server 500, and can also infer the fault diagnosis result himself from the related error code information.
[0068] That is, in one embodiment of the present invention, a repair worker can access the fault diagnosis server 500 through the repair terminal 600 to check all error codes that have occurred in the elevator, and can predict and assess the on-site situation before dispatching the repair worker to the site.
[0069] In this way, since error codes and elevator operation status information are provided through the repair terminal 600 in addition to the fault diagnosis results, experienced repair workers can determine the cause of the fault by themselves, which differs from the fault diagnosis results provided by the fault diagnosis server 500, and therefore more accurate prediction and on-site response are possible. Also, novice repair workers can smoothly respond to the on-site situation by referring to the fault diagnosis results provided by the fault diagnosis server 500.
[0070] In addition, since a large number of error codes occur in the time period before and after the occurrence of a fault, the fault diagnosis server 500 can receive in real time error code information detected in the elevator control panel 100. Since all error code information and elevator operation status information occurring in the time period before and after the occurrence of a fault can be collected, more accurate fault diagnosis results can be derived.
[0071] Furthermore, error codes that occur in sequence at very short time intervals are classified into time series groups based on a reference time unit, and the cause of the fault is diagnosed for each time series group, thereby making it possible to obtain a quicker and more accurate diagnosis result. The reference time can be set by the error code storage unit 502 of the fault diagnosis server 500.
[0072] For example, the error code storage unit 502 of the fault diagnosis server 500 can set a reference time to 5 minutes and classify and store a plurality of error codes into one time series data group at 5-minute intervals. When a fault occurs in an elevator, error code information is generated continuously around the time of the fault occurrence, which can be classified into one time series data group at 5-minute intervals. In this way, the cause of the fault is diagnosed and provided for each time series data group. Therefore, it is possible to quickly classify and analyze error code information generated at very short time intervals of several seconds at the time of the fault occurrence, and thus to quickly derive a fault diagnosis result, thereby improving the processing speed and accuracy of repair work.
[0073] Meanwhile, a fault diagnosis program capable of diagnosing the cause of a fault by analyzing error code information may be installed in the fault diagnosis server 500. The fault diagnosis program may be configured in such a way that the cause of a fault is diagnosed based on information previously input by a veteran engineer.
[0074] To this end, the fault diagnosis server 500 may include a fault cause storage unit 504 that matches a plurality of pre-specified reference error code information and at least one fault cause corresponding to each of the reference error code information and stores the matched information.
[0075] The diagnosis unit 503 can diagnose a cause of failure for the error code information based on the data stored in the failure cause storage unit 504. For example, the diagnosis unit 503 can learn the mutually matched error code information and at least one or more failure causes as learning data and diagnose a cause of failure for the error code using a machine learning method.
[0076] In addition, when the repair work at the repair work site is completed, the repair worker can input the fault processing result. At this time, the input fault processing result can be transferred to the fault diagnosis server 500 through the central management server 400. The fault diagnosis server 500 can change the information stored in the fault cause storage unit 504 by reflecting the information on the fault processing result of the repair worker.
[0077] To this end, the fault diagnosis server 500 may include a fault cause update unit 505 that reflects information on the fault processing results input by the repair worker and newly matches the fault cause with the reference error code information stored in the fault cause storage unit 504.
[0078] The fault cause update unit 505 updates the error code and the information on the fault cause stored in the fault cause storage unit 504, and the accuracy of the information on the error code and the fault cause can be improved as the amount of data of the fault processing result increases. Therefore, in the elevator maintenance system according to an embodiment of the present invention, the accuracy and reliability of the fault diagnosis result of the fault diagnosis server 500 can be improved as the usage period elapses.
[0079] Meanwhile, if an error occurs for a certain period of time in the communication state between the elevator control panel 100, the central management server 400, and the fault diagnosis server 500, the error code information stored in the elevator control panel 100 may not be transferred to the fault diagnosis server 500 during the time the error occurred. In this case, since all error code information is not transferred to the fault diagnosis server 500, the accuracy of the fault diagnosis result in which the fault diagnosis server 500 diagnoses the cause of the fault based on the error code information may decrease. To prepare for this, a manual collection button may be formed on the first output screen 610 of the repair terminal 600. When the repair worker touches the manual collection button, the error code information, etc. may be collected again from the elevator control panel 100 to the fault diagnosis server 500 for a certain period of time.
[0080] FIG. 7 is a diagram illustrating an example of a method for displaying a fault diagnosis result in a repair terminal according to an embodiment of the present invention.
[0081] In the elevator maintenance system according to an embodiment of the present invention, as described above, when an information request signal is transmitted from the repair terminal 600 to the fault diagnosis server 500 in response to a connection input signal, an error code and a fault diagnosis result can be transmitted from the fault diagnosis server 500 to the repair terminal 600 for each time series data group and displayed thereon.
[0082] However, when a connection input signal is generated from repair terminal 600, an information request signal for the error code is transmitted to fault diagnosis server 500, and a plurality of pieces of error code information can be transmitted to and displayed on repair terminal 600 for each time series data group from fault diagnosis server 500 as shown in Fig. 7. When an information request signal requesting a fault diagnosis result is transmitted through repair terminal 600, diagnosis unit 503 of fault diagnosis server 500 can diagnose the cause of the fault for the error code for each time series data group. Fault diagnosis server 500 can transmit the corresponding fault diagnosis result to repair terminal 600 and display it.
[0083] In other words, the fault diagnosis result for an error code of one time series data group is not immediately provided by connecting to the fault diagnosis server 500, but when a repair worker requests the corresponding diagnosis result, the fault diagnosis server 500 can be configured to diagnose the cause of the fault through a fault diagnosis program and provide the fault diagnosis result to the repair terminal.
[0084] More specifically, when a repair worker touches a link address CL transferred to the repair terminal 600 by a short message or touches a connection button CB of the repair management program to generate a connection input signal, the control unit 604 of the repair terminal 600 can control an operation to transfer an information request signal for error code information to the fault diagnosis server 500. When the fault diagnosis server 500 receives such an information request signal, it transfers the error codes stored in the error code storage unit 502 to the repair terminal 600 for each time series data group, and the control unit 604 of the repair terminal 600 can control an operation to display the transferred error codes for each time series data group on the display unit 602.
[0085] 7(a), the control unit 604 of the repair terminal 600 may control an operation such that, in a state where error code information is classified and displayed by time series data group in the error code display area 611, a diagnosis result request input button 613 for inputting an information request signal for a fault diagnosis result is formed in the diagnosis result display area 612. As described above, since the diagnosis result display area 612 is formed one by one in the error code display area 611 separated for each time series data group, and the diagnosis result request input button 613 is formed in the diagnosis result display area 612, one diagnosis result request input button 613 may be formed for each time series data group.
[0086] In this displayed state, when the repair worker touches the diagnosis result request input button 613 of any one of the time series data groups, an input signal requesting a fault diagnosis result may be generated. When such an input signal is generated, the control unit 604 of the repair terminal 600 may control an operation to transmit an information request signal requesting a fault diagnosis result for the error code information of the corresponding time series data group corresponding to the diagnosis result request input button 613 to the fault diagnosis server 500. The fault diagnosis server 500 diagnoses a fault cause for the error code of the corresponding time series data group through the diagnosis unit 503 in accordance with the information request signal and derives a diagnosis result. The derived fault diagnosis result may be transmitted from the fault diagnosis server 500 to the repair terminal 600. The control unit 604 of the repair terminal 600 may control an operation to display the transmitted fault diagnosis result of the time series data group in the diagnosis result display area 612 of the corresponding time series data group on the first output screen 610. At the same time, the control unit 604 may control an operation to remove the diagnosis result request input button 613 displayed in the diagnosis result display area 612. That is, when the fault diagnosis result is transferred to the repair terminal 600, as shown in FIG. 7(b), the fault diagnosis result may be displayed in the diagnosis result display area 612 while the diagnosis result request input button 613 is removed.
[0087] The diagnosis result request input button 613 formed in the diagnosis result display area 612 may be formed to be touch operable in a form in which a message "CALL" is displayed as shown in FIG.
[0088] With this structure, the fault diagnosis server 500 can diagnose the cause of a fault for a specific time-series data group only when a fault diagnosis result request signal is transmitted from the repair terminal 600. Therefore, it is not necessary to repeatedly diagnose the cause of a fault for all past error codes, and it is not necessary to separately store the fault diagnosis results for all past error codes, which prevents the fault diagnosis server 500 from being overloaded and reduces its capacity.
[0089] Meanwhile, the diagnosis unit 503 of the fault diagnosis server 500 can derive at least one or more fault causes and occurrence probability information for each fault cause together in the process of diagnosing the fault cause for the error code information of one time-series data group. The fault causes and occurrence probability information thus derived can be displayed together in the diagnosis result display area 612 of the repair terminal 600.
[0090] For example, as shown in FIG. 7(b), the fault diagnosis result for the first time series data group is displayed as "Platform Up Button Entrapment (100%)." This means that the cause of the fault is the trap's up button being trapped, and the corresponding fault probability is 100%. The fault diagnosis result for the second time series data group is displayed as "Door motor failure (75%), door trapped (25%)." This may mean that the probability that the cause of the fault is a door motor failure is 75%, and the probability that the door is trapped is 25%.
[0091] In this way, since the probability information for the cause of the failure is also displayed, the repair worker can determine the work order taking the corresponding probability information into account during the failure handling process, so that the repair work can be performed more quickly and accurately.
[0092] On the other hand, when the cause of the failure and / or occurrence probability information displayed in the result display area 612 is selected, a repair guide corresponding to the cause of the failure is displayed. The repair guide may include parts and / or repair methods that can repair the displayed failure.
[0093] The above describes the process of diagnosing the cause of an elevator fault for an error code through the fault diagnosis server 500 and displaying the diagnosis result on the repair terminal 600, i.e., the pre-fault processing process. Through this pre-fault processing process, as described above, the fault processing work can be performed more quickly and efficiently. After that, when the fault processing work is completed, the repair worker inputs the fault processing result into the repair terminal 600.
[0094] Hereinafter, the configuration of the repair terminal 600 capable of inputting such a failure processing result accurately without input errors or omissions will be described with reference to Figs. 8 to 11.
[0095] FIG. 8 is a diagram illustrating an example of a basic information input screen on a processing result input screen of a repair terminal according to one embodiment of the present invention, FIG. 9 is a diagram illustrating an example of a part selection input screen in a selection input screen of a processing result input screen according to one embodiment of the present invention, FIG. 10 is a diagram illustrating an example of an additional selection input screen in a selection input screen of a processing result input screen according to one embodiment of the present invention, and FIG. 11 is a diagram illustrating an example of an error code selection input screen in a selection input screen of a processing result input screen according to one embodiment of the present invention.
[0096] Referring to FIG. 8, the repair terminal 600 according to an embodiment of the present invention may include a processing result input screen 690 where a repair worker can input a failure processing result after completing a failure processing task.
[0097] The processing result input screen 690 may include a basic information input screen 691 for inputting basic information on the fault processing work, and a plurality of selection input screens 692 for inputting the fault processing results by selecting them through a plurality of selection buttons.
[0098] As shown in FIG. 8, the basic information input screen 691 may have a basic information input area 691a in which basic information for the fault handling work can be input. The basic information input area 691a may be formed to allow various information related to the fault handling work to be input. For example, a summary of the fault, details, etc. can be handwritten and input in the basic information input area 691a. An assistant inspector can be selected through an assistant inspector selection menu. If the fault handling is not completed, a reason for unprocessed can be selected through an "Unprocessed Reason" menu formed in the basic information input area 691a.
[0099] The basic information input screen 691 may have a done button 691b for switching the screen to a selection input screen 692 described below. When the repair worker touches the done button 691b after inputting basic information through the basic information input area 691a, the selection input screen 692 may be displayed on the display screen of the repair terminal.
[0100] 9 to 11, information on a malfunctioning part of the elevator may be input into a selection input screen 692. A plurality of selection input screens 692 may be formed so as to be displayed in sequence according to an operation by a repair worker. A plurality of selection buttons may be formed on each selection input screen 692, which display the malfunctioning part, additional information on the malfunction, an error code, etc. Such selection input screen 692 may include a part selection input screen 693, an additional selection input screen 694, and an error code selection input screen 695.
[0101] The part selection input screen 693, the additional selection input screen 694, and the error code selection input screen 695 can be displayed in order according to the input operation of the repair worker. That is, when the selection operation for the selection button of the part selection input screen 693 is completed, the additional selection input screen 694 is displayed, and when the selection operation for the selection button of the additional selection input screen 694 is completed, the error code selection input screen 695 is finally displayed. The repair worker can complete the input operation of the failure processing result by selecting the selection button of the error code selection input screen 695.
[0102] In this manner, a separate screen switching tap for screen switching may be formed in the upper region of each of the plurality of selection input screens 692:693,694,695, and the screen switching for the plurality of selection input screens may be performed by a repair worker touching the screen switching tap. Of course, a separate selection completion button (not shown) may be displayed on each selection input screen, different from the screen switching tap, and the screen may be switched to the next selection input screen when the selection completion button is touched, and the screen switching method may be variously set.
[0103] In this way, the fault processing results can be input by selecting a specific selection button from among a plurality of selection buttons formed on each of a plurality of selection input screens 692:693,694,695 which are switched in sequence, so that the handwritten input process is eliminated from the process of inputting the fault processing results, and the fault processing results can be input accurately without input errors or omissions. Even a novice repair worker can easily input the fault processing results without difficulty.
[0104] The selection input screen 692 will be described in more detail below.
[0105] First, the part selection input screen 693 can be formed so that the repair worker can select and input the faulty part. In other words, the part selection input screen 693 can select and input information on the faulty part. The part selection input screen 693 is formed so that the repair worker can select a plurality of fault-related selection buttons 6931, 6932, 6933, which respectively display a faulty area, a faulty part, and a faulty part in which a fault may occur in the elevator.
[0106] Such a part selection input screen 693 may include a one-stage selection input screen 693a, a two-stage selection input screen 693b, and a three-stage selection input screen 693c, as shown in FIG.
[0107] In the first-stage selection input screen 693a, a plurality of major category selection buttons 6931 for primarily classifying and displaying areas where an elevator may fail may be formed so that the repair worker can select one of them. As shown in FIG. 9(a), the major category selection buttons 6931 may be formed in a manner of displaying a corresponding position together with a visualized image of the elevator. The major category selection buttons 6931 may be formed with four major category selection buttons 6931 for largely classifying areas where an elevator may fail into four areas. For example, the major category selection buttons 6931 for largely classifying areas where an elevator may fail into four major categories, namely, a machine room, an elevator cage, a hoistway / pit, and a hall, may be formed. The repair worker can primarily select the failure area at the major category stage by selecting one of the major category selection buttons 6931 in a touch manner. Of course, this is merely an example, and the areas where an elevator may fail may be divided into various numbers, such as three or five, and formed in the major category selection buttons 6931.
[0108] The two-step selection input screen 693b may be formed so that a repair worker can select a plurality of failure part selection buttons 6932 displaying failure parts where a failure may occur in a failure area corresponding to the major category selection button 6931 selected through the one-step selection input screen 693a. For example, as shown in Fig. 9(b), when the major category selection button 6931 for the machine room is selected on the one-step selection input screen 693a, the two-step selection input screen 693b may be formed with failure part selection buttons 6932 displaying failure parts where a failure may occur in the machine room, such as a control panel PCB, an inverter, a control panel part, etc.
[0109] The three-step selection input screen 693c may be formed so that a repair worker can select a plurality of faulty part selection buttons 6933 displaying faulty parts that may cause a fault in a fault location corresponding to the faulty part selection button 6932 selected through the two-step selection input screen 693b. For example, as shown in Fig. 9(c), when the faulty part selection button 6932 for the control panel PCB is selected on the two-step selection input screen 693b, the three-step selection input screen 693c may be formed with faulty part selection buttons 6933 displaying faulty parts that may cause a fault in the control panel PCB, such as a main board (Main Bd), a safety board (Safety Bd), a power board (Power Bd), etc.
[0110] The first-stage selection input screen 693a, the second-stage selection input screen 693b, and the third-stage selection input screen 693c can be displayed in sequence as the repair worker completes a selection operation on each selection input screen, resulting in the selection input screen for the next stage being displayed.
[0111] For example, as described above, when the selection of the major category selection button 6931 for the machine room is completed on the one-step selection input screen 693a, a two-step selection input screen 693b is displayed on the display screen of the repair terminal, and when the selection of the faulty part selection button 6932 for the control board PCB is completed on the two-step selection input screen 693b, a three-step selection input screen 693c is displayed on the display screen of the repair terminal. When one or more items, for example, the faulty part selection button 6933 for the main board, are selected on the three-step selection input screen 693c, an additional selection input screen 694 described below is displayed. At this time, as described above, a screen switching tap or a separate selection completion button may be formed on each selection input screen, through which screen switching can be performed.
[0112] When the selection input process for the part selection input screen 693 including the three selection input screens 693a, 693b, and 693c is completed, an additional selection input screen 694 may be displayed on the display screen of the repair terminal.
[0113] The additional selection input screen 694 can be formed so that additional information regarding a failure can be selected and input, as shown in Fig. 10. The additional selection input screen 694 can be formed so that a repair worker can select a plurality of additional selection buttons 6941, 6942, 6943 that display the cause of the failure, the entity that caused the failure, and the type of failure handling work.
[0114] Such additional selection input screen 694 may include a failure cause selection input screen 694a, a failure subject selection input screen 694b, and a processing operation selection input screen 694c.
[0115] The fault cause selection input screen 694a may be formed so that a plurality of fault cause addition selection buttons 6941 each displaying a fault occurrence cause that may occur in the elevator can be selected by the repair worker. For example, as shown in Fig. 10(a), a plurality of fault cause addition selection buttons 6941 each displaying a type of fault occurrence cause such as part defect, installation defect, contact defect, etc. may be formed.
[0116] The fault subject selection input screen 694b may be formed so that a repair worker can select a plurality of fault subject additional selection buttons 6942 each displaying a fault subject for a fault that may occur in the elevator. For example, as shown in Fig. 10(b), a plurality of fault subject additional selection buttons 6942 each displaying a type of fault subject such as inspection item, user error, power outage, etc. may be formed.
[0117] The processing operation selection input screen 694c is formed so that a plurality of processing operation addition selection buttons 6943 each indicating a type of fault processing operation for a fault that may occur in the elevator can be selected by the repair worker. For example, as shown in Fig. 10(c), a plurality of processing operation addition selection buttons 6943 each indicating a type of fault processing operation such as adjustment, replacement, removal, etc. can be formed.
[0118] The failure cause selection input screen 694a, the failure subject selection input screen 694b, and the treatment operation selection input screen 694c can display the next selection input screen in sequence as the repair worker completes the selection operation on each selection input screen.
[0119] For example, as described above, when the selection of the failure cause addition selection button 6941 for the component defect is completed on the failure cause selection input screen 694a, a failure subject selection input screen 694b may be displayed on the display screen of the repair terminal. When the selection of the failure subject addition selection button 6942 for the inspection item is completed on the failure subject selection input screen 694b, a processing operation selection input screen 694c may be displayed on the display screen of the repair terminal. When the selection of the processing operation addition selection button 6943 for the adjustment is completed on the processing operation selection input screen 694c, an error code selection input screen 695 described below is displayed. At this time, a screen switching tap or a separate selection completion button may be formed on each selection input screen as described above, and screen switching may be performed through this. Also, each additional selection input screen 694 may be set to allow one selection button or multiple selection buttons to be selected.
[0120] When the selection input process for the additional selection input screen 694 including these three selection input screens 694a, 694b, and 694c is completed, an error code selection input screen 695 may be displayed on the display screen of the repair terminal. The error code selection input screen 695 may be configured to be displayed after the selection input process for the additional selection input screen 694, but since the additional selection input screen 694 is used to input additional information regarding a malfunction, the additional selection input screen 694 may be omitted as necessary, and the error code selection input screen 695 may be configured to be displayed after the selection input process for the part selection input screen 693.
[0121] 11, the error code selection input screen 695 may be formed so that a repair worker can select a plurality of error code selection buttons 6951 each displaying an error code that may cause a failure for a failed part selected through the part selection input screen 693. For example, the repair worker can select a failed part selection button 6933 for the final failed part (main board) on a three-stage selection input screen 693c through one-stage to three-stage selection input screens 693a, 693b, and 693c in the part selection input screen 693. At this time, the error code selection input screen 695 may be formed with a plurality of error code selection buttons 6951 each displaying all error codes that may cause a failure for the selected failed part.
[0122] The repair worker can finally complete the input work of the fault processing results by touching and selecting the error code selection button 6951 corresponding to the error code for which he or she has completed the fault processing from among the multiple error code selection buttons 6951.
[0123] When an elevator malfunctions, multiple error codes are generated, and therefore the repair worker can select multiple error code selection buttons 6951 on the error code selection input screen 695. Fig. 11 illustrates an example in which six error code selection buttons 6951 are selected, and as illustrated in Fig. 11, the six selected error code selection buttons 6951 can be displayed in a different color or shape, etc., so that they can be distinguished from the unselected error code selection buttons 6951.
[0124] Also, in the error code selection input screen 695, when the repair worker touches and selects a plurality of error code selection buttons 6951, the corresponding order may be displayed in one side area of the error code selection buttons 6951 according to the selection order of the error code selection buttons 6951. Exemplarily, in FIG. 11, the corresponding order may be displayed in the form of red circle numbers in the upper right area of the error code selection buttons 6951.
[0125] In this way, when the repair worker inputs the failure treatment results by selecting multiple selection buttons instead of by handwriting input into the repair terminal, the failure treatment results can be input accurately without input errors or omissions. Also, even novice repair workers can easily input the failure treatment results.
[0126] Meanwhile, since the fault processing results inputted to the repair terminal in this manner are highly accurate, they can be collected by the fault diagnosis server 500 described in Figures 1 to 7 and reflected in the fault cause diagnosis process of the fault diagnosis server 500.
[0127] As described above, in the elevator maintenance system according to an embodiment of the present invention, the fault diagnosis server 500 can collect and store elevator error code information from the elevator control panel 100. The fault diagnosis server 500 can diagnose the cause of a fault based on the collected error code information. The error code information and the fault diagnosis result can be transferred to the repair terminal and displayed.
[0128] At this time, the fault diagnosis server 500 can collect the fault processing results inputted through the selection input screen 692 of the repair terminal 600. In the process of diagnosing the cause of a fault based on error code information, the fault diagnosis server 500 can diagnose the cause of a fault by reflecting the fault processing results collected in the past.
[0129] More specifically, the fault diagnosis server 500 may include the fault cause storage unit 504 and the fault cause update unit 505 as described above in order to improve the accuracy of the fault diagnosis by the diagnosis unit 503. The fault cause update unit 505 can newly match the fault cause with the reference error code information stored in the fault cause storage unit 504 by reflecting information on the fault processing result input by the repair worker.
[0130] Therefore, the higher the accuracy of the fault processing result input by the repair technician, the higher the accuracy of the fault diagnosis by the diagnoser 503 can be.
[0131] In one embodiment of the present invention, since the fault processing results are input in a selective input manner through the selective input screen 692 of the repair terminal 600, the accuracy can be improved. Since such highly accurate fault processing results are reflected in the fault cause storage unit 504 through the fault cause update unit 505, the accuracy of the fault diagnosis of the diagnosis unit 503 can be further improved. In particular, as the amount of data of highly accurate fault processing results accumulates, the accuracy of information on error codes and fault causes increases. Therefore, in the elevator maintenance system according to one embodiment of the present invention, the accuracy and reliability of the fault diagnosis results of the fault diagnosis server 500 improves as the period of use passes.
[0132] The above describes a configuration of an elevator maintenance system according to an embodiment of the present invention for analyzing an error code when an elevator fault occurs, diagnosing the cause of the current fault, and displaying the diagnosis result, as well as a configuration for inputting the fault processing result after the fault processing is completed.
[0133] In addition to the above functions, the elevator maintenance system according to an embodiment of the present invention has a configuration for predicting a failure that may occur in the future. Such a failure prediction configuration will be described below.
[0134] FIG. 12 is an operational flow diagram illustrating a failure prediction method for an elevator maintenance system according to one embodiment of the present invention along an operational flow.
[0135] 3, the fault diagnosis server 500 can include the first communication unit 501a, the error code storage unit 502, the diagnosis unit 503, and the second communication unit 501b as described above. Through this structure, the fault diagnosis server 500 collects and stores elevator error code information from the elevator control panel 100, and diagnoses the cause of the fault based on the collected error code information.
[0136] The repair terminal 600 can be connected to the fault diagnosis server 500 and can receive and display error code information and a diagnosis result for a fault cause stored in the fault diagnosis server 500. In addition, the repair terminal 600 is configured to input the fault processing results, such as the faulty parts and error code information, after the fault processing is completed.
[0137] At this time, the fault diagnosis server 500 can collect and store the fault processing results inputted from the repair terminal 600. In addition, the fault diagnosis server 500 can predict a faulty part that may cause a fault in the future and the time of the fault occurrence by applying the stored fault processing results together with fault occurrence time information to a separate machine learning model. The repair terminal 600 can be configured to receive and display the fault prediction results from the fault diagnosis server 500.
[0138] As shown in FIG. 3, the fault diagnosis server 500 may include a processing result storage unit 510 that collects the fault processing results inputted from the repair terminal 600 and stores them together with fault occurrence time information, and a calculation unit 520 that applies the faulty part and error code information of the fault processing results and the fault occurrence time information of each faulty part to a separate machine learning model to predict faulty parts that may fail in the future and the time when the fault will occur.
[0139] In this case, the machine learning model used in the calculation unit 520 is a machine learning model different from the machine learning model used by the diagnosis unit 503 for diagnosing the cause of the failure, and a separate machine learning model may be applied to predict failures that may occur in the future by utilizing past failure processing result information as learning data.
[0140] More specifically, the processing result storage unit 510 may classify the failure processing results collected from the repair terminal 600 by the failed part and store them in order according to the time of failure occurrence. The calculation unit 520 may calculate a failure occurrence time interval for each failed part stored in the processing result storage unit 510. In addition, the calculation unit 520 may be configured to predict a future time when a failure will occur for each failed part by applying each failed part, error code information, and a failure occurrence time interval for each failed part to a machine learning model.
[0141] The elevator's failure history from the past to the present can be expressed in the form of multiple failures occurring in multiple parts. The processing result storage unit 510 can collect all the elevator failure history data, and then sort and store the data in order of the time when the failure occurred for each failed part. For example, the data can be sorted according to the time when the failure occurred for each individual failed part such as a main board, door motor, etc. At this time, the processing result storage unit 510 can store error code information matched with the failed part through the failed part and error code information input during the failure processing result input process.
[0142] The calculation unit 520 may calculate a failure occurrence time interval for each faulty component. The calculation unit 520 may apply each faulty component, error code information, and the failure occurrence time interval for each faulty component to a machine learning model to predict a time when a failure may occur for each individual faulty component in the future. For example, the calculation unit 520 may calculate the failure occurrence time interval of the main board as 1 month, 3 months, and 12 months from the completion date. The calculation unit 520 may predict that the main board may be likely to be broken down 24 months from the completion date in the future. The calculation unit 520 may calculate the failure occurrence time interval of the door motor as 0.5 months, 1 month, 3 months, and 18 months from the completion date in the future, and may predict that the door motor may be likely to be broken down 40 months from the completion date in the future.
[0143] The failure prediction result predicted by the calculation unit 520 in this manner may be transferred to and displayed on the repair terminal 600. A separate failure prediction display screen (not shown) may be formed in the repair terminal 600, and the failure prediction time for each failed part may be displayed on the failure prediction display screen. Alternatively, the failure prediction time for each failed part may be configured to be displayed on any one of the above-mentioned processing result input screens 690 or displayed through screen switching. Also, a setting may be made such that a separate notification is displayed for a failed part that is predicted to fail for the first time from the current time point or a failed part that is predicted to fail within a certain period of time.
[0144] In this way, since the failure prediction result is displayed on the repair terminal 600, the repair worker can refer to the failure prediction result while performing the repair work and repair the specific failed part before the failure occurs. In particular, if the possibility of a failure occurring is imminent, the repair worker can be dispatched to the elevator site separately from the repair work to repair the failed part before the failure occurs. As a result, the elevator can be prevented from failing before it occurs, and the convenience and safety of the elevator can be further enhanced.
[0145] To summarize this failure prediction method, as shown in Fig. 12, first, a process of inputting failure processing results including faulty parts and error code information to the repair terminal 600 can be performed (S10). Then, the failure processing results input to the repair terminal 600 can be collected and stored by the fault diagnosis server 500 (S20). The fault diagnosis server 500 can apply the stored failure processing results together with failure occurrence time information to a machine learning model to predict faulty parts that may cause future failures and the time of failure occurrence (S30). Then, the repair terminal 600 can receive the failure prediction results from the fault diagnosis server 500 and display them on the screen (S40).
[0146] At this time, in the step of collecting and storing the fault processing results through the fault diagnosis server 500 (S20), the fault processing results are collected from the repair terminal 600, and the collected fault processing results are classified by faulty parts and stored in the processing result storage unit 510 in order of the time of fault occurrence.
[0147] The step of predicting a time when a failure will occur (S30) may include a step of calculating a time interval when a failure will occur for each failed component stored in the processing result storage unit 510 (S31), and a step of predicting a time when a failure may occur for each failed component by applying the information on each failed component and the error code stored in the processing result storage unit 510 and the time interval when a failure will occur for each failed component to a machine learning model (S32). The step of predicting a time when a failure will occur (S30) may be performed by the calculation unit 520.
[0148] In the above, it has been explained that the calculation unit 520 of the fault diagnosis server 500 predicts future faults for each individual component based on the fault processing results inputted to the repair terminal 600. However, in another embodiment of the present invention, the calculation unit 520 can predict future faults for each individual component based on the diagnosis results of the diagnosis unit 503.
[0149] As described above, the fault diagnosis server 500 may include an error code storage unit 502. The error code storage unit 502 may chronologically arrange and store elevator error code information collected from an elevator control panel, and classify and store the information into one time series data group for each preset reference time interval. The diagnosis unit 503 may analyze the corresponding error code information for each time series data group stored in the error code storage unit 502, and diagnose the cause of a fault for the time series data group.
[0150] At this time, the calculation unit 520 applies the faulty part and the corresponding error code information calculated as the cause of the failure through the diagnosis result of the diagnosis unit 503 together with the failure occurrence time information to the machine learning model, thereby predicting the faulty part that may fail in the future and the time when the failure will occur.
[0151] More specifically, the diagnosis unit 503 can extract the faulty part and the corresponding error code information corresponding to the fault cause in the fault cause diagnosis process. The calculation unit 520 can collect all the diagnosis results of the diagnosis unit 503 from past data and calculate the fault occurrence time interval for each faulty part. Based on this, the calculation unit 520 can predict the time when a fault may occur for each faulty part by applying each faulty part, the error code information, and the fault occurrence time interval for each faulty part to a machine learning model. The fault prediction process of the calculation unit 520 is the same as the fault prediction process based on the above-mentioned fault processing result input data, except that data based on the diagnosis result of the diagnosis unit 503 is used as learning data to be applied to the machine learning model.
[0152] In other words, the calculation unit 520 can predict the faulty part and the time when the fault will occur based on the fault processing result information input through the repair terminal 600, or can predict the faulty part and the time when the fault will occur based on the diagnosis result information by the diagnosis unit 503.
[0153] In this way, the calculation unit 520 can predict failures using two different methods, but can integrate the respective failure prediction results by a method such as averaging to calculate one failure prediction result. In other words, the failure prediction result using the failure processing result of the repair terminal 600 and the failure prediction result using the diagnosis result of the diagnosis unit 503 can be integrated to calculate one failure prediction result for a failed part that may fail in the future and the time point at which the failure will occur.
[0154] In this way, by predicting future failures based on two types of information, more accurate failure prediction results can be calculated.
[0155] In particular, the diagnosis unit 503 of the fault diagnosis server 500 diagnoses the cause of a fault by reflecting the fault processing results inputted from the repair terminal 600, so that the accuracy of the fault cause diagnosis results of the diagnosis unit 503 improves as time passes, and accordingly, the accuracy of the fault prediction results of the calculation unit 520 based on the diagnosis results of the diagnosis unit 503 also improves as time passes.
[0156] The above description is merely illustrative of the technical idea of the present invention, and various modifications and variations are possible within the scope of the essential characteristics of the present invention, if one has ordinary knowledge in the technical field to which the present invention belongs. Therefore, the embodiments disclosed in the present invention are for illustrative purposes only, and are not intended to limit the technical idea of the present invention, and the scope of the technical idea of the present invention is not limited by such embodiments. The scope of protection of the present invention should be interpreted according to the following claims, and all technical ideas within the scope equivalent thereto should be interpreted as being included in the scope of the present invention.
[0157] (Explanation of symbols)
[0158] 100: Elevator control panel
[0159] 200: Communications Department
[0160] 310: Modem
[0161] 320: Monitoring panel server
[0162] 400: Central Management Server
[0163] 500: Fault diagnosis server
[0164] 501a: 1st Communication Department
[0165] 501b:Second Communication Department
[0166] 502: Error code storage section
[0167] 503: Diagnostics Department
[0168] 504: Failure cause storage section
[0169] 505: Failure cause update section
[0170] 510: Processing result storage unit
[0171] 520: Arithmetic section
[0172] 600: Repair terminal
[0173] 601: Terminal communication unit
[0174] 602: Display section
[0175] 603: Input section
[0176] 604: Control unit
[0177] 610: First output screen
[0178] 611: Error code display area
[0179] 612: Diagnostic result display area
[0180] 613: Diagnostic result request input button
[0181] 690: Processing result input screen
[0182] 691: Basic information input screen
[0183] 692: Selection input screen
[0184] 693: Part selection input screen
[0185] 6931: Major category selection button
[0186] 6932: Faulty part selection button
[0187] 6933: Faulty part selection button
[0188] 694: Additional selection input screen
[0189] 6941: Additional fault cause selection button
[0190] 6942: Additional selection button for fault subject
[0191] 6943: Processing operation addition selection button
[0192] 695: Error code selection input screen
[0193] 6951: Error code selection button
Claims
1. A repair terminal carried by a repair worker and configured to input the results of the repair including information on the faulty parts and error code after the repair is completed; and a fault diagnosis server that collects and stores the fault processing results inputted from the repair terminal and applies the stored fault processing results together with fault occurrence time information to a machine learning model to predict faulty parts that may cause future faults and the time of the fault occurrence; wherein the repair terminal receives and displays a failure prediction result from the failure diagnosis server.
2. The fault diagnosis server includes: a processing result storage unit that collects the failure processing results and stores them together with failure occurrence time information; and a calculation unit for applying information on faulty parts and error codes obtained as a result of the fault processing and information on the time when each faulty part is faulty to a machine learning model to predict faulty parts that may be faulty in the future and the time when the fault will occur; 2. A maintenance system for a passenger transportation device as claimed in claim 1, comprising:
3. The processing result storage unit classifies the failure processing results collected from the repair terminal by failure part and stores them in order of failure occurrence time, 3. The passenger transport device maintenance system of claim 2, wherein the calculation unit calculates a failure occurrence time interval for each faulty part stored in the processing result storage unit, and applies each faulty part, error code information, and the failure occurrence time interval for each faulty part to a machine learning model to predict a time when a future failure may occur for each faulty part.
4. The fault diagnosis server collects and stores error code information of the passenger transport device from a passenger transport device control panel, diagnoses the cause of the fault based on the collected error code information, 3. The passenger transport device maintenance system of claim 2, wherein the repair terminal is connected to the fault diagnosis server and transmits and displays error code information and a diagnosis result for a cause of a fault stored in the fault diagnosis server.
5. The fault diagnosis server includes: an error code storage unit that chronologically arranges and stores the error code information of the passenger transport device collected from the passenger transport device control panel, and classifies and stores the information into one time series data group for each preset reference time interval; and a diagnosis unit for analyzing corresponding error code information for each time-series data group stored in the error code storage unit and diagnosing a cause of a failure for the time-series data group; and wherein the calculation unit applies the faulty part, the corresponding error code information, and the fault occurrence time information calculated through the diagnosis result of the diagnosis unit to a machine learning model to predict a faulty part that may fail in the future and a time point at which the fault will occur.
6. The passenger transport equipment maintenance system of claim 5, wherein the calculation unit integrates a failure prediction result using the failure processing result of the repair terminal and a failure prediction result using the diagnosis result of the diagnosis unit to calculate one failure prediction result for a faulty part that may fail in the future and a time point at which the fault will occur.
7. A method for controlling a passenger transport device maintenance system including a repair terminal and a fault diagnosis server, inputting a failure processing result including information on a failed part and an error code into the repair terminal; collecting and storing the fault processing results inputted to the repair terminal through the fault diagnosis server; Applying the failure processing result stored in the failure diagnosis server together with failure occurrence time information to a machine learning model to predict a faulty part that may fail in the future and a time when the fault will occur through the failure diagnosis server; and a step of transmitting and displaying a failure prediction result of the failure diagnosis server through the repair terminal; 13. A method for controlling a passenger transportation device maintenance system, comprising:
8. In the step of collecting and storing the information through the fault diagnosis server, Collecting failure processing results from the repair terminal, classifying the collected failure processing results by the faulty parts and storing them in order according to the time of fault occurrence; The step of predicting through the fault diagnosis server includes: calculating a failure occurrence time interval for each of the faulty parts stored in the fault diagnosis server; and applying each faulty part, error code information, and fault occurrence time interval for each faulty part stored in the processing result storage unit to a machine learning model to predict a time when a fault may occur in the future for each faulty part; 8. The method of claim 7, further comprising:
Citation Information
Patent Citations
Remote monitoring system for lifter
JP2007176618A
Information processor and information processing program
JP2018147080A
Failure prediction device and failure prediction method
JP2019206247A
Failure correspondence support person arrangement system and failure correspondence support person arrangement method
JP2022143727A
System for part lifetime prediction of elevator
KR1020180130614A