Maintenance support system, maintenance support method, and program

Abstract

To provide a maintenance support system, maintenance support method, and program that can generate a maintenance plan with high feasibility.SOLUTION: A first DB (21) stores facility data related to an object facility (200). A second DB (22) stores maintenance data related to maintenance of the object facility (200). The facility data includes information related to operation history and maintenance history of the object facility (200). The maintenance data includes information related to work cost and personnel margin required for a maintenance work of the object facility (200). A processor calculates a survival expectancy of the object facility (200) at each future time point based on the facility data. The processor calculates a maintenance implementation score at each future time point from the survival expectancy, work cost, and personnel margin at each future time point, and selects implementation timing of the maintenance work so as to satisfy a plan generation criterion based on the calculated maintenance implementation score.SELECTED DRAWING: Figure 3

Description

Technical Field

[0001] The present disclosure relates to a maintenance support system, a maintenance support method, and a program for assisting in the implementation of facility maintenance.

Background Art

[0002] For example, Japanese Unexamined Patent Application Publication No. 2009-3517 (Patent Document 1) discloses a maintenance management support device for equipment constituting a plant. This maintenance management support device includes an input unit that receives calculation conditions including degrees of coincidence with respect to a plurality of evaluation items, a signal input unit that measures and inputs state signals in the plant, a calculation unit, and an output unit. The calculation unit estimates the deterioration state of the equipment based on the state signals, and evaluates a countermeasure plan including the content and timing of maintenance work with respect to a plurality of evaluation items based on the deterioration state and the calculation conditions. The output unit displays the calculation results regarding the countermeasure plan.

[0003] In the above configuration, the plurality of evaluation items include the cumulative cost (LCC) when the countermeasure plan is implemented, the failure stop probability, and an index representing the performance of the equipment. The cumulative cost is calculated as the sum of the operation cost that tends to increase with respect to the operation time and output of the equipment constituting the plant and the maintenance cost that increases with respect to the number of times of maintenance work. The failure stop probability is calculated as the probability of failure stop that decreases with respect to the maintenance cost. The index indicating the performance of the equipment is calculated as an index related to the ability of the target equipment that increases with respect to the maintenance cost.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] The maintenance management support device described in Patent Document 1 can output a countermeasure plan considering the cumulative cost, the probability of failure stop, and the performance of the equipment according to the deterioration state of the equipment constituting the plant.

[0006] However, on the other hand, depending on the personnel composition of the workers in the maintenance contractor who undertakes the maintenance work, there is a concern that it may be difficult to carry out the maintenance work at the time specified for the maintenance work specified in the countermeasure plan due to a shortage of personnel or the like. Also, depending on the proficiency of the workers engaged in the maintenance work, there is a concern that the content of the maintenance work specified in the countermeasure plan may not be completed on time. In these cases, there may be a divergence between the evaluation result by the calculation unit of the maintenance management support device and a plurality of actual evaluation items.

[0007] The present disclosure has been made to solve such problems, and an object of the present disclosure is to provide a maintenance support system, a maintenance support method, and a program capable of generating a highly feasible maintenance plan.

Means for Solving the Problems

[0008] A maintenance support system according to an embodiment is a system that supports the implementation of preventive maintenance for target equipment, and includes a first communication unit, a first database, a processor, and a memory that stores a program executed by the processor. The first communication unit communicates with the target equipment and a first communication terminal device that can be operated by a maintenance contractor for the target equipment. The first database stores equipment data related to the target equipment received by the first communication unit from the target equipment. The second database stores maintenance data related to the maintenance of the target equipment received by the first communication unit from the first communication terminal device. The equipment data includes information related to the operation history and maintenance history of the target equipment. The maintenance data includes information related to the work cost required for the maintenance work of the target equipment and the personnel margin of the workers engaged in the maintenance work. The processor calculates the survival expectancy value of the target equipment at each future time point based on the equipment data according to the program. The processor calculates the maintenance implementation score at each future time point from the survival expectancy value, work cost, and personnel margin at each future time point. The processor selects the implementation time of the maintenance work so as to satisfy a predetermined plan generation criterion based on the calculated maintenance implementation score.

Effect of the Invention

[0009] According to the present disclosure, a highly feasible maintenance plan can be generated.

Brief Description of the Drawings

[0010]

Figure 1

Figure 2

Figure 3

Figure 4

Figure 5

Figure 6

Figure 7

Figure 8

Figure 9

Figure 10

Figure 11

Figure 12

Figure 13

Figure 14

Figure 15

Figure 16

Figure 17

Figure 18

[0011] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals and their descriptions are not repeated.

[0012] [Embodiment 1] [Application Example of Maintenance Support System] FIG. 1 is a diagram for explaining an application example of a maintenance support system according to Embodiment 1. The maintenance support system 100 according to Embodiment 1 is a system for supporting the implementation of preventive maintenance of a target facility 200. The target facility 200 is, for example, building facilities such as air conditioning facilities and lighting facilities. The operation of these building facilities is usually managed by a building operation management system that performs building operation management tasks.

[0013] As shown in FIG. 1, the maintenance support system 100 according to Embodiment 1 exchanges various signals and data with the target facility 200 and communication terminal devices 300 and 400 via a communication network NW such as the Internet.

[0014] The target facility 200 includes a controller 210, an electric device 220, and a sensor 230. The controller 210 is connected to the electric device 220 and the sensor 230. The electric device 220 is an electric device installed in the building and includes, for example, air conditioning devices and lighting devices. The sensor 230 is various sensors for detecting the operating state of the electric device 220 and includes, for example, an illuminance sensor, a temperature and humidity sensor, and a power meter.

[0015] The controller 210 controls the startup / stop of the connected electric device 220 and the operation of the electric device 220. Further, the controller 210 monitors the measured values of the various sensors 230 connected thereto.

[0016] In addition, the controller 210 periodically acquires data related to the target facility 200 (hereinafter, also referred to as "facility data") based on the operating state of the electric device 220 and the measured values of the sensor 230. The facility data includes information such as the specifications of the target facility 200, the operation history of the target facility 200, the measured values of the sensor 230 during the operation of the target facility 200, and the maintenance history of the target facility 200.

[0017] The information regarding the specifications of the target facility 200 includes information such as the manufacturer, model name, type, and rated output of the electrical equipment 220. The information regarding the operation history of the target facility 200 includes information such as the operation time, stop time, cumulative operation time, cumulative operation count, and power consumption of the electrical equipment 220. Note that the cumulative operation time and the cumulative operation count are the respective accumulations of the operation time and the operation count since the electrical equipment 220 started operation. The information regarding the measured values of the sensor 230 includes the time-series data of the measured values acquired at a predetermined sampling period. The information regarding the maintenance history of the target facility 200 includes information regarding the timing of inspections, repairs, and component replacements of the electrical equipment 220.

[0018] The controller 210 transmits the facility data acquired periodically to the maintenance support system 100 via the communication network NW. The maintenance support system 100 stores the facility data received from the controller 210 in a database (not shown).

[0019] The communication terminal device 300 can be operated by a maintenance contractor who performs maintenance on the target facility 200. The communication terminal device 300 is composed of a terminal device such as a PC (Personal Computer) or a PDA (Personal Digital Assistant) that can be connected to the communication network NW. The installation location of the communication terminal device 300 is not particularly limited. The communication terminal device 300 may be a mobile terminal (such as a smartphone or a tablet) owned by the maintenance contractor.

[0020] The communication terminal device 300 mainly manages data regarding the maintenance of the target facility 200 (hereinafter, also referred to as "maintenance data"). The maintenance data includes information such as the content of the maintenance work (inspection, repair, and component replacement) of the target facility 200, as well as the time and cost required for the maintenance work. The content of the maintenance work of the target facility 200 includes information such as the types (identification names, etc.) of components that require inspection, repair, or replacement, the number of workers assigned to the maintenance work, and the proficiency levels of each worker. The maintenance support system 100 stores the maintenance data received from the communication terminal device 300 in a database (not shown).

[0021] The communication terminal device 400 can be operated by a facility owner (e.g., the owner of a building) who owns the target facility 200. The facility owner has concluded a maintenance contract with a maintenance contractor. The communication terminal device 400 is composed of a terminal device such as a PC or a PDA that can be connected to the communication network NW. The installation location of the communication terminal device 400 is not particularly limited. The communication terminal device 400 may be a mobile terminal (such as a smartphone or a tablet) owned by the facility owner.

[0022] The maintenance support system 100 generates a maintenance plan for the target facility 200 by using the facility data and maintenance data collected from the target facility 200 and the communication terminal device 300 respectively. The maintenance support system 100 will be described in detail later. The communication terminal device 400 receives information regarding the maintenance plan generated by the maintenance support system 100 via the communication network NW. The communication terminal device 400 presents the maintenance plan of the target facility 200 to the facility owner based on the received information.

[0023] <Hardware Configuration of the Maintenance Support System> FIG. 2 is a diagram showing an example of the hardware configuration of the maintenance support system 100. As shown in FIG. 2, the maintenance support system 100 is realized by a device having a function of communicating with external devices including the target facility 200 and the communication terminal devices 300 and 400 and an arithmetic function. The maintenance support system 100 can be realized, for example, by a general server.

[0024] The maintenance support system 100 includes a CPU (Central Processing Unit) 101, a RAM (Random Access Memory) 102, a ROM (Read Only Memory) 103, an I / F (Interface) device 104, and a storage device 105. The CPU 101, the RAM 102, the ROM 103, the I / F device 104, and the storage device 105 exchange various data through the communication bus 106.

[0025] The CPU 101 expands and executes the program stored in the ROM 103 in the RAM 102. The program stored in the ROM 103 describes the processes executed by the maintenance support system 100. Note that in FIG. 2, a configuration in which the CPU 101 is singular is illustrated, but the maintenance support system 100 may have a configuration with a plurality of CPUs.

[0026] The I / F device 104 is an input / output device for exchanging signals and data with external devices including the target facility 200 and the communication terminal devices 300 and 400. The I / F device 104 receives facility data from the target facility 200. Also, the I / F device 4 receives maintenance data from the communication terminal device 300. The I / F device 4 transmits information regarding the maintenance plan for the target facility 200 formulated by the CPU 101 to the communication terminal device 400.

[0027] The storage device 105 is a storage for storing various information, and stores various information for formulating the maintenance plan for the target facility 200. The various information includes the above-described facility data and maintenance data, as well as a plan generation criterion that serves as a standard for generating the maintenance plan.

[0028] <Functional Configuration of the Maintenance Support System> FIG. 3 is a block diagram showing the functional configuration of the maintenance support system 100 according to Embodiment 1. As shown in FIG. 3, the maintenance support system 100 includes a communication unit 10, a data management unit 20, a survival expectancy calculation unit 30, a maintenance plan generation unit 40, and a communication unit 50. These functions are realized, for example, when the CPU 101 executes the program stored in the ROM 103. Note that some or all of these functions may be configured to be realized by hardware.

[0029] The communication unit 10 communicates with the target facility 200 and the communication terminal device 300. The communication unit 10 receives facility data from the target facility 200 at predetermined intervals. As described above, the facility data includes information such as the specifications of the electrical equipment 220 included in the target facility 200, the operation history, the measured values of the sensors 230 during operation, and the maintenance history. The communication unit 10 corresponds to an embodiment of the "first communication unit".

[0030] In addition, the communication unit 10 receives maintenance data from the communication terminal device 300 at predetermined intervals. As described above, the maintenance data includes information such as the content of the maintenance of the target facility 200, and the time and cost spent on the maintenance. The communication unit 10 transfers the received facility data and maintenance data to the data management unit 20.

[0031] The data management unit 20 manages the signals and data exchanged between the maintenance support system 100 and external devices. The data management unit 20 includes an equipment DB 21 and a work information DB 22. The equipment DB 21 stores the equipment data of the target facility 200. The work information DB 22 stores the maintenance data of the target facility 200. Each of these DBs is stored in the storage device 105 (Figure 2) of the maintenance support system 100. The equipment DB 21 corresponds to an embodiment of the "first database", and the work information DB 22 corresponds to an embodiment of the "second database".

[0032] The survival expectancy calculation unit 30 calculates the survival expectancy P of the target facility 200 using the equipment data stored in the equipment DB 21. In this specification, the "survival expectancy P(t)" means the probability (unit: %) that the target facility 200 is surviving (not malfunctioning) at a certain time point t.

[0033] The survival expectancy calculation unit 30 calculates the survival expectancy P at a future time point t starting from the current time. The survival expectancy P can be calculated using existing failure prediction techniques based on the information regarding the operation history and the maintenance history of the target facility 200 included in the equipment data.

[0034] For example, the survival expected value P of a fan installed in an air conditioning facility varies according to its operating rotation speed. To calculate the survival expected value P of the fan, first, based on the cumulative operating time of the air conditioning facility, the set temperature of the air conditioning facility, the actual values of the air volume and the outside air temperature included in the operation history of the air conditioning facility, etc., the temporal change in the operating rotation speed of the fan up to the present time is calculated. Next, assuming that the air conditioning facility is operated under the same operating conditions as before, based on the calculated temporal change in the operating rotation speed of the fan, the temporal change in the operating rotation speed of the fan in the future is predicted. Then, based on the predicted value of the operating rotation speed at a certain future time point t, the survival expected value P of the fan at the time point t is calculated.

[0035] The maintenance plan generation unit 40 receives the survival expected value P(t) of the target facility 200 from the survival expected value calculation unit 30 and receives maintenance data from the work information DB 22. The maintenance plan generation unit 40 uses these pieces of information to generate a maintenance plan for the target facility 200. The maintenance plan includes the timing for performing the maintenance work on the target facility 200 and information regarding the personnel composition of the workers who perform the maintenance work. The generation of the maintenance plan in the maintenance plan generation unit 40 will be described in detail later.

[0036] The communication unit 50 communicates with the communication terminal device 400. The communication unit 50 transmits the generated maintenance plan for the target facility 200 to the communication terminal device 400. The communication terminal device 400 presents the maintenance plan for the target facility to the facility owner based on the received information. The communication unit 50 corresponds to an embodiment of the "second communication unit".

[0037] <Operation of the Maintenance Support System> FIG. 4 is a flowchart showing an example of the processing executed by the maintenance support system 100 according to Embodiment 1. A series of processing shown in this flowchart is executed when a predetermined condition is satisfied (for example, every predetermined period). Each step is realized by software processing by the CPU 101, but may also be realized by hardware (electric circuit) arranged in the maintenance support system 100. Hereinafter, the steps are abbreviated as "S".

[0038] As shown in FIG. 4, in S10, the maintenance support system 100 stores the equipment data received from the target equipment 200 in the equipment DB 21. The equipment data of the target equipment 200 is accumulated in the equipment DB 21.

[0039] In S20, the maintenance support system 100 stores the maintenance data received from the communication terminal device 300 in the work information DB 22. The maintenance data is accumulated in the work information DB 22.

[0040] In S30, the maintenance support system 100 calculates the survival expectancy value P of the target equipment 200 using the equipment data accumulated in the equipment DB 21. In S30, based on the information regarding the operation history and the maintenance history of the target equipment 200 included in the equipment data, the operation state of the target equipment 200 at a certain future time point t is predicted. Then, from the predicted operation state at the time point t, the survival expectancy value P at the time point t is calculated.

[0041] FIG. 5 is a diagram showing an example of the survival expectancy value P of the target equipment 200 and the maintenance data. FIG. 5 shows the temporal change of the survival expectancy value P from the current time to a certain future time. In FIG. 5, the temporal change of the survival expectancy value P from the first ten days of January (1B) of a certain future year to the first ten days of January (1B) of the following year is shown. Note that the numbers at each time point indicate "months", the English letter "B" indicates the first ten days of that month, the English letter "M" indicates the middle ten days of that month, and the English letter "E" indicates the last ten days of that month.

[0042] FIG. 5 further shows the temporal change of the maintenance data from the first ten days of January (1B) of a certain future year to the first ten days of January (1B) of the following year. The maintenance data at each time point includes the work cost C, which is the cost required when performing maintenance work at that time, and the personnel margin N, which represents the margin of the workers at that time.

[0043] The working cost C and the personnel margin N at each point in time can be predicted, for example, by a maintenance contractor based on the past performance of maintenance work. Also, the maintenance contractor can estimate the personnel margin N from the number of workers that can be assigned to the maintenance work at each point in time based on the personnel plan. Note that for the personnel margin N, a negative value indicates the number of workers lacking, and a positive value indicates the number of surplus workers.

[0044] FIG. 6 is a graph showing the time evolution of the survival expectancy P shown in FIG. 5. FIG. 7 is a graph showing the time evolution of the working cost C shown in FIG. 5. FIG. 8 is a graph showing the time evolution of the personnel margin N shown in FIG. 5.

[0045] As shown in FIG. 6, the survival expectancy P of the target facility 200 monotonically decreases over time. However, the rate at which the survival expectancy P decreases varies depending on the operating state of the target facility 200 at each point in time. In the example of FIG. 6, the survival expectancy P gradually decreases during the period from January to May and the period from August to December, while the survival expectancy P sharply decreases during the period from May to August.

[0046] On the other hand, as shown in FIGS. 7 and 8, the working cost C and the personnel margin N increase or decrease depending on the time. For the facility owner, in order to suppress the cost of maintenance, it is desirable to carry out maintenance work during a period when the working cost C is low. However, if the survival expectancy P is low during a period when the working cost C is low, the risk of a failure occurring in the target facility 200 before the maintenance work is carried out increases, which may impede the operation of the building equipped with the target facility 200. Conversely, if the survival expectancy P is high during a period when the working cost C is low, there is a concern that unnecessary costs may be incurred by replacing the still operable electrical equipment 220 and its parts.

[0047] Also, when the personnel margin N shows a negative value at the time when maintenance work is scheduled to be carried out, it is feared that the maintenance work cannot be carried out due to a shortage of workers, and the implementation of the maintenance work may be delayed compared to the original plan. Since the survival expectancy value P decreases due to the delay in the implementation of the maintenance work, the risk that the target facility 200 breaks down before the maintenance work is carried out becomes high. Also, due to the delay in the implementation of the maintenance work, the work cost C may increase and become higher than the initial estimate of the work cost.

[0048] To eliminate such concerns, the maintenance support system 100 according to Embodiment 1 generates a maintenance plan for the target facility 200 in comprehensive consideration of the survival expectancy value P of the target facility 200, the work cost C required for the maintenance work, and the personnel margin N for the maintenance work. FIG. 9 is a flowchart showing the detailed processing procedure of S40 in FIG. 4.

[0049] As shown in FIG. 9, in the process of generating a maintenance plan (S40), first in S401, the maintenance support system 100 calculates a maintenance execution score S based on the survival expectancy value P, the work cost C, and the personnel margin N. The maintenance execution score S is defined by the following formula (1). S = (100 - P) + C - N ···(1) The (100 - P) in the first term on the right side of formula (1) represents the probability (failure risk) that the target facility 200 has failed at a certain point in time. That is, the maintenance execution score S is defined as the sum of the probability (100 - P) that the target facility 200 has failed, the work cost C, and the product of the personnel margin N and (-1).

[0050] In the example of FIG. 5, at each point in time during the period from the first ten days of January (1B) of a certain year to the first ten days of January (1B) of the following year, the maintenance execution score S at that point in time is calculated by substituting the survival expectancy value P, the work cost C, and the personnel margin N at that point in time into formula (1).

[0051] FIG. 10 is a diagram showing an example of the maintenance execution score S of the target facility 200. FIG. 10 shows the temporal change of the maintenance execution score S calculated from the survival expectancy P, the work cost C, and the personnel margin N shown in FIG. 5.

[0052] For example, for mid-April (4M), the survival expectancy P = 95%, the work cost C = 80,000 yen, and the personnel margin N = 2 people. Therefore, the maintenance execution score S is S=(100 - 95)+8 - 2 = 11. Also, for mid-July (7M), the survival expectancy P = 42%, the work cost C = 230,000 yen, and the personnel margin N = -4 people. Therefore, the maintenance execution score S is S=(100 - 42)+23 - (-4)=85.

[0053] FIG. 11 is a graph showing the temporal change of the maintenance execution score S shown in FIG. 10. The maintenance execution score S varies according to the survival expectancy P, the work score C, and the personnel margin N. A decrease in the survival expectancy P, that is, an increase in the failure risk, acts in the direction of increasing the maintenance execution score S. An increase in the work cost C acts in the direction of increasing the maintenance execution score S. A decrease in the personnel margin N acts in the direction of increasing the maintenance execution score S. FIG. 10 shows the amount of change in the maintenance execution score S from the previous time point at each time point. A negative amount of change indicates that the maintenance execution score S has decreased from the previous time point, and a positive amount of change indicates that the maintenance execution score S has increased from the previous time point. While the survival expectancy P decreases monotonically, the work score C and the personnel margin N increase and decrease, so the amount of change in the maintenance execution score S fluctuates between positive and negative.

[0054] The maintenance support system 100 selects the timing for performing the maintenance work of the target facility 200 based on the temporal change of the maintenance execution score S in S402 of FIG. 9. In S402, the maintenance support system 100 selects the timing for performing the maintenance work based on a preset plan generation criterion.

[0055] The planning generation criteria can be arbitrarily set by the equipment owner or the like. In a certain situation, the planning generation criteria can be set so that maintenance work is carried out by highly skilled workers at the time when the maintenance implementation score S is minimized during the period when the survival expectancy P is 30% or more and 50% or less.

[0056] In the example of FIG. 10, the period during which the survival expectancy P is 30% or more and 50% or less is the period from the first ten days of July (7B) to the last ten days of October (10E). The times when the maintenance implementation score S is minimized during this period are the last ten days of September (9E), the first ten days of October (10B), and the middle ten days of October (10M). Therefore, the maintenance support system 100 selects the period from the last ten days of September (9E) to the middle ten days of October (10M) as the time for carrying out the maintenance work.

[0057] In another situation, the planning generation criteria can be set so that maintenance work is carried out immediately before the time when the positive change amount (increase amount) of the maintenance implementation score S is maximized and when there is a margin in the number of workers.

[0058] In the example of FIG. 10, the positive change amount (increase amount) of the maintenance implementation score S is maximized in the first ten days of July (7B). The time when the personnel margin N is 0 or more immediately before the first ten days of July (7B) is the first ten days of June (6B). Therefore, the maintenance support system 100 selects the first ten days of June (6B) as the time for carrying out the maintenance work.

[0059] When the time for carrying out the maintenance work is selected in S402, subsequently, the maintenance support system 100 generates a maintenance plan based on the planning generation criteria by S403. In S403, the schedule for carrying out the maintenance work is determined, and the workers for carrying out the maintenance work are selected, etc.

[0060] For generating a maintenance plan, the maintenance data stored in the work information DB 22 is used. Based on the worker information regarding the workers included in the maintenance data, a maintenance plan is generated. FIG. 12 is a diagram showing an example of worker information. FIG. 12 shows information regarding the proficiency levels of the workers engaged in maintenance work. On the left side of FIG. 12, information regarding the proficiency levels of the workers assignable to each working day during the period from late September (9E) to mid-October (10M) is shown. On the right side of FIG. 12, information regarding the proficiency levels of the workers assignable to each working day during the period of early June (6B) is shown.

[0061] In the example of FIG. 12, at least one of workers A to D is assigned to each working day. Which worker is assigned to each working day can be set by the maintenance contractor based on a personnel plan or the like. The proficiency levels of workers A to D are set such that the higher the proficiency level, the higher the numerical value. Worker B has the highest proficiency level, and worker C has the lowest proficiency level.

[0062] In S403, the maintenance support system 100 determines the schedule for performing the maintenance work based on the execution time of the maintenance work selected in S402 and the information regarding the proficiency level of the workers at the execution time. For example, assume a case where the planning generation criteria are set such that the maintenance work is to be performed by a highly proficient worker at the time when the maintenance execution score S is minimized during the period when the survival expectancy value P is 30% or more and 50% or less. In this case, in response to the period from late September (9E) to mid-October (10M) being selected as the execution time of the maintenance work by S402, the maintenance support system 100 refers to the information regarding the proficiency level of the workers during the period (left side of FIG. 12) to generate a maintenance plan. Specifically, the maintenance support system 100 identifies the working days (September 27, September 28, October 4, and October 10) to which the most highly proficient worker B is assigned, and based on the identified working days, determines the schedule for performing the maintenance work on the target equipment 200. According to this, it becomes possible to perform the maintenance work on the target equipment 200 by a highly proficient worker (worker B).

[0063] Alternatively, assume a case where the planning generation criteria are set so that maintenance work is carried out at a time just before the period when the positive change amount (increase amount) of the maintenance execution score S is maximized and when there is a surplus of workers. In this case, in response to the selection of the first ten days of June (6B) as the maintenance work execution period by S402, the maintenance support system 100 generates a maintenance plan with reference to information regarding the proficiency of workers during that period (right side of FIG. 12). Specifically, the maintenance support system 100 determines the schedule for carrying out the maintenance work on the target facility 200 based on the workday (June 2) with the largest number of workers assigned. Although both workers A and C assigned to June 2 have low proficiency, since a plurality of workers are assigned, the possibility of carrying out the maintenance work according to the determined work schedule is increased.

[0064] Note that the calculation formula (formula (1)) of the above-described maintenance execution score S and the planning generation criteria can be appropriately changed by the user of the maintenance support system 100 (for example, the facility owner, etc.). The set calculation formula and planning generation criteria can be stored in the storage device 105 of the maintenance support system 100 or a dedicated DB.

[0065] When a maintenance plan is generated according to the flowchart shown in FIG. 9, the maintenance support system 100 proceeds to S50 in FIG. 4 and transmits information regarding the generated maintenance plan to the communication terminal device 400 via the communication unit 50. The communication terminal device 400 presents the generated maintenance plan to the facility owner by displaying the received information on the display.

[0066] As described above, according to the maintenance support system 100 according to Embodiment 1, the maintenance execution score S is calculated based on the survival expectancy P of the target facility, the work cost C required for the maintenance work, and the personnel surplus margin N of the workers who carry out the maintenance work, and based on the calculated maintenance execution score S, a maintenance plan for the target facility is generated so as to satisfy the planning generation criteria.

[0067] The conservative implementation score S reflects the failure risk of the target facility, as well as the work cost and personnel margin of the maintenance work. Therefore, by using the conservative implementation score S to generate a maintenance plan, it is possible to select an implementation time when the maintenance work can be reliably carried out after comparing and weighing the failure risk and work cost of the target facility. As a result, a highly feasible maintenance plan can be generated.

[0068] In addition, the plan generation criteria can include conditions related to the proficiency of the workers who perform the maintenance work, in addition to the conditions for the conservative implementation score S. Therefore, a maintenance plan that conforms to the intention of the facility owner can be generated.

[0069] [Embodiment 2] FIG. 13 is a block diagram showing the functional configuration of the maintenance support system 100 according to Embodiment 2. The maintenance support system 100 according to Embodiment 2 differs from the maintenance support system 100 according to Embodiment 1 shown in FIG. 3 in the configuration of the data management unit 20. As shown in FIG. 13, the data management unit 20 according to Embodiment 2 is obtained by adding a weight DB 23 to the data management unit 20 according to Embodiment 1.

[0070] The weight DB 23 stores weight data indicating weights for the survival expectancy value P and the work cost C. The weight data includes a weight coefficient α that defines the relative importance of the survival expectancy value P and a weight coefficient β that defines the relative importance of the work cost C. The facility owner can input the weight data by operating the communication terminal device 400. The weight DB 23 corresponds to an example of the "third database".

[0071] The conservative plan generation unit 40 receives the survival expectancy value P of the target facility 200 from the survival expectancy value calculation unit 30, receives maintenance data from the work information DB 22, and receives weight data from the weight DB 23. The conservative plan generation unit 40 generates a maintenance plan for the target facility 200 using this information. The conservative plan generation unit 40 calculates a maintenance execution score S based on the survival expectancy value P, the work cost C, and the personnel margin N according to the procedure shown in the flowchart of FIG. 9, and generates a maintenance plan so as to satisfy the plan generation criteria based on the calculated maintenance execution score S.

[0072] In Embodiment 2, the conservative plan generation unit 40 uses weight data in calculating the maintenance execution score S. The maintenance execution score S is defined by the following formula (2). S = α×(100 - P)+β×C - N ···(2) The probability (100 - P) that the target facility 200 of the first term on the right side of formula (2) has failed is multiplied by the weight coefficient α, and the work cost C of the second term on the right side is multiplied by the weight coefficient β. However, α and β are values greater than 0 and less than 1, and α + β = 1.

[0073] FIG. 14 is a diagram showing an example of the maintenance execution score S of the target facility 200. FIG. 14 shows the same survival expectancy value P, work cost C, and personnel margin N as in FIG. 5, and the time transition of the maintenance execution score S calculated based on these.

[0074] In the example of FIG. 14, at each time point in the period from the beginning of January (1B) of a certain year to the beginning of January (1B) of the following year, the survival expectancy value P, work cost C, and personnel margin N at that time point are substituted into formula (2), whereby the maintenance execution score S at that time point is calculated. The maintenance execution score S includes the maintenance execution score S when α = 0.7 and β = 0.3, and the maintenance execution score S when α = 0.2 and β = 0.8.

[0075] For example, when explaining the middle of April (4M), since the survival expectancy value P = 95%, the operation cost C = 80,000 yen, and the personnel margin N = 2 people, the maintenance implementation score S is given by S = α×(100 - 95)+β×8 - 2. When α = 0.7 and β = 0.3, S = 3.9, and when α = 0.2 and β = 0.8, S = 5.4.

[0076] Also, when explaining the middle of July (7M), since the survival expectancy value P = 42%, the operation cost C = 230,000 yen, and the personnel margin N = -4 people, the maintenance implementation score S is given by S = α×(100 - 42)+β×23 - (-4). When α = 0.7 and β = 0.3, S = 51.5, and when α = 0.2 and β = 0.8, S = 34.

[0077] In this way, for one set of the survival expectancy value P, the operation cost C, and the personnel margin N, by changing the magnitudes of the weighting coefficients α and β, the magnitude of the maintenance implementation score S obtained from the set also changes. The equipment owner can set the weighting coefficients α and β according to whether they prioritize the failure risk or the operation cost of the target equipment 200. For example, when prioritizing the failure risk of the target equipment 200 over the operation cost, the weighting coefficients α and β can be set such that α>β. Conversely, when prioritizing the operation cost over the failure risk of the target equipment 200, the weighting coefficients α and β can be set such that α<β.

[0078] Note that as shown in FIG. 14, when the weighting coefficients α and β are set such that α>β, as the survival expectancy value P decreases, that is, as the failure risk increases, the maintenance implementation score S increases. On the other hand, when the weighting coefficients α and β are set such that α<β, as the operation cost C increases, the maintenance implementation score S increases.

[0079] The maintenance support system 100 selects the timing for performing maintenance work so as to meet preset plan generation criteria. Assume a case where the plan generation criteria are set such that maintenance work is carried out by highly skilled workers at the time when the maintenance implementation score S is minimized during the period when the survival expectancy value P is 30% or more and 50% or less.

[0080] In the example of FIG. 14, the period during which the survival expectancy value P is 30% or more and 50% or less is the period from early July (7B) to late October (10E). When α = 0.7 and β = 0.3, the time when the maintenance implementation score S is minimized is early July (7B). Therefore, the maintenance support system 100 selects early July (7B) as the timing for performing maintenance work. That is, when the failure risk is regarded as more important than the work cost, the time with the lowest failure risk among the periods when the survival expectancy value P is 30% or more and 50% or less is selected as the timing for performing maintenance work.

[0081] On the other hand, when α = 0.2 and β = 0.8, the times when the maintenance implementation score S is minimized are early October (10B) and mid - October (10M). Therefore, the maintenance support system 100 selects early October (10B) and mid - October (10M) as the timing for performing maintenance work. That is, when the work cost is regarded as more important than the failure risk, the time with the lowest work cost among the periods when the survival expectancy value P is 30% or more and 50% or less is selected as the timing for performing maintenance work.

[0082] As described above, according to the maintenance support system according to Embodiment 2, it is possible to generate a maintenance plan that appropriately responds to the content that the facility owner values (the failure risk of the target facility or the cost of maintenance work).

[0083] [Embodiment 3] FIG. 15 is a block diagram showing the functional configuration of the maintenance support system 100 according to Embodiment 3. The maintenance support system 100 according to Embodiment 3 differs from the maintenance support system 100 according to Embodiment 1 shown in FIG. 3 in the configuration of the data management unit 20. As shown in FIG. 15, the data management unit 20 according to Embodiment 3 is obtained by adding a component DB 24 to the data management unit 20 according to Embodiment 1.

[0084] Component data regarding components used for the maintenance work of the target facility 200 is stored in the component DB 24. The component data includes inventory information of components, manufacturing plans of components, and information regarding the prices of components. The component manufacturer can input the component data by operating the communication terminal device 500. The communication terminal device 500 is composed of a terminal device such as a PC or a PDA that can be connected to the communication network NW. The communication terminal device 500 may be a mobile terminal (such as a smartphone or a tablet) owned by the component manufacturer. The component DB 24 corresponds to an example of the "fourth database".

[0085] The maintenance plan generation unit 40 receives the survival expectancy value P of the target facility 200 from the survival expectancy calculation unit 30, receives maintenance data from the work information DB 22, and receives component data from the component DB 24. The maintenance plan generation unit 40 generates a maintenance plan for the target facility 200 using these pieces of information. The maintenance plan generation unit 40 calculates a maintenance execution score S based on the survival expectancy value P, the work cost C, and the personnel margin N according to the procedure shown in the flowchart of FIG. 9, and generates a maintenance plan based on the plan generation criteria using the calculated maintenance execution score S.

[0086] In Embodiment 3, the maintenance plan generation unit 40 uses component data in the calculation of the maintenance execution score S. The maintenance execution score S is defined by the following formula (3). S = (100 - P) + K × C - N ···(3) The second term on the right side of Equation (2) represents the product of the operation cost C and the component price increase rate K. In this specification, "component price increase rate K(t)" means the ratio (unit: %) of the price of a component at a certain point in time t to the reference price of the component. The component price increase rate K at a future point in time t can be calculated by predicting the price of the component at that point in time t from the inventory information, manufacturing plan, and price-related information of the components included in the component data, and comparing the predicted price of the component with the reference price.

[0087] When the price of a component rises above the reference price, the component price increase rate K shows a value higher than 100%. When the price of a component falls below the reference price, the component price increase rate K shows a value lower than 100%. The second term on the right side of Equation (3) corresponds to adding such fluctuations in the price of components on top of the operation cost C.

[0088] Figure 16 is a diagram showing an example of the survival expectancy P of the target facility 200, maintenance data, and the component price increase rate K. Figure 16 shows the time progression of the component price increase rate K, along with the survival expectancy P, operation cost C, and personnel margin N from the current time to a future point in time.

[0089] In the example of Figure 16, at each point in time during the period from the beginning of January (1B) of a certain year to the beginning of January (1B) of the following year, by substituting the survival expectancy P, operation cost C, personnel margin N, and component price increase rate K at that point in time into Equation (3), the maintenance implementation score S at that point in time is calculated. Figure 16 shows the time progression of the calculated maintenance implementation score S.

[0090] According to Figure 16, it can be seen that at two points in time (for example, the end of January (1E) and the beginning of February (2B)) where the survival expectancy P and the operation cost C are equal, the maintenance implementation score S at the point in time with a higher component price increase rate K is larger than the maintenance implementation score S at the point in time with a lower component price increase rate K.

[0091] The maintenance support system 100 selects the timing for performing maintenance work so as to meet preset plan generation criteria. Assume a case where the plan generation criteria are set such that maintenance work is to be carried out by a highly skilled worker at the time when the maintenance execution score S is minimized during a period when the survival expectancy value P is 30% or more and 50% or less.

[0092] In the example of FIG. 16, the period during which the survival expectancy value P is 30% or more and 50% or less is the period from the first ten days of July (7B) to the last ten days of October (10E). The time when the maintenance execution score S is minimized during this period is the first ten days of July (7B). Therefore, the maintenance support system 100 selects the first ten days of July (7B) as the timing for performing maintenance work.

[0093] Note that, as described in Embodiment 1, when the maintenance execution score S is calculated without including the component price increase rate K, based on the above plan generation criteria, the period from the last ten days of September (9E) to the middle ten days of October (10M) is selected as the timing for performing maintenance work. On the other hand, in Embodiment 3, the first ten days of July (7B), where the component price increase rate K is lower than that during this period, is selected as the timing for performing maintenance work.

[0094] Thus, according to the maintenance support system 100 according to Embodiment 3, it is possible to generate a maintenance plan for the target facility considering fluctuations in component prices.

[0095] [Embodiment 4] FIG. 17 is a block diagram showing the functional configuration of the maintenance support system 100 according to Embodiment 4. The maintenance support system 100 according to Embodiment 4 differs from the maintenance support system 100 according to Embodiment 1 shown in FIG. 3 in the configuration of the data management unit 20. As shown in FIG. 17, the data management unit 20 according to Embodiment 4 is obtained by adding a budget DB25 to the data management unit 20 according to Embodiment 1.

[0096] Budget DB25 stores budget data regarding the budget available for maintenance work. The budget data includes information indicating the temporal transition of the budget from the current time to a future time. The facility owner can input the budget data by operating the communication terminal device 400. Budget DB25 corresponds to an embodiment of the "fifth database".

[0097] The maintenance plan generation unit 40 receives the survival expectancy value P of the target facility 200 from the survival expectancy calculation unit 30, receives maintenance data from the work information DB22, and receives budget data from the budget DB25. The maintenance plan generation unit 40 generates a maintenance plan for the target facility 200 using this information.

[0098] In a certain aspect, when the planning generation criteria are set such that maintenance work is to be carried out by highly skilled workers at the time when the maintenance implementation score S is minimized during the period when the survival expectancy value P is 30% or more and 50% or less, the maintenance plan generation unit 40 may be configured to select, as the maintenance work execution time, a time when the work cost C does not exceed the budget among the maintenance work execution times selected based on the said planning generation criteria.

[0099] In another aspect, when calculating the maintenance implementation score S using the weight data as described in Embodiment 2, when the work cost C at the maintenance work execution time selected based on the planning generation criteria exceeds the budget, the maintenance plan generation unit 40 may be configured to change the weight coefficient β of the work cost C to a larger value and then recalculate the maintenance implementation score S.

[0100] Thus, according to the maintenance support system 100 according to Embodiment 4, it is possible to generate a maintenance plan for the target facility in consideration of the budget available for maintenance work.

[0101] [Embodiment 5] FIG. 18 is a block diagram showing the functional configuration of the maintenance support system 100 according to Embodiment 5. The maintenance support system 100 according to Embodiment 5 differs from the maintenance support system 100 according to Embodiment 1 shown in FIG. 3 in the configuration of the data management unit 20. As shown in FIG. 18, the data management unit 20 according to Embodiment 5 is obtained by adding a maintenance management DB 26 to the data management unit 20 according to Embodiment 1.

[0102] The maintenance management DB 26 stores maintenance plan data regarding the maintenance plan of the target facility 200. The maintenance plan data includes, based on the information regarding the maintenance plan received from the maintenance plan generation unit 40, the schedule of maintenance work designed by the facility owner, etc. In the schedule of maintenance work, the schedule for implementing the maintenance work and the workers assigned to each working day are set. The facility owner can input the maintenance plan data by operating the communication terminal device 400. The maintenance management DB 26 corresponds to an example of the "sixth database".

[0103] The maintenance plan data stored in the maintenance management DB 26 is transmitted to the communication terminal device 300 via the communication unit 10. The communication terminal device 300 presents the maintenance plan of the target facility 200 to the maintenance contractor based on the received maintenance plan data.

[0104] According to the maintenance support system 100 according to Embodiment 5, the maintenance plan of the target facility actually designed by the facility owner based on the maintenance plan generated by the maintenance support system 100 is transmitted by the maintenance support system 100 to the maintenance contractor. Thereby, the facility owner and the maintenance contractor can share the maintenance plan of the target facility 200.

[0105] The configurations exemplified as the above-described embodiments are examples of the configuration of the present disclosure, and it is also possible to combine them with other known technologies. It is also possible to change the configuration by omitting a part, etc., without departing from the gist of the present disclosure.

[0106] [Appendix] The above-described embodiments are specific examples of the following appendices.

[0107] (Appendix 1) A system for assisting in the preventive maintenance of target equipment, a first communication unit that communicates with the target equipment and a first communication terminal device that can be operated by a maintenance contractor of the target equipment; a first database that stores equipment data related to the target equipment received by the first communication unit from the target equipment; a second database that stores maintenance data related to the maintenance of the target equipment received by the first communication unit from the first communication terminal device; a processor; and a memory that stores a program executed by the processor, wherein the equipment data includes information related to the operation history and maintenance history of the target equipment, the maintenance data includes information related to the work cost required for the maintenance work of the target equipment and the personnel margin of the workers engaged in the maintenance work, the processor, according to the program, calculates the survival expectancy of the target equipment at each future time point based on the equipment data, calculates a maintenance implementation score at each future time point from the survival expectancy, the work cost, and the personnel margin at each future time point, and selects the implementation time of the maintenance work so as to meet a predetermined plan generation criterion based on the calculated maintenance implementation score, a maintenance support system.

[0108] (Appendix 2) wherein the maintenance data further includes worker information related to the number of workers assigned to each working day and the proficiency of each worker, and the processor generates a maintenance plan for the target equipment based on the worker information at the implementation time of the selected maintenance work, the maintenance support system according to Appendix 1.

[0109] (Appendix 3) It further includes a third database for storing weight data indicating the weights of the survival expectancy and the operation cost in the maintenance implementation score. The processor calculates the maintenance implementation score at each future time point from the survival expectancy, the operation cost, the personnel margin, and the weight data at each future time point, for the maintenance support system according to Appendix 1 or 2.

[0110] (Appendix 4) It further includes a second communication unit for communicating with a second communication terminal device that can be operated by the owner of the target facility. The third database stores the weight data received by the second communication unit from the second communication terminal device, for the maintenance support system according to any one of Appendices 1 to 3.

[0111] (Appendix 5) It further includes a fourth database for storing component data regarding components used in the maintenance work of the target facility. The component data includes information regarding the price of the component. The processor calculates the maintenance implementation score at each future time point from the survival expectancy, the operation cost, the personnel margin, and the price of the component at each future time point, for the maintenance support system according to any one of Appendices 1 to 4.

[0112] (Appendix 6) The processor calculates the maintenance implementation score at each future time point from the product of the operation cost at each future time point and the inflation rate of the price of the component at that time point, the survival expectancy, and the personnel margin at each future time point, for the maintenance support system according to Appendix 5.

[0113] (Appendix 7) It further includes a fifth database for storing budget data regarding the budget available for the maintenance work of the target facility. The budget data includes information indicating the budget at each future time point. The processor generates a maintenance plan for the target facility based on a point in time when the operation cost does not exceed the budget among the times for performing maintenance work selected based on the calculated maintenance execution score, according to any one of Appendices 1 to 6. The maintenance support system described in any one of Appendices 1 to 6.

[0114] (Appendix 8) A second communication unit that communicates with a second communication terminal device that can be operated by the owner of the target facility, The maintenance support system further includes a sixth database that stores maintenance plan data related to the maintenance plan of the target facility received by the second communication unit from the second communication terminal device. The first communication unit transmits the maintenance plan data stored in the sixth database to the first communication terminal device, according to any one of Appendices 1 to 7. The maintenance support system described in any one of Appendices 1 to 7.

[0115] (Appendix 9) A maintenance support method for assisting in the preventive maintenance of a target facility, A step in which a processor receives equipment data related to the target facility from the target facility and stores the received equipment data in a first database, A step in which the processor receives maintenance data related to the maintenance of the target facility from a first communication terminal device that can be operated by a maintenance contractor of the target facility and stores the received maintenance data in a second database. The equipment data includes information related to the operation history and maintenance history of the target facility, The maintenance data includes information related to the operation cost required for the maintenance work of the target facility and the personnel margin of the workers engaged in the maintenance work. A step in which the processor calculates the survival expectancy value of the target facility at each future point in time based on the equipment data, A step in which the processor calculates a maintenance execution score at each future point in time from the survival expectancy value, the operation cost, and the personnel margin at each future point in time. The method for maintenance support further includes a step in which the processor selects a timing for performing maintenance work so as to meet a predetermined plan generation criterion based on the calculated maintenance execution score.

[0116] (Appendix 10) The maintenance data further includes worker information regarding the number of workers assigned to each working day and the proficiency of each worker. The method for maintenance support according to Appendix 9 further includes a step in which the processor generates a maintenance plan for the target facility based on the worker information at the selected timing for performing maintenance work.

[0117] (Appendix 11) The method further includes a step in which the processor stores weight data indicating weights of the survival expectancy and the work cost in the maintenance execution score in a third database. The step of calculating the maintenance execution score includes a step of calculating the maintenance execution score at each future time point from the survival expectancy, the work cost, the personnel margin, and the weight data at each future time point. The method for maintenance support according to Appendix 9 or Appendix 10.

[0118] (Appendix 12) The method further includes a step in which the processor stores component data regarding components used for maintenance work of the target facility in a fourth database. The component data includes information regarding the price of the component. The step of calculating the maintenance execution score includes a step of calculating the maintenance execution score at each future time point from the survival expectancy, the work cost, the personnel margin, and the price of the component. The method for maintenance support according to any one of Appendices 9 to 11.

[0119] (Appendix 13) The step of calculating the maintenance implementation score includes multiplying the work cost at each future time point by the rate of increase in the price of the component at that time point, and calculating the maintenance implementation score at each future time point from the survival expectancy and the personnel margin at each future time point. The maintenance support method according to Supplementary Note 12.

[0120] (Supplementary Note 14) The processor further includes a step of storing budget data regarding the budget available for the maintenance work of the target facility in a fifth database. The budget data includes information indicating the budget at each future time point. The processor further includes a step of generating a maintenance plan for the target facility based on a time point at which the work cost does not exceed the budget among the implementation times of the maintenance work selected based on the calculated maintenance implementation score. The maintenance support method according to any one of Supplementary Notes 9 to 13.

[0121] (Supplementary Note 15) The step of the processor storing the maintenance plan data regarding the maintenance plan of the target facility received from a second communication terminal device that can be operated by the owner of the target facility in a sixth database, and The step of the processor transmitting the maintenance plan data stored in the sixth database to the first communication terminal device. The maintenance support method according to any one of Supplementary Notes 9 to 14.

[0122] (Supplementary Note 16) A program for causing a computer to execute the maintenance support method according to any one of Supplementary Notes 9 to 15.

[0123] It should be considered that all aspects of the embodiments disclosed this time are illustrative and not restrictive. The scope of the present disclosure is indicated not by the above description but by the claims, and it is intended that all modifications within the meaning and scope equivalent to the claims are included.

Explanation of Reference Numerals

[0124] 10,50 Communication Unit, 20 Data Management Unit, 21 Equipment DB, 22 Work Information DB, 23 Weight DB, 24 Parts DB, 25 Maintenance Management DB, 30 Expected Life Calculation Unit, 40 Maintenance Plan Generation Unit, 100 Maintenance Support System, 101 CPU, 102 RAM, 103 ROM, 104 I / F Device, 105 Storage Device, 106 Communication Bus, 200 Target Equipment, 300, 400, 500 Communication Terminal Devices, 210 Controller, 220 Electrical Equipment, 230 Sensor, NW Communication Network.

Claims

1. A system for assisting in the preventive maintenance of a target facility, comprising: a first communication unit that communicates with the target facility and a first communication terminal device that can be operated by a maintenance contractor of the target facility; a first database that stores equipment data related to the target facility received by the first communication unit from the target facility; a second database that stores maintenance data related to the maintenance of the target facility received by the first communication unit from the first communication terminal device; a processor; a memory that stores a program executed by the processor, wherein the equipment data includes information related to the operation history and maintenance history of the target facility, the maintenance data includes information related to the work cost required for the maintenance work of the target facility and the personnel margin of the workers engaged in the maintenance work, the processor, according to the program, calculates the survival expectancy value of the target facility at each future time point based on the equipment data, calculates a maintenance implementation score at each future time point from the survival expectancy value, the work cost, and the personnel margin at each future time point, and selects the implementation time of the maintenance work so as to meet a predetermined plan generation criterion based on the calculated maintenance implementation score. A maintenance support system.

2. The maintenance data further includes worker information related to the number of workers assigned to each working day and the proficiency of each worker, The processor generates a maintenance plan for the target facility based on the worker information at the implementation time of the selected maintenance work. The maintenance support system according to claim 1.

3. The system further comprises a third database that stores weight data indicating the weights of each of the survival expectancy value and the work cost in the maintenance implementation score, The processor calculates the maintenance implementation score at each future time point from the survival expectancy value, the work cost, and the personnel margin at each future time point and the weight data. The maintenance support system according to claim 1 or 2.

4. The system further comprises a second communication unit that communicates with a second communication terminal device that can be operated by an owner of the target facility, The third database stores the weight data received by the second communication unit from the second communication terminal device. The maintenance support system according to claim 3.

5. The system further includes a fourth database for storing component data related to components used in the maintenance work of the target equipment. The component data includes information on the price of the component. The processor calculates the maintenance execution score at each future time point from the survival expectancy, the work cost, the personnel margin, and the price of the component at each future time point. The maintenance support system according to claim 1 or 2.

6. The processor multiplies the work cost at each future time point by the rate of increase in the price of the component at that time point, and calculates the maintenance execution score at each future time point from the survival expectancy and the personnel margin at each future time point. The maintenance support system according to claim 5.

7. The system further includes a fifth database for storing budget data related to the budget available for the maintenance work of the target facility. The budget data includes information indicating the budget at each future time point. Based on the time points at which the work cost does not exceed the budget among the times for implementing the maintenance work selected based on the calculated maintenance execution score, the processor generates a maintenance plan for the target equipment. The maintenance support system according to claim 1.

8. A second communication unit that communicates with a second communication terminal device that can be operated by the owner of the target equipment, A sixth database for storing maintenance plan data related to the maintenance plan of the target equipment received by the second communication unit from the second communication terminal device. The first communication unit transmits the maintenance plan data stored in the sixth database to the first communication terminal device. The maintenance support system according to claim 1 or 2.

9. A maintenance support method for assisting in the preventive maintenance of target equipment, A step in which a processor receives equipment data related to the target equipment from the target equipment and stores the received equipment data in a first database. A step in which the processor receives maintenance data related to the maintenance of the target equipment from a first communication terminal device that can be operated by a maintenance contractor of the target equipment and stores the received maintenance data in a second database. The equipment data includes information on the operation history and maintenance history of the target equipment. The maintenance data includes information on the work cost required for the maintenance work of the target equipment and the personnel margin of the workers engaged in the maintenance work. The step of the processor calculating an expected survival value of the target facility at each future time point based on the facility data; The step of the processor calculating a maintenance implementation score at each future time point from the expected survival value, the work cost, and the personnel margin at each future time point; The maintenance support method further comprising the step of the processor selecting an implementation time of a maintenance operation so as to satisfy a predetermined plan generation criterion based on the calculated maintenance implementation score.

10. The maintenance data further includes worker information regarding the number of workers assigned to each working day and the proficiency of each worker; The maintenance support method according to claim 9, further comprising the step of the processor generating a maintenance plan for the target facility based on the worker information at the selected implementation time of the maintenance operation.

11. The processor further comprises the step of storing, in a third database, weight data indicating weights of each of the expected survival value and the work cost in the maintenance implementation score; The step of calculating the maintenance implementation score includes calculating the maintenance implementation score at each future time point from the expected survival value, the work cost, the personnel margin, and the weight data at each future time point. The maintenance support method according to claim 9 or 10.

12. The processor further comprises the step of storing, in a fourth database, component data regarding components used for the maintenance operation of the target facility; The component data includes information regarding the price of the component; The step of calculating the maintenance implementation score includes calculating the maintenance implementation score at each future time point from the expected survival value, the work cost, the personnel margin, and the price of the component at each future time point. The maintenance support method according to claim 9 or 10.

13. The step of calculating the maintenance implementation score includes calculating the maintenance implementation score at each future time point from the product of the work cost at each future time point and the inflation rate of the price of the component at that time point, the expected survival value, and the personnel margin at each future time point. The maintenance support method according to claim 12.

14. The processor further comprises the step of storing, in a fifth database, budget data regarding the budget available for the maintenance operation of the target facility; The budget data includes information indicating the budget at each future point in time. The method for maintenance support according to claim 9, further comprising a step in which the processor generates a maintenance plan for the target facility based on a point in time at which the work cost does not exceed the budget among the implementation times of the maintenance work selected based on the calculated maintenance implementation score.

15. The step in which the processor stores, in a sixth database, maintenance plan data regarding the maintenance plan of the target facility received from a second communication terminal device that can be operated by the owner of the target facility; The method for maintenance support according to claim 9 or 10, further comprising a step in which the processor transmits the maintenance plan data stored in the sixth database to the first communication terminal device.

16. A program for causing a computer to execute the method for maintenance support according to any one of claims 9 to 15.

Images