JP6664343B2 - Software update management system and program - Google Patents

Description

  The present invention relates to a software update management system and a program, and in particular, to an update of software operating on equipment.

  2. Description of the Related Art Applications are distributed to terminals such as tablets and smartphones used by customers such as owners of buildings to be maintained, and services related to equipment in customer buildings are provided to customers. In order for the customer to successfully use the service using the distributed application, the version of software running on the facility equipment of the building needs to correspond to the distributed application. If not, it is necessary to update or newly install the software of the equipment. In the following description, the update and the new installation are collectively referred to as “update”.

  2. Description of the Related Art Conventionally, there has been proposed a technique of creating a software update schedule of equipment (controller) with reference to update results and building equipment operation schedules (for example, Patent Document 1).

JP-A-2015-191502 JP 2009-157597 A JP 2009-286600 A JP 2008-186392 A JP 2009-169524 A JP 2011-113391 A JP 2008-152332 A JP 2001-067225 A

  By the way, if the customer cannot use the above service, the customer cannot determine which equipment device software may be updated and at what timing the software device may be updated. The building management company manages the software of the equipment and the update thereof, and the software update is performed by another system (for example, an access control system when the update target is an air conditioner) or another customer (for example, the building There is a possibility that the control of equipment by another tenant in the case of a tenant building may be affected. Therefore, it is desired to update the software at an appropriate timing, for example, during a time period when equipment is not used much.

  Conventionally, a time zone that does not affect the control of the equipment is obtained by referring to the update results of the software and the control schedule of the equipment, and the software can be updated during the time. However, the control processing for operating the facility equipment includes control that is not set as a control schedule (for example, control that is executed in response to a customer operation or environmental change as a trigger) or internal processing of building equipment (for example, data aggregation processing). However, in the past, no consideration was given to the influence on control that does not appear in the software update record or the control schedule of the equipment.

  An object of the present invention is to update software in consideration of control that does not appear in a control schedule of equipment.

  A software update management system according to the present invention includes a control schedule information storage unit that stores control schedule information in which a schedule for controlling equipment is defined, and a scheduled update time and a required update time of software operating on the equipment. Receiving means for receiving update request information, state information obtaining means for obtaining state information indicating a state of a load applied to the equipment, update determining means for determining whether or not software can be updated, and instructions from the update determining means Update means for updating the software according to the update determination means, wherein the update determination means refers to the state information, and the update processing of the software at the scheduled update time is defined in the control schedule information. Indicate the degree of impact on not only defined controls but also undefined controls It includes influence calculation unit for calculating a degree of influence calculated degree of influence in the case of more than the predetermined threshold value is one that does not instruct the update of the software in the updating means.

  Further, in the control schedule information, a priority for each control of the equipment is set in advance, and the update determination unit determines that the software that has not been updated even when the scheduled update time has elapsed is updated. Includes a priority setting unit that sets the priority according to the elapsed time from the time, even if the influence of the software is equal to or greater than the threshold, and the priority of the software attempts to execute the update of the software. When the priority of the control to be executed redundantly is exceeded, the updating of the software is instructed to the updating means.

  In addition, the apparatus further includes a load model storage unit that stores a load model in which a time-series change of a load applied to the facility device is defined, and the update determination unit is configured such that, even if an influence degree of the software is equal to or more than a threshold value, When it is determined that the load on the equipment will increase in the future by referring to the load model, the update unit is instructed to update the software.

  A program according to the present invention provides a computer that can access a control schedule information storage unit that stores control schedule information in which a schedule for controlling equipment is defined, by updating scheduled time and required update time of software operating on the equipment. Receiving means for receiving update request information including, state information obtaining means for obtaining state information indicating a state of a load applied to the equipment, update determining means for determining whether or not software can be updated, and an instruction from the update determining means. It functions as updating means for updating the software accordingly.

  The update determination unit refers to the state information, and influences the update process of the software reaching the scheduled update time not only on the control whose schedule is defined in the control schedule information but also on the control not defined. And an influence degree calculation unit for calculating an influence degree indicating the degree of the influence. When the calculated influence degree is equal to or more than a predetermined threshold value, the update means is not instructed to update the software.

  According to the present invention, software can be updated in consideration of control that does not appear in the control schedule of equipment.

  Further, even when the software update is made to be on standby so as not to hinder the execution of the control, the software can be updated when the time elapsed from the scheduled update date and time becomes long.

  Also, even in a state where the load on the control device is high and hinders the execution of control, if the load on the control device further increases in the future, it is possible to update the software at this time. it can.

FIG. 1 is an overall configuration diagram showing an embodiment of a software update management system according to the present invention. FIG. 3 is a hardware configuration diagram of a computer mounted on building equipment according to the first embodiment. FIG. 2 is a block diagram of building equipment according to the first embodiment. 5 is a diagram illustrating an example of a data configuration of update request information registered in an update request information storage unit according to Embodiment 1. FIG. 5 is a diagram illustrating an example of a data configuration of control schedule information registered in a control schedule information storage unit according to Embodiment 1. FIG. 5 is a flowchart illustrating a software update process according to the first embodiment. 5 is a diagram illustrating an example of a data configuration of state information acquired in Embodiment 1. FIG. FIG. 9 is a block diagram of building equipment according to a second embodiment. FIG. 14 is a diagram illustrating an example of a data configuration of update request information registered in an update request information storage unit according to Embodiment 2. FIG. 13 is a diagram illustrating an example of a data configuration of control schedule information registered in a control schedule information storage unit according to Embodiment 2. 13 is a flowchart illustrating a software update process according to the second embodiment. FIG. 14 is a block diagram of building equipment according to a third embodiment. 15 is a flowchart illustrating a software update process according to the third embodiment.

  Hereinafter, a preferred embodiment of the present invention will be described with reference to the drawings.

Embodiment 1 FIG.
FIG. 1 is an overall configuration diagram showing an embodiment of a software update management system according to the present invention. FIG. 1 shows a remote monitoring center 1, a customer office 2, and a customer building 3. The customer office 2 is an office of a customer such as an owner of the customer building 3, and is provided with a customer terminal 20 that communicates with the remote monitoring center 1 via a customer network 4 such as a public line or the Internet. The customer terminal 20 is a terminal such as a personal computer (PC), a smartphone, or a tablet used by the customer. The customer building 3 is a building owned by the customer, and has one or a plurality of equipment (hereinafter, “building equipment”) 30 to be updated with software. The building facility 30 communicates with the remote monitoring center 1 via a facility network 5 such as a public line or the Internet. One or a plurality of building facilities 30 are installed in the customer building 3, but since each building facility 30 only needs to have a configuration described later, FIG. 1 shows only one building facility for convenience. Is shown.

  The remote monitoring center 1 is a facility of a building equipment maintenance company and monitors building equipment 30 installed in the customer building 3 from a remote place. Further, by distributing the application to the customer terminal 20, a service related to the use of the building equipment 30 of the customer building 3 owned by the customer is provided to the customer.

  The remote monitoring center 1 has a configuration in which a management terminal 11, a software management server 12, a customer information management server 13, a customer service server 14, and a building equipment management device 15 are connected via an intranet 16. The management terminal 11 includes a PC or the like used by an administrator who manages applications for customer terminals and software for building facilities in the remote monitoring center 1, and is used for management of software and various information. The software management server 12 is a server computer that holds and manages applications for customer terminals and software for building facilities. The customer information management server 13 is a server computer that holds and manages configuration information including the arrangement and software version of the building equipment 30 of the customer building 3. The customer service server 14 is a server computer that provides services to customers. For that purpose, the customer service server 14 downloads the customer terminal application to the customer terminal 20 in response to a request from the customer. Further, the customer service server 14 requests the building equipment management apparatus 15 to update the software in the building equipment 30 and further receives a notification that the software has been updated from the building equipment management apparatus 15, and uses the downloaded application for the customer terminal. Notify the customer that it is possible. The building equipment management device 15 is a server computer used for managing the building equipment 30. Specifically, control and state monitoring of the building equipment 30 are executed. Also, it manages software updates executed by the building equipment 30 itself in response to a software update request.

  FIG. 2 is a hardware configuration diagram of a computer mounted on the building equipment 30 in the present embodiment. In the present embodiment, a controller capable of updating software by itself and having the ability to execute the software is assumed. The controller is equipment that controls the operation of various facilities (not shown) such as connected air conditioners. A computer mounted on the controller can be realized by a general-purpose hardware configuration that has existed before. That is, the computer is configured by connecting a CPU 41, a ROM 42, a RAM 43, a hard disk drive (HDD) 44, and a network interface (IF) 45 provided as communication means to an internal bus 46 as shown in FIG.

  FIG. 3 is a block diagram of the building equipment 30 in the present embodiment. Note that components not used in the description of the present embodiment are omitted from the drawings. The building equipment 30 according to the present embodiment includes an update request receiving unit 31, a state monitoring unit 32, an update determination unit 33, a software update unit 34, a control unit 35, a software storage unit 36, an update request information storage unit 37, and control schedule information. It has a storage unit 38. The update request receiving unit 31 receives, from the remote monitoring center 1, update request information of software operating in the building equipment 30. The state monitoring unit 32 monitors the state of the load applied to the building equipment 30 and passes state information indicating the state to the update determination unit 33. The update determination unit 33 determines whether the requested software can be updated in response to the update request received by the update request reception unit 31. When it is determined that the update is possible, the software update unit 34 is instructed to update the software. The update request receiving unit 31 according to the present embodiment includes an influence degree calculating unit 331. The influence degree calculation unit 331 refers to the state information, and determines whether the software update processing reaching the scheduled update time affects not only the control whose schedule is defined in the control schedule information but also the control whose schedule is not defined. The degree of influence indicating the degree is calculated. The software update unit 34 updates the software according to an instruction from the update determination unit 33. The control unit 35 controls the software update process in cooperation with the components 31 to 34. Software to be updated is stored in the software storage unit 36.

  FIG. 4 is a diagram illustrating an example of a data configuration of update request information registered in the update request information storage unit 37 according to the present embodiment. The update request information acquired by the update request receiving unit 31 is registered in the update request information storage unit 37, and is deleted when the software update unit 34 executes the update. The update request information includes a U-ID, a building ID, a facility ID, a software name, a version, a required time, and an update request date and time. U-ID is identification information of update request information (record). The building ID is identification information of the customer building 3 that has received the update request information. The equipment ID is identification information of the building equipment 30 whose software is to be updated. In the present embodiment, since the update request information is stored for each building facility 30, the same identification information is set for each of the building ID and the facility ID. The software name is a name as information for specifying software to be updated, and the version indicates the version of the software after the update. The required time is the time required for updating the software. The update request date and time is a scheduled date and time at which execution of the update process of the software is started.

  FIG. 5 is a diagram illustrating an example of a data configuration of control schedule information registered in the control schedule information storage unit 38 according to the present embodiment. Update request information in which a schedule of control performed on the building equipment 30 is defined in advance is registered in the control schedule information storage unit 38. The operation control unit (not shown) controls the operation of the building equipment 30 or equipment such as an air conditioner connected to the building equipment 30 according to the control schedule. The control schedule information includes an SC-ID, a building ID, a facility ID, a control content, a set value, a start date and time, and an end date and time. SC-ID is identification information of control schedule information (record). The building ID and the facility ID are as described in the update request information. The control content is a name that specifies the content of the control to be performed. As the set value, a specific set value for performing the control is set. The start date and time and the end date and time are information for specifying the range of time for performing the control, and the start and end of the control are set.

  Each of the constituent elements 31 to 35 in the building equipment 30 is realized by a cooperative operation of a computer mounted on the building equipment 30 and a program operated by the CPU 41 mounted on the computer. Each of the storage units 36 to 38 is realized by the HDD 44 mounted on the building equipment 30. Alternatively, the RAM 43 or an external storage means may be used via a network.

  In addition, the program used in the present embodiment can be provided not only by communication means but also stored in a computer-readable recording medium such as a CD-ROM or a USB memory. The program provided from the communication means or the recording medium is installed in the computer, and various processes are realized by the CPU of the computer sequentially executing the program.

  When the customer terminal application or the building facility software is updated, the manager updates the software updated using the management terminal 11 and the correspondence information indicating the correspondence between the customer terminal application and the version of the building facility software. Register in the software management server 12. The customer operates the customer terminal 20 to obtain the customer terminal application from the customer service server 14 by downloading. The customer service server 14 refers to the correspondence information registered in the software management server 12 and the customer information registered in the customer information management server 13 to respond to the customer terminal application newly acquired by the customer. When recognizing that the version of the building equipment software is not installed in the building equipment 30 of the customer building 3 of the customer, the building equipment management apparatus 15 is requested to update the software of the building equipment 30. The building equipment management device 15 instructs the software update by transmitting update request information to the building equipment 30 in response to the request.

  When update request information is transmitted from the remote monitoring center 1, the update request receiving unit 31 acquires the information and registers the information in the update request information storage unit 37, thereby receiving a software update request.

  Next, a software update process according to the present embodiment will be described with reference to a flowchart shown in FIG.

  The update determining unit 33 reads one record from the update request information from the update request information storage unit 37 (Step 101). Here, the description will focus on one piece of read update request information. Similarly, the other update request information is read from the update request information storage unit 37 and subjected to the processing described later. The update determining unit 33 further reads out the control schedule information from the control schedule information storage unit 38 (Step 102).

  In the read update request information, the process waits until the scheduled update date and time of the software to be updated is reached (N in step 103), and when the scheduled update date and time is reached (Y in step 103), the update determination unit 33 sets the status monitoring unit 32. (Step 104). In the present embodiment, the processing is performed according to the above-described procedure. In step 101, the update determination unit 33 constantly compares the scheduled update date and time of the update request information with the current time. Alternatively, the corresponding update request information may be read.

  FIG. 7 is a diagram illustrating a data configuration example of the state information according to the present embodiment. The status information includes an S-ID, a building ID, a facility ID, a monitoring item name, a status, and an acquisition date and time. The S-ID is identification information of the state information (record). The building ID and the facility ID are as described in the update request information. The monitoring item name is a name indicating an item to be monitored. The status is the current status of the monitoring item. The status information in the first record indicates that the CPU load factor is 70%. The acquisition date and time is the date and time when the load status was acquired.

  Subsequently, the influence degree calculation unit 331 calculates the influence degree for the software whose scheduled update date and time is reached (Step 105). The degree of influence is an index that numerically indicates the effect on the building equipment 30 by executing the software update processing that reaches the scheduled update date and time. In the present embodiment, the degree of influence is calculated as follows. First, for the sake of simplicity, the description will focus on the CPU load factor.

  In the present embodiment, a threshold is set in advance to determine the presence or absence of the degree of influence. For example, it is assumed that a threshold value for the CPU load factor is set to 80%. Here, it is assumed that the CPU load factor detected from the state information is 70%. In this case, the degree of influence is 70%, which is lower than the threshold value (80%) (N in step 106). Therefore, the update determination unit 33 instructs the software update unit 34 to update the software. In response to this instruction, the software update unit 34 obtains a new version of the software from the remote monitoring center 1 and updates the software (step 107).

  On the other hand, if the CPU load ratio (degree of influence) detected from the state information is 90%, the threshold becomes (80%) or more (Y in step 106). The process returns to step 104 without instructing the updating unit 34. That is, steps 104 to 106 are repeated until the degree of influence falls below the threshold.

In the above description, the CPU load factor has been focused on for the sake of simplicity, but the information indicating the load of the building equipment 30 also includes various other information (monitoring items) such as a memory usage factor. . Therefore, in the present embodiment, the degree of influence is calculated by calculation. That is, assuming that the degree of influence is I, the degree of influence is calculated by the following equation.
I = a (tb−ta) + bLa

  Here, tb is the required time set in the update request information, ta is the time obtained from the start date and time of the control schedule information, and the time when the control is to be executed next from the current time for a certain control. (Start date and time). Here, the “certain control” corresponds to a control that is repeatedly executed when an attempt is made to execute the software update processing. Since the control and the software update process use (consume) the resources of the building equipment 30 together, if the software update process is executed at the scheduled update date and time, the existing control executed redundantly is affected. Because it could end up being La is load information obtained by quantifying the load on the building equipment 30 at the present time based on the acquired state information using a predetermined calculation formula. “a” and “b” are coefficients, which are appropriately set for each building facility 30 or for each type of building facility 30 (air conditioning, entrance / exit system, etc.).

  In the above formula, (tb-ta) indicates whether the software update process can be executed while the control defined in the control schedule information is not executed. If the required time tb of the software update is longer than the idle time ta during which the control is not executed, the execution of the control will be affected accordingly.

  In addition, the load information La is based on control not defined in the control schedule (for example, control performed by a customer operation or environmental change as a trigger) or internal processing of building equipment (for example, data aggregation processing). The load applied to the building equipment 30 is included. By calculating the degree of influence by adding the load information La, it is possible to consider a software update record or a control load that does not appear in the control schedule of the equipment when determining whether or not the software can be updated. Becomes If the value indicated by the load information La is relatively large even though the control defined in the control schedule is not executed, there is a possibility that the control not defined in the control schedule is executed. It can be estimated that there is. In other words, starting the update of the software may affect the execution of control not defined in the control schedule.

  In the above description, the CPU load factor has been used for simple description. However, the update determination unit 33 compares the impact calculated by the above-described equation in the impact calculation unit 331 with a predetermined threshold value, As described, it is determined whether the software can be updated. Note that the above calculation formula is an example, and it is not necessary to limit to this.

  When the calculated degree of influence falls below the threshold value (N in step 106), as described above, the software is updated according to the instruction from the update determination unit 33 (step 107).

  On the other hand, when the degree of influence is equal to or larger than the threshold (Y in step 106), steps 104 to 106 are repeated. However, it is conceivable that the load on the building equipment 30 will eventually drop and the degree of influence will eventually fall below the threshold. Although the scheduled update date and time may have passed, the software update can be executed at a timing that does not affect the execution of the control of the building equipment 30.

  As described above, according to the present embodiment, by considering the load on the building equipment 30, the software update process is defined not only in the control defined in the control schedule information but also in the control schedule information. The execution of the software update can be controlled in consideration of the influence on the control that is not performed. That is, according to the present embodiment, the software can be updated without affecting the operation and operation of the building equipment 30.

  When the software update is completed, the update request information corresponding to the software is deleted from the update request information storage unit 37 by the control unit 35 or the software update unit 34 under the control of the control unit 35. Then, the update of the software is notified to the customer via the remote monitoring center 1, whereby the customer knows that the customer terminal application can be used. As described above, according to the present embodiment, the customer can receive the service without being aware of the software to be updated in the building equipment 30 and the timing of updating the software.

  In the present embodiment, the update request information corresponding to the software whose update has been completed is deleted from the update request information storage unit 37. However, without deleting the update request information, the flag information indicating that the update has been completed or the update The end date and time may be recorded in association with the update request information.

Embodiment 2 FIG.
FIG. 8 is a block diagram of the building equipment according to the present embodiment. The same components as those in the first embodiment (FIG. 1) are denoted by the same reference numerals, and description thereof is omitted. In the present embodiment, a priority setting unit 332 is added to the update determination unit 33 shown in the first embodiment. The priority setting unit 332 sets the priority according to the elapsed time from the scheduled update time for software that has not been updated even at the scheduled update time. The hardware configuration of the building equipment 30 may be the same as in the first embodiment.

  FIG. 9 is a diagram illustrating an example of a data configuration of update request information registered in the update request information storage unit 37 according to the present embodiment. In the update request information in the present embodiment, the priority set and updated by the priority setting unit 332 is additionally set to the data configuration shown in the first embodiment (FIG. 4).

  FIG. 10 is a diagram illustrating an example of a data configuration of control schedule information registered in the control schedule information storage unit 38 according to the present embodiment. In the control schedule information in the present embodiment, the degree of setting is set in advance to the data configuration shown in the first embodiment (FIG. 5). The priority included in the control schedule information is a fixed value set corresponding to each control. A higher priority is set for a control that is to be executed according to a schedule without delay.

  Next, a software update process according to the present embodiment will be described using a flowchart shown in FIG. The same processing steps as those in the first embodiment are denoted by the same step numbers, and description thereof will be omitted as appropriate.

  As described above, when determining whether the software can be updated, the update determination unit 33 calculates the degree of influence with reference to the load state of the building equipment 30 (steps 101 to 105). Then, when the calculated degree of influence falls below the threshold value (N in step 106), the software is updated by an instruction from the update determination unit 33 as in the first embodiment (step 107).

  On the other hand, if the degree of influence is equal to or larger than the threshold (Y in step 106), the priority setting unit 332 in the present embodiment sets a priority for the software (step 201). Describing in more detail, 0 is set as the initial value of the priority of each software, and the priority is increased by 1 each time the elapsed time from the update request date and time of the software exceeds a predetermined threshold Ts. Go. For example, when the threshold value Ts is 5 minutes, the priority is updated so that the priority becomes higher as time elapses, such as 1 when 5 minutes have elapsed from the update request date and time and 2 when 10 minutes have elapsed. .

  When the priority is set, the update determination unit 33 refers to the required time of the software and the start date and time and the end date and time of the control schedule information, and temporarily updates the software from among the controls defined in the control schedule information. If it is attempted to execute the control, control that will be executed in duplicate with the software update process is extracted. The priority of the software is compared with the priority of the extracted one or more controls. If the priority of the software exceeds the priority of all the controls (N in step 202), the update determination unit 33 By instructing the software updating unit 34, the software is updated (step 107).

  On the other hand, if the priority of the software is equal to or lower than the priority of any of the controls (Y in step 202), the process returns to step 104 without giving a software update instruction. As a result, there is a possibility that the processing of steps 104 to 202 may be repeatedly executed. However, in step 201, the priority of the software increases with the lapse of time. , And the software will be updated.

  In the first embodiment, even if the degree of influence is equal to or more than the threshold, it is assumed that the load on the building equipment 30 will eventually decrease, and the degree of influence will eventually fall below the threshold. Decided to update. In the present embodiment, such an assumption is unnecessary. That is, if the load on the building equipment 30 is continuously higher than a certain level, the software cannot be updated. Therefore, in order to deal with such a case, the priority is set to software and control, and if software cannot be updated continuously, priority is given to control that may be executed repeatedly. Due to the degree, the software is updated when the priority of the software update processing becomes higher than the execution of the control. This may have a slight effect on the execution of the control, but it can be avoided from continuing from a state where the software update is not executed.

Embodiment 3 FIG.
FIG. 12 is a block diagram of the building equipment according to the present embodiment. The same components as those in the first embodiment (FIG. 1) are denoted by the same reference numerals, and description thereof is omitted. The hardware configuration of the building equipment 30 may be the same as in the first embodiment.

  This embodiment has a configuration in which a load model storage unit 39 is added to the configuration shown in the first embodiment. The load model stored in the load model storage unit 39 is model data in which a time-series change of a load applied to the building equipment 30 is defined, and is generated from a transition of a past load. For example, when a control with a high load is executed or a plurality of controls are executed at the same time, a load applied to the building equipment 30 increases. The load model includes not only the load transition but also information indicating the usage status of the building equipment 30 such as a time zone during control, or during maintenance or counting (for example, when a control program for daily report processing is operating). May be set in association with. The current usage status of the building equipment 30 may be acquired from the remote monitoring center 1.

  Next, a software update process according to the present embodiment will be described using a flowchart shown in FIG. The same processing steps as those in the first embodiment are denoted by the same step numbers, and description thereof will be omitted as appropriate.

  As described above, when determining whether the software can be updated, the update determination unit 33 calculates the degree of influence with reference to the load state of the building equipment 30 (steps 101 to 105). Then, when the calculated degree of influence falls below the threshold value (N in step 106), the software is updated by an instruction from the update determination unit 33 as in the first embodiment (step 107).

  On the other hand, when the degree of influence is equal to or greater than the threshold (Y in step 106), the update determination unit 33 in the present embodiment acquires the load model from the load model Is recognized (step 301). Here, when it is determined that the load on the building equipment 30 will increase in the future (Y in step 302), the software is updated by instructing the software updating unit 34 (step 107).

  On the other hand, if it is determined that the load applied to the building equipment 30 will not increase in the future (N in step 302), the process returns to step 104 without giving a software update instruction.

  In the first embodiment, even when the degree of influence is equal to or more than the threshold value, steps 104 to 106 are repeated on the assumption that the load on the building equipment 30 will eventually decrease. However, it is conceivable that the load applied to the building equipment 30 will rise rather than decrease.

  Therefore, in the present embodiment, by referring to the load model generated based on the past performance, if the load does not decrease from the current time, that is, if it is not expected that the impact falls below the threshold, the impact is set to the threshold. Even if it is above, I tried to update the software. In this way, it is possible to prevent the software update from continuing without being executed.

  In the above description, whether or not the software can be updated is determined by focusing only on the transition of the load. However, when information indicating the use status such as during control is added, the information may be further referred to to determine whether the software can be updated. For example, even if the load tends to increase in the future, if there is a time period during which maintenance is not performed immediately and no control is performed, the software update waits until that time. Alternatively, even if the load tends to decrease in the future, if the control is continued for a while after the present time, the software is updated at the present time during the maintenance. In this way, whether or not the software can be updated may be determined by referring to the past usage status of the building equipment 30 in addition to the transition of the load.

  In the present embodiment, a case has been described in which one load model is provided for convenience, but a plurality of load models may be prepared according to business days / holidays, seasons, and the like.

  Although the present embodiment has been described as a function added to the first embodiment, it may be implemented in combination with the second embodiment.

  By the way, other than the above-described embodiment, the present invention may be modified as follows. For example, the state monitoring unit 32 monitors the state of the load applied to the building equipment 30. In addition to this, specific software, specifically, software to be updated or software executed in cooperation with this software Alternatively, an operation state of control software or the like having a higher priority may be set as a monitoring target. Then, when the specific software is operating, the update of the software is waited.

  In each of the above embodiments, the threshold value to be compared with the degree of influence in step 106 is a fixed value. However, the set value may be changed according to time like a load model.

  Further, in each of the above-described embodiments, the update of the software of the building equipment 30 is controlled in the building equipment 30, but the update of the software of the building equipment 30 is performed by another device, for example, another device with a gateway. Control may be performed. When a plurality of building facilities 30 are installed in the customer building 3, the building management device that manages the plurality of building facilities 30 may be used. Alternatively, it may be performed from the remote monitoring center 1.

  In addition, when a plurality of building facilities 30 are installed in the customer building 3 and the plurality of building facilities 30 operate in cooperation with each other, the load of the other building facilities 30 is also taken into consideration, that is, the other building facilities 30 are considered. The degree of influence may be calculated by also referring to the state information. When the remote monitoring center 1 performs software update control, the load on the building equipment 30 of another customer building 3 may be considered. In this case, the software update in the customer building 3 of the remote monitoring center 1 is managed. In this case, the order of updating the software may be determined based on the calculated influence degree.

  Further, in the present embodiment, whether or not the software update in the building equipment 30 is allowed is automatically determined in the building equipment 30. However, a notification unit is provided in the building equipment 30 to inform the customer whether or not to update the software. An inquiry may be made.

1 remote monitoring center, 2 customer office, 3 customer building, 4 customer network, 5 facility network, 11 management terminal, 12 software management server, 13 customer information management server, 14 customer service server, 15 building facility management device, 16 intranet, 20 customer terminals, 30 building equipment, 31 update request receiving unit, 32 status monitoring unit, 33 update determination unit, 34 software update unit, 35 control unit, 36 software storage unit, 37 update request information storage unit, 38 control Schedule information storage unit, 39 load model storage unit, 41 CPU, 42 ROM, 43 RAM, 44 hard disk drive (HDD), 45 network interface (IF), 46 internal bus, 331 influence calculation unit, 332 priority setting unit.

Claims (4)

Control schedule information storage means for storing control schedule information in which a control schedule of the equipment is defined,
A receiving unit that receives update request information including a scheduled update time and a required update time of software operating on the equipment,
State information acquisition means for acquiring state information indicating the state of the load applied to the equipment,
Update determination means for determining whether the software can be updated;
Updating means for updating software according to an instruction from the update determining means,
Has,
The update determination unit includes:
A degree of influence indicating the degree of influence that the software update processing that reaches the scheduled update time affects not only the control whose schedule is defined in the control schedule information but also the undefined control with reference to the state information. Including an influence degree calculation unit for calculating
If the calculated degree of influence is equal to or greater than a predetermined threshold, the software update management system does not instruct the update unit to update the software. In the control schedule information, a priority for each control of the equipment is set in advance,
The update determination unit includes:
Including a priority setting unit that sets a priority according to an elapsed time from the scheduled update time for software that has not been updated even at the scheduled update time,
Even if the degree of influence of the software is equal to or greater than the threshold, if the priority of the software exceeds the priority of control that will be executed repeatedly when trying to update the software, the software The software update management system according to claim 1, wherein the software update management system is instructed to update the software. A load model storage unit that stores a load model in which a time-series change of the load applied to the equipment is defined,
Even if the degree of influence of the software is equal to or greater than a threshold value, the update determining unit determines that the load on the equipment will increase in the future by referring to the load model. The software update management system according to claim 1, wherein the instruction is issued. A computer that can access a control schedule information storage unit that stores control schedule information in which a schedule of control of the equipment is defined.
A receiving unit that receives update request information including a scheduled update time and a required update time of software operating on the equipment,
State information obtaining means for obtaining state information indicating a state of a load applied to the equipment,
Update determining means for determining whether software can be updated,
Updating means for updating software according to an instruction from the update determining means,
Function as
The update determination unit includes:
Influence calculation for calculating the influence of the software update processing reaching the scheduled update time on not only the control whose schedule is defined in the control schedule information but also the undefined control with reference to the state information. Part,
If the calculated degree of influence is equal to or greater than a predetermined threshold, the program does not instruct the updating means to update the software.

Images