Maintenance management system of elevator equipment

Abstract

The management system is provided with: a storage unit that stores agreed implementation item information that is agreed in advance with a customer as a response content item that should be implemented when an abnormality occurs in the elevator equipment; a reception unit that receives an abnormality signal indicating that an abnormality has occurred in the elevator device; a list generation unit that generates a list in which items corresponding to the type of the abnormal signal are extracted from the agreed implementation item information; and a display unit that displays the list generated by the list generation unit.

Description

Technical Field

[0001] The present disclosure relates to a maintenance management system for elevator equipment. Background Art

[0002] Patent Document 1 discloses a technique related to a system for recording responses to failures occurring in equipment in a building. When a failure occurs in an equipment, the system of this technique displays the content of responses that should be taken when the equipment fails on a failure response screen.

[0003] Prior art literature

[0004] Patent Literature

[0005] Patent Document 1: Japanese Patent Application Publication No. 2018-182476 Summary of the invention

[0006] Problems to be solved by the invention

[0007] In the system of Patent Document 1, when a device fails, all the contents of the response that should be taken when the device fails are displayed. In this way, when the display that requires confirmation and the display that does not require confirmation are mixed, the operator who confirms the display may be tempted to neglect.

[0008] The present disclosure is completed to solve the above-mentioned problems, and its purpose is to provide a maintenance management system technology that is conducive to properly fulfilling the agreed implementation matters agreed in advance with the customer as the response content items that should be implemented when an abnormality occurs in the elevator equipment.

[0009] Means for solving problems

[0010] The maintenance management system for elevator equipment disclosed in the present invention comprises: a storage unit, which stores information on agreed implementation matters agreed in advance with a customer as response content items that should be implemented when an abnormality occurs in the elevator equipment; an acceptance unit, which accepts an abnormality signal indicating that an abnormality has occurred in the elevator equipment; a list generation unit, which generates a list by extracting items corresponding to the category of the abnormality signal from the agreed implementation matter information; and a display unit, which displays the list generated by the list generation unit.

[0011] Effects of the Invention

[0012] According to the maintenance management system of the present disclosure, it is possible to extract and display items corresponding to the type of the received abnormal signal from the scheduled implementation matter information, thereby avoiding display of unnecessary items, thereby improving usability for an operator checking the list. BRIEF DESCRIPTION OF THE DRAWINGS

[0013] Figure 1It is a diagram showing the configuration of a maintenance management system according to an embodiment.

[0014] Figure 2 This is a diagram showing an example of building information.

[0015] Figure 3 This is a diagram showing an example of agreed implementation matter information.

[0016] Figure 4 This is a diagram showing an example of an abnormal signal category master table.

[0017] Figure 5 This is a diagram showing an example of a generated TODO list.

[0018] Figure 6 This is a diagram showing an example of a TODO list on which list editing processing has been executed.

[0019] Figure 7 This is a diagram showing an example of a TODO list on which list correction processing has been executed.

[0020] Figure 8 1 is a flowchart showing a routine of a list generation process executed in the list management device 15 .

[0021] Fig. 9 1 is a flowchart showing a routine of suggestion processing, list editing processing, notification processing, and list correction processing executed in the list management device 15 .

[0022] Fig.10 This is a diagram showing an example of hardware resources of a maintenance management system.

[0023] Fig.11 This is a diagram showing another example of hardware resources of the maintenance management system. DETAILED DESCRIPTION

[0024] Hereinafter, the embodiment will be described with reference to the drawings. In addition, the same reference numerals are given to the same elements in each figure, and repeated descriptions are omitted.

[0025] Implementation

[0026] 1. Structure of the maintenance management system for lift equipment

[0027] Figure 1 1 is a diagram showing the structure of the maintenance management system of this embodiment. The elevator facility to which the maintenance management system 100 of this embodiment is applied is the elevator 2. The elevator facility may include, for example, escalators, moving walkways, or facilities other than elevators for which a maintenance contract has been signed.

[0028] The elevator system 1 is a system including a plurality of elevators 2. Each elevator 2 is applied to a building having a plurality of floors, for example. A plurality of elevators 2 may be installed in one building. A shaft 3 for the elevators 2 is installed in the building. The shaft 3 is a long space in the vertical direction that extends over a plurality of floors. In this example, each elevator 2 is a traction elevator. In addition, the elevator system 1 may include a drum elevator, a hydraulic elevator, and the like, for example. The traction elevator has a traction machine 4, a main rope 5, a car 6, a counterweight 7, and a control panel 9.

[0029] The traction machine 4 has a motor that generates a driving force and a sheave that rotates by the driving force generated by the motor. The traction machine 4 is, for example, arranged at the upper part or the lower part of the hoistway 3. Alternatively, when a machine room is provided in the elevator 2, for example, above the hoistway 3, the traction machine 4 may also be arranged in the machine room.

[0030] The main rope 5 is a rope that supports the load of the car 6 and the counterweight 7 in the hoistway 3. The main rope 5 is wound around the sheave of the hoisting machine 4. The main rope 5 supports the load of the car 6 on one side of the sheave of the hoisting machine 4. The main rope 5 supports the load of the counterweight 7 on the other side of the sheave of the hoisting machine 4. The main rope 5 moves in a manner that pulls up one side of the sheave of the hoisting machine 4 by the driving force generated by the motor of the hoisting machine 4.

[0031] The car 6 is a device that transports passengers of the elevator 2 between multiple floors by running in the vertical direction in the hoistway 3. The counterweight 7 is a device that balances the load of the car 6 applied to one side of the sheave of the traction machine 4 on the other side of the sheave of the traction machine 4. As the main rope 5 is moved by the motor of the traction machine 4, the car 6 and the counterweight 7 run in the hoistway 3 in the vertical direction to the opposite sides.

[0032] The control panel 9 is a device for controlling the operation of the elevator 2. The operation of the elevator 2 includes, for example, the travel of the car 6. The control panel 9 is, for example, arranged at the upper part or the lower part of the shaft 3. Alternatively, when a machine room is provided, the control panel 9 may also be arranged in the machine room. The control panel 9 is connected to the equipment of the elevator 2 so as to obtain the state information of the elevator 2 for controlling the operation of the elevator 2. The control panel 9 obtains the state information of the elevator 2 from, for example, sensors or switches provided in the car 6, the traction machine 4 or the shaft 3 of the elevator 2.

[0033] Each elevator 2 has a remote monitoring device 11. The remote monitoring device 11 is a device that monitors the state of the elevator 2. The remote monitoring device 11 obtains the state information of the elevator 2 from, for example, the control panel 9. For example, when an abnormality occurs in the elevator 2, the remote monitoring device 11 obtains an abnormality signal from the control panel 9. Examples of such abnormalities include being trapped and abnormal door opening and closing.

[0034] A maintenance management system 100 is applied to an elevator system 1. The maintenance management system 100 performs maintenance management on an elevator 2 of a customer who has signed a maintenance contract. In the maintenance contract, agreed implementation items are agreed upon as the response content items to be implemented when an abnormality occurs in the elevator 2. The maintenance management system 100 is a system that manages the display of the agreed implementation items for reference by the operator when an abnormality occurs in the elevator 2. The maintenance management system 100 includes a central management device 13 and a list management device 15.

[0035] The central management device 13 is a device for remotely monitoring each elevator 2. The central management device 13 is, for example, arranged in an information center 16 or the like. The information center 16 is a base for collecting information of a plurality of elevators 2. The central management device 13 is, for example, one or more server devices or the like. The central management device 13 is connected to each remote monitoring device 11 through a telephone line such as LTE, for example, so as to be able to communicate the status of each elevator 2 during normal operation, etc.

[0036] The list management device 15 is a device that manages the list display of the agreed implementation items when some abnormality occurs in the elevator 2. The list management device 15 is configured in the information center 16, etc., for example. The list management device 15 is, for example, one or more server devices, etc. The central management device 13 is connected to each remote monitoring device 11 through a telephone line such as LTE, so that abnormal signals of each elevator 2 can be communicated. The list management device 15 is connected to the central management device 13 through the internal network of the maintenance company, etc.

[0037] The operators include senior operators who are highly skilled in the lift equipment and junior operators who are less skilled than the senior operators. The senior operators are in a position to assist the junior operators in their work, and therefore are also called supervisors. The senior operators and the junior operators have terminal devices 18a and 18b, respectively. The terminal devices 18a and 18b have an input function for inputting information and a display function for displaying information. The terminal devices 18a and 18b are connected to the list management device 15, for example, via the intranet of the maintenance company.

[0038] As described above, in the maintenance contract with the customer, the agreed implementation items for each building are agreed upon. When an abnormality occurs in the customer's elevator 2, the operator is required to comply with these agreed implementation items. Therefore, the list management device 15 generates a list of agreed implementation items corresponding to the building where the abnormality occurs, and displays it on the operator's terminal device 18a, 18b. This list is hereinafter referred to as a "TODO list".

[0039] As functional blocks related to the management of the TODO list, the list management device 15 includes an abnormal signal receiving unit 21, a storage unit 22, a list generating unit 23, a suggestion unit 24, a notification unit 25, a list correction unit 26, and a display unit 27. The various functions of the list management device 15 will be described below with reference to specific examples.

[0040] 2. Functions of the list management device 15

[0041] 2-1.TODO list generation function

[0042] There are also list items in the agreed implementation items that are not related to the abnormality that occurred this time. When such irrelevant list items are mixed in the TODO list, the operator may ignore the implementation items. Therefore, the list management device 15 generates a TODO list that only extracts items related to the abnormality that occurred. This process is hereinafter referred to as "list generation processing".

[0043] Figure 2 2 is a diagram showing an example of building information. The building information is information for specifying a target elevator facility, and is composed of, for example, an identification number and a machine number assigned to each building. Figure 3 This is a diagram showing an example of agreed implementation information. As shown in the diagram, the agreed implementation information matches the identification number, machine number, and abnormal signal category of the building to be the target with the classification and response content of the agreed implementation. The abnormal signal category is a symbol for classifying abnormal signals, and is specified in the abnormal signal category master table. Figure 4 2 is a diagram showing an example of an abnormal signal category master table. As shown in the figure, the abnormal signal category master table associates abnormal signal categories with abnormal contents such as being trapped in the elevator 2. The storage unit 22 stores building information, agreed implementation information, and the abnormal signal category master table.

[0044] The abnormal signal receiving unit 21 is a part that receives abnormal signals of the elevator 2 from each remote monitoring device 11. The abnormal signal includes the abnormal content of the elevator 2 and the building information that specifies the elevator 2. In the list generation process, the list generation unit 23 refers to the building information and abnormal signal category master table to specify the building and abnormal signal category based on the abnormal signal received by the abnormal signal receiving unit 21. Then, the list generation unit 23 generates a TODO list by extracting the items of the specified building and abnormal signal category from the agreed implementation matter information. Figure 5 : is a diagram showing an example of a generated TODO list. The example shown in this figure is a display example of a list generated when an abnormal signal of abnormal signal category A is received from a building with identification number AA-XXX. Figure 5In the TODO list shown, the displayed / non-displayed items indicate the display / non-display setting status of the list items. The TODO list can extract and display only the list items that are set to be displayed. In addition, all list items are set to "display" by default. The undisplayed / completed items are the operator's response status. The display unit 27 causes the operator's terminal device 18a, 18b to display the TODO list.

[0045] According to the above list generation process, it is possible to generate a TODO list by extracting only the list items related to the abnormality of the elevator facility that has occurred. This can reduce the burden on the operator who refers to the TODO list.

[0046] 2-2. Editing function of TODO list

[0047] In the generated TODO list, there are also list items such as communication matters that cannot be judged as necessary only by abnormal signals. Therefore, the list generation process based only on abnormal signals sometimes also includes unnecessary list items that are not sufficient to deal with the current abnormality. Therefore, the display / non-display setting in the TODO list is configured to be editable through the operator's operation. For example, a low-level operator operates the terminal device 18b to select a list item to be edited to be non-displayed from the list items in the displayed TODO list. The list correction unit 26 receives input from the terminal device 18b and sets the corresponding list item to be non-displayed. This process is referred to as "list editing process" below. Figure 6 2 is a diagram showing an example of a TODO list on which a list editing process has been executed. In the example shown in this diagram, a case is illustrated where the top two items of the list items of the TODO list are edited so as not to be displayed.

[0048] According to the above-described list editing process, among the list items of the TODO list, the list items that the low-level operator determines to be unnecessary can be set not to be displayed.

[0049] 2-3. Suggestion function for editing TODO list

[0050] The editing performance of the list editing process is stored in the storage unit 22 as performance information. In addition, the correction performance of the list correction process described later is also stored in the storage unit 22 as performance information. The suggestion unit 24 suggests that the low-level operator edit the TODO list based on the performance information. This process is referred to as the "suggestion process" below. In the suggestion process, the suggestion unit 24 determines whether the list item consistent with the list item of the TODO list has a performance that becomes non-displayed in the performance information after the registration date of the agreed implementation matter. Then, the suggestion unit 24 suggests that the operator edit the list item so that it is not displayed for the list item that has the performance that becomes non-displayed. There is no limitation on the method of suggestion. For example, the suggestion unit 24 makes a suggestion through a pop-up display on the screen of the terminal device 18b, an email, or a voice output.

[0051] According to the above suggestion processing, it is possible to identify unnecessary list items from the TODO list based on the performance information and to suggest them.

[0052] 2-4. Notification function for senior operators and modification function for TODO list

[0053] The content of the suggestion suggested by the suggestion process is based on the performance information including the judgment of the senior operator, so the reliability is ensured. However, it is also possible that the junior operator may make a judgment different from the suggestion of the suggestion process. It is best to ask the senior operator for confirmation of such arbitrary judgment of the junior operator.

[0054] Therefore, when the low-level operator takes a different response from the suggestion of the suggestion process, the notification unit 25 notifies the high-level operator of the response of the low-level operator. This process is hereinafter referred to as "notification process". There is no limitation on the notification method in the notification process. The notification process can be exemplified by, for example, a pop-up notification on the screen of the terminal device 18a of the high-level operator, a notification by e-mail, etc.

[0055] The high-level operator who has received the notification based on the notification process confirms the response of the low-level operator in the TODO list, and inputs the correction of display / non-display of the TODO list from the terminal device 18a as needed. The list correction unit 26 receives the input from the terminal device 18a and corrects the display / non-display of the corresponding list item. This process is hereinafter referred to as "list correction process". Figure 7 1 is a diagram showing an example of a TODO list on which list correction processing has been performed. In the example shown in the figure, a case is illustrated where one of the list items in the TODO list that was set not to be displayed by a low-level operator is corrected to be displayed again. The correction results of the list correction processing are stored in the storage unit 22 as performance information. The correction results as performance information are used for the above-mentioned suggestion processing.

[0056] According to the above notification process and list correction process, the senior operator can correct the judgment error of the junior operator in response to the list editing process performed by the junior operator. In addition, the correction results are used as performance information for the next suggestion process. As a result, in the suggestion process, suggestions reflecting the judgment content of the senior operator can be made, so that the TODO list can be narrowed down to necessary and sufficient list items.

[0057] 2-5. Narrowing the TODO list using other elements

[0058] Since the content of the TODO list involves many aspects, the required TODO list varies depending on the scene. Therefore, the list generation unit 23 determines the implementation time of each list item based on the classification and content of the agreed implementation matter information. The implementation time can be exemplified by the time when the abnormal signal is received, when the respondent decides, when the response is completed, etc. The list generation unit 23 extracts the list items corresponding to the current time into the TODO list. This process is referred to as "list reduction processing" below. According to the list reduction processing, the operator can refer to the TODO list corresponding to the scene, which increases convenience.

[0059] 3. Specific processing performed in the list management device 15

[0060] Figure 8 1 is a flowchart showing a routine of list generation processing executed in the list management device 15. Figure 8 In step S100 of the routine shown, the abnormal signal receiving unit 21 determines whether an abnormal signal has been received. If the result is that the non-approval determination is established, this routine ends, and if the approval determination is established, the process proceeds to step S102.

[0061] In step S102, the list generator 23 extracts the list items of the identification numbers of the target buildings from the scheduled implementation information as display candidates of the TODO list based on the building information included in the abnormal signal. In step S104, display candidates of the same abnormal signal type as that included in the abnormal signal are extracted.

[0062] In step S106, the content to be displayed at the current time is further extracted from the display candidates based on the classification and content of the list items. In step S108, the TODO list is displayed on the terminal device 18b of the low-level operator.

[0063] Fig. 9 1 is a flowchart showing a routine of suggestion processing, list editing processing, notification processing, and list correction processing executed in the list management device 15. Figure 8 In the routine shown, the TODO list is displayed on the terminal device 18b of the low-level operator during execution. Fig. 9 The routine shown. Fig. 9 In step S120 of the routine shown, the suggestion unit 24 notifies the low-level operator of the TODO list editing suggestion by executing the suggestion process. In step S122, it is determined whether the low-level operator has taken a different response from the content suggested in the suggestion process. Here, it is determined whether the list correction unit 26 has executed a list correction process different from the content suggested in the suggestion process. If the result is that the determination is not approved, the process proceeds to step S128, and if the determination is approved, the process proceeds to step S124.

[0064] In step S124, the notification unit 25 notifies the terminal device 18a of the high-level operator of the response of the low-level operator. In step S126, upon receiving an input from the terminal device 18a of the high-level operator, the list correction unit 26 executes a list correction process for correcting the TODO list.

[0065] In step S128, the display unit 27 displays the TODO list on the terminal device 18b of the low-level operator. In step S130, the correction result of the list correction process and the editing result of the list editing process are stored in the storage unit 22 as performance information.

[0066] 4. Modifications

[0067] The maintenance management system 100 of the present embodiment may also be applied in the following modified forms.

[0068] 4-1. Hardware resources of maintenance management system 100

[0069] Fig.10 1 is a diagram showing an example of hardware resources of the maintenance management system 100. As hardware resources, the list management device 15 of the maintenance management system 100 has a processing circuit 34 including a processor 30 and a memory 32. The processing circuit 34 may include a plurality of processors 30. The processing circuit 34 may also include a plurality of memories 32.

[0070] In this embodiment, the components indicated by reference numerals 21 to 27 represent functions of the list management device 15. The functions of the storage unit 22 are implemented by the memory 32. The functions of the components indicated by reference numerals 21 to 27 can be implemented by software, firmware, or a combination of software and firmware described as a program. The program is stored in the memory 32. The list management device 15 implements the functions of the components indicated by reference numerals 21 to 27 by executing the program stored in the memory 32 by the processor 30 (computer).

[0071] The processor 30 is also called a CPU (Central Processing Unit), a central processing device, a processing device, an arithmetic device, a microprocessor, a microcomputer or a DSP. As the memory 32, a semiconductor memory, a magnetic disk, a floppy disk, an optical disk, a high-density disk, a mini disk or a DVD may also be used. The semiconductor memory that can be used includes a RAM, a ROM, a flash memory, an EPROM and an EEPROM.

[0072] Fig.11 FIG. 1 is a diagram showing another example of hardware resources of the maintenance management system 100. Fig.11 In the example shown, the list management device 15 has a processing circuit 34 including a processor 30 , a memory 32 and dedicated hardware 36 . Fig.11 This is an example in which a part of the functions of the list management device 15 is implemented by the dedicated hardware 36. All the functions of the list management device 15 may be implemented by the dedicated hardware 36. As the dedicated hardware 36, a single circuit, a complex circuit, a programmed processor, a parallel programmed processor, an ASIC, an FPGA, or a combination thereof can be used.

[0073] The list narrowing process, the suggestion process, the list editing process, the notification process, and the list correction process are not essential processes in the maintenance management system 100 .

[0074] In step S108 , the information is not limited to the terminal device 18 a of the low-level operator, but may be displayed on the terminal device 18 a of the high-level operator.

[0075] Description of symbols

[0076] 1: elevator system; 2: elevator; 3: hoistway; 4: traction machine; 5: main rope; 7: counterweight; 9: control panel; 11: remote monitoring device; 13: central management device; 15: list management device; 16: information center; 18a; 18b: terminal device; 21: abnormal signal receiving unit; 22: storage unit; 23: list generating unit; 24: suggestion unit; 25: notification unit; 26: list correction unit; 27: display unit; 30: processor; 32: memory; 34: processing circuit; 36: dedicated hardware; 100: maintenance management system.

Claims

1. A maintenance management system for elevator equipment, wherein: The maintenance management system of the elevator equipment has: A storage unit storing information on agreed implementation items agreed in advance with a customer as response content items to be implemented when an abnormality occurs in the elevator equipment; a receiving unit configured to receive an abnormality signal indicating that an abnormality has occurred in the elevator equipment; a list generating unit configured to generate a list by extracting items corresponding to the types of the abnormal signals received by the receiving unit from the agreed implementation item information; as well as A display unit displays the list generated by the list generating unit.

2. The maintenance management system for elevator equipment according to claim 1, wherein: The agreed implementation information is information that associates the type of abnormal signal with the response content item that should be implemented. The list generating unit is configured to extract a countermeasure content item associated with a type of the abnormal signal received by the receiving unit.

3. The maintenance management system for elevator equipment according to claim 1 or 2, wherein: The maintenance management system for the elevator equipment further includes a list correction unit that accepts correction of the list by an operator.

4. The maintenance management system for elevator equipment according to claim 3, wherein: The storage unit stores performance information indicating the correction performance of the list correction unit. The list correction unit includes a suggestion unit that suggests correction of the list to the operator based on the performance information.

5. The maintenance management system for elevator equipment according to claim 4, wherein: The operators include senior operators with high proficiency and junior operators with lower proficiency than the senior operators. The list correction unit includes a notification unit configured to notify the high-level operator when a correction different from the content suggested by the suggestion unit is received from the low-level operator.

Images