Monitoring and control device and its control method

Abstract

The present invention provides a monitoring and control device and a control method that can suitably monitor and control building equipment installed in multiple buildings, while suppressing communication charges and without impose unnecessary data usage restrictions, thereby not compromising the ability to monitor building equipment. [Solution] The processor 111 sets a threshold for the amount of data to be sent and received between each of the multiple controllers 220 and the communication IF 113 for the current month. The sum of the thresholds for each of the multiple controllers 220 is a sum of thresholds smaller than the communication upper limit. If one of the multiple controllers 220 exceeds the threshold for the amount of data to be sent and received for the current month, the processor 111 makes the data reception cycle between the exceeding controller 220 and the communication IF 113 longer than the current reception cycle.

Description

Technical Field

[0001] The present disclosure relates to a monitoring and control device and a control method thereof.

Background Art

[0002] In a monitoring and control device such as a cloud server that monitors and controls building facilities installed in a building via a communication line, when the amount of data transmitted and received between a controller connected to the building facilities and the monitoring and control device exceeds the upper limit value (referring to the contract capacity; the same applies hereinafter) in one month, there are some cases where a contract is made with a communication carrier under a tariff system where the communication fee increases significantly. In such a case, in order to reduce the communication cost, there is a customer need to ensure that the amount of data transmitted and received in one month does not exceed this upper limit value.

[0003] For example, Japanese Patent Application Laid-Open No. 2019-102879 (Patent Document 1) discloses a communication control device that controls to reduce the frequency of some data communications when the difference between the upper limit value of the fixed fee set in the contract for the current month and the current communication data usage amount is below a threshold value.

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Summary of the Invention

Problems to be Solved by the Invention

[0005] In the aforementioned monitoring and control system, for example, if a customer owns multiple buildings, there are contracts that stipulate that communication charges will increase significantly if the total amount of data transmitted and received between all these buildings and the monitoring and control system exceeds an upper limit. In this case, control should be implemented to suppress the amount of data transmitted and received while considering the total amount of data transmitted and received generated in multiple buildings. However, the communication control system described in Patent Document 1 does not take into account such a scenario involving multiple buildings.

[0006] This disclosure was made to solve the aforementioned problems, and its purpose is to provide a monitoring control device and control method that can suitably monitor and control building equipment installed in multiple buildings without impose unnecessary restrictions on the amount of data transmitted and received, while suppressing communication charges and without impairing the ability to monitor building equipment. In this way, in this disclosure, firstly, in order to suppress the total amount of data transmitted and received each month (or to prevent the total amount from exceeding an upper limit), the "threshold" for activating communication restrictions in each building can be shared among multiple buildings, taking into account the usage status of the amount of data transmitted and received. Secondly, by taking into account the actual usage of the amount of data transmitted and received in the current month, it becomes possible to review the "threshold" for each building in the following month and beyond so that communication restrictions are not biased towards a particular building. [Means for solving the problem]

[0007] The monitoring and control device relating to this disclosure comprises a communication device and a processing device. The communication device transmits and receives data for monitoring or controlling multiple building facilities between multiple controllers, each installed in multiple buildings, and multiple building facilities connected to each of the multiple controllers. The processing device processes the data transmitted and received by the communication device. The charges are set such that the communication charges for the current month increase if the sum of the amount of data transmitted and received between the communication device and each of the multiple controllers for the current month exceeds a first amount. The processing device sets a threshold for the amount of data transmitted and received between each of the multiple controllers for the current month. The sum of the thresholds for each of the multiple controllers is a second amount, which is smaller than the first amount. If an excess controller occurs among the multiple controllers, which is a controller whose amount of data for the current month exceeds the threshold, the processing device lengthens the data reception cycle between the excess controller and the communication device compared to the current reception cycle. By lengthening the data reception cycle compared to the current reception cycle, the total amount of data transmitted and received each month can be suppressed.

[0008] The control method relating to this disclosure is a control method for a monitoring and control device comprising a communication device and a processing device. The control method comprises the steps of: a communication device sending and receiving data for monitoring or controlling a plurality of building facilities between a plurality of controllers, each installed in a plurality of buildings, and a plurality of building facilities connected to each of the plurality of controllers; and a processing device processing the data sent and received by the communication device. The charges are set such that the communication charges for the current month increase if the sum of the amount of data sent and received between the communication device and each of the plurality of controllers for the current month exceeds a first amount. The processing step includes setting a threshold for the amount of data to be sent and received between each of the plurality of controllers for the current month. The sum of the thresholds in each of the plurality of controllers is a second amount, which is smaller than the first amount. The processing step further includes, if an excess controller occurs among the plurality of controllers, which is a controller whose amount of data for the current month exceeds the threshold, the step of making the data reception cycle between the excess controller and the communication device longer than the current reception cycle. [Effects of the Invention]

[0009] According to this disclosure, it is possible to suitably monitor and control building equipment installed in multiple buildings while suppressing communication charges and without impose unnecessary restrictions on the amount of data transmitted and received, thus not compromising the ability to monitor building equipment. [Brief explanation of the drawing]

[0010] [Figure 1] This figure shows an example of the overall configuration of the monitoring and control system according to this embodiment. [Figure 2] This figure shows an example of the hardware configuration of a monitoring and control system. [Figure 3] This table explains user operation history and data reception cycles. [Figure 4] This table explains user operation history and data reception cycles. [Figure 5] This diagram illustrates the changes in data traffic due to standalone control processing. [Figure 6] This is a flowchart of the standalone control process. [Figure 7] This diagram illustrates the changes in data traffic due to multiple control processes. [Figure 8] This is a diagram to explain the method of allocating thresholds. [Figure 9] This is a flowchart of multiple control processes. [Figure 10] This diagram explains how to determine the current month's threshold candidate based on the previous month's performance. [Figure 11] This is a flowchart of the threshold setting process. [Modes for carrying out the invention]

[0011] The embodiments will be described below with reference to the drawings. In the following description, identical parts are denoted by the same reference numerals. Their names and functions are also the same. Therefore, detailed descriptions of them will not be repeated.

[0012] First, the monitoring and control system 1 according to the present embodiment will be described. FIG. 1 is a diagram showing an example of the overall configuration of the monitoring and control system 1 according to the present embodiment.

[0013] As shown in FIG. 1, the monitoring and control system 1 includes a monitoring and control device 100, a plurality of terminals 400 including terminals 400a and 400b used by the user 5, and gateways (GW) 210 and controllers 220 installed in each of a plurality of buildings. The user 5 is the owner of the building or the administrator of the building entrusted by the owner of the building. The user 5 may be the administrator of the monitoring and control system 1.

[0014] The monitoring and control system 1 is a system that monitors and controls a plurality of building facilities installed in a plurality of buildings. Each of the plurality of terminals 400 is configured to be communicable with the monitoring and control device 100 via a network NW2 (for example, the Internet).

[0015] The user 5 can display a monitoring screen or a control screen of the building facilities on the terminal 400. The user 5 can monitor the operating state of the building facilities (for example, check the air conditioning temperature) by checking the monitoring screen of the terminal 400. The user 5 can perform a control operation of the building facilities (for example, change the temperature of the air conditioning) from the control screen of the terminal 400.

[0016] <000009I> The monitoring and control device 100 may be configured as a cloud server connectable via the Internet, or its functions may be realized by a plurality of devices. When configured in this way, the user 5 can monitor and control the building facilities of each building via the cloud server.

[0017] In the present embodiment, it is assumed that the monitoring and control system 1 manages at least three buildings: building 201 (also referred to as "building A"), building 202 (also referred to as "building B"), and building 203 (also referred to as "building C"). Buildings A to C (buildings 201 to 203) are assumed to be owned by the same owner.

[0018] In each of Buildings A to C, a GW210, a controller 220, and various building facilities (such as air conditioning, lighting, and sanitary facilities) are installed. These building facilities are connected to the controller 220 by signal lines. The controller 220 is connected to a gateway (GW) 210 that relays communication, and is configured to be communicable with a monitoring and control device 100 via a network NW1.

[0019] The network NW1 is, for example, a dedicated network / regional network provided by a telecommunications carrier. The communication fee for this dedicated network / regional network is determined according to the monthly data communication volume.

[0020] The communication IF113 (see FIG. 2) of the monitoring and control device 100 transmits and receives data for monitoring or controlling a plurality of building facilities between the plurality of building facilities and the plurality of controllers 220 respectively connected to the plurality of controllers 220 via the plurality of controllers 220 installed in the plurality of buildings 201 to 203. The processor 111 (see FIG. 2) processes the data transmitted and received by the communication IF113.

[0021] Thereby, based on the received data (monitoring signal) from the building facilities collected by the monitoring and control device 100 via the controller 220, the operating state of the building facilities can be displayed on the monitoring screen of the terminal 400. Furthermore, based on the control operation performed on the control screen of the terminal 400, transmission data (control signal) is transmitted from the monitoring and control device 100 to the controller 220, thereby enabling control of the building facilities. Hereinafter, each of Buildings A to C is also referred to as a "building base" or "base".

[0022] In this embodiment, it is assumed that one controller 220 is installed in each building location. In the following description, "amount of data transmitted and received (communication volume) in Building A" means the amount of data transmitted and received between the monitoring and control device 100 and the controller 220 installed in Building A. The same applies to Buildings B and C. Note that multiple controllers 220 may be installed in a single building, in which case the amount of data transmitted and received (communication volume) in Building A means the sum of the amounts of data transmitted and received between the monitoring and control device 100 and the multiple controllers 220 installed in Building A.

[0023] Figure 2 shows an example of the hardware configuration of the monitoring and control system 1. The monitoring and control device 100 comprises a processor 111 as a processing unit, a memory 112 as a storage device, and a communication interface (IF) 113 as a communication device. These are connected to each other via a bus so that they can communicate with one another.

[0024] The processor 111 is, for example, a CPU (Central Processing Unit). The memory 112 includes, for example, ROM (Read Only Memory), RAM (Random Access Memory), and a non-volatile storage device. The non-volatile storage device is, for example, an HDD (Hard Disk Drive), an SSD (Solid State Drive), etc.

[0025] The CPU loads programs stored in ROM or non-volatile storage devices into RAM and executes them to realize various functions of the monitoring and control device 100. ROM or non-volatile storage devices store programs and various data that describe the processing procedures of the monitoring and control device 100. RAM serves as the CPU's workspace when executing programs and temporarily stores programs and data used to execute them.

[0026] The terminal 400 comprises a processor 411, memory 412, communication interface 413, input unit 420, and display unit 421. Similar to the monitoring and control device 100, the processor 411 is a CPU, and the memory 412 includes ROM, RAM, and a non-volatile storage device (HDD, SSD, etc.). The processor 411 executes programs stored in the memory 412 to realize various functions of the terminal 400.

[0027] The display unit 421 is, for example, a display. The input unit (reception unit) 420 is, for example, a keyboard, a mouse, or a touch panel display integrated with the display unit 421. The terminal 400 receives input from user 5 via the input unit 420. The display unit 421 can display the processing results performed by the monitoring and control device 100 based on the input from user 5 via the input unit 420.

[0028] The GW210 installed in the building is a device that relays communication between the controller 220 and the monitoring and control device 100. The GW210 transmits data (control signals) received from the monitoring and control device 100 to the controller 220, and transmits data (monitoring signals) received from the controller 220 to the monitoring and control device 100.

[0029] In this embodiment, the controller 220 is a PLC (Programmable Logic Controller). The controller 220 comprises a CPU, ROM, RAM, and a communication interface (IF). These are interconnected via a bus to enable communication with each other. The CPU loads programs stored in ROM into RAM and executes them to realize various functions of the controller 220. ROM stores programs that describe the processing procedures of the controller 220. RAM serves as a workspace for the CPU when executing programs and temporarily stores programs and data used when executing programs.

[0030] Various building facilities are connected to the controller 220 by signal lines. The controller 220 transmits data (control signals) received from the GW210 to the various building facilities and transmits data (monitoring signals) received from the various building facilities to the GW210. The controller 220 may be composed of multiple controllers, including a main controller and local controllers.

[0031] Next, the relationship between building equipment and data reception cycles will be explained. Figures 3 and 4 are tables illustrating user operation records and data reception cycles. In this embodiment, the communication charges to be paid are determined according to the monthly communication volume between the multiple controllers 220 installed in buildings A to C and the monitoring and control device 100. For example, the charge is M1 yen until the monthly communication volume reaches the upper limit C, and if it exceeds the upper limit C, the charge becomes M2 yen (M2 > M1).

[0032] The building owner, who owns buildings A through C, wishes to reduce communication costs by limiting the monthly communication volume between the multiple controllers 220 installed in buildings A through C and the monitoring and control device 100 to within the upper limit C (communication fee: M1 yen). To address this need, in this embodiment, the monitoring and control device 100 is configured to limit the monthly communication volume to within the upper limit C. This will be explained in detail below.

[0033] The building facilities of Building A include air conditioning, lighting, and electricity meters. The table shown in Figure 3 shows the equipment management points in Building A and the frequency of user operations by User 5. Examples of equipment management points in Building A are the ON / OFF operation of the air conditioning on the 1st floor (hereinafter referred to as "1F air conditioning operation"), the ON / OFF operation of the lighting on the 2nd floor (hereinafter referred to as "2F lighting operation"), the electricity meter on the 3rd floor (hereinafter referred to as "3F electricity meter"), the indoor temperature of office A on the 4th floor (hereinafter referred to as "4F indoor temperature"), and the indoor temperature of office B on the 5th floor (hereinafter referred to as "5F indoor temperature").

[0034] User operation frequency refers to the number of times the building equipment manager (User 5) opened the monitoring or control screen related to the equipment management point in order to view or control information about that point. This count is compiled for the most recent periods: (a) within the last month, (b) within the last three months, and (c) more than six months prior. This count may be the average number of times per month for each period, or the total number of times for each period.

[0035] For example, within the last month, User 5 has opened the 1F air conditioning control screen (the screen for controlling the air conditioning on the 1st floor to be turned ON or OFF) four times, opened the 2F lighting control screen (the screen for controlling the lighting on the 2nd floor to be turned ON or OFF) once, opened the 3F power meter monitoring screen (the screen that displays the power meter on the 3rd floor) six times, opened the 4F indoor temperature monitoring screen (the screen that displays the indoor temperature on the 4th floor) twice, and has not opened the 5F indoor temperature monitoring screen (the screen that displays the indoor temperature on the 5th floor).

[0036] The operation to open the control screen for the 1st floor air conditioning system has been performed 4 times in the last month, an average of 4 times per month in the last 3 months, and an average of 2 times per month more than 6 months ago.

[0037] In this embodiment, the default reception cycle for received data (monitoring signals) from building equipment is once per hour. For example, the monitoring control device 100 acquires and stores all monitoring signals output from the building equipment of building A once per hour. In addition, whenever the monitoring control device 100 sends transmission data (control signals) to the building equipment, it saves the information of the transmission data each time. As a result, for example, when the control screen for 1F air conditioning operation is opened, the information about the 1F air conditioning equipment acquired in the previous session (such as the indoor temperature on the 1F) and the information about the 1F air conditioning equipment that was transmitted in the previous session (such as the ON / OFF information of the 1F air conditioning equipment) are displayed. When the monitoring screen for the 3F power meter is opened, the information about the power meter installed on the 3F, acquired in the previous session, is displayed.

[0038] Furthermore, in this embodiment, if it is predicted that the monthly data volume may exceed the upper limit C, the reception cycle for received data (monitoring signals) from building equipment is lengthened. For example, by changing the data reception cycle from once an hour to once every two hours, once every three hours, etc., the system controls the monthly data volume so that it does not exceed the upper limit C.

[0039] In this embodiment in particular, the reception cycle is lengthened for building equipment that the building equipment manager (user 5) may consider to be of low importance, while the reception cycle is kept as short as possible for building equipment that the manager may consider to be of high importance. The level of importance is estimated based on the frequency of user operations at the equipment management point. This will be explained in detail below.

[0040] First, an evaluation value is calculated based on the frequency of user operations. For each equipment management point, the evaluation value is calculated as follows: (a) the number of times the screen was opened within the last month × the weighting coefficient of (a) (also simply referred to as "weight") + (b) the number of times the screen was opened within the last three months × the weighting coefficient of (b) + (c) the number of times the screen was opened more than six months ago × the weighting coefficient of (c).

[0041] For example, in the 1F air conditioning operation, an evaluation score of 4 × 3 + 3 × 2 + 2 × 1 = 20 points is calculated. In the 2F lighting operation, an evaluation score of 1 × 3 + 1 × 2 + 5 × 1 = 10 points is calculated. Similarly, in the 3F power meter, an evaluation score of 6 × 3 + 6 × 2 + 6 × 1 = 36 points is calculated. In the 4F indoor temperature, an evaluation score of 2 × 3 + 2 × 2 + 2 × 1 = 12 points is calculated. In the 5F indoor temperature, an evaluation score of 0 × 3 + 0 × 2 + 4 × 1 = 4 points is calculated.

[0042] The evaluation score is calculated so that the higher the frequency of operation, the higher the score. The weights are calculated so that the evaluation score is higher for each operation, in the order of frequency of operation in (a), (b), and (c), with more recent operations resulting in a higher evaluation score. For example, the 3F power meter, which has a high frequency of operation, has an evaluation score of 36 points, while the 5F indoor temperature meter, which has a low frequency of operation, has an evaluation score of 4 points. Here, it is assumed that the higher the evaluation score (higher frequency of operation), the more the building equipment manager (user 5) perceives the importance of that building equipment.

[0043] By default, data is received once per hour at each equipment management point (see STEP0). However, if data usage becomes critical, the data reception cycle is changed in stages, as shown in Figure 4. STEP0 is the pattern with no restrictions on the reception cycle, and when the reception cycle is restricted, it is switched in stages to communication restriction pattern 1 (also called "STEP1") to communication restriction pattern 4 (also called "STEP4").

[0044] The data reception cycle is configured to decrease as the evaluation value decreases (i.e., as the operation frequency decreases). For example, when switching from STEP0 to STEP1, the 1F air conditioning operation cycle decreases from once / hour to once / 2 hours (evaluation value: 20 points), the 2F lighting operation cycle decreases from once / hour to once / 4 hours (evaluation value: 10 points), the 3F power meter cycle remains at once / hour (evaluation value: 36 points), the 4F indoor temperature cycle decreases from once / hour to once / 3 hours (evaluation value: 12 points), and the 5F indoor temperature cycle decreases from once / hour to once / 4 hours (evaluation value: 4 points).

[0045] In this case, if the evaluation score is 30 points or higher, the current setting is maintained; if the evaluation score is between 20 and 29 points, it is reduced to once every 2 hours; if the evaluation score is between 11 and 19 points, it is reduced to once every 3 hours; and if the evaluation score is 10 points or lower, it is reduced to once every 4 hours.

[0046] Here, the reception cycle is maintained for the 3F power meter, which is considered to be of high importance, while the reception cycle is lengthened for the 2F lighting operation, which is considered to be of relatively low importance. In this example, User 5 has little interest in the status of the lighting installed on the 2F, but considers the power meter installed on the 3F to be of high importance, and therefore wants to check the status of the power meter as close to the current time as possible (and check its changes in detail).

[0047] In this embodiment, as data becomes scarce, the system switches from STEP0 to STEP1, and then to STEP2, 3, and 4 in that order. For example, in 1F air conditioning operation, STEP0 to 4 switches in the order of once per hour, once per 2 hours, once per 3 hours, once per 4 hours, and once per 6 hours. In 2F air conditioning operation, STEP0 to 4 switches in the order of once per hour, once per 4 hours, once per 6 hours, once per 8 hours, and once per 12 hours.

[0048] Thus, in steps 0 to 4, the data reception cycle is configured to gradually lengthen. Furthermore, the lower the frequency of user 5's operations (lower evaluation value), the longer the data reception cycle becomes, and when user 5's operations are frequent (higher evaluation value), the data reception cycle is configured to be as short as possible.

[0049] Data usage (communication volume) is the sum of the amount of data received from building equipment (monitoring signals) and the amount of data transmitted to building equipment (control signals). The majority of data usage is received data (monitoring signals), with transmission data (control signals) accounting for a small proportion. Therefore, in this embodiment, the focus is on received data (monitoring signals), and the system is configured to reduce the amount of received data related to equipment management points that user 5 does not consider important. This controls the communication volume so that it does not exceed the upper limit C for one month.

[0050] Note that the points and categories for equipment management vary from building to building. Also, additions or deletions of building equipment will affect the overall communication volume. The evaluation rules for the aforementioned evaluation values ​​should be reviewed as needed when building equipment is added or deleted, or in accordance with other building operations.

[0051] Furthermore, as described above, the estimation of importance is not limited to the frequency of user operations at equipment management points; it may also be estimated based on the operational performance of the building equipment. For example, in the example in Figure 4, an upper limit for the operating time of the air conditioning in a one-month period on the first floor (for example, 1000 hours) may be set, and the reception cycle may be changed according to the rate of reaching the upper limit (if the operating time is 586 hours, the rate of reaching the upper limit is 58.6%). If the rate of reaching the upper limit is low, the reception cycle should be lengthened, while if the rate of reaching the upper limit is high, the reception cycle should not be reduced as much as possible. In the case of the power meter on the third floor, for example, the rate of reaching the upper limit is calculated using the meter value (122 kW) against an upper limit of 300 kW. In the case of the indoor temperature on the fourth floor, for example, the rate of reaching the upper limit is calculated using the indoor temperature (29.6°C) against an upper limit of 30°C.

[0052] In this embodiment, the frequency of communication restrictions is determined by weighting each building equipment management point based on the operational information (user operation and viewing frequency) of user 5 who manages the building equipment or the operating performance of the building equipment.

[0053] Figure 5 is a diagram illustrating the change in data communication volume due to single-control processing. In this embodiment, the monitoring and control device 100 can perform single-control processing (see Figures 5 and 6) and multiple-control processing (see Figures 7 to 11).

[0054] Single-control processing is the process of controlling the reception cycle for a controller 220 installed in one building. Multiple-control processing is the process of controlling the reception cycle for multiple controllers 220 installed in multiple buildings.

[0055] Figure 5 shows the monthly trend of data traffic resulting from the implementation of standalone control processing for Building A (for example, from January 1st to January 31st).

[0056] In this embodiment, the charges are set so that if the total amount of data transmitted and received between the monitoring and control device 100 (communication IF 113) and each of the multiple controllers 220 for the current month exceeds the communication limit, the communication charges for the current month will increase.

[0057] In the example shown in Figure 5, we will explain an example where only Building A is included. Here, we will explain an example where the monthly communication charges increase if the monthly communication volume between Building A controller 220 and monitoring and control device 100 exceeds 100GB (upper limit C).

[0058] In standalone control processing, a threshold g is set in advance for the upper limit C. In this example, a threshold g of 80GB is set for the upper limit C = 100GB (80% of the upper limit C is set as the threshold g). In standalone control processing, if the threshold g (80GB) is exceeded, communication restrictions are activated and the process moves from STEP0 to STEP1.

[0059] In the example in Figure 5, let's assume that the average data usage from day 1 to day N in January was aGB. aGB includes the data usage for 1F air conditioning operation, 2F lighting operation, 3F power meter, 4F indoor temperature, and 5F indoor temperature, as explained using Figure 4. Since aGB × N days exceeds 80GB, data restrictions are triggered. As a result, on day N+1, the system transitions from STEP0 to STEP1 (data restriction pattern 1).

[0060] As shown in Fig. 4, since the data reception period becomes longer, the traffic volume decreases to b1 GB (< a GB) on the (N + 1)-th day. In the independent control process, an over-prediction is executed. In the over-prediction, it is predicted whether the final traffic volume exceeds 100 GB when it is assumed that the traffic volume remains at b1 GB from the day after the (N + 1)-th day to the 31st day. Here, it is assumed that as a result of executing the over-prediction, the final traffic volume is predicted to exceed 100 GB (a GB × N days + b1 GB × (31 - N)> 100 GB). In this case, it further shifts to STEP2 (communication restriction pattern 2) from the next day.

[0061] Due to the shift to STEP2, the traffic volume further decreases to b2 GB (< b1 GB) on the (N + 2)-th day. However, as a result of executing the over-prediction, it is assumed that the traffic volume remains at b2 GB from the day after the (N + 2)-th day to the 31st day, and it is predicted that the final traffic volume exceeds 100 GB (a GB × N days + b1 GB + b2 GB × (31 - (N + 1))> 100 GB). In this case, it further shifts to STEP3 (communication restriction pattern 3) from the next day.

[0062] Due to the shift to STEP3, the traffic volume further decreases to b3 GB (< b2 GB) on the (N + 3)-th day. However, as a result of executing the over-prediction, it is assumed that the traffic volume remains at b3 GB from the day after the (N + 3)-th day to the 31st day, and it is predicted that the final traffic volume exceeds 100 GB (a GB × N days + b1 GB + b2 GB + b3 GB × (31 - (N + 2))> 100 GB). In this case, it further shifts to STEP4 (communication restriction pattern 4) from the next day.

[0063] By transitioning to STEP4, the traffic has further decreased to b4 GB (< b3 GB) on N + 4 days. Here, assuming that as a result of performing the excess prediction, the traffic remains at b4 GB from N + 5 days to the 31st day after the day following N + 4 days, it is predicted that the final traffic will not exceed 100 GB (a GB × N days + b1 GB + b2 GB + b3 GB + b4 GB × (31 - (N + 3)) ≤ 100 GB). In this case, since it is predicted that it will not exceed 100 GB even if remaining at STEP4, the subsequent days will also continue with STEP4.

[0064] As described above, after the activation of the communication restriction, the traffic is predicted daily, and when it is predicted that the predicted value will exceed the upper limit value C, the communication restriction level is further increased. By performing the communication restriction in this way, the traffic for one month will not exceed the upper limit value C = 100 GB.

[0065] Note that even when the communication restriction is implemented until STEP4, if it is predicted that the traffic for one month will exceed the upper limit value C, it may be configured not to receive the received data (monitoring signal) from the building equipment in the remaining days.

[0066] If the building equipment is added or deleted in the middle of the month, if it is a minor change, the impact on the overall traffic is small. Even if the impact on the traffic is large, if it is predicted that the traffic will be tight and exceed the upper limit value C, further communication restrictions will be imposed, so as a result, it will not exceed the upper limit value C.

[0067] Hereinafter, the single control process executed by the processor 111 of the monitoring control device 100 will be described using a flowchart. FIG. 6 is a flowchart of the single control process. Hereinafter, "step" will also be simply referred to as "S".

[0068] When one building is the control target, the single control process may be started at 0:00 on the 1st of each month, for example. When a plurality of buildings are the control targets, the single control process is called and executed from the plurality of control processes (FIG. 9).

[0069] As shown in Figure 6, when the standalone control process starts, the monitoring and control device 100 obtains the current data traffic for the current month in S101. For example, in the example shown in Figure 5, if the current data traffic (i.e., the total traffic from day 1 to day N) is calculated at 0:00 on day N+1, the data traffic will be 80GB.

[0070] In S102, the monitoring and control device 100 determines whether the current communication volume is less than or equal to the threshold g. If the current communication volume is less than or equal to the threshold g (YES in S102), the monitoring and control device 100 proceeds to S103. If the current communication volume is not less than or equal to the threshold g (i.e., the current communication volume exceeds the threshold g) (YES in S102), the monitoring and control device 100 proceeds to S104.

[0071] In the above example, the current data usage at 0:00 on day N+1 exceeds the threshold g (80GB), so the process proceeds to S104. On the other hand, from 0:00 on day 1 to 0:00 on day N, the current data usage is below the threshold g, so the process proceeds to S103.

[0072] In S103, the monitoring and control device 100 performs communication for one day without restrictions (STEP0) and proceeds to processing in S112. In Figure 3, this corresponds to the control for 1 to N days. In this case, received data is acquired at all equipment management points with a reception cycle of once every hour.

[0073] In S112, the monitoring and control device 100 determines whether or not it is the last day of the month. If the monitoring and control device 100 determines that it is the last day of the month (YES in S112), it terminates the standalone control process. On the other hand, if the monitoring and control device 100 does not determine that it is the last day of the month (NO in S112), it returns the process to S101.

[0074] In other words, if the communication performed in S103 is on the last day of the month (for example, January 31st), the standalone control process is terminated; otherwise, the processes in S101 and S102 are executed again to determine whether the current communication volume is greater than or equal to the threshold g.

[0075] The monitoring and control device 100 initiates communication restriction (S104) and executes communication restriction pattern 1 (STEP1) (S105). In the example in Figure 5, this corresponds to the control over N+1 days. The amount of communication (also referred to as "height") over N+1 days is b1GB.

[0076] In S106, the monitoring and control device 100 performs communication for the current day and obtains the amount of communication per day. For example, over N+1 days, the amount of communication per day is b1GB.

[0077] In S107, the monitoring and control device 100 performs an excess prediction. In S108, the monitoring and control device 100 determines whether the upper limit C will be exceeded if the situation continues as is until the end of the month. If the monitoring and control device 100 determines that the upper limit C will be exceeded (YES in S108), it proceeds to S110. On the other hand, if the monitoring and control device 100 does not determine that the upper limit C will be exceeded (NO in S108), it proceeds to S109.

[0078] In S109, the monitoring and control device 100 maintains the communication restriction pattern (maintaining the communication volume bn, n>=1). For example, after N+4 days, b4 is maintained.

[0079] In S110, the monitoring and control device 100 raises the communication restriction pattern by one level. For example, as described above, in the excess prediction after communication (communication volume: b1) for N+1 days using STEP1 (communication restriction pattern 1), if we assume that the communication volume remains at b1GB from the day after N+1 to the 31st day, the final communication volume is predicted to exceed the upper limit C (100GB) (aGB × N days + b1GB × (31-N) > 100GB). In this case, the system moves to STEP2 (communication restriction pattern 2) from the next day (communication volume: b2).

[0080] In S111, the monitoring and control device 100 determines whether or not it is the last day of the month. If the monitoring and control device 100 determines that it is the last day of the month (YES in S111), it terminates the standalone control process.

[0081] On the other hand, if the monitoring and control device 100 does not determine that it is the last day of the month (NO in S111), it returns to processing S106 and executes processing S106 to S110 again. As a result of performing the daily excess prediction (S107), if the upper limit C is exceeded, the communication restriction pattern is raised by one level (S109), but if the upper limit C is not exceeded, the communication restriction pattern is maintained (S110).

[0082] Next, we will explain the multiple control process. As mentioned above, the multiple control process is a process that controls the reception cycle for multiple controllers 220 installed in multiple buildings. Figure 7 is a diagram illustrating the change in data communication volume due to the multiple control process.

[0083] The following describes an example of controlling the reception cycle for controllers 220 installed in three buildings, A, B, and C. Here, it is assumed that communication charges increase when the total monthly communication volume of building A + building B + building C exceeds 100GB (upper limit C).

[0084] In this case, the threshold ga for building A (meaning the threshold at controller 220 installed in building A; the same applies hereafter) is set to 30GB, the threshold gb for building B is set to 40GB, and the threshold gc for building C is set to 20GB, and the sum of the thresholds for buildings A to C (threshold g) is set to 90GB (30 + 40 + 20) < 100GB (upper limit C).

[0085] In this configuration, for example, even if the threshold ga is reached in building A, it is possible that the thresholds gb and gc have not yet been reached in buildings B and C. Therefore, overall, it can be considered that there is still some leeway (reserve capacity) before reaching the threshold g. For this reason, in this embodiment, if there is still leeway before reaching the thresholds gb and gc in buildings B and C, the system is configured not to unnecessarily restrict communication in building A. By doing so, it is possible to minimize communication restrictions at a single building site (avoid unnecessarily lengthening the communication cycle).

[0086] In this example, no communication restrictions were triggered in any of the buildings A through C from day 1 to day N. In other words, from day 1 to day N, the state is STEP 0.

[0087] Assume that on day N, the threshold ga for building A is exceeded. From day 1 to day N, the average traffic volume for building A is a0GB, and a0GB × N days exceeds 30GB. As a result, from the next day (day N+1), building A transitions from STEP0 to STEP1. In this respect, the same control as the standalone control process explained using Figure 5 is performed.

[0088] On the other hand, on day N, building B did not exceed its threshold of GB. The average traffic volume of building B from day 1 to day N was b0 GB, and b0 GB × N days did not exceed 40 GB. Therefore, as long as the threshold of GB is not exceeded, the STEP 0 state will continue beyond day N+1.

[0089] Furthermore, on day N, the threshold gc for building C was not exceeded. From day 1 to day N, the average traffic volume for building C was c0GB, and cb0GB × N days did not exceed 20GB. Therefore, as long as the threshold gc is not exceeded, the STEP0 state will continue beyond day N+1.

[0090] Assume that on day N+1, the data usage in Building A decreased from a0GB to a1GB due to the data usage restriction in STEP 1. Then, assuming that the data usage remained at a1GB from day N+2 to day 31, the predicted data usage for Building A for the current month (1st to 31st) is a0GB × N days + a1GB × (31 days - N days). Here, the excess amount for Building A is calculated as: predicted data usage for Building A for the current month - threshold ga for Building A.

[0091] For example, if the predicted data usage for Building A for the current month is 36GB, then the excess data usage for Building A = predicted data usage for Building A for the current month (36GB) - Building A's threshold ga (30GB) = 6GB. Since the data usage decreases from day N+1 onwards, the cumulative data usage for Building A progresses as shown in the graph in Figure 7.

[0092] On the other hand, in Building B, we assume that the traffic volume will remain at b0GB even after N+1 days. In this case, the predicted traffic volume for the current month (1st to 31st) in Building B = b0GB × 31 days. Here, the remaining capacity of Building B is calculated as Building B's threshold - Building B's predicted value for the current month. For example, if Building B's predicted value for the current month is 36GB, then the remaining capacity of Building B = Building B's threshold gb (40GB) - Building B's predicted value for the current month (36GB) = 4GB.

[0093] Similarly, we assume that the traffic volume in Building C will remain at c0GB even after day N+1. In this case, the predicted traffic volume in Building C for the current month (1st to 31st) = c0GB × 31 days. Here, the remaining capacity of Building C is calculated as Building C threshold gc - Building C's predicted value for the current month. For example, if the predicted value for the current month of Building C is 17GB, then the remaining capacity of Building C = Building C threshold gc (20GB) - Building C's predicted value for the current month (17GB) = 3GB.

[0094] In this case, the excess amount in Building A (6GB) ≤ the surplus capacity of Building B (4GB) + the surplus capacity of Building C (3GB). In this case, even on the 31st, the sum of the predicted data usage for Buildings A to C (36GB + 36GB + 17GB = 89GB) is not expected to exceed the threshold g (90GB). Since the total does not exceed the threshold g (virtually, 6GB of the combined 7GB of surplus capacity from Buildings B and C is being provided to Building A), the restrictions in STEP 1 will continue in Building A. In this case, the average daily data usage in Building A is expected to remain at a1GB.

[0095] In this manner, the predicted data usage is calculated daily from day N+1 onwards. Then, suppose a day occurs where the excess data usage in Building A > the remaining capacity of Building B + the remaining capacity of Building C. In this case, the sum of the predicted data usage for Buildings A to C is expected to exceed the threshold g (90GB) for the current month. In this case, the limit in Building A is changed from STEP 1 to STEP 2. In this case, the average data usage in Building A decreases from a1GB to a2GB.

[0096] The process continues in the same manner, and if the excess amount of Building A ≤ the surplus capacity of Building B + the surplus capacity of Building C, then STEP 2 is continued. If the excess amount of Building A > the surplus capacity of Building B + the surplus capacity of Building C, then STEP 2 is moved to STEP 3. Furthermore, if the excess amount of Building A ≤ the surplus capacity of Building B + the surplus capacity of Building C, then STEP 3 is continued. If the excess amount of Building A > the surplus capacity of Building B + the surplus capacity of Building C, then STEP 3 is moved to STEP 4.

[0097] Furthermore, if Building B exceeds the threshold gb, Building B is excluded and the remaining capacity is calculated using only Building C. On the other hand, if Building C exceeds the threshold gc, Building C is excluded and the remaining capacity is calculated using only Building B.

[0098] For example, if the threshold gb for building B is exceeded, building B is excluded. Then, if the excess amount in building A > the remaining capacity of building C, a further restriction is placed on building A. If the threshold gc for building C is exceeded, building C is excluded. Then, if the excess amount in building A > the remaining capacity of building B, a further restriction is placed on building A.

[0099] If both Building B and Building C exceed the threshold, it becomes impossible to share surplus capacity. Therefore, independent control processing is performed on Building A as well, using the method shown in Figures 5 and 6. In this case, since there are no buildings that can share surplus capacity with either Building B or Building C, independent control processing is performed on both Building B and Building C.

[0100] In this case, for example, let's say the threshold ga of building A is 30GB and the upper limit Ca is 33GB, the threshold gb of building B is 40GB and the upper limit Cb is 45GB, and the threshold gc of building C is 20GB and the upper limit Cc is 22GB. In this case, the upper limit C = upper limit Ca (33GB) + upper limit Cb (45GB) + upper limit Ca (22GB) = 100GB.

[0101] In this case, if individual control processing is performed for each of buildings A to C, the upper limit Ca will not be reached in building A, the upper limit Cb will not be reached in building B, and the upper limit Cc will not be reached in building C. As a result, the overall upper limit of 100GB will not be reached. The distribution of the upper limits Ca to Cc can be set by user 5 at any value, or the monitoring and control device 100 can decide the distribution based on the actual amount of communication.

[0102] Furthermore, if both Building A and Building B exceed the threshold, but Building C does not, a portion of Building C's surplus capacity may be transferred to Building A, and the remainder to Building B. Another building may be pre-configured to transfer surplus capacity to Building B.

[0103] If all of buildings A through C exceed the threshold, another building (for example, building D) may be added. For example, if building A reaches the threshold, surplus capacity is transferred from buildings B and C to building A; if buildings A and B reach the threshold, surplus capacity is transferred from building C to buildings A and B; and if buildings A through C reach the threshold, a new building D is added, and surplus capacity is transferred from building D to buildings A through C. In this case, it may also be possible to transfer surplus capacity only from building D to building A.

[0104] In this example, buildings A through D are, for example, owned by the same owner. Buildings A through C are located in Area X1 (managed by branch Y1 of the building management company), and building D is located in Area X2 (managed by branch Y2 of the building management company). In this case, in principle, surplus capacity should be shared between buildings A through C in Area X1, which is under the jurisdiction of branch Y1. If it becomes impossible to share surplus capacity between them, surplus capacity may be urgently shared from building D in Area X2, which is under the jurisdiction of another branch Y2. Furthermore, buildings other than building D, such as buildings E and F, may also be added as buildings from which surplus capacity can be urgently shared.

[0105] In the above explanation, control is based on a "threshold g" rather than a "maximum value C" for monthly data usage. This is because using "maximum value C" as the basis would create a risk of exceeding the maximum value C. Even if Building A is unable to receive data from Buildings B and C, it is possible to avoid exceeding the maximum value for Building A by continuing to impose data restrictions on Building A alone.

[0106] Figure 8 is a diagram illustrating the method of allocating thresholds. In the explanation of Figure 7, the threshold value ga for building A is set to 30GB, the threshold gb for building B is set to 40GB, and the threshold gc for building C is set to 20GB. These can also be calculated using the following method.

[0107] The monitoring and control device 100 sets thresholds (thresholds ga to gc) for the amount of data to be transmitted and received between the communication IF 113 for the current month in each of the multiple controllers 220 in buildings A to C. The sum of the thresholds (thresholds ga to gc) in each of the multiple controllers 220 (threshold g) is set to be less than the communication upper limit C. In the above example, threshold ga (30GB) + threshold gb (40GB) + threshold gc (20GB) = 90GB < threshold g (100GB).

[0108] The monitoring and control device 100 estimates the amount of data to be transmitted and received in each of the multiple controllers 220 in buildings A to C, based on the type and number of signals being input and output to and from the connected building equipment. The processor 111 determines a threshold in each of the multiple controllers 220 according to the estimated amount of data. This allows for allocating a larger amount of communication (threshold) to buildings (controllers 220) with high communication loads. This will be explained in detail below.

[0109] As shown in Figure 8, Building A has 100 DI (Digital Input) status points, 100 DI alarm points, 100 DO (Digital Output) start / stop points, 100 PI (Phone Input) measurement points, and 100 AI (Analog Input) measurement points.

[0110] At the DI status points, the communication rate is 10KB / period per point, so the total is 10 × 100 = 1000KB / period. At the DI alarm points, the communication rate is 10KB / period per point, so the total is 10 × 100 = 1000KB / period. At the DO start / stop points, the communication rate is 20KB / period per point, so the total is 20 × 100 = 2000KB / period. At the PI metering points, the communication rate is 50KB / period per point, so the total is 50 × 100 = 5000KB / period. At the AI ​​measurement points, the communication rate is 30KB / period per point, so the total is 30 × 100 = 3000KB / period. Therefore, in Building A, a total of 12000 (=1000 + 1000 + 2000 + 5000 + 3000)KB / period of communication occurs.

[0111] Building B has 100 DI status points, 50 DI alarm points, 100 DO start / stop points, 160 PI measurement points, and 150 AI measurement points. Similarly, calculations show that a total of 16,000 KB / cycle of communication occurs in Building B.

[0112] Building C has 200 DI status points, 200 DI alarm points, 50 DO start / stop points, 20 PI measurement points, and 100 AI measurement points. Similarly, calculations show that a total of 8000KB / cycle of communication occurs in Building C.

[0113] Calculating the ratio of data traffic, we get A:B:C = 12000KB / cycle:16000KB / cycle:8000KB / cycle = 3:4:2. In other words, it is presumed that the amount of data traffic increases in the order of B, A, and C.

[0114] Therefore, using the above ratio, the thresholds are configured to be increased in order of the expected amount of data traffic. Specifically, the thresholds for building A, building B, and building C are set to 3:4:2 = 30GB:40GB:20GB (total 90GB).

[0115] Thus, the monitoring and control device 100 may automatically determine the threshold using the predicted ratio of communication volume in each building. However, since the calculated value is only an estimate, the device may be configured to set the threshold determined by the user 5, using the above ratio as a reference (guideline). Furthermore, even if additional work occurs at the equipment management point during the operation of the month, the threshold can be reviewed using the above method.

[0116] Figure 9 is a flowchart of the multiple control process. For example, the multiple control process starts at 0:00 on the 1st of every month.

[0117] When multiple control processes begin, the monitoring and control device 100 acquires the current communication volume for each building (location) in S201. In the example shown in Figure 7, the current communication volume for each of buildings A to C (the amount of data transmitted and received between the monitoring and control device 100 and each of the controllers 220 for buildings A to C) is acquired. In the following, we will explain a specific example assuming that the thresholds have been exceeded in the order of buildings A, B, and C.

[0118] In S202, the monitoring and control device 100 determines whether a new building has exceeded a threshold (referred to as an "exceeding building") among the multiple buildings. If the monitoring and control device 100 determines that a new exceeding building has occurred (YES in S202), it proceeds to S203.

[0119] In this case, if the monitoring and control device 100 detects that one of the multiple buildings (multiple controllers 220) has exceeded the threshold for the current month's data volume, it lengthens the data reception cycle between the excess building and the monitoring and control device 100 compared to the current reception cycle. For example, in the case of building A shown in Figure 7, the threshold ga (30GB) was exceeded on day N, so the system transitions from STEP0 to STEP1. This reduces the amount of communication to the building that has exceeded the threshold, thereby enabling appropriate monitoring and control of building equipment installed in multiple buildings while suppressing communication charges.

[0120] On the other hand, if the monitoring and control device 100 does not determine that a new excess building has occurred (NO in S202), it returns to processing S201. This means that it will wait until an excess building occurs.

[0121] In S203, the monitoring and control device 100 acquires the communication volume of the excess building (Building A) and the buildings to which the capacity is to be shared (Buildings B and C). In the example in Figure 7, Building A is the excess building. The buildings to which the capacity is to be shared are buildings that virtually share surplus capacity with the excess building, and in this example, these are Buildings B and C.

[0122] In S204, the monitoring and control device 100 determines whether or not there are any buildings in the buildings subject to the sharing program (for example, buildings B and C) that have exceeded the threshold. If the monitoring and control device 100 determines that there are no buildings in the buildings subject to the sharing program that have exceeded the threshold (YES in S204), it proceeds to S208. On the other hand, if the monitoring and control device 100 determines that there are buildings in the buildings subject to the sharing program that have exceeded the threshold (NO in S204), it proceeds to S205.

[0123] In S208, the monitoring and control device 100 performs an excess forecast for each building (Buildings A to C) until the end of the month. In this way, the monitoring and control device 100 periodically calculates a predicted value for the amount of data for the current month in each of the multiple buildings.

[0124] In the excess forecasting process, the monitoring and control device 100 calculates the excess amount in the excess building (Building A) by subtracting a threshold from the predicted value of the data volume for the current month. In addition, in the excess forecasting process, the monitoring and control device 100 calculates the surplus amount in each of the multiple buildings that are eligible for data sharing (Buildings B and C: also referred to as "non-excess buildings": multiple non-excess controllers 220) where the data volume for the current month does not exceed the threshold, by subtracting the predicted value of the data volume for the current month from the threshold.

[0125] If the excess amount > total surplus (the excess amount of the excess building is greater than the sum of the surplus amounts of each of the multiple buildings to which capacity is to be shared) (YES in S209), the monitoring and control device 100 lengthens the reception cycle of the excess building (specifically, it raises the communication restriction pattern by one level) (S210). In this way, surplus capacity can be shared with the excess building, thus preventing the communication cycle from being unnecessarily lengthened.

[0126] On the other hand, the monitoring and control device 100 maintains the communication restriction pattern (S211) if the excess amount ≤ total surplus capacity (NO in S209). In the example explained in Figure 7, when the excess amount > total surplus capacity, building A transitions from step 1 (communication amount: a1) to step 2 (communication amount: a2).

[0127] The monitoring and control device 100 terminates the multiple control process if it is the last day of the month (YES in S212), and returns the process to S203 if it is not the last day of the month (NO in S212).

[0128] Returning to S203, in Building A, which has moved to STEP2, if the excess amount > total surplus amount, the system moves from STEP2 to STEP3.

[0129] Furthermore, returning to S203, if the monitoring and control device 100 determines that any of the multiple buildings eligible for data sharing have exceeded the threshold for the current month (NO in S204), it excludes the building whose data volume for the current month has exceeded the threshold from the calculation of the surplus capacity (S205). For example, if the threshold is exceeded in building B, building B is excluded from the buildings eligible for data sharing. As a result, only building C remains eligible for data sharing. This ensures that data can be shared only from buildings with surplus capacity to compensate for buildings exceeding the limit.

[0130] If there is one or more buildings eligible for sharing (YES in S206), the monitoring and control device 100 proceeds to S208. If there is one or more buildings eligible for sharing, buildings that have exceeded the threshold can virtually receive the surplus capacity of the eligible buildings.

[0131] On the other hand, if there is no compatible building (NO in S206), the monitoring and control device 100 executes a single control process (S207, Figure 6) and then terminates the multiple control process.

[0132] If there are no buildings eligible for capacity sharing, it is not possible to virtually share the excess capacity, so the standalone control process explained using Figure 6 is executed. For example, if the threshold is exceeded in buildings B and C, buildings B and C are excluded from the list of buildings eligible for capacity sharing. As a result, there are no buildings eligible for capacity sharing. In this case, building A executes the standalone control process, and the communication restriction pattern is controlled so that the amount of communication does not exceed the upper limit.

[0133] When the standalone control process (Figure 6) is executed in Building A, the threshold g in Figure 6 is replaced with the threshold ga mentioned above, and the upper limit C is replaced with the upper limit Ca. Also, in S105, the currently executed communication restriction pattern continues to be executed.

[0134] In this way, if any of the multiple buildings are excluded from the calculation of surplus capacity, the monitoring and control device 100 controls the excess building (Building A) to make the reception cycle longer than the current reception cycle, based on the upper limit Ca calculated based on the predicted data volume for the current month and the upper limit C. In this way, even if there are no buildings that can share surplus capacity, it is possible to prevent exceeding the upper limit by executing a standalone control process.

[0135] Next, we will explain how to determine the current month's threshold candidate based on the previous month's performance. By reviewing the current month's threshold based on the previous month's performance, it is possible to avoid or suppress the activation of communication restrictions as much as possible.

[0136] Figure 10 is a diagram illustrating the method for determining the current month's threshold candidates based on the previous month's performance. In the example in Figure 10, the thresholds for each building in the previous month were assumed to be: Building A: 30GB, Building B: 40GB, and Building C: 20GB.

[0137] Here, we assume that a data usage restriction was imposed on Building A from day N+1 onwards. As a result, the average data usage in Building A from day 1 to N is a0GB (STEP0), and then decreases to a1GB (STEP1), a2GB (STEP2), a3GB (STEP3), and so on. Consequently, the actual data usage in Building A for the previous month was 32GB. In this case, the thresholds for Buildings A to C for the current month are determined using the following method.

[0138] First, in the previous month, the actual data usage in Building A progressed as follows: a0GB (STEP0), a1GB (STEP1), a2GB (STEP2), and a3GB (STEP3). Now, let's estimate the data usage assuming that the usage did not progress to a2GB (STEP2) and a3GB (STEP3), but remained at a1GB (STEP1). In this case, the estimated value (virtual value) is assumed to be 36GB, which is higher than the actual 32GB.

[0139] Next, we estimate the data usage assuming that the user did not switch to a3GB (STEP3) in the previous month, but remained at a2GB (STEP2). In this case, the estimated value (virtual value) is assumed to be 34GB.

[0140] Then, as the threshold for Building A for the current month, it is possible to select one of the following: 36GB assuming it is maintained at the above state a1GB (STEP1), 34GB assuming it is maintained at the state a2GB (STEP2), 32GB assuming it ends at the state a3GB (STEP3), as in the actual progression, or the previous month's threshold of 30GB.

[0141] If the threshold ga for Building A is 30GB, then, as with last month, the threshold gb for Building B is 40GB and the threshold gc for Building C is 20GB. In this case, considering last month's performance, there is a high probability that data usage restrictions will be imposed this month as well.

[0142] On the other hand, if the threshold ga of building A is 32GB (+2GB), then, for example, the threshold gb of building B is set to 39GB (-1GB), and the threshold gc of building C is set to 19GB (-1GB). In this case, 2GB will be allocated from the thresholds of buildings B and C to building A.

[0143] If the threshold ga of building A is 34GB (+4GB), then, for example, the threshold gb of building B is set to 38GB (-2GB), and the threshold gc of building C is set to 18GB (-2GB). In this case, 4GB will be allocated from the thresholds of buildings B and C to building A.

[0144] If the threshold ga for building A is 36GB (+6GB), then, for example, set the threshold gb for building B to 37GB (-3GB) and the threshold gc for building C to 17GB (-3GB). In this case, 6GB from the thresholds of buildings B and C will be allocated to building A. Considering last month's performance, this scenario is highly likely to avoid triggering the data usage limit for the current month.

[0145] The amount of data transferred from the thresholds of buildings B and C to the threshold of building A may be distributed fairly and equally between buildings B and C, as described above, or it may be distributed considering the previous month's performance of buildings B and C. For example, a 2:1 ratio may be used, with 4GB transferred from building B and 2GB from building C. This ratio may be freely changed by user 5. Alternatively, if the threshold of building A is changed, the thresholds of buildings B and C may be set to the same threshold as the previous month.

[0146] The threshold for the current month may be manually set by user 5 at the beginning of each month. Alternatively, multiple threshold candidates calculated as described above may be displayed, and user 5 may be allowed to select one. Or, the monitoring and control device 100 may calculate multiple threshold candidates and automatically select one of them. For example, it may automatically select the actual value from the previous month, or it may automatically select the threshold ga for building A that is the largest.

[0147] Alternatively, user 5 may pre-set threshold strengths (1-4), and the threshold may be automatically selected according to the set strength. For example, in the above example, if strength 1 is set, the threshold ga=30GB for building A may be automatically selected; if strength 2 is set, the threshold ga=32GB for building A may be automatically selected; if strength 3 is set, the threshold ga=34GB for building A may be automatically selected; and if strength 4 is set, the threshold ga=36GB for building A may be automatically selected.

[0148] Figure 11 is a flowchart of the threshold setting process. The threshold setting process is executed after multiple control processes. In other words, it can be described as an end-of-month process that is executed at the end of each month.

[0149] The monitoring and control device 100 changes the threshold for the current month based on the data volume of the previous month for buildings (multiple controllers 220) that were over-exceeding in the previous month. This makes it possible to set an appropriate threshold based on the communication volume of the previous month.

[0150] When the threshold setting process starts, the monitoring and control device 100 determines in S301 whether or not there are any buildings that exceeded the threshold in the previous month (referred to as "buildings that exceeded the threshold in the previous month"). If there are buildings that exceeded the threshold in the previous month (YES in S301), the monitoring and control device 100 proceeds to S302, and if there are no buildings that exceeded the threshold in the previous month (NO in S301), the threshold setting process ends. In the example in Figure 10, the building that exceeded the threshold in the previous month is Building A.

[0151] In S302, the monitoring and control device 100 obtains the number of times n the communication restriction pattern was changed in the previous month for the building that exceeded the previous month's limit. In the example in Figure 10, the communication restriction pattern was changed 3 times in Building A, from STEP0 to STEP3. That is, the number n = 3.

[0152] In S303, the monitoring and control device 100 sets the threshold ga(0) to the previous month's threshold. In the example in Figure 10, the threshold ga(0) = previous month's threshold = 30GB. In this way, the monitoring and control device 100 determines the actual data volume from the previous month as a candidate threshold for the current month in buildings that have exceeded the previous month's limit.

[0153] In S304, the monitoring and control device 100 sets i to 1. In S305, the monitoring and control device 100 sets the threshold ga(i) to "the predicted value of the data volume for the previous month, assuming that the reception cycle was changed i times in the previous month, and then the last day of the previous month ended without the reception cycle being changed again." The monitoring and control device 100 determines threshold ga(i) as the threshold candidate for the current month. As a result, multiple threshold candidates are presented, which can be used by user 5 to consider which threshold to set for the current month.

[0154] In the example in Figure 10, if i=1, the process ends at STEP1 (data transfer volume: a1). In this case, the threshold ga(1) = 36GB.

[0155] If i=n (NO in S306), the monitoring and control device 100 increments i by 1 (S307) and returns to processing S305. If i=n (YES in S306), the monitoring and control device 100 proceeds to processing S308.

[0156] In the example in Figure 10, if i=2, the process ends at STEP2 (data volume: a2). In this case, the threshold ga(2) = 34GB.

[0157] In the example in Figure 10, if i=3 (=n), the process ends at STEP3 (data usage: a3). In this case, the threshold ga(3) = 32GB (actual value from the previous month).

[0158] In S308, the monitoring and control device 100 sets the threshold ga(K) selected from among the multiple threshold candidates for the current month, which are thresholds ga(0) to ga(n), as the threshold for the current month for buildings that exceeded the previous month's threshold. As explained using Figure 10, the threshold ga(K) may be selected by the user 5 received from the input unit 420, or it may be automatically selected by the monitoring and control device 100. If it is selected manually, for example, if K=1 is selected, the threshold for the current month (threshold ga(K)) = 36GB.

[0159] In S309, the monitoring and control device 100 sets the difference D to "Current month threshold for oversized buildings - Previous month threshold". In the above example, the difference D = Current month threshold for oversized buildings (36GB) - Previous month threshold (30GB) = 6GB.

[0160] If the monitoring and control device 100 determines that the resources will be distributed evenly from the target buildings (YES in S310), it proceeds to process S311. If the monitoring and control device 100 determines that the resources will not be distributed evenly from the target buildings (NO in S310), it proceeds to process S312.

[0161] In S311, the monitoring and control device 100 sets the monthly threshold by equally distributing the difference D to each building subject to the data transfer, and then terminates the threshold setting process. In the above example, the difference D (6GB) is equally distributed between Building B and Building C (3GB each). As a result, the monthly threshold for Building B becomes 40GB - 3GB = 37GB, and the monthly threshold for Building C becomes 20GB - 3GB = 17GB (see Figure 10).

[0162] In S312, the monitoring and control device 100 sets the threshold for the current month by bearing the difference D (6GB) for each building subject to data sharing according to the previous month's actual data, and then terminates the threshold setting process. In the above example, suppose that the actual data volume for Building B in the previous month was 40GB and the actual data volume for Building C in the previous month was 20GB. In this case, the difference D will be borne by Building B:Building C = 40GB:20GB = 2:1 = 4GB:2GB according to the actual data for the previous month. In this case, the threshold for Building B for the current month will be 40GB - 4GB = 36GB, and the threshold for Building C for the current month will be 20GB - 2GB = 18GB.

[0163] As shown in S311 and S312, the monitoring and control device 100 determines the current month threshold for each of the multiple buildings so that the sum of the previous month's thresholds for each of the multiple buildings matches the sum of the current month's thresholds for each of the multiple buildings. This allows the thresholds for each building to be set in a balanced manner.

[0164] After the threshold setting process is executed, the multiple control processes are executed. In other words, after each threshold for the current month is determined, the execution of the multiple control processes begins as part of the normal operation for that month.

[0165] As described above, in this embodiment, the monitoring and control device 100 includes a communication interface (IF) 113 as a communication device and a processor 111 as a processing device. The communication IF 113 transmits and receives data for monitoring or controlling multiple building facilities between multiple controllers 220, each installed in multiple buildings 201 to 203, and multiple building facilities connected to each of the multiple controllers 220. The processor 111 processes the data transmitted and received by the communication IF 113. The charges are set so that the communication charges for the current month increase if the total amount of data transmitted and received between the communication IF 113 and each of the multiple controllers 220 for the current month exceeds the communication limit. The processor 111 sets a threshold for the amount of data transmitted and received between each of the multiple controllers 220 for the current month. The sum of the thresholds in each of the multiple controllers 220 is a sum of thresholds smaller than the communication limit. If a controller 220 among the multiple controllers 220 has exceeded a threshold for the amount of data received in the current month, the processor 111 lengthens the data reception cycle between the excess controller 220 and the communication IF 113 compared to the current reception cycle.

[0166] As described above, in this embodiment, in a system that controls the amount of communication data in multiple buildings (controllers 220), if a building (controller 220) exceeds a threshold for the amount of data in the current month, the reception cycle of that controller 220 is lengthened. By lengthening the data reception cycle compared to the current reception cycle, the total amount of data in a given month can be suppressed. This allows for a reduction in communication volume for buildings that have exceeded the threshold, thereby suppressing communication charges and avoiding the need to impose unnecessary data volume restrictions, thus ensuring that the monitoring capabilities of building equipment are not compromised, and enabling appropriate monitoring and control of building equipment installed in multiple buildings. With the configuration described above, firstly, in order to suppress the total amount of data in a given month (or to prevent the total from exceeding the communication limit), the "threshold" used when activating communication restrictions in each building can be shared among multiple buildings, taking into account the data usage status. Secondly, by taking into account the data usage record for the current month, the "threshold" for each building in subsequent months can be reviewed to prevent communication restrictions from being biased towards a particular building.

[0167] Furthermore, the configurations of the multiple control processes described using Figures 7 to 9 may be applied as appropriate to the above configuration, and the configurations of the threshold setting processes described using Figures 10 and 11 may be applied as appropriate. In addition, the configurations of the threshold setting processes may be combined as appropriate with the configurations of the multiple control processes, and the configurations of the multiple control processes may be combined as appropriate with the configurations of the threshold setting processes.

[0168] [Note] The embodiments described above are specific examples of the following appendix.

[0169] (Note 1) A communication device that transmits and receives data for monitoring or controlling multiple building facilities via multiple controllers installed in multiple buildings, and multiple building facilities connected to each of the multiple controllers, The communication device comprises a processing device that processes data transmitted and received by the communication device, The charges are set such that if the total amount of data transmitted and received between the communication device and each of the multiple controllers during the current month exceeds a certain limit, the communication charges for the current month will increase. The processing device sets a threshold for the amount of data to be transmitted and received between the communication device and each of the plurality of controllers for the current month. The sum of the thresholds in each of the aforementioned multiple controllers is a second quantity that is smaller than the first quantity. The processing device is a monitoring and control device that, when an excess controller occurs among the plurality of controllers, which is a controller whose data volume for the current month exceeds a threshold, extends the data reception cycle between the excess controller and the communication device to a longer period than the current reception cycle.

[0170] (Note 2) The aforementioned processing apparatus is Each of the aforementioned controllers periodically calculates a predicted value for the amount of data for the current month. In the aforementioned excess controller, the excess amount is calculated by subtracting a threshold from the predicted value of the data volume for the current month. In each of the controllers among the aforementioned multiple controllers whose data volume for the current month does not exceed the threshold, the reserve capacity is calculated by subtracting the predicted data volume for the current month from the threshold. The monitoring and control device according to Appendix 1, further extending the reception cycle of the excess controller to a longer period than the current reception cycle if the excess amount of the excess controller is greater than the sum of the remaining capacity of each of the plurality of non-excess controllers.

[0171] (Note 3) The processing device is a monitoring and control device as described in Appendix 1 or Appendix 2, wherein if any of the multiple controllers that have not exceeded the limit for the current month have exceeded a threshold for the amount of data collected, the controller whose data volume for the current month has exceeded the threshold is excluded from the calculation of the reserve capacity.

[0172] (Note 4) The processing device is a monitoring control device according to any one of the appendices 1 to 3, wherein, if any of the plurality of controllers is excluded from the calculation of the surplus amount, the excess controller lengthens the reception cycle to a longer period than the current reception cycle based on the predicted value of the data volume for the current month and the value based on the first amount.

[0173] (Note 5) The aforementioned processing apparatus is In each of the aforementioned multiple controllers, the amount of data to be transmitted and received is estimated according to the type and number of signals input and output to and from the connected building equipment. A monitoring and control device according to any one of the appendices 1 to 4, wherein each of the plurality of controllers determines a threshold according to the estimated amount of data.

[0174] (Note 6) The processing device is a monitoring and control device according to any one of the appendices 1 to 5, wherein, among the plurality of controllers, the previous month's excess controller changes the threshold for the current month based on the amount of data from the previous month.

[0175] (Note 7) The monitoring and control device according to any one of the appendices 1 to 6, wherein the processing device determines the current month threshold for each of the plurality of controllers such that the sum of the previous month's thresholds for each of the plurality of controllers matches the sum of the current month's thresholds for each of the plurality of controllers.

[0176] (Note 8) The processing device is a monitoring and control device according to any one of the appendices 1 to 7, wherein the processing device determines a predicted value for the amount of data in the previous month as a threshold candidate for the current month, assuming that the reception cycle was changed once in the previous month and the last day of the previous month ended without the reception cycle being changed thereafter, in the previous month's excess controller.

[0177] (Note 9) The processing device is a monitoring and control device according to any one of the appendices 1 to 8, wherein the processing device determines a predicted value for the amount of data in the previous month as a threshold candidate for the current month, assuming that the reception cycle was changed twice in the previous month and the last day of the previous month ended without the reception cycle being changed thereafter, in the previous month's excess controller.

[0178] (Note 10) The processing device is a monitoring and control device according to any one of the appendices 1 to 9, wherein the previous month's excess controller determines the actual value of the previous month's data volume as a threshold candidate for the current month.

[0179] (Note 11) It also includes a reception area to accept user selections. The aforementioned processing device is a monitoring and control device according to any one of the appendices 1 to 10, wherein the processing device sets the threshold candidate for the current month selected by the user from among a plurality of determined threshold candidates for the current month as the threshold for the current month.

[0180] (Note 12) A control method for a monitoring and control device comprising a communication device and a processing device, The steps include: the communication device sending and receiving data to monitor or control the multiple building facilities between the multiple controllers, each of which is installed in a multiple building; The process includes the step of the processing device processing the data transmitted and received by the communication device, The charges are set such that if the total amount of data transmitted and received between the communication device and each of the multiple controllers during the current month exceeds a certain limit, the communication charges for the current month will increase. The processing step includes setting a threshold for the amount of data to be transmitted and received between each of the plurality of controllers for the current month and the communication device, The sum of the thresholds in each of the aforementioned multiple controllers is a second quantity that is smaller than the first quantity. A control method wherein, if an excess controller occurs among the plurality of controllers, which is a controller whose data volume for the current month exceeds a threshold, the data reception cycle between the excess controller and the communication device is made longer than the current reception cycle.

[0181] The embodiments disclosed herein are illustrative and not limited to those described herein. The scope of the present invention is defined by the claims, and all modifications within the meaning and scope equivalent to the claims are intended to be included. [Explanation of Symbols]

[0182] 1 monitoring and control system, 5 users, 100 monitoring and control devices, 111,411 processors, 112,412 memory, 113,413 communication interface, 220 controllers, 201 building A, 202 building B, 203 building C, 210 gateways, 400,400a,400b terminals, 420 input unit, 421 display unit, NW1,NW2 networks.

Claims

1. A communication device that transmits and receives data for monitoring or controlling multiple building facilities between multiple controllers installed in multiple buildings and multiple building facilities connected to each of the multiple controllers, The communication device comprises a processing device that processes data transmitted and received by the communication device, The charges are set such that if the total amount of data transmitted and received between the communication device and each of the multiple controllers during the current month exceeds a certain limit, the communication charges for the current month will increase. The processing device sets a threshold for the amount of data to be transmitted and received between the communication device and each of the plurality of controllers for the current month. The sum of the thresholds in each of the aforementioned plurality of controllers is a second quantity that is smaller than the first quantity. The processing device is a monitoring and control device that, when an excess controller occurs among the plurality of controllers, which is a controller whose data volume for the current month exceeds a threshold, extends the data reception cycle between the excess controller and the communication device to a longer period than the current reception cycle.

2. The aforementioned processing apparatus is Each of the aforementioned controllers periodically calculates a predicted value for the amount of data for the current month. In the aforementioned excess controller, the excess amount is calculated by subtracting a threshold from the predicted value of the data volume for the current month. In each of the controllers among the aforementioned multiple controllers whose data volume for the current month does not exceed the threshold, the reserve capacity is calculated by subtracting the predicted data volume for the current month from the threshold. The monitoring and control device according to claim 1, further extending the reception period of the excess controller to a longer period than the current reception period if the excess amount of the excess controller is greater than the sum of the remaining capacity of each of the plurality of non-excess controllers.

3. The monitoring and control device according to claim 2, wherein if any of the plurality of non-exceeding controllers have a data volume exceeding a threshold for the current month, the device excludes the controller whose data volume exceeds the threshold for the current month from the calculation of the reserve capacity.

4. The monitoring control device according to claim 3, wherein, if any of the plurality of controllers is excluded from the calculation of the surplus amount, the excess controller lengthens the reception cycle to a longer period than the current reception cycle based on the predicted value of the data volume for the current month and the value based on the first amount.

5. The aforementioned processing apparatus is In each of the aforementioned multiple controllers, the amount of data to be transmitted and received is estimated according to the type and number of signals input and output to and from the connected building equipment. A monitoring and control device according to any one of claims 1 to 4, wherein each of the plurality of controllers determines a threshold according to the estimated amount of data.

6. The monitoring control device according to claim 1, wherein the processing device changes the threshold for the current month based on the amount of data from the previous month in the previous month's excess controller among the plurality of controllers.

7. The monitoring and control device according to claim 6, wherein the processing device determines the threshold value for the current month in each of the plurality of controllers such that the sum of the threshold values ​​for the previous month in each of the plurality of controllers matches the sum of the threshold values ​​for the current month.

8. The monitoring control device according to claim 6, wherein the processing device determines a predicted value for the amount of data in the previous month as a threshold candidate for the current month, assuming that the reception cycle was changed once in the previous month and the last day of the previous month ended without the reception cycle being changed thereafter, in the previous month's excess controller.

9. The monitoring control device according to claim 6, wherein the processing device determines a predicted value of the data volume for the previous month as a threshold candidate for the current month, assuming that the reception cycle was changed twice in the previous month and the last day of the previous month ended without the reception cycle being changed thereafter, in the previous month excess controller.

10. The monitoring control device according to claim 6, wherein the processing device determines the actual value of the data volume for the previous month as a threshold candidate for the current month in the previous month's excess controller.

11. It also includes a reception area to accept user selections. The monitoring and control device according to any one of claims 8 to 10, wherein the processing device sets the threshold candidate for the current month selected by the user from among a plurality of threshold candidates for the current month that has been determined, as the threshold for the current month.

12. A control method for a monitoring and control device comprising a communication device and a processing device, The steps include: the communication device sending and receiving data to monitor or control the multiple building facilities between the multiple controllers, each of which is installed in a multiple building; The process includes the step of the processing device processing the data transmitted and received by the communication device, The charges are set such that if the total amount of data transmitted and received between the communication device and each of the multiple controllers during the current month exceeds a certain limit, the communication charges for the current month will increase. The processing step includes setting a threshold for the amount of data to be transmitted and received between each of the plurality of controllers for the current month and the communication device, The sum of the thresholds in each of the aforementioned plurality of controllers is a second quantity that is smaller than the first quantity. A control method wherein, if an excess controller occurs among the plurality of controllers, which is a controller whose data volume for the current month exceeds a threshold, the data reception cycle between the excess controller and the communication device is made longer than the current reception cycle.

Images