Management device and facility equipment management method

Abstract

In a facility management system (1), a management device (3) stores the versions of control programs stored in respective one or more sets of facility equipment (2). In response to arrival of a predetermined timing, the management device (3) compares, for each of the one or more sets of facility equipment (2), the version of the control program stored in the management device (3) with a version specified by version information relating to a control program stored in a cloud server (4) to determine whether control program update is necessary. Then, the management device (3) downloads the control program from the cloud server (4) for facility equipment for which control program update is determined to be necessary.

Description

Management device and facility equipment management method

[0001] The present disclosure relates to management of equipment.

[0002] Buildings and other premises are generally equipped with equipment such as air conditioners and lighting, and it is becoming common for management devices to also be installed to manage these devices. The management devices monitor and control the equipment by communicating with the equipment via wired or wireless connections. As equipment has become more sophisticated in recent years, the programs tend to become more complex, and there has been an increasing number of cases in the market each year where on-site updates to equipment programs are required due to program malfunctions or security vulnerabilities.

[0003] Here, as an example of facility equipment, we will consider equipment installed on the ceiling or roof of each room in a building, such as the indoor and outdoor units of an air conditioner, and consider the work procedures that would be required if a program update were required for such facility equipment.

[0004] First, program update information (target model name, target version, update target version, reason for update, etc.) is published on the equipment manufacturer's website or elsewhere. The building's equipment management department obtains the program update information for the equipment, checks the model name and running program version of the equipment installed in the building, and confirms on the equipment manufacturer's website whether the version in question is eligible for update, and determines whether a program update is necessary. If a program update is necessary, the building's equipment management department contacts the equipment service company to arrange a schedule. The dispatched service technician then travels to the equipment's installation location (rooftop, attic, etc.) and performs the program update work. Because a series of tasks like this are required to update equipment programs, it often takes a lot of time and money.

[0005] Various studies have been conducted to solve these problems. For example, Japanese Patent Laid-Open Publication No. 2010-205152 (Patent Document 1) discloses a network system and a network adapter that make it easy to check information related to version upgrades of software (sub-software) executed by a sub-processing unit of a network adapter, and simplify the determination of the need for a version upgrade.

[0006] More specifically, in the system described in Patent Document 1, when a version check button is pressed on an operation terminal in the home, an upgrade confirmation request is sent to a center server. In response, the center server receives version information of the secondary software and determines whether an upgrade is necessary. If it determines that an upgrade is necessary, it transmits information regarding the upgrade to the network. The operation terminal displays a web page included in the upgrade confirmation response. When a user operates the operation terminal, a version upgrade start request is sent to the center server. In response, the center server receives the version upgrade start request. The center server then transmits upgrade information to the network adapter for upgrading the secondary software to version information newer than the version information received from the network adapter. In the network adapter, the main processing unit receives the upgrade information and outputs it to the sub-processing unit. The sub-processing unit rewrites the secondary software stored in the sub-storage unit based on the upgrade information.

[0007] JP 2010-205152 A

[0008] By applying the technology of Patent Document 1, the software version of facility equipment such as a network adapter can be easily confirmed, and the need for an upgrade can be easily determined. Furthermore, when a notification is received that the software needs to be upgraded, software upgrade information is downloaded from a server, which allows the facility equipment to easily update to the latest version.

[0009] However, even with the technology of Patent Document 1, updating the software of facility equipment requires user operation. In other words, as described above, in the system described in Patent Document 1, the process of determining whether an update is necessary begins only when the user presses a program version check button on the operation terminal. Therefore, even if a new version of a program that fixes a defect or improves functionality of the facility equipment is released, the need for a program update in the facility equipment will not be recognized unless a user of the latest version checks the version on the operation terminal. In this situation, there is a need for a technology that not only allows for simple and easy software updates for facility equipment, but also ensures user comfort and security.

[0010] The present invention has been made to solve the above-mentioned problems, and its purpose is to provide technology for updating software in facility equipment in a manner that not only makes it simple and easy to do so, but also ensures user comfort and security.

[0011] The present disclosure relates to a management device that manages one or more facility devices that make up a group of facility devices. The management device includes a storage device that stores versions of control programs stored in each of the one or more facility devices, a communication interface for communicating with a server that stores the control programs for the facility devices, and a controller that, upon the arrival of a predetermined timing, determines whether a control program update is required for each of the one or more facility devices by comparing the version of the control program stored in the storage device with a version identified by version information of the control program stored in the server. The controller downloads the control program from the server for facility devices that are determined to require a control program update.

[0012] According to another aspect of the present disclosure, there is provided a method for managing one or more facility devices that constitute a group of facility devices by a management device. The facility device management method includes a step of determining, in response to the arrival of a predetermined timing, whether a control program update is required for each of the one or more facility devices by comparing a version of a control program stored in a storage device of the management device with a version identified by version information of the control program stored on a server. The facility device management method also includes a step of downloading a control program from the server for facility devices determined to require a control program update.

[0013] According to the present disclosure, the management device determines whether a control program for an equipment device needs to be updated at a predetermined timing, and if it determines that an update is necessary, downloads the control program from a server. This allows the management device to download the latest control program from the server without requiring user operation. Therefore, it is possible to avoid a situation in which the download of the latest control program is delayed due to a user's failure to confirm, thereby jeopardizing user comfort and security.

[0014] 5 is a diagram showing a configuration of an equipment management system 1 according to an embodiment of the present disclosure. FIG. 6 is a block diagram showing a configuration of a management device 3 in embodiment 1. FIG. 7 is a block diagram showing a configuration of a cloud server 4 in embodiment 1. FIG. 8 is a diagram showing a flow of an update program check process executed by the management device 3 and the cloud server 4. FIG. 9 is a diagram showing a flow of a program update necessity confirmation process executed by the management device 3 and the cloud server 4. FIG. 10 is a diagram showing a flow of an update program download process executed by the management device 3 and the cloud server 4. FIG. 11 is a flowchart of a modified example of the program update necessity confirmation process of FIG. 5. FIG. 12 is a block diagram showing a configuration of a management device 3 in embodiment 2. FIG. 13 is a diagram showing a flow of an update program check process executed by the management device 3 and the cloud server 4. FIG. 14 is a diagram showing a flow of a program update necessity confirmation process executed by the management device 3 and the cloud server 4. FIG. 15 is a diagram showing a flow of a program download process executed by the management device 3 and the cloud server 4. FIG. 16 is a diagram showing a flow of a program update process executed by the management device 3.

[0015] Hereinafter, embodiments of the present disclosure will be described in detail with reference to the drawings. While multiple embodiments will be described below, it is anticipated from the beginning that the configurations described in each embodiment will be appropriately combined. Note that identical or corresponding parts in the drawings will be designated by the same reference numerals, and their description will not be repeated.

[0016] Embodiment 1 (Facility Management System) Fig. 1 is a diagram illustrating the configuration of a facility management system 1 according to an embodiment of the present disclosure. As shown in Fig. 1, the facility management system 1 includes facility equipment 2, a management device 3, and a cloud server 4. In the facility management system 1, multiple facility equipment 2 and multiple management devices 3 are provided.

[0017] The facility devices 2 and the management device 3 are connected via a dedicated communication line 5. This allows the facility devices 2 and the management device 3 to communicate with each other. A plurality of management devices 3 may be connected to each other via the dedicated communication line 5 so as to be able to communicate with each other.

[0018] The management device 3 and the cloud server 4 are connected via a communication line 6. This allows the management device 3 to communicate with the cloud server 4. The communication line 6 may be, for example, an Internet line that connects the cloud server 4 and the management device 3 via a broadband router. The communication line 6 may also be configured as a LAN (Local Area Network) that is connected to the management device 3 and the cloud server 4 within the same base.

[0019] Examples of the facility equipment 2 include various facility equipment installed in a building. More specifically, the facility equipment 2 is, for example, an air conditioning device, a lighting device, or a hot water supply device.

[0020] The plurality of equipment devices 2 are installed in designated locations within the building. Each equipment device 2 operates under the management of a management device 3. The operating status of the equipment devices 2 is notified to the management device 3 via a dedicated communication line 5. The plurality of equipment devices 2 connected to the same management device 3 will hereinafter also be referred to as an "equipment device group 7."

[0021] The management device 3 comprehensively manages a group of equipment 7 including multiple equipment devices 2. The cloud server 4 is a general-purpose computer that operates while connected to the Internet. The cloud server 4 stores program update information for each equipment device (information referenced for program updates, including information identifying the latest version) and registration information for the management device 3. The configuration of the management device 3 will be described below with reference to FIG. 2, and the configuration of the cloud server 4 will be described with reference to FIG. 3.

[0022] (Management Device) Fig. 2 is a block diagram showing the configuration of the management device 3 in embodiment 1. As shown in Fig. 2, the management device 3 includes a display device 10, an input device 20, a control unit 30, a data management unit 40, a program management unit 50, an equipment communication management unit 60, and a cloud communication management unit 70.

[0023] Under the control of the control unit 30, the display device 10 displays various screens for managing (monitoring and controlling) the facility device group 7 and for notifying the user.

[0024] The input device 20 is an input device such as a mouse, a keyboard, and / or a touch panel. When the input device 20 is a touch panel, the input device 20 is installed on the display device 10. By operating the input device 20, the administrator can realize various controls such as switching screens or operating facility equipment.

[0025] The control unit 30 is a computer including a CPU (Central Processing Unit), a memory, etc. In one implementation example, the CPU executes a program stored in the memory to realize the functions of the control unit 30. The control unit 30 is an example of a controller that controls the management device 3.

[0026] The control unit 30 holds (manages) the operating status of the facility equipment 2 and performs processing to send and receive data required for the monitoring screen displayed on the cloud server 4 .

[0027] The control unit 30 includes, as its functions, an equipment management unit 31 , a cloud connection management unit 32 , a program update determination unit 33 , a program update unit 34 , and a time management unit 35 .

[0028] The facility equipment management unit 31 manages (monitors and controls) the operating status of the facility equipment 2. In one implementation example, the facility equipment management unit 31 periodically collects, from each facility equipment 2, information on the operating status of the facility equipment 2 and version information on the control program stored (installed) in the facility equipment 2. If the facility equipment 2 is an air conditioning device, the operating status may be, for example, an operating / stopped state, an operating mode such as cooling or heating, a set temperature, an indoor temperature, and / or an operating schedule. In this specification, the "control program" may also be simply referred to as a "program."

[0029] The cloud connection manager 32 communicates with the cloud server 4. Specifically, the cloud connection manager 32 acquires program update information for the equipment 2 managed by the management device 3 (the management device 3 including the cloud connection manager 32) from the cloud server 4 at predetermined times. The predetermined times may be at regular intervals or may be one or more times (for example, 5:00 AM and 11:30 AM each day) scheduled in advance by an administrator or the like.

[0030] The cloud connection management unit 32 also receives an update program for the facility device 2 from the cloud server 4 and stores the received update program in the program management unit 50 as the facility device program 51 .

[0031] The program update determination unit 33 determines whether a program update is required for the facility devices 2 managed by the management device 3, based on the program update information received from the cloud server 4. Specifically, the program update determination unit 33 determines whether a program update is required for the facility devices 2 by comparing the version of the control program stored in the facility devices 2 with the version of the control program for the facility devices 2 specified in the program update information downloaded from the cloud server 4. The control program for the facility devices 2 is a program executed to control the facility devices 2. The program update information may include information indicating fixed defects and / or information about added functions in the latest programs of each facility device. The program update determination unit 33 may determine that a program update is required for the facility devices 2, provided that the information included in the program update information includes fixed defects or added functions.

[0032] In one example, the program update determination unit 33 determines that a program update in the facility device 2 is necessary if the version of the program stored in the facility device 2 is older than the version of the program downloaded from the cloud server 4, and determines that a program update in the facility device 2 is unnecessary if the version of the program stored in the facility device 2 is the same as or newer than the version of the program downloaded from the cloud server 4. Note that even if the program update determination unit 33 determines that a program update is necessary based on the version or the like, it may also determine that a program update is unnecessary if the program downloaded from the cloud server 4 is not suitable for a preset program update setting.

[0033] Information specifying the timing at which the program update determination unit 33 determines whether a program update is necessary is stored as a "check time" in the storage device of the management device 3. In other words, the determination of whether a program update is necessary is made at a predetermined timing. The "check time" is a component of time information 44, which will be described later. The check time may be set by the user or by the administrator of the equipment management system 1. Furthermore, in the equipment device group 7, the check time may be set for each equipment device 2, or may be common to all equipment devices 2.

[0034] When the program update determination unit 33 determines that a program update is necessary, it downloads an update program for the facility device 2 from the cloud server 4 .

[0035] The program update unit 34 updates the program. Specifically, the program update unit 34 updates the program of the facility device 2 via the dedicated communication line 5.

[0036] When it is determined that a program update is necessary in the facility device 2, the program update unit 34 may update the program of the facility device 2 without requiring any operation from the user. Furthermore, when it is determined that a program update is necessary in the facility device 2, the program update determination unit 33 may display a program update time setting screen on the display device 10 and update the program of the facility device 2 in response to an operation on the input device 20 by the user (at the timing set by the user).

[0037] The program update determination unit 33 may display a setting screen for the program update time on the display device 10. When displaying the setting screen, the program update determination unit 33 may calculate candidate program update times based on the equipment model information 41 and / or the operating state information 45, and present the candidates on the setting screen. There may be one or more candidates. When the program update information includes information indicating defects fixed in the latest program of each equipment and / or information about added functions, the program update determination unit 33 may display information indicating the defects and / or added functions on the setting screen.

[0038] An example of the calculated candidate time is a time included in a time period in which the facility equipment 2 is scheduled not to operate (to be stopped) in the operation schedule included in the operation status information 45. For example, if the operation schedule specifies that the facility equipment 2 is to be stopped from 1:00 AM to 4:00 AM, an example of the calculated candidate time may be a time included in that time period (1:00 AM to 4:00 AM). More specifically, the program update determination unit 33 may calculate a certain time (e.g., 5 minutes) after the start of that time period as a candidate time for the program update. Another example of the calculated candidate time may be one that takes into account the time required for the update program identified from the model name, model name, and / or serial number included in the facility equipment model information 41. For example, a time period in which the update is not expected to be completed by the time the facility equipment 2 starts operating in the operation schedule may be excluded from the candidates. For example, if the operation schedule specifies that the facility device 2 is stopped from 1:00 AM to 4:00 AM and resumes operation at 4:00 AM, and if the time required for a program update is calculated to be 20 minutes based on the data size of the update program, time slots after 3:40 AM (20 minutes before 4:00 AM) may be excluded from the candidates. More specifically, even if "3:00 AM," "3:15 AM," "3:30 AM," and "3:45 AM" are initially calculated as candidate program update times, "3:45 AM" may be excluded, and ultimately "3:00 AM," "3:15 AM," and "3:30 AM" may be presented as candidates. Furthermore, the candidates may represent start times for the update or may represent time slots that can be specified as start times. That is, a candidate may represent one or more times (e.g., "3:00 AM," "3:15 AM," and "3:30 AM"), or one or more time periods (e.g., "3:00 AM - 3:30 AM").

[0039] When displaying the program update time setting screen on the display device 10, the program update determination unit 33 may display the previous program update time of the facility device 2 based on the facility device program information 43. However, if there is no information to display, the program update determination unit 33 may display a message indicating that such information cannot be displayed.

[0040] The time management unit 35 manages time information (check time, program update time, etc.). Specifically, the time management unit 35 updates the time information, displays a screen for updating the time information on the display device 10, and accepts the setting of time information (check time and / or program update time) from the user. The time management unit 35 also detects when the check time or program update time has arrived.

[0041] In one implementation example, the data management unit 40 and the program management unit 50 are realized by a non-volatile storage device. The data management unit 40 stores equipment model information 41, system configuration information 42, equipment program information 43, time information 44, and operating status information 45.

[0042] The equipment model information 41 includes information about each equipment 2 (model name, model name, serial number, etc.).

[0043] The system configuration information 42 represents system configuration information of the facility device group 7. The system configuration information includes, for example, the installation location, address, program update settings, and connection mode with other management devices 3 of each facility device 2. The program update settings may specify conditions for updating the program of each facility device 2. For example, the program update settings may specify that a program update is necessary only if the program to be updated fixes a defect or if a new function is added to the program to be updated.

[0044] The facility device program information 43 represents program information of the facility device 2. The program information includes, for example, the latest program version of each facility device 2 and the update time of the previous program.

[0045] The time information 44 includes, for example, a confirmation time and a program update time for the facility device 2 .

[0046] The operating status information 45 includes various data required for the control unit 30 to monitor the facility equipment group 7, and various data for displaying a monitoring screen to the user. The operating status information 45 includes, for example, setting data and operating information of each facility equipment 2. The setting data includes, for example, an operation schedule, a program update time, and a time for transmitting information to the cloud server 4. If the facility equipment 2 is an air conditioning equipment, the operating information includes, for example, an operating / stopped state, an operating mode such as cooling or heating, a set temperature, an indoor temperature, and abnormality information.

[0047] The program management unit 50 includes a plurality of facility device programs 51. The facility device programs 51 are, for example, control programs for the facility devices 2. Specifically, the facility device programs 51 include programs downloaded from the cloud server 4 and written to each facility device 2 in the facility device group 7.

[0048] The facility equipment communication management unit 60 is a communication interface for communication via the dedicated communication line 5. The management device 3 transmits and receives data to and from the facility equipment 2 via the facility equipment communication management unit 60. The dedicated communication line 5 does not necessarily have to be a dedicated communication line, and may be a general-purpose communication line such as a LAN or an RS-485 interface.

[0049] The cloud communication management unit 70 is a communication interface for communication via the communication line 6. The management device 3 transmits and receives data to and from the cloud server 4 via the cloud communication management unit 70. The communication line 6 may be a wired LAN or a wireless LAN. The communication line 6 may also utilize an internet line or the like that connects the cloud server 4 and the management device 3 via a broadband router.

[0050] (Cloud Server) Fig. 3 is a block diagram showing the configuration of cloud server 4 in embodiment 1. As shown in Fig. 3, cloud server 4 includes a control unit 80, a data management unit 90, a program management unit 100, and an internet communication management unit 110.

[0051] In one implementation example, the control unit 80 is realized by a processor such as a CPU executing a given program. The control unit 80 includes, as its functions, a management device management unit 81, an Internet connection management unit 82, and a program information management unit 83.

[0052] The management device management unit 81 manages the management device 3. Specifically, the management device management unit 81 manages, for example, connection authentication of the management device 3 and communication response processing.

[0053] The internet connection management unit 82 communicates with the management device 3 registered in the management device registration information 91 to transmit the model-specific program update information 92 and each version of the program for the facility device 2 to the management device 3 .

[0054] The program information management unit 83 manages program information in the management device 3. Specifically, the program information management unit 83 instructs each management device 3 to add or delete programs stored in the program management unit 50, for example. The program information management unit 83 also updates model-specific program update information. In one implementation example, the model-specific program update information (information specifying a program to be stored by update for each model corresponding to each facility device 2) represents the latest version of the facility device program 101 stored in the program management unit 100, which will be described later.

[0055] In one embodiment, the data management unit 90 and the program management unit 100 are implemented by a non-volatile storage device. The data management unit 90 stores management device registration information 91, model-specific program update information 92, and model-specific frequent error information 93.

[0056] The management device registration information 91 includes information (e.g., a client ID for which connection is permitted, client certificate information, etc.) about the management device 3 registered in the cloud server 4. The management device 3 may be registered in the cloud server 4 when the management device 3 is manufactured or after the management device 3 is shipped.

[0057] The model-specific program update information 92 includes model-specific program update information. Specifically, the model-specific program update information includes, for the facility devices 2, model-specific program information (the latest version, function improvement information (whether or not a defect has been fixed, functions for which defects have been fixed, details of the fixed defect, whether or not a function has been added, details of the added function, etc.), the device number of the facility devices 2 that are the target of the program update, etc.), and / or defect information for each version. The model-specific program update information also includes information that identifies the version of the program stored in the program management unit 100. The model-specific program update information further includes information that specifies the latest program version for the management device 3.

[0058] The model-specific frequent abnormality information 93 includes information about functions to be improved, extracted from the management device registration information.

[0059] The program management unit 100 includes an equipment program 101 and a management device program 102 .

[0060] The facility device program 101 is a control program for the facility device 2. The program management unit 100 may store all versions of programs for each model as the facility device program 101, or may store the version of the program that should currently be installed in the facility device 2.

[0061] The management device program 102 is a control program for the management device 3. The program management unit 100 may store all versions of the management device program 102, or may store only the version of the program that should currently be installed in the management device 3.

[0062] The internet communication management unit 110 is an interface with the communication line 6. The cloud server 4 transmits and receives data to and from the management device 3 via the internet communication management unit 110.

[0063] (Operations During Program Update) Next, operations of the management device 3 and the cloud server 4 regarding program updates in the facility devices 2 will be described with reference to FIGS. 4 to 7. FIG.

[0064] (Update Program Check) FIG. 4 is a diagram showing the flow of update program check processing executed by the management device 3 and the cloud server 4. As shown in FIG.

[0065] When the time management unit 35 determines that the confirmation time has arrived, the cloud connection management unit 32 performs a program update necessity confirmation process (step S1a). In the program update necessity confirmation process, the cloud connection management unit 32 transmits equipment model information 41, system configuration information 42, equipment program information 43, and operating status information 45 to the cloud server 4 via the cloud communication management unit 70. The program update necessity confirmation process will be described in more detail below with reference to FIG. 5.

[0066] The process branches (step S1b) depending on the result of the determination in the program update necessity confirmation process (whether or not a program update is required in the facility device 2). If it is determined that a program update is not required in the facility device 2 (step S1b: No), the program update determination unit 33 ends the process in FIG.

[0067] If it is determined that a program update is required for the facility devices 2 (step S1b: Yes), the management device 3 downloads update programs for the facility devices 2 determined to require an update from the cloud server 4 (step S1c). In the program update necessity confirmation process, it is determined whether an update is required for each of one or more facility devices 2. In step S1c, update programs are downloaded for all facility devices 2 determined to require an update. The details of the program download process in step S1c will be described later with reference to FIG. 6.

[0068] Next, the program update determination unit 33 calculates candidate program update times (step S1d). In one implementation example, the calculation of the candidate update times is based on the equipment model information 41 and / or the operating status information 45. If it is determined that a program update is required for multiple equipment devices 2, candidate update times are calculated for each equipment device 2 in step S1d.

[0069] Next, the program update determination unit 33 notifies the user of the following three points (step S1e): If it is determined that a program update is required for multiple facility devices 2, the notification is made for each facility device 2 in step S1e.

[0070] The notification may include the following: - That a program update is necessary - Candidate program update times - Previous program update time The notification may be realized by displaying the above information on the display device 10, by notifying the user, or by both. The notification to the user is realized, for example, by the program update determination unit 33 sending the above information to a destination associated with the user (e.g., the user's email address). In this case, the storage device of the management device 3 stores a destination associated with the user (e.g., the user's email address) for each facility device 2.

[0071] Next, the program update determination unit 33 displays a setting screen for setting the program update time for the facility device 2 on the display device 10 and accepts the program update time setting from the user (step S1f). The program update determination unit 33 then ends the processing of Fig. 4. In step S1f, the program update determination unit 33 may display information on the fixed defects and / or information on the added functions, which are included in the program update information, on the setting screen.

[0072] In the process described above with reference to FIG. 4 , when a predetermined timing (confirmation time) arrives, the management device 3 determines whether or not a control program update is required for each of the facility devices 2 that make up the facility device group 7. If it is determined that an update of the control program of the facility device 2 is required, the management device 3 notifies candidates for the update time and accepts the update time setting from the user. Note that the management device 3 may set the update time without requiring setting from the user. In one implementation example, the management device 3 sets the time calculated as the candidate update time as the update time.

[0073] (Checking Whether Program Update is Necessary) FIG. 5 is a diagram showing the flow of a process for checking whether a program update is necessary, which is executed by the management device 3 and the cloud server 4. As shown in FIG.

[0074] When the program update necessity confirmation process (step S1a in FIG. 4) is started, the cloud connection management unit 32 of the management device 3 sends a program update version acquisition request for each model of facility device 2 to the cloud server 4 via the cloud communication management unit 70 (step S2a).

[0075] Subsequently, the Internet connection management unit 82 of the cloud server 4 receives the program update version acquisition request (step S2b).

[0076] Next, the program information management unit 83 reads the update program version and function improvement information for the model requested in the program update version acquisition request from the model-specific program update information 92 (step S2c). In the model-specific program update information 92, the update program version is stored as the latest program version for each model.

[0077] Next, the cloud server 4 transmits the version of the update program for the requested model to the management device 3 via the Internet connection management unit 82 and the Internet communication management unit 110 (step S2d). The update program that the cloud server 4 transmits to the management device 3 is an update program that is determined to be appropriate to transmit to the management device 3 based on information held by the cloud server 4 (information such as the model and program version of the equipment device 2 managed by the management device 3) and information sent from the management device 3 (equipment model information 41, system configuration information 42, and equipment program information 43). At this time, depending on the situation (the type of equipment device 2 managed by the management device 3, the types of other devices installed at the installation location of the equipment device 2 managed by the management device 3, etc.), the transmitted update program may not be the latest version.

[0078] Next, the management device 3 receives the version of the update program (step S2e), and then transmits a reception completion notification to the cloud server (step S2f).

[0079] Next, the program update determination unit 33 compares the version received from the cloud server 4 with the program version collected from the facility devices 2 for each model (step S2g).

[0080] Next, if there is a difference between the two versions compared in step S2g, the program update determination unit 33 determines that a program update in the facility device 2 is necessary (step S2h: Yes, step S2i). Note that even if there is a difference between the two versions, the program update determination unit 33 may determine that a program update is unnecessary if the difference is not suitable for the program update setting. On the other hand, if there is no difference between the program versions, the program update determination unit 33 determines that a program update in the facility device 2 is unnecessary (step S2h: No, step S2j) and ends the processing of FIG. 5.

[0081] If the facility device group 7 includes multiple models of facility devices 2, a program update version acquisition request is sent for each of the multiple models in step S2a. In this case, the version is sent for each of the multiple models in step S2d. Then, in step S2g, the program update determination unit 33 compares, for each model, the program version collected from the facility devices 2 with the version received from the cloud server 4, and in step S2h, determines for each model whether a program update is necessary.

[0082] (Downloading of Update Program) FIG. 6 is a diagram showing the flow of the process of downloading an update program, which is executed by the management device 3 and the cloud server 4. As shown in FIG.

[0083] When the program download process (step S1c in FIG. 4) is started, the cloud connection management unit 32 of the management device 3 sends an update program download request to the cloud server 4 via the cloud communication management unit 70 for the equipment device 2 that requires a program update (step S3a).

[0084] Subsequently, the Internet connection management unit 82 of the cloud server 4 receives the update program download request (step S3b).

[0085] Next, the cloud server 4 checks whether the requested version of the facility device program 101 exists in the program management unit 100 based on the model-specific program update information 92 (step S3c).

[0086] Next, if the requested version of the equipment program 101 does not exist (step S3d: No), the cloud server 4 notifies the management device 3 via the Internet connection management unit 82 and the Internet communication management unit 110 that the requested version of the program does not exist (step S3e), and terminates the processing of Figure 6.

[0087] Next, if the requested version of the equipment program 101 exists in the program management unit 100 (step S3d: Yes), the program information management unit 83 reads the requested equipment program 101 from the program management unit 100 as an update program (step S3f).

[0088] Next, cloud server 4 transmits the program (update program) read in step S3f to management device 3 via internet connection management unit 82 and internet communication management unit 110 (step S3g).

[0089] Next, when the management device 3 receives the update program (step S3h), it transmits a reception completion notification to the cloud server 4 (step S3i).

[0090] Next, the program update unit 34 updates the facility device program 51 in the program management unit 50 using the program received in step S3h (step S3j), and ends the processing of FIG.

[0091] (Program Update) FIG. 7 is a diagram showing the flow of a program update process executed by the management device 3.

[0092] When the time management unit 35 detects that the time for program update has arrived, the program update determination unit 33 determines whether or not the program update is possible for each of the equipment 2 requiring program update, based on the operating status of the equipment 2 collected by the equipment management unit 31 (step S4a). If the equipment 2 is an air conditioning equipment, the operating status may be, for example, an operating / stopped state, an operating mode such as cooling or heating, a set temperature, an indoor temperature, and / or an operating schedule.

[0093] In one implementation example, the criteria for the determination in step S4 a may be stored in the storage device of the management device 3 as setting data for a program for implementing the program update determination unit 33 .

[0094] An example of the criteria is that if the equipment is in operation or if the start time of the operation schedule of the equipment is within five minutes, it is determined that the program update for the equipment is not possible.

[0095] Another example of the criterion specifies that if the facility equipment is an air conditioning equipment, it is determined that the program update is possible even if the air conditioning equipment is in operation if the indoor temperature of the space to be regulated by the air conditioning equipment has reached the set temperature. In one implementation example, if the operation mode is cooling and the set temperature is 28°C, it is determined that the set temperature has been reached if the indoor temperature is 28°C or below. Also, if the operation mode is heating and the set temperature is 18°C, it is determined that the set temperature has been reached if the indoor temperature is 18°C ​​or above.

[0096] Next, the program update determination unit 33 determines whether the programs of all of the equipment 2 that require program updates can be updated (step S4b).

[0097] If all of the equipment devices 2 that require program updates are program updatable (step S4b: Yes), the program update unit 34 updates the programs of all of the equipment devices 2 that require program updates using update programs appropriate for each model (step S4c).

[0098] The program update unit 34 then transmits the post-update version information to the cloud server 4 (step S4d). The post-update version information indicates the version of the program installed after the update for the facility device 2 for which the program was updated. As a result, the cloud server 4 manages, as model-specific program update information 92, the latest control program version for each model, as well as the program version installed in each facility device 2. The program update unit 34 then terminates the processing of FIG. 7.

[0099] On the other hand, if not all of the facility devices 2 requiring program updating are program updatable (step S4b: No), the program update unit 34 confirms that there are facility devices 2 that are program updatable (step S4e).

[0100] If there is any facility device 2 whose program can be updated (step S4e: Yes), the program update unit 34 updates the programs of the facility devices 2 whose programs can be updated among the facility devices 2 that require program updating (step S4f).

[0101] Then, the program update unit 34 transmits, to the cloud server 4, the updated version information of the facility device 2 for which the program has been updated (step S4g).

[0102] Thereafter, the program update unit 34 notifies the user of the facility devices 2 that could not be updated (step S4h), and ends the processing in FIG. 7. Here, the program update unit 34 may prompt the user to set the update time for the control program again. When the program update unit 34 receives an update time setting from the user, it updates the control program according to the newly received update time.

[0103] If there are no facility devices 2 for which the program can be updated (step S4e: No), the program update unit 34 notifies the user of the facility devices 2 for which the update could not be performed (step S4h) and ends the processing in FIG. 7. The notification is achieved, for example, by displaying on the display device 10 and / or notifying the user. In step S4h, the program update unit 34 may prompt the user to set the program update time again. If the program update unit 34 receives an update time setting from the user, the program update unit 34 starts the processing in FIG. 7 in response to the arrival of the newly received update time.

[0104] In the process described with reference to FIG. 7, in response to a program update being performed on the equipment 2 (step S4c or step S4f), the equipment management unit 31 may register the time at which the update was performed as the “previous program update time” in the equipment program information 43 for the equipment 2 to be updated.

[0105] (Summary of the embodiment) In the above description, the management device 3 determines whether or not the control program of the facility device 2 needs to be updated. However, the cloud server 4 may determine whether or not the control program of the facility device 2 needs to be updated. In other words, the cloud server 4 may determine whether or not an update is necessary, and the management device 3 may perform the update.

[0106] In the above description, the management device 3 downloads only the control programs that require updating. However, the management device 3 may also download in advance one or more control programs stored in the cloud server 4 other than the programs that require updating.

[0107] In the above description, when the management device 3 completes reception of the program, it transmits a reception completion notification to the cloud server 4. Note that the management device 3 may continue processing without transmitting the reception completion notification.

[0108] In the above description, the program update time is set by the user in step S1f, etc. However, the program update time does not necessarily have to be set by the user; for example, a time set in advance by an administrator may be used as the program update time. Furthermore, the management device 3 may accept the setting of the update time for the control program of the facility device 2 from the user at any time other than the confirmation time.

[0109] In the above description, when downloading a program, the management device 3 downloads the program for each model of facility device 2, and the same program is not downloaded multiple times in a single download process. Note that the management device 3 may download the program for each facility device 2, thereby downloading the same program multiple times.

[0110] In the above description, the management device 3 downloads the update program from the cloud server 4. Note that if another management device 3 connected via the dedicated communication line 5 already stores the program version to be downloaded, the management device 3 may share the program from the other management device 3 via the dedicated communication line 5. More specifically, in step S1c, the management device 3 may download the update program from another management device 3 instead of downloading the update program from the cloud server 4. In this case, the management device 3 may send an inquiry to another management device 3 in the equipment management system 1 as to whether the update program is stored therein. Upon receiving a response from the other management device 3 indicating that the update program is stored therein, the management device 3 may download the update program from the other management device 3. The following effects, for example, can be expected from the management device 3 downloading the update program from another management device 3 rather than from the cloud server 4. That is, in the equipment management system 1, if communication between the management device 3 and the cloud server 4 is charged according to the amount of communication, but communication between management devices 3 is not charged according to the amount of communication, downloading from the other management device 3 can reduce costs. In this sense, the other management device 3 is an example of an "information processing device other than a server."

[0111] In the above description, notifications to and input from the user are made using the display device 10 and input device 20 included in the management device 3. Note that if the management device 3 does not include an LCD screen (display device 10, input device 20) and is monitored and operated using a web browser of a general-purpose computer connected to the management device 3 via a LAN, it is intended that notifications to and input from the user in the above description will be made using the display device and input device of the general-purpose computer.

[0112] Although not specifically mentioned in the above description, in order to perform monitoring and operation using the above-mentioned general-purpose computer, an application program for monitoring and operation using a web browser may be installed in the control unit 30 of the management device 3.

[0113] According to the facility management system 1 described above, the management device 3 automatically acquires update programs for the facility devices 2 from the cloud server 4 (without requiring instructions from the user). As a result, acquiring the update programs does not require the user to periodically check the update information. Furthermore, because the management device 3 determines whether or not a program update is necessary for the facility devices 2, the latest programs can always be applied to the facility devices without requiring the services of a service company.

[0114] According to the facility management system 1 described above, the user is notified that a program update is required in the facility equipment 2, thereby preventing the user from continuing to use the facility equipment 2 without knowing that an update program exists.

[0115] According to the facility management system 1 described above, it is possible to update the programs in the facility devices 2 at a timing that does not impair the comfort of the user.

[0116] According to the facility management system 1 described above, there is no need for an operator to go to the facility equipment 2 to update the program, which can reduce the burden of updating the program.

[0117] According to the facility management system 1 described above, candidates for program update times are presented, which can reduce the burden on the user in determining the program update times for the facility devices 2.

[0118] According to the facility management system 1 described above, it is possible to prevent the facility equipment 2 from stopping functioning due to the start of a program update while the facility equipment 2 is in operation.

[0119] In the facility management system 1 described above, notification of information is realized by display, but may be realized in other ways such as audio output, etc. Furthermore, input of information is realized by operating the keyboard of the input device or touching the screen, but may be realized in other ways such as audio input.

[0120] (Modification) Information on a function in which an abnormality has occurred in the facility device 2 may be used in determining whether or not a control program update is required in the facility device 2. Fig. 8 is a flowchart of a modification of the program update necessity confirmation process of Fig. 5 .

[0121] Regarding the modification of FIG. 8 , when the management device 3 transmits the operating state information 45 in step S1a in the process described with reference to FIG. 4 , the cloud server 4 may update the model-specific frequent abnormality information 93 using the abnormality information included in the operating state information 45. The abnormality information includes the type and number of occurrences of an abnormality that has occurred in each facility device 2. The cloud server 4 may calculate the cumulative number of occurrences for each type of abnormality using the abnormality information transmitted from the management device 3 (and abnormality information transmitted from the management device 3 in the past). Then, the cloud server 4 may update the calculated cumulative number of occurrences for each type of abnormality in the equipment model-specific frequent abnormality information 93. Each type of abnormality is related to the function of the facility device 2.

[0122] An example of a type of abnormality is "no destination" which is an abnormality related to the function "communication" of the facility device 2. "no destination" means that when the facility device 2 sends a message to another device, it receives an error indicating that the destination of the message does not exist. Another example is "receive unanalyzable content" which is an abnormality related to the function "communication" of the facility device 2. "receive unanalyzable content" means that the facility device 2 is unable to analyze the content of a message received from another device. Another example of a type of abnormality is "abnormal value acquired" which is an abnormality related to the function "sensor linkage" of the facility device 2. "abnormal value acquired" means that the facility device 2 has acquired an abnormal value from a sensor. Another example of a type of abnormality is "sensor value cannot be acquired" which is an abnormality related to the function "sensor linkage" of the facility device 2. "sensor value cannot be acquired" means that when the facility device 2 requests a detection value from the sensor, it is unable to acquire the detection value from the sensor even after a certain time has passed since the request.

[0123] Cloud server 4 may store, as a "frequent abnormality" a type of abnormality that has occurred a certain number of times or more among one or more types of abnormality, in model-specific frequent abnormality information 93, separately from the cumulative total. Furthermore, cloud server 4 may store, in equipment model-specific frequent abnormality information 93, a cumulative total of the number of occurrences of each type of abnormality (and frequent abnormalities) by model.

[0124] Compared with the process of FIG. 5, the process shown in FIG. 8 includes steps S2cx and S2dx instead of steps S2c and S2d, and further includes step S2hx.

[0125] In step S2cx of FIG. 8 , the program information management unit 83 reads the update program version, function improvement information, and model-specific program update information 92 for the model requested in the program update version acquisition request, and also reads frequent abnormalities from equipment model-specific frequent abnormality information 93.

[0126] In step S2dx of FIG. 8, the cloud server 4 transmits the update program version, function improvement information, and frequently occurring abnormalities for the requested model to the management device 3 via the Internet connection management unit 82 and the Internet communication management unit 110.

[0127] 8, if the program update determination unit 33 determines that there is a difference between the two versions compared in step S2g (step S2h: Yes), control proceeds to step S2hx. In step S2hx, the program update determination unit 33 reads the function improvement information transmitted from the cloud server 4 in step S2dx and identifies the functions included in the function improvement information. The program update determination unit 33 also reads the abnormality information transmitted from the cloud server 4 in step S2dx and identifies the functions included in the abnormality information. Then, the program update determination unit 33 determines whether the functions included in the function improvement information include the functions included in the abnormality information.

[0128] If the program update determination unit 33 determines that the functions included in the function improvement information include the functions included in the abnormality information (step S2hx: Yes), the control proceeds to step S2i. On the other hand, if the program update determination unit 33 determines that the functions included in the function improvement information do not include the functions included in the abnormality information (step S2hx: No), the control proceeds to step S2j.

[0129] In step S2i, it is determined that the program in the facility device 2 needs to be updated. On the other hand, in step S2j, it is determined that the program in the facility device 2 does not need to be updated.

[0130] In the modification example described above with reference to FIG. 8 , even if the update program downloaded from the cloud server 4 is a newer version than the control program currently installed in the facility device 2, it may be determined that a program update is not necessary. More specifically, the function improvement information in the update program includes information identifying functions whose defects have been fixed in the update program. If the function improvement information in the update program does not include a function whose defects have been fixed and whose malfunctions frequently occur in the facility device 2, it is determined that a program update is not necessary in the facility device 2. In other words, even if the update program downloaded from the cloud server 4 is a newer version than the control program currently installed in the facility device 2, it is determined that a program update is not necessary in the facility device 2 unless the update program fixes the malfunction in the function whose malfunctions frequently occur in the facility device 2.

[0131] Second Embodiment A second embodiment of the present invention will now be described in detail with reference to the drawings.

[0132] (Facility Management System) The configuration of the facility management system in the second embodiment is the same as the configuration of the facility management system 1 shown in FIG. 1 in the first embodiment.

[0133] (Management Device) Fig. 9 is a block diagram showing the configuration of the management device 3 in the second embodiment. As shown in Fig. 9, in the management device 3 in the second embodiment, compared to the management device 3 in the first embodiment, main body version information 46 is stored in the data management unit 40, and a management device program 52 is stored in the program management unit 50. In the second embodiment, updating of a program in the management device 3 will be described. In this specification, the program of the management device 3 (the program for controlling the management device 3) may be referred to as a "management program" or simply as a "program."

[0134] The main body version information 46 has program information of the management device 3. Specifically, the main body version information 46 indicates information such as the version of the program of the management device 3 and / or the time of the previous program update in the management device 3.

[0135] The management device program 52 includes a program for the management device 3 that is downloaded from the cloud server 4 .

[0136] (Operations During Program Update) Next, operations of the management device 3 and the cloud server 4 regarding program updates in the management device 3 will be described with reference to FIGS. 10 to 13. FIG.

[0137] (Update Program Check) FIG. 10 is a diagram showing the flow of update program check processing executed by the management device 3 and the cloud server 4. As shown in FIG.

[0138] When the time management unit 35 determines that the confirmation time has arrived, the cloud connection management unit 32 performs a program update necessity confirmation process by transmitting the equipment model information 41, system configuration information 42, operating status information 45, and main unit version information 46 to the cloud server 4 via the cloud communication management unit 70 (step S5a). The details of the program update necessity confirmation process will be described later with reference to FIG. 11. Note that in step S5a, the transmission of the equipment model information 41, system configuration information 42, and operating status information 45 may be omitted.

[0139] 10 branches according to the result of the program update necessity confirmation process, which determines whether or not a program update is necessary in the management device 3 (step S5b). If it is determined that a program update is unnecessary in the management device 3 (step S5b: No), the program update determination unit 33 ends the process in FIG.

[0140] If it is determined that a program update is required in the management device 3 (step S5b: Yes), the management device 3 downloads one or more update programs for the management device 3 from the cloud server 4 (step S5c) and executes the following procedure. The program download process is described in FIG. 6.

[0141] Next, the program update determination unit 33 calculates program update time candidates from the operation status (including operation schedules, etc.) of the equipment 2 collected by the equipment management unit 31 or the operation status information 45, and information contained in the operation status information 45 (including operation schedule information, etc.) (step S5d). In one implementation example, in step S5d, a time period during which none of the equipment 2 is expected to operate, or a time period during which management of none of the equipment 2 is expected to be unnecessary, is set as a program update time candidate based on the operation schedule information of each of the equipment 2 managed by the management device 3. An example of a time period during which management is expected to be unnecessary is the same day of the week and time period during which all of the managed equipment 2 were stopped in the information stored in the operation status information 45 for the past week. Another example can be identified based on the time information 44. More specifically, a time period during which program updates are scheduled for all of the managed equipment 2 can be set as a program update time candidate. Yet another example is a time period during which none of the equipment 2 are expected to be operating, identified based on the operation schedules of all of the managed equipment 2. Yet another example is a time period from the time when an environment occurs in which all of the equipment 2 do not need to operate (for example, in the case of air conditioning equipment, the room temperature meets the set temperature), which is identified based on "various data required for monitoring" of all of the equipment 2 to be managed, to the nearest operation start time specified in the operation schedule. Note that if a candidate includes a certain time period (time period A) and the length of time identified by that time period A is shorter than the length of time expected to be required for updating the program, that time period A may be excluded from the candidates.

[0142] Next, the program update determining unit 33 notifies the user of the following three points (step S5e).

[0143] The program update determination unit 33 then displays a program update time setting screen for the management device 3 on the display device 10, and accepts the program update time setting from the user (step S5f). Thereafter, the program update determination unit 33 ends the process of FIG. 10.

[0144] In the process described above with reference to FIG. 10 , when a predetermined timing (confirmation time) arrives, the management device 3 determines whether or not the management program of the management device 3 needs to be updated. If it is determined that the management program of the management device 3 needs to be updated, the management device 3 notifies candidates for the update time and accepts the update time setting from the user. Note that the management device 3 may set the update time without requiring setting from the user. In one implementation example, the management device 3 may set the time calculated as the candidate update time as the update time without requiring input from the user.

[0145] In the process described with reference to FIG. 10 , when the management device 3 transmits the operating status information 45 in step S5a, the cloud server 4 may update the model-specific frequent abnormality information 93 using the abnormality information included in the operating status information 45. The abnormality information includes the type of abnormality that has occurred in each facility device 2 and the number of occurrences. The cloud server 4 may calculate the cumulative number of occurrences for each type of abnormality using the abnormality information transmitted from the management device 3 (and abnormality information transmitted from the management device 3 in the past). The cloud server 4 may then update the calculated cumulative number of occurrences for each type of abnormality in the equipment model-specific frequent abnormality information 93. The cloud server 4 may store an abnormality that has occurred a certain number of times or more among one or more types of abnormality as a "frequent abnormality" in the model-specific frequent abnormality information 93, separately from the cumulative number. Furthermore, the cloud server 4 may store the cumulative number of occurrences (and frequent abnormalities) for each type of abnormality for each model in the equipment model-specific frequent abnormality information 93.

[0146] 11 is a diagram showing the flow of a program update necessity confirmation process executed by the management device 3 and the cloud server 4. When the program update necessity confirmation process (step S5a in FIG. 10) starts, the cloud connection management unit 32 of the management device 3 sends a program update version acquisition request for the management device 3 to the cloud server 4 via the cloud communication management unit 70 (step S6a).

[0147] The internet connection management unit 82 of the cloud server 4 receives the program update version acquisition request (step S6b). The program information management unit 83 reads the latest program version of the management device 3 from the model-specific program update information 92 (step S6c). The cloud server 4 transmits the latest program version of the management device 3 to the management device 3 via the internet connection management unit 82 and the internet communication management unit 110 (step S6d).

[0148] The management device 3 receives the latest version of the program of the management device 3 (step S6e), and transmits a reception completion notification to the cloud server 4 (step S6f).

[0149] Next, the program update determination unit 33 compares the version received in step S6e with the version of the program stored (installed) in the management device 3 (step S6g).

[0150] If there is a difference between the two versions compared in step S6g, the program update determination unit 33 determines that a program update is necessary (step S6h: Yes, step S6i). On the other hand, if there is no difference between the two versions, the program update determination unit 33 determines that a program update is not necessary (step S6h: No, step S6j), and ends the processing of FIG.

[0151] (Downloading of Update Program) FIG. 12 is a diagram showing the flow of a program download process executed by the management device 3 and the cloud server 4. As shown in FIG.

[0152] When the program download process (step S5c in FIG. 10) is started, the cloud connection management unit 32 of the management device 3 sends an update program download request for the management device 3 to the cloud server 4 via the cloud communication management unit 70 (step S7a).

[0153] The Internet connection management unit 82 of the cloud server 4 receives the update program download request (step S7b).

[0154] The cloud server 4 checks whether the requested version of the management device program 102 exists in the program management unit 100 based on the model-specific program update information 92 (step S7c).

[0155] If the requested version of the management device program 102 does not exist in the program management unit 100 (step S7d: No), the cloud server 4 notifies the management device 3 via the Internet connection management unit 82 and the Internet communication management unit 110 that the requested program version does not exist (step S7e), and terminates the processing of Figure 12.

[0156] If the requested version of the management device program 102 exists in the program management unit 100 (step S7d: Yes), the program information management unit 83 reads the requested version of the program (management device program 102) from the program management unit 100 as an update program (step S7f).

[0157] Subsequently, cloud server 4 transmits the update program read in step S7f to management device 3 via internet connection management unit 82 and internet communication management unit 110 (step S7g).

[0158] When the management device 3 receives the update program (step S7h), it transmits a reception completion notification to the cloud server (step S7i).

[0159] The program update unit 34 uses the update program received in step S7h to update the facility device program 51 in the program management unit 50 (step S7j), and ends the processing of FIG.

[0160] (Program Update) FIG. 13 is a diagram showing the flow of a program update process executed by the management device 3.

[0161] When the time management unit detects that the program update time has arrived, the program update determination unit 33 determines whether or not to update the program in the management device 3 (step S8a). In one implementation example, the program update determination unit 33 determines whether or not to update the program in the management device 3 based on the operating status of each of the managed facility devices 2 collected by the facility device management unit 31. If the facility device is an air conditioning device, the operating status includes, for example, an operating / stopped state, an operating mode (cooling / heating), a set temperature, an indoor temperature, and / or an operating schedule.

[0162] For example, if any of the one or more managed facility devices 2 is in operation, or if the start time of the operation schedule of any of the one or more managed facility devices 2 is within five minutes, it is determined that the program update is not possible. However, in the management device 3, if the managed object is an air conditioning device, various criteria may be set, such as allowing the program update even if the air conditioning device is in operation as long as all indoor temperatures to be adjusted by the operating air conditioning device have reached the set temperature.

[0163] The process of FIG. 13 branches depending on the result of the determination in step S8a. If it is determined that a program update is possible in the management device 3 (step S8b: Yes), the program update unit 34 performs a program update in the management device 3 (step S8c). In one implementation example, the program update involves installing the management device program 52 stored in the program management unit 50 in the management device 3. Thereafter, the program update unit 34 notifies the cloud server 4 that the program update is complete (step S8d), and terminates the process of FIG. 13. As a result, the cloud server 4 stores the updated program version in the management device 3 as management device registration information 91.

[0164] If the program update in the management device 3 is not possible (step S8b: No), the program update unit 34 notifies the user that the program update was not possible (step S8e) and ends the processing of FIG. 13. In step S8e, the program update unit 34 may prompt the user to set a program update time. The set new update time is stored in the time management unit 35. When the newly stored update time arrives, the program update unit 34 starts the processing of FIG. 13 again.

[0165] (Summary of the embodiment) In the second embodiment, the determination of whether or not the program in the management device 3 needs to be updated is performed by the management device 3, but this determination does not necessarily have to be performed by the management device 3. The cloud server 4 may manage version information of the program in the management device 3 and determine whether or not the program in the management device 3 needs to be updated.

[0166] In the second embodiment, only the programs that require updating are downloaded. However, the management device 3 may download in advance one or more programs, including the programs that require updating and the programs other than the programs that require updating, from among the programs stored in the cloud server 4.

[0167] In the second embodiment, the management device 3 transmits a reception completion notification to the cloud server 4 when reception is completed, but the reception completion notification does not necessarily have to be transmitted.

[0168] In the second embodiment, the program update time is set by the user, but it does not necessarily have to be set by the user. A predetermined time may also be used as the program update time. Furthermore, the program update time may also be set at a timing other than the confirmation time.

[0169] In the second embodiment, the update program is downloaded from the cloud server 4, but if the version of the program to be downloaded exists on another management device 3 connected via a dedicated communication line 5, the program may be shared from the other management device 3 via the dedicated communication line 5.

[0170] In the second embodiment, the management device program 52 stored in the program management unit 50 may be only the latest program, or may be the latest program and the program before the update. By storing the program before the update in the program management unit 50, the control unit 30 of the management device 3 can restore the state of the management device 3 to the state before the update by installing the program before the update in the management device 3 when unauthorized operation is detected after a program update.

[0171] In the first embodiment, a program update in the facility device 2 is described, and in the second embodiment, a program update in the management device 3 is described. The management device 3 may be configured to simultaneously update the programs in both the management device 3 and the facility device 2. In one implementation example, when the confirmation time arrives, the management device 3 starts the processes of Fig. 4 and Fig. 10 in parallel.

[0172] According to the facility management system 1 of the second embodiment, the management device 3 automatically acquires program update information for the management device 3 from the cloud server 4. This eliminates the need for the user to periodically check update information. Furthermore, the management device 3 determines whether a program update is necessary and updates the program of the management device 3 at an appropriate time. This makes it possible to always have the latest program applied to the management device 3 without having to request a service company.

[0173] According to the facility management system 1 of the second embodiment, a user can be notified that a program update is required for the management device 3. This can prevent the user from continuing to use the management device 3 without knowing that an update program for the management device 3 exists.

[0174] According to the facility management system 1 of the second embodiment, it is possible to update the program in the management device 3 at a timing that does not impair the user's comfort.

[0175] According to the facility management system 1 of the second embodiment, when updating a program in the management device 3, the user (worker) does not need to go to the site, and the burden of updating the program can be reduced.

[0176] According to the facility management system 1 of the second embodiment, candidates for program update times are presented, thereby reducing the burden on the user in determining the program update time in the management device 3.

[0177] According to the facility management system 1 of the second embodiment, the timing of updating the programs in the management device 3 is set based on the operation schedule of the facility devices 2, which makes it possible to more reliably implement measures to deal with malfunctions of the facility devices 2 even in an environment where it is not easy to stop the operation of the facility devices 2. In other words, it becomes possible to always install the latest programs in the management device 3, which makes it possible to more reliably prevent the facility devices 2 from stopping functioning (due to the programs in the management device 3 becoming outdated).

[0178] 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 by the description of the above embodiments, and is intended to include all modifications within the meaning and scope of the claims.

[0179] 1 Facility management system, 2 Facility equipment, 3 Management device, 4 Cloud server

Claims

1. A management device for managing one or more pieces of equipment constituting a group of equipment, A storage device for storing versions of the control programs stored in each of the one or more facility devices; A communication interface for communicating with a server that stores a control program for the facility device; a controller that, in response to the arrival of a predetermined timing, determines whether or not a control program needs to be updated by comparing, for each of the one or more facility devices, a version of the control program stored in the storage device with a version specified by version information of the control program stored in the server; The controller downloads a control program for the facility device for which it is determined that a control program update is required, The management device, in determining whether or not a control program needs to be updated, includes comparing, for each model of facility equipment, the version of the control program stored in the storage device with a version identified by version information of the control program stored in the server.

2. A management device for managing one or more pieces of equipment constituting a group of equipment, A storage device for storing versions of the control programs stored in each of the one or more facility devices; A communication interface for communicating with a server that stores a control program for the facility device; a controller that, in response to the arrival of a predetermined timing, determines whether or not a control program needs to be updated by comparing, for each of the one or more facility devices, a version of the control program stored in the storage device with a version specified by version information of the control program stored in the server; The controller downloads a control program for the facility device for which it is determined that a control program update is required, The management device, determining whether or not a control program update is necessary includes determining, for each model of facility equipment, whether or not functional improvement information of the control program stored in the server is suitable for a preset program update setting.

3. 3. The management device according to claim 1, wherein the controller notifies a user of an equipment device that a control program update is required by at least one of displaying the control program update on a display device and notifying the user of the equipment device that the control program update is required.

4. The management device according to claim 3 , wherein the controller further notifies candidates for a control program update time for the facility device for which a control program update is determined to be necessary.

5. A management device for managing one or more pieces of equipment constituting a group of equipment, A storage device for storing versions of the control programs stored in each of the one or more facility devices; A communication interface for communicating with a server that stores a control program for the facility device; a controller that, in response to the arrival of a predetermined timing, determines whether or not a control program needs to be updated by comparing, for each of the one or more facility devices, a version of the control program stored in the storage device with a version specified by version information of the control program stored in the server; The controller downloads a control program for the facility device for which it is determined that a control program update is required, The controller notifies the user of an equipment device that has been determined to require a control program update of the equipment device of the necessity of the update by at least one of displaying the control program on a display device and notifying the user of the equipment device of the necessity of the update; The controller further notifies candidates for a control program update time for the facility device for which a control program update is determined to be necessary, The controller calculates the candidates for each of the facility devices for which it is determined that a control program update is required, based on an operation schedule of each facility device.

6. The management device according to claim 1 , wherein the controller determines whether or not to update the control program for each of the facility devices for which it is determined that a control program update is required, based on the operating state of each of the facility devices.

7. the storage device stores a management program for controlling the management apparatus; The controller: determining whether or not an update of the management program in the management device is necessary by comparing a version of the management program stored in the storage device with a version specified by version information of the management program stored in the server in response to the arrival of the predetermined timing; 6. The management device according to claim 1, wherein, when it is determined that an update of the management program in the management device is necessary, the management device downloads the management program of the management device from the server.

8. A management device for managing one or more pieces of equipment constituting an equipment group, A storage device for storing versions of the control programs stored in each of the one or more facility devices; A communication interface for communicating with a server that stores a control program for the facility device; a controller that, in response to the arrival of a predetermined timing, determines whether or not a control program needs to be updated by comparing, for each of the one or more facility devices, a version of the control program stored in the storage device with a version specified by version information of the control program stored in the server; The controller downloads a control program for the facility device for which it is determined that a control program update is required, the storage device stores a management program for controlling the management apparatus; The controller: determining whether or not an update of the management program in the management device is necessary by comparing a version of the management program stored in the storage device with a version specified by version information of the management program stored in the server in response to the arrival of the predetermined timing; downloading the management program of the management device from the server when it is determined that the management program in the management device needs to be updated; A management device that calculates candidates for update times of the management program based on the operation schedules of each of the one or more facility devices.

9. A management device for managing one or more pieces of equipment constituting an equipment group, comprising: A storage device for storing versions of the control programs stored in each of the one or more facility devices; A communication interface for communicating with a server that stores a control program for the facility device; a controller that, in response to the arrival of a predetermined timing, determines whether or not a control program needs to be updated by comparing, for each of the one or more facility devices, a version of the control program stored in the storage device with a version specified by version information of the control program stored in the server; The controller downloads a control program for the facility device for which it is determined that a control program update is required, the storage device stores a management program for controlling the management apparatus; The controller: determining whether or not an update of the management program in the management device is necessary by comparing a version of the management program stored in the storage device with a version specified by version information of the management program stored in the server in response to the arrival of the predetermined timing; downloading the management program of the management device from the server when it is determined that the management program in the management device needs to be updated; A management device that determines whether or not to execute an update of the management program based on the operating status of each of the one or more facility devices.

10. The management device according to claim 1 , wherein the controller downloads a control program for an equipment device for which it is determined that a control program update is required from an information processing device other than the server.

11. The management device according to claim 4 , 5 , or 8 , wherein the candidates represent update start times or time periods that can be specified as update start times.

12. A management device for managing one or more pieces of equipment constituting a group of equipment, A storage device for storing versions of the control programs stored in each of the one or more facility devices; A communication interface for communicating with a server that stores a control program for the facility device; a controller that, in response to the arrival of a predetermined timing, determines whether or not a control program needs to be updated by comparing, for each of the one or more facility devices, a version of the control program stored in the storage device with a version specified by version information of the control program stored in the server; The controller downloads a control program for the facility device for which it is determined that a control program update is required, The controller determines whether or not a control program needs to be updated by comparing the types of functions in which abnormalities frequently occur in the one or more facility devices with the types of functions in which malfunctions have been corrected in the control program stored in the server.

13. A method for managing one or more pieces of equipment constituting an equipment group by a management device, comprising: a step of determining whether or not a control program needs to be updated by comparing, in response to the arrival of a predetermined timing, a version of a control program stored in a storage device of the management device with a version specified by version information of the control program stored in a server for each of the one or more facility devices; downloading a control program from the server for the facility equipment for which it has been determined that a control program update is required; A method for managing facility equipment, wherein the step of determining whether or not a control program needs to be updated includes comparing, for each model of facility equipment, the version of the control program stored in the storage device with a version identified by version information of the control program stored in the server.

14. A method for managing one or more pieces of equipment constituting an equipment group by a management device, comprising: a step of determining whether or not a control program needs to be updated by comparing, in response to the arrival of a predetermined timing, a version of a control program stored in a storage device of the management device with a version specified by version information of the control program stored in a server for each of the one or more facility devices; downloading a control program from the server for the facility equipment for which it has been determined that a control program update is required; The step of determining whether a control program needs to be updated includes determining, for each model of facility equipment, whether function improvement information for the control program stored in the server is suitable for a preset program update setting.

15. A method for managing one or more pieces of equipment constituting an equipment group by a management device, comprising: a step of determining whether or not a control program needs to be updated by comparing, in response to the arrival of a predetermined timing, a version of a control program stored in a storage device of the management device with a version specified by version information of the control program stored in a server for each of the one or more facility devices; downloading a control program from the server for the facility device for which it has been determined that a control program update is required; and notifying a user of the facility device that the control program of the facility device is determined to require updating of the control program of the facility device of the necessity of updating the control program by at least one of displaying the control program on the display device and notifying the user of the facility device of the necessity of updating the control program of the facility device. The step of notifying includes further notifying candidates for a control program update time for the facility device for which it is determined that a control program update is required, The facility equipment management method further comprises a step of calculating the candidates for each facility equipment determined to require a control program update, based on an operation schedule of each facility equipment.

16. A method for managing one or more pieces of equipment constituting an equipment group by a management device, comprising: a step of determining whether or not a control program needs to be updated by comparing, in response to the arrival of a predetermined timing, a version of a control program stored in a storage device of the management device with a version specified by version information of the control program stored in a server for each of the one or more facility devices; downloading a control program from the server for the facility device for which it has been determined that a control program update is required; a step of determining whether or not an update of the management program in the management device is necessary by comparing a version of the management program stored in the storage device with a version specified by version information of the management program stored in the server in response to the arrival of the predetermined timing; downloading the management program of the management device from the server when it is determined that the management program in the management device needs to be updated; and calculating a candidate update time for the management program based on an operation schedule of each of the one or more facility devices.

17. A method for managing one or more pieces of equipment constituting an equipment group by a management device, comprising: a step of determining whether or not a control program needs to be updated by comparing, in response to the arrival of a predetermined timing, a version of a control program stored in a storage device of the management device with a version specified by version information of the control program stored in a server for each of the one or more facility devices; downloading a control program from the server for the facility equipment for which it has been determined that a control program update is required; the storage device stores a management program for controlling the management apparatus; a step of determining whether or not an update of the management program in the management device is necessary by comparing a version of the management program stored in the storage device with a version specified by version information of the management program stored in the server in response to the arrival of the predetermined timing; downloading the management program of the management device from the server when it is determined that the management program in the management device needs to be updated; and determining whether or not to update the management program based on the operating status of each of the one or more facility devices.

18. A method for managing one or more pieces of equipment constituting an equipment group by a management device, comprising: a step of determining whether or not a control program needs to be updated by comparing, in response to the arrival of a predetermined timing, a version of a control program stored in a storage device of the management device with a version specified by version information of the control program stored in a server for each of the one or more facility devices; downloading a control program from the server for the facility equipment for which it has been determined that a control program update is required; The step of determining whether a control program needs to be updated further includes determining whether a control program needs to be updated by comparing a type of function in which an abnormality frequently occurs in the one or more facility devices with a type of function in which a malfunction has been corrected in the control program stored in the server.