Management apparatus and management method

Abstract

To make a user recognize a schedule for performing maintenance of equipment.SOLUTION: The management device 3 includes a memory 36 for storing a future maintenance time of the facility equipment 2, and a control device 30. The control device 30 determines an execution schedule for executing the maintenance of the facility equipment 2 based on the maintenance time. The control device 30 notifies the user of the facility equipment 2 of the execution schedule.SELECTED DRAWING: Figure 2

Description

[Technical Field]

[0001] The present disclosure relates to a management device and a management method. [Background technology]

[0002] For example, International Publication No. 2023 / 170780 (Patent Document 1) discloses a management device that determines the lifespan of air conditioner parts. This management device manages an inventory of replacement parts to be replaced with the parts based on the lifespan. [Prior art documents] [Patent documents]

[0003] [Patent Document 1] International Publication No. 2023 / 170780 Summary of the Invention [Problem to be solved by the invention]

[0004] Generally, operation of facility equipment (e.g., air conditioners) may be stopped for maintenance (e.g., part replacement). The above technology may cause a problem in that the user is unable to recognize the schedule on which maintenance of the facility equipment will be performed. Therefore, a problem may occur in that the user is unable to recognize the schedule on which the operation of the facility equipment will be stopped.

[0005] The present disclosure has been made to solve the above-mentioned problem, and its purpose is to make a user aware of the dates on which maintenance of facility equipment will be performed. [Means for solving the problem]

[0006] A management device according to the present disclosure manages facility equipment. The management device includes a memory that stores future maintenance dates for the facility equipment and a control device. The control device determines an execution schedule for performing maintenance on the facility equipment based on the maintenance date. The control device then notifies a user of the facility equipment of the execution schedule.

[0007] A management method disclosed herein is a method for managing facility equipment. The management method includes determining an execution schedule for performing maintenance on the facility equipment based on a future maintenance time for the facility equipment. The management method also includes notifying a user of the execution schedule. [Effects of the Invention]

[0008] According to the present disclosure, it is possible to make a user aware of the dates on which maintenance of facility equipment will be performed. [Brief explanation of the drawings]

[0009] [Figure 1] 1 is a diagram illustrating an example of the configuration of a management system according to an embodiment of the present invention; [Figure 2] FIG. 2 is a functional block diagram of a management device. [Figure 3] FIG. 10 is a diagram illustrating an example of a parts DB. [Figure 4] FIG. 4 is a diagram showing an example of an operation data DB. [Figure 5] FIG. 2 is a functional block diagram of a maintenance server. [Figure 6] FIG. 10 is a diagram illustrating an example of a worker DB. [Figure 7] FIG. 10 is a diagram illustrating an example of an inventory DB. [Figure 8] FIG. 10 is a diagram illustrating an example of a display image. [Figure 9] FIG. 10 is a diagram illustrating an example of a display image. [Figure 10] 10 is a flowchart of main processing executed by a management device. [Figure 11] FIG. 10 is a diagram for explaining the configuration of a second embodiment. [Figure 12] FIG. 10 is a diagram for explaining the configuration of a second embodiment. [Figure 13] FIG. 10 is a diagram for explaining the configuration of a third embodiment. DETAILED DESCRIPTION OF THE INVENTION

[0010] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. In the drawings, identical or corresponding parts are designated by the same reference numerals, and their description will not be repeated. It is also intended from the outset that at least some of the configurations in each embodiment may be used in appropriate combination.

[0011] Embodiment 1 [Management system configuration] Fig. 1 is a diagram showing an example of the configuration of a management system 1 according to this embodiment. The management system 1 includes at least one facility device 2, at least one management device 3, a maintenance server 4, and a network NW. The example shown in Fig. 1 discloses an example in which the management system 1 includes multiple facility devices 2 and multiple management devices 3.

[0012] The facility devices 2 and the management device 3 are communicatively connected via a communication line 5 (dedicated communication line). The management device 3 and the maintenance server 4 are communicatively connected via a network NW. The network NW is, for example, an internet line that connects the maintenance server 4 and the management device 3 via a broadband router.

[0013] The facility equipment 2 is various types of equipment installed in a facility (for example, a building). The facility equipment 2 is, for example, an air conditioner, a hot water supply device, a low-temperature device, and the like.

[0014] At least one equipment device 2 is installed in a designated location within the facility. The equipment device 2 operates under the management of a management device 3. The equipment device 2 transmits operation information indicating the operating status of the equipment device 2 to the management device 3 via a dedicated communication line 5. The management device 3 stores the operation information. Hereinafter, multiple equipment devices 2 connected to (corresponding to) one management device 3 will also be referred to as an "equipment device group 7" (see the dashed line in Figure 1). In this way, the management device 3 comprehensively manages the equipment device group 7 including multiple equipment devices 2.

[0015] The maintenance server 4 is a server that manages the maintenance of the facility devices 2. In this embodiment, "facility device maintenance" refers to "replacing parts included in the facility devices." By performing such part replacement work, it is possible to prevent the facility devices 2 from having to be replaced themselves, thereby shortening the downtime of the facility devices 2 while repairing and maintaining the facility devices 2. If the facility device is an air conditioner, the parts included in the facility devices are, for example, the compressor and fan of the air conditioner. The facility device maintenance may include other work, such as inspecting, cleaning, and lubricating the facility devices 2.

[0016] In this embodiment, identification information (management device ID (identification)) for identifying the management device is assigned to each of the multiple management devices 3. Similarly, an equipment device ID is assigned to each of the multiple equipment, and a part ID is assigned to each of the multiple parts.

[0017] In the following, the ID may be used as a reference symbol. For example, as shown in FIG. 3 described later, a part with a part ID of C1 may be referred to as "part C1."

[0018] Furthermore, the “user” in the present disclosure is, for example, a user of the management device 3. The user may also be defined as an “administrator” or “owner” of the management device 3. The user may also be a user of the facility device 2.

[0019] The management device 3 has, as its main hardware components, a CPU (Central Processing Unit) 35, a memory 36, and an interface 38. The CPU 35 executes various processes and calculations. The memory 36 includes a ROM (Read Only Memory) and a RAM (Random Access Memory), etc. The CPU 35, the memory 36, etc. constitute the "control device 30 (see FIG. 2)" of the present disclosure. The control device is also referred to as a control circuit. The CPU 35 may also be referred to as "at least one processor" or "control circuit."

[0020] The ROM stores the control program 37 executed by the CPU 35. The RAM temporarily stores data generated by the execution of the program in the CPU 35. The RAM can function as a temporary data memory used as a working area.

[0021] The interface 38 communicates with an external device of the management device 3 (for example, the facility device 2 or the maintenance server 4).

[0022] [Configuration of management device 3] 2 is a diagram (functional block diagram) for explaining the configuration of the management device 3. The management device 3 includes a display device 10, an input device 20, a control device 30, a memory 36, an equipment interface 50, and a network interface 60.

[0023] The display device 10 displays various screens (images). For example, the display device 10 displays various screens for managing the equipment group 7 (equipment 2), a parts replacement reservation screen (see FIG. 8 described later), and the like. The display device 10 is also referred to as a "display." The control device 30 communicates with the display device 10 to display various images on the display device 10.

[0024] The input device 20 accepts input from a user. The information accepted by the input device 20 is transmitted to the control device 30. The input device 20 is an input device configured from a mouse, keyboard, touch panel, etc. When the user operates the input device 20, the screen displayed by the display device 10 can be switched and facility equipment can be operated according to the operation content. Furthermore, the display device 10 and the input device 20 may be integrated to form a touch panel.

[0025] The control device 30 includes an equipment management unit 31, an exchange management unit 32, and a reservation management unit 33. The equipment management unit 31 manages the operating state of the equipment 2 through communication using the equipment interface 50 and the communication line 5. For example, if the equipment 2 is an air conditioner, the equipment management unit 31 controls the set temperature, air volume, etc. of the air conditioner.

[0026] The facility device 2 estimates future replacement times for parts of the facility device 2 based on predetermined information. The predetermined information is information for estimating future replacement times for parts, such as deterioration information for the facility device 2. The "future replacement time" indicates, for example, a time when the part may be replaced in the future. The replacement time corresponds to an example of the "maintenance time" in the present disclosure.

[0027] The deterioration information is information that indicates the degree of deterioration of the part by the facility equipment 2. The deterioration information is information that the facility equipment 2 uses to estimate the replacement time of the part. The deterioration information includes, for example, at least one of information on the accumulated operating time of the part, the number of starts and stops of the part, and the operating state of the facility equipment 2 that includes the part. The facility equipment 2 may also estimate the replacement time of the part using other methods (for example, AI (Artificial Intelligence)).

[0028] When the facility device 2 estimates the replacement time, it transmits replacement time information 91 indicating the replacement time to the management device 3. Then, the management device 3 stores, for each part ID, the replacement time of the part indicated by the part ID as a part DB 41 (FIG. 3 described later).

[0029] The memory 36 stores a parts DB (Data Base) 41 and an operation data DB 42. First, the parts DB 41 will be described. FIG. 3 is a diagram showing an example of the parts DB 41. As shown in FIG. 3, for each equipment ID, the types and numbers of all parts to be replaced (parts that can be replaced) included in the equipment 2 are stored. The example of FIG. 3 discloses an example in which equipment B1 includes D1 parts C1 and D2 parts C2.

[0030] Furthermore, the part DB 41 associates and defines information about each part with each part ID. This information about the part includes, for example, a replacement time indicating when the part should be replaced. The replacement time is estimated by the facility device 2 as described above.

[0031] Furthermore, the facility device 2 transmits to the management device 3, at the time of regular communication between the management device 3 and the facility device 2 (for example, at the time of the first communication), part information 92 (see FIG. 2) of parts to be replaced that are mounted on the facility device 2. This part information 92 is information that indicates the type and number of parts to be replaced. This allows the management device 3 to recognize the type and number of parts (parts that can be replaced) mounted on the facility device 2. The management device 3 generates part IDs and the like for the part DB 41 based on the type and number of parts to be replaced.

[0032] Furthermore, as will be described later, the replacement management unit 32 determines a tentative execution schedule based on the replacement timing. Here, the tentative execution schedule is a tentative schedule for when workers will replace parts of the equipment 2. A method for determining the tentative execution schedule will be described later. The tentative execution schedule corresponds to the "execution schedule" in the present disclosure. Furthermore, the "schedule" used in the "tentative execution schedule" or the like, or the "time" used in the maintenance timing or the like, may include a period from any first time to a second time that is later than the first time, etc.

[0033] Furthermore, the exchange management unit 32 proposes a tentative execution schedule to the user. This proposal corresponds to the display of a first image 101 in Fig. 8 described below. Then, when the user agrees to perform the exchange work on the tentative execution schedule and inputs that the exchange work will be performed on the tentative execution schedule (for example, when the Yes button image 102A is operated), the exchange management unit 32 stores this tentative execution schedule as a confirmed execution schedule.

[0034] On the other hand, if the user does not agree to perform the replacement work on the tentative execution schedule and inputs that the replacement work will not be performed on the tentative execution schedule (if the No button image 102B is operated), the replacement management unit 32, for example, accepts input of the replacement work schedule desired by the user from the user (see FIG. 9). Then, the replacement management unit 32 stores the accepted replacement work schedule as the confirmed execution schedule.

[0035] In the example of Fig. 3, it is specified that the replacement time for D1 parts C1 in facility device B1 is E1. Furthermore, in Fig. 3, it is specified that the tentative execution schedule for the replacement work of D1 parts C1 is F1, and the confirmed execution schedule for the replacement work is G1.

[0036] Although not specifically shown in Fig. 3, other information related to the part identified by the part ID is stored for each part ID. This other information includes operation time data of the part. The operation time data is, for example, data indicating the operation time of the part in chronological order.

[0037] Next, the operation data DB 42 will be described. The operation data DB 42 stores past operation data of the facility equipment 2. The future operation period of the facility equipment 2 includes a first period and a second period. The second period is a period in which the operation ratio of the facility equipment 2 is lower than that of the first period. Here, the operation ratio is a parameter indicating the degree of operation, and typically indicates the ratio of operation time in a unit period. For example, the unit period is set to one day. The second period includes a period in which the operation ratio is low and a period in which the operation period is zero.

[0038] 4 is a diagram showing an example of the operation data DB 42. In the operation data DB 42, operation data is defined for each facility device ID.

[0039] 4 shows an example in which whether or not an equipment device has operated in the past is associated with each equipment device ID. In general, the past operation state of the equipment device 2 and the future operation state of the equipment device 2 generally coincide. For example, the operation data DB 42 specifies that the equipment device B1 operates from Monday to Saturday and stops operating on Sundays. Therefore, it is highly likely that the equipment device B1 will operate from Monday to Saturday in the future and stop operating on Sundays.

[0040] The control device 30 identifies (estimates) a second period, which is a future period, based on past operation data. In the example of Fig. 4, for example, for the facility device B1, Monday to Saturday is estimated as the first period, and Sunday is estimated as the second period. The second period becomes candidate dates for the tentative execution schedule.

[0041] 4, the operation data mainly indicates whether the facility equipment is operating, but as a modified example, the operation data may be other data that can identify the second period. The other data may be, for example, data indicating at least one of the accumulated operation time of the facility equipment, the number of starts and stops of the facility equipment, and the amount of power consumed by the facility equipment.

[0042] [Maintenance Server] Fig. 5 is a diagram showing an example configuration of the maintenance server 4. In the example of Fig. 5, the maintenance server 4 includes a control device 70, a memory 80, and a network interface 90. The control device 70 includes a reservation management unit 71. The memory 80 also stores a worker DB 81, a user DB 82, a reservation DB 83, and an inventory DB 84. The inventory DB 84 corresponds to the "inventory information" of this disclosure.

[0043] The reservation management unit 71 acquires the replacement time from the management device 3 via the network interface 90. Upon acquiring the replacement time, the reservation management unit 71 transmits the information from a worker DB 81 and an inventory DB 84 (described later) to the management device 3. The management device 3 determines a tentative execution schedule based on the replacement time by referring to information corresponding to the worker DB 81 and information corresponding to the inventory DB 84.

[0044] Next, we will explain the worker DB 81. The worker DB 81 is a DB that stores the schedules of workers who perform maintenance (parts replacement) on the equipment 2. In other words, the worker DB 81 is a DB that indicates, for each worker ID, the level of availability of the worker identified by the worker ID.

[0045] FIG. 6 is a diagram showing an example of the worker DB 81. As shown in FIG. 6, a worker ID for identifying each of a plurality of workers is assigned. In the worker DB 81, the schedule of the worker identified from the worker ID is specified for each worker ID. In the example of FIG. 6, "◯" indicates that the worker's schedule is available, and "×" indicates that the worker's schedule is not available. For example, it is shown that worker A is available on September 1st, 3rd, and 5th, but is not available on September 4th and September 6th.

[0046] That is, the replacement management unit 32 of the management device 3 refers to the worker DB 81 (worker schedule) transmitted from the maintenance server 4. Then, the replacement management unit 32 determines a possible period during which the worker can perform the part replacement work for the equipment 2, by referring to the worker DB. The possible period is a period marked with "○" and corresponds to the "candidate dates for the tentative execution schedule" in parentheses in FIG. 6. In the example of FIG. 6, the reservation management unit 71 identifies September 1, September 3, and September 5 as the possible periods.

[0047] Although not specifically shown, the worker DB 81 may also specify, for each worker ID, personal information of the worker identified by the worker ID, and the details of the request that the worker is undertaking.

[0048] Although not specifically shown, the user DB 82 defines user information for each user (each management device 3) of the management device 3. The user information includes the user's name, etc. The user information also includes the management device ID of the user's management device, the equipment device IDs of all equipment devices 2 managed by the user's management device, all parts to be replaced in all equipment devices 2, and the number of parts to be replaced.

[0049] Although not shown in the figure, the reservation DB 83 stores, for each management device ID, the reservation details transmitted from the management device 3. The reservation details include, for example, the schedule for the part replacement work (the confirmed execution schedule in FIG. 3) and the number of replacement parts to be replaced in the part replacement work.

[0050] The inventory DB 84 is a DB that stores the inventory of parts to be replaced in the equipment 2. Fig. 7 is a diagram for explaining an example of the inventory DB 84. In the example of Fig. 7, the presence or absence of inventory of the part identified by the part ID is specified for each part ID.

[0051] For example, it is specified that part C1 will be out of stock from September 1st to September 4th, but will be in stock on September 5th and 6th.

[0052] That is, the replacement management unit 32 refers to the inventory DB 84 (inventory information) transmitted from the maintenance server 4. Then, the replacement management unit 32 determines the period during which the part to be replaced will be in stock (inventory period) by referring to the inventory DB 84. The inventory period corresponds to the "candidate dates for the tentative execution schedule" in parentheses in FIG. 7. In the example of FIG. 6, the replacement management unit 32 specifies September 5th and 6th as the inventory period for the replacement work using part C1.

[0053] The following describes a method for determining a tentative execution schedule by the replacement management unit 32 when it is estimated that the replacement time for D1 parts C1 of the equipment B1 is September 1st, the operation data DB 42 is as shown in FIG. 4, the worker DB 81 is as shown in FIG. 6, and the inventory DB 84 is as shown in FIG. 7.

[0054] Based on Fig. 4, the replacement management unit 32 specifies Sunday as the second period (a period when the operation ratio of the facility device B1 is low). Based on Fig. 6, the control device 30 specifies 9 / 3 (Wed), 9 / 5 (Fri), and 9 / 7 (Sun) as possible periods. Based on Fig. 7, the control device 30 specifies 9 / 5 (Fri) to 9 / 7 (Sun) as the inventory period.

[0055] The control device 30 then determines a common period for these specific details as the tentative execution schedule. Therefore, the control device 30 can determine as the tentative execution schedule a period when the operation ratio of the equipment B1 is low, the schedule of the equipment B1 worker is open, and replacement parts are in stock. In this example, Sunday, September 7th is determined as the tentative execution schedule.

[0056] In other words, a tentative execution period is determined to be a schedule that corresponds to the available period, the second period, and the inventory period. In this disclosure, the "schedule that corresponds to the period" typically includes the concept of one of at least one candidate schedule included in this period. In this way, the tentative execution period is a date after the replacement time.

[0057] [Display image] Next, an example of an image displayed by the display device 10 under the control of the control device 30 will be described. Fig. 8 is a diagram showing an example of a display image 150. The display image 150 includes a first image 101, a second image 102, a third image 103, and a fourth image 104. The display device 10 displays the first image 101, the second image 102, the third image 103, and the fourth image 104 on the same screen.

[0058] The first image 101 is an image showing the recommended replacement date. The recommended replacement date corresponds to the tentative execution date described above. In the example of Fig. 8, the tentative execution date is displayed as year B, month C, and date D.

[0059] The second image 102 is an image for receiving input from the user regarding whether or not the worker will perform the replacement work on the recommended replacement schedule (tentative execution schedule) shown by the first image 101. In the example of Fig. 8, the second image 102 includes a Yes button image 102A and a No button image 102B.

[0060] If the user agrees to the replacement work on the recommended replacement schedule (tentative execution schedule), the user operates the Yes button image 102A. On the other hand, if the user does not agree to the replacement work on the recommended replacement schedule, the user operates the No button image 102B. When the Yes button image 102A is operated, the management device 3 recognizes the tentative execution schedule as the confirmed execution schedule.

[0061] The third image 103 is an image showing the budget for maintenance (parts replacement work) of the facility equipment 2. The maintenance server 4 or the management device 3 calculates the budget by adding, for example, the price of the parts to be replaced and the labor costs of the workers.

[0062] The fourth image 104 is an image indicating that the current time has arrived a certain period of time before the maintenance time. The certain period of time is a predetermined period, for example, two weeks.

[0063] 9 is an example of a display image 152 displayed by the display device 10 when the No button image 102B is operated. The display image 152 includes a fifth image 105, a sixth image 106, and a decision button image 107.

[0064] The fifth image 105 is an image that allows the user to input a desired replacement work schedule. The fifth image 105 includes a text image that reads "Please enter the replacement work schedule" and an input area where the replacement work schedule is input. If the user desires a replacement work schedule that is different from the recommended replacement schedule shown in the first image 101, the user inputs the desired replacement work schedule into the fifth image 105.

[0065] The sixth image 106 is an image for preventing the replacement work from being carried out. The sixth image 106 is a text image that reads, "I do not want the replacement work carried out." There are cases where the user does not want the part replacement work carried out. In this case, the user operates the sixth image 106.

[0066] When a replacement work schedule is entered into the fifth image 105, or when the sixth image 106 is operated, and the user operates the decision button image 107, information indicating that the entered replacement work schedule or the replacement work will not be carried out is sent to the control device 30.

[0067] When the Yes button image 102A is operated on the display image 150, the control device 30 stores the recommended replacement schedule (tentative replacement schedule) on the first image 101 in the confirmed execution schedule of the part DB 41 of Fig. 3. Also, when the replacement work schedule is input by the user on the fifth image 105 of the display image 152, the control device 30 stores the input replacement work schedule in the confirmed execution schedule of the part DB 41 of Fig. 3.

[0068] Furthermore, when the sixth image 106 of the display image 152 is designated, the control device 30 stores information indicating that "no replacement work" is not performed in the confirmed execution schedule of the parts DB 41 in FIG. 3. The user's display device 10 or a display device (not shown) of the maintenance server 4 may be configured to display a history of past confirmed execution schedules. With this configuration, the user of the management device 3 or the administrator of the maintenance server 4 can check past confirmed execution schedules.

[0069] 8, a configuration has been described in which one recommended replacement schedule is proposed (displayed) by displaying the first image 101. However, a configuration in which a plurality of recommended replacement schedules are proposed (displayed) by displaying the first image 101 may also be adopted.

[0070] [flowchart] FIG. 10 is an example of a flowchart of the main processing (management method) executed by the management device 3. The management device 3 detects lifespan information related to the lifespan of a part from the operation data of the part, etc. The management device 3 also monitors the operating time of the part whose lifespan has been detected, and starts the processing of FIG. 10 for this part when the operating time is reached before a certain period of time has elapsed since the end of the part's lifespan. The lifespan information may be the lifespan of the part itself. Alternatively, the lifespan information may be the replacement time for the part. The lifespan information may be generated by the management device 3 or the facility device 2.

[0071] In step S2, the management device 3 acquires information indicating the replacement time and the part to be replaced transmitted from the facility device 2. Next, in step S4, the management device 3 stores the replacement time acquired in step S2 in association with the part ID of the part to be replaced acquired in step S2, as shown in the part DB 41 of FIG.

[0072] Next, in step S6, the management device 3 acquires the worker DB 81 (worker schedule) and the inventory DB 84 (inventory information of parts to be replaced) from the maintenance server 4.

[0073] Furthermore, in step S6, the management device 3 acquires, from the operation data DB 42 (see FIG. 4), the operation data of the facility device ID of the facility device for which the replacement time was transmitted in step S2.

[0074] Next, in step S8, the management device 3 refers to the operation data acquired in step S6 and determines whether there is a certain trend in the operation data. A certain trend in the operation data means, for example, as shown in Fig. 4, that there is a past period (first past period) corresponding to the above-mentioned first period and a past period (second past period) corresponding to the above-mentioned second period. In the example of Fig. 4, for facility device B1, the first past period is Monday to Saturday, and the second past period is Sunday.

[0075] If the determination in step S8 is YES, the process proceeds to step S10, and if the determination in step S8 is NO, the process proceeds to step S12.

[0076] In step S10, the management device 3 determines a period when replacement parts are in stock, the operation rate is low, and the worker can perform maintenance as the tentative execution schedule. In the above example, the tentative execution schedule is Sunday, September 7th.

[0077] On the other hand, in step S12, the tentative execution schedule is determined without using information related to the operation ratio. Specifically, the management device 3 determines the tentative execution schedule as a period during which replacement parts are in stock and workers are able to perform maintenance.

[0078] In step S14, the management device 3 displays the tentative execution schedule and the like determined in step S10 or step S12 on the display device 10. Specifically, the management device 3 generates image data corresponding to the first image 101 (an image showing the tentative execution schedule determined in step S10 or step S12) and the second to fourth images 102 to 104. Then, the management device 3 displays an image based on this image data (for example, display image 150 in FIG. 8 ) on the display device 10.

[0079] Next, in step S16, the management device 3 determines whether or not there is a request for replacement work from the user. If the user operates the Yes button image 102A in the second image 102 of the display image 150 displayed in step S14, or if the replacement work schedule is input into the fifth image 105 of the display image 152, the determination in step S16 is Yes. Also, if the sixth image 106 of the display image 152 is operated, the determination in step S16 is No.

[0080] If the determination in step S16 is Yes, in step S18, the management device 3 transmits the confirmed execution schedule to the maintenance server 4. This allows the manager or the like of the maintenance server 4 to recognize the confirmed execution schedule. At a later date, the manager or the like dispatches a worker carrying the part to be replaced to the location of the equipment 2 on the confirmed execution schedule. Then, the processing ends.

[0081] On the other hand, if the determination in step S16 is NO, the process of step S18 is not executed and the process of FIG. 10 ends.

[0082] If the user inputs a replacement work schedule in the fifth image 105 of Fig. 9, the management device 3 executes the process of Fig. 10 again to determine a new tentative execution schedule. Then, the management device 3 determines whether the replacement work schedule input by the user matches the new tentative execution schedule. If the replacement work schedule matches the tentative execution schedule, the management device 3 displays an image indicating the match (match image) on the display device 10. This match image is an image indicating that the replacement work schedule input by the user has been recognized by the management device 3 as the confirmed execution schedule.

[0083] On the other hand, if the replacement work schedule input by the user does not match the tentative execution schedule, the management device 3 may display an image (re-input image) for prompting the user to re-input the replacement work schedule on the display device 10. Furthermore, if the replacement work schedule input by the user does not match the tentative execution schedule, the management device 3 may display a tentative execution schedule (another schedule image) different from this replacement work schedule on the display device 10.

[0084] 9, the display device 10 may display the replacement work schedule, the matching image, the re-input image, the separate execution schedule image, etc. in a chat format. Specifically, the display device 10 displays the replacement work schedule, the matching image, the re-input image, the separate execution schedule image, etc. on the same screen. Therefore, the user can intuitively recognize the replacement work schedule, the matching image, the re-input image, the separate execution schedule image, etc.

[0085] [Summary] (1) As described above, the facility device 2 estimates the timing of maintenance (parts replacement in the above example) for the facility device 2 and transmits it to the management device 3. The management device 3 has a memory 36 that stores future maintenance times for the facility device. In the above example, the maintenance times are stored in the parts DB 41 of FIG. 3. The control device 30 also determines an execution schedule (tentative execution schedule in FIG. 3) for performing maintenance on the facility device 2 based on this maintenance time. The management device 3 then notifies the user of the facility device 2 of the execution schedule (see the first image 101 in FIG. 8).

[0086] According to this configuration, the management device 3 can make the user aware of the execution schedule for maintenance of the facility device 2. This can improve user convenience.

[0087] (2) Furthermore, as shown in the second image 102 of FIG. 8, the control device 30 receives input of information from the user regarding whether or not maintenance of the facility device 2 will be performed on the execution schedule (see the first image 101 of FIG. 8).

[0088] According to this configuration, the user can be made aware of the execution schedule of the facility device 2, and can input to the management device 3 whether or not maintenance will be performed on the execution schedule of the facility device 2. This improves user convenience.

[0089] (3) The control device 30 identifies a possible period during which the worker can perform maintenance on the equipment 2, based on the worker schedule in the worker DB of Fig. 6. Then, the control device 30 determines a schedule according to the possible period as the execution schedule.

[0090] With this configuration, a schedule that corresponds to a period during which the worker can perform maintenance on the facility equipment can be determined as the execution schedule, thereby preventing the worker from determining a schedule that the worker cannot perform from a scheduling perspective as the execution schedule.

[0091] (4) The future operation period of the facility equipment 2 includes a first period and a second period in which the operation ratio of the facility equipment 2 is lower than that of the first period. The control device 30 estimates the second period based on past operation data of the facility equipment 2 (see FIG. 4). The control device 30 then determines a schedule corresponding to the second period as the execution schedule.

[0092] With this configuration, the control device 30 can estimate a second period in which the operation ratio of the equipment 2 is lower than the first period, and determine a schedule corresponding to the second period as the execution schedule. Therefore, the period in which the operation ratio of the equipment 2 is low can be set as the maintenance schedule. Therefore, the impact of downtime of the equipment 2 can be reduced.

[0093] (5) Furthermore, the maintenance of the facility device 2 includes replacement of parts of the facility device 2. Furthermore, the memory 36 of the management device 3 stores part information related to parts of the facility device 2 (part information 92 in FIG. 2, part ID 41 in FIG. 3, etc.).

[0094] With this configuration, the management device 3 can recognize parts that can be replaced. (6) The management device 3 identifies an inventory period during which the part to be replaced is in stock, based on inventory information (see FIG. 7) indicating whether or not the part to be replaced of the facility device 2 is in stock. In the example of FIG. 7, for part C1, the period is from September 5th (Friday) to September 7th (Sunday). Then, the control device 30 determines a schedule according to the inventory period as the execution schedule.

[0095] With this configuration, the management device 3 can prevent itself from deciding on a period during which the part to be replaced is not in stock as the execution schedule.

[0096] (7) As shown in Fig. 8, the management device 3 displays a first image 101 and a second image 102 on the display device 10. The first image 101 is an image corresponding to the tentative execution schedule. The second image 102 is an image for receiving input from the user regarding whether or not to perform maintenance on the facility device 2 on the tentative execution schedule.

[0097] With this configuration, the user can input whether or not to perform maintenance while checking the tentative execution schedule in the first image 101. This improves user convenience.

[0098] (8) As shown in FIG. 8, the management device 3 displays the third image 103 indicating the maintenance budget for the facility device 2, the first image 101, and the second image 102 on the display device 10.

[0099] This configuration allows the user to be aware of the maintenance budget. (9) As shown in FIG. 8, the management device 3 displays on the display device 10 a fourth image 104 indicating that the execution date is a certain period before the scheduled execution date.

[0100] With this configuration, a user viewing the display can recognize that the current time is a certain period before the execution schedule.

[0101] Embodiment 2 In the above-described embodiment, the management device 3 is configured to determine a tentative execution schedule for one maintenance job. In the second embodiment, the management device 3 determines tentative execution schedules for multiple maintenance jobs.

[0102] FIG. 11 is a diagram illustrating a configuration for determining a tentative execution schedule according to the second embodiment. In the example of FIG. 11, the multiple maintenance tasks include a first maintenance task and a second maintenance task. Here, the first maintenance task and the second maintenance task are different types of maintenance tasks for the same equipment device 2. Here, the same equipment 2 may be the completely same equipment 2. The same equipment 2 may also be a plurality of equipment 2 included in the equipment group 7.

[0103] As described above, the first maintenance and the second maintenance are different maintenance. The different maintenance may include first concepts of different types of maintenance. In this case, for example, the first maintenance is the replacement of parts of the equipment 2, and the second maintenance is the cleaning of the equipment 2.

[0104] The different maintenance may include a second concept in which the type of maintenance is the same but the parts to be maintained are different. In this case, for example, for one piece of equipment, the first maintenance is the replacement of part C1, and the second maintenance is the replacement of part C2. FIG. 11 discloses an example in which the different maintenance includes the second concept.

[0105] Furthermore, the management device 3 determines candidate dates for each of the first maintenance and the second maintenance. Hereinafter, the candidate date for the first maintenance will also be referred to as the first candidate date, and the candidate date for the second maintenance will also be referred to as the second candidate date.

[0106] In the example of FIG. 11, the first candidate dates are September 5th and September 6th. The second candidate date is September 6th. September 5th corresponds to the "first execution date" of the present disclosure, and September 6th corresponds to the "second execution date" of the present disclosure.

[0107] In a case like that shown in FIG. 11, the management device 3 determines the second execution date (September 6th), which is an execution date common to the first candidate schedule and the second candidate schedule, as the tentative execution date for both the first maintenance and the second maintenance.

[0108] Generally, when the first maintenance and the second maintenance are performed on different dates, the maintenance costs may increase in terms of labor costs, etc. As a result, the efficiency of the first maintenance and the second maintenance may decrease.

[0109] In contrast, with the configuration of this embodiment, the management device 3 can determine, as the tentative execution schedule, a second execution schedule that allows the first maintenance and the second maintenance to be performed together, thereby improving the efficiency of the first maintenance and the second maintenance.

[0110] 11, the management device 3 can determine a second execution schedule that allows the first maintenance and the second maintenance, which are different types of maintenance, to be performed together, thereby improving the efficiency of maintenance.

[0111] FIG. 12 is a diagram illustrating another example of the second embodiment. In the example of FIG. 12, the multiple facility devices include a first facility device and a second facility device. In the example of FIG. 12, the first maintenance is maintenance for the first facility device, and the second maintenance is maintenance for the second facility device. Here, the second facility device is a facility device located within a certain range from the first facility device. For example, the second facility device is a facility device that is close in distance to the first facility device.

[0112] With this configuration, the management device 3 can determine, as a tentative execution schedule, a second execution schedule that allows for simultaneous maintenance of the first facility device and the second facility device, each of which is located within a certain range, thereby improving the efficiency of maintenance.

[0113] In the present embodiment, two maintenance tasks (first maintenance and second maintenance) have been described. However, the management device 3 may determine a tentative execution schedule for three or more maintenance tasks.

[0114] Embodiment 3 In the example of FIG. 8 described above, an example was described in which a recommended replacement schedule is proposed (displayed) by the first image 101. In the third embodiment, an example is described in which a recommended replacement schedule is displayed based on multiple criteria. Here, the criteria are information used by the management device 3 to determine at least one recommended replacement schedule. Here, an example in which the multiple criteria are a first criterion and a second criterion is mainly described.

[0115] 13 is an example of the display image 152 according to the third embodiment. The display image 152 includes a character image 420, a first reference image 421, a first schedule image 431, a second reference image 422, and a second schedule image 432.

[0116] The first reference image 421 is an image showing a first reference. In the example of Fig. 13, the first reference is low maintenance costs for the facility equipment. The second reference image 422 is an image showing a second reference. The second reference is low operation rates for the facility equipment.

[0117] As explained in the second embodiment, when the first maintenance and the second maintenance are performed together on the same execution schedule, the costs of the first maintenance and the second maintenance are lower than when the first maintenance and the second maintenance are performed on different execution schedules. The management device 3 determines at least one recommended replacement schedule in which the maintenance cost is lower than a threshold (satisfies the first criterion). The management device 3 also determines at least one recommended replacement schedule in which the operation ratio is smaller than a threshold (satisfies the second criterion).

[0118] 13, the management device 3 determines October 1, October 2, and October 3 as at least one tentative execution schedule based on the first criterion (satisfies the first criterion). Therefore, as shown in FIG. 13, the first schedule image 431 will be October 1, October 2, and October 3.

[0119] Furthermore, it is assumed that the management device 3 determines September 26th and September 27th as at least one tentative execution schedule based on the second criterion (satisfies the second criterion). Therefore, as shown in FIG. 13, the second schedule image 432 will be September 26th and September 27th.

[0120] The text image 420 is an image that prompts the user to specify (select) a fixed execution schedule from the tentative execution schedule shown in the first schedule image 431 and the tentative execution schedule shown in the second schedule image 432. The text image 420 in Fig. 13 is a text image that reads "Please select the exchange schedule below."

[0121] When a predetermined operation is performed by the user while displaying display image 150 (FIG. 8) of FIG. 8, management device 3 displays display image 154 of FIG. 13. Display image 154 may be included in display image 150. That is, display image 154 is displayed in step S14 of FIG. 10.

[0122] Then, when the user specifies either the tentative execution schedule shown in the first schedule image 431 or the tentative execution schedule shown in the second schedule image 432 (YES in step S16), the management device 3 recognizes the specified tentative execution schedule as the confirmed execution schedule and executes processing such as step S18.

[0123] 13, the management device 3 notifies the user of at least one execution schedule based on the first criterion and at least one execution schedule based on the second criterion. The user can then select an execution schedule that best suits their preferences from these execution schedules. This improves the user's freedom of choice.

[0124] Furthermore, the first criterion is low maintenance costs for the facility equipment 2, and the second criterion is low operation rates for the facility equipment 2. Therefore, the management device 3 allows the user to determine the execution schedule from the perspective of low maintenance costs and low operation rates.

[0125] [Variations] (1) In the above embodiment, the device that estimates the maintenance timing of the facility device 2 is the facility device 2 itself. However, the device that estimates the maintenance timing of the facility device 2 may be the management device 3 that manages the facility device 2. The processing when such a configuration is adopted will be described.

[0126] For example, the equipment 2 transmits the above-mentioned deterioration information of the equipment 2 to the management device 3 at regular intervals. The replacement management unit 32 acquires the deterioration information. Then, based on the deterioration information, the replacement management unit 32 estimates the future replacement time of the part corresponding to the deterioration information. In this way, the management device 3 (control device 30) may estimate the replacement time of all parts of all equipment 2 managed by the management device 3.

[0127] (2) In the above embodiment, the management device 3 is configured to display the first image 101 and the second image 102. However, the management device 3 may be configured to inquire of the user whether or not to perform the replacement work when the replacement time arrives before the predetermined period. This inquiry involves displaying an inquiry screen on the display device 10 to accept input of information indicating whether or not to perform the replacement work. Then, when the user inputs on this inquiry screen that the replacement work will be performed, the management device 3 determines a tentative execution schedule. On the other hand, when the user inputs on this inquiry screen that the replacement work will not be performed, the management device 3 ends the processing.

[0128] (3) In the example of FIG. 6, the entity performing the maintenance work is a worker (human). However, the entity performing the maintenance work may also include a work robot. In the example of FIG. 6, the worker ID includes the ID of the worker and the ID of the work robot.

[0129] (4) In the above embodiment, the management device 3 is configured to determine the tentative execution schedule using three pieces of information: the operation data in Fig. 4, the worker schedule in Fig. 6, and the inventory information in Fig. 7. However, the management device 3 may be configured to determine the tentative execution schedule using any one or two of these three pieces of information.

[0130] (5) At least one of the above processes of the management device 3 may be executed by another device. The other device may include the maintenance server 4. At least one of the above processes of the maintenance server 4 may be executed by another device. The other device may include the management device 3.

[0131] (6) In the above embodiment, the display device 10 is described as being included in the management device 3. However, the display device 10 may be separate from the management device 3. Furthermore, the display device 10 may be, for example, a terminal (such as a smartphone or tablet) that can be carried by the user of the management device 3.

[0132] [Note] (Item 1) A management device according to the present disclosure manages facility equipment. The management device includes a memory that stores future maintenance dates for the facility equipment, and a control device. The control device determines an execution schedule for performing maintenance on the facility equipment based on the maintenance date. The control device 30 then notifies the user of the facility equipment 2 of the execution schedule.

[0133] (Item 2) In the management device according to item 1, the control device receives an input from a user of the facility device regarding whether or not maintenance of the facility device will be performed on the execution schedule.

[0134] (Clause 3) In the management device described in paragraph 1 or 2, the control device identifies a possible period during which the worker or work robot can perform maintenance on the equipment based on the schedule of the worker or work robot performing maintenance on the equipment, and determines a date corresponding to the possible period as the execution date.

[0135] (4) In the management device according to any one of paragraphs 1 to 3, the future operation period of the facility equipment includes a first period and a second period in which the operation ratio of the facility equipment is lower than that of the first period. The control device estimates the second period based on past operation data of the facility equipment, and determines a schedule corresponding to the second period as the execution schedule.

[0136] (Item 5) In the management device according to any one of Items 1 to 4, the maintenance of the facility equipment includes replacement of a part of the facility equipment, and the memory stores information about the part of the facility equipment.

[0137] (Item 6) In the management device described in item 5, the control device identifies an inventory period during which the part to be replaced is in stock based on inventory information indicating whether the part to be replaced in the equipment is in stock, and determines a schedule corresponding to the inventory period as the execution schedule.

[0138] (Clause 7) A management device according to any one of clauses 2 to 6, wherein the control device communicates with a display, and the control device displays on the display a first image corresponding to an execution schedule and a second image for receiving input from a user regarding whether or not to perform maintenance on facility equipment on the execution schedule.

[0139] (Item 8) In the management device according to item 7, the control device displays a third image indicating a budget for maintenance of the facility equipment, the first image, and the second image on the same screen of the display.

[0140] (Item 9) In the management device according to item 7 or 8, the control device displays a fourth image on the display, which indicates that the execution date is a certain period before the execution date.

[0141] (Item 10) In the management device according to any one of items 1 to 9, the control device estimates a maintenance time and stores the maintenance time in a memory.

[0142] (Item 11) In the management device according to any one of Items 1 to 10, the maintenance of the facility equipment includes a first maintenance and a second maintenance. When the candidate schedule for performing the first maintenance includes the first execution schedule and the second execution schedule, and the candidate schedule for performing the second maintenance includes the second execution schedule, the control device determines the execution schedule for performing the first maintenance and the second maintenance as the second execution schedule.

[0143] (Item 12) In the management device according to item 11, the first maintenance and the second maintenance are different types of maintenance for the same facility device.

[0144] (Item 13) In the management device according to item 11, the facility devices include a first facility device and a second facility device located within a certain range of the first facility device. The first maintenance is maintenance of the first facility device, and the second maintenance is maintenance of the second facility device.

[0145] (Clause 14) A management device according to any one of clauses 1 to 13, wherein the control device notifies a user of the facility equipment of at least one execution schedule based on a first criterion, which is a criterion for determining the execution schedule, and at least one execution schedule based on a second criterion, which is a criterion for determining the execution schedule.

[0146] (Item 15) In the management device according to item 14, the first criterion is low maintenance costs for the facility equipment, and the second criterion is low operation rates for the facility equipment.

[0147] The embodiments disclosed herein should be considered to be illustrative in all respects and not restrictive. The scope of the present disclosure is defined by the claims, not the above description, and is intended to include all modifications within the meaning and scope of the claims. [Explanation of symbols]

[0148] 1 Management system, 2 Equipment equipment, 3 Management device, 4 Maintenance server, 5 Communication line, 7 Equipment equipment group, 10 Display device, 20 Input device, 30, 70 Control device, 31 Equipment equipment management unit, 32 Replacement management unit, 33, 71 Reservation management unit, 36, 80 Memory, 37 Control program, 38 Interface, 50 Equipment equipment interface, 60, 90 Network interface, 91 Replacement time information, 92 Part information, 101 First image, 102 Second image, 103 Third image, 104 Fourth image, 105 Fifth image, 106 Sixth image, 107 Decision button image, 420 Character image, 421 First reference image, 422 Second reference image, 431 First schedule image, 432 Second schedule image.

Claims

1. A management device for facility equipment, a memory that stores future maintenance times for the facility equipment; a control device; The control device determining an execution date for performing maintenance of the facility equipment based on the maintenance time; A management device notifies a user of the facility device of the execution schedule.

2. The management device according to claim 1 , wherein the control device receives, from a user of the facility equipment, an input from the user regarding whether or not maintenance of the facility equipment will be performed on the execution schedule.

3. the control device identifies a possible period during which the worker or the work robot can perform maintenance of the facility equipment based on a schedule of the worker or the work robot performing maintenance of the facility equipment; The management device according to claim 1 or 2, wherein a schedule corresponding to the available period is determined as the execution schedule.

4. The future operation period of the equipment is: The first period, and a second period in which the operation ratio of the facility equipment is lower than the first period, The control device estimating the second period based on past operation data of the facility equipment; The management device according to claim 1 or 2, wherein a schedule corresponding to the second period is determined as the execution schedule.

5. The maintenance of the facility equipment includes replacement of parts of the facility equipment, The management device according to claim 1 or 2, wherein the memory stores information relating to the parts of the facility equipment.

6. The control device Identifying an inventory period during which the part to be replaced is in stock based on inventory information indicating whether or not the part to be replaced of the facility equipment is in stock; The management device according to claim 5 , wherein the execution schedule is determined to be a schedule corresponding to the inventory period.

7. the controller is in communication with a display; 3. The management device according to claim 2, wherein the control device displays on the display a first image corresponding to the execution schedule and a second image for receiving input from a user regarding whether or not to perform maintenance on the facility equipment on the execution schedule.

8. The management device according to claim 7 , wherein the control device displays a third image indicating a maintenance budget for the facility device, the first image, and the second image on the same screen of the display.

9. The management device according to claim 7 or 8, wherein the control device displays a fourth image on the display, the fourth image indicating that the execution date is a certain period before the execution date.

10. 3. The management device according to claim 1, wherein the control device estimates the maintenance time and stores the maintenance time in the memory.

11. The maintenance of the facility equipment includes first maintenance and second maintenance, The control device, as described in claim 1 or claim 2, determines the execution date on which the first maintenance and the second maintenance are performed as the second execution date when the candidate dates on which the first maintenance is performed include the first execution date and the second execution date, and when the candidate dates on which the second maintenance is performed include the second execution date.

12. The management device according to claim 11 , wherein the first maintenance and the second maintenance are different types of maintenance for the same facility device.

13. The facility equipment includes a first facility equipment and a second facility equipment located within a certain range of the first facility equipment, the first maintenance is maintenance of the first facility device, The management device according to claim 11 , wherein the second maintenance is maintenance of the second facility device.

14. The control device 3. The management device according to claim 1, wherein the management device notifies a user of the facility equipment of at least one of the execution schedules based on a first criterion, which is a criterion for determining the execution schedule, and at least one of the execution schedules based on a second criterion, which is a criterion for determining the execution schedule.

15. The first criterion is low maintenance costs for the facility equipment, The management device according to claim 14 , wherein the second criterion is a small operation ratio of the facility equipment.

16. A method for managing facility equipment, comprising: determining an execution date for performing maintenance of the facility equipment based on a future maintenance time for the facility equipment; and notifying a user of the facility device of the execution schedule.

Images