Management device, management method, and control program

Abstract

To improve the efficiency of updating work when updating program files of control programs for a plurality of elevators. [Solution] The management device (50A) includes an update unit (62) that updates the program file of a leading update elevator (10A) that updates its program file first among multiple elevators (10), a detection unit (64) that detects the occurrence of an abnormality in the confirmation operation of the leading update elevator (10A), a determination unit (65A) that, when the detection unit (64) detects an abnormality in the confirmation operation, determines whether or not it is appropriate to update the program file of the scheduled update elevator whose program file is scheduled to be updated thereafter, and a schedule deletion unit (66) that deletes the update schedule for the scheduled update elevator whose program file update is determined to be inappropriate.

Description

[Technical Field]

[0001] The present disclosure relates to a management device that manages updates to program files of control programs for multiple elevators. [Background technology]

[0002] There is known a technology for remotely updating an elevator control program, as disclosed in Patent Document 1. In the technology disclosed in Patent Document 1, if an abnormality occurs when updating the elevator control program, the elevator is started using the data before the update. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] Japanese Patent Application Laid-Open No. 2009-155092 Summary of the Invention [Problem to be solved by the invention]

[0004] However, when remotely updating the control programs of multiple elevators, if the same program that has caused an abnormality is applied to other elevators, there is a risk that the other elevators will also experience abnormalities. On the other hand, stopping the program updates for all elevators scheduled for update will reduce the efficiency of the update.

[0005] One aspect of the present disclosure aims to realize a management device or the like that can improve the efficiency of update work when updating program files of control programs for multiple elevators. [Means for solving the problem]

[0006] In order to solve the above problems, the management device according to aspect 1 of the present disclosure is a management device that manages updates of program files of control programs of a plurality of elevators, and includes: an update unit that updates the program file of a leading update elevator, among the plurality of elevators, which will have its program file updated first, from a pre-update program file to an updated program file; a detection unit that detects the occurrence of an abnormality during confirmation operation of the leading update elevator, whose program file has been updated to the updated program file; a judgment unit that, when the detection unit detects an abnormality during the confirmation operation, judges whether or not it is appropriate to update the program file of an update-scheduled elevator whose program file is scheduled to be updated thereafter; and a schedule deletion unit that deletes the update schedule of the program file of an update-scheduled elevator for which the judgment unit has judged that updating the program file is inappropriate.

[0007] According to the above configuration, if an abnormality occurs during the confirmation operation of the preceding elevator to be updated, the update schedule of only those elevators for which it is determined that updating of the program files is inappropriate among the elevators scheduled for update thereafter is deleted, thereby improving the efficiency of the update work when updating the program files of the control programs of multiple elevators.

[0008] The management device according to aspect 2 of the present disclosure may be configured such that, in aspect 1, the judgment unit judges that updating the program file of the elevator scheduled to be updated, which is scheduled to be updated to the same program file as the updated program file of the preceding update elevator, is inappropriate.

[0009] According to the above configuration, it is possible to limit the elevators for which updating is to be stopped to elevators scheduled for updating that are scheduled to be updated to the same program file as the updated program file of the preceding updated elevator.

[0010] The management device according to aspect 3 of the present disclosure may be configured such that, in aspect 1, the judgment unit judges that updating the program file of the elevator to be updated is inappropriate when at least a portion of a first difference, which is the difference in source code between the pre-update program file and the updated program file in the preceding update elevator, overlaps with at least a portion of a second difference, which is the difference in source code between the pre-update program file and the updated program file in the elevator to be updated.

[0011] According to the above configuration, the elevators for which updating will be stopped can be limited to elevators scheduled for updating that are considered to have a high probability of experiencing an abnormality similar to that of the previously updated elevator, and for which at least a portion of the first difference is included in at least a portion of the second difference.

[0012] The management device according to aspect 4 of the present disclosure may be configured in any of aspects 1 to 3 to further include an update schedule creation unit that sets at least one of the elevators scheduled to have the program file updated as the advance update elevator and creates an update schedule for the program files of the elevators.

[0013] According to the above configuration, an update schedule including the setting of the elevator to be updated first can be automatically created, thereby further improving the efficiency of the update work when updating the program files of multiple elevators.

[0014] In order to solve the above problems, a management method according to aspect 5 of the present disclosure is a management method for managing updates of program files of control programs of a plurality of elevators, and includes: an update step of updating the program file of a leading update elevator, of the plurality of elevators, whose program file is to be updated first, from a pre-update program file to an updated program file; a detection step of detecting the occurrence of an abnormality in confirmation operation of the leading update elevator, whose program file has been updated to the updated program file, if an abnormality is detected in the detection step, a determination step of determining whether or not it is appropriate to update the program file of an update-scheduled elevator, whose program file is scheduled to be updated thereafter; and a schedule deletion step of deleting the update schedule for the program file of the update-scheduled elevator, for which it is determined in the determination step that updating the program file is inappropriate.

[0015] According to the above configuration, if an abnormality occurs during the confirmation operation of the elevator that is being updated first, the update schedule of only those elevators that are scheduled to be updated subsequently and for which it is determined that updating the program files is inappropriate is deleted. This makes it possible to improve the efficiency of the update work when updating the program files of the control programs of multiple elevators.

[0016] The control program according to aspect 6 of the present disclosure is a program for causing a computer to function as a management device according to any one of aspects 1 to 4, and is a control program for causing a computer to function as the update unit, the detection unit, the determination unit, and the schedule deletion unit.

[0017] The management device according to each aspect of the present invention may be realized by a computer, in which case the control program that realizes the management device or the information terminal on a computer by causing the computer to operate as each part (software element) of the management device or the information terminal, and the computer-readable recording medium on which it is recorded, also fall within the scope of the present invention. [Effects of the Invention]

[0018] According to one aspect of the present disclosure, it is possible to improve the efficiency of update work when updating program files of control programs for multiple elevators. [Brief explanation of the drawings]

[0019] [Figure 1] 1 is a block diagram showing a configuration of a main part of an elevator management system according to a first embodiment of the present disclosure. [Figure 2] 10 is a flowchart illustrating an example of a process of a management method performed by the management device. [Figure 3] FIG. 10 is a block diagram showing the configuration of a main part of an elevator management system according to a second embodiment of the present disclosure. [Figure 4] 10 is a flowchart illustrating an example of a process of a management method performed by the management device. DETAILED DESCRIPTION OF THE INVENTION

[0020] [Embodiment 1] An embodiment of the present invention will be described in detail below. FIG. 1 is a block diagram showing the configuration of a main part of an elevator management system 100A according to this embodiment. As shown in FIG. 1, the elevator management system 100A includes a plurality of elevators 10 and a management device 50A. The plurality of elevators 10 are remotely managed by the management device 50A, and updates to program files of control programs that control the elevators 10 are managed remotely by the management device 50A. The plurality of elevators 10 may be provided in a single building, or may be provided in multiple buildings located at different locations. Furthermore, the plurality of elevators 10 may be provided in one or more buildings, respectively. The elevators 10 and the management device 50A will be described in detail below.

[0021] <Elevator 10> The elevator 10 includes a car 11, a camera 12, a human presence sensor 13, a load sensor 14, a door open / closed state detection switch 15, a memory unit 16, a communication unit 17, and a control unit 20.

[0022] The camera 12 is attached to the car 11. The camera 12 captures an image of the inside of the car 11 and outputs the captured image to the control unit 20.

[0023] The human presence sensor 13 is attached to the car 11. The human presence sensor 13 is a sensor that detects the presence or absence of a passenger inside the car 11. The human presence sensor 13 outputs the detection result to the control unit 20.

[0024] The load sensor 14 is attached to the car 11. The load sensor 14 detects the load on the floor surface of the car 11. The load sensor 14 outputs the detection result to the control unit 20.

[0025] The door open / closed state detection switch 15 detects the open / closed state of the door of the car 11. The door open / closed state detection switch 15 outputs the detection result to the control unit 20.

[0026] The storage unit 16 stores various data used by the elevator 10. The storage unit 16 stores a program file 30 that programs the operation of the elevator 10.

[0027] The communication unit 17 communicates with the management device 50A via a network such as the Internet.

[0028] The control unit 20 controls each unit of the elevator 10. The control unit 20 includes an operation control unit 21, a passenger detection unit 22, a door open / close state detection unit 23, a program file update unit 24, and an abnormality detection unit 25.

[0029] The operation control unit 21 reads out the program file 30 stored in the storage unit 16 and controls the operation of each part of the elevator 10 based on the program file 30.

[0030] The passenger detection unit 22 detects the presence or absence of a passenger inside the car 11 based on the detection results from the camera 12, the human presence sensor 13, and / or the load sensor 14. Note that the passenger detection unit 22 does not need to use all of the detection results from the camera 12, the human presence sensor 13, and the load sensor 14, and may detect the presence or absence of a passenger inside the car 11 using the detection result from any one of the camera 12, the human presence sensor 13, and the load sensor 14.

[0031] The door open / closed state detection unit 23 detects whether the door of the car 11 is in an open state or a closed state based on the detection result by the door open / closed state detection switch 15.

[0032] The program file update unit 24 updates the program file 30. Specifically, when the program file update unit 24 receives an instruction to update the program file from the management device 50A, the program file update unit 24 updates the program file 30 (hereinafter also referred to as the pre-update program file) stored in the storage unit 16 to the update program file 31 (hereinafter also referred to as the updated program file) transmitted from the management device 50A.

[0033] When updating the program file, it is preferable from a safety standpoint that there are no passengers inside the car 11 and the door of the car 11 is closed. Therefore, it is preferable that the program file update unit 24 updates the program file when the passenger detection unit 22 detects that there are no passengers inside the car 11 and the door open / closed state detection unit 23 detects that the door of the car 11 is closed.

[0034] The abnormality detection unit 25 detects an abnormality in the operation of the elevator 10 based on the detection results of each sensor (for example, an acceleration sensor) not shown that is provided in the elevator 10. When the abnormality detection unit 25 detects an abnormality in the operation of the elevator 10, it transmits a notification that an abnormality has occurred in the elevator 10 to the management device 50A via the communication unit 17.

[0035] <Management device 50A> The management device 50A is a device that remotely manages the elevators 10. The management device 50A includes a communication unit 51 that communicates with each elevator 10 via a network, a memory unit 52, an input unit 53 that accepts input to the management device 50A, a display unit 54 that displays various information, and a control unit 60A.

[0036] The storage unit 52 stores various data used by the management device 50A. The storage unit 52 stores the program files 30 used by each elevator 10 and the update program files 31 for each elevator 10. The storage unit 52 also stores an update schedule 70 that indicates the times at which the program files are to be updated, and that is created by an update schedule creation unit 61, which will be described later. The update schedule 70 is linked to the names of the program files to be updated for each elevator 10.

[0037] The control unit 60A controls each unit of the management device 50A. The control unit 60A includes an update schedule creation unit 61, an update unit 62, a verification operation instruction unit 63, a detection unit 64, a determination unit 65A, and a schedule deletion unit 66.

[0038] The update schedule creation unit 61 creates an update schedule 70 for the program files of each elevator 10. The update schedule creation unit 61 creates the update schedule 70 based on information indicating time periods during which the program files for each elevator 10 can be updated. The information indicating time periods during which the program files can be updated may be stored in advance in the storage unit 52, or may be input to the management device 50A via the input unit 53.

[0039] When multiple elevators 10 are scheduled to have their program files updated to the same program file, the update schedule creation unit 61 sets at least one of the elevators 10 scheduled to have their program files updated to the same program file as a lead update elevator (described later). The elevator 10 set as the lead update elevator may be, for example, the elevator 10 with the earliest scheduled update time among the multiple elevators 10 scheduled to have their program files updated to the same program file. Furthermore, when multiple elevators scheduled to have their program files updated in a single building, only one of the multiple elevators may be set as the lead update elevator. In this embodiment, the update schedule creation unit 61 sets the elevator 10 with the earliest scheduled update time among the multiple elevators 10 scheduled to have their program files updated to the same program file as the lead update elevator. Furthermore, when multiple elevators scheduled to have their program files updated in a single building, the update schedule creation unit 61 may create an update schedule such that each elevator has a different update time. This minimizes the number of unavailable elevators.

[0040] The update unit 62 updates the program file of each elevator 10 based on the update schedule 70. The update unit 62 references the update schedule stored in the storage unit 52 to acquire the update time of the program file of each elevator 10 and the file name of the update program file. Then, when the program file update time arrives, the update unit 62 reads out the update program file 31 of each elevator 10 from the storage unit 52 and transmits it to the elevator 10 for which the program file is scheduled to be updated.

[0041] When multiple elevators 10 are scheduled to be updated to the same program file, the update unit 62 transmits the update program file 31 to those elevators 10 that the update schedule creation unit 61 has set as the leading update elevator among the multiple elevators 10, and does not transmit the update program file 31 to the other elevators 10. The update unit 62 transmits the update program file 31 to elevators 10 other than the leading update elevator 10A among the multiple elevators scheduled to be updated to the same program file, based on the determination result of a determination unit 65A, which will be described later. Details of this processing will be described later.

[0042] The confirmation operation instruction unit 63 executes a confirmation operation on the preceding update elevator 10A that has been updated from the pre-update program file 30 to the update program file 31. When the control unit 20 of the preceding update elevator 10A receives an instruction to execute a confirmation operation from the management device 50A, it executes a predetermined confirmation operation. When the abnormality detection unit 25 of the preceding update elevator 10A detects an abnormality in the operation of the preceding update elevator 10A during the confirmation operation, it sends a notification of the abnormality to the management device 50A.

[0043] The detection unit 64 detects the occurrence of an abnormality during the confirmation operation of the precedent update elevator 10A. Specifically, the detection unit 64 detects the occurrence of an abnormality during the confirmation operation of the precedent update elevator 10A by determining whether or not a notification that an abnormality has been detected during the confirmation operation has been received from the abnormality detection unit 25 of the precedent update elevator 10A.

[0044] When the detection unit 64 detects the occurrence of an abnormality during the confirmation operation of the lead update elevator 10A, the determination unit 65A determines whether or not it is appropriate to update the program file of an elevator whose program file is scheduled to be updated thereafter (hereinafter also referred to as an update-scheduled elevator). In this embodiment, the determination unit 65A determines that it is inappropriate to update the program file of an elevator 10 whose program file is scheduled to be updated thereafter to the same program file as the update program file of the lead update elevator 10A. Note that if the determination unit 65A does not determine that the program file update is inappropriate, in other words, if no abnormality has occurred during the confirmation operation of the lead update elevator 10A, the update unit 62 updates the program file of the elevator 10 whose program file is scheduled to be updated to the same program file as the update program file of the lead update elevator 10A according to the update schedule 70.

[0045] The schedule deletion unit 66 deletes the update schedule for the program file of the elevator 10 for which the determination unit 65A has determined that updating of the program file is inappropriate (i.e., the elevator scheduled for update). Specifically, the schedule deletion unit 66 deletes the update schedule for the elevator 10 for which the determination unit 65A has determined that updating of the program file is inappropriate from the update schedule stored in the memory unit 52.

[0046] <Example of Management Method Processing by Management Device 50A> Next, an example of the processing of the management method by the management device 50A will be described with reference to Fig. 2. Fig. 2 is a flowchart showing an example of the processing of the management method by the management device 50A. In this example, an example of updating multiple elevators 10 to the same program file will be described.

[0047] 2, in the management method by the management device 50A, first, the update unit 62 updates the program file of the elevator 10 (i.e., the lead update elevator 10A) with the earliest scheduled update time among the elevators 10 scheduled to be updated to the same program file (step S1, update step). Specifically, the update unit 62 reads out the update program file 31 of the lead update elevator 10A from the storage unit 52, transmits it, and instructs the lead update elevator 10A to update the program file to the update program file 31. As a result, the program file update unit 24 of the lead update elevator 10A updates the pre-update program file 30 to the update program file 31.

[0048] Next, the confirmation operation instruction unit 63 causes the leading update elevator 10A to perform confirmation operation (step S2). As a result, the control unit 20 of the leading update elevator 10A performs confirmation operation. Then, if the abnormality detection unit 25 of the leading update elevator 10A detects an abnormality in the operation of the leading update elevator 10A during the confirmation operation, it transmits a notification that an abnormality has occurred to the management device 50A.

[0049] Next, the detection unit 64 detects the occurrence of an abnormality in the confirmation operation of the preceding update elevator 10A by determining whether or not a notification that an abnormality has been detected in the confirmation operation of the preceding update elevator 10A has been received from the abnormality detection unit 25 of the preceding update elevator 10A (step S3, detection step).If the occurrence of an abnormality is not detected in step S3 (NO in step S3), the update unit 62 updates the program files of elevators for which the program files are scheduled to be updated later (i.e., elevators scheduled to be updated) (step S4).

[0050] On the other hand, if an abnormality is detected in step S3 (YES in step S3), the judgment unit 65A judges that the program file update is inappropriate for elevators 10 that are scheduled to update their program files to the same program file as the update program file of the preceding update elevator 10A (step S5, judgment step).

[0051] Next, the schedule deletion unit 66 deletes the update schedule of the program file of the elevator 10 for which the determination unit 65A has determined that the program file update is inappropriate (step S6, schedule deletion step). Specifically, the schedule deletion unit 66 deletes the update schedule of the elevator 10 for which the determination unit 65A has determined that the program file update is inappropriate from the update schedule 70 stored in the storage unit 52.

[0052] As described above, when the management device 50A in this embodiment detects the occurrence of an abnormality in the confirmation operation of the preceding update elevator that has previously updated its program file to the update program file 31, it deletes the update schedule for the elevator 10 that is scheduled to be updated to the same program file as the update program file 31. This reduces the possibility that an abnormality that occurred in the preceding update elevator will occur in other elevators 10. This allows the management device 50A to improve the efficiency of the update work when updating the program files of multiple elevators 10.

[0053] The management device 50A in this embodiment also includes an update schedule creation unit 61 that sets at least one of the multiple elevators 10 for which a program file update is scheduled as a leading update elevator 10A, and creates an update schedule 70 for the program files of the multiple elevators 10. This makes it possible to automatically create the update schedule 70 that includes the setting of the leading update elevator 10A, thereby further improving the efficiency of the update work when updating the program files of the multiple elevators 10.

[0054] In the elevator management system 100A of this embodiment, the detection unit 64 of the management device 50A is configured to detect the occurrence of an abnormality during the confirmation operation of the precedent update elevator 10A based on whether or not a notification that an abnormality has been detected has been received from the abnormality detection unit 25 of the elevator 10, but the present invention is not limited to this. An elevator management system of one aspect of the present invention may be configured to acquire, via the communication unit 51, detection results detected by each sensor provided in the precedent update elevator 10A during the confirmation operation of the precedent update elevator 10A, and to detect the occurrence of an abnormality during the confirmation operation of the precedent update elevator 10A based on the acquired detection results.

[0055] In the elevator management system 100A of the present embodiment, the control unit 20 of the elevator 10 executes the check operation upon receiving an instruction from the check operation instruction unit 63 of the management device 50A, but the present invention is not limited to this. In an elevator management system according to one aspect of the present invention, the control unit 20 of the elevator 10 may be configured to automatically execute the check operation when the program file is updated from the management device 50A.

[0056] In the elevator management system 100A in this embodiment, the update schedule creation unit 61 is configured to create the update schedule 70, but the present invention is not limited to this. An elevator management system according to one aspect of the present invention may be configured such that the update schedule 70 is created by a person (manager), and the update schedule 70 created by the person is input to the management device 50A via the input unit 53 and stored in the storage unit 52.

[0057] [Embodiment 2] Other embodiments of the present disclosure will be described in detail below. For ease of explanation, the same reference numerals will be used to designate components having the same functions as those described in the first embodiment, and the description thereof will not be repeated.

[0058] Fig. 3 is a block diagram showing the configuration of the main parts of an elevator management system 100B according to this embodiment. As shown in Fig. 1, the elevator management system 100B includes a management device 50B instead of the management device 50A in the first embodiment. The management device 50B includes a control unit 60B instead of the control unit 60A in the first embodiment. The control unit 60B includes a determination unit 65B instead of the determination unit 65A in the first embodiment.

[0059] In the elevator management system 100A in the first embodiment, when an abnormality is detected in the confirmation operation of the preceding update elevator 10A, the determination unit 65A determines that the program file update is inappropriate for the elevators 10 that are scheduled to update their program files to the same program file as the update program file of the preceding update elevator 10A in the future. In contrast, the determination unit 65B in the present embodiment determines the appropriateness of the program file updates scheduled in the future by performing processing different from that of the determination unit 65A.

[0060] Specifically, when the determination unit 65B detects an abnormality in the confirmation operation of the preceding update elevator 10A, it first reads out the pre-update program file (program file 30) and the post-update program file (update program file 31) in the preceding update elevator 10A from the storage unit 52. Then, the determination unit 65B identifies a first difference, which is a difference in source code between the pre-update program file and the post-update program file.

[0061] Next, the determination unit 65B reads from the storage unit 52 the pre-update program file (program file 30) and the post-update program file (update program file 31) for each elevator scheduled to be updated in the future. The determination unit 65B then identifies a second difference, which is the difference in source code between the pre-update program file and the post-update program file, for each elevator scheduled to be updated. If at least a portion of the first difference overlaps with at least a portion of the second difference, the determination unit 65B determines that updating the program file for that elevator scheduled to be updated is inappropriate.

[0062] <Example of Management Method Process by Management Device 50B> Next, an example of the management method processing by the management device 50B will be described with reference to Fig. 4. Fig. 4 is a flowchart showing an example of the management method processing by the management device 50B.

[0063] As shown in FIG. 4, steps S1 to S4 of the management method by the management device 50B are the same as the processes of the management method by the management device 50A in the first embodiment.

[0064] In the management method by the management device 50B, if an abnormality is detected in the confirmation operation of the preceding update elevator 10A in step S3 (YES in step S3), the determination unit 65B identifies a first difference for the preceding update elevator 10A (step S11). Next, the determination unit 65B identifies a second difference for each update-scheduled elevator whose program file is scheduled to be updated thereafter (step S12). Next, the determination unit 65B determines whether at least a portion of the first difference overlaps with at least a portion of the second difference for each update-scheduled elevator (step S13). If there is no update-scheduled elevator whose first difference overlaps with at least a portion of the second difference (NO in step S13), the update unit 62 updates the program files for the elevators whose program files are scheduled to be updated thereafter (step S4).

[0065] On the other hand, if there is an elevator scheduled to be updated in which at least a portion of the first difference overlaps with at least a portion of the second difference (YES in step S13), the judgment unit 65B judges that updating the program file for that elevator scheduled to be updated is inappropriate (step S14, judgment step).

[0066] Next, the schedule deletion unit 66 deletes the update schedule of the program file of the elevator 10 for which the determination unit 65B has determined that updating of the program file is inappropriate (step S15, schedule deletion step).

[0067] As described above, in the management device 50B of this embodiment, when an abnormality is detected during the confirmation operation of a leading-update elevator whose program file has been updated to the update program file 31, the management device 50B deletes the update schedule of the program file of the scheduled-update elevator in which at least a portion of the first difference in the leading-update elevator overlaps with at least a portion of the source code difference between the pre-update program file and the updated program file. Here, the abnormality occurring during the confirmation operation of the leading-update elevator 10A is likely to be caused by the first difference or a portion of the first difference. Therefore, even in the scheduled-update elevator in which at least a portion of the first difference is included in at least a portion of the second difference, an abnormality similar to that of the leading-update elevator 10A is likely to occur after the program file is updated. Therefore, by deleting only the update schedule of the program file of the scheduled-update elevator in which at least a portion of the first difference overlaps with at least a portion of the second difference, the possibility of a malfunction occurring after the program file is updated can be reduced. As a result, the efficiency of the update work when updating the program files of multiple elevators 10 can be improved.

[0068] [Software implementation example] The functions of management device 50A or 50B (hereinafter referred to as "device") can be realized by a program that causes a computer to function as the device, and a program that causes a computer to function as each control block of the device.

[0069] In this case, the device includes a computer having at least one control device (e.g., a processor) and at least one storage device (e.g., a memory) as hardware for executing the program. The control device and storage device execute the program, thereby realizing the functions described in each of the above embodiments.

[0070] The program may be non-transitory and may be recorded on one or more computer-readable recording media. The recording media may or may not be included in the device. In the latter case, the program may be supplied to the device via any wired or wireless transmission medium.

[0071] [Additional Notes] The present disclosure is not limited to the above-described embodiments, and various modifications are possible within the scope of the claims. Embodiments obtained by appropriately combining the technical means disclosed in different embodiments are also included in the technical scope of the present disclosure. [Explanation of symbols]

[0072] 10 Elevator 10A Advance Renewal Elevator 30 Program files (pre-update program files) 31 Update program file (updated program file) 50A, 50B management device 61 Update Schedule Creation Department 62 Update section 64 Detection unit 65A, 65B judgment section 66 Schedule deletion section 70 Update Schedule

Claims

1. A management device that manages updates to program files of control programs for a plurality of elevators, an update unit that updates the program file of a leading update elevator that updates the program file first among the plurality of elevators from a pre-update program file to an updated program file; a detection unit that detects occurrence of an abnormality in a confirmation operation of the preceding updated elevator whose program file has been updated to the updated program file; a determination unit that, when the detection unit detects an abnormality in the confirmation operation, determines whether or not it is appropriate to update the program file of an elevator that is scheduled to have its program file updated thereafter; a schedule deletion unit that deletes the update schedule of the program file of the elevator scheduled for update, for which the determination unit has determined that updating of the program file is inappropriate; Equipped with The judgment unit determines that updating the program file of the elevator to be updated is inappropriate when at least a portion of a first difference, which is the difference in source code between the pre-update program file and the updated program file in the preceding update elevator, overlaps with at least a portion of a second difference, which is the difference in source code between the pre-update program file and the updated program file in the elevator to be updated.

2. The management device according to claim 1, wherein the determination unit determines that updating the program file of the elevator scheduled to be updated, which is scheduled to be updated to the same program file as the updated program file of the preceding update elevator, is inappropriate.

3. The management device according to claim 1, further comprising an update schedule creation unit that sets at least one of the plurality of elevators for which the program file is scheduled to be updated as the preceding update elevator and creates an update schedule for the program file for the plurality of elevators.

4. A management method for managing updates of program files of control programs for a plurality of elevators, comprising: an updating step of updating the program file of a leading update elevator, which will update the program file first among the plurality of elevators, from a pre-update program file to an updated program file; a detection step of detecting occurrence of an abnormality in a confirmation operation of the preceding updated elevator whose program file has been updated to the updated program file; a determination step of determining whether or not it is appropriate to update the program file of an elevator scheduled to be updated thereafter when an abnormality is detected in the confirmation operation in the detection step; a schedule deletion step of deleting the update schedule of the program file of the elevator to be updated, for which it has been determined in the determination step that updating of the program file is inappropriate; Including, In the judgment step, if at least a part of a first difference, which is the difference in source code between the pre-update program file and the updated program file in the preceding update elevator, overlaps with at least a part of a second difference, which is the difference in source code between the pre-update program file and the updated program file in the elevator to be updated, it is determined that updating the program file of the elevator to be updated is inappropriate.

5. 2. A program for causing a computer to function as the management device according to claim 1, the program causing a computer to function as the update unit, the detection unit, the determination unit, and the schedule deletion unit.

Images