Maintenance management system of passenger transfer device

Abstract

The present invention relates to a maintenance management system for a passenger transfer device, and provides a maintenance management system for a passenger transfer device, characterized by comprising: a maintenance terminal which is carried by a maintenance worker and is formed so as to be able to input a failure processing result including a failure component and error code information after failure processing is completed; and a fault diagnosis server which collects and stores the fault processing result input from the maintenance terminal, and applies the stored fault processing result and fault occurrence time information to a machine learning model to predict a fault component which may fail in the future and a fault occurrence time point, and the maintenance terminal receives the fault prediction result from the fault diagnosis server and displays the fault prediction result.

Description

Technical Field

[0001] The present invention relates to a maintenance management system for a passenger transfer device capable of predicting failures. Background Art

[0002] Generally, in various types of high-rise buildings such as residential buildings, business buildings, and commercial buildings, elevator devices are installed to facilitate smooth movement of passengers entering and exiting the corresponding buildings between floors.

[0003] An elevator device is composed of the following: an elevator car, which moves in the up and down directions along a lifting path formed in the vertical direction inside a building when there are passengers inside, and at the same time moves the passengers; a mechanical part, including a motor part and a traction machine that generate a specified power, and moves the elevator car to the corresponding floor according to the button operation of the passenger; and an elevator control part, which controls the mechanical part according to the button operation of the passenger and controls the elevator car in a way that allows it to operate smoothly and stably.

[0004] On the other hand, when a fault occurs in an elevator device, even if the fault is diagnosed remotely, elevator maintenance personnel can only go to the site to repair the fault after the fault occurs, so passengers cannot use the elevator during the repair period. In particular, with many high-rise buildings today, even a short downtime can cause great inconvenience to users, so it is very important to predict elevator failures in advance.

[0005] In accordance with this trend, a predictive maintenance technology for predicting elevator failure in advance has been actively studied and developed recently.

[0006] This predictive maintenance technology is a technology that collects information about the elevator's operating status and predicts failures in advance through machine learning. It is very important in preventing operation interruptions caused by elevator failures and minimizing maintenance time.

[0007] However, the fact is that currently developed predictive maintenance technologies have not been widely used due to their low accuracy, and there is an urgent need to develop technologies for improving accuracy.

[0008] (Prior Art Document) Korean Registered Patent No. 10-1775529 Summary of the invention

[0009] Technical issues

[0010] The present invention is invented to solve the problems of the prior art, and an object of the present invention is to provide a maintenance management system for a passenger transfer device that can predict possible future failures with high accuracy based on past failure history information.

[0011] Problem Solving Methods

[0012] The present invention provides a maintenance management system for a passenger transfer device, which is characterized in that it includes: a maintenance terminal, which is carried by maintenance personnel and is configured to input a fault handling result including faulty components and error code information after the fault handling is completed; and a fault diagnosis server, which collects and stores the fault handling results input from the maintenance terminal, applies the stored fault handling results together with the fault occurrence time information to a machine learning model to predict the faulty components and fault occurrence time points that may fail in the future, and the maintenance terminal receives and displays the fault prediction results from the fault diagnosis server.

[0013] At this time, the fault diagnosis server may include: a processing result storage unit, which collects the fault processing results and stores them together with the fault occurrence time information; and a calculation unit, which applies the faulty components and error code information of the fault processing results and the fault occurrence time information of each faulty component to a machine learning model to predict the faulty components and fault occurrence time points that may fail in the future.

[0014] In addition, the processing result storage unit classifies the fault processing results collected from the maintenance terminal according to faulty components, and stores them in sequence according to the fault occurrence time sequence. The calculation unit can calculate the fault occurrence time interval of each faulty component stored in the processing result storage unit, and apply each faulty component and error code information and the fault occurrence time interval of the faulty component to the machine learning model to predict the future fault occurrence time point of each faulty component.

[0015] In addition, the fault diagnosis server collects and stores error code information of the passenger transfer device from the passenger transfer device control panel, and diagnoses the cause of the fault based on the collected error code information. The maintenance terminal can be connected to the fault diagnosis server to receive and display the error code information stored in the fault diagnosis server and the diagnosis results of the cause of the fault.

[0016] In addition, the fault diagnosis server also includes: an error code storage unit, which arranges and stores the error code information of the passenger transfer device collected from the passenger transfer device control panel in chronological order, and classifies it into a time series data group for storage at every preset reference time interval; and a diagnosis unit, which analyzes the corresponding error code information of each time series data group stored in the error code storage unit, and diagnoses the cause of the fault of the time series data group. The calculation unit can apply the faulty components calculated by the diagnosis results of the diagnosis unit and the corresponding error code information and fault occurrence time information to the machine learning model to predict the faulty components and fault occurrence time points that may fail in the future.

[0017] In addition, the calculation unit may combine the fault prediction result using the fault processing result of the maintenance terminal with the fault prediction result using the diagnosis result of the diagnosis unit to calculate a fault prediction result for the faulty components that may fail in the future and the time point of the fault occurrence.

[0018] On the other hand, the present invention provides a control method for a passenger transfer device maintenance and management system, which is a control method for a passenger transfer device maintenance and management system including a maintenance terminal and a fault diagnosis server, and is characterized in that it includes the following steps: inputting a fault handling result including faulty components and error code information into the maintenance terminal; collecting and storing the fault handling results input into the maintenance terminal through the fault diagnosis server; applying the fault handling results stored in the fault diagnosis server together with the fault occurrence time information to a machine learning model, and predicting the faulty components and fault occurrence time points that may fail in the future through the fault diagnosis server; and receiving and displaying the fault prediction results of the fault diagnosis server through the maintenance terminal.

[0019] At this time, in the step of collecting and storing through the fault diagnosis server, the fault handling results are collected from the maintenance terminal, and the collected fault handling results are classified according to the fault components, and stored in sequence according to the fault occurrence time sequence. The step of predicting through the fault diagnosis server may include the following steps: calculating the fault occurrence time interval of each fault component stored in the fault diagnosis server; and applying each fault component and error code information and the fault occurrence time interval of the fault component stored in the processing result storage unit to the machine learning model to predict the future fault occurrence time point of each fault component.

[0020] Effects of the Invention

[0021] According to the present invention, based on the past fault history information, the fault occurrence time interval of each fault component is extracted, and based on this, the possible future fault occurrence time point of each fault component can be predicted.

[0022] In addition, by predicting the time point at which a failure may occur in the future, maintenance work can be performed in advance before the failure occurs, thereby having the effect of improving the ease of use and safety of the passenger transfer device. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 This is a diagram conceptually showing the overall configuration of an elevator maintenance management system according to an embodiment of the present invention.

[0024] Figure 2 This is a diagram conceptually showing the overall configuration of an elevator maintenance management system according to still another embodiment of the present invention.

[0025] Figure 3 It is a block diagram functionally showing the structure of a fault diagnosis server and a maintenance terminal of an elevator maintenance management system according to an embodiment of the present invention.

[0026] Figure 4 and Figure 5 The figure exemplarily shows a connection mode of a maintenance terminal to a fault diagnosis server and a display mode of a fault diagnosis result in an elevator maintenance management system according to an embodiment of the present invention.

[0027] Figure 6 FIG. 1 is a diagram exemplarily showing the form of error code information displayed on a maintenance terminal according to an embodiment of the present invention.

[0028] Figure 7 FIG. 4 is a diagram exemplarily showing a method of displaying a fault diagnosis result in a maintenance terminal according to an embodiment of the present invention.

[0029] Figure 8 FIG. 1 is a diagram exemplarily showing a basic information input screen in a processing result input screen of a maintenance terminal according to an embodiment of the present invention.

[0030] Fig. 9 FIG. 1 is a diagram exemplarily showing a component selection input screen in a selection input screen of a processing result input screen according to an embodiment of the present invention.

[0031] Fig.10 FIG. 1 is a diagram exemplarily showing an additional selection input screen in the selection input screen of the processing result input screen according to an embodiment of the present invention.

[0032] Fig.11 FIG. 1 is a diagram exemplarily showing an error code selection input screen in a selection input screen of a processing result input screen according to an embodiment of the present invention.

[0033] Fig.12 The present invention is a flowchart showing a fault prediction method of an elevator maintenance management system according to an embodiment of the present invention according to an action flow. DETAILED DESCRIPTION

[0034] Hereinafter, the preferred embodiments of the present invention will be described in detail with reference to the accompanying drawings. First, when assigning reference symbols to the components of the drawings, it should be noted that the same components should be assigned the same symbols as much as possible even if they are shown in other drawings. In addition, when describing the present invention, if it is considered that the detailed description of the relevant known structure or function may obscure the gist of the present invention, its detailed description will be omitted.

[0035] First, the passenger transfer device according to the present invention includes an elevator, an escalator and a moving walkway. The following description will be based on the elevator.

[0036] Figure 1 FIG. 2 is a diagram conceptually showing the overall structure of an elevator maintenance management system according to an embodiment of the present invention. Figure 2 This is a diagram conceptually showing the overall configuration of an elevator maintenance management system according to another embodiment of the present invention.

[0037] According to an embodiment of the present invention, the maintenance management system of an elevator includes the following: a fault diagnosis server (500), which collects error code information from the elevator control panel (100) to diagnose the cause of the fault; and a maintenance terminal (600), which is connected to the fault diagnosis server (500) and receives and displays the error code information and the fault diagnosis result.

[0038] First, the entire system structure is described. The elevator may include a control panel (100) for controlling the operation state of the elevator. The control panel (100) may receive a signal about the operation state information of the elevator. The control panel may receive various fault occurrence signals. The operation state information and the fault occurrence signal of the elevator may be generated by a plurality of sensors arranged in the elevator. The control panel (100) may receive the operation state information and the fault occurrence signal of the elevator through these sensors. These control panels (100) may receive and store signals related to the operation state and fault of the elevator. When a fault occurrence signal occurs, the control panel (100) may generate an error code matching the fault occurrence signal.

[0039] The actuation status signal and error code information can be transmitted to the central management server (400) in real time through the communication unit (200). Figure 1 As shown, the communication unit (200) can communicate with the central management server (400) through its own modem (310) and transmit the operation status signal and error code information. Figure 2 As shown, when there is a separate monitoring panel, the communication unit (200) can communicate with the central management server (400) through the monitoring panel server (320) and transmit corresponding information.

[0040] The central management server (400) may transmit the received relevant information to a separate fault diagnosis server (500). The fault diagnosis server (500) may receive an actuation state signal and error code information. The fault diagnosis server (500) is used as a cloud server and may be connected to a maintenance terminal (600) via the Internet. The actuation state information and error code information of the elevator received by the fault diagnosis server (500) may be transmitted to the maintenance terminal (600). In the maintenance terminal (600), a user may connect to the fault diagnosis server (500) via an application to receive the actuation state information and error code information of the elevator. In addition, the fault diagnosis server (500) may analyze the received error code information to analyze the cause of the fault. The fixed diagnosis server (500) may obtain a diagnosis result of the cause of the fault. The fault diagnosis result obtained in this manner may be provided to the maintenance terminal (600) via an application of the maintenance terminal (600).

[0041] When a fault signal of an elevator occurs or a fault report is received, a maintenance worker may be selected according to the maintenance management system. Basic information about the corresponding elevator may be provided to the selected maintenance worker. The basic information of the elevator provided to the maintenance worker may include the fault report status or the basic specifications of the elevator.

[0042] In the maintenance management system of an elevator according to an embodiment of the present invention, the error code and the fault diagnosis result can be transmitted to the maintenance terminal through the fault diagnosis server (500). The maintenance staff can prepare the required parts or equipment before going out. Therefore, the fault handling time can be shortened and the fault handling work can be performed more easily.

[0043] Hereinafter, the detailed structure of the elevator maintenance management system according to an embodiment of the present invention will be described in more detail.

[0044] Figure 3 is a block diagram functionally illustrating the configuration of a fault diagnosis server and a maintenance terminal of an elevator maintenance management system according to an embodiment of the present invention. Figure 4 and Figure 5 1 is a diagram exemplarily showing a fault diagnosis server connection mode of a maintenance terminal and a fault diagnosis result display mode in an elevator maintenance management system according to an embodiment of the present invention, Figure 6 FIG. 1 is a diagram exemplarily showing the form of error code information displayed on a maintenance terminal according to an embodiment of the present invention.

[0045] The maintenance management system for an elevator according to an embodiment of the present invention may include a fault diagnosis server (500) and a maintenance terminal (600), as described above.

[0046] The fault diagnosis server (500) can collect and store the error code information of the elevator from the elevator control panel (100), and diagnose the cause of the fault based on the collected error code information. The maintenance terminal (600) can be connected to the fault diagnosis server (500), receive and display the diagnosis results about the error code information and the cause of the fault stored in the fault diagnosis server (500).

[0047] 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 also include a processing result storage unit (510) and a calculation unit (520), such as Figure 3 As shown, the description of this will be described below.

[0048] The first communication unit (501a) receives the 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 transmitted to the central management server (400). 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, in addition to the error code information recorded in the elevator control panel (100), the first communication unit (501a) can also receive the actuation state information of the elevator. For example, the first communication unit (501a) can receive the actuation state information of the general elevator, such as the speed, number of floors, door actuation state, and sensing signals of various sensors. In particular, the first communication unit (501a) can receive various information such as the actuation state change information of the elevator at the time when the error code occurs.

[0049] The error code storage unit (502) can store error code information and elevator operation status information received through the first communication unit (501a). The diagnosis unit (503) can analyze the error code information stored in the error code storage unit (502) to diagnose the cause of the fault. When the diagnosis unit (503) receives an information request signal from the maintenance terminal (600), it can diagnose the cause of the fault.

[0050] The second communication unit (501b) can communicate with the maintenance terminal (600) and receive an information request signal from the maintenance terminal (600). The second communication unit (501b) can transmit the error code information stored in the error code storage unit (502) and the fault diagnosis result obtained by the diagnosis unit (503) to the maintenance terminal (600). The second communication unit (501b) can also transmit various information such as the operation state information of the elevator stored in the error code storage unit (502) to the maintenance terminal (600).

[0051] The fault diagnosis server (500) can collect the error code and elevator actuation status information recorded in the elevator control panel (100) 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 maintenance terminal (600), the fault diagnosis server (500) can diagnose the cause of the fault of the error code through the diagnosis unit (503). In addition, the fault diagnosis server (500) can transmit the error code information, the fault diagnosis result and the actuation status information of the elevator to the maintenance terminal (600).

[0052] The maintenance terminal (600) may refer to a terminal that can communicate wirelessly and is carried by maintenance personnel. The maintenance terminal (600) may include an input unit (603), a display unit (602), a terminal communication unit (601) and a control unit (604).

[0053] The input unit (603) can be formed on the maintenance terminal (600) so that the maintenance staff can perform input operations. The input unit (603) can be formed in various forms such as touch operation on the maintenance terminal (600) through a touch panel, or a separate physical button.

[0054] The display unit (602) can display error code information, fault diagnosis results, elevator operation status information, etc. transmitted from the fault diagnosis server (500). The display unit (602) can form a display screen formed in the maintenance terminal (600).

[0055] The terminal communication unit (601) communicates with the second communication unit (501b) of the fault diagnosis server (500), and can transmit information request signals, etc. to the fault diagnosis server (500) or receive error code information, fault diagnosis results and elevator operation status information, etc. from the fault diagnosis server (500).

[0056] The control unit (604) can perform action control on the input unit (603), the display unit (602) and the terminal communication unit (601) of the maintenance terminal (600). When the maintenance staff generates an input signal through the input unit (603), the control unit (604) can perform action control to transmit an information request signal corresponding to the corresponding input signal to the fault diagnosis server (500) through the terminal communication unit (601). According to the transmission of these information request signals, error code information, fault diagnosis results, and elevator actuation status information, etc. can be received from the fault diagnosis server (500) through the terminal communication unit (601). The control unit (604) can perform action control to display the error code information, fault diagnosis results, and elevator actuation status information, etc. received from the fault diagnosis server (500) on the display unit (602).

[0057] When a fault signal is generated in the elevator, a maintenance worker is selected, and basic information about the corresponding elevator can be provided to the selected maintenance worker through the maintenance terminal (600). In one embodiment of the present invention, the error code information and the fault diagnosis result can be additionally transmitted to the maintenance terminal (600) through the fault diagnosis server (500).

[0058] At this time, in one embodiment of the present invention, if Figure 4 As shown, a confirmation request notification message requesting confirmation of the fault diagnosis result may be transmitted to the maintenance terminal (600) of the maintenance staff. The confirmation request notification message may include the network link address (CL) of the fault diagnosis server that can confirm the fault diagnosis result. Figure 4 As shown, the confirmation request notification message can be transmitted to the mobile phone or maintenance terminal of the maintenance staff through a short message service (SMS) transmission mode.

[0059] The maintenance staff can generate a connection input signal for the network link address (CL) by touching the network link address (CL) included in the confirmation request notification message in the SMS format. The control unit (604) can transmit an information request signal corresponding to the network link address (CL) to the fault diagnosis server (500) based on these connection input signals. The control unit (604) can perform action control based on the transmission of the information request signal so that the error code information and fault diagnosis results received from the fault diagnosis server (500) are displayed on the display unit (602).

[0060] That is, the maintenance staff can connect to the fault diagnosis server (500) to confirm the error code and fault diagnosis result, etc. by touching the network link address (CL) of the confirmation request notification information transmitted to the maintenance terminal (600).

[0061] On the other hand, Figure 5 As shown, it can be configured so that the maintenance staff can connect to the fault diagnosis server through a separate maintenance management program set in the maintenance terminal. For example, a connection button (CB) can be formed in the maintenance management program of the maintenance terminal. When the maintenance staff touches the connection button (CB), a connection input signal to the fault diagnosis server (500) can be generated. The control unit (604) can transmit an information request signal corresponding to the connection button (CB) to the fault diagnosis server (500) based on these connection input signals, and perform action control based on the transmission of the information request signal so that the error code information and fault diagnosis results received from the fault diagnosis server (500) are displayed on the display unit (602).

[0062] That is, the maintenance worker touches the connection button (CB) formed in the maintenance management program of the maintenance terminal (600), thereby connecting to the fault diagnosis server (500) to confirm the error code and fault diagnosis results, etc. At this time, the connection button (CB) can be formed in the form of a button displaying text such as "fault diagnosis connection", such as Figure 5 shown.

[0063] In the maintenance management program, when confirming the past fault handling results, when confirming the fault information such as the past error code information about the corresponding elevator as a reference, the past error code information and the fault diagnosis result can be confirmed by the connection button (CB). That is, in the maintenance management program, the connection button (CB) can be touched at any time according to the needs of the maintenance staff to confirm the error code information and the fault diagnosis result about the corresponding elevator. This can improve the compatibility of the maintenance work, and can also be used as reference information for maintenance work for unskilled people.

[0064] In summary, when an elevator fails, basic information about the corresponding elevator can be transmitted to the maintenance terminal of the selected maintenance staff, and at the same time, a confirmation request notification about the error code and fault diagnosis result of the corresponding elevator can be transmitted. This can be achieved by SMS. If a connection input signal is generated by a link address (CL) contained in the SMS or a connection button (CB) of the maintenance management program, an information request signal can be transmitted to the fault diagnosis server (500), and the error code and fault diagnosis result can be received from the fault diagnosis server (500) and displayed on the display unit (602) of the maintenance terminal (600).

[0065] Therefore, before the maintenance staff goes to the fault site, they can confirm the error code and fault diagnosis results of the corresponding elevator, so that they can prepare the necessary parts and equipment in advance.

[0066] On the other hand, the error code storage unit (502) of the fault diagnosis server (500) can arrange and store the error code information received through the first communication unit (501a) in time sequence. The error code storage unit (502) can classify and store the error code information into a time series data group at every preset reference time interval. The diagnosis unit (503) can analyze the corresponding error code information of each time series data group stored in the error code storage unit (502) to diagnose the cause of the fault of the time series data group.

[0067] In addition, if Figure 4 and Figure 5As shown, in the display unit (602) of the maintenance terminal (600), a first output screen (610) having an error code display area (611) for displaying error code information and a diagnosis result display area (612) for displaying the fault diagnosis result can be formed. In the error code display area (611), at least one or more error codes are displayed in chronological order, and can be classified and displayed according to a time series data group classified in the fault diagnosis server (500). That is, it can be formed to display a time series data group in an error code display area (611). At this time, a diagnosis result display area (612) can be formed in a manner corresponding to each error code display area (611) to display the fault diagnosis result of each time series data group.

[0068] In addition, if Figure 6 As shown, each error code information displayed in the error code display area (611) includes the error code name (EN), the error code occurrence time (ET) and the elevator actuation state information (ED) at the error code occurrence time point. In addition, the activation information (EA) of the corresponding error code can also be displayed simultaneously.

[0069] For example, the error code name (EN) indicates the type of error code and can be displayed as "ER_HUP_BTN_JAM", and the time when the corresponding error code occurred (ET) can be displayed in the lower area. In addition, the elevator's actuation status information (ED) at the time when the corresponding error code occurred can display the number of floors, current speed / maximum speed (in Figure 6 In the figure, it is shown as 3 layers, current speed 0 / maximum speed 120), etc. In addition, the activation information (EA) of the error code indicates whether the corresponding error code is currently in an active state or an inactive state, such as Figure 6 As shown, when it is indicated as "OFF", it can be known that the corresponding error code is currently in an inactive state.

[0070] According to the structure as described above, when the maintenance staff is connected to the fault diagnosis server (500) through the maintenance terminal (600), the error code information and fault diagnosis information about the corresponding elevator are displayed on the screen of the maintenance terminal (600). At this time, the error code information displays the error code name, the time of occurrence and the actuation status information of the elevator, etc. Therefore, in addition to the fault diagnosis results provided by the fault diagnosis server (500), the maintenance staff can also confirm the basic actuation status information about the elevator, and the maintenance staff can infer the fault diagnosis results by themselves through the relevant error code information.

[0071] That is, in one embodiment of the present invention, maintenance personnel are connected to the fault diagnosis server (500) via the maintenance terminal (600), so that all error codes occurring in the corresponding elevator can be confirmed, and the on-site conditions can be predicted and judged in advance before going out to the site.

[0072] As described above, in addition to the fault diagnosis result, the maintenance terminal (600) receives the error code and the elevator operation status information, so that for skilled maintenance personnel, they can judge the fault cause different from the fault diagnosis result provided by the fault diagnosis server (500), and can make more accurate predictions and on-site responses. In addition, for unskilled maintenance personnel, they can refer to the fault diagnosis result provided by the fault diagnosis server (500) and smoothly perform on-site responses.

[0073] In addition, many error codes may occur in the time period before and after the fault occurs, and the fault diagnosis server (500) may receive the detected error code information in real time from the elevator control panel (100). All error code information and elevator actuation status information occurring in the time period before and after the fault occurs may be collected, thereby obtaining a more accurate fault diagnosis result.

[0074] Furthermore, error codes that occur sequentially at very short time intervals are classified separately in units of time series groups of reference time units, and the cause of the fault is diagnosed in units of time series groups, thereby obtaining a more accurate diagnosis result more quickly. The reference time can be set by an error code storage unit (502) of the fault diagnosis server (500).

[0075] For example, the error code storage unit (502) of the fault diagnosis server (500) sets the reference time to 5 minutes, and can classify multiple error codes into a time series data group at intervals of 5 minutes for storage. When a fault occurs in the elevator, error code information occurs continuously before and after the time point of the fault occurrence, and the error code information can be classified into a time series data group at intervals of 5 minutes. As described above, the cause of the fault is diagnosed and provided according to a time series data group. Therefore, at the time point of the fault occurrence, the error code information that occurs at extremely short intervals can be quickly classified and analyzed in units of a few seconds, thereby quickly obtaining a fault diagnosis result and improving the processing speed and accuracy of the maintenance work.

[0076] On the other hand, the fault diagnosis server (500) may be provided with a fault diagnosis program that can analyze the error code information to diagnose the cause of the fault. The fault diagnosis program may be configured to diagnose the cause of the fault based on information pre-entered by a skilled technician.

[0077] To this end, the fault diagnosis server (500) may include a fault cause storage unit (504) that matches and stores a plurality of pre-specified reference error information with at least one fault cause that corresponds to each of the reference error code information.

[0078] The diagnosis unit (503) can diagnose the fault cause of the error code information based on the data stored in the fault cause storage unit (504). For example, the diagnosis unit (503) can learn the error code information and at least one fault cause that match each other through learning data, and diagnose the fault cause of the error code in a machine learning manner.

[0079] In addition, when the maintenance work is completed at the maintenance site, the maintenance staff can input the fault processing results. At this time, the input fault processing results can be transmitted to the fault diagnosis server (500) through the central management server (400). The fault diagnosis server (500) can reflect the information about the fault processing results of these maintenance staff and change the information stored in the fault cause storage unit (504).

[0080] To this end, the fault diagnosis server (500) may include a fault cause updating unit (505) which reflects the information on the fault processing result input by the maintenance staff to re-match the fault cause of the reference error code information stored in the fault cause storage unit (504).

[0081] By making new changes to the information about the error code and the cause of the fault stored in the fault cause storage unit (504) through the fault cause updating unit (505), the more data of the fault processing result, the higher the accuracy of the information about the error code and the cause of the fault. Therefore, according to the elevator maintenance management system of one 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 use time goes by.

[0082] On the other hand, when the communication state between the elevator control panel (100), the central management server (400) and the fault diagnosis server (500) is wrong within a certain period of time, the error code information stored in the elevator control panel (100) may not be transmitted to the fault diagnosis server (500) during the error occurrence time. In this case, since the error code information is not all transmitted to the fault diagnosis server (500), the accuracy of the fault diagnosis result based on the error code information in the fault diagnosis server (500) may decrease. A manual collection button can be formed in the first output screen (610) of the maintenance terminal (600) to cope with this situation. When the maintenance staff touches the manual collection button, the error code information and the like can be collected from the elevator control panel (100) to the fault diagnosis server (500) again within a certain period of time.

[0083] Figure 7 FIG. 4 is a diagram exemplarily showing a method of displaying a fault diagnosis result in a maintenance terminal according to an embodiment of the present invention.

[0084] According to an elevator maintenance management system of one embodiment of the present invention, as described above, when an information request signal is transmitted from a maintenance terminal (600) to a fault diagnosis server (500) according to a connection input signal, an error code and a fault diagnosis result can be transmitted from the fault diagnosis server (500) to the maintenance terminal (600) and displayed in a time series data group.

[0085] However, when a connection input signal is generated from the maintenance terminal (600), an information request signal for an error code is transmitted to the fault diagnosis server (500), and Figure 7 As shown, a plurality of error code information can be transmitted from the fault diagnosis server (500) to the maintenance terminal (600) in a time series data group and displayed. When an information request signal requesting a fault diagnosis result is transmitted through the maintenance terminal (600), the diagnosis unit (503) of the fault diagnosis server (500) can diagnose the cause of the fault related to the error code in the time series data group. The fault diagnosis server (500) can transmit the corresponding fault diagnosis result to the maintenance terminal (600) and display it.

[0086] That is, it can be configured so that when the maintenance staff requests the corresponding diagnostic result, the fault diagnosis server (500) diagnoses the cause of the fault through a fault diagnosis program and provides the fault diagnosis result to the maintenance terminal, instead of immediately providing a fault diagnosis result of an error code of a time series data group as the connection to the fault diagnosis server (500) is made.

[0087] More specifically, when a maintenance worker touches a link address (CL) transmitted to a maintenance terminal (600) by a text message or touches a connection button (CB) of a maintenance management program to generate a connection input signal, a control unit (604) of the maintenance terminal (600) can perform action control to transmit an information request signal for error code information to a fault diagnosis server (500). Upon receiving these information request signals, the fault diagnosis server (500) transmits the error codes stored in the error code storage unit (502) to the maintenance terminal (600) in a time series data group, and the control unit (604) of the maintenance terminal (600) can perform action control to display the error codes of each received time series data group on the display unit (602).

[0088] At this time, if Figure 7 As shown in (a), in a state where the error code display area (611) classifies and displays the error code information by time series data group, the control unit (604) of the maintenance terminal (600) can perform action control to form a diagnosis result request input button (613) in the diagnosis result display area (612) for inputting an information request signal for the fault diagnosis result. As described above, since one diagnosis result display area (612) is formed in one error code display area (611) separated by 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) can be formed for each time series data group.

[0089] In the state displayed as described above, when the maintenance staff touches the diagnosis result request input button (613) of any time series data group, an input signal requesting a fault diagnosis result may be generated. When such an input signal occurs, the control unit (604) of the maintenance terminal (600) may perform action control to transmit the information request signal corresponding to the diagnosis result request input button (613) requesting the fault diagnosis result of the corresponding time series data group regarding the error code information to the fault diagnosis server (500). The fault diagnosis server (500) diagnoses the cause of the fault of the error code of the corresponding time series data group through the diagnosis unit (503) according to these information request signals, and obtains a diagnosis result. The obtained fault diagnosis result may be transmitted from the fault diagnosis server (500) to the maintenance terminal (600). The control unit (604) of the maintenance terminal (600) may perform action control to display the fault diagnosis result of the received time series data group in the diagnosis result display area (612) of the corresponding time series data group of the first output screen (610). At the same time, action control can be performed 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 transmitted to the maintenance terminal (600), if Figure 7 As shown in (b), the diagnosis result request input button (613) can be removed from the diagnosis result display area (612), while the fault diagnosis result is displayed.

[0090] The diagnosis result request input button (613) formed in the diagnosis result display area (612) can be formed in a touch-operated manner by displaying the word "import", such as Figure 7 shown.

[0091] With this structure, the fault diagnosis server (500) can diagnose the fault cause of a specific time series data group only when a fault diagnosis result request signal is transmitted from the maintenance terminal (600). Therefore, there is no need to repeatedly diagnose the fault cause of all past error codes, and there is no need to separately store the fault diagnosis results of all past error codes, thereby preventing the fault diagnosis server (500) from being overloaded and miniaturizing the capacity.

[0092] On the other hand, the diagnosis unit (503) of the fault diagnosis server (500) can obtain at least one fault cause and occurrence probability information about each fault cause as a diagnosis result during the process of diagnosing the fault cause of the error code information of a time series data group. The fault cause and occurrence probability information obtained in this way can be displayed together in the diagnosis result display area (612) of the maintenance terminal (600).

[0093] For example, Figure 7 As shown in (b), the fault diagnosis result for the first time series data group can be displayed as "the floor station up button is stuck (100%)". This may mean that the cause of the fault is that the floor station up button is stuck, and the probability of the corresponding fault is 100%. The fault diagnosis result for the second time series data group can be displayed as "door motor failure (75%), door stuck (25%)". This may mean that the probability that the fault cause is the door motor failure is 75%, and the probability that the door is stuck is 25%.

[0094] As described above, by simultaneously displaying the probability information of the fault causes, maintenance personnel can determine the work sequence by considering the corresponding probability information during the fault handling process, thereby performing maintenance work more quickly and accurately.

[0095] On the other hand, when the fault cause and / or occurrence probability information displayed in the result display area (612) is selected, a maintenance guide corresponding to the fault cause may be displayed. The maintenance guide may include a component and / or maintenance method that can repair the displayed fault.

[0096] The above describes the process of diagnosing the cause of the fault code through the fault diagnosis server (500) and displaying the diagnosis result on the maintenance terminal (600) when the elevator fails, that is, the process before the fault processing. As described above, through this process before the fault processing, the fault processing work can be performed more quickly and effectively. Afterwards, when the fault processing work is completed, the maintenance staff inputs the fault processing result into the maintenance terminal (600).

[0097] The following Figures 8 to 11 The structure of a maintenance terminal (600) that can accurately input such a fault processing result without causing input errors or omissions is described as the center.

[0098] Figure 8 is a diagram exemplarily showing a basic information input screen in a processing result input screen of a maintenance terminal according to an embodiment of the present invention, Fig. 9 FIG. 1 is a diagram exemplarily showing a component selection input screen in a selection input screen of a processing result input screen according to an embodiment of the present invention, Fig.10 is a diagram exemplarily showing an additional selection input screen in a selection input screen of a processing result input screen according to an embodiment of the present invention, Fig.11 FIG. 1 is a diagram exemplarily showing an error code selection input screen in a selection input screen of a processing result input screen according to an embodiment of the present invention.

[0099] Reference Figure 8 According to an embodiment of the present invention, the maintenance terminal (600) may include a processing result input screen (690) for the maintenance staff to input the fault processing result after completing the fault processing work.

[0100] The processing result input screen (690) may include a basic information input screen (691) for inputting basic information of the fault processing work and a multiple selection input screen (692) for inputting the fault processing result by selecting the fault processing result through multiple selection buttons.

[0101] The basic information input screen (691) may form a basic information input area (691a) for inputting basic information of the fault handling work, such as Figure 8 As shown. In the basic information input area (691a), various information related to the fault handling work can be input. For example, the fault summary, detailed content, etc. can be input by handwriting in the basic information input area (691a). The auxiliary inspector can be selected through the auxiliary inspector selection menu. When the fault handling is not completed, the unhandled reason can be selected through the "unhandled reason" menu formed in the basic information input area (691a).

[0102] A completion button (691b) for switching the screen to a selection input screen (692) described later may be formed in the basic information input screen (691). After the maintenance worker inputs basic information in the basic information input area (691a) and touches the completion button (691b), the selection input screen (692) may be displayed on the display screen of the maintenance terminal.

[0103] Reference Figures 9 to 11 In the selection input screen (692), information about the faulty part of the elevator can be input. A plurality of selection input screens (692) can be formed so as to be displayed in sequence according to the operation of the maintenance staff. In each selection input screen (692), a plurality of selection buttons for displaying the faulty part, additional information of the fault, an error code, etc. can be formed. Such a selection input screen (692) can include a part selection input screen (693), an additional selection input screen (694), and an error code selection input screen (695).

[0104] The component selection input screen (693), the additional selection input screen (694), and the error code selection input screen (695) can be displayed in sequence according to the input operation of the maintenance staff. That is, when the selection work of the selection button of the component selection input screen (693) is completed, the additional selection input screen (694) is displayed, and when the selection work of the selection button of the additional selection input screen (694) is completed, the error code selection input screen (695) can be displayed last. The maintenance staff can complete the input work of the fault processing result by selecting the selection button of the error code selection input screen (695).

[0105] As described above, a separate screen switching label for screen switching can be formed in the upper area of ​​each of the plurality of selection input screens (692: 693, 694, 695), and the screen switching of the plurality of selection input screens can be completed by the maintenance staff touching the screen switching label. Of course, a separate selection completion button (not shown) can be displayed in each selection input screen, and the screen switching method can be variously set, such as the method of switching to the next selection input screen when the selection completion button is touched.

[0106] As described above, since the fault handling result can be input by selecting a specific selection button from among the multiple selection input screens (692: 693, 694, 695) that are respectively formed by switching the screens in sequence, the handwriting input process is eliminated in the input process of the fault handling result, so that the fault handling result can be accurately input without input errors or omissions of the fault handling result. Even in the case of unskilled maintenance personnel, the fault handling result can be easily input without difficulty.

[0107] The selection input screen (692) will be described in more detail below.

[0108] First, the component selection input screen (693) can be formed so that the maintenance staff can select and input the component where the fault occurs. In other words, the component selection input screen (693) can select and input information about the fault location. The component selection input screen (693) can be selectively formed by the maintenance staff to form a plurality of fault-related selection buttons (6931, 6932, 6933) that respectively display the fault area, fault location, and fault component that may cause a fault in the elevator.

[0109] This component selection input screen (693) is as follows Fig. 9 As shown, it may include a one-stage selection input screen (693a), a two-stage selection input screen (693b) and a three-stage selection input screen (693c).

[0110] In the first-stage selection input screen (693a), a plurality of large classification selection buttons (6931) for first classifying and displaying the areas where a failure may occur in the elevator can be selectively formed by the maintenance staff. Fig. 9 As shown in (a), the major category selection buttons (6931) can be formed together with the visual image of the elevator in a manner that displays the corresponding position. The major category selection buttons (6931) can form four major category selection buttons (6931) that roughly classify the areas where the elevator may fail into four areas. For example, a major category selection button (6931) that classifies the areas where the elevator may fail into the four major categories of the machine room, elevator car (cage), lifting path / pit, and floor station (hall) can be formed. The maintenance staff can select any of these major category selection buttons (6931) by touch to select the fault area for the first time in the major classification step. Of course, this is exemplary, and the areas where the elevator may fail can also be divided into 3 or 5 or other numbers to form major category selection buttons (6931).

[0111] The second-stage selection input screen (693b) can be selectively formed by the maintenance staff into a plurality of fault location selection buttons (6932), wherein the fault location selection buttons (6932) display the fault locations that may fail in the fault area corresponding to the large category selection button (6931) selected through the first-stage selection input screen (693a). Fig. 9As shown in (b), if the large category selection button (6931) of the mechanical room is selected in the first-stage selection input screen (693a), a fault location selection button (6932) displaying possible fault locations in the mechanical room, such as the control panel printed circuit board (PCB), inverter, control panel components, etc., can be formed in the second-stage selection input screen (693b).

[0112] The three-stage selection input screen (693c) can be selectively formed by the maintenance staff into a plurality of fault component selection buttons (6933), wherein the fault component selection buttons (6933) display the fault components that may fail in the fault location corresponding to the fault location selection button (6932) selected through the two-stage selection input screen (693b). Fig. 9 As shown in (c), if the fault part selection button (6932) of the control panel PCB is selected in the second-stage selection input screen (693b), a fault part selection button (6933) that displays the faulty parts that may fail in the control panel PCB, such as the main board (Main Bd), the safety board (Safety Bd), the power board (Power Bd), etc., can be formed in the third-stage selection input screen (693c).

[0113] In each of the first-stage selection input screen (693a), the second-stage selection input screen (693b) and the third-stage selection input screen (693c), the next-stage selection input screen can be displayed in sequence according to the completion of the maintenance staff's selection operation.

[0114] For example, as described above, when the selection of the large category selection button (6931) of the machine room is completed in the first-stage selection input screen (693a), the second-stage selection input screen (693b) is displayed on the display screen of the maintenance terminal. When the selection of the fault part selection button (6932) of the control panel PCB is completed in the second-stage selection input screen (693b), the third-stage selection input screen (693c) is displayed on the display screen of the maintenance terminal. When the selection of any one or more, such as the fault part selection button (6933) of the main board, is completed in the three-stage selection input screen (693c), the additional selection input screen (694) described later is displayed. At this time, the screen switching label or a separate selection completion button as described above can be formed in each selection input screen, thereby realizing screen switching.

[0115] When the selection input process of the component selection input screen (693) including these three selection input screens (693a, 693b, 693c) is completed, an additional selection input screen (694) may be displayed in the display screen of the maintenance terminal.

[0116] Additional selection input screen (694) such as Fig.10 As shown, additional information of the fault can be selected and input. In the additional selection input screen (694), a plurality of additional selection buttons (6941, 6942, 6943) showing the cause of the fault, the subject of the fault, and the type of fault handling work can be selectively formed by the maintenance staff.

[0117] Such additional selection input screen (694) may include a fault cause selection input screen (694a), a fault subject selection input screen (694b), and a processing work selection input screen (694c).

[0118] The fault cause selection input screen (694a) can be selectively formed by the maintenance staff to form a plurality of fault cause additional selection buttons (6941) that respectively display the causes of the faults that may occur in the elevator. Fig.10 As shown in (a), a plurality of additional selection buttons (6941) for the causes of the fault may be formed to respectively display the types of causes of the fault, such as component failure, setting failure, and contact failure.

[0119] The fault subject selection input screen (694b) can be selectively formed by the maintenance staff to form a plurality of fault subject additional selection buttons (6942) that respectively display the fault subjects for the faults that may occur in the elevator. Fig.10 As shown in (b), a plurality of additional selection buttons (6942) for fault subjects may be formed to respectively display the types of fault subjects such as inspection items, user errors, power outages, etc.

[0120] The processing work selection input screen (694c) can be selectively formed by the maintenance staff to form a plurality of processing work additional selection buttons (6943) that respectively display the types of fault processing work for the faults that may occur in the elevator. Fig.10 As shown in (c), a plurality of additional selection buttons (6943) for processing work may be formed to respectively display the types of troubleshooting work such as adjustment, replacement, and clearing.

[0121] In each of the selection input screens of the fault cause selection input screen (694a), the fault subject selection input screen (694b) and the processing work selection input screen (694c), the selection input screen of the next stage can be displayed in sequence according to the completion of the selection operation by the maintenance staff.

[0122] For example, as described above, when the selection of the additional selection button (6941) for the fault cause of component failure is completed in the fault cause selection input screen (694a), the fault subject selection input screen (694b) can be displayed in the display screen of the maintenance terminal. When the selection of the additional selection button (6942) for the fault subject of the inspection item is completed in the fault subject selection input screen (694b), the processing work selection input screen (694c) can be displayed in the display screen of the maintenance terminal. When the selection of the additional selection button (6943) for the processing work of adjustment is completed in the processing work selection input screen (694c), the error code selection input screen (695) described later is displayed. At this time, the screen switching label or a separate selection completion button as described above can be formed in each selection input screen, thereby realizing screen switching. In addition, in each additional selection input screen (694), it can be set so that one selection button or multiple selection buttons can be selected.

[0123] When the selection input process of the additional selection input screen (694) including the three selection input screens (694a, 694b, 694c) is completed, the error code selection input screen (695) can be displayed on the display screen of the maintenance terminal. This error code selection input screen (695) can also be configured to be displayed after the selection input process of the additional selection input screen (694), but the additional selection input screen (694) is additional information for inputting the fault, so the additional selection input screen (694) can be omitted as needed, and it can also be configured to be displayed after the selection input process of the component selection input screen (693).

[0124] like Fig.11 As shown, the error code selection input screen (695) can be selectively formed by the maintenance staff to form a plurality of error code selection buttons (6951) that respectively display the error codes that may cause the failure for the failed component selected through the component selection input screen (693). For example, the maintenance staff can go through the steps of the one-stage selection input screen to the three-stage selection input screen (693a, 693b, 693c) in the component selection input screen (693), and select the final failed component (mainboard) in the three-stage selection input screen (693c). At this time, in the error code selection input screen (695), a plurality of error code selection buttons (6951) that respectively display all the error codes that may cause the failure for the selected failed component can be formed.

[0125] The maintenance staff can finally complete the input of the fault handling result by touching and selecting the error code selection button (6951) corresponding to the error code for completing their own fault handling among these multiple error code selection buttons (6951).

[0126] When an elevator breaks down, multiple error codes will occur, so in the error code selection input screen (695), the maintenance staff can select multiple error code selection buttons (6951). Fig.11 The case where six error code selection buttons (6951) are selected is exemplarily shown in FIG. Fig.11 As shown, the selected six error code selection buttons (6951) can be displayed in different colors or shapes, etc., so as to be distinguishable from the unselected error code selection buttons (6951).

[0127] In addition, in the error code selection input screen (695), when the maintenance staff touches and selects multiple error code selection buttons (6951), the corresponding order can be displayed in the area on one side of the error code selection buttons (6951) according to the selection order of the error code selection buttons (6951). Fig.11 For these selection sequences, the corresponding sequence can be displayed in the form of numbers displayed in a red circle in the upper right area of ​​the error code selection button (6951).

[0128] As mentioned above, when the maintenance staff inputs the fault handling result by selecting a plurality of selection buttons rather than by handwriting input to the maintenance terminal, the fault handling result can be accurately input without input errors or omissions. In addition, unskilled maintenance staff can also easily input the fault handling result.

[0129] On the other hand, the fault processing result input to the maintenance terminal in the above-mentioned manner has high accuracy, so it can be Figures 1 to 7 The fault diagnosis server (500) described in the above description collects and reflects the fault cause diagnosis process of the fault diagnosis server (500).

[0130] According to the maintenance management system of an elevator of an embodiment of the present invention, as described above, the fault diagnosis server (500) can collect and store the error code information of the elevator from the elevator control panel (100). The fault diagnosis server (500) can diagnose the cause of the fault based on the collected error code information. The error code information and the fault diagnosis result can be transmitted to the maintenance terminal and displayed.

[0131] At this time, the fault diagnosis server (500) can collect the fault processing results input through the selection input screen (692) of the maintenance terminal (600). In the process of diagnosing the cause of the fault based on the error code information, the fault diagnosis server (500) can reflect the fault processing results collected in the past to diagnose the cause of the fault.

[0132] More specifically, the fault diagnosis server (500) may include a fault cause storage unit (504) and a fault cause update unit (505) as described above, so as to improve the fault diagnosis accuracy of the diagnosis unit (503). The fault cause update unit (505) may reflect the information on the fault processing result input by the maintenance staff, and re-match the fault cause of the reference error code information stored in the fault cause storage unit (504).

[0133] Therefore, the higher the accuracy of the fault processing result input by the maintenance staff, the higher the fault diagnosis accuracy of the diagnosis unit (503) can be.

[0134] In one embodiment of the present invention, since the fault handling result is inputted through the selection input screen (692) of the maintenance terminal (600) in a selection input mode, the accuracy can be improved. Since such a high-accuracy fault handling result is reflected in the fault cause storage unit (504) through the fault cause update unit (505), the fault diagnosis accuracy of the diagnosis unit (503) can be further improved. In particular, as the amount of data of the high-accuracy fault handling result accumulates, the accuracy of the information on the error code and the cause of the fault can continue to increase. Therefore, according to the maintenance management system of the elevator in one embodiment of the present invention, the accuracy and reliability of the fault diagnosis result of the fault diagnosis server (500) can be continuously improved as the use time goes by.

[0135] The following contents are explained above: in the elevator maintenance management system according to one embodiment of the present invention, when an elevator fails, the current fault cause is diagnosed by analyzing the error code and the diagnosis result is displayed, as well as the fault handling result input process after the fault handling is completed.

[0136] In addition to these functions, the elevator maintenance management system according to an embodiment of the present invention also has a structure for predicting possible future failures. This failure prediction structure is described below.

[0137] Fig.12 The present invention is a flowchart showing a fault prediction method of an elevator maintenance management system according to an embodiment of the present invention according to an action flow.

[0138] First, refer to Figure 3 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) as described above. With this structure, the fault diagnosis server (500) collects and stores the error code information of the elevator from the elevator control panel (100), and diagnoses the cause of the fault based on the collected error code information.

[0139] The maintenance terminal (600) can be connected to the fault diagnosis server (500) to receive and display the error code information and the diagnosis result of the fault cause stored in the fault diagnosis server (500). In addition, the maintenance terminal (600) is formed to input the fault processing result such as the fault component and the error code information after the fault processing is completed.

[0140] At this time, the fault diagnosis server (500) may collect and store the fault processing results input from the maintenance terminal (600). In addition, the fault diagnosis server (500) applies the stored fault processing results together with the fault occurrence time information to a separate machine learning model to predict the faulty components and the time point of the fault occurrence that may fail in the future. The maintenance terminal (600) may be configured to receive and display the fault prediction results from the fault diagnosis server (500).

[0141] like Figure 3 As shown, the fault diagnosis server (500) may include: a processing result storage unit (510), which collects the fault processing results input from the maintenance terminal (600) and stores them together with the fault occurrence time information; and a calculation unit (520), which applies the fault component and error code information of the fault processing results and the fault occurrence time information of each fault component to a separate machine learning model to predict the fault components and fault occurrence time points that may fail in the future.

[0142] At this time, the machine learning model used in the calculation unit (520) is a machine learning model different from the machine learning model used in the diagnosis unit (503) to diagnose the cause of the fault. A separate machine learning model can be applied that uses past fault handling result information as learning data to predict possible future faults.

[0143] More specifically, the processing result storage unit (510) can classify the fault processing results collected from the maintenance terminal (600) by fault components and store them in order according to the fault occurrence time. The calculation unit (520) can calculate the fault occurrence time interval of each fault component stored in the processing result storage unit (510). In addition, the calculation unit (520) can be configured to apply each fault component and error code information and the fault occurrence time interval of the fault component to a machine learning model to predict the future fault occurrence time point of each fault component.

[0144] The fault history of the elevator from the past to the present may be manifested as multiple faults occurring in multiple components. After the processing result storage unit (510) collects all the fault history data of the elevator, it can arrange and store them in order according to the fault occurrence time of each fault component. For example, it can be arranged according to the fault occurrence time by each individual fault component such as the main board, the door motor, etc. At this time, the processing result storage unit (510) can store the error code information matching the fault component together with the fault component and the error code information input in the fault processing result input process.

[0145] The calculation unit (520) can calculate the time interval between the failures of each faulty component. Furthermore, the calculation unit (520) applies each faulty component and the error code information and the time interval between the failures of the faulty components to the machine learning model, so as to predict the future time points of the failures of each individual faulty component. For example, the calculation unit (520) can calculate the time interval between the failures of the main board, such as 1 month, 3 months, and 12 months from the date of completion. Furthermore, the calculation unit (520) can predict that the main board may fail 24 months from the date of completion in the future. In addition, the calculation unit (520) can calculate the time interval between the failures of the door motor, such as 0.5 months, 1 month, 3 months, and 18 months from the date of completion, and predict that the door motor may fail 40 months from the date of completion in the future.

[0146] As described above, the fault prediction result predicted by the calculation unit (520) can be transmitted to the maintenance terminal (600) and displayed. A separate fault prediction display screen (not shown) can be formed in the maintenance terminal (600), and the fault prediction time point of the faulty component can be displayed in the fault prediction display screen. Different from this, the fault prediction time point of the faulty component can be configured to be displayed in any one of the above-mentioned processing result input screens (690) or displayed by screen switching. In addition, for the faulty component that is predicted to fail first from the current time point or the faulty component that is predicted to fail within a period of time, a separate notification can be set.

[0147] As described above, by displaying the fault prediction result on the maintenance terminal (600), the maintenance staff can refer to the fault prediction result when performing maintenance work to pre-repair the specific faulty component before the fault occurs. In particular, when the possibility of a fault is approaching, in addition to the maintenance work, the maintenance staff can also go to the corresponding elevator site to pre-repair the corresponding faulty component. Therefore, the occurrence of a fault can be prevented before the elevator fails, thereby further enhancing the convenience and safety of elevator use.

[0148] Summarizing the fault prediction methods mentioned above, Fig.12As shown, first, a process of inputting a fault handling result including a fault component and an error code information in a maintenance terminal (600) may be performed (S10). Afterwards, the fault handling result input into the maintenance terminal (600) may be collected and stored by the fault diagnosis server (500) (S20). The fault diagnosis server (500) may apply the stored fault handling result together with the fault occurrence time information to a machine learning model to predict the fault component and the fault occurrence time point that may fail in the future (S30). Afterwards, the maintenance terminal (600) may receive the fault prediction result of the fault diagnosis server (500) and display it on the screen (S40).

[0149] At this time, in the step (S20) of collecting and storing fault processing results through the fault diagnosis server (500), the fault processing results can be collected from the maintenance terminal (600), and the collected fault processing results can be classified according to the fault components and stored in the processing result storage unit (510) in sequence according to the time sequence of the fault occurrence.

[0150] The step of predicting the time point of failure occurrence (S30) can be achieved by executing the following processes: a process of calculating the time interval of failure occurrence of each faulty component stored in the processing result storage unit (510) (S31); and a process of applying each faulty component and the error code information and the time interval of failure occurrence of the faulty component stored in the processing result storage unit (510) to a machine learning model to predict the future time point of failure occurrence of each faulty component (S32). The step of predicting the time point of failure occurrence (S30) can be achieved by the calculation unit (520).

[0151] The above describes a situation in which the calculation unit (520) of the fault diagnosis server (500) predicts possible future failures of individual components based on the fault processing results input into the maintenance terminal (600). However, in another embodiment of the present invention, the calculation unit (520) may predict possible future failures of individual components based on the diagnosis results of the diagnosis unit (503).

[0152] As described above, the fault diagnosis server (500) may include an error code storage unit (502). The error code storage unit (502) arranges and stores the error code information of the elevator collected from the elevator control panel in chronological order, and may be classified into a time series data group and stored every preset reference time interval. The diagnosis unit (503) may analyze the corresponding error code information of each time series data group stored in the error code storage unit (502) to diagnose the cause of the fault of the time series data group.

[0153] At this time, the calculation unit (520) will calculate the faulty component and corresponding error code information of the cause of the fault through the diagnosis result of the diagnosis unit (503) and apply them together with the fault occurrence time information to the machine learning model, so as to predict the faulty components and fault occurrence time points that may fail in the future.

[0154] More specifically, the diagnosis unit (503) can extract the fault component and corresponding error code information corresponding to the fault cause during the fault cause diagnosis process. The calculation unit (520) can collect all the diagnosis results of these diagnosis units (503) from past data to calculate the fault occurrence time interval of each fault component. In addition, the calculation unit (520) can apply the fault occurrence time interval of each fault component and error code information and the fault component to the machine learning model based on this to predict the future fault occurrence time point of each fault component. In addition to using the data based on the diagnosis results of the diagnosis unit (503) as the learning data applied to the machine learning model, the fault prediction process of this calculation unit (520) can be the same as the fault prediction process based on the above-mentioned fault processing result input data.

[0155] That is, the calculation unit (520) can predict the faulty component and the time point of the fault occurrence based on the fault processing result information input through the maintenance terminal (600), or can also predict the faulty component and the time point of the fault occurrence based on the diagnosis result information of the diagnosis unit (503).

[0156] As described above, the calculation unit (520) can predict faults in two ways, and can calculate a fault prediction result by averaging the fault prediction results. That is, the fault prediction result using the fault processing result of the maintenance terminal (600) and the fault prediction result using the diagnosis result of the diagnosis unit (503) can be combined to calculate a fault prediction result for the faulty component that may fail in the future and the time point of the fault occurrence.

[0157] As described above, by predicting the occurrence of future failures based on two types of information, a more accurate failure prediction result can be calculated.

[0158] In particular, the diagnosis unit (503) of the fault diagnosis server (500) reflects the fault processing results input from the maintenance terminal (600) to diagnose the cause of the fault. Therefore, as time goes by, the accuracy of the fault cause diagnosis results of the diagnosis unit (503) will improve. Therefore, the accuracy of the fault prediction results of the calculation unit (520) based on the diagnosis results of the diagnosis unit (503) will also be further improved with the passage of time.

[0159] The above description is only an exemplary description of the technical idea of ​​the present invention. In the technical field to which the present invention belongs, technicians can make various modifications and deformations without departing from the essential characteristics of the present invention. Therefore, the embodiments disclosed in the present invention are not intended to limit the technical idea of ​​the present invention, but to illustrate, and the scope of the technical idea of ​​the present invention is not limited by these embodiments. The protection scope of the present invention should be interpreted according to the above claims, and all technical ideas within the equivalent scope should be interpreted as included in the scope of rights of the present invention.

[0160] (Explanation of Symbols)

[0161] 100: Elevator control panel

[0162] 200: Ministry of Communications

[0163] 310: Modem

[0164] 320: Monitoring panel server

[0165] 400: Central Management Server

[0166] 500: Fault diagnosis server

[0167] 501a: First communication unit

[0168] 501b: Second communication unit

[0169] 502: Error code storage unit

[0170] 503: Diagnosis Department

[0171] 504: Fault cause storage unit

[0172] 505: Failure cause update department

[0173] 510: Processing result storage unit

[0174] 520: Computing Department

[0175] 600: Maintenance terminal

[0176] 601: Terminal Communication Department

[0177] 602: Display unit

[0178] 603: Input

[0179] 604: Control Department

[0180] 610: First output screen

[0181] 611: Error code display area

[0182] 612: Diagnosis result display area

[0183] 613: Diagnosis result request input button

[0184] 690: Processing result input screen

[0185] 691: Basic information input screen

[0186] 692: Select input screen

[0187] 693: Parts selection input screen

[0188] 6931: Large category selection button

[0189] 6932: Fault location selection button

[0190] 6933: Faulty component selection button

[0191] 694: Additional selection input screen

[0192] 6941: Additional selection button for fault cause

[0193] 6942: Additional selection button for fault subject

[0194] 6943: Processing job additional selection button

[0195] 695: Error code selection input screen

[0196] 6951: Error code selection button

Claims

1. A maintenance management system for a passenger transfer device, include: A maintenance terminal is carried by maintenance personnel and is configured to input a fault handling result including faulty components and error code information after the fault handling is completed; as well as The fault diagnosis server collects and stores the fault processing results input from the maintenance terminal, and applies the stored fault processing results together with the fault occurrence time information to the machine learning model to predict the faulty components and fault occurrence time points that may fail in the future. The maintenance terminal receives and displays the fault prediction result from the fault diagnosis server.

2. The maintenance management system for a passenger transfer device according to claim 1, The fault diagnosis server include: A processing result storage unit, which collects the fault processing results and stores them together with the fault occurrence time information; as well as The calculation unit applies the faulty components and error code information of the fault handling results and the fault occurrence time information of each faulty component to the machine learning model to predict the faulty components and fault occurrence time points that may fail in the future.

3. The maintenance management system for a passenger transfer device according to claim 2, The processing result storage unit classifies the fault processing results collected from the maintenance terminal according to the fault components and stores them in order according to the time sequence of the fault occurrence. The calculation unit calculates the failure time interval of each faulty component stored in the processing result storage unit, and applies each faulty component and error code information and the failure time interval of the faulty component to the machine learning model to predict the future failure time point of each faulty component.

4. The maintenance management system for a passenger transfer device according to claim 2, The fault diagnosis server collects and stores error code information of the passenger transfer device from the passenger transfer device control panel, and diagnoses the cause of the fault based on the collected error code information. The maintenance terminal is connected to the fault diagnosis server, and receives and displays the error code information and the diagnosis result of the fault cause stored in the fault diagnosis server.

5. The maintenance management system for a passenger transfer device according to claim 4, The fault diagnosis server also include: The error code storage unit arranges and stores the error code information of the passenger transfer device collected from the passenger transfer device control panel in chronological order, and classifies and stores the error code information into a time series data group at each preset reference time interval; as well as a diagnosis unit, which analyzes the corresponding error code information of each time series data group stored in the error code storage unit to diagnose the cause of the failure of the time series data group, The calculation unit applies the faulty components and corresponding error code information and fault occurrence time information calculated by the diagnosis result of the diagnosis unit to the machine learning model to predict the faulty components and fault occurrence time points that may fail in the future.

6. The maintenance management system for a passenger transfer device according to claim 5, The calculation unit combines the fault prediction result using the fault processing result of the maintenance terminal with the fault prediction result using the diagnosis result of the diagnosis unit, and calculates a fault prediction result for the faulty components that may fail in the future and the time point of the fault occurrence.

7. A control method for a passenger transfer device maintenance management system, as a control method for a passenger transfer device maintenance management system including a maintenance terminal and a fault diagnosis server, The following steps are involved: Inputting the fault handling result including the fault component and error code information into the maintenance terminal; Collecting and storing the fault processing results input to the maintenance terminal through the fault diagnosis server; Applying the fault processing results stored in the fault diagnosis server together with the fault occurrence time information to the machine learning model, and predicting the faulty components and fault occurrence time points that may fail in the future through the fault diagnosis server; as well as The fault prediction result of the fault diagnosis server is received and displayed through the maintenance terminal.

8. The control method of the passenger transfer device maintenance management system according to claim 7, In the step of collecting and storing by the fault diagnosis server, Collecting the fault handling results from the maintenance terminal, classifying the collected fault handling results by fault components, and storing them in order according to the time sequence of the fault occurrence, Steps of predicting by the fault diagnosis server The following steps are involved: Calculating the time interval between the occurrence of failures of various faulty components stored in the fault diagnosis server; as well as The faulty components and error code information stored in the processing result storage unit and the fault occurrence time interval of the faulty components are applied to the machine learning model to predict the future fault occurrence time point of each faulty component.

Images