Maintenance Management System for Elevator Equipment

Abstract

This management system comprises: a storage unit which stores promise execution matter information determined in advance with customers as response items that should be executed when an abnormality occurs in an elevator facility; a reception unit which receives an abnormality signal indicating that an abnormality occurs in the elevator facility; a list generation unit which generates a list obtained by extracting, from the promise execution matter information, items corresponding to the types of abnormality signals; and a display unit for displaying the list generated by the list generation unit.

Description

[Technical field]

[0001] The present disclosure relates to a maintenance management system for an elevator installation. [Background technology]

[0002] Patent Document 1 discloses technology related to a system that records responses to breakdowns that occur in building equipment. When a breakdown occurs in equipment, the system of this technology displays the content of the response that should be taken when the breakdown occurs in the equipment on a breakdown response screen. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Publication No. 2018-182476 Summary of the Invention [Problem to be solved by the invention]

[0004] In the system of Patent Document 1, when a failure occurs in a facility, all the details of the response that should be taken when the failure occurs in the facility are displayed. In this way, when displays that require confirmation and displays that do not require confirmation are displayed together, there is a risk that the operator checking the displays will overlook something.

[0005] The present disclosure has been made to solve the problems described above, and aims to provide technology for a maintenance management system that is advantageous in properly fulfilling the promised implementation items that have been agreed upon in advance with customers as response content items to be implemented in the event of an abnormality in elevator equipment. [Means for solving the problem]

[0006] The elevator equipment maintenance management system disclosed herein includes a memory unit that stores promised implementation item information that is agreed upon in advance with a customer as a response content item to 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 equipment, a list generation unit that generates a list in which items corresponding to the type of abnormality signal are extracted from the promised implementation item information, and a display unit that displays the list generated by the list generation unit. A list correction unit that accepts corrections to the list by an operator, the storage unit stores performance information that indicates the performance of corrections made by the list correction unit, and the list correction unit includes a suggestion unit that proposes corrections to the list to the operator based on the performance information. It is equipped with the following. Effect of the Invention

[0007] According to the maintenance management system of the present disclosure, items corresponding to the type of abnormal signal received can be extracted from the promise implementation information and displayed. This prevents unnecessary items from being displayed, improving usability for operators checking the list. [Brief description of the drawings]

[0008] [Figure 1] FIG. 1 is a diagram illustrating a configuration of a maintenance management system according to an embodiment. [Diagram 2] FIG. 11 is a diagram illustrating an example of building information. [Diagram 3] FIG. 13 is a diagram showing an example of promise implementation information. [Figure 4] FIG. 13 is a diagram illustrating an example of an abnormality signal type master. [Diagram 5] FIG. 13 is a diagram showing an example of a generated TODO list. [Figure 6] FIG. 13 is a diagram showing an example of a TODO list after list editing processing has been executed. [Figure 7] FIG. 13 is a diagram showing an example of a TODO list after list modification processing has been executed. [Figure 8] 13 is a flowchart showing a list creation processing routine executed in the list management device 15. [Figure 9] 13 is a flowchart showing routines of a suggestion process, a list editing process, a notification process, and a list correction process executed in the list management device 15. [Figure 10] FIG. 2 is a diagram illustrating an example of hardware resources of a maintenance management system. [Figure 11] FIG. 13 is a diagram illustrating another example of hardware resources of the maintenance management system. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0009] Hereinafter, an embodiment will be described with reference to the drawings. In addition, elements common to the various drawings are given the same reference numerals, and duplicated explanations will be omitted.

[0010] Embodiment 1. Configuration of elevator equipment maintenance management system Fig. 1 is a diagram showing the configuration of a maintenance management system according to this embodiment. The elevator facility to which the maintenance management system 100 according to this embodiment is applied is an elevator 2. The elevator facility may also include, for example, an escalator, a moving walkway, or facilities other than elevators for which there is a maintenance contract.

[0011] The elevator system 1 is a system including a plurality of elevators 2. Each elevator 2 is applied to, for example, a building having a plurality of floors. A single building may be provided with a plurality of elevators 2. A hoistway 3 for the elevators 2 is provided in the building. The hoistway 3 is a vertically long space spanning a plurality of floors. In this example, each elevator 2 is a traction type elevator. Note that the elevator system 1 may also include, for example, a drum type elevator and a hydraulic type elevator. The traction type elevator includes a hoist 4, a main rope 5, a car 6, a counterweight 7, and a control panel 9.

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

[0013] 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 so as to pull up one side of the sheave of the hoisting machine 4 by the driving force generated by the motor of the hoisting machine 4.

[0014] The car 6 is a device that transports passengers of the elevator 2 between multiple floors by traveling up and down the hoistway 3. The counterweight 7 is a device that balances the load of the car 6 on one side of the sheave of the hoisting machine 4 on the other side of the sheave of the hoisting machine 4. The car 6 and the counterweight 7 travel up and down the hoistway 3 in opposite directions as the main rope 5 is moved by the motor of the hoisting machine 4.

[0015] The control panel 9 is a device that controls the operation of the elevator 2. The operation of the elevator 2 includes, for example, the running of the car 6. The control panel 9 is arranged, for example, at the upper or lower part of the hoistway 3. Alternatively, if a machine room is provided, the control panel 9 may be arranged in the machine room. The control panel 9 is connected to the devices of the elevator 2 so as to be able to obtain information on the state of the elevator 2 used to control the operation of the elevator 2. The control panel 9 obtains information on the state of the elevator 2 from, for example, sensors or switches provided in the car 6, the hoistway 4, or the hoistway 3 of the elevator 2.

[0016] Each elevator 2 is equipped with a remote monitoring device 11. The remote monitoring device 11 is a device that monitors the status of the elevator 2. The remote monitoring device 11 acquires information on the status of the elevator 2, for example, from the control panel 9. For example, when an abnormality occurs in the elevator 2, the remote monitoring device 11 acquires an abnormality signal from the control panel 9. Examples of such abnormalities include being trapped inside, door opening / closing abnormality, etc.

[0017] A maintenance management system 100 is applied to an elevator system 1. The maintenance management system 100 maintains and manages elevators 2 for customers with whom the customer has a maintenance contract. The maintenance contract specifies promised implementation items, which are response content items that should be implemented if an abnormality occurs in the elevator 2. The maintenance management system 100 is a system that manages the display of promised implementation items that an operator refers to if an abnormality occurs in the elevator 2. The maintenance management system 100 includes a central management device 13 and a list management device 15.

[0018] The central management device 13 is a device that remotely monitors each elevator 2. The central management device 13 is disposed in, for example, an information center 16. The information center 16 is a base that collects information on the multiple elevators 2. The central management device 13 is, for example, one or a plurality of server devices. The central management device 13 is connected from each remote monitoring device 11 via a telephone line such as LTE so that the status of each elevator 2 during normal operation can be communicated.

[0019] The list management device 15 is a device that manages the list display of promise implementation items when some abnormality occurs in the elevator 2. The list management device 15 is disposed in, for example, an information center 16. The list management device 15 is, for example, one or a plurality of server devices. The central management device 13 is connected from each remote monitoring device 11 via a telephone line such as LTE so that abnormality signals and the like of each elevator 2 can be communicated. The list management device 15 is connected to the central management device 13 via, for example, a maintenance company's intranet.

[0020] The operators include upper level operators who are highly skilled in elevator equipment, and lower level operators who are less skilled than the upper level operators. The upper level operators are also called supervisors because they are in a position to give advice to the lower level operators on their work. The upper level operators and the lower level operators each have terminal devices 18a and 18b. 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 maintenance company's intranet.

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

[0022] The list management device 15 includes, as functional blocks related to the management of the TODO list, an abnormality signal receiving unit 21, a storage unit 22, a list generating unit 23, a suggesting unit 24, a notifying unit 25, a list correcting unit 26, and a display unit 27. Various functions of the list management device 15 will be described below with specific examples.

[0023] 2. Functions of the list management device 15 2-1.TODO list generation function Among the promise implementation items, there are list items that are unrelated to the abnormality that has just occurred. If such unrelated list items are mixed in the TODO list, the operator may overlook the implementation items. Therefore, the list management device 15 generates a TODO list that extracts only the items related to the abnormality that has just occurred. This process is hereinafter referred to as the "list generation process."

[0024] FIG. 2 is a diagram showing an example of building information. The building information is information for identifying the target elevator equipment, and is composed of, for example, an identification number and a unit number assigned to each building. FIG. 3 is a diagram showing an example of promise implementation information. As shown in this figure, the promise implementation information associates the identification number and unit number of the target building with the classification and corresponding content of the promise implementation item, and the abnormal signal type. The abnormal signal type is a symbol that classifies the abnormal signal, and is specified by the abnormal signal type master. FIG. 4 is a diagram showing an example of the abnormal signal type master. As shown in this figure, the abnormal signal type is associated with the abnormal content such as being trapped in the elevator 2. The memory unit 22 stores the building information, the promise implementation information, and the abnormal signal type master.

[0025] The abnormal signal receiving unit 21 is a part that receives an abnormal signal of the elevator 2 from each remote monitoring device 11. The abnormal signal includes the abnormal content of the elevator 2 and building information that identifies the elevator 2. In the list generation process, the list generating unit 23 refers to the building information and the abnormal signal type master, and identifies the building and the abnormal signal type from the abnormal signal received by the abnormal signal receiving unit 21. Then, the list generating unit 23 generates a TODO list by extracting the items of the identified building and abnormal signal type from the promise implementation information. FIG. 5 is a diagram showing an example of a generated TODO list. In the example shown in this figure, it is a display example of a list generated when an abnormal signal of abnormal signal type A is received from a building with identification number AA-XXX. In the TODO list shown in FIG. 5, the display / hidden items indicate the display / hidden setting status of the list items. The TODO list can extract and display only list items that are set to be displayed. Note that all list items are set to "display" by default. Items marked as "uncompleted" indicate the handling status by the operator. The display unit 27 displays the TODO list on the operator's terminal device 18a, 18b.

[0026] According to the above-described list generation process, a TODO list can be generated by extracting only list items related to the elevator equipment abnormality that has occurred. This reduces the burden on the operator who has to refer to the TODO list.

[0027] 2-2. TODO list editing function In the generated TODO list, there are list items such as matters to be communicated whose necessity cannot be determined by the abnormality signal alone. Therefore, the list generation process based on the abnormality signal alone may include unnecessary list items that are not necessary or sufficient as a response to the current abnormality. Therefore, the display / non-display setting in the TODO list is configured to be editable by the operation of the operator. For example, a lower-level operator operates the terminal device 18b to select a list item to be edited to be hidden from among the list items in the displayed TODO list. The list correction unit 26 receives the input from the terminal device 18b and sets the corresponding list item to be hidden. This process is hereinafter referred to as "list editing process". FIG. 6 is a diagram showing an example of a TODO list after the list editing process is executed. In the example shown in this figure, a case is illustrated in which the top two items of the TODO list are edited to be hidden.

[0028] According to the list editing process described above, it is possible to set to not display any list items in the TODO list that a lower-level operator judges to be unnecessary.

[0029] 2-3.Suggestion function for editing TODO list The editing results from the list editing process are stored in the storage unit 22 as result information. The correction results from the list correction process described below are also stored in the storage unit 22 as result information. The suggestion unit 24 proposes editing of the TODO list to the lower-level operator based on the result information. This process is hereinafter referred to as the "proposal process." In the proposal process, the suggestion unit 24 determines whether a list item that matches a list item in the TODO list has been hidden in the result information after the registration date of the promise implementation item. Then, the suggestion unit 24 proposes to the operator that the list item that has been hidden be edited to be hidden. There is no limitation on the method of proposal. For example, the suggestion unit 24 makes the proposal by displaying a pop-up on the screen of the terminal device 18b, by email, or by voice output.

[0030] According to the above-described suggestion process, unnecessary list items can be identified and suggested from the TODO list based on the performance information.

[0031] 2-4. Notification function for higher-level operators and TODO list modification function The contents of the proposals made by the proposal process are based on performance information including the judgment of higher-ranking operators, so their reliability is ensured. However, it is possible that lower-ranking operators may make decisions that differ from those proposed by the proposal process. It is advisable to have such arbitrary decisions of lower-ranking operators confirmed by higher-ranking operators.

[0032] Therefore, if the lower-level operator takes a different action from that proposed by the proposal process, the notification unit 25 notifies the higher-level operator of the lower-level operator's action. This process will be referred to as the "notification process" below. There is no limitation on the notification method in the notification process. Examples of the notification process include notification by pop-up on the screen of the terminal device 18a of the higher-level operator, notification by e-mail, etc.

[0033] The higher-level operator who receives the notification from the notification process checks the response of the lower-level operator in the TODO list, and inputs a correction of the display / hide of the TODO list from the terminal device 18a as necessary. The list correction unit 26 receives the input from the terminal device 18a and corrects the display / hide of the corresponding list item. This process is hereinafter referred to as "list correction process." FIG. 7 is a diagram showing an example of a TODO list after the list correction process has been executed. The example shown in this figure illustrates a case where one of the list items in the TODO list that was set to hidden by a lower-level operator is corrected to be displayed again. The correction record by the list correction process is stored in the storage unit 22 as record information. The correction record as record information is used in the above-mentioned proposal process.

[0034] According to the notification process and list correction process described above, the higher-level operator can correct the lower-level operator's mistake in judgment in response to the list editing process by the lower-level operator. In addition, the correction results are used as performance information for the next and subsequent proposal processes. This allows the proposal process to reflect the higher-level operator's judgment, so the TODO list can be narrowed down to only the necessary and sufficient list items.

[0035] 2-5. TODO list filtering function using other elements Since the contents of the TODO list are diverse, the TODO list required differs depending on the situation. Therefore, the list generation unit 23 determines the implementation timing of each list item based on the classification and contents of the promise implementation information. Examples of implementation timing include when an abnormality signal is received, when a responder is decided, and when the response is completed. The list generation unit 23 extracts list items that correspond to the current timing into the TODO list. This process is hereinafter referred to as "list narrowing down process." The list narrowing down process allows the operator to refer to a TODO list appropriate to the situation, thereby increasing convenience.

[0036] 3. Specific processing executed by the list management device 15 Fig. 8 is a flowchart showing a routine of a list generation process executed in the list management device 15. In step S100 of the routine shown in Fig. 8, it is determined whether or not the abnormal signal receiving unit 21 has received an abnormal signal. If the determination is not established, the routine is terminated, and if the determination is established, the process proceeds to step S102.

[0037] In step S102, the list generating unit 23 extracts a list item of the identification number of the target building from the promise implementation item information as a display candidate of the TODO list based on the building information included in the abnormal signal. In step S104, display candidates common to the abnormal signal type included in the abnormal signal are extracted.

[0038] In step S106, the contents to be displayed at the current timing are further extracted from the display candidates based on the classification and contents of the list items. In step S108, the TODO list is displayed on the terminal device 18b of the subordinate operator.

[0039] FIG. 9 is a flowchart showing routines of a proposal process, a list editing process, a notification process, and a list correction process executed in the list management device 15. The routine shown in FIG. 9 is executed while the TODO list is displayed on the terminal device 18b of the lower-level operator in the routine shown in FIG. 8. In step S120 of the routine shown in FIG. 9, the proposal unit 24 notifies the lower-level operator of a proposal to edit the TODO list by executing the proposal process. In step S122, it is determined whether the lower-level operator has responded differently from the content proposed in the proposal process. Here, it is determined whether the list correction unit 26 has executed a list correction process different from the content proposed in the proposal process. As a result, if the determination is not found to be true, the process proceeds to step S128, and if the determination is found to be true, the process proceeds to step S124.

[0040] In step S124, the notification unit 25 notifies the terminal device 18a of the higher-level operator of the response of the lower-level operator. In step S126, when the list modification unit 26 receives an input from the terminal device 18a of the higher-level operator, the list modification unit 26 executes a list modification process to modify the TODO list.

[0041] In step S128, the display unit 27 displays the TODO list on the terminal device 18b of the subordinate operator. In step 130, 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.

[0042] 4. Variations The maintenance management system 100 of this embodiment may be modified as follows.

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

[0044] 10 is a diagram showing an example of hardware resources of the maintenance management system 100. The list management device 15 of the maintenance management system 100 includes, as hardware resources, a processing circuit 34 including a processor 30 and a memory 32. The processing circuit 34 may include multiple processors 30. The processing circuit 34 may include multiple memories 32.

[0045] In this embodiment, each unit indicated by reference numerals 21 to 27 indicates a function possessed by the list management device 15. The function of the storage unit 22 is realized by a memory 32. The function of each unit indicated by reference numerals 21 to 27 can be realized by software written as a program, firmware, or a combination of software and firmware. The program is stored in the memory 32. The list management device 15 realizes the function of each unit indicated by reference numerals 21 to 27 by executing the program stored in the memory 32 by a processor 30 (computer).

[0046] The processor 30 is also called a CPU (Central Processing Unit), central processing unit, processing unit, arithmetic unit, microprocessor, microcomputer, or DSP. The memory 32 may be a semiconductor memory, a magnetic disk, a flexible disk, an optical disk, a compact disk, a mini disk, or a DVD. Possible semiconductor memories include RAM, ROM, flash memory, EPROM, and EEPROM.

[0047] Fig. 11 is a diagram showing another example of hardware resources of the maintenance management system 100. In the example shown in Fig. 11, the list management device 15 includes a processor 30, a memory 32, and a processing circuit 34 including dedicated hardware 36. Fig. 11 shows an example in which some of the functions of the list management device 15 are realized by the dedicated hardware 36. All of the functions of the list management device 15 may be realized by the dedicated hardware 36. As the dedicated hardware 36, a single circuit, a composite circuit, a programmed processor, a parallel programmed processor, an ASIC, an FPGA, or a combination of these can be adopted.

[0048] The list narrowing down process, the proposal process, the list editing process, the notification process, and the list correction process are not essential processes for the maintenance management system 100.

[0049] In step S108, the message may be displayed not only on the terminal device 18a of the lower-level operator, but also on the terminal device 18a of the higher-level operator. [Explanation of symbols]

[0050] 1 elevator system, 2 elevator, 3 hoistway, 4 hoist, 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 reception unit, 22 memory unit, 23 list generation unit, 24 proposal 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 storage unit that stores information on agreed-upon implementation items pre-determined with a customer as content items to be implemented when an abnormality occurs in elevator equipment; a reception unit that receives an abnormality signal indicating that an abnormality has occurred in the elevator equipment; a list generation unit that generates a list by extracting items corresponding to the type of the abnormality signal received by the reception unit from among the agreed-upon implementation item information; a display unit that displays the list generated by the list generation unit; a list modification unit that receives modification of the list by an operator; comprising the storage unit stores performance information representing the performance of modification in the list modification unit; the list modification unit A maintenance management system for elevator equipment, comprising a proposal unit that proposes modification of the list to the operator based on the performance information.

2. the agreed-upon implementation item information is information in which the type of the abnormality signal is associated with the content item to be implemented; the list generation unit extracts the content item associated with the type of the abnormality signal received by the reception unit The maintenance management system for elevator equipment according to claim 1, configured as such.

3. the operator includes a senior operator with high proficiency and a junior operator with lower proficiency than the senior operator; the list modification unit when receiving a modification of content different from that proposed by the proposal unit from the junior operator, includes a notification unit that notifies the senior operator The maintenance management system for elevator equipment according to claim 1 or claim 2.

Images