Building equipment monitoring device, building management system, and building management method

Abstract

Properly monitor multiple building facilities. [Solution] The monitoring server 2 includes a communication interface 25 that communicates with multiple controllers 1A to 1C, each of which collects abnormality logs indicating abnormalities that have occurred in multiple building facilities installed in multiple buildings, and an abnormality log database 262 that stores the abnormality logs acquired from the multiple controllers 1A to 1C as first abnormality logs. The processor 21 sets a log request period, which is the period during which it requests each of the multiple controllers 1A to 1C to send abnormality logs, to a different period for each building or building facility. The processor 21 acquires the abnormality logs sent from the multiple controllers 1A to 1C that have responded to the log request as second abnormality logs, and by comparing the first abnormality log and the second abnormality log, it detects a newly occurring abnormality in any of the multiple buildings or multiple building facilities.

Description

Technical Field

[0001] The present disclosure relates to a monitoring device for building facilities, a building management system, and a building management method.

Background Art

[0002] The production history management device disclosed in Japanese Patent Application Laid-Open No. 2003-241815 (Patent Document 1) includes a large-capacity storage device. The large-capacity storage device acquires material information, production information, and failure information buffered in a data collection control device at regular time intervals through a communication line, and accumulates the acquired data for a long period (see

[0023] of Patent Document 1).

[0003] The monitoring device disclosed in Japanese Patent Application Laid-Open No. 63-158696 (Patent Document 2) includes accident analysis means. The accident analysis means inputs data related to a plant accident from a data buffer after a certain time, performs predetermined accident analysis, and outputs the analysis result as an alarm signal (see the upper right column of page 2 of Patent Document 2).

Prior Art Documents

Patent Documents

[0004]

Patent Document 1

Patent Document 2

Summary of the Invention

Problems to be Solved by the Invention

[0005] Generally, a building management system includes a plurality of information devices (for example, controllers) that collect abnormal logs of a plurality of building facilities installed in a plurality of buildings locally (usually inside the building), and a monitoring device (for example, a monitoring server) that acquires abnormal logs from the plurality of information devices and monitors the plurality of building facilities from a remote location.

[0006] Monitoring devices are required to collect abnormality logs necessary for monitoring multiple building facilities. However, if the volume of abnormality log communication between multiple information devices and the monitoring device increases excessively, the load on the monitoring device will increase. This could lead to insufficient processing capacity in the monitoring device, potentially preventing it from properly processing the abnormality logs. As a result, it may become impossible to properly monitor multiple building facilities.

[0007] This disclosure was made to solve the above-mentioned problems, and one of the purposes of this disclosure is to provide a building equipment monitoring device, a building management system, and a building management method that can appropriately monitor multiple building facilities. [Means for solving the problem]

[0008] The building equipment monitoring device according to the first aspect of this disclosure comprises a communication unit that communicates with multiple information devices, each of which collects abnormality logs indicating abnormalities that have occurred in multiple building equipment installed in multiple buildings; an abnormality log database that stores the abnormality logs acquired from the multiple information devices as first abnormality logs; and a processor that performs abnormality monitoring processing for multiple building equipment. The processor sets a log request period, which is the period at which it requests each of the multiple information devices to send abnormality logs, to a different period for each building or building equipment. The processor acquires the abnormality logs transmitted from the multiple information devices that have responded to the log request as second abnormality logs, and detects a newly occurring abnormality in any of the multiple buildings or multiple building equipment by comparing the first abnormality log and the second abnormality log.

[0009] A building management method for building facilities according to a second aspect of this disclosure includes the steps of: outputting log requests from a server to a plurality of information devices to send abnormal logs to each of the plurality of information devices that collect abnormal logs indicating abnormalities that have occurred in a plurality of building facilities installed in a plurality of buildings; the server acquiring the abnormal logs sent from the plurality of information devices that responded to the log requests; and the server detecting a newly occurring abnormality in any of the plurality of buildings or a plurality of building facilities by comparing the acquired abnormal logs with the abnormal logs stored in the server's abnormal log database. The output step includes setting the log request period of the log request to a different period for each building or building facility.

[0010] In the above apparatus and method, the log request cycle is set to a different cycle for each building or building equipment. This allows, for example, the acquisition of the necessary amount of abnormality logs from buildings or building equipment that are prone to abnormalities. Alternatively or in addition, it is also possible to suppress an excessive increase in the amount of communication volume for abnormality logs from buildings or building equipment that are less prone to abnormalities. Therefore, according to the above apparatus and method, multiple building equipment can be appropriately monitored. [Effects of the Invention]

[0011] According to this disclosure, a building equipment monitoring device, a building management system, and a building management method can appropriately monitor multiple building facilities. [Brief explanation of the drawing]

[0012] [Figure 1] This figure shows an example of the overall configuration of a building management system according to Embodiment 1 of this disclosure. [Figure 2] This figure shows an example of the hardware configuration of the monitoring server in Embodiment 1. [Figure 3] This is a conceptual diagram showing an example of an abnormal log. [Figure 4] This is a functional block diagram showing an example of the functional configuration of the controller and monitoring server in Embodiment 1. [Figure 5]It is a flowchart showing an example of a processing procedure regarding the setting of the log request period in Embodiment 1. [Figure 6] It is a flowchart showing an example of a processing procedure of the abnormality monitoring process in Embodiment 1. [Figure 7] It is a diagram showing an example of the hardware configuration of the monitoring server in Embodiment 2. [Figure 8] It is a diagram for explaining the priority table set. [Figure 9] It is a diagram for explaining the conversion table. [Figure 10] It is a flowchart showing an example of a processing procedure regarding the setting of the log request period in Embodiment 2. [Figure 11] It is a flowchart showing an example of a processing procedure of the abnormality monitoring process in Embodiment 2.

Modes for Carrying Out the Invention

[0013] Hereinafter, this embodiment will be described in detail with reference to the drawings. In the drawings, the same or corresponding parts are denoted by the same reference numerals, and the description thereof will not be repeated.

[0014] [Embodiment 1] <Overall System Configuration> FIG. 1 is a diagram showing an example of the overall configuration of a building management system (BMS: Building Management System) according to Embodiment 1 of the present disclosure. The BMS 100 includes a plurality (three in FIG. 1) of controllers 1A to 1C and a monitoring server 2. The plurality of controllers 1A to 1C and the monitoring server 2 are connected so as to be able to communicate bidirectionally via a network NW such as the Internet.

[0015] Controllers 1A to 1C are respectively arranged in buildings 9A to 9C. Controller 1A collects an operation log indicating the operation information of a plurality of building facilities (such as air conditioning facilities, elevator facilities, escalator facilities, security gate facilities, lighting facilities, water supply and drainage facilities, etc.) installed in building 9A, and an abnormality log (abnormality log elements in FIG. 3) indicating the abnormalities that occurred in the plurality of building facilities. Controller 1A transmits the collected logs (operation log and abnormality log) to monitoring server 2. The same applies to the other controllers 1B and 1C. Hereinafter, when not distinguishing between controllers 1A to 1C, they are described as controller 1.

[0016] Monitoring server 2 is arranged at a remote location away from buildings 9A to 9C (for example, a central monitoring center operated by an operator who comprehensively manages many buildings). Monitoring server 2 centrally monitors a plurality of building facilities in buildings 9A to 9C by acquiring the operation log and the abnormality log from controllers 1A to 1C. Monitoring server 2 may be configured to enable remote control of each building facility via controllers 1A to 1C.

[0017] Although three buildings 9A to 9C are illustrated in FIG. 1, typically there are more buildings. However, there may be only one building. Also, although one controller is arranged in one building, two or more controllers may be arranged in one building. The two or more controllers may be provided for each building facility, or may be provided for each type of abnormality.

[0018] The plurality of controllers 1A to 1C correspond to the "plurality of information devices" according to the present disclosure. Monitoring server 2 corresponds to the "monitoring device" according to the present disclosure.

[0019] <Server configuration> FIG. 2 is a diagram showing an example of the hardware configuration of monitoring server 2 in Embodiment 1. Monitoring server 2 includes a processor 21, a memory 22, an input device 23, a display 24, a communication interface 25, and a database 26.

[0020] The processor 21 is, for example, a CPU (Central Processing Unit) and is configured to execute predetermined arithmetic processing according to a program. The memory 22 includes a ROM (Read Only Memory) 121, a RAM (Random Access Memory) 122, and an HDD (Hard Disk Drive) 123, and stores the program executed by the processor 21 and various data used by that program (maps, relational expressions, parameters, etc.). The input device 23 is a keyboard, mouse, etc., and accepts user input. The display 24 displays various information to the user. The communication interface 25 is configured to communicate with external devices (controllers 1A to 1C, etc.).

[0021] In this specification, the term "processor" is not limited to processors that execute processing using stored-program methods, but may also include hardwired circuits such as ASICs (Application Specific Integrated Circuits) and FPGAs (Field-Programmable Gate Arrays). Therefore, the term "processor" can also be interpreted as processing circuitry in which processing is predefined by computer-readable code and / or hardwired circuits.

[0022] Database 26 includes, for example, a building equipment database 261 and an anomaly log database 262. The building equipment database 261 stores information about which building equipment is installed in which buildings under management. The anomaly log database 262 stores anomaly logs.

[0023] <Error Log> Figure 3 is a conceptual diagram showing an example of an anomaly log. As shown in Figure 3, an anomaly log includes multiple anomaly log elements 31 for each detected anomaly. Anomaly log elements 31 are, for example, pieces of information in which management information 32, type information 33, and time information 34 are related to each other.

[0024] In this example, the management information 32 includes a building ID, which is a unique identifier assigned to each building in advance, and a building equipment ID, which is a unique identifier assigned to each building equipment in advance. Although not shown in the diagram, the management information 32 may also include a unique identifier (controller ID) assigned to the controller. The type information 33 includes, for example, an abnormality ID, which indicates the major category of the abnormality type, and an abnormality sub-ID, which indicates the minor category of the abnormality type. The time information 34 includes the time the abnormality occurred and the time the abnormality was resolved. If the resolution time is blank, it indicates that the abnormality has not been resolved (the abnormality is ongoing).

[0025] Figure 4 is a functional block diagram showing an example of the functional configuration of Controller 1 and Monitoring Server 2 in Embodiment 1. Controller 1 includes, for example, a communication unit 101, a log management unit 102, and an error storage unit 103. Note that only one Controller 1 is shown in Figure 4 due to space limitations. However, other controllers have a similar functional configuration.

[0026] The communication unit 101 communicates with the monitoring server 2 and with the building equipment 41-43 installed in buildings 9A-9C (see Figure 1). When a potential abnormality is detected by a sensor (not shown) installed in the building equipment, each of the building equipment 41-43 notifies the communication unit 101 of this fact (the possibility of an abnormality occurring and the type of abnormality). Each of the building equipment 41-43 may notify the communication unit 101 each time an abnormality (potential abnormality) is detected, or it may notify the communication unit 101 of multiple abnormalities detected during a certain period all at once. The communication unit 101 outputs the notifications from the building equipment 41-43 to the log management unit 102.

[0027] When the log management unit 102 receives notifications collected from building equipment 41-43, it generates an abnormal log containing new abnormal log elements and stores it in the abnormal log storage unit 103. Furthermore, at intervals set by the monitoring server 2 (details described later), the log management unit 102 reads the abnormal log stored in the abnormal log storage unit 103 and transmits the read abnormal log to the monitoring server 2 via the communication unit 101. The log management unit 102 is implemented by a processor (not shown). The abnormal log storage unit 103 is implemented by memory (not shown).

[0028] The monitoring server 2 includes, for example, a communication unit 201, a log acquisition unit 202, an anomaly detection unit 203, an anomaly storage unit 204, an anomaly notification unit 205, an anomaly display unit 206, and a period setting unit 207.

[0029] The communication unit 201 communicates with the controller 1 and the maintenance worker terminal 5. The maintenance worker terminal 5 is a device (smartphone, tablet, etc.) carried by a maintenance worker responsible for maintaining the building equipment under management.

[0030] The log acquisition unit 202 requests the controller 1 to send an abnormal log. Hereinafter, this request will be referred to as the "log request". The log request is output to the controller 1 via the communication unit 201. When the log acquisition unit 202 receives an abnormal log from the controller 1, it outputs the abnormal log to the abnormal detection unit 203.

[0031] The anomaly detection unit 203 detects anomalies in multiple building facilities based on anomaly logs. More specifically, the anomaly detection unit 203 compares a new anomaly log received from the log acquisition unit 202 with past anomaly logs stored in the anomaly storage unit 204. If there is a difference between the two anomaly logs, the anomaly detection unit 203 detects that difference as a newly occurring anomaly. When a new anomaly is detected, the anomaly detection unit 203 stores the latest anomaly log in the anomaly storage unit 204. The anomaly detection unit 203 also outputs the newly occurring anomaly to the anomaly notification unit 205 and the anomaly display unit 206.

[0032] The anomaly notification unit 205 notifies the maintenance worker terminal 5 of the newly occurring anomaly (the fact that an anomaly has occurred, and the type of anomaly that has occurred) via the communication unit 201.

[0033] The anomaly display unit 206 displays newly occurring anomalies to the monitoring personnel using the monitoring server 2. The anomaly display unit 206 is implemented by the display 24 (see Figure 2).

[0034] The period setting unit 207 sets the period for outputting log requests to the controller 1 based on the abnormal logs stored in the abnormal storage unit 204. Hereinafter, this period will be referred to as the "log request period". The log request period is set for each building or building equipment from which abnormal logs are collected by the controller 1. A specific example of the method for setting the log request period is explained in detail in Figure 5. The period setting unit 207 outputs the set log request period to the log acquisition unit 202. The log acquisition unit 202 outputs log requests to the controller 1 according to the log request period.

[0035] The communication unit 201 is implemented by a communication device (not shown) connected to the communication interface 25 (see Figure 2). The log acquisition unit 202, the anomaly notification unit 205, and the period setting unit 207 are implemented by the processor 21. The anomaly storage unit 204 is implemented by the anomaly log database 262.

[0036] <Setting the log request cycle> Figure 5 is a flowchart showing an example of the processing procedure for setting the log request cycle in Embodiment 1. The processing shown in this flowchart is executed when predetermined conditions are met (e.g., at regular intervals, when an operator operates on the input device 23). Each step is implemented by software processing by the monitoring server 2 (processor 21), but may also be implemented by hardware (electrical circuits) located within the monitoring server 2. Hereinafter, each step will be abbreviated as S.

[0037] In S101, the monitoring server 2 (period setting unit 207) analyzes the abnormal logs (corresponding to the "first abnormal log" in this disclosure) stored in the abnormal log database 262. For example, rule-based processing, statistical processing, or machine learning can be used as the analysis method. Then, based on the analysis results (results of statistical processing, rule-based processing, or machine learning) of the abnormal logs stored in the abnormal log database 262, the monitoring server 2 sets the log request period to a different period for each building or building equipment (S102).

[0038] As mentioned above, each of controllers 1A to 1C collects abnormal logs for one or more assigned buildings or one or more building facilities. Therefore, setting a different log request cycle for each building or building facility is equivalent to setting a different log request cycle for each controller. Below, we will explain three examples of abnormal log analysis methods.

[0039] (1) The monitoring server 2 calculates the expected time interval at which anomalies occur for each building or building equipment from which abnormal logs are collected by the controller 1, by performing statistical processing of the abnormal log stored in the abnormal log database 262. The monitoring server 2 may then set the log request period to be equal to or shorter than the expected value.

[0040] As one specific example, monitoring server 2 calculates the expected time interval at which an anomaly will occur in each building. If this expected value is, for example, one hour, monitoring server 2 sets the log request cycle for that building to one hour or less. Monitoring server 2 may also set the log request cycle according to the expected time interval for each building facility instead of for each building.

[0041] (2) The monitoring server 2 may set a shorter log request cycle for buildings or building equipment that have a higher number of abnormal occurrences per predetermined period, based on the results of statistical processing of abnormal logs within a specified period in the past (for example, within one year).

[0042] As one specific example, monitoring server 2 may set a shorter log request cycle for building facilities that experience multiple anomalies per predetermined period (e.g., one day) compared to building facilities that experience one or fewer anomalies per predetermined period. For example, monitoring server 2 may set the log request cycle to 6 hours for building facilities that experience one or fewer anomalies per predetermined period, while setting the log request cycle to 2 hours for building facilities that experience multiple anomalies per predetermined period. Monitoring server 2 may also set the log request cycle according to the number of anomalies per predetermined period for each building, rather than for each building facility. Note that the number of anomalies per predetermined period may be read as the frequency of anomalies or the probability of anomalies.

[0043] (3) Based on the results of statistical processing or machine learning of the abnormal logs stored in the abnormal log database 262, the monitoring server 2 identifies, for each building or building equipment, a first period in which the number of abnormal occurrences per predetermined period is high, and a second period in which the number of abnormal occurrences per predetermined period is low compared to the first period in which the number of abnormal occurrences is high. The monitoring server 2 may then set the log request cycle shorter in the first period compared to the second period.

[0044] As a specific example, monitoring server 2 identifies that for each building, the period with a high number of anomalies is during the daytime (e.g., 10am to 4pm), and the period with a low number of anomalies is at night (e.g., midnight to 6am). Monitoring server 2 sets the daytime log request cycle to 1 hour, while setting the nighttime log request cycle to 3 hours. Monitoring server 2 may also set the log request cycle according to the number of anomalies for each building facility instead of for each building.

[0045] As another specific example, for each building, numerous datasets are prepared that associate the number of anomalies per time period based on the time information 34 (especially the time of occurrence) of the anomaly logs shown in Figure 3 with the weather conditions near the building during each time period (average temperature, average precipitation, average solar radiation, etc.). Then, using machine learning with these datasets, a machine learning model (trained model) is generated that takes weather conditions as input and outputs the number of anomalies per time period. For each building, the monitoring server 2 uses the trained model to calculate the number of anomalies per time period according to the weather conditions of that building. The monitoring server 2 sets the log setting cycle to 1 hour during time periods with a high number of anomalies (e.g., weekdays), while setting the log setting cycle to 6 hours during periods with a low number of anomalies (e.g., holidays). The monitoring server 2 may also set the log request cycle according to the number of anomalies per building facility instead of per building. Note that the input to the machine learning model is not limited to weather conditions. The input to the machine learning model may be, for example, geographical conditions (e.g., the location of the building) or temporal conditions (e.g., the number of years since the installation of the building facilities).

[0046] <Overall Processing Flow> Figure 6 is a flowchart showing an example of the processing procedure for abnormality monitoring in Embodiment 1. The processing shown in this flowchart is executed when predetermined conditions are met (for example, at predetermined processing cycles). In the figure, the processing executed by Controller 1 is shown on the left, and the processing executed by Monitoring Server 2 is shown on the right. Each step is implemented by software processing by Controller 1 or Monitoring Server 2, but may also be implemented by hardware (electrical circuits) located within Controller 1 or Monitoring Server 2.

[0047] In S201, monitoring server 2 outputs log requests to controller 1 according to the log request cycle set in S102 in Figure 5.

[0048] In S202, Controller 1 determines whether it has received a log request from Monitoring Server 2. If it has received a log request (YES in S202), Controller 1 sends an abnormal log to Monitoring Server 2 in response to the log request (S203). Controller 1 may also send an operational log to Monitoring Server 2 in addition to the abnormal log. On the other hand, if it has not received a log request (NO in S202), Controller 1 skips the process in S203.

[0049] In S204, monitoring server 2 acquires abnormal logs sent from controller 1.

[0050] In S205, monitoring server 2 compares the new abnormal log acquired in S204 with past abnormal logs stored in the abnormal log database 262. Specifically, monitoring server 2 determines whether there is a difference between the two abnormal logs (S206). If there is a difference between the two abnormal logs (YES in S206), monitoring server 2 proceeds to S207.

[0051] In S207, the monitoring server 2 determines that it has detected a new anomaly corresponding to the difference. The monitoring server 2 may notify the monitoring personnel by displaying the new anomaly on the display 24, or by sending the new anomaly to the maintenance personnel terminal 5.

[0052] In S208, monitoring server 2 stores the abnormal log acquired in S204 as the latest abnormal log in the abnormal log database 262. In other words, monitoring server 2 updates the abnormal log stored in the abnormal log database 262.

[0053] If there is no difference between the two abnormal logs (NO in S206), monitoring server 2 terminates the series of processes without executing processes S207 and S208.

[0054] As described above, in Embodiment 1, the monitoring server 2 sets a log request period for each building or building equipment from which abnormal logs are collected by the controller 1. More specifically, the monitoring server 2 sets a shorter log request period for buildings or building equipment that are more prone to abnormalities. Conversely, for buildings and building equipment that are less prone to abnormalities, a longer log request period is set. This allows the monitoring server 2 to acquire the necessary amount of abnormal logs from buildings or building equipment that are prone to abnormalities. In addition, since an excessive increase in the amount of communication of abnormal logs between multiple controllers 1 and the monitoring server 2 is suppressed, it is possible to prevent the monitoring server 2 from becoming unable to process abnormal logs properly due to insufficient processing capacity (for example, missing abnormal logs). Therefore, according to Embodiment 1, multiple building equipment can be appropriately monitored.

[0055] [Embodiment 2] Embodiment 2 describes an example in which the log request cycle is set according to the priority of the building and building equipment.

[0056] Figure 7 shows an example of the hardware configuration of the monitoring server 2 in Embodiment 2. In Embodiment 2, the monitoring server 2 includes database 26A instead of database 26. Database 26A further includes a contract information database 263, a usage information database 264, a priority table set 6, and a conversion table 7, in addition to the building equipment database 261 and the abnormal log database 262.

[0057] The contract information database 263 stores contract information for buildings. The monitoring server 2 can identify the type of building based on the contract information. The usage information database 264 stores information about the usage of building facilities.

[0058] Figure 8 is a diagram illustrating priority table set 6. In this example, priority table set 6 includes priority tables 61-64.

[0059] Priority Table 61 is a table that defines priorities (indicators such as points that quantify priority) according to the type of building. Monitoring Server 2 identifies the type of building (medical facility, general office, special office, commercial facility, logistics warehouse, etc.) based on the building's contract information. Monitoring Server 2 then calculates the priority for each building according to its type by referring to Priority Table 61. The priority of a building is typically determined according to the importance, urgency, and security level of the building type. The priority of a building may also be determined according to the amount of management fees paid by the building owner to the management company (the operator of Monitoring Server 2).

[0060] Priority table 62 is a table that defines the priority of air conditioning equipment according to its intended use. Priority table 63 is a table that defines the priority of elevator equipment according to its intended use. Priority table 64 is a table that defines the priority of security gate equipment according to its intended use. Monitoring server 2 calculates the priority of each building piece of equipment according to its intended use by referring to priority tables 62 to 64. The priority of building equipment is determined, like the priority of the building, according to the importance, urgency, security level, etc. of the building equipment's intended use. Although not shown in the diagram, similar priority tables may be prepared for other types of building equipment (escalator equipment, lighting equipment, water supply and drainage equipment, etc.).

[0061] Figure 9 is a diagram illustrating the conversion table 7. As shown in Figure 9, the conversion table 7 is a table that defines the correspondence between the priority of buildings and building equipment and the log request cycle. The monitoring server 2 calculates the log request cycle according to the priority for each building or building equipment by referring to the conversion table 7.

[0062] Figure 10 is a flowchart showing an example of the processing procedure for setting the log request cycle in Embodiment 2. The processing shown in this flowchart is executed by the monitoring server 2 when predetermined conditions are met (e.g., at regular intervals, when an operator operates on the input device 23).

[0063] In S301, the monitoring server 2 (period setting unit 207) calculates the priority of a building or building equipment by referring to priority tables 61 to 64. Then, the monitoring server 2 sets the log request period for each building or building equipment according to the priority calculated in S301 (S302). As a result, the log request period is set to a different period for each building or building equipment.

[0064] Figure 11 is a flowchart showing an example of the processing procedure for abnormality monitoring in Embodiment 2. The processing shown in this flowchart is executed by the monitoring server 2 when predetermined conditions are met (for example, at predetermined processing cycles). The processing executed by the controller 1 is the same as the processing described in Figure 6, so for the sake of space, it will not be shown again.

[0065] If monitoring server 2 outputs log requests according to the log request cycle, there is a possibility that the processing timing of many log requests will overlap. Monitoring server 2 has a defined maximum number of log requests that it can process at the same time, depending on its processing capacity. The maximum processing number for monitoring server 2 is known from its specifications, and in this example, it is assumed to be 500 requests.

[0066] In S401, monitoring server 2 determines whether the number of log requests being processed at the same time exceeds the maximum processing limit.

[0067] If the number of log requests being processed exceeds the maximum processing limit (YES in S401), monitoring server 2 outputs the highest priority log requests within the maximum processing limit to controller 1 (S402). If the number of log requests being processed at the same time is 700, monitoring server 2 outputs the 500 highest priority log requests to controller 1.

[0068] In S403, the monitoring server determines whether a specified time has elapsed after outputting high-priority log requests in S402. The specified time is set to allow additional log requests to be processed, taking into account the processing capacity of monitoring server 2. Monitoring server 2 waits until the specified time has elapsed (NO in S403). Once the specified time has elapsed (YES in S403), monitoring server 2 outputs the remaining (unprocessed) log requests to controller 1 (S404). In this example, monitoring server 2 outputs 200 log requests with relatively low priority to controller 1. After that, monitoring server 2 proceeds to processing in S406.

[0069] In contrast, if the number of log requests processed at the same time is less than or equal to the maximum number of requests (NO in S41), monitoring server 2 outputs all log requests at the same time according to the log request cycle (S405). After that, monitoring server 2 proceeds to processing in S406.

[0070] The processing in S406 to S410 is the same as the processing in S204 to S208 in Embodiment 1 (see Figure 6), so the explanation will not be repeated.

[0071] This example illustrates a scenario where log requests with relatively low priority are output at a staggered timing. However, monitoring server 2 does not have to output low-priority log requests. In other words, monitoring server 2 may skip processing low-priority log requests. In this case, low-priority log requests will be processed when the next log request cycle arrives.

[0072] Monitoring server 2 does not need to determine which log requests to output first based on priority. Monitoring server 2 may, for example, simply output log requests in the order in which they were generated. Monitoring server 2 may output log requests without particularly considering the maximum number of requests that can be processed.

[0073] As described above, in Embodiment 2, the monitoring server 2 sets the log request cycle according to the type of building or the use of the building. More specifically, the monitoring server 2 sets a shorter log request cycle the higher the importance, urgency, or security level of the type of building or the use of the building. Conversely, for buildings and building facilities with relatively low importance, urgency, and security levels, the log request cycle is set to a longer length. This allows the monitoring server 2 to acquire the necessary amount of abnormal logs from buildings or building facilities with high importance, urgency, or security levels. In addition, since an excessive increase in the amount of abnormal log communication between the multiple controllers 1 and the monitoring server 2 is suppressed, it is possible to prevent the monitoring server 2 from becoming unable to process abnormal logs properly due to insufficient processing capacity. Therefore, according to Embodiment 2, multiple building facilities can be appropriately monitored.

[0074] Embodiment 1 and Embodiment 2 may be combined. That is, the monitoring server 2 may set the log request cycle to be shorter for buildings or building equipment that are more prone to abnormalities, and may also set the log request cycle to be shorter for buildings of a higher importance, urgency, or security level than the type of building or the building's use.

[0075] [Note] Finally, the various aspects of this disclosure are summarized as clauses.

[0076] <Note 1> A communication unit that communicates with multiple information devices, each of which collects anomaly logs indicating abnormalities that occurred in multiple building facilities installed in multiple buildings, An abnormal log database that stores the abnormal logs acquired from the aforementioned multiple information devices as first abnormal logs, The system includes a processor that performs abnormality monitoring processing for the aforementioned multiple building facilities, The aforementioned processor, The log request period, which is the period at which each of the multiple information devices is requested to send the aforementioned abnormal log, is set to a different period for each building or building equipment. The abnormal logs transmitted from the multiple information devices in response to the log request are acquired as a second abnormal log. A building equipment monitoring device that detects a newly occurring anomaly in any of the multiple buildings or the multiple building equipment by comparing the first anomaly log and the second anomaly log.

[0077] <Note 2> The building equipment monitoring device described in Appendix 1, wherein the processor sets the log request period based on the results of rule-based processing, statistical processing, or machine learning on the first abnormal log.

[0078] <Note 3> The aforementioned processor, By statistically processing the first anomaly log, the expected time interval at which a new anomaly occurs is calculated for each building or building equipment. A building equipment monitoring device as described in Appendix 2, which sets the log request period to be equal to or shorter than the expected value.

[0079] <Note 4> The building equipment monitoring device according to Appendix 2, wherein the processor sets the log request period shorter for buildings or building equipment where the number of occurrences of the anomaly per predetermined period is higher, based on the results of statistical processing of the first anomaly logs within a specified period in the past.

[0080] <Note 5> The aforementioned processor, Based on the results of statistical processing or machine learning of the first anomaly log, for each building or building equipment, a first period in which the number of occurrences of the anomaly per predetermined period is high, and a second period in which the number of occurrences of the anomaly per predetermined period is lower than that of the first period are identified. The building equipment monitoring device described in Appendix 2, wherein the log request cycle is set shorter during the first period compared to the second period.

[0081] <Note 6> The building equipment monitoring device according to any one of the appendices 1 to 5, wherein the processor sets the log request period to a different period for each building based on the type of building.

[0082] <Note 7> The aforementioned processor, Depending on the importance, urgency, or security level of the building, the priority for anomaly detection is calculated for each building. The building equipment monitoring device described in Appendix 6, wherein the higher the priority, the shorter the log request period is set.

[0083] <Note 8> If the number of log requests to be processed exceeds the maximum number of processing requests determined according to the processing capacity of the monitoring device, the processor processes the log requests for the building with the highest priority within the range of the maximum number of processing requests at a first timing, and processes the log requests exceeding the maximum number of processing requests at a second timing later than the first timing, as described in Appendix 7 for the building equipment monitoring device.

[0084] <Note 9> The building equipment monitoring device according to any one of the appendices 1 to 5, wherein the processor sets the log request period to a different period for each building equipment based on the use of the building equipment.

[0085] <Note 10> The aforementioned processor, The priority for detecting anomalies is calculated for each building facility according to its importance, urgency, or security level. A building equipment monitoring device as described in Appendix 9, wherein the higher the priority, the shorter the log request period is set.

[0086] <Note 11> If the number of log requests to be processed exceeds the maximum number of processing requests determined according to the processing capacity of the monitoring device, the processor processes the log requests for the building equipment with the highest priority within the range of the maximum number of processing requests at a first timing, and processes the log requests exceeding the maximum number of processing requests at a second timing later than the first timing, as described in Appendix 10.

[0087] <Note 12> A monitoring device for building equipment described in any one of the items 1 to 11 of the appendices, A building management system comprising the aforementioned multiple information devices.

[0088] <Note 13> The steps include: outputting a log request from the server to multiple information devices so as to send the abnormal log to each of the multiple information devices that collect abnormal logs indicating abnormalities that have occurred in multiple building facilities installed in multiple buildings; The steps include: acquiring the abnormal logs transmitted from the multiple information devices in response to the log request by the server; The process includes the step of having the server detect a newly occurring anomaly in any of the multiple buildings or the multiple building facilities by comparing the acquired anomaly log with the anomaly log stored in the server's anomaly log database, A building management method comprising the step of setting the log request period of the log request to a different period for each building or building equipment, wherein the output step includes setting the log request period of the log request to a different period for each building or building equipment.

[0089] The embodiments disclosed herein should be considered in all respects to be illustrative and not restrictive. The scope of this disclosure is indicated by the claims rather than by the description of the embodiments above, and all modifications within the meaning and scope equivalent to the claims are intended to be included. [Explanation of Symbols]

[0090] 1,1A,1B,1C Controller, 101 Communication Unit, 102 Log Management Unit, 103 Anomaly Storage Unit, 2 Monitoring Server, 21 Processor, 22 Memory, 23 Input Device, 24 Display, 25 Communication Interface, 26,26A Database, 201 Communication Unit, 202 Log Acquisition Unit, 203 Anomaly Detection Unit, 204 Anomaly Storage Unit, 205 Anomaly Notification Unit, 206 Anomaly Display Unit, 207 Cycle Setting Unit, 261 Building Equipment Database, 262 Anomaly Log Database, 263 Contract Information Database, 264 Usage Information Database, 31 Anomaly Log Element, 32 Management Information, 33 Type Information, 34 Time Information, 41~43,ID Building Equipment, 5 Maintenance Personnel Terminal, 6 Priority Table Set, 61~64 Priority Table, 7 Conversion Table, 9A,9B,9C Building.

Claims

1. A communication unit that communicates with multiple information devices, each of which collects anomaly logs indicating abnormalities that occurred in multiple building facilities installed in multiple buildings, An abnormal log database that stores the abnormal logs acquired from the aforementioned multiple information devices as first abnormal logs, The system includes a processor that performs abnormality monitoring processing for the aforementioned multiple building facilities, The aforementioned processor, The log request period, which is the period at which each of the multiple information devices is requested to send the aforementioned abnormal log, is set to a different period for each building or building equipment. The abnormal logs transmitted from the multiple information devices in response to the log request are acquired as a second abnormal log. A building equipment monitoring device that detects a newly occurring anomaly in any of the multiple buildings or the multiple building equipment by comparing the first anomaly log with the second anomaly log.

2. The building equipment monitoring device according to claim 1, wherein the processor sets the log request period based on the results of rule-based processing, statistical processing, or machine learning on the first abnormal log.

3. The aforementioned processor, By statistically processing the first anomaly log, the expected time interval at which a new anomaly occurs is calculated for each building or building equipment. A building equipment monitoring device according to claim 2, wherein the log request period is set to be equal to or shorter than the expected value.

4. The building equipment monitoring device according to claim 2, wherein the processor sets the log request period shorter for buildings or building equipment where the number of occurrences of the anomaly per predetermined period is greater, based on the results of statistical processing of the first anomaly logs within a specified period in the past.

5. The aforementioned processor, Based on the results of statistical processing or machine learning of the first anomaly log, for each building or building equipment, a first period in which the number of occurrences of the anomaly per predetermined period is high, and a second period in which the number of occurrences of the anomaly per predetermined period is lower than that of the first period are identified. The building equipment monitoring device according to claim 2, wherein in the first period, the log request period is set to be shorter than in the second period.

6. The building equipment monitoring device according to any one of claims 1 to 5, wherein the processor sets the log request period to a different period for each building based on the type of building.

7. The aforementioned processor, Depending on the importance, urgency, or security level of the building, the priority for anomaly detection is calculated for each building. The building equipment monitoring device according to claim 6, wherein the higher the priority, the shorter the log request period is set.

8. If the number of log requests to be processed exceeds a maximum number of processing requests determined according to the processing capacity of the monitoring device, the processor processes the log requests for the building with the highest priority within the range of the maximum number of processing requests at a first timing, and processes the log requests exceeding the maximum number of processing requests at a second timing later than the first timing, as described in claim 7.

9. The building equipment monitoring device according to any one of claims 1 to 5, wherein the processor sets the log request period to a different period for each building equipment based on the use of the building equipment.

10. The aforementioned processor, The priority for detecting anomalies is calculated for each building facility according to its importance, urgency, or security level. The building equipment monitoring device according to claim 9, wherein the higher the priority, the shorter the log request period is set.

11. If the number of log requests to be processed exceeds a maximum number of processing requests determined according to the processing capacity of the monitoring device, the processor processes the log requests for the building equipment with the highest priority within the range of the maximum number of processing requests at a first timing, and processes the log requests exceeding the maximum number of processing requests at a second timing later than the first timing, as described in claim 10.

12. A building equipment monitoring device according to any one of claims 1 to 5, A building management system comprising the aforementioned multiple information devices.

13. The steps include: outputting a log request from the server to multiple information devices so as to send the abnormal log to each of the multiple information devices that collect abnormal logs indicating abnormalities that have occurred in multiple building facilities installed in multiple buildings; The steps include: acquiring the abnormal logs transmitted from the multiple information devices in response to the log request by the server; The process includes the step of having the server detect a newly occurring anomaly in any of the multiple buildings or the multiple building facilities by comparing the acquired anomaly log with the anomaly log stored in the server's anomaly log database, A building management method comprising the step of setting the log request period of the log request to a different period for each building or building equipment, wherein the output step includes setting the log request period of the log request to a different period for each building or building equipment.

Images