Patent Application
20190025776
This application claims the benefit of and the priority to Indian Provisional Patent Application No. 2017/41025951 filed Jul. 21, 2017, the entire disclosure of which is incorporated by reference herein.
The present disclosure relates generally to the field of building management systems. A building management system (BMS) is, in general, a system of devices configured to control, monitor, and manage equipment in or around a building or building area. A BMS can include, for example, a HVAC system, a security system, a lighting system, a fire alerting system, any other system that is capable of managing building functions or devices, or any combination thereof. Specifically, the present disclosure relates to a BMS with an equipment monitoring system to easily determine when the BMS is experiencing a fault.
One implementation of the present disclosure is a building management system for monitoring equipment status, the building management system comprising a processing circuit. The processing circuit is configured to generate one or more constants for a piece of building equipment based on thresholds and device specific templates, wherein the constants are equation based relationships between a value and a threshold. The processing circuit is further configured to generate one or more sub-rules based on the one or more constants, wherein the sub-rules are equation based relationships between the one or more constants. The processing circuit is further configured to generate a rule based on the one or more sub-rules, wherein the rule is an equation based relationship between the one or more sub-rules and indicates whether the piece of building equipment is experiencing a fault.
In some embodiments, the processing circuit of the building management system is further configured to identify a fault for the building equipment based on the rule and measured values for the building equipment.
In some embodiments, the processing circuit of the building management system is further configured to determine one or more diagnostics based on a fault by identifying the fault for the building equipment based on the rule and measured values for the building equipment, determining sub-rules and constants that the rule is based on that are responsible for indicating the fault, and generating a diagnostic based on the determined sub-rules and constants.
In some embodiments, the processing circuit of the building management system is further configured to determine reasons for the fault occurring based on the determined sub-rules and constants and one or more fault reasons associated with the determined sub-rules and constants.
In some embodiments, the processing circuit of the building management system is further configured to generate a plurality of rules based on the one or more sub-rules, determine a plurality of faults based on the plurality rules and determine the length of time that the fault has been active, and generate a plurality of diagnostics based on the one or more faults.
In some embodiments, the processing circuit of the building management system is further configured to generate a diagnostic list comprising the plurality diagnostics ordered based on the determined length of time that each of the faults associated with the diagnostic has been active.
In some embodiments, the processing circuit of the building management system is further configured to generate a work order for one of the plurality of faults in response to determining that the fault has existed for at least a predefined amount of time or that the fault has occurred for at least a predefined number of times.
Another implementation of the present disclosure is a method for monitoring equipment status by a building management system. The method includes generating, by a processing circuit, one or more constants for a piece of building equipment based on thresholds and device specific templates, wherein the constants are equation based relationships between a value and a threshold. The method further includes generating, by the processing circuit, one or more sub-rules based on the one or more constants, wherein the sub-rules are equation based relationships between the one or more constants. The method further includes generating, by the processing circuit, a rule based on the one or more sub-rules, wherein the rule is an equation based relationship between the one or more sub-rules and indicates whether the piece of building equipment is experiencing a fault.
In some embodiments, the method further includes identifying a fault for the building equipment based on the rule and measured values for the building equipment.
In some embodiments, the method further includes determining one or more diagnostics based on a fault by identifying the fault for the building equipment based on the rule and measured values for the building equipment, determining sub-rules and constants that the rule is based on that are responsible for indicating the fault, and generating a diagnostic based on the determined sub-rules and constants.
In some embodiments, the method further includes determining reasons for the fault occurring based on the determined sub-rules and constants and one or more fault reasons associated with the determined sub-rules and constants.
In some embodiments, the method further includes generating a plurality of rules based on the one or more sub-rules, determining a plurality of faults based on the plurality rules and determine the length of time that the fault has been active, and generating a plurality of diagnostics based on the one or more faults. generating a diagnostic list comprising the plurality diagnostics ordered based on the determined length of time that each of the faults associated with the diagnostic has been active.
In some embodiments, the method further includes generating a diagnostic list comprising the plurality diagnostics ordered based on the determined length of time that each of the faults associated with the diagnostic has been active.
In some embodiments, the method further includes generating a work order for one of the plurality of faults in response to determining that the fault has existed for at least a predefined amount of time or that the fault has occurred for at least a predefined number of times.
Another implementation of the present disclosure is a building management controller for monitoring equipment status, the building management controller comprising a processing circuit. The processing circuit is configured to generate one or more constants for a piece of building equipment based on thresholds and device specific templates, wherein the constants are equation based relationships between a value and a threshold. The processing circuit is further configured to generate one or more sub-rules based on the one or more constants, wherein the sub-rules are equation based relationships between the one or more constants. The processing circuit is further configured to generate a rule based on the one or more sub-rules, wherein the rule is an equation based relationship between the one or more sub-rules and indicates whether the piece of building equipment is experiencing a fault. The processing circuit is further configured to identify a fault for the building equipment based on the rule and measured values for the building equipment.
In some embodiments, the processing circuit of the building management controller is further configured to determine one or more diagnostics based on a fault by identifying the fault for the building equipment based on the rule and measured values for the building equipment, determining sub-rules and constants that the rule is based on that are responsible for indicating the fault, and generating a diagnostic based on the determined sub-rules and constants.
In some embodiments, the processing circuit of the building management controller is further configured to determine reasons for the fault occurring based on the determined sub-rules and constants and one or more fault reasons associated with the determined sub-rules and constants.
In some embodiments, the processing circuit of the building management controller is further configured to generate a plurality of rules based on the one or more sub-rules, determine a plurality of faults based on the plurality rules and determine the length of time that the fault has been active, and generate a plurality of diagnostics based on the one or more faults.
In some embodiments, the processing circuit of the building management controller is further configured to generate a diagnostic list comprising the plurality diagnostics ordered based on the determined length of time that each of the faults associated with the diagnostic has been active.
In some embodiments, the processing circuit of the building management controller is further configured to generate a work order for one of the plurality of faults in response to determining that the fault has existed for at least a predefined amount of time or that the fault has occurred for at least a predefined number of times.
Dynamic Rules with Sub-Rule Re-Use and Equation Driven Smart Diagnostics
Referring generally to the FIGURES, systems and methods for dynamic rules with sub-rule re-use and equation driven smart diagnostics are shown, according to various exemplary embodiments. A building, e.g., building 10 of
The characteristics can be formed into a template for each type of device of a building. The building controller can be configured to generate constants which incorporate the device specific templates and various thresholds for the templates. The thresholds may be defined by the building controller and/or manually by a user and may be based on design conditions and/or site specific conditions. The building controller can be configured to use the constants in generating rules, sub-rules, and/or performing diagnostics. Any changes to a constant would automatically be realized in changes in the rules, sub-rules, or equation driven diagnostics that use the constants. Similarly, any changes to a sub-rule would automatically cause a change in any rules and/or equation driven diagnostics that utilize the sub-rule.
The sub-rules generated by the building controller can be an amalgamation of arithmetic/logical operands and constants. The sub-rules, when triggered, may indicate that a piece of building equipment is experiencing a fault or may indicate a particular operating condition of the piece of equipment. The sub-rules may indicate various statuses of a piece of equipment, for example, a sub-rule could be whether an AHU (e.g., AHU 116) is operational. The building controller can use the sub-rules to trigger equipment faults. The building controller can be configured to use the sub-rules to generate higher-level rules or to be used in equation driven diagnostics (e.g., diagnostic rules). Both the diagnostics functions that the building controller can be configured to perform and the rules may be equation driven and thus can incorporate the sub-rules. By modularly combining the sub-rules into rules and/or equation driven diagnostics, any change that is necessary for a rule and/or equation driven diagnostic can be realized by changing the sub-rules.
By changing a single sub-rule, a change across numerous rules and/or equation driven diagnostics that utilize the sub-rule can be realized by the building controller. By modularly combing sub-rules into rules and/or equation driven diagnostics, the amount of manual work required in setting up rules or equation driven diagnostics can be reduced. For example, if the rules and diagnostics did not modularly incorporate sub-rules, if a user wanted to universally change a single low level rule for multiple rules and diagnostics, the user would manually have to change every single rule and/or equation based diagnostic.
Diagnostics that can be generated via the building controller can be generated based on the sub-rules and/or rules e.g., diagnostic equations that can use the sub-rules and/or rules to generate the diagnostics. The diagnostic equations may be equation based, thus allowing for equation driven diagnostic generation. The building controller can be configured to generate a diagnostic list. Since the diagnostic equations are equation driven, the diagnostic list may be a list of diagnostics in order of duration. This may allow a technician to view how long the condition associated with the diagnostic has existed. This may allow a technician to view multiple diagnostics and determine from among the diagnostics, which diagnostic identifies what is causing the fault for the equipment. By having a dynamic list, a user may not need to sort through a static list to manually identify what has occurred that has caused a fault and thus to determine the proper diagnostic requires more manual user work. An example of lists of diagnostics is in
An example of constants, sub-rules, and rules, for an AHU (e.g., AHU 116) of a building (e.g., building 10) is as follows in an example. A constant for the AHU may be that supply air fan output being greater than a particular amount indicates that the AHU is operating (e.g., it is on and functioning). The constant may be based on a device specific template for AHUs that indicates that the output of the supply air fan should be greater than a threshold amount. The particular threshold amount and the device specific template can be combined to generate the constant for the AHU. In this example, the threshold amount may be zero. The constant can be realized as, “Supply Air Fan Output >0.”
A sub-rule for the AHU may incorporate the constant and/or multiple constants or equipment points. For example, a sub-rule may indicate whether the AHU is operating or not. The sub-rule may include two separate constants, the constants may be “Supply Air Fan Status >0” and the previously discussed constant, “Supply Air Fan Output >0.” The sub-rule may indicate that if either of the constants is true, the AHU is operating. The sub-rule as a whole may be realized as, “(Supply Air Fan Status >0) OR (Supply Air Fan Output >0).” The sub-rule may be seen below in the high level rule as “AHU Operational.”
Sub-rules for the AHU may further be based on equipment points. An equipment point may be an attribute, a variable, or a parameter associated with a piece of building equipment. An equipment point may be a measurement taken by a sensor, such as a temperature point or flow rate of the supply airflow. Additionally, an equipment point may be an attribute used to describe a piece of building equipment, such as a name. Equipment points may also be used to generate rules.
The high level rule may be based on the sub-rule and/or multiple sub-rules. The following high level rule may determine if the supply air pressure is above a setpoint. The high level rule may include the sub-rule discussed above and another sub-rule which indicates whether supply air pressure is higher than a setpoint. In this regard, the sub-rules can be combined into the rule with a Boolean AND comparison. The high level rule may be “(AHU Operational >0) AND (Supply Air Pressure Higher Than Supply Air Pressure Setpoint Point >0).” This high level rule may only trigger if the AHU is operating and the measured pressure has exceeded a setpoint.
Dynamic Work-Order Generation with Adaptive Diagnostic Task Details
The building controller can be configured to perform dynamic work-order generation with adaptive diagnostic task details. The work order system of the building controller can be a mechanism by which faults of equipment of a building are fixed by automatically assigning work orders to technicians, the task details being specific to a current fault in the system. The building controller can leverage rules, sub-rules, and diagnostic methods of the building controller to populate a work order with possible and/or probable causes of equipment faults and indicate tasks that the assigned technician needs to complete to resolve the fault.
The building controller can be configured to generate the work order in response to receiving a command from a user i.e., a user may observe a fault and indicate the fault to the building controller to generate a work order. The work order may be “Fix AHU.” The building controller can be configured to fill in tasks in the work order for fixing the AHU. When the technician opens the generated work order, the technician can view the details for the tasks. The details may be based on faults and associated diagnostics. The building controller can be configured to cause the work order to include where the fault of the work order has occurred (e.g., what building, what floor, what room) and further what tasks the technician needs to perform (e.g., what systems or values need to be tested or checked). The work order may indicate one or more faults. A user may click or otherwise interact with the faults to view the causes for the fault and task details which may indicate to a technician how to resolve the fault. This may give a technician an idea of what needs to be fixed and what equipment, parts, or tools that the technician needs to bring to a job site.
Since the work order generated by the building controller can pinpoint the cause of equipment faults and includes a diagnostic and a task description, the technician knows, via the work order, what equipment and/or parts the technician needs to bring to a job site before departing to the job site. This prevents multiple trips from a technician base and a particular job site. The work orders generated by the building controller may include general information. The general information may include location, time of fault, etc. The work order may further include run hours (e.g., how long the particular fault has existed). The building controller can be configured to automatically generate the work order after the fault is present for a predefined amount of time. Further, the work orders may include the current state of the building equipment, for example, may state that there is a problem with a particular piece of equipment.
The building controller can be configured to use rules, sub-rules, and/or equation driven diagnostics in generating the work orders. Based on the rules, sub-rules, equation driven diagnostics, and/or other information, the equipment at issue can be identified, the time the issued occurred can be identified, spaces and/or buildings served by the equipment experiencing the issue is identified, the location of the particular piece of equipment, and/or what tasks or diagnostics should be done and/or have already been performed. This may link a general fault to the underlying equipment.
The building controller can include auto thresholds that it uses in generating a work order. If an issue in a piece of equipment is active for a predefined amount of time, the building controller can be configured to generate the work order. The predefined amount of time could be three days, five days, seven days, and/or any amount of time. The work order could be generated if a particular rule is triggered a particular amount of times and/or for particular durations of time. This may take into account both persistence of a fault (e.g., the length of time the fault has been active), and the number of occurrences of the fault. For example, the building controller can be configured to generate a work order if a rule indicates a fault for a first number of times during a predefined amount of time. Another example is that the building controller generates the work order if the issue has occurred for a particular amount of time over the course of another amount of time (e.g., the fault has been active three days out of a week).
The building controller can be configured to automatically assign the work order to a particular technician team based on the nature of the work order. For example, a particular team may specialize in fixing AHUs while another team may specializing in fixing device networks in a building. Work orders for AHUs may be assigned to the AHU team while work orders associated with building networks may be assigned to the building network team. The building controller can be configured to generate the work orders to include lists of actions to perform in resolving faults. For example, the work order may indicate which pieces of equipment in a system are likely responsible for the fault. This may allow a user to diagnose a system piece by piece in order of pertinence.
Referring now to
The BAS that serves building 10 includes an HVAC system 100. HVAC system 100 can include a plurality of HVAC devices (e.g., heaters, chillers, air handling units, pumps, fans, thermal energy storage, etc.) configured to provide heating, cooling, ventilation, or other services for building 10. For example, HVAC system 100 is shown to include a waterside system 120 and an airside system 130. Waterside system 120 can provide a heated or chilled fluid to an air handling unit of airside system 130. Airside system 130 can use the heated or chilled fluid to heat or cool an airflow provided to building 10. An exemplary waterside system and airside system which can be used in HVAC system 100 are described in greater detail with reference to
HVAC system 100 is shown to include a chiller 102, a boiler 104, and a rooftop air handling unit (AHU) 106. Waterside system 120 can use boiler 104 and chiller 102 to heat or cool a working fluid (e.g., water, glycol, etc.) and can circulate the working fluid to AHU 106. In various embodiments, the HVAC devices of waterside system 120 can be located in or around building 10 (as shown in
AHU 106 can place the working fluid in a heat exchange relationship with an airflow passing through AHU 106 (e.g., via one or more stages of cooling coils and/or heating coils). The airflow can be, for example, outside air, return air from within building 10, or a combination of both. AHU 106 can transfer heat between the airflow and the working fluid to provide heating or cooling for the airflow. For example, AHU 106 can include one or more fans or blowers configured to pass the airflow over or through a heat exchanger containing the working fluid. The working fluid can then return to chiller 102 or boiler 104 via piping 110.
Airside system 130 can deliver the airflow supplied by AHU 106 (i.e., the supply airflow) to building 10 via air supply ducts 112 and can provide return air from building 10 to AHU 106 via air return ducts 114. In some embodiments, airside system 130 includes multiple variable air volume (VAV) units 116. For example, airside system 130 is shown to include a separate VAV unit 116 on each floor or zone of building 10. VAV units 116 can include dampers or other flow control elements that can be operated to control an amount of the supply airflow provided to individual zones of building 10. In other embodiments, airside system 130 delivers the supply airflow into one or more zones of building 10 (e.g., via supply ducts 112) without using intermediate VAV units 116 or other flow control elements. AHU 106 can include various sensors (e.g., temperature sensors, pressure sensors, etc.) configured to measure attributes of the supply airflow. AHU 106 can receive input from sensors located within AHU 106 and/or within the building zone and can adjust the flow rate, temperature, or other attributes of the supply airflow through AHU 106 to achieve setpoint conditions for the building zone.
Referring now to
In
Hot water loop 214 and cold water loop 216 can deliver the heated and/or chilled water to air handlers located on the rooftop of building 10 (e.g., AHU 106) or to individual floors or zones of building 10 (e.g., VAV units 116). The air handlers push air past heat exchangers (e.g., heating coils or cooling coils) through which the water flows to provide heating or cooling for the air. The heated or cooled air can be delivered to individual zones of building 10 to serve the thermal energy loads of building 10. The water then returns to subplants 202-212 to receive further heating or cooling.
Although subplants 202-212 are shown and described as heating and cooling water for circulation to a building, it is understood that any other type of working fluid (e.g., glycol, CO2, etc.) can be used in place of or in addition to water to serve the thermal energy loads. In other embodiments, subplants 202-212 can provide heating and/or cooling directly to the building or campus without requiring an intermediate heat transfer fluid. These and other variations to waterside system 200 are within the teachings of the present invention.
Each of subplants 202-212 can include a variety of equipment configured to facilitate the functions of the subplant. For example, heater subplant 202 is shown to include a plurality of heating elements 220 (e.g., boilers, electric heaters, etc.) configured to add heat to the hot water in hot water loop 214. Heater subplant 202 is also shown to include several pumps 222 and 224 configured to circulate the hot water in hot water loop 214 and to control the flow rate of the hot water through individual heating elements 220. Chiller subplant 206 is shown to include a plurality of chillers 232 configured to remove heat from the cold water in cold water loop 216. Chiller subplant 206 is also shown to include several pumps 234 and 236 configured to circulate the cold water in cold water loop 216 and to control the flow rate of the cold water through individual chillers 232.
Heat recovery chiller subplant 204 is shown to include a plurality of heat recovery heat exchangers 226 (e.g., refrigeration circuits) configured to transfer heat from cold water loop 216 to hot water loop 214. Heat recovery chiller subplant 204 is also shown to include several pumps 228 and 230 configured to circulate the hot water and/or cold water through heat recovery heat exchangers 226 and to control the flow rate of the water through individual heat recovery heat exchangers 226. Cooling tower subplant 208 is shown to include a plurality of cooling towers 238 configured to remove heat from the condenser water in condenser water loop 218. Cooling tower subplant 208 is also shown to include several pumps 240 configured to circulate the condenser water in condenser water loop 218 and to control the flow rate of the condenser water through individual cooling towers 238.
Hot TES subplant 210 is shown to include a hot TES tank 242 configured to store the hot water for later use. Hot TES subplant 210 can also include one or more pumps or valves configured to control the flow rate of the hot water into or out of hot TES tank 242. Cold TES subplant 212 is shown to include cold TES tanks 244 configured to store the cold water for later use. Cold TES subplant 212 can also include one or more pumps or valves configured to control the flow rate of the cold water into or out of cold TES tanks 244.
In some embodiments, one or more of the pumps in waterside system 200 (e.g., pumps 222, 224, 228, 230, 234, 236, and/or 240) or pipelines in waterside system 200 include an isolation valve associated therewith. Isolation valves can be integrated with the pumps or positioned upstream or downstream of the pumps to control the fluid flows in waterside system 200. In various embodiments, waterside system 200 can include more, fewer, or different types of devices and/or subplants based on the particular configuration of waterside system 200 and the types of loads served by waterside system 200.
Referring now to
In
Each of dampers 316-320 can be operated by an actuator. For example, exhaust air damper 316 can be operated by actuator 324, mixing damper 318 can be operated by actuator 326, and outside air damper 320 can be operated by actuator 328. Actuators 324-328 can communicate with an AHU controller 330 via a communications link 332. Actuators 324-328 can receive control signals from AHU controller 330 and can provide feedback signals to AHU controller 330. Feedback signals can include, for example, an indication of a current actuator or damper position, an amount of torque or force exerted by the actuator, diagnostic information (e.g., results of diagnostic tests performed by actuators 324-328), status information, commissioning information, configuration settings, calibration data, and/or other types of information or data that can be collected, stored, or used by actuators 324-328. AHU controller 330 can be an economizer controller configured to use one or more control algorithms (e.g., state-based algorithms, extremum seeking control (ESC) algorithms, proportional-integral (PI) control algorithms, proportional-integral-derivative (PID) control algorithms, model predictive control (MPC) algorithms, feedback control algorithms, etc.) to control actuators 324-328.
Still referring to
Cooling coil 334 can receive a chilled fluid from waterside system 200 (e.g., from cold water loop 216) via piping 342 and can return the chilled fluid to waterside system 200 via piping 344. Valve 346 can be positioned along piping 342 or piping 344 to control a flow rate of the chilled fluid through cooling coil 334. In some embodiments, cooling coil 334 includes multiple stages of cooling coils that can be independently activated and deactivated (e.g., by AHU controller 330, by BAS controller 366, etc.) to modulate an amount of cooling applied to supply air 310.
Heating coil 336 can receive a heated fluid from waterside system 200 (e.g., from hot water loop 214) via piping 348 and can return the heated fluid to waterside system 200 via piping 350. Valve 352 can be positioned along piping 348 or piping 350 to control a flow rate of the heated fluid through heating coil 336. In some embodiments, heating coil 336 includes multiple stages of heating coils that can be independently activated and deactivated (e.g., by AHU controller 330, by BAS controller 366, etc.) to modulate an amount of heating applied to supply air 310.
Each of valves 346 and 352 can be controlled by an actuator. For example, valve 346 can be controlled by actuator 354 and valve 352 can be controlled by actuator 356. Actuators 354-356 can communicate with AHU controller 330 via communications links 358-360. Actuators 354-356 can receive control signals from AHU controller 330 and can provide feedback signals to controller 330. In some embodiments, AHU controller 330 receives a measurement of the supply air temperature from a temperature sensor 362 positioned in supply air duct 312 (e.g., downstream of cooling coil 334 and/or heating coil 336). AHU controller 330 can also receive a measurement of the temperature of building zone 306 from a temperature sensor 364 located in building zone 306.
In some embodiments, AHU controller 330 operates valves 346 and 352 via actuators 354-356 to modulate an amount of heating or cooling provided to supply air 310 (e.g., to achieve a setpoint temperature for supply air 310 or to maintain the temperature of supply air 310 within a setpoint temperature range). The positions of valves 346 and 352 affect the amount of heating or cooling provided to supply air 310 by cooling coil 334 or heating coil 336 and may correlate with the amount of energy consumed to achieve a desired supply air temperature. AHU controller 330 can control the temperature of supply air 310 and/or building zone 306 by activating or deactivating coils 334-336, adjusting a speed of fan 338, or a combination of both.
Still referring to
In some embodiments, AHU controller 330 receives information from BAS controller 366 (e.g., commands, setpoints, operating boundaries, etc.) and provides information to BAS controller 366 (e.g., temperature measurements, valve or actuator positions, operating statuses, diagnostics, etc.). For example, AHU controller 330 can provide BAS controller 366 with temperature measurements from temperature sensors 362-364, equipment on/off states, equipment operating capacities, and/or any other information that can be used by BAS controller 366 to monitor or control a variable state or condition within building zone 306.
Client device 368 can include one or more human-machine interfaces or client interfaces (e.g., graphical user interfaces, reporting interfaces, text-based computer interfaces, client-facing web services, web servers that provide pages to web clients, etc.) for controlling, viewing, or otherwise interacting with HVAC system 100, its subsystems, and/or devices. Client device 368 can be a computer workstation, a client terminal, a remote or local interface, or any other type of user interface device. Client device 368 can be a stationary terminal or a mobile device. For example, client device 368 can be a desktop computer, a computer server with a user interface, a laptop computer, a tablet, a smartphone, a PDA, or any other type of mobile or non-mobile device. Client device 368 can communicate with BAS controller 366 and/or AHU controller 330 via communications link 372.
Referring now to
Each of building subsystems 428 can include any number of devices, controllers, and connections for completing its individual functions and control activities. HVAC subsystem 440 can include many of the same components as HVAC system 100, as described with reference to
Still referring to
Interfaces 407, 409 can be or include wired or wireless communications interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wire terminals, etc.) for conducting data communications with building subsystems 428 or other external systems or devices. In various embodiments, communications via interfaces 407, 409 can be direct (e.g., local wired or wireless communications) or via a communications network 446 (e.g., a WAN, the Internet, a cellular network, etc.). For example, interfaces 407, 409 can include an Ethernet card and port for sending and receiving data via an Ethernet-based communications link or network. In another example, interfaces 407, 409 can include a Wi-Fi transceiver for communicating via a wireless communications network. In another example, one or both of interfaces 407, 409 can include cellular or mobile phone communications transceivers. In one embodiment, communications interface 407 is a power line communications interface and BAS interface 409 is an Ethernet interface. In other embodiments, both communications interface 407 and BAS interface 409 are Ethernet interfaces or are the same Ethernet interface.
Still referring to
Memory 408 (e.g., memory, memory unit, storage device, etc.) can include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage, etc.) for storing data and/or computer code for completing or facilitating the various processes, layers and modules described in the present application. Memory 408 can be or include volatile memory or non-volatile memory. Memory 408 can include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present application. According to an exemplary embodiment, memory 408 is communicably connected to processor 406 via processing circuit 404 and includes computer code for executing (e.g., by processing circuit 404 and/or processor 406) one or more processes described herein.
In some embodiments, BAS controller 366 is implemented within a single computer (e.g., one server, one housing, etc.). In various other embodiments BAS controller 366 can be distributed across multiple servers or computers (e.g., that can exist in distributed locations). Further, while
Still referring to
Enterprise integration layer 410 can be configured to serve clients or local applications with information and services to support a variety of enterprise-level applications. For example, enterprise control applications 426 can be configured to provide subsystem-spanning control to a graphical user interface (GUI) or to any number of enterprise-level business applications (e.g., accounting systems, user identification systems, etc.). Enterprise control applications 426 can also or alternatively be configured to provide configuration GUIs for configuring BAS controller 366. In yet other embodiments, enterprise control applications 426 can work with layers 410-420 to optimize building performance (e.g., efficiency, energy use, comfort, or safety) based on inputs received at interface 407 and/or BAS interface 409.
Building subsystem integration layer 420 can be configured to manage communications between BAS controller 366 and building subsystems 428. For example, building subsystem integration layer 420 can receive sensor data and input signals from building subsystems 428 and provide output data and control signals to building subsystems 428. Building subsystem integration layer 420 can also be configured to manage communications between building subsystems 428. Building subsystem integration layer 420 translate communications (e.g., sensor data, input signals, output signals, etc.) across a plurality of multi-vendor/multi-protocol systems.
Demand response layer 414 can be configured to optimize resource usage (e.g., electricity use, natural gas use, water use, etc.) and/or the monetary cost of such resource usage in response to satisfy the demand of building 10. The optimization can be based on time-of-use prices, curtailment signals, energy availability, or other data received from utility providers, distributed energy generation systems 424, from energy storage 427 (e.g., hot TES 242, cold TES 244, etc.), or from other sources. Demand response layer 414 can receive inputs from other layers of BAS controller 366 (e.g., building subsystem integration layer 420, integrated control layer 418, etc.). The inputs received from other layers can include environmental or sensor inputs such as temperature, carbon dioxide levels, relative humidity levels, air quality sensor outputs, occupancy sensor outputs, room schedules, and the like. The inputs can also include inputs such as electrical use (e.g., expressed in kWh), thermal load measurements, pricing information, projected pricing, smoothed pricing, curtailment signals from utilities, and the like.
According to an exemplary embodiment, demand response layer 414 includes control logic for responding to the data and signals it receives. These responses can include communicating with the control algorithms in integrated control layer 418, changing control strategies, changing setpoints, or activating/deactivating building equipment or subsystems in a controlled manner. Demand response layer 414 can also include control logic configured to determine when to utilize stored energy. For example, demand response layer 414 can determine to begin using energy from energy storage 427 just prior to the beginning of a peak use hour.
In some embodiments, demand response layer 414 includes a control module configured to actively initiate control actions (e.g., automatically changing setpoints) which minimize energy costs based on one or more inputs representative of or based on demand (e.g., price, a curtailment signal, a demand level, etc.). In some embodiments, demand response layer 414 uses equipment models to determine an optimal set of control actions. The equipment models can include, for example, thermodynamic models describing the inputs, outputs, and/or functions performed by various sets of building equipment. Equipment models can represent collections of building equipment (e.g., subplants, chiller arrays, etc.) or individual devices (e.g., individual chillers, heaters, pumps, etc.).
Demand response layer 414 can further include or draw upon one or more demand response policy definitions (e.g., databases, XML files, etc.). The policy definitions can be edited or adjusted by a user (e.g., via a graphical user interface) so that the control actions initiated in response to demand inputs can be tailored for the user's application, desired comfort level, particular building equipment, or based on other concerns. For example, the demand response policy definitions can specify which equipment can be turned on or off in response to particular demand inputs, how long a system or piece of equipment should be turned off, what setpoints can be changed, what the allowable set point adjustment range is, how long to hold a high demand setpoint before returning to a normally scheduled setpoint, how close to approach capacity limits, which equipment modes to utilize, the energy transfer rates (e.g., the maximum rate, an alarm rate, other rate boundary information, etc.) into and out of energy storage devices (e.g., thermal storage tanks, battery banks, etc.), and when to dispatch on-site generation of energy (e.g., via fuel cells, a motor generator set, etc.).
Integrated control layer 418 can be configured to use the data input or output of building subsystem integration layer 420 and/or demand response later 414 to make control decisions. Due to the subsystem integration provided by building subsystem integration layer 420, integrated control layer 418 can integrate control activities of the subsystems 428 such that the subsystems 428 behave as a single integrated supersystem. In an exemplary embodiment, integrated control layer 418 includes control logic that uses inputs and outputs from a plurality of building subsystems to provide greater comfort and energy savings relative to the comfort and energy savings that separate subsystems could provide alone. For example, integrated control layer 418 can be configured to use an input from a first subsystem to make an energy-saving control decision for a second subsystem. Results of these decisions can be communicated back to building subsystem integration layer 420.
Integrated control layer 418 is shown to be logically below demand response layer 414. Integrated control layer 418 can be configured to enhance the effectiveness of demand response layer 414 by enabling building subsystems 428 and their respective control loops to be controlled in coordination with demand response layer 414. This configuration can reduce disruptive demand response behavior relative to conventional systems. For example, integrated control layer 418 can be configured to assure that a demand response-driven upward adjustment to the setpoint for chilled water temperature (or another component that directly or indirectly affects temperature) does not result in an increase in fan energy (or other energy used to cool a space) that would result in greater total building energy use than was saved at the chiller.
Integrated control layer 418 can be configured to provide feedback to demand response layer 414 so that demand response layer 414 checks that constraints (e.g., temperature, lighting levels, etc.) are properly maintained even while demanded load shedding is in progress. The constraints can also include setpoint or sensed boundaries relating to safety, equipment operating limits and performance, comfort, fire codes, electrical codes, energy codes, and the like. Integrated control layer 418 is also logically below fault detection and diagnostics layer 416 and automated measurement and validation layer 412. Integrated control layer 418 can be configured to provide calculated inputs (e.g., aggregations) to these higher levels based on outputs from more than one building subsystem.
Automated measurement and validation (AM&V) layer 412 can be configured to verify that control strategies commanded by integrated control layer 418 or demand response layer 414 are working properly (e.g., using data aggregated by AM&V layer 412, integrated control layer 418, building subsystem integration layer 420, FDD layer 416, or otherwise). The calculations made by AM&V layer 412 can be based on building system energy models and/or equipment models for individual BAS devices or subsystems. For example, AM&V layer 412 can compare a model-predicted output with an actual output from building subsystems 428 to determine an accuracy of the model.
Fault detection and diagnostics (FDD) layer 416 can be configured to provide on-going fault detection for building subsystems 428, building subsystem devices (i.e., building equipment), and control algorithms used by demand response layer 414 and integrated control layer 418. FDD layer 416 can receive data inputs from integrated control layer 418, directly from one or more building subsystems or devices, or from another data source. FDD layer 416 can automatically diagnose and respond to detected faults. The responses to detected or diagnosed faults can include providing an alarm message to a user, a maintenance scheduling system, or a control algorithm configured to attempt to repair the fault or to work-around the fault.
FDD layer 416 can be configured to output a specific identification of the faulty component or cause of the fault (e.g., loose damper linkage) using detailed subsystem inputs available at building subsystem integration layer 420. In other exemplary embodiments, FDD layer 416 is configured to provide “fault” events to integrated control layer 418 which executes control strategies and policies in response to the received fault events. According to an exemplary embodiment, FDD layer 416 (or a policy executed by an integrated control engine or business rules engine) can shut-down systems or direct control activities around faulty devices or systems to reduce energy waste, extend equipment life, or assure proper control response.
FDD layer 416 can be configured to store or access a variety of different system data stores (or data points for live data). FDD layer 416 can use some content of the data stores to identify faults at the equipment level (e.g., specific chiller, specific AHU, specific terminal unit, etc.) and other content to identify faults at component or subsystem levels. For example, building subsystems 428 can generate temporal (i.e., time-series) data indicating the performance of BAS 400 and the various components thereof. The data generated by building subsystems 428 can include measured or calculated values that exhibit statistical characteristics and provide information about how the corresponding system or process (e.g., a temperature control process, a flow control process, etc.) is performing in terms of error from its setpoint. These processes can be examined by FDD layer 416 to expose when the system begins to degrade in performance and alarm a user to repair the fault before it becomes more severe.
Referring now to
The processing circuit 504 of the building controller of
The building controller 502 can be configured to perform the dynamic rule functions and the work order generation functions described herein. The memory 508 is shown to include a constants generator 510. The constants generator 510 can be configured to receive thresholds 512 and device specific templates 514 that the building controller 502 can store or receive (e.g., receive from an equipment specification database or from a user via a user interface). Based on the thresholds 512 and the device specific templates 514, the constants generator 510 can be configured to generate constants 516. The device specific templates 514 may be particular low level rules for various devices. For example, templates for a particular device may include various low level rules such as “Air temperature should be above A” or “Differential pressure should not exceed B.”
The thresholds 512 used by the constants generator 510 may be particular values for “A” or “B” of the templates. Both the thresholds 512 and the device specific templates 514 can be input by a user e.g., input via the user interface 538 shown in
The sub-rule generator 518 can be configured to generate sub-rules 520 based on the constants 516 it receives. The sub-rule generator 518 may include one or more constants and one or more Boolean comparisons. For example, a sub-rule may be that a particular condition is true if either a first constant or a second constant is true. For example, a sub-rule which is “AHU Operating” may be operational if Constant A OR Constant B is true. Another sub-rule could be “AHU Operating” may be operational if Constant A AND Constant B is true. Another sub-rule could be “AHU Operating” may be true if Constant A XOR Constant B is true. The Boolean comparison may be any type of Boolean operation (e.g., AND, OR, NAND, NOR, XOR, NOT, etc.).
The sub-rules 520 generated by the sub-rule generator 518 may be provided to a rule generator 522 and a diagnostics controller 530. The rule generator 522 can be configured to generate rules 524 i.e., high level rules based on one or more sub-rules 520. For example, a rule could be “AHU air pressure is above a setpoint” if two sub-rules are true, the first rule being that the AHU is operational and that a measured air pressure is above the setpoint. In this regard, the rule could be: rule is true if sub-rule A is true AND sub-rule B is true. Any Boolean operator or comparison or hierarchy of comparisons can be used between the sub-rules 520.
The fault generator 526 can be configured to receive the rules 524 from the rule generator 522 and determine faults 528 based on the rules 524 and monitored values of pieces of building equipment. The fault generator 526 can be configured to receive information pertaining to the status of the building equipment and apply the status information to the rules 524. If a rule is true, the piece of building equipment may be experiencing a fault 528 or otherwise is operating abnormally. In this regard, the fault generator 526 can generate a fault 528 if a particular piece of equipment or system within a building is experiencing a fault. Fault generator 526 can be configured to provide the indication of the fault 528 to the diagnostic controller 530. As an example, there may be a rule that indicates that a room is not getting enough cooling. The rule may indicate that an AHU is not supplying enough air. The rule may use sub-rules 520 such as is the AHU operational, whether the cooling mode on, and whether the airflow in a proper range. If all three sub-rules of the rule are true, fault generator 526 may identify that there is a fault 528. In some embodiments, fault generator 526 determines that there is a fault 528 if the sub-rules 520 have each been true for a predefined amount of time.
The diagnostic controller 530 can be configured to generate diagnostics 532 based on rules 524, constants 516, and/or faults 528 it receives. If the diagnostic controller receives a fault 528 for a piece of equipment for a particular constant 516 and/or rule 524, the diagnostic controller 530 can be configured to monitor how long the fault 528 has been persisting. The diagnostic controller 530 can be configured to generate diagnostics 532 based on the rules 524, constants 516, and/or faults 528 which indicate that a particular fault 528 has occurred in the system for a particular amount of time. The diagnostic controller 530 can be configured to generate a diagnostic list 1000 which indicates diagnostics 532 and the amount of time that the diagnostic has been active. The diagnostic list 1000 may be organized in order of the longest active fault associated with the diagnostic. This can be seen in
The diagnostic controller 530 can be configured to receive fault reasons. The fault reasons may be a list of potential reasons for a particular fault occurring. In this regard, the diagnostics 532 that the diagnostic controller 530 generates may include an indication of the reasons that could have led to a particular fault. Therefore, a user can view the fault reasons for a particular diagnostic in order to resolve the fault. The diagnostic list 1000 may include one or more diagnostics 532 that a user can interact with to view the various fault reasons.
The diagnostic controller 530 may include a plurality of diagnostic rules or equations. The diagnostic controller 530 can be configured to use the diagnostic equations, faults 528 determined by fault generator 526, sub-rules 520 generated by sub-rule generator 518, and/or constants 516 generated by constants generator 510 to generate the diagnostics 532. The various diagnostics equations may be based on various sub-rules 520 and/or constants 516 that it receives from the constants generator 510 and/or the sub-rule generator 518. The diagnostics equations may indicate particular reasons for a fault and/or potential solutions to the fault. Various reason for the fault may be stored in the memory 508 and/or retrieved by the diagnostic controller 530 i.e., from the fault reasons block of the memory 508.
As an example, a diagnostic equation or equations may indicate a reason why the cooled water provided by a cooling tower is not cold enough. The cooling tower may not be giving full output even though it is operating at 100%. The diagnostic equations may be based on three sub-rules 520, is the cooling tower operational, is the airflow of the cooling tower correct, and is a variable frequency drive (VFD) operating properly. The diagnostic equations may use the three sub-rules 520 to identify the possible cause of the cooled water not being cold enough. The diagnostic equations may specifically use equipment values that it receives during a time when the fault was active to identify the cause of the fault. The diagnostic equation may look at the lengths of time that the sub-rules were true to determine the a diagnosis for the fault.
As another example, if a rule 524 indicates that there is a fault 528 with a with a chiller, a diagnostic equation or equations may indicate what the cause of the fault 528 is. The diagnostic equation may look at how long a cooling coil of the chiller has been closed and whether there is an indication of a chiller supply output being too high (these indications may be based on sub-rules or constants). If a cooling coil valve was closed for a predefined amount of time and the chiller supply was too high for a predefined amount of time, the diagnostic rule may indicate that the cooling coil valve is responsible for the chiller not properly functioning and for air in a room not being cold enough. In some embodiments, the diagnostic equation can be configured to generate a list of faults in order of length of time that the faults were active. For example, if the diagnostic equation indicates that the cooling coil was closed for 20 hours and that the chiller supply was too high for 1 hour, the diagnostic may list “cooling coil closed” above “chiller supply to high” to give a technician an idea of what may be the root cause of a fault and what they should analyze first.
The work order generator 534 can be configured to generate work orders 540 based on the diagnostics 532 and/or directly or indirectly based on the constants 516, sub-rules 520, and/or rules 524. In this regard, the work order generator 534 can be configured to generate a work order 540 and provide the work order 540 to a user via the user interface 538. The work order 540 may include a particular fault 528 and the various reasons that may have caused the fault 528 i.e., the work order 540 may be based on the diagnostics 532 generated by the diagnostic controller 530. Further, the work order 540 may include various steps for resolving the problem e.g., the work order 540 may be based on the fault reasons included in the diagnostics 532. The task description which the work order generator 534 includes in the work order it generates may be based on the most probable diagnostic generated by diagnostic controller 530 e.g., the diagnostic 532 associated with a fault 528 that has been active for the longest amount of time.
The work order generator 534 can be configured to assign the work order 540 to a particular technician and/or technician group. For example, based on the fault 528 that the work order 540 is generated for, the work order generator 534 can be configured to assign the work order 540 to a technician group that specializes in fixing that particular fault. Further, the work order generator 534 can be configured to assign work orders 540 based on number of work orders 540 per technician or technician group i.e., the work order generator 534, can be configured to load balance the work loads of various technicians.
The work order generator 534 can be configured to automatically open and/or close work orders 540. For example, if the work order generator 534 determines that a work order 540 should be opened based on a fault or faults 528 occurring, the work order generator 534 can be configured to generate a work order 540. Further in response to the work order generator 534 determining that the fault 528 has been fixed, work order generator 534 can further be configured to close the work order 540. Also, a technician can indicate via the user interface 538 that the work order 540 is complete and in response the work order generator 534 can be configured to close the work order 540.
The work orders 540 generated by work order generator 534 may indicate equipment information to a technician. The work order 540 may indicate energy usage, performance trends, and/or any other information. Equipment may be malfunctioning when the energy usage becomes too high or too low. The work order 540 may identify the equipment that is experiencing the issue, the time that the issue was first detected, the associated spaces that the equipment serves, the location of the equipment, and what diagnostics may have already been attempted if the issue is a reoccurring issue.
The user interface 538 shown in
Referring now to
In step 602, the constants generator 510 can generate one or more constants 516 based on device specific templates 610 and/or thresholds for the templates 612. The constants 516 that the constants generator 510 generates may be low level rules i.e., equation based relationships between templates 610 and thresholds 612. For example, a constant 516 could be that a pressure differential for a particular piece of HVAC equipment is within a particular range (e.g., defined by the threshold). The thresholds 612 used in the constants 516 may be based on design conditions (e.g., the actual design of the piece of HVAC equipment) and/or may be based on site specific information (e.g., the configuration of the HVAC equipment in a particular building).
In step 604, the sub-rule generator 518 can be configured to generate sub-rules 520 based on the one or more constants. For example, a sub-rule 520 may be that a particular outcome is true if one or both of the constants are true. For example, a sub-rule 520 for an AHU may be that the AHU is operational is either a supply air fan status is greater than zero (e.g., a first constant) or that a supply air fan output is greater than zero (a second constant).
In step 605, the rule generator 522 can generate one or more rules 524 based on one or more sub-rules 520. The rules 524 may indicate that a particular fault 528 has or has not occurred in a particular piece of HVAC equipment. For example, a rule 524 may indicate that measured air pressure is higher than a setpoint for an AHU based on two sub-rules 520. The sub-rules 520 may be AHU operational and supply air pressure greater than a setpoint. The rule 524 may be based on a Boolean “and” comparison of the two sub rules 520 and/or any other Boolean comparison i.e., determining if both sub-rules 520 are true.
In step 606, the fault generator 526 can determine whether any faults 528 have occurred based on the rules 524 generated by the rule generator 522. If any of the rules 524 are true and/or have been true for a predefined number of times and/or for predefined lengths of time, fault generator 526 can determine that a fault 528 for a particular piece of building equipment has occurred. In some embodiments, a work order 540 is automatically generated for a piece of equipment after a piece equipment has run for a predefined amount of time since the equipment may require maintenance after the predefined amount of time.
In step 608, the diagnostic controller 530 can generate diagnostics 532 based on any determined faults 528, sub-rules 520, and/or constants 516. Further, the diagnostic controller 530 can include various reasons for a fault 528 in the diagnostics 532. If a particular fault 528 is determined, the diagnostic controller 530 can analyze what sub-rules 520 and/or constants 516 are responsible for the fault 528 being triggered. Based on various fault reasons 614 that the diagnostic controller 530 can receive and/or store, the diagnostic controller 530 can be configured to identify particular reasons for the fault 528 occurring. The diagnostic controller 530 may by equation driven and use various diagnostic equations that take into account the constants 516 and/or sub-rules 520 to identify the most likely reason for the fault 528 occurring.
As an example, an AHU and a VAV may supply air to a particular room. A fault 528 may be triggered that identifies that the room is not getting enough cooling. This may be triggered based on a rule 524 for the room. Based on the various constants 516 and sub-rules 520 that make up the rule 524, the diagnostic controller 530 can be configured to identify whether the AHU or the VAV is responsible for the fault 528 with the constants 516, sub-rules 520, and/or diagnostics 532. Further, the diagnostic controller 530 can be configured to determine what is particularly at fault with the identified source of the fault 528. For example, based on the constants 516 and/or sub-rules 520, if the diagnostic controller 530 determines that the VAV is responsible for the fault, the diagnostic controller 530 can further determine that the valve of the VAV is stuck and/or not positioned correctly.
Referring now to
Referring now to
Referring now to
Referring now to both
Referring now to
The diagnostic controller 530 is shown to order the diagnostics 532 in order time that the diagnostic 532 has been active i.e., the time that the rule 524 has been triggered. As can be seen in
Referring now to
In response to receiving the work order request and/or based on the diagnostics, in step 1104, the diagnostic controller 530 can generate a work order 540. The work order 540 may indicate task details that can be populated based on information (e.g., “Fix cooling coil valve” or step by step direction to fix fault by analyzing pieces of equipment piece by piece) included in the diagnostics 532 generated in step 1102. In some embodiments, the work order 540 includes the diagnostic or task information related to the diagnostic 532 that has been active for the longest amount of time, i.e., a fault 528 causing the diagnostic 532 has been active longer than other faults related to other diagnostics 532. The work order 540 may be generated in step 1104 if the fault 528 causing the diagnostic 532 has been active for a predefined amount of time, has occurred a predetermined number of times, has be active for a predefined amount of time within a longer predefined amount of time, or has occurred a predefined amount of time within a predefined amount of time. In step 1106, the generated work order 540 may be sent to a technician and/or technician group. The work order generator 534 can assign the work order 540 based on a location of the technician or technician group and the piece of equipment experiencing a fault 528, based on the specialties of the technician or technician group, and/or based on the work load of the technician or technician group.
Referring now to
Referring now to
The construction and arrangement of the systems and methods as shown in the various exemplary embodiments are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.). For example, the position of elements may be reversed or otherwise varied and the nature or number of discrete elements or positions may be altered or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps may be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions may be made in the design, operating conditions and arrangement of the exemplary embodiments without departing from the scope of the present disclosure.
The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. When information is transferred or provided over a network or another communications connection (either hardwired, wireless, or a combination of hardwired or wireless) to a machine, the machine properly views the connection as a machine-readable medium. Thus, any such connection is properly termed a machine-readable medium. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.
Although the figures show a specific order of method steps, the order of the steps may differ from what is depicted. Also two or more steps may be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps.
| Number | Date | Country | Kind |
|---|---|---|---|
| 201741025951 | Jul 2017 | IN | national |
