CN111386540A

CN111386540A - Maintenance planning system and maintenance planning method

Info

Publication number: CN111386540A
Application number: CN201780097064.XA
Authority: CN
Inventors: 福井孝太郎; 谷口贵耶
Original assignee: Mitsubishi Electric Corp
Current assignee: Mitsubishi Electric Corp
Priority date: 2017-11-29
Filing date: 2017-11-29
Publication date: 2020-07-07
Anticipated expiration: 2037-11-29
Also published as: KR102242630B1; WO2019106753A1; KR20200061413A; TW201926091A; JPWO2019106753A1; CN111386540B; JP6462954B1

Abstract

The management terminal (300) displays an adjustment screen including a risk graph representing a time series of risk values, an allowable flag representing an allowable value, a deadline flag representing a deadline date when a risk value reaches the allowable value, and a change interface for changing the allowable value. The management terminal receives a designated allowable value designated through the change interface. A maintenance planning device (200) calculates a new deadline based on the specified allowable value and the risk value time series, and determines a maintenance work day based on the new deadline.

Description

Maintenance planning system and maintenance planning method

Technical Field

The present invention relates to a system for planning maintenance of a mechanical product accompanied by remote monitoring.

Background

In risk-based maintenance (RBM), a risk and an occurrence probability thereof at the time of occurrence of an abnormality are obtained for each part of equipment such as a plant, and an optimal maintenance plan is made based on a risk calculated by multiplying the risks.

Patent document 1 proposes the following method: in the risk-based maintenance, a time period when the equipment is damaged or the performance of the equipment is degraded is predicted, and an appropriate maintenance time period is determined by considering the prediction result as cost.

In some mechanical devices such as elevators, remote monitoring is performed to detect the occurrence of an abnormality based on information from sensors or the like in the machine body.

Patent document 2 proposes the following technique: in remote monitoring, information collected from various sensors is collected, and the occurrence timing of an abnormality is calculated from the amount of change in mahalanobis distance.

Documents of the prior art

Patent document

Patent document 1: japanese patent laid-open publication No. 2003-303243

Patent document 2: japanese patent laid-open publication No. 2013-113775

Disclosure of Invention

Problems to be solved by the invention

The downtime reference is applied when providing maintenance services to the owner of the device. Specifically, when a maintenance service is provided for an apparatus that rarely stops operating even if sufficient maintenance quality is not ensured, such as an elevator, the downtime reference may be applied.

However, the downtime reference does not appropriately reflect the expectations of the owners, and therefore, it is difficult to make the maintenance schedule efficient while maintaining the customer satisfaction.

The purpose of the present invention is to make a maintenance plan based on the allowable risk designated by a manager (including an owner).

Means for solving the problems

The maintenance scheduling system of the present invention includes: a display unit that displays an adjustment screen including a risk graph representing a time series of risk values, an allowable flag representing an allowable value, a deadline flag representing a deadline date when a risk value reaches the allowable value, and a change interface for changing the allowable value; a receiving unit that receives a specified allowable value specified by the change interface; an adjustment unit that calculates a new deadline based on the specified allowable value and the risk value time series; and a planning unit that determines a maintenance work day based on the new deadline day.

Effects of the invention

According to the present invention, a maintenance plan can be made according to the allowable risk designated by the manager (including the owner).

Drawings

Fig. 1 is a configuration diagram of a maintenance scheduling system 100 according to embodiment 1.

Fig. 2 is a configuration diagram of a maintenance planning apparatus 200 according to embodiment 1.

Fig. 3 is a configuration diagram of the management terminal 300 according to embodiment 1.

Fig. 4 is an explanatory diagram of the maintenance schedule data 120 according to embodiment 1.

Fig. 5 is a flowchart of a maintenance scheduling method in embodiment 1.

Fig. 6 is a diagram illustrating the adjustment screen 130 in embodiment 1.

Fig. 7 is a diagram illustrating movement of the adjustment screen 130 in embodiment 1.

Fig. 8 is an explanatory view of the maintenance work date in embodiment 1.

Fig. 9 is an explanatory view of the maintenance work date in embodiment 1.

Fig. 10 is an explanatory view of the maintenance work date in embodiment 1.

Fig. 11 is a configuration diagram of a maintenance planning apparatus 200 according to embodiment 2.

Fig. 12 is a flowchart of a maintenance scheduling method according to embodiment 2.

Fig. 13 is a flowchart of a maintenance scheduling method according to embodiment 2.

Fig. 14 is a diagram illustrating a restriction screen 140 in embodiment 2.

Fig. 15 is an explanatory view of the maintenance work date in embodiment 2.

Fig. 16 is an explanatory view of the maintenance work date in embodiment 2.

Fig. 17 is a configuration diagram of a maintenance planning apparatus 200 according to embodiment 3.

Fig. 18 is a configuration diagram of a maintenance planning apparatus 200 according to embodiment 4.

Fig. 19 is a flowchart of a phenomenon coping method in embodiment 4.

Fig. 20 is a hardware configuration diagram of maintenance planning apparatus 200 according to the embodiment.

Fig. 21 is a hardware configuration diagram of the management terminal 300 according to the embodiment.

Detailed Description

In the embodiments and the drawings, the same elements and corresponding elements are denoted by the same reference numerals. The description of elements labeled with the same reference numerals is omitted or simplified as appropriate. The arrows in the figure primarily represent data flow or processing flow.

Embodiment mode 1

The maintenance scheduling system 100 will be described with reference to fig. 1 to 10.

Description of the structure

The structure of the maintenance scheduling system 100 will be described with reference to fig. 1.

The maintenance planning system 100 is a system for making a maintenance plan for the monitored object 110.

The maintenance scheduling system 100 includes a monitoring target 110, a maintenance scheduling device 200, and a management terminal 300.

The monitoring target 110, the maintenance scheduling device 200, and the management terminal 300 communicate with each other via the network 101.

The monitoring object 110 is a device to be remotely monitored, and includes various sensors 111. The monitoring object 110 is, for example, an elevator or an escalator.

The maintenance planning apparatus 200 makes a maintenance plan for the monitoring target 110.

The management terminal 300 is used to manage a maintenance plan.

The structure of the maintenance planning apparatus 200 will be described with reference to fig. 2.

The maintenance planning apparatus 200 is a computer having hardware such as a processor 201, a memory 202, an auxiliary storage apparatus 203, and a communication apparatus 204. These pieces of hardware are connected to each other via signal lines.

The processor 201 is an IC (Integrated Circuit) that performs arithmetic processing, and controls other hardware. For example, the Processor 201 is a CPU (Central Processing Unit), a DSP (digital Signal Processor), or a GPU (Graphics Processing Unit).

The memory 202 is a volatile storage device. The memory 202 is also referred to as a main storage device or main memory. For example, the Memory 202 is a RAM (Random Access Memory). The data stored in the memory 202 is stored in the auxiliary storage device 203 as needed.

The secondary storage device 203 is a non-volatile storage device. The secondary storage device 203 is, for example, a ROM (Read Only memory), an HDD (Hard Disk Drive), or a flash memory. Data stored in the secondary storage device 203 is loaded into the memory 202 as needed.

The communication device 204 is a receiver and a transmitter. For example, the communication device 204 is a communication chip or NIC (network interface Card).

The maintenance scheduling apparatus 200 includes elements such as a screen 211, an adjustment unit 212, and a scheduling unit 213. These elements are implemented by software.

The auxiliary storage device 203 stores a maintenance scheduling program for causing the computer to function as the screen section 211, the adjustment section 212, the scheduling section 213, the storage section 291, and the communication section 292. The maintenance scheduling program is loaded into the memory 202 and executed by the processor 201.

Further, the auxiliary storage device 203 stores an OS (Operating System). At least a portion of the OS is loaded into memory 202 and executed by processor 201.

That is, the processor 201 executes the maintenance scheduling program while executing the OS.

Data obtained by executing the maintenance scheduling program is stored in a storage device such as the memory 202, the auxiliary storage device 203, a register in the processor 201, or a cache memory in the processor 201.

The memory 202 functions as the storage section 291. However, other storage devices may function as the storage portion 291 instead of the memory 202 or together with the memory 202.

The communication device 204 functions as a communication unit 292.

The maintenance planning apparatus 200 may have a plurality of processors instead of the processor 201. The plurality of processors share the role of the processor 201.

The maintenance scheduling program can be recorded (stored) in a non-volatile recording medium such as an optical disk or a flash memory so as to be readable by a computer.

The structure of the management terminal 300 will be explained with reference to fig. 3.

The management terminal 300 is a computer having hardware such as a processor 301, a memory 302, an auxiliary storage device 303, a communication device 304, and an input/output interface 305. These pieces of hardware are connected to each other via signal lines.

The processor 301 is an IC that performs arithmetic processing, and controls other hardware. For example, the processor 301 is a CPU, DSP, or GPU.

The memory 302 is a volatile storage device. The memory 302 is also referred to as a main storage device or main memory. For example, the memory 302 is a RAM. The data stored in the memory 302 is stored in the secondary storage device 303 as needed.

The secondary storage 303 is a non-volatile storage. The secondary storage device 303 is, for example, a ROM, HDD, or flash memory. Data stored in the secondary storage device 303 is loaded into the memory 302 as needed.

The communication means 304 is a receiver and a transmitter. The communication device 304 is, for example, a communication chip or NIC.

The input/output interface 305 is a port to which an input device and an output device are connected. For example, the input/output interface 305 is a USB terminal, the input devices are a keyboard and a mouse, and the output device is a display. USB is a short for Universal Serial Bus (Universal Serial Bus).

The management terminal 300 includes a controller 311 that controls the storage 391, the communication unit 392, the display unit 393, and the reception unit 394. The control section 311 is implemented by software.

The auxiliary storage device 303 stores a management program for causing a computer to function as the control unit 311, the storage unit 391, the communication unit 392, the display unit 393, and the reception unit 394. The hypervisor is loaded into memory 302 for execution by processor 301.

Further, the OS is stored in the auxiliary storage device 303. At least a portion of the OS is loaded into memory 302 for execution by processor 301.

That is, the processor 301 executes the hypervisor while executing the OS.

Data obtained by executing the hypervisor is stored in a storage device such as the memory 302, the auxiliary storage device 303, a register in the processor 301, or a cache memory in the processor 301.

The memory 302 functions as the storage unit 391. However, other storage devices may also function as the storage section 391 instead of the memory 302 or in addition to the memory 302.

The communication device 304 functions as a communication unit 392.

The input/output interface 305 functions as a display unit 393 and a reception unit 394.

The management terminal 300 may have a plurality of processors instead of the processor 301. The plurality of processors shares the role of the processor 301.

The management program can be recorded (stored) in a nonvolatile recording medium such as an optical disk or a flash memory so as to be readable by a computer.

The maintenance schedule data 120 is explained with reference to fig. 4.

The maintenance plan data 120 shows a maintenance plan for the monitored object 110.

Specifically, the maintenance schedule data 120 shows an access schedule and a maintenance job schedule.

The visit schedule is a schedule of visit days.

The visit date is the date on which the worker visited the subject facility.

The subject facility is a facility having a monitoring subject 110.

The dashed triangles indicate regular visit days.

The maintenance work schedule is a schedule of maintenance work days.

The maintenance work day is a day when the worker performs the maintenance work on the monitoring target 110.

The solid line triangle indicates the maintenance work day.

The maintenance work day is determined based on the time series of risk values of the monitoring target 110.

Specifically, the visit date before the day on which the risk value (total) reaches the allowable value is determined as the maintenance work date.

The allowable value is a value determined as the maximum risk value that is allowed.

The risk value (total) is the sum of the individual risk values. For example, the risk value (total) is the sum of the risk value a and the risk value B.

The risk value a is the risk value of the failure risk a.

The risk value B is the risk value of the failure risk B.

The risk value is a value representing the degree of risk of failure. The greater the risk value, the higher the risk of failure. The risk of failure becomes higher with the passage of time.

The time series of risk values and the initial maintenance schedule data 120 are obtained by existing methods in Risk Based Maintenance (RBM).

For example, the time series of the risk values and the initial maintenance schedule data 120 are obtained by the method disclosed in patent document 1.

Description of actions

The operation of the maintenance scheduling system 100 (particularly, the operation of the maintenance scheduling device 200) corresponds to a maintenance scheduling method. Further, the steps of the maintenance planning method correspond to the procedure of the maintenance planning program.

The maintenance scheduling method is explained with reference to fig. 5.

In the description of the maintenance planning method, the risk value means a risk value (total).

The initial maintenance scheduling data 120 is stored in the storage 291 of the maintenance scheduling device 200. Further, the risk value time series and the initial allowable value are stored in the storage 291 of the maintenance scheduling device 200.

In step S110, the display unit 393 displays the adjustment screen 130 on the display.

The adjustment screen 130 will be described with reference to fig. 6.

The adjustment screen 130 includes a risk map 131, an allowance flag 132, a deadline flag 133, and a change interface 134.

The risk graph 131 represents a time series of risk values of the monitored subject 110.

Specifically, the risk graph 131 is a line graph showing a time series of risk values. The vertical axis shows the risk value and the horizontal axis shows the time of day.

The solid line portion of the risk graph 131 represents the performance value time series. The performance value is a past risk value.

The dashed portion of the risk graph 131 represents a predicted value time series. The predicted value is a future risk value.

The tolerance mark 132 indicates a tolerance value. Specifically, the tolerance mark 132 is a straight line.

The deadline flag 133 indicates a deadline day. The deadline day is the day when the risk value reaches the allowable value. In other words, the term day is the day of the risk value corresponding to the same value as the tolerance value. Specifically, the term mark 133 is an arrow indicating a term day.

The change interface 134 is an interface for changing the allowable value.

Specifically, the change interface 134 is an up button and a down button. The up button is pressed to raise the allowable value and the down button is pressed to lower the allowable value.

Returning to fig. 5, the procedure of step S110 will be described.

First, the screen section 211 generates data of the adjustment screen 130.

Next, the communication unit 292 transmits the data of the adjustment screen 130 to the management terminal 300.

Next, the communication unit 392 receives data of the adjustment screen 130 from the maintenance scheduling device 200.

Then, the display unit 393 displays the adjustment screen 130 on the display using the data of the adjustment screen 130.

A process of generating data of the adjustment screen 130 will be described.

First, the screen unit 211 calculates an initial deadline date from the risk value time series and the initial allowable value. The initial deadline date is a date corresponding to a risk value of the same value as the initial tolerance value.

Next, the screen unit 211 generates a risk graph 131 from the risk value time series, a tolerance flag 132 from the initial tolerance value, and a deadline flag 133 from the initial deadline date.

Then, the screen section 211 generates data of the adjustment screen 130.

In step S120, the reception unit 394 receives the designated allowable value.

The designated allowable value is an allowable value designated through the change interface 134 of the adjustment screen 130.

The process of step S120 will be explained.

First, the administrator operates the input device of the management terminal 300, thereby specifying the allowable value using the change interface 134. Specifically, the administrator operates the mouse to press the up button or the down button.

Then, the reception unit 394 receives the designated allowable value.

In step S130, adjustment unit 212 calculates a new deadline.

The new term day is a term day corresponding to a specified permissible value.

The process of step S130 will be explained.

First, the communication unit 392 transmits a designated allowable value to the maintenance scheduling device 200.

Next, the communication unit 292 receives the designated allowable value from the management terminal 300. The storage 291 also updates the stored allowable value to a predetermined allowable value.

Then, adjusting unit 212 calculates a new deadline based on the risk value time series and the designated allowable value. The new deadline date is the day the risk value reaches the specified tolerance value. In other words, the new term day is a day corresponding to a risk value of the same value as the specified permissible value. The storage 291 updates the stored term date to a new term date.

In step S140, the screen section 211 updates the adjustment screen 130.

Specifically, the screen unit 211 moves the permission flag 132 of the adjustment screen 130 according to the designated permission value, and moves the deadline flag 133 of the adjustment screen 130 according to the new deadline date.

The movement of the adjustment screen 130 will be described with reference to fig. 7.

When the up button as the change interface 134 is pressed, the permission flag 132 moves upward, and the deadline flag 133 moves rightward.

When a down button as the change interface 134 is pressed, the permission flag 132 moves downward, and the deadline flag 133 moves leftward.

Returning to fig. 5, the procedure of step S140 will be described.

First, the screen unit 211 generates a risk graph 131 from the risk value time series, a permission flag 132 from a designated permission value, and a deadline flag 133 from a new deadline date.

Next, the screen section 211 generates updated data of the adjustment screen 130.

Next, the communication unit 292 transmits the updated data of the adjustment screen 130 to the management terminal 300.

Next, the communication unit 392 receives the updated data of the adjustment screen 130 from the maintenance scheduling device 200.

Then, the display unit 393 displays the adjustment screen 130 on the display using the updated data of the adjustment screen 130.

In step S150, the planning unit 213 determines a maintenance work day based on the new deadline.

Then, the planning unit 213 registers the maintenance work date in the maintenance scheduling data 120.

The process of step S150 will be explained.

First, the planning unit 213 selects the next visit date from the maintenance schedule data 120.

Next, the planning unit 213 compares the next visit date with the new deadline date.

When the next visit date is a date before the new deadline date, the planning unit 213 determines the visit date before the new deadline date as the maintenance work date. Specifically, the planning unit 213 selects an access day immediately before the new deadline from the maintenance schedule data 120. The selected visit date becomes the maintenance work date. Then, the planning unit 213 registers the maintenance work date in the maintenance scheduling data 120.

When the next visit date is a date after the new deadline date, the planning unit 213 determines an additional visit date before the new deadline date as the maintenance work date. Specifically, the planning unit 213 selects any one of the days before the new deadline. The selected day becomes an additional access day and a maintenance work day. Then, the scheduling unit 213 registers the added visit date in the maintenance scheduling data 120. Further, the planning unit 213 registers the maintenance work date in the maintenance scheduling data 120.

The determination of the maintenance operation date will be described with reference to fig. 8 to 10.

Currently is the day after the 2 nd visit day and is the day before the 3 rd visit day. That is, the next visit date is the 3 rd visit date.

Fig. 8 to 10 show 3 allowable values. The 1 st tolerance is the maximum tolerance, the 2 nd tolerance is the intermediate tolerance, and the 3 rd tolerance is the minimum tolerance.

In fig. 8, the administrator designates the 1 st allowable value.

In this case, the next visit date (visit 3 date) is a date before the deadline date, and the visit date immediately before the deadline date is the visit 4 date. Therefore, the planning unit 213 determines the 4 th visit date as the maintenance work date.

In fig. 9, the administrator designates the 2 nd allowable value.

In this case, the next visit date (visit 3 date) is a date before the deadline date, and the visit date immediately before the deadline date is the visit 3 date. Therefore, the planning unit 213 determines the 3 rd visit date as the maintenance work date.

In fig. 10, the administrator designates the 3 rd allowable value.

In this case, the next visit date (visit date 3) is a day after the deadline date. Therefore, the planning unit 213 selects the day before the next visit date as an additional visit date, and determines the additional visit date as the maintenance work date.

Supplement to embodiment 1

A specific example of the monitored object 110 is a mechanical device.

The mechanical apparatus is constituted by a plurality of components, and each component deteriorates depending on the number of uses or the lapse of years. Therefore, maintenance work (inspection, adjustment, component replacement, and the like) is performed periodically so that an abnormality such as a service stop does not occur.

A specific example of the mechanical equipment is an elevator.

Remote monitoring of the elevator is implemented. In remote monitoring, sensor information obtained by the sensors 111 inside the body is centralized at the center. When an abnormality is detected by remote monitoring, a maintenance worker goes to the site to perform repair.

A specific example of the monitored object 110 or a facility having the monitored object 110 is a factory.

In order to make a reasonable maintenance plan for the plant, the influence degree and occurrence frequency of each abnormal item are multiplied, and thus the risk is calculated. Then, Risk Based Maintenance (RBM) is performed. In the RBM, a maintenance period and maintenance contents are decided according to the risk. The influence level indicates an influence when an abnormality occurs. Specifically, the influence degree is obtained from the influence on human life, the loss of money, the time required for coping with the damage, and the like. The frequency of occurrence indicates the possibility of occurrence of an abnormality. In a general RBM, the frequency of occurrence is determined from the actual performance of the occurrence of a model failure, knowledge of a designer, and the like.

Further, with the progress of analysis techniques and simulation techniques, techniques for predicting component degradation due to use have been proposed. Even if simulation is difficult, the number of times of use and the time of use in which an abnormality occurs can be predicted by performing a durability test in many cases.

Here, the frequency of occurrence of a failure increases according to component deterioration as a cause of the failure. Therefore, if the estimation result obtained by the degradation prediction technique is used, the frequency of occurrence of each failure at a specific time can be estimated.

Further, since the state of the component is improved after the maintenance work is performed, the frequency of occurrence of an abnormality regarding the component on which the maintenance work is performed is reduced.

Even if the deterioration state changes, the degree of influence of each abnormality does not change. Therefore, if the frequency of occurrence and the degree of influence are multiplied, the risk at a specific time can be calculated.

Here, the degree of influence of a failure that causes damage to a user is intentionally set to a higher value than a normal failure, and thus degradation of an important component is reflected in a larger risk.

In the maintenance scheduling system 100, the administrator (including the owner of the monitoring target 110) can easily change the allowable value as the reference for performing the maintenance work. The risk value of the monitored object 110 is calculated using the RBM.

First, when the monitoring target 110 is set, an initial allowable value (initial value of allowable level) is determined. Then, a deterioration prediction is performed using the result of the acceleration test, past failure performance data, and the like, a risk value time series is calculated from the prediction result, and initial maintenance schedule data 120 is generated from the risk value time series.

In the case where an operator visits the site at a certain period, maintenance work is performed at the time of regular visits immediately before the risk value exceeds the allowable value. In addition, a regular maintenance plan (initial maintenance plan) is made so that the risk value does not exceed the allowable value and the amount of work is minimized. In this case, conditions such as the dependency relationship between the staff plan and the plurality of jobs at the execution site of the maintenance job are considered.

After the operation of the object to be monitored 110 is started, remote monitoring is performed by the sensor 111 of the object to be monitored 110. Then, the deterioration state of each member of the monitoring target 110 is grasped.

Here, there are data obtained by the degradation estimation and observed data, but there is measurement variation in the observed data. Therefore, by combining these 2 types of data by a method such as a kalman filter, it is possible to estimate the degradation with higher accuracy. For a site that is not remotely monitored, the state estimation may be performed using the inspection result at the time of visit.

When the difference between the deterioration state of all the components and the deterioration state predicted at the time of installation is within a certain range, it is not necessary to correct the maintenance schedule. Therefore, the operation is continued.

On the other hand, in the case where the difference exceeds a certain range, the maintenance schedule is revised.

As the correction in stage 1, the timing and content of the implementation of the periodic maintenance are adjusted.

When the state deterioration is earlier than the prior prediction, the maintenance schedule is changed to cope with the previous 1-time regular access. Further, when the risk value exceeds the allowable value immediately before the maintenance execution date due to the deterioration, the schedule of the maintenance work can be adjusted in units of several days.

Even when the deterioration of the state is delayed from the prior prediction, the maintenance schedule can be changed so as to cope with the next 1-time regular access.

Further, by optimizing the maintenance schedule based on the same constraint condition as that in the initial maintenance schedule generation, the final implementation content of the regular maintenance can be determined.

If the increase in the risk value cannot be made to fall within the allowable range by the correction in stage 1, the maintenance schedule is changed so as to perform irregular maintenance. In particular, if there is no time margin until the risk value reaches the allowable value, the maintenance schedule is changed to implement the emergency trip. In emergency attendance, an operator makes an emergency visit to the site to perform maintenance work on a target site. On the other hand, when there is a time margin, the maintenance schedule of the entire target machine body can be optimized on the premise of access execution for performing the non-periodic maintenance before the non-periodic maintenance is performed. This enables maintenance work for the target site to be performed together with maintenance work for other sites.

When the job content at the time of the next and subsequent accesses is adjusted, the maintenance schedule data 120 is updated, and the monitoring of the state change is continued based on the updated data. By correcting the maintenance schedule when it is found that the maintenance schedule cannot completely cope with the risk, it is possible to always determine an optimal coping guideline according to the maintenance scheduling system 100.

In addition, the accuracy of the degradation prediction is improved in the course of operating the system. Therefore, the initial maintenance plan itself can also be re-estimated at a longer period, so that the effect of the improvement is reflected in the initial maintenance plan.

The allowable value of the risk is preferably set according to the desire of the administrator.

For example, in high-end hotels, it is desirable to maintain noise and vibration at extremely low levels. In addition, in medical institutions, extremely short downtime is required.

In this case, the allowable value is set lower than usual, and thus an optimal maintenance plan reflecting the desire can be made. However, when the allowable value is adjusted in this way, it is not possible to allow adjustment to a level at which a failure affecting the human body of the user occurs.

In addition to the risk value being used when the maintenance service company generates the maintenance plan, the risk value can be effectively used by disclosing the risk value to the administrator in real time.

The maintenance scheduling system 100 has a management terminal 300. The management terminal 300 may be installed at a central facility where the maintenance scheduling system 100 is operated, or may be installed at a remote location connected via the network 101.

The manager can use the management terminal 300 to confirm that the maintenance service company is managing the risk of the machine body and appropriately perform the maintenance work. Further, the manager can change the allowable value on the spot according to the study result about the appropriate allowable value.

When the manager changes the allowable value, the maintenance plan is recalculated using the current prediction of the risk value. The maintenance planning system 100 plans unscheduled maintenance in the event that the risk value is already above the new allowable value, or in the event that the risk value is predicted to be above the new allowable value before the next scheduled visit. This makes it possible to quickly respond to the desires of the administrator.

Effects of embodiment 1

The maintenance scheduling system 100 provides the adjustment screen 130 to the administrator, so that the administrator can appropriately adjust the allowable value. As a result, the maintenance service desired by the administrator is provided. Therefore, customer satisfaction can be improved.

Other structure

The maintenance scheduling system 100 (e.g., the maintenance scheduling device 200) may include a generation unit that generates the initial maintenance scheduling data 120. The generation unit predicts a future risk value time series from a past risk value time series, and generates maintenance schedule data 120 from the future risk value time series. In the prediction of the risk values and the generation of the maintenance schedule data 120, the existing methods in risk-based maintenance can be utilized.

Embodiment mode 2

A description will be given of a method of restricting the operation of monitoring target 110 instead of adding an access day when the next access day is a day after the new deadline day, mainly with reference to fig. 11 to 16, as a difference from embodiment 1.

Description of the structure

The maintenance scheduling system 100 has the same configuration as that of embodiment 1 (see fig. 1).

The configuration of the maintenance planning apparatus 200 will be described with reference to fig. 11.

The maintenance planning apparatus 200 further includes a limiting unit 214 and a predicting unit 215.

The maintenance scheduling program also causes the computer to function as the limiting unit 214 and the predicting unit 215.

Description of actions

The maintenance scheduling method will be described with reference to fig. 12 and 13.

In step S201 (see fig. 12), the display unit 393 displays the restriction screen 140 on the display.

The restriction screen 140 will be described with reference to fig. 14.

The restriction screen 140 has a restriction interface 141.

The restriction interface 141 is an interface for specifying an action restriction for the monitoring object 110. The restriction interface 141 includes an interface for specifying a recommended action restriction.

Specifically, the restriction interface 141 has check boxes for each type of action restriction.

Referring back to fig. 12, the procedure of step S201 will be described.

First, the screen section 211 generates data of the restriction screen 140.

Next, the communication unit 292 transmits the data of the restriction screen 140 to the management terminal 300.

Next, the communication unit 392 receives the data of the restriction screen 140 from the maintenance scheduling device 200.

Then, the display unit 393 displays the restriction screen 140 on the display using the data of the restriction screen 140.

In step S202, the reception unit 394 receives the designated operation restriction.

The designated action limit is an action limit designated through the limit interface 141 of the limit screen 140.

The process of step S202 will be explained.

First, the administrator operates the input device of the management terminal 300, thereby specifying the operation restriction using the restriction interface 141. Specifically, the administrator operates the mouse to check a check box for any operation restriction.

Then, the reception unit 394 receives the designated operation restriction.

Further, the communication unit 392 transmits a notification of specifying the operation restriction to the maintenance scheduling device 200.

Next, the communication unit 292 receives a notification of specifying the operation restriction from the management terminal 300.

Then, the storage 291 stores the designated operation restriction.

In step S211, the display unit 393 displays the adjustment screen 130 on the display.

Step S211 is the same as step S110 (see fig. 5) in embodiment 1.

In step S212, the reception unit 394 receives the designated allowable value.

Step S212 is the same as step S120 (see fig. 5) in embodiment 1.

In step S213, adjustment unit 212 calculates a new deadline.

Step S213 is the same as step S130 (see fig. 5) in embodiment 1.

In step S220, the limiting unit 214 selects the next visit date from the maintenance schedule data 120.

Then, the restricting unit 214 compares the next visit date with the new deadline date.

If the next visit date is a day before the new term date, the process proceeds to step S221 and step S222.

If the next visit date is a date after the new deadline date, the process proceeds to step S231 (see fig. 13).

In step S221, the screen unit 211 updates the adjustment screen 130.

The update method is the same as step S140 (see fig. 5) in embodiment 1.

In step S222, the planning unit 213 determines the visit date before the new deadline as the maintenance work date. Specifically, the planning unit 213 selects an access day immediately before the new deadline from the maintenance schedule data 120. The selected visit date becomes the maintenance work date.

In step S231 (see fig. 13), the limiting unit 214 limits the operation of the monitoring target 110.

Specifically, the limiting unit 214 generates an operation command corresponding to the designated operation limit. Then, the communication unit 292 transmits the generated operation command to the monitoring target 110. The monitoring object 110 receives the operation command and operates in accordance with the received operation command. This restricts the operation of the monitoring target 110.

In step S232, the prediction unit 215 calculates a time series of risk values after the limitation.

The restricted risk value time series is a risk value time series in which the motion of the monitoring subject 110 is restricted.

Specifically, the prediction unit 215 calculates a future risk time series of the monitoring target 110 from the restricted operation of the monitoring target 110 and the past risk time series of the monitoring target 110.

In the calculation of the risk value time series, the existing calculation method in the risk-based maintenance can be utilized.

In step S233, adjustment unit 212 calculates the limited deadline.

The limited term day is a term day corresponding to a predetermined allowable value after the operation of the monitoring target 110 is limited.

Specifically, adjustment unit 212 calculates the limited deadline date from the time series of the designated allowable value and the limited risk value. The deadline day after the restriction is the day when the risk value reaches the specified tolerance value. In other words, the limited term day is a day corresponding to a risk value of the same value as the specified permissible value. The storage 291 updates the stored term date to the limited term date.

In step S234, the screen unit 211 updates the adjustment screen 130.

Specifically, the screen unit 211 moves the permission flag 132 of the adjustment screen 130 according to the designated permission value, and moves the deadline flag 133 of the adjustment screen 130 according to the limited deadline date.

The process of step S234 is the same as the process of step S140 (see fig. 5) in embodiment 1.

In step S235, the planning unit 213 determines a maintenance work day based on the limited deadline.

The process of step S235 is the same as the process of step S150 (see fig. 5) in embodiment 1.

The determination of the maintenance work date will be described with reference to fig. 15 and 16.

In fig. 15, the risk graph shows a time series of risk values before the action of the monitoring subject 110 is restricted.

The next visit date (visit 3 date) is a day after the deadline date. Therefore, the action of the monitoring object 110 is limited.

In fig. 16, the risk graph shows a time series of risk values after the motion of the monitoring subject 110 is restricted. Since the operation of the monitoring target 110 is already restricted, the increase in the risk value is suppressed.

The next visit date (visit 3 date) is a day before the deadline date, and the visit date immediately before the deadline date is the visit 3 date. Therefore, the planning unit 213 determines the 3 rd visit date as the maintenance work date.

Supplement to embodiment 2

When it is difficult to reduce the increase in the risk value to the allowable value or less by only correcting the job content at the scheduled access, the operation of the monitoring target 110 is partially restricted instead of performing the non-periodic maintenance. Most components deteriorate according to the number of uses. Therefore, by limiting the number of uses, the progress of deterioration can be suppressed. The limiting unit 214 determines the level of operation limitation so that the risk value of the next visit date is smaller than the allowable value. When the risk value cannot be suppressed only by the operation restriction, the planning unit 213 determines the added visit date as the maintenance work date.

The contents of the operation restriction are determined in advance and registered in the storage portion 291. The content of the action restriction can be displayed on the display of the management terminal 300. Further, the state of execution of the operation restriction can be displayed on the display of the management terminal 300. The administrator can change the content of the operation restriction on the restriction screen 140.

When the content of the operation restriction is changed, the prediction unit 215 recalculates the risk value time series. When it is estimated that the risk value is higher than the allowable value, the planning unit 213 makes a maintenance plan to perform irregular maintenance, as in the case where no operation restriction is performed.

The operation restriction may be performed for the entire device or may be limited to a range directly related to a component in which deterioration progresses.

For example, when a specific landing door of an elevator is deteriorated, the number of times of use of the elevator at the floor may be limited.

In addition, when deterioration associated with a drive mechanism of the elevator occurs, the operating speed of the elevator car may be reduced, or the setting of the passenger detection section may be changed, thereby operating the elevator car so as to limit the number of passengers.

Further, when the landing door is deteriorated, the door operation speed or the starting acceleration may be reduced at the time of opening the door or at the time of closing the door.

Further, in the case where a part of the hoistway is deteriorated, it is possible to restrict the speed of the elevator car to be reduced when the elevator car passes through the deteriorated part.

The manager can select a recommended item (recommended action limit). The recommended item is an item having a small influence and is selected with reference to a normal usage pattern.

The confirmation step may be provided before the selected operation restriction is applied. In the confirmation step, display unit 393 displays the time series of the restricted risk values and the next maintenance work day result, which are notified from maintenance planning apparatus 200, on a display. After confirming the display, the administrator determines the action restriction to be applied. Then, after determining the operation restriction to be applied, the restriction unit 214 restricts the operation of the monitoring target 110.

When the operation restriction is applied, the restriction unit 214 may notify the user of the monitoring target 110 of the content of the applied operation restriction.

When the monitoring target 110 is an elevator, a message may be displayed on a display in the elevator car, a mail may be sent to a mail address registered in advance, or a message may be displayed on an advertising display provided around a landing door.

Effects of embodiment 2

Even when the next access day is a day after the new deadline day, an arbitrary access day can be set as the maintenance work day without adding an access day.

Embodiment 3

The following describes a method of proposing recommended action restrictions, mainly with reference to fig. 17, which is different from embodiment 1 and embodiment 2.

Description of the structure

The configuration of the maintenance planning apparatus 200 will be described with reference to fig. 17.

The maintenance planning apparatus 200 further includes a recommendation unit 216.

The maintenance scheduling program also causes the computer to function as the recommendation unit 216.

Description of actions

The recommendation unit 216 determines a recommended action limit in advance.

Specifically, the recommendation unit 216 determines recommended operation limits based on the operation history of the monitoring target 110.

The operation history of the monitoring target 110 is data indicating the past operation status of the monitoring target 110, and is stored in the storage 291 in advance.

When the administrator sets the allowable range of the operation restriction, it is difficult to clearly specify the allowable range.

Therefore, the recommendation unit 216 determines recommended action limits based on the action history of the monitoring target 110.

For example, when the monitoring target 110 is an elevator, the recommending unit 216 obtains the frequency of use for each time slot or each floor. Then, the recommending unit 216 selects a time zone or floor with little influence as the restriction target, and determines the use limit or speed limit of the restriction target as the recommended operation limit. The recommendation unit 216 may select a building similar to the building having the elevator of the monitoring target 110 in use, the number of floors, or the like based on the building data indicating the information of each building, and determine the recommended operation limit based on data obtained by evaluating the operation limit effect of the elevator in the selected building. That is, the recommendation unit 216 may determine recommended action limits based on the influence of action limits previously implemented in similar buildings.

Effects of embodiment 3

Since the recommended operation restriction is determined in the maintenance scheduling system 100, the manager can appropriately restrict the operation of the monitoring target 110 by selecting the recommended operation restriction on the restriction screen 140.

Embodiment 4

A description will be given of a method of appropriately changing a maintenance schedule when a large-scale disaster occurs, which is different from embodiment 1, mainly with reference to fig. 18 to 20.

Description of the structure

The configuration of the maintenance planning apparatus 200 will be described with reference to fig. 18.

The maintenance planning apparatus 200 further includes a phenomenon section 217.

The maintenance scheduling program also causes the computer to function as the event section 217.

Description of actions

The phenomenon coping method is explained with reference to fig. 19.

The phenomenon coping method is a part of the maintenance planning method.

In step S410, the phenomenon unit 217 determines whether or not a specific phenomenon has occurred.

The specific phenomenon is a phenomenon that the allowable value needs to be changed, that is, a phenomenon that the maintenance schedule needs to be changed. A particular phenomenon is a large-scale disaster.

The occurrence of a specific phenomenon is detected by a person or a sensor.

When the occurrence of a specific phenomenon is detected, an occurrence notification is input to maintenance planning apparatus 200.

When the occurrence notification is input to the maintenance scheduling apparatus 200, the phenomenon unit 217 determines that the specific phenomenon has occurred.

In the case where the specific phenomenon has occurred, the process proceeds to step S420.

In the case where no specific phenomenon occurs, the processing ends.

In step S420, adjustment unit 212 calculates a phenomenon deadline.

The phenomenon term date is a term date corresponding to the phenomenon tolerance.

The phenomenon tolerance is a tolerance used when a specific phenomenon occurs.

Specifically, the setting range of the allowable value is stored in the storage portion 291 in advance.

Then, adjustment unit 212 selects the upper limit allowable value from the setting range, and calculates the phenomenon deadline based on the upper limit allowable value and the risk value time series. The event deadline day is the day when the risk value reaches the upper-limit allowable value. In other words, the phenomenon term day is a day corresponding to a risk value of the same value as the upper limit allowable value. The storage 291 updates the stored allowable value to the upper limit allowable value and updates the stored term date to the phenomenon term date.

In step S430, the planning unit 213 determines a new maintenance work day based on the event due date.

Then, the planning unit 213 changes the maintenance operation day registered in the maintenance schedule data 120 to a new maintenance operation day.

The procedure for determining the new maintenance operation day is the same as the procedure for determining the maintenance operation day in step S150 (see fig. 5) of embodiment 1.

Supplement to embodiment 4

In the case where a large-scale disaster occurs, an emergency operation such as a recovery operation is frequently performed, and therefore, it is expected that personnel resources are insufficient.

On the other hand, even in the case of a large-scale disaster, the manager desires to use the equipment as much as possible.

Therefore, when a large-scale disaster occurs, the adjustment unit 212 automatically increases the allowable value. However, the adjustment unit 212 adjusts the increased allowable value to the upper limit of the allowable value that can be set in the normal state. That is, the allowable value is increased only when the allowable value is set low.

This makes it possible to suppress an increase in maintenance work while giving priority to emergency handling.

The increase of the allowable value in an emergency is indicated to the manager in advance. For example, the display unit 393 displays a notification screen indicating the application condition and the variation range on the display.

Depending on the use of the monitoring target 110, a priority maintenance work is required in an emergency. For example, in the case of a device in a medical institution, a preferential maintenance work is required in an emergency.

The allowable value may not be increased for such a monitoring target 110.

Further, the extent of increase of the allowable value may be set to be changed according to the scale of the disaster. For example, the allowable value corresponding to the disaster size is selected from a table in which the disaster size and the allowable value are associated with each other.

Thus, even in the case of emergency services, appropriate services can be provided in a form according to the intention of the administrator by management based on the risk value and the allowable value.

Further, when a large-scale disaster occurs, the operation of the monitoring target 110 is restricted according to the operation restriction (phenomenon operation restriction) for the disaster occurrence, and thus more appropriate service can be executed.

Further, the display unit 393 can display a setting screen for specifying the allowable value and the operation restriction to be applied in the emergency on the display. Then, as in the case of specifying the allowable value and the operation restriction at the normal time, the administrator can specify the allowable value and the operation restriction to be applied at the emergency time on the setting screen.

Other structure

Embodiment 4 can also be implemented in combination with embodiment 2 or embodiment 3. That is, the maintenance scheduling device 200 may include the limiting unit 214, the predicting unit 215, and the recommending unit 216.

Supplement to embodiments

The maintenance planning apparatus 200 obtains the frequency of occurrence of each failure mode using information on the deterioration states of a plurality of components constituting the apparatus grasped by remote monitoring. The maintenance planning system 100 multiplies the degree of influence obtained from the influence at the time of occurrence of each failure mode by the frequency of occurrence of each failure mode, calculates a risk value for each failure mode, and acquires the sum of these risk values.

The maintenance planning apparatus 200 compares a preset allowable risk value with a current risk total value of the equipment. Then, the maintenance scheduling device 200 corrects the schedule of the maintenance work for the equipment at the stage when the higher than allowable risk value is predicted.

The management terminal 300 displays the actual performance value of the risk total value and the predicted time-series change to the manager (owner including the equipment). The management terminal 300 can perform an operation of the manager to change the allowable risk value based on the displayed risk total value.

The maintenance planning apparatus 200 detects that the operation is performed, and corrects the plan of the maintenance work.

Basically, maintenance work is planned and carried out according to a preset allowable value. However, the administrator can provide maintenance services at a level required by the administrator by changing the allowable value according to the situation.

The maintenance planning apparatus 200 has a model of the progress of the deterioration of the elements obtained by the accelerated test with the passage of time or the number of times of use.

The maintenance planning apparatus 200 uses both the output of the model of progress of deterioration and the information of the remote monitoring result to estimate the deterioration state of the component.

In the state estimation of the component deterioration, the calculation result in the time series model estimated in advance by the accelerated test is integrated with the remote monitoring data and the access time check data, thereby enabling the state estimation with higher accuracy.

When it is estimated that the total risk is higher than the allowable value before the next scheduled visit, the maintenance planning apparatus 200 remotely sets the machine body so as to limit (or suppress) the operation (the number of times or the speed) of the apparatus (the whole or a part of the apparatus). Further, the maintenance scheduling apparatus 200 manages the content of the operation restriction.

The management terminal 300 displays the allowable contents of the operation restriction and the contents of the operation restriction to be actually applied to the manager. The management terminal 300 can execute an operation of rewriting the content of the allowable operation restriction.

When the component cannot be maintained to a predetermined next scheduled maintenance due to rapid degradation of the component or the like, the operation is restricted, thereby suppressing degradation of the component and avoiding additional maintenance. What operation restriction is allowed is set in advance at the time of combination. The range of motion limits also includes complete stops. However, when the operation restriction is actually applied, there is a possibility that the operation restriction is desired to be promptly released because of a large influence. Therefore, the administrator can easily change or release the content of the operation restriction.

The maintenance planning apparatus 200 extracts a condition that the number of times of performing the service is small, based on the operation history data of each operation target and each time period in the normal state of the target apparatus. Then, the maintenance scheduling apparatus 200 selects the object and content of the operation restriction, and causes the management terminal 300 to display the selected information as recommended content.

The maintenance planning apparatus 200 temporarily changes the allowable value of the risk set for each facility to a value higher than normal when a predetermined serious phenomenon occurs, such as a large-scale disaster.

When there is a high possibility of insufficient maintenance resources, such as in a large-scale disaster, the allowable risk value of each machine body is varied, thereby suppressing an increase in the amount of maintenance work. However, the maximum allowable risk of variability (the minimum limit at which the influence on the body of the user can be avoided) does not change, and the allowable value of the body, which is set to be low in the normal-time allowable value, is increased within a range up to the maximum value.

When a predetermined serious phenomenon occurs, for example, in the event of a large-scale disaster, the maintenance planning apparatus 200 temporarily changes the allowable contents of the operation restriction set for each device to a range wider than usual.

Elevators or escalators are the subject.

The maintenance planning apparatus 200 limits the number of times of opening and closing of the door of a specific floor within a certain period of time to a certain number of times or less, and does not perform service for calls of the number of times or more. Alternatively, the maintenance planning apparatus 200 allocates only the other bodies in the same group.

The maintenance scheduling device 200 suppresses the starting acceleration or the operating speed at the time of opening the door or closing the door at a specific floor or all floors.

The maintenance planning apparatus 200 changes the determination reference value in the apparatus for determining whether or not to travel based on the measurement setting value of the sensor for detecting a person in the car or the output of the sensor during all travel, travel in a specific direction, or service from a specific floor.

The hardware configuration of the maintenance planning apparatus 200 will be described with reference to fig. 20.

The maintenance planning apparatus 200 has a processing circuit 209.

The processing circuit 209 is hardware that realizes the screen section 211, the adjustment section 212, the planning section 213, the limiting section 214, the prediction section 215, the recommendation section 216, the phenomenon section 217, and the storage section 291.

The processing circuit 209 may be dedicated hardware or may be the processor 201 executing a program stored in the memory 202.

Where the processing circuitry 209 is dedicated hardware, the processing circuitry 209 is, for example, a single circuit, a complex circuit, a programmed processor, a parallel programmed processor, an ASIC, an FPGA, or a combination thereof.

An ASIC is an abbreviation for Application Specific Integrated Circuit (Application Specific Integrated Circuit), and an FPGA is an abbreviation for Field Programmable Gate Array (Field Programmable Gate Array).

The maintenance planning apparatus 200 may have a plurality of processing circuits instead of the processing circuit 209. The plurality of processing circuits share the role of the processing circuit 209.

In the maintenance scheduling apparatus 200, some of the functions may be implemented by dedicated hardware, and the remaining functions may be implemented by software or firmware.

Thus, the processing circuit 209 can be implemented in hardware, software, firmware, or a combination thereof.

The hardware configuration of the management terminal 300 will be described with reference to fig. 21.

The management terminal 300 has a processing circuit 309.

The processing circuit 309 is hardware that realizes the control unit 311 and the storage unit 391.

The processing circuit 309 may be dedicated hardware or may be the processor 301 executing a program stored in the memory 302.

Where the processing circuitry 309 is dedicated hardware, the processing circuitry 309 is, for example, a single circuit, a complex circuit, a programmed processor, a parallel programmed processor, an ASIC, an FPGA, or a combination thereof.

The management terminal 300 may have a plurality of processing circuits instead of the processing circuit 309. The plurality of processing circuits share the role of the processing circuit 309.

In the management terminal 300, some functions may be implemented by dedicated hardware, and the remaining functions may be implemented by software or firmware.

As such, the processing circuit 309 can be implemented in hardware, software, firmware, or a combination thereof.

The embodiments are illustrative of preferred embodiments and are not intended to limit the technical scope of the present invention. The embodiments may be partially implemented or implemented in combination with other embodiments. The procedure described with reference to the flowchart and the like may be changed as appropriate.

Description of the reference symbols

100: a maintenance planning system; 101: a network; 110: monitoring the object; 111: a sensor; 120: maintaining the planning data; 130: adjusting the picture; 131: a risk map; 132: a permissive flag; 133: a deadline token; 134: changing the interface; 140: limiting the picture; 141: a restriction interface; 200: a maintenance planning device; 201: a processor; 202: a memory; 203: a secondary storage device; 204: a communication device; 209: a processing circuit; 211: drawing a face part; 212: an adjustment part; 213: a planning unit; 214: a restricting section; 215: a prediction unit; 216: a recommendation unit; 217: a phenomenon part; 291: a storage unit; 292: a communication unit; 300: a management terminal; 301: a processor; 302: a memory; 303: a secondary storage device; 304: a communication device; 305: an input/output interface; 309: a processing circuit; 311: a control unit; 391: a storage unit; 392: a communication unit; 393: a display unit; 394: and a reception unit.

Claims

1. A maintenance planning system, the maintenance planning system having:

a display unit that displays an adjustment screen including a risk graph representing a time series of risk values, an allowable flag representing an allowable value, a deadline flag representing a deadline date when a risk value reaches the allowable value, and a change interface for changing the allowable value;

a receiving unit configured to receive a specified allowable value specified by the change interface;

an adjustment unit that calculates a new deadline based on the specified allowable value and the risk value time series; and

and a planning unit for determining a maintenance work day based on the new deadline.

2. The maintenance planning system of claim 1,

the maintenance planning system includes a screen unit that moves the permission flag of the adjustment screen according to the specified permission value and moves the deadline flag of the adjustment screen according to the new deadline.

3. The maintenance planning system according to claim 1 or 2,

the risk graph is a line graph of the risk,

the tolerance mark is a straight line which is,

the change interface is an up button for raising the permission flag and a down button for lowering the permission flag.

4. The maintenance planning system according to claim 1 or 2,

the planning unit selects a next visit date from maintenance plan data indicating a visit schedule, and determines a visit date before the new deadline as the maintenance work date when the next visit date is a date before the new deadline.

5. The maintenance planning system of claim 4, wherein,

the planning unit determines an additional visit date before the new deadline as the maintenance work date when the next visit date is a day after the new deadline.

6. The maintenance planning system of claim 4, wherein,

the maintenance scheduling system includes:

a limiting unit that limits an operation of the monitoring target when the next visit date is a date after the new deadline date; and

a prediction unit that calculates a time series of risk values after restriction when the next visit date is a date subsequent to the new deadline date,

the adjusting unit calculates a limited deadline based on the specified allowable value and the limited risk value time series,

the planning unit determines the maintenance work day based on the limited deadline day when the next visit day is a day after the new deadline day.

7. The maintenance planning system of claim 6,

the display unit displays a restriction screen including a restriction interface for specifying an operation restriction on the monitoring target,

accepting a specified action restriction specified through the restriction interface,

the restricting unit restricts the operation of the monitoring target in accordance with the designated operation restriction when the next visit date is a date subsequent to the new deadline date,

the prediction unit calculates the post-restriction risk value time series from the designated operation restriction when the next visit date is a date subsequent to the new deadline date.

8. The maintenance planning system of claim 7, wherein,

the restriction interface includes an interface for specifying recommended action restrictions.

9. The maintenance planning system of claim 8,

the maintenance scheduling system includes a recommendation unit configured to determine the recommended operation limit based on an operation history indicating a past operation state of the monitoring target.

10. A maintenance planning system according to any one of claims 6 to 9,

the monitoring object is an elevator or escalator.

11. The maintenance planning system according to any one of claims 1 to 10,

the maintenance planning system has a phenomenon part that determines whether a specific phenomenon has occurred,

the adjusting unit calculates a phenomenon deadline based on a phenomenon tolerance value and the risk value time series when the specific phenomenon occurs,

the planning unit changes the maintenance work day according to the event deadline day when a specific event occurs.

12. A maintenance planning method, wherein,

the display unit displays an adjustment screen including a risk graph showing a time series of risk values, an allowable flag showing an allowable value, a deadline flag showing a deadline date when the risk value reaches the allowable value, and a change interface for changing the allowable value,

receiving a specified allowable value specified through the change interface,

the adjusting section calculates a new deadline based on the specified allowable value and the risk value time series,

the planning unit determines a maintenance work day based on the new deadline.