Facility management system, facility management method, and facility management program

Abstract

To provide a facility management system, a facility management method, and a facility management program which propose a facility repair plan refined on the basis of operation results.SOLUTION: In a facility management system 100 for refining a repair plan for a facility, an application unit 110 which is realized by executing various kinds of programs by a processor comprises: a facility ledger management unit 121 that manages a ledger of the facility; and a repair plan management unit 122 that calculates a recommended next repair date on the basis of the number of days that have passed from a date of installation of the facility. The repair plan management unit 122 re-calculates the recommended repair date by using a maximum period of operability from operation results and the date of installation of the facility.SELECTED DRAWING: Figure 2A

Description

[Technical field]

[0001] The present invention relates to a facility management system for optimizing a facility repair plan. [Background technology]

[0002] Facilities such as office buildings are equipped with equipment such as air conditioning, elevators, water supply piping, etc. In order to maintain proper operation of these facilities and ensure their long-term use, they need to be repaired periodically according to an equipment repair plan.

[0003] Background art in this technical field includes Patent Document 1 (JP Patent Publication No. 2007-37035), Patent Document 2 (JP Patent Publication No. 2005-352729), and Patent Document 3 (JP Patent Publication No. 2012-55417). Patent Document 1 discloses a facility management system that is connected to at least one central control monitoring device provided in each facility that controls the operation of each facility device in the facility, monitors the operation status, and periodically provides operation status information of each facility device, and that performs maintenance management of each facility device in the facility, and that changes master maintenance and repair plan information for each facility device according to predetermined conditions related to the operation status information and inspection information based on the operation status information of each facility device from the central control monitoring device and the inspection information of each facility device obtained by maintenance and inspection by maintenance personnel, so as to postpone maintenance and repair measures.

[0004] Patent Document 2 also discloses a building repair plan calculation device that includes a repair necessity storage means that stores a standard repair necessity, which is a reference value for determining the need for repairs of various repair objects in a building, and an existing repair necessity for each repair object at the time of a past regular inspection, an inspection cycle storage means that stores an inspection cycle, which is the cycle of regular inspections for each repair object, a repair necessity input means that inputs the latest repair necessity for each repair object at the time of the latest regular inspection, a standard repair cycle calculation means that calculates a standard repair implementation time based on the standard repair necessity and the existing repair necessity stored in the repair necessity storage means, the inspection cycle stored in the inspection cycle storage means, and the latest repair necessity input by the repair necessity input means, and a standard repair cycle display means that displays the standard repair implementation time calculated by the standard repair cycle calculation means.

[0005] Patent Document 3 also discloses an electrical device having a function of notifying the user when it is time for maintenance and inspection. The electrical device has a control device that controls each part, a memory unit connected to the control device and storing information regarding the state and control of the electrical device, a notification unit connected to the control unit and notifying the user of the state of the electrical device, and a safety device connected to the control device and detecting the state of each part of the electrical device, the control device being constantly powered to operate the safety device, the control device measuring the cumulative power-on time since power was first supplied to the electrical device and writing this into the memory unit, and when the cumulative power-on time exceeds a preset value, the notification unit notifies the user of the time for maintenance and inspection. [Prior art documents] [Patent documents]

[0006] [Patent Document 1] JP 2007-37035 A [Patent Document 2] JP 2005-352729 A [Patent Document 3] JP 2012-55417 A Summary of the Invention [Problem to be solved by the invention]

[0007] Generally, equipment deteriorates with age and operation, so the less operation, the less deterioration there will be. Furthermore, equipment repair plans should be reviewed according to the degree of deterioration.

[0008] However, because reviewing facility repair plans places a heavy burden on managers, facility repair plans are often not reviewed even if actual operation results are lower than initially expected. Therefore, there is a need to optimize repair costs by appropriately revising facility repair plans to reflect actual operation results.

[0009] The present invention aims to propose an optimized facility repair plan based on operational records. [Means for solving the problem]

[0010] A representative example of the invention disclosed in the present application is as follows: A facility management system for optimizing a facility repair plan includes a calculation device that executes a predetermined calculation process to realize each of the following functional units, and a storage device that stores information used in the calculation process, and includes a facility ledger management unit that manages a ledger of the facility, and a repair plan management unit that calculates the next recommended repair date based on the number of days that have passed since the installation date of the facility. The smaller value of the replacement period minus the operating time measured during the inspection of the equipment, divided by the operating rate of the equipment, and the maximum period during which the equipment can be operated from the date of installation. The method is characterized in that the recommended repair date is recalculated using the above formula. Effect of the Invention

[0011] According to one aspect of the present invention, it is possible to flexibly change the immediate repair plan based on the operation record of the facility. Problems, configurations, and effects other than those described above will become apparent from the following description of the embodiments. [Brief description of the drawings]

[0012] [Figure 1] FIG. 2 is a diagram showing the operation of the facility repair plan optimization system according to an embodiment of the present invention. [Figure 2A] FIG. 1 is a diagram showing the configuration of a facility repair plan optimization system. [Figure 2B] FIG. 2 is a diagram showing the configuration of a terminal. [Diagram 3] 13 is a flowchart of a facility repair plan optimization process. [Figure 4A] 13 is a flowchart of processing at the time of equipment ledger registration. [Figure 4B] 13 is a flowchart of operation result registration process 1. [Figure 4C] 13 is a flowchart of a repair history registration process 1. [Figure 4D] 13 is a flowchart of operation result registration process 2. [Figure 4E] 13 is a flowchart of a repair history registration process 2. [Figure 4F] 13 is a flowchart of operation result registration process 3. [Diagram 5] FIG. 2 is a diagram illustrating an example of the configuration of an equipment register database. [Figure 6] FIG. 2 is a diagram illustrating an example of the configuration of a repair plan database. [Figure 7] FIG. 2 is a diagram illustrating an example of the configuration of an inspection result database. [Figure 8] FIG. 13 is a diagram illustrating an example of the configuration of a repair history database. [Figure 9] FIG. 13 is a diagram showing an example of an equipment repair plan details display screen. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0013] FIG. 1 is a diagram showing the operation of a facility repair plan optimization system 100 according to an embodiment of the present invention.

[0014] The facility repair plan optimization system 100 is connected to a terminal 200 used by a facility manager. The facility repair plan optimization system 100 and the terminal 200 are each configured with a computer, and their configurations will be described later with reference to Figs. 2A and 2B.

[0015] An overview of facility management using the facility repair plan optimization system 100 is as follows. (1) The equipment manager inputs the equipment installation date, replacement cycle, expected operating time, and maximum period into the terminal 200. Equipment not only requires repairs after a specified operating time, but also requires repairs after the maximum period has elapsed even if the equipment has been in operation for a short time. Therefore, the maximum period is the period during which the equipment can be used, and equipment requires repairs after the maximum period has elapsed. The input information is registered in the equipment ledger database 141 of the equipment repair plan optimization system 100. (2) The equipment repair plan optimization system 100 calculates the recommended repair dates from the equipment information registered in the equipment ledger database 141 and creates a repair plan. (3) The facility manager edits the maintenance plan by referring to the calculated recommended dates, and stores the edited maintenance plan in the maintenance plan database 142. (4) Maintenance and inspection personnel will inspect the equipment and measure its operating performance. (5) The equipment manager registers the operation results measured by the maintenance inspector in the inspection result database 143. (6) The facility repair plan optimization system 100 recalculates the recommended repair date using the registered operation history. (7) The facility manager updates the repair plan by referring to the recalculated recommended dates.

[0016] Representative examples of equipment that the equipment repair plan optimization system 100 of this embodiment targets are air conditioning, elevators, and water supply piping, but the system is not limited to these and can be applied to any equipment that is installed in a facility such as an office building and requires maintenance inspection and regular repairs.

[0017] FIG. 2A is a diagram showing the configuration of the facility repair plan optimization system 100. As shown in FIG.

[0018] The facility repair plan optimization system 100 is configured with a computer having a processor (CPU), a memory, an auxiliary storage device, and a communication interface (not shown).

[0019] The facility repair plan optimization system 100 is a computer system configured on multiple logically or physically configured computers, or on a single physical computer, and may operate on a virtual computer constructed on multiple physical computer resources.

[0020] The processor is a computing device that executes programs (computational processing) stored in a memory. The processor executes various programs to realize the application unit 110. Note that some of the processing performed by the processor executing the programs may be executed by another computing device (for example, a hardware computing device such as an FPGA or an ASIC). The application unit 110 includes a repair plan management function 120 and a communication unit 130.

[0021] The repair plan management function 120 has an equipment ledger management unit 121, a repair plan management unit 122, an inspection result management unit 123, and a repair history management unit 124. The equipment ledger management unit 121 manages the writing and reading of data to the equipment ledger database 141. The repair plan management unit 122 creates repair plans, writes them to the repair plan database 142, and reads out the repair plans stored in the repair plan database 142. The inspection result management unit 123 manages the writing and reading of data to the inspection result database 143. The repair history management unit 124 manages the writing and reading of data to the repair history database 144.

[0022] The communication unit 130 controls transmission and reception of data to and from other devices (eg, the terminal 200) via a network (eg, the Internet 250).

[0023] Memory includes ROM, which is a non-volatile storage element, and RAM, which is a volatile storage element. ROM stores unchanging programs (e.g., BIOS), etc. RAM is a high-speed, volatile storage element such as DRAM (Dynamic Random Access Memory), which temporarily stores programs executed by a processor and data used when executing the programs.

[0024] The auxiliary storage device is, for example, a large-capacity, non-volatile storage device such as a magnetic storage device (HDD) or a flash memory (SSD). The auxiliary storage device stores data used by the processor when executing a program (e.g., an equipment ledger database 141, a repair plan database 142, an inspection result database 143, and a repair history database 144), and programs executed by the processor (e.g., an equipment ledger management program, a repair plan management program, an inspection result management program, and a repair history management program). In other words, the programs are read from the auxiliary storage device, loaded into the memory, and executed by the processor to realize the functions of the equipment repair plan optimization system 100.

[0025] The configuration of each database will be described later with reference to Figures 5 to 8. Note that, although examples of databases configured in a table format will be described in Figures 5 to 8, these databases do not necessarily have to be in a table format, and may be expressed in a list, a queue, or other data structure.

[0026] The communication interface is a network interface device that controls communications with other devices according to a predetermined protocol.

[0027] The program executed by the processor is provided to the facility maintenance plan optimization system 100 via a removable medium (such as a CD-ROM or a flash memory) or a network, and is stored in a non-volatile auxiliary storage device, which is a non-transitory storage medium. For this reason, the facility maintenance plan optimization system 100 may have an interface for reading data from the removable medium.

[0028] FIG. 2B is a diagram showing the configuration of terminal 200.

[0029] The terminal 200 is configured by a computer having a processor (CPU), a memory, an auxiliary storage device, a communication interface, an input interface, and an output interface (not shown).

[0030] The processor is a computing device that executes programs (computational processing) stored in a memory. The processor executes various programs to realize functions of the terminal 200 (for example, the web browser 210 and the communication unit 220). Note that some of the processes performed by the processor by executing the programs may be executed by another computing device (for example, a hardware computing device such as an FPGA or an ASIC).

[0031] The web browser 210 outputs (e.g., displays) information generated by the equipment repair plan optimization system 100 to an output interface, and transmits information input to an input interface to the equipment repair plan optimization system 100. The web browser 210 executes code (e.g., Java script, "Java script" is a registered trademark) received from the equipment repair plan optimization system 100 to realize the function of the equipment repair plan optimization unit 230. The equipment repair plan optimization unit 230 system has an equipment ledger display unit 231, a repair plan display unit 232, an inspection result display unit 233, and a repair history display unit 234.

[0032] The equipment ledger display unit 231 displays the equipment ledger database 141 and accepts input therefor. The repair plan display unit 232 displays the repair plan database 142 and accepts changes to the scheduled repair date. For example, the repair plan display unit 232 may display the repair plan by an equipment repair plan details display screen (FIG. 9). The inspection result display unit 233 displays the inspection result database 143. The repair history display unit 234 displays the repair history database 144.

[0033] The communication unit 130 controls transmission and reception of data to and from other devices (for example, the facility repair plan optimization system 100) via a network (for example, the Internet 250).

[0034] Memory includes ROM, which is a non-volatile storage element, and RAM, which is a volatile storage element. ROM stores unchanging programs (e.g., BIOS), etc. RAM is a high-speed, volatile storage element such as DRAM (Dynamic Random Access Memory), which temporarily stores programs executed by a processor and data used when executing the programs.

[0035] The auxiliary storage device is, for example, a large-capacity non-volatile storage device such as a magnetic storage device (HDD) or a flash memory (SSD). The auxiliary storage device stores a program (for example, a web browser program) to be executed by the processor. That is, the program is read from the auxiliary storage device, loaded into the memory, and executed by the processor to realize the functions of the terminal 200.

[0036] The communication interface is a network interface device that controls communications with other devices according to a predetermined protocol.

[0037] FIG. 3 is a flowchart of the facility repair plan optimization process.

[0038] First, the equipment manager inputs equipment information to the terminal 200. The input information, such as the installation date, replacement interval, and expected operation time, is registered in the equipment ledger database 141 (S31).

[0039] As shown in FIG. 5, the equipment ledger database 141 is a database in which information about equipment managed by the equipment repair plan optimization system 100 is stored, and includes data such as ID, major category, medium category, medium category branch number, minor category, minor category branch number, part name, part branch number, installation date, replacement cycle, maximum period, and expected operating time.

[0040] The ID is an identifier for uniquely identifying data recorded in the equipment ledger database 141. The major category, medium category, medium category sub-number, minor category, and minor category sub-number are categories of parts that constitute the equipment defined hierarchically. The part name is the name of the part that constitutes the equipment and is subject to inspection and repair. The part sub-number is an identifier for uniquely identifying the part that constitutes the equipment. The installation date is the date on which the equipment was installed. The replacement cycle is the cycle at which the equipment should be replaced, and the replacement or repair of the part is performed at the timing of the replacement cycle. As described above, the maximum period is the usable period of the equipment, that is, the period after which repair is required even if the equipment has been in operation for a short time. The expected operation time is a numerical value that indicates the operation rate of the equipment, and for example, 24-hour operation, 8 hours a day on weekdays operation, etc. are recorded.

[0041] Thereafter, when the terminal 200 receives an instruction from the equipment manager to start creating a repair plan, the equipment repair plan optimization system 100 calculates the recommended repair date from the equipment information registered in the equipment ledger database 141, and creates a repair plan (S32). In step S32, as shown in Fig. 4A, the equipment repair plan optimization system 100 calculates the recommended repair date from the equipment information registered in the equipment ledger database 141 using the following formula, and creates a repair plan. In the following formula, MIN(a, b) is a function that gives the minimum value of the arguments a and b. Next recommended repair date = installation date + MIN((replacement cycle / expected operating time), maximum period) Next next recommended repair date = Next repair date + MIN((replacement cycle / expected operating time), maximum period) Thereafter, the third and subsequent recommended repair dates are calculated in the same manner.

[0042] Here, the expected operating time is a numerical value indicating the operating ratio of the equipment recorded in the equipment ledger database 141 described later, and is an operating rate according to the unit of the replacement cycle. For example, if the unit of the replacement cycle is days and the equipment operates 24 hours a day, the expected operating time is 1. Also, if the unit of the replacement cycle is hours and the equipment operates 8 hours a day on weekdays, the expected operating time can be calculated as 40÷(24×7), which is 5 / 21.

[0043] In the equipment ledger registration process in step S32, the recommended repair date is calculated using the predetermined replacement cycle and expected operating time repair for each piece of equipment, making it possible to calculate an appropriate recommended repair date based on the failure frequency for each piece of equipment (e.g., the operation warranty period and MTBF).

[0044] Thereafter, the terminal 200 acquires and displays the repair plan from the facility repair plan optimization system 100. The terminal 200 accepts the repair plan edited by the facility manager and registers it in the repair plan database 142 (S33). Furthermore, the terminal 200 registers a plurality of repair plans created by the facility manager as necessary in the repair plan database 142 (S34).

[0045] As shown in FIG. 6, the maintenance plan database 142 is a database in which maintenance plans for equipment (e.g., planned maintenance dates) are stored, and includes data such as ID, major category, medium category, medium category branch number, minor category, minor category branch number, part name, part branch number, and planned date.

[0046] The ID is an identifier for uniquely identifying data recorded in the repair plan database 142. The major category, medium category, medium category sub-number, minor category, and minor category sub-number are categories of parts that make up the equipment, represented hierarchically. The part name is the name of the part that is subject to inspection or repair and that makes up the equipment. The part sub-number is an identifier for uniquely identifying the part that makes up the equipment. The planned date is the planned date for repairing the equipment, and is the planned repair date determined by the equipment manager based on the recommended repair date calculated by the equipment repair plan optimization system 100. The planned date is usually set for each equipment, but it can also be set for each part that makes up the equipment.

[0047] Thereafter, a maintenance inspector inspects the equipment and measures the equipment's operation record 1 (operation time since installation) (S35).

[0048] The terminal 200 receives operation results measured by a maintenance inspector through operation by the equipment manager. The input operation results are transmitted from the terminal 200 to the equipment repair plan optimization system 100 and registered in the inspection value column of the inspection result database 143. The equipment repair plan optimization system 100 then recalculates the recommended repair date using the registered operation results (S36). In operation result registration process 1 of step S36, as shown in FIG. 4B, first, the terminal 200 receives input of the inspection results (inspection date, operation results) by the equipment manager. The input inspection results are transmitted from the terminal 200 to the equipment repair plan optimization system 100 and registered in the inspection result database 143 (S361).

[0049] The facility maintenance plan optimization system 100 acquires one maintenance plan, and recalculates the recommended maintenance date for the acquired maintenance plan from the registered operation record using the following formula (S362). In the formula, MIN(a, b) is a function that gives the minimum value of the arguments a and b. Next recommended repair date = inspection date + MIN(((replacement cycle - operation record 1) / expected operation time), maximum period) Next next recommended repair date = Next repair date + MIN((replacement cycle / expected operating time), maximum period) Thereafter, the third and subsequent recommended repair dates are calculated in the same manner.

[0050] Thereafter, it is determined whether the recommended maintenance dates for all maintenance plans have been recalculated (S363). If there is a maintenance plan for which the recommended maintenance dates have not been recalculated, the process returns to step S362, and the recommended maintenance dates for the next maintenance plan are recalculated. On the other hand, if the recalculation of the recommended maintenance dates for all maintenance plans has been completed, the operation record registration process 1 is terminated, and the process proceeds to step S37.

[0051] In operation record registration process 1 in step S36, the recommended repair date is calculated using the predetermined replacement cycle for each piece of equipment and the most recent operation record 1 (operating time since installation), so that an appropriate recommended repair date can be calculated based on the actual operating state. For example, since equipment with shorter operating hours than planned is expected to take longer to break down, the recommended repair date can be postponed. On the other hand, equipment with longer operating hours than planned is expected to break down sooner, so the recommended repair date should be brought forward.

[0052] As shown in FIG. 7, the inspection result database 143 is a database in which information about equipment managed by the equipment repair plan optimization system 100 is stored, and includes data such as ID, major category, medium category, medium category branch number, minor category, minor category branch number, part name, part branch number, inspection date, and inspection value.

[0053] The ID is an identifier for uniquely identifying data recorded in the inspection result database 143. The major category, the medium category, the medium category sub-number, the minor category, and the minor category sub-number are categories of parts constituting the equipment defined hierarchically. The part name is the name of the part constituting the equipment that is the subject of inspection or repair. The part sub-number is an identifier for uniquely identifying the part constituting the equipment. The inspection date is the date on which the equipment was inspected. The inspection date is usually set for each equipment, but can be set for each part constituting the equipment. The inspection value is a numerical value measured by the inspection, and FIG. 7 shows the operation time. In addition to the operation time, the current value, temperature, vibration, sound, etc. may be measured and recorded as the inspection value. Since the current value, temperature, vibration, and sound indirectly indicate the deterioration degree of the equipment, these values ​​may be used as the operation record to recalculate the recommended repair date.

[0054] Thereafter, the facility manager operates the terminal 200 to change the planned maintenance date with reference to the recalculated recommended date, and updates the maintenance plan (S37).

[0055] Thereafter, the maintenance and inspection personnel performs the repairs, inspects the equipment, and measures the equipment's operation record 2 (the operation time from installation to the current repair) (S38).

[0056] The terminal 200 receives the operation result 2 measured by the maintenance inspector through the operation of the equipment manager. The input operation result 2 is transmitted from the terminal 200 to the equipment repair plan optimization system 100 and registered in the inspection value column of the inspection result database 143. It is preferable that the inspection value of the inspection result database 143 is provided with a column for recording the operation result for each period, and the operation result 1, operation result 2, ..., operation result n are recorded separately. Furthermore, the terminal 200 receives the history of repairs (repair date 1) performed by the maintenance inspector through the operation of the equipment manager. The input repair history is transmitted from the terminal 200 to the equipment repair plan optimization system 100 and registered in the repair history database 144. The equipment repair plan optimization system 100 then recalculates the recommended repair date using the registered repair history and operation history (S39).

[0057] As shown in Fig. 4C, in repair history registration process 1 in step S39, the recommended repair date is calculated using operation record 2 from installation to the current repair. Specifically, first, the equipment manager inputs operation record 2 into terminal 200. The input operation record 2 is transmitted from terminal 200 to equipment repair plan optimization system 100 and registered in the inspection value column of inspection result database 143 (S391).

[0058] Next, the facility manager inputs the repair history (repair date 1) into the terminal 200. The input repair history is transmitted from the terminal 200 to the facility repair plan optimization system 100 and registered in the repair history database 144 (S392).

[0059] The facility maintenance plan optimization system 100 acquires one maintenance plan, and for the acquired maintenance plan, recalculates the recommended maintenance date from the registered operation record 2 using the following formula (S393). In the formula, MIN(a,b) is a function that gives the minimum value of the arguments a and b, and average(a,b) is a function that gives the average value of the arguments a and b. Next recommended repair date = Repair date 1 + MIN((average (replacement cycle, operation record 2) / expected operation time), maximum period) Next next recommended repair date = Next recommended repair date + MIN((average (replacement cycle, operation record 2) / expected operation time), maximum period) Thereafter, the third and subsequent recommended repair dates are calculated in the same manner.

[0060] Thereafter, it is determined whether the recommended maintenance dates for all maintenance plans have been recalculated (S394). If there is a maintenance plan for which the recommended maintenance dates have not been recalculated, the process returns to step S393, and the recommended maintenance dates for the next maintenance plan are recalculated. On the other hand, if the recalculation of the recommended maintenance dates for all maintenance plans has been completed, the repair history registration process 1 is terminated, and the process proceeds to step S41.

[0061] In the repair history registration process 1 in step S39, the most recent operating history 2 up until the repair (the operating time from installation to the current repair) is used to calculate the recommended repair date, thereby making it possible to calculate an appropriate recommended repair date based on the actual operating history, and further making it possible to calculate an appropriate recommended repair date while avoiding sudden changes in the repair cycle.

[0062] As shown in FIG. 8, the repair history database 144 is a database in which the history of equipment repairs (e.g., repair date) is stored, and includes data such as ID, major category, medium category, medium category branch number, minor category, minor category branch number, part name, part branch number, and repair date.

[0063] The ID is an identifier for uniquely identifying data recorded in the repair history database 144. The major category, medium category, medium category sub-number, minor category, and minor category sub-number are categories of parts that make up the equipment, represented hierarchically. The part name is the name of the part that makes up the equipment and is subject to inspection or repair. The part sub-number is an identifier for uniquely identifying the part that makes up the equipment. The repair date is the date on which repairs such as replacement or adjustment of a part that makes up the equipment were performed.

[0064] Thereafter, the facility manager operates the terminal 200 to change the planned maintenance date with reference to the recalculated recommended date, and updates the maintenance plan (S40).

[0065] Thereafter, a maintenance inspector inspects the equipment and measures the equipment's operation record 3 (operation time since the last repair) (S41).

[0066] The terminal 200 receives the operation record 3 measured by a maintenance inspector through operation by the equipment manager. The input operation record 3 is transmitted from the terminal 200 to the equipment repair plan optimization system 100 and registered in the inspection value column of the inspection result database 143. Then, the equipment repair plan optimization system 100 recalculates the recommended repair date using the registered operation record (S42).

[0067] As shown in Fig. 4D, in operation record registration process 2 in step S42, the recommended repair date is calculated using operation record 2 up to repair and operation record 3 from repair. Specifically, first, the equipment manager inputs operation record 3 into terminal 200. The input operation record 3 is transmitted from terminal 200 to equipment repair plan optimization system 100 and registered in the inspection value column of inspection result database 143 (S421).

[0068] The facility maintenance plan optimization system 100 acquires one maintenance plan, and for the acquired maintenance plan, recalculates the recommended maintenance date from the registered operation record using the following formula (S422). In the formula, MIN(a,b) is a function that gives the minimum value of the arguments a and b, and average(a,b) is a function that gives the average value of the arguments a and b. Next recommended repair date = inspection date + MIN(((average (replacement cycle, operation record 2) - operation record 3) / expected operation time), maximum period) Next next recommended repair date = Next recommended repair date + MIN((average (replacement cycle, operation record 2) / expected operation time), maximum period) Thereafter, the third and subsequent recommended repair dates are calculated in the same manner.

[0069] Thereafter, it is determined whether the recommended maintenance dates for all maintenance plans have been recalculated (S423). If there is a maintenance plan for which the recommended maintenance dates have not been recalculated, the process returns to step S422 and recalculates the recommended maintenance dates for the next maintenance plan. On the other hand, if the recalculation of the recommended maintenance dates for all maintenance plans has been completed, the operation record registration process 2 is terminated and the process proceeds to step S43.

[0070] In operation history registration process 2 in step S42, the recommended repair date is calculated using operation history 2 up to the most recent repair (operating time up to the previous repair) and operation history 3 since the most recent repair (operating time since the previous repair), thereby making it possible to correct the replacement cycle based on the actual operation history and to calculate an appropriate recommended repair date using the corrected replacement cycle.

[0071] The facility manager operates the terminal 200 to change the planned maintenance date with reference to the recalculated recommended date, and updates the maintenance plan (S43).

[0072] Thereafter, the maintenance and inspection personnel performs repairs, inspects the equipment, and measures the equipment's operation record 4 (the operation time from the previous repair to the current repair) (S44).

[0073] The terminal 200 receives the operation record 4 measured by the maintenance inspector through operation by the equipment manager. The input operation record 4 is transmitted from the terminal 200 to the equipment repair plan optimization system 100 and registered in the inspection value column of the inspection result database 143. The terminal 200 also receives the repair history (repair date 2) performed by the maintenance inspector through operation by the equipment manager. The input repair history is transmitted from the terminal 200 to the equipment repair plan optimization system 100 and registered in the repair history database 144. The equipment repair plan optimization system 100 then recalculates the recommended repair date using the registered repair history and operation record (S45).

[0074] As shown in Fig. 4E, in repair history registration process 2 in step S45, the recommended repair date is calculated using the average of operation record 2 up until the previous repair and operation record 4 from the previous repair to the current repair. Specifically, first, the equipment manager inputs operation record 4 into terminal 200. The input operation record 2 is transmitted from terminal 200 to equipment repair plan optimization system 100 and registered in the inspection value column of inspection result database 143 (S451).

[0075] Next, the facility manager inputs the repair history (repair date 2) into the terminal 200. The input repair history is transmitted from the terminal 200 to the facility repair plan optimization system 100 and registered in the repair history database 144 (S452).

[0076] The facility repair plan optimization system 100 acquires one repair plan, and for the acquired repair plan, recalculates the recommended repair date from the registered operation results 2 and operation results 4 using the following formula (S453). In the formula, MIN(a,b) is a function that gives the minimum value of the arguments a and b, and average(a,b) is a function that gives the average value of the arguments a and b. Next recommended repair date = Repair date 2 + MIN((average (replacement cycle, operation record 2, operation record 4) / expected operation time), maximum period) Next next recommended repair date = Next recommended repair date + MIN((average (replacement cycle, operation record 2, operation record 4) / expected operation time), maximum period) Thereafter, the third and subsequent recommended repair dates are calculated in the same manner.

[0077] Thereafter, it is determined whether the recommended maintenance dates for all maintenance plans have been recalculated (S454). If there is a maintenance plan for which the recommended maintenance dates have not been recalculated, the process returns to step S473, and the recommended maintenance dates for the next maintenance plan are recalculated. On the other hand, if the recalculation of the recommended maintenance dates for all maintenance plans has been completed, the repair history registration process 2 is terminated, and the process proceeds to step S46.

[0078] In the repair history registration process 2 in step S45, the recommended repair date is calculated using the average of the operation record 2 up until the previous repair (operation time up until the previous repair) and the most recent operation record 4 up until the repair (operation time from the previous repair to this repair), so that the replacement cycle can be corrected based on the actual operation record, and an appropriate recommended repair date can be calculated using the corrected replacement cycle. Furthermore, an appropriate recommended repair date can be calculated while avoiding sudden changes in the repair cycle.

[0079] The facility manager operates the terminal 200 to change the planned maintenance date with reference to the recalculated recommended date, and updates the maintenance plan (S46).

[0080] Thereafter, the maintenance inspector inspects the equipment and measures the equipment's operation record 5 (the operation time since the last repair) (S47).

[0081] Terminal 200 receives operation record 5 measured by a maintenance inspector through operation by the equipment manager. The input operation record 5 is transmitted from terminal 200 to equipment repair plan optimization system 100 and registered in the inspection value column of inspection result database 143. Then, equipment repair plan optimization system 100 recalculates the recommended repair date using the registered operation record (S48).

[0082] As shown in Fig. 4F, in operation record registration process 3 in step S48, the recommended repair date is calculated using the average of operation record 2 up to the repair before last (operation time up to the repair before last) and operation record 4 up to the most recent repair (operation time from the repair before last to the previous repair). Specifically, first, the equipment manager inputs operation record 5 into terminal 200. The input operation record 5 is transmitted from terminal 200 to equipment repair plan optimization system 100 and registered in the inspection value column of inspection result database 143 (S481).

[0083] The facility maintenance plan optimization system 100 acquires one maintenance plan, and for the acquired maintenance plan, recalculates the recommended maintenance date from the registered operation record using the following formula (S482). In the formula, MIN(a,b) is a function that gives the minimum value of the arguments a and b, and average(a,b) is a function that gives the average value of the arguments a and b. Next recommended repair date = Inspection date + MIN(((Average (replacement cycle, operation record 2, operation record 4) - operation record 5) / expected operation time), maximum period) Next next recommended repair date = Next recommended repair date + MIN((average (replacement cycle, operation record 2, operation record 4) / expected operation time), maximum period) Thereafter, the third and subsequent recommended repair dates are calculated in the same manner.

[0084] Thereafter, it is determined whether the recommended maintenance dates for all maintenance plans have been recalculated (S483). If there is a maintenance plan for which the recommended maintenance dates have not been recalculated, the process returns to step S482, and the recommended maintenance dates for the next maintenance plan are recalculated. On the other hand, if the recalculation of the recommended maintenance dates for all maintenance plans has been completed, the operation record registration process 3 is terminated, and the process proceeds to step S49.

[0085] In operation history registration process 3 in step S48, the recommended repair date is calculated using the average of operation history 2 up to the last repair (operating time up to the repair before last) and the most recent operation history 4 up to the repair (operating time from the repair before last to the last repair), that is, the average of the operating time up to each of multiple repairs, thereby making it possible to correct the replacement cycle based on the actual operation history and to calculate an appropriate recommended repair date using the corrected replacement cycle.

[0086] The facility manager operates the terminal 200 to change the planned maintenance date with reference to the recalculated recommended date, and updates the maintenance plan (S49).

[0087] FIG. 9 is a diagram showing an example of an equipment repair plan details display screen.

[0088] In the upper left area of ​​the illustrated equipment repair plan detail display screen, the equipment managed by the equipment repair plan optimization system 100 is classified into parts and displayed. In the upper right area, the recommended repair dates 910 and 915 and the scheduled repair date 920 calculated by the equipment repair plan optimization system 100 are displayed on the time axis. The recommended repair date may be determined from the operating time or from the maximum period, and it is preferable to display the two in a manner that allows them to be distinguished. For example, the recommended repair date 910 is a recommended repair date determined from the operating time, and the recommended repair date 915 is a recommended repair date determined from the maximum period. The equipment manager can change the scheduled repair date 920 by moving it on the time axis. For example, the scheduled repairs for 2021 and 2022 for the part = power supply 2 in the second row have been changed to scheduled repair dates that are brought forward by several months, and the scheduled repairs for 2022 for the subdivision = outdoor unit in the third row have been changed to scheduled repair dates that are brought forward by several months. It is preferable that the planned maintenance date 920, which is changed from the recommended maintenance date 910, is displayed in a manner different from the unchanged planned maintenance date 920. It is also preferable that the difference between the recommended maintenance date 910 and the planned maintenance date 920 is displayed on the time axis so that it can be seen.

[0089] In the upper right area of ​​the equipment repair plan details display screen, repair costs (past results, future estimates) 930 are displayed near the scheduled repair date 920. In the lower right area, the budget, results, and estimates of repair costs for a given period (half a year in the figure) are displayed, allowing budget and actual management.

[0090] As described above, the equipment repair plan optimization system 100 of an embodiment of the present invention has an equipment ledger management unit 121 that manages equipment ledgers, and a repair plan management unit 122 that calculates the next recommended repair date based on the number of days that have elapsed since the equipment was installed. The repair plan management unit 122 recalculates the recommended repair date using the equipment's operating history (e.g., operating hours), so that when calculating the recommended repair date, the most recent repair plan can be flexibly changed based on the equipment's operating history.

[0091] In addition, the repair plan management unit 122 recalculates the recommended repair date using the operating results measured during equipment inspection, so that it can calculate an appropriate recommended repair date based on the actual operating results for each inspection, allowing the repair plan to be changed flexibly.

[0092] In addition, the repair plan management unit 122 recalculates the recommended repair date based on the value obtained by subtracting the operating time, which is the actual operating performance, from the equipment replacement cycle and dividing the result by the operating rate of the equipment, so that it is possible to calculate a highly accurate recommended repair date based on the actual operating performance for each inspection timing.

[0093] In addition, the repair plan management unit 122 recalculates the recommended repair date based on the value obtained by subtracting the most recent operation performance measured at the time of equipment inspection from the average value of the operation performance up to the last repair and the operation performance since the last repair, and dividing the result by the operation rate of the equipment. Therefore, it is possible to calculate an appropriate recommended repair date while avoiding sudden changes in the period until repair.

[0094] The present invention is not limited to the above-described embodiments, and includes various modified examples and equivalent configurations within the spirit of the appended claims. For example, the above-described embodiments have been described in detail to clearly explain the present invention, and the present invention is not necessarily limited to those including all of the configurations described. Furthermore, a part of the configuration of one embodiment may be replaced with the configuration of another embodiment. Furthermore, the configuration of another embodiment may be added to the configuration of one embodiment. Furthermore, a part of the configuration of each embodiment may be added, deleted, or replaced with another configuration.

[0095] In addition, each of the above-mentioned configurations, functions, processing units, processing means, etc. may be realized in hardware, for example by designing some or all of them as an integrated circuit, or may be realized in software by a processor interpreting and executing a program that realizes each function.

[0096] Information such as programs, tables, and files that realize each function can be stored in a storage device such as a memory, a hard disk, or an SSD (Solid State Drive), or in a recording medium such as an IC card, an SD card, or a DVD.

[0097] In addition, the control lines and information lines shown are those considered necessary for the explanation, and do not necessarily show all the control lines and information lines necessary for implementation. In reality, it can be considered that almost all components are connected to each other. [Explanation of symbols]

[0098] 100 Equipment Repair Planning Optimization System 110 Application Section 120 Repair plan management function 121 Equipment Ledger Management Department 122 Repair Planning and Management Department 123 Inspection Results Management Department 124 Repair History Management Department 130 Communications Department 141 Equipment ledger database 142 Repair Plan Database 143 Inspection Results Database 144 Repair History Database 200 terminals 210 Web Browser 220 Communications Department

Claims

1. A facility management system that optimizes facility repair plans, The present invention includes a computing device that executes a predetermined computing process to realize each of the following functional units, and a storage device that stores information used in the computing process, An equipment ledger management unit that manages a ledger of the equipment; A repair plan management unit that calculates the next recommended repair date based on the number of days that have elapsed since the installation date of the equipment, The repair plan management unit recalculates the recommended repair date using the smaller value of the following: (a) the replacement cycle of the equipment minus the operating time measured during inspection of the equipment, divided by the operating rate of the equipment, and (b) the maximum period for which the equipment can be operated from the date of installation.

2. A facility management system for optimizing a facility repair plan, comprising: The present invention includes a computing device that executes a predetermined computing process to realize each of the following functional units, and a storage device that stores information used in the computing process, An equipment ledger management unit that manages a ledger of the equipment; A repair plan management unit that calculates the next recommended repair date based on the number of days that have elapsed since the installation date of the equipment, The repair plan management unit recalculates the recommended repair date using the smaller value of the following: (a) the average replacement cycle and operating time until repair of the equipment minus the most recent operating time measured at the time of inspection of the equipment, (b) the average value is divided by the operating rate of the equipment, and (c) the maximum period for which the equipment can be operated from the date of installation.

3. A facility management method in which a facility management system optimizes a facility repair plan, comprising: The facility management system includes a calculation device that executes a predetermined calculation process to realize each of the following functional units, and a storage device that stores information used in the calculation process, The facility management method includes: an equipment ledger management step in which the arithmetic device receives input of the equipment ledger and records it in the storage device; The calculation device includes a repair plan management step of calculating a next recommended repair date based on the number of days elapsed since the installation date of the equipment, An equipment management method characterized in that in the repair plan management step, the calculation device recalculates the recommended repair date using the smaller value between the replacement cycle of the equipment minus the operating time measured during inspection of the equipment, divided by the operating rate of the equipment, and the maximum period for which the equipment can be operated from the installation date.

4. A facility management method in which a facility management system optimizes a facility repair plan, comprising: The facility management system includes a calculation device that executes a predetermined calculation process to realize each of the following functional units, and a storage device that stores information used in the calculation process, The facility management method includes: an equipment ledger management step in which the arithmetic device receives input of the equipment ledger and records it in the storage device; The calculation device includes a repair plan management step of calculating a next recommended repair date based on the number of days elapsed since the installation date of the equipment, This equipment management method is characterized in that in the repair plan management step, the calculation device recalculates the recommended repair date using the smaller value of the following: a value obtained by subtracting the most recent operation time measured at the time of inspection of the equipment from the average value of the replacement cycle and operation time until repair of the equipment, divided by the operation rate of the equipment, or the maximum period for which the equipment can be operated from the date of installation.

5. A facility management program for optimizing a facility repair plan in a facility management system, comprising: The facility management system includes a calculation device that executes a predetermined calculation process to realize each of the following functional units, and a storage device that stores information used in the calculation process, The facility management program includes: an equipment ledger management procedure for receiving input of the equipment ledger and recording it in the storage device; A repair plan management procedure for calculating the next recommended repair date based on the number of days elapsed since the installation date of the equipment, The equipment management program is characterized in that the repair plan management procedure causes the calculation device to recalculate the recommended repair date using the smaller value of the following: the replacement cycle of the equipment minus the operating time measured during inspection of the equipment, divided by the operating rate of the equipment, and the maximum period for which the equipment can be operated from the date of installation.

6. A facility management program for optimizing a facility repair plan in a facility management system, comprising: The facility management system includes a calculation device that executes a predetermined calculation process to realize each of the following functional units, and a storage device that stores information used in the calculation process, The facility management program includes: an equipment ledger management procedure for receiving input of the equipment ledger and recording it in the storage device; A repair plan management procedure for calculating the next recommended repair date based on the number of days elapsed since the installation date of the equipment, The equipment management program, characterized in that the repair plan management procedure has the calculation device recalculate the recommended repair date using the smaller value of the following: a value obtained by subtracting the most recent operation time measured during inspection of the equipment from the average value of the equipment's replacement cycle and operation time until repair, divided by the operation rate of the equipment, or the maximum period of operation possible from the date of installation.

Images