US20210080139A1 - User experience system for improving compliance of temperature, pressure, and humidity - Google Patents

Abstract

A building management system (BMS) for heating, ventilation, or air conditioning (HVAC) parameters in a building. The BMS includes one or more processing circuits including one or more memory devices coupled to one or more processors. The one or more processors query a training data storage and receive training data, institute a policy with a machine learning engine and train the policy using the training data, receive temperature, pressure, and humidity (TPH) sensor data from one or more sensors, determine a fault based on the TPH sensor data, provide the TPH sensor data and the fault to the policy of the machine learning engine and output a corrective action to resolve the fault, and generate a work order for a user based on the TPH sensor data, the determined fault and the corrective action.

Description

CROSS-REFERENCE TO RELATED APPLICATIONS
• The present application claims benefit of and priority to U.S. Provisional Patent Application No. 62/902,338 filed Sep. 18, 2019, the entire disclosure of which is incorporated by reference herein.
BACKGROUND
• The present disclosure relates to control systems in a building. More particularly, the present disclosure relates to improving compliance of temperature, pressure, and humidity in building management systems.
SUMMARY
• This summary is illustrative only and is not intended to be in any way limiting. Other aspects, inventive features, and advantages of the devices or processes described herein will become apparent in the detailed description set forth herein, taken in conjunction with the accompanying figures, wherein like reference numerals refer to like elements.
• One implementation of the present disclosure is a building management system (BMS) for heating, ventilation, or air conditioning (HVAC) parameters in a building. The BMS includes one or more processing circuits including one or more memory devices coupled to one or more processors. The one or more memory devices store instructions thereon that, when executed by the one or more processors, cause the one or more processors to query a training data storage and receive training data, institute a policy with a machine learning engine and train the policy using the training data, receive temperature, pressure, and humidity (TPH) sensor data from one or more sensors, determine a fault based on the TPH sensor data, provide the TPH sensor data and the fault to the policy of the machine learning engine and output a corrective action to resolve the fault, generate a work order for a user based on the TPH sensor data, the determined fault, and the corrective action, and provide the work order to a user interface.
• In some embodiments, the one or more memory devices store instructions thereon that, when executed by the one or more processors, cause the one or more processors to adjust HVAC building equipment based on the provided work order.
• In some embodiments, the user interface includes a first user profile and a second user profile. In some embodiments, the one or more memory devices store instructions thereon that, when executed by the one or more processors, cause the one or more processors to generate a first dashboard associated with the first user profile and a second dashboard associated with the second user profile, provide a first subset of information from the work order to the first dashboard, and provide a second subset of information from the work order to the second dashboard.
• In some embodiments, the one or more memory devices store instructions thereon that, when executed by the one or more processors, cause the one or more processors to update the second dashboard based on an action entered on the first dashboard.
• In some embodiments, the work order is stored within the one or more memory devices. In some embodiments, the one or more memory devices store instructions thereon that, when executed by the one or more processors, cause the one or more processors to update the work order from either the first dashboard or the second dashboard.
• In some embodiments, the one or more memory devices store instructions thereon that, when executed by the one or more processors, cause the one or more processors to assign the work order to the second dashboard from the first dashboard.
• In some embodiments, the BMS system further includes an application structured to access one of the first user profile or the second user profile and display the associated dashboard on a human machine interface, the associated dashboard displaying at least one of the TPH sensor data or the work order.
• In some embodiments, the human machine interface includes a mobile device, a wall mounted panel, a monitor, a tablet, a kiosk, an augmented reality device, a virtual reality device, or a wearable device.
• In some embodiments, the one or more memory devices store instructions thereon that, when executed by the one or more processors, cause the one or more processors to retrieve a fault causation template, map a plurality of operational parameters relating to an associated HVAC device to the fault causation template, map the corrective action to the fault causation template, and provide a populated fault causation template to the user interface.
• In some embodiments, the one or more memory devices store instructions thereon that, when executed by the one or more processors, cause the one or more processors to receive a notification that the work order has been completed, the notification including the determined fault and a fault solution, wherein the fault solution is either the corrective action or a different action, and train the policy with the machine learning engine by providing the determined fault and the fault solution to the machine learning engine.
• In some embodiments, the machine learning engine includes at least one of a neural network, a reinforcement learning scheme, a model-based control scheme, a linear regression algorithm, a decision tree, a logistic regression algorithm, and a Naïve Bayes algorithm.
• Another implementation of the present disclosure is a building management system (BMS) for heating, ventilation, or air conditioning (HVAC) parameters in a building. The BMS includes one or more processing circuits including one or more memory devices coupled to one or more processors. The one or more memory devices store instructions thereon that, when executed by the one or more processors, cause the one or more processors to receive temperature, pressure, and humidity (TPH) sensor data from one or more sensors, generate a work order using a machine learning engine that receives the TPH sensor data and fault information and outputs a recommended action, receive first credentials for a first user and grant access to a first user profile including a first dashboard including first information based at least in part on the TPH sensor data and the work order, receive second credentials for a second user and grant access to a second user profile including a second dashboard including second information based at least in part on the TPH sensor data and the work order, and provide communication between the first dashboard and the second dashboard.
• In some embodiments, the first dashboard displays one or more customizable features to satisfy a first set of preferences of the first user and selectively displays the first information according to a type of the first user profile, the type of the first user profile indicating a first amount of detail regarding the TPH sensor data and the work order that can be provided to the first dashboard. In some embodiments, the second dashboard displays the customizable features to satisfy a second set of preferences of the second user and selectively displays the second information according to a type of the second user profile, the type of the second user profile indicating a second amount of detail regarding the TPH sensor data and the work order that can be provided to the second dashboard.
• In some embodiments, the one or more memory devices store instructions thereon that, when executed by the one or more processors, cause the one or more processors to adjust HVAC building equipment based on the work order.
• In some embodiments, providing communication between the first dashboard and the second dashboard includes at least one of updating the second dashboard based on an action entered on the first dashboard, updating the work order from either the first dashboard or the second dashboard, and assigning the work order to the second dashboard from the first dashboard.
• In another embodiment, a building management system (BMS) for heating, ventilation, or air conditioning (HVAC) parameters in a building includes one or more processing circuits comprising one or more memory devices coupled to one or more processors, the one or more memory devices configured to store instructions thereon. When executed by the one or more processors, the instructions cause the one or more processors to: receive temperature, pressure, and humidity (TPH) sensor data from one or more sensors, receive a scheduling request for a building room via an application dashboard, the scheduling request including a reservation time, a reservation date, and requested TPH setpoints, receive a work order including a fault code affecting the availability of the building room, determine if the building room is unavailable based on the work order, determine a required time to achieve the requested TPH setpoints based on the scheduling request and the work order, provide the required time and a scheduling confirmation to the application dashboard, and adjust HVAC equipment in the building to achieve the TPH setpoints prior to the reservation date and time.
• In some embodiments, determining a required time to adjust the requested TPH setpoints includes determining a set of preconditioning parameters to be implemented in the building room prior to the reservation date and time and determining the required time based on at least one of a time for preconditioning parameters to be performed and a time for TPH levels to adjust to the TPH setpoints.
• In some embodiments, the preconditioning parameters include at least one of an ultra-violet (UV) soak system, a fumigation system, a sanitization system, an air removal system, and an air filtration system.
• In some embodiments, the application dashboard includes a scheduling interface configured to receive the required time and the scheduling confirmation, adjust the required time to achieve the requested TPH setpoints, update at least one of the reservation time, the reservation date, and the request for the building room, and adjust the preconditioning parameters implemented.
• In some embodiments, the one or more memory devices store instructions thereon that, when executed by the one or more processors, cause the one or more processors to determine that the required time to achieve the requested TPH setpoints prior to the reservation date and time creates a scheduling conflict within the BMS, update the application dashboard based on the scheduling conflict, and provide the application dashboard with at least one of a new reservation time and a new reservation date such that the HVAC equipment can be adjusted prior to the reservation date and time.
• In some embodiments, the user is one of a chief compliance officer, a facilities manager, an operating room administrator, a health care professional or a facilities technician.
• In some embodiments, the one or more memory devices store instructions thereon that, when executed by the one or more processors, cause the one or more processors to receive an indication that the work order has been completed and updating the user interface to indicate that the work order has been completed.
• In some embodiments, generating the work order includes generating a set of data including the fault and at least one of the corrective action, a time of the fault, and a location of the fault.
• In some embodiments, the one or more memory devices store instructions thereon that, when executed by the one or more processors, cause the one or more processors to provide assistance functionality to the user interface, receive a request for assistance from the user interface via the assistance functionality, and provide additional information related to the corrective action to the user interface.
• In some embodiments, the one or more memory devices store instructions thereon that, when executed by the one or more processors, cause the one or more processors to provide an alert in the building in response to determining the fault, wherein the alert includes at least one of a visual alert, an audible alert, a fault indication, and corrective action indication.
• In some embodiments, the first dashboard or the second dashboard or both are configured to operate within a heads up display (HUD), and provide a list of inventory parts currently available for addressing the work order.
• In some embodiments, the first dashboard or the second dashboard or both are configured to display regulations and codes related to TPH compliance, display information related to an interrelation of TPH of one or more building zones in the building, and display the TPH sensor data and the work order at least in part with color-coded formatting to indicate an intensity of the work order.
• In some embodiments, the first dashboard or the second dashboard or both includes at least one of an audio interface, a visual interface, a touch screen interface, and a holographic interface, and a visual indicator proximate to the first dashboard or the second dashboard or both configured to indicate a compliance level of the TPH sensor data.
BRIEF DESCRIPTION OF THE DRAWINGS
• FIG. 1 is a drawing of a building with a heating, ventilation, or air conditioning (HVAC) system, according to some embodiments.
• FIG. 2 is a schematic of a waterside system which can be used as part of the HVAC system ofFIG. 1, according to some embodiments,
• FIG. 3 is a diagram of an airside system, which can be used as part of the HVAC system ofFIG. 1, according to some embodiments.
• FIG. 4 is a block diagram of a building management system (BMS) which can be used in the building ofFIG. 1, according to some embodiments.
• FIG. 5A is a diagram of a BMS for optimizing building conditions based on user input, which can be used in the building ofFIG. 1, according to some embodiments.
• FIG. 5B is a diagram of a BMS for providing work orders to an application which can be performed by the controller ofFIG. 5A, according to some embodiments.
• FIG. 5C is a diagram of a BMS with alert functionality which can be performed by the controller ofFIG. 5A, according to some embodiments.
• FIG. 5D is a diagram of a BMS with scheduling system integration which can be performed by the controller ofFIG. 5A, according to some embodiments.
• FIG. 6A is a diagram of an application on a user interface, which can be generated by the server ofFIG. 5A, according to some embodiments.
• FIG. 6B is a diagram of an application on a user interface, which can be generated by the server ofFIG. 5A, according to some embodiments.
• FIG. 7 is a flow diagram of a process for optimizing building conditions based on user input, which can be performed by the BMS controller ofFIG. 5A, according to some embodiments.
• FIG. 8 is a flow diagram of a process for predicting solutions to issues in an HVAC system, which can be performed by the BMS controller ofFIG. 5A, according to some embodiments.
• FIG. 9 is a flow diagram of a process optimizing control decisions for HVAC control in a building based on machine learning, which can be performed by the BMS controller ofFIG. 5A, according to some embodiments.
• FIG. 10 is a flow diagram of a process for determining fault causes in a BMS, which can be performed by the BMS controller ofFIG. 5A, according to some embodiments.
• FIG. 11 is a flow diagram of a process for operating an HVAC system based on scheduling requests, which can be performed by the BMS controller ofFIG. 5A, according to some embodiments.
DETAILED DESCRIPTIONOverview
• Before turning to the FIGURES, which illustrate certain exemplary embodiments in detail, it should be understood that the present disclosure is not limited to the details or methodology set forth in the description or illustrated in the FIGURES. It should also be understood that the terminology used herein is for the purpose of description only and should not be regarded as limiting.
• Referring generally to the FIGURES, systems and methods are disclosed that improve comfortability for building occupants while maintaining appropriate levels of temperature, pressure, and humidity. In some embodiments, hospitals and/or clinics may need to conform to certain design criteria (e.g., American Society of Heating, Refrigerating and Air-Conditioning Engineers (ASHRAE) standard 170-2017, etc.) with regards to their HVAC systems to minimize infection, maintain staff comfort and contribute to an environment of patient care. These design criteria may require one or more building zones of the hospital or clinic to maintain temperature, pressure, and humidity (TPH) within a certain range or ranges. There exists a need to maintain TPH within these ranges while simultaneous providing comfortability to the building occupants, energy efficiency, and optimization in the HVAC system.
ASHRAE Standards Overview
• Rooms in hospitals may require special design considerations due to intensified infection concerns (e.g., the spread of a contagious disease, etc.), high air change rates, special equipment, unique procedures, high internal loads and the presence of immunocompromised patients. However, these special considerations may be particularly important for hospital operating rooms (ORs), where their purpose is to minimize infection, maintain staff comfort and contribute to an environment of patient care.
• In some embodiments, ANSI/ASHRAE/ASHE Standard 170, Ventilation of Health Care Facilities, is considered a critical standard of heating, ventilation, and air conditioning (HVAC) health-care ventilation design. The intent of the standard may be to provide comprehensive guidance, including a set of minimum requirements that define ventilation system design that helps provide environmental control for comfort, asepsis, and odor in health-care facilities. In some embodiments, it is adopted by code-enforcing agencies.
• The standard may define minimum design requirements only, and due to the wide diversity of patient population and variations in their vulnerability and sensitivity, these standards may not guarantee an OR environment that will sufficiently provide comfort and control of airborne contagions and other elements of concern. When selecting the temperature and relative humidity combination to be incorporated into the design, these standard minimums and the desires of the surgical staff may need to be taken into consideration. In some embodiments, the ASHRAEHVAC Design Manual for Hospitals and Clinicsdiscloses the inability to maintain low OR temperature as the primary complaint by surgeons to facility engineers.
Building Management System and HVAC SystemBuilding Site
• Referring now toFIG. 1, a perspective view of abuilding10 is shown.Building10 is served by a building management system (BMS). A 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.
• The BMS that serves building10 includes aHVAC system100.HVAC system100 may 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 building10. For example,HVAC system100 includes awaterside system120 and anairside system130.Waterside system120 may provide a heated or chilled fluid to an air handling unit ofairside system130.Airside system130 may use the heated or chilled fluid to heat or cool an airflow provided to building10. In some embodiments,waterside system120 is replaced with a central energy plant such ascentral plant200, described with reference toFIG. 2.
• Still referring toFIG. 1,HVAC system100 includes achiller102, aboiler104, and a rooftop air handling unit (AHU)106.Waterside system120 may useboiler104 andchiller102 to heat or cool a working fluid (e.g., water, glycol, etc.) and may circulate the working fluid toAHU106. In embodiments, the HVAC devices ofwaterside system120 may be located in or around building10 (as shown inFIG. 1) or at an offsite location such as a central plant (e.g., a chiller plant, a steam plant, a heat plant, etc.). The working fluid may be heated inboiler104 or cooled inchiller102, depending on whether heating or cooling is required in building10.Boiler104 may add heat to the circulated fluid, for example, by burning a combustible material (e.g., natural gas) or using an electric heating element.Chiller102 may place the circulated fluid in a heat exchange relationship with another fluid (e.g., a refrigerant) in a heat exchanger (e.g., an evaporator) to absorb heat from the circulated fluid. The working fluid fromchiller102 and/orboiler104 may be transported toAHU106 viapiping108.
• AHU106 may place the working fluid in a heat exchange relationship with an airflow passing through AHU106 (e.g., via one or more stages of cooling coils and/or heating coils). The airflow may be, for example, outside air, return air from within building10, or a combination of both.AHU106 may transfer heat between the airflow and the working fluid to provide heating or cooling for the airflow. For example,AHU106 may 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 may then return tochiller102 orboiler104 viapiping110.
• Airside system130 may deliver the airflow supplied by AHU106 (i.e., the supply airflow) to building10 viaair supply ducts112 and may provide return air from building10 toAHU106 viaair return ducts114. In some embodiments,airside system130 includes multiple variable air volume (VAV)units116. For example,airside system130 includes aseparate VAV unit116 on each floor or zone of building10.VAV units116 may include dampers or other flow control elements that can be operated to control an amount of the supply airflow provided to individual zones of building10. In other embodiments,airside system130 delivers the supply airflow into one or more zones of building10 (e.g., via air supply ducts112) without usingintermediate VAV units116 or other flow control elements.AHU106 may include sensors (e.g., temperature sensors, pressure sensors, etc.) configured to measure attributes of the supply airflow.AHU106 may receive input from sensors located withinAHU106 and/or within the building zone and may adjust the flow rate, temperature, or other attributes of the supply airflow throughAHU106 to achieve setpoint conditions for the building zone.
Waterside System
• Referring now toFIG. 2, a block diagram of acentral plant200 is shown, according to an exemplary embodiment. In brief overview,central plant200 may include types of equipment configured to serve the thermal energy loads of a building or campus (i.e., a system of buildings). For example,central plant200 may include heaters, chillers, heat recovery chillers, cooling towers, or other types of equipment configured to serve the heating and/or cooling loads of a building or campus.Central plant200 may consume resources from a utility (e.g., electricity, water, natural gas, etc.) to heat or cool a working fluid that is circulated to one or more buildings or stored for later use (e.g., in thermal energy storage tanks) to provide heating or cooling for the buildings. In embodiments,central plant200 may supplement or replacewaterside system120 in building10 or may be implemented separate from building10 (e.g., at an offsite location).
• Central plant200 includes a plurality of subplants202-212 including aheater subplant202, a heatrecovery chiller subplant204, achiller subplant206, acooling tower subplant208, a hot thermal energy storage (TES) subplant210, and a cold thermal energy storage (TES)subplant212. Subplants202-212 consume resources from utilities to serve the thermal energy loads (e.g., hot water, cold water, heating, cooling, etc.) of a building or campus. For example,heater subplant202 may be configured to heat water in ahot water loop214 that circulates the hot water betweenheater subplant202 andbuilding10.Chiller subplant206 may be configured to chill water in acold water loop216 that circulates the cold water between chiller subplant206 andbuilding10. Heatrecovery chiller subplant204 may be configured to transfer heat fromcold water loop216 tohot water loop214 to provide additional heating for the hot water and additional cooling for the cold water.Condenser water loop218 may absorb heat from the cold water inchiller subplant206 and reject the absorbed heat incooling tower subplant208 or transfer the absorbed heat tohot water loop214. Hot TES subplant210 andcold TES subplant212 may store hot and cold thermal energy, respectively, for subsequent use.
• Hot water loop214 andcold water loop216 may deliver the heated and/or chilled water to air handlers located on the rooftop of building10 (e.g., AHU106) or to individual floors or zones of building10 (e.g., VAV units116). 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 may be delivered to individual zones of building10 to serve the thermal energy loads of building10. The water then returns to subplants202-212 to receive further heating or cooling.
• Although subplants202-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, CO₂, etc.) may be used in place of or in addition to water to serve the thermal energy loads. In other embodiments, subplants202-212 may provide heating and/or cooling directly to the building or campus without requiring an intermediate heat transfer fluid. These and other variations tocentral plant200 are within the teachings of the present invention.
• Each of subplants202-212 may include a variety of equipment configured to facilitate the functions of the subplant. For example,heater subplant202 includes a plurality of heating elements220 (e.g., boilers, electric heaters, etc.) configured to add heat to the hot water inhot water loop214.Heater subplant202 is also shown to includeseveral pumps222 and224 configured to circulate the hot water inhot water loop214 and to control the flow rate of the hot water throughindividual heating elements220.Chiller subplant206 includes a plurality ofchillers232 configured to remove heat from the cold water incold water loop216.Chiller subplant206 is also shown to includeseveral pumps234 and236 configured to circulate the cold water incold water loop216 and to control the flow rate of the cold water throughindividual chillers232.
• Heatrecovery chiller subplant204 includes a plurality of heat recovery heat exchangers226 (e.g., refrigeration circuits) configured to transfer heat fromcold water loop216 tohot water loop214. Heatrecovery chiller subplant204 is also shown to includeseveral pumps228 and230 configured to circulate the hot water and/or cold water through heatrecovery heat exchangers226 and to control the flow rate of the water through individual heatrecovery heat exchangers226.Cooling tower subplant208 includes a plurality of coolingtowers238 configured to remove heat from the condenser water incondenser water loop218.Cooling tower subplant208 is also shown to includeseveral pumps240 configured to circulate the condenser water incondenser water loop218 and to control the flow rate of the condenser water through individual cooling towers238.
• Hot TES subplant210 includes ahot TES tank242 configured to store the hot water for later use. Hot TES subplant210 may also include one or more pumps or valves configured to control the flow rate of the hot water into or out ofhot TES tank242. Cold TES subplant212 includescold TES tanks244 configured to store the cold water for later use. Cold TES subplant212 may also include one or more pumps or valves configured to control the flow rate of the cold water into or out ofcold TES tanks244.
• In some embodiments, one or more of the pumps in central plant200 (e.g., pumps222,224,228,230,234,236, and/or240) or pipelines incentral plant200 include an isolation valve associated therewith. Isolation valves may be integrated with the pumps or positioned upstream or downstream of the pumps to control the fluid flows incentral plant200. In embodiments,central plant200 may include more, fewer, or different types of devices and/or subplants based on the particular configuration ofcentral plant200 and the types of loads served bycentral plant200.
Airside System
• Referring now toFIG. 3, a block diagram of anairside system300 is shown, according to an example embodiment. In embodiments,airside system300 can supplement or replaceairside system130 inHVAC system100 or can be implemented separate fromHVAC system100. When implemented inHVAC system100,airside system300 can include a subset of the HVAC devices in HVAC system100 (e.g.,AHU106,VAV units116,duct112,duct114, fans, dampers, etc.) and can be located in or around building10.Airside system300 can operate to heat or cool an airflow provided to building10 using a heated or chilled fluid provided bywaterside system200.
• InFIG. 3,airside system300 includes an economizer-type air handling unit (AHU)302. Economizer-type AHUs vary the amount of outside air and return air used by the air handling unit for heating or cooling. For example,AHU302 can receivereturn air304 from buildingzone306 viareturn air duct308 and can deliversupply air310 to buildingzone306 viasupply air duct312. In some embodiments,AHU302 is a rooftop unit located on the roof of building10 (e.g.,AHU106 as shown inFIG. 1) or otherwise positioned to receive both returnair304 and outsideair314.AHU302 can be configured to operateexhaust air damper316, mixingdamper318, and outsideair damper320 to control an amount ofoutside air314 and returnair304 that combine to formsupply air310. Anyreturn air304 that does not pass through mixingdamper318 can be exhausted fromAHU302 throughexhaust damper316 asexhaust air322.
• Each of dampers316-320 can be operated by an actuator. For example,exhaust air damper316 can be operated byactuator324, mixingdamper318 can be operated byactuator326, and outsideair damper320 can be operated byactuator328. Actuators324-328 can communicate with anAHU controller330 via acommunications link332. Actuators324-328 can receive control signals fromAHU controller330 and can provide feedback signals toAHU controller330. 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 actuators324-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 actuators324-328.AHU controller330 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 actuators324-328.
• Still referring toFIG. 3,AHU302 includes acooling coil334, aheating coil336, and afan338 positioned withinsupply air duct312.Fan338 can be configured to forcesupply air310 throughcooling coil334 and/orheating coil336 and providesupply air310 to buildingzone306.AHU controller330 can communicate withfan338 via communications link340 to control a flow rate ofsupply air310. In some embodiments,AHU controller330 controls an amount of heating or cooling applied to supplyair310 by modulating a speed offan338.
• Cooling coil334 can receive a chilled fluid from waterside system200 (e.g., from cold water loop216) viapiping342 and can return the chilled fluid towaterside system200 viapiping344.Valve346 can be positioned along piping342 or piping344 to control a flow rate of the chilled fluid throughcooling coil334. In some embodiments, coolingcoil334 includes multiple stages of cooling coils that can be independently activated and deactivated (e.g., byAHU controller330, byBMS controller366, etc.) to modulate an amount of cooling applied to supplyair310.
• Heating coil336 can receive a heated fluid from waterside system200 (e.g., from hot water loop214) viapiping348 and can return the heated fluid towaterside system200 viapiping350.Valve352 can be positioned along piping348 or piping350 to control a flow rate of the heated fluid throughheating coil336. In some embodiments,heating coil336 includes multiple stages of heating coils that can be independently activated and deactivated (e.g., byAHU controller330, byBMS controller366, etc.) to modulate an amount of heating applied to supplyair310.
• Each ofvalves346 and352 can be controlled by an actuator. For example,valve346 can be controlled byactuator354 andvalve352 can be controlled by actuator356. Actuators354-356 can communicate withAHU controller330 via communications links358-360. Actuators354-356 can receive control signals fromAHU controller330 and can provide feedback signals tocontroller330. In some embodiments,AHU controller330 receives a measurement of the supply air temperature from atemperature sensor362 positioned in supply air duct312 (e.g., downstream of coolingcoil334 and/or heating coil336).AHU controller330 can also receive a measurement of the temperature ofbuilding zone306 from atemperature sensor364 located in buildingzone306.
• In some embodiments,AHU controller330 operatesvalves346 and352 via actuators354-356 to modulate an amount of heating or cooling provided to supply air310 (e.g., to achieve a setpoint temperature forsupply air310 or to maintain the temperature ofsupply air310 within a setpoint temperature range). The positions ofvalves346 and352 affect the amount of heating or cooling provided to supplyair310 by coolingcoil334 orheating coil336 and may correlate with the amount of energy consumed to achieve a desired supply air temperature.AHU controller330 can control the temperature ofsupply air310 and/orbuilding zone306 by activating or deactivating coils334-336, adjusting a speed offan338, or a combination of both.
• Still referring toFIG. 3,airside system300 includes a building management system (BMS)controller366 and aclient device368.BMS controller366 can include one or more computer systems (e.g., servers, supervisory controllers, subsystem controllers, etc.) that serve as system level controllers, application or data servers, head nodes, or master controllers forairside system300,waterside system200,HVAC system100, and/or other controllable systems that servebuilding10.BMS controller366 can communicate with multiple downstream building systems or subsystems (e.g.,HVAC system100, a security system, a lighting system,waterside system200, etc.) via acommunications link370 according to like or disparate protocols (e.g., LON, BACnet, etc.). In embodiments,AHU controller330 andBMS controller366 can be separate (as shown inFIG. 3) or integrated. In an integrated implementation,AHU controller330 can be a software module configured for execution by a processor ofBMS controller366.
• In some embodiments,AHU controller330 receives information from BMS controller366 (e.g., commands, set points, operating boundaries, etc.) and provides information to BMS controller366 (e.g., temperature measurements, valve or actuator positions, operating statuses, diagnostics, etc.). For example,AHU controller330 can provideBMS controller366 with temperature measurements fromtemperature sensors362 and364, equipment on/off states, equipment operating capacities, and/or any other information that can be used byBMS controller366 to monitor or control a variable state or condition withinbuilding zone306.
• Client device368 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 withHVAC system100, its subsystems, and/or devices.Client device368 can be a computer workstation, a client terminal, a remote or local interface, or any other type of user interface device.Client device368 can be a stationary terminal or a mobile device. For example,client device368 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 device368 can communicate withBMS controller366 and/orAHU controller330 via communications link372.
Building Management System
• Referring now toFIG. 4, a block diagram of a building management system (BMS)400 is shown, according to an example embodiment.BMS400 can be implemented in building10 to automatically monitor and control building functions.BMS400 includesBMS controller366 and a plurality ofbuilding subsystems428. Buildingsubsystems428 are shown to include a buildingelectrical subsystem434, an information communication technology (ICT)subsystem436, asecurity subsystem438, aHVAC subsystem440, alighting subsystem442, a lift/escalators subsystem432, and afire safety subsystem430. In embodiments,building subsystems428 can include fewer, additional, or alternative subsystems. For example,building subsystems428 can also or alternatively include a refrigeration subsystem, an advertising or signage subsystem, a cooking subsystem, a vending subsystem, a printer or copy service subsystem, or any other type of building subsystem that uses controllable equipment and/or sensors to monitor or controlbuilding10. In some embodiments,building subsystems428 includewaterside system200 and/orairside system300, as described with reference toFIGS. 2 and 3.
• Each of buildingsubsystems428 can include any number of devices, controllers, and connections for completing its individual functions and control activities.HVAC subsystem440 can include many of the same components asHVAC system100, as described with reference toFIGS. 1-3. For example,HVAC subsystem440 can include a chiller, a boiler, any number of air handling units, economizers, field controllers, supervisory controllers, actuators, temperature sensors, and other devices for controlling the temperature, humidity, airflow, or other variable conditions within building10.Lighting subsystem442 can include any number of light fixtures, ballasts, lighting sensors, dimmers, or other devices configured to controllably adjust the amount of light provided to a building space.Security subsystem438 can include occupancy sensors, video surveillance cameras, digital video recorders, video processing servers, intrusion detection devices, access control devices (e.g., card access, etc.) and servers, or other security-related devices.
• Still referring toFIG. 4,BMS controller366 includes acommunications interface407 and aBMS interface409.Interface407 can facilitate communications betweenBMS controller366 and external applications (e.g., monitoring andreporting applications422,enterprise control applications426, remote systems andapplications444, applications residing onclient devices448, etc.) for allowing user control, monitoring, and adjustment toBMS controller366 and/orsubsystems428.Interface407 can also facilitate communications betweenBMS controller366 andclient devices448.BMS interface409 can facilitate communications betweenBMS controller366 and building subsystems428 (e.g., HVAC, lighting security, lifts, power distribution, business, etc.).
• Interfaces407,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 buildingsubsystems428 or other external systems or devices. In embodiments, communications viainterfaces407,409 can be direct (e.g., local wired or wireless communications) or via a communications network446 (e.g., a WAN, the Internet, a cellular network, etc.). For example, interfaces407,409 can include an Ethernet card and port for sending and receiving data via an Ethernet-based communications link or network. In another example, interfaces407,409 can include a Wi-Fi transceiver for communicating via a wireless communications network. In another example, one or both ofinterfaces407,409 can include cellular or mobile phone communications transceivers. In one embodiment,communications interface407 is a power line communications interface andBMS interface409 is an Ethernet interface. In other embodiments, bothcommunications interface407 andBMS interface409 are Ethernet interfaces or are the same Ethernet interface.
• Still referring toFIG. 4,BMS controller366 includes aprocessing circuit404 including aprocessor406 andmemory408.Processing circuit404 can be communicably connected toBMS interface409 and/orcommunications interface407 such thatprocessing circuit404 and the components thereof can send and receive data viainterfaces407,409.Processor406 can be implemented as a general purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable electronic processing components.
• Memory408 (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 processes, layers and modules described in the present application.Memory408 can be or include volatile memory or non-volatile memory.Memory408 can include database components, object code components, script components, or any other type of information structure for supporting the activities and information structures described in the present application. According to an example embodiment,memory408 is communicably connected toprocessor406 viaprocessing circuit404 and includes computer code for executing (e.g., by processingcircuit404 and/or processor406) one or more processes described herein.
• In some embodiments,BMS controller366 is implemented within a single computer (e.g., one server, one housing, etc.). In otherembodiments BMS controller366 can be distributed across multiple servers or computers (e.g., that can exist in distributed locations). Further, whileFIG. 4 showsapplications422 and426 as existing outside ofBMS controller366, in some embodiments,applications422 and426 can be hosted within BMS controller366 (e.g., within memory408).
• Still referring toFIG. 4,memory408 includes anenterprise integration layer410, an automated measurement and validation (AM&V)layer412, a demand response (DR)layer414, a fault detection and diagnostics (FDD)layer416, anintegrated control layer418, and a building subsystem integration later420. Layers410-420 can be configured to receive inputs from buildingsubsystems428 and other data sources, determine optimal control actions for buildingsubsystems428 based on the inputs, generate control signals based on the optimal control actions, and provide the generated control signals tobuilding subsystems428. The following paragraphs describe some of the general functions performed by each of layers410-420 inBMS400.
• Enterprise integration layer410 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 applications426 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 applications426 can also or alternatively be configured to provide configuration GUIs for configuringBMS controller366. In yet other embodiments,enterprise control applications426 can work with layers410-420 to optimize building performance (e.g., efficiency, energy use, comfort, or safety) based on inputs received atinterface407 and/orBMS interface409.
• Buildingsubsystem integration layer420 can be configured to manage communications betweenBMS controller366 andbuilding subsystems428. For example, buildingsubsystem integration layer420 can receive sensor data and input signals from buildingsubsystems428 and provide output data and control signals tobuilding subsystems428. Buildingsubsystem integration layer420 can also be configured to manage communications betweenbuilding subsystems428. Buildingsubsystem integration layer420 translate communications (e.g., sensor data, input signals, output signals, etc.) across a plurality of multi-vendor/multi-protocol systems.
• Demand response layer414 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 building10. The optimization can be based on time-of-use prices, curtailment signals, energy availability, or other data received from utility providers, distributedenergy generation systems424, from energy storage427 (e.g.,hot TES242,cold TES244, etc.), or from other sources.Demand response layer414 can receive inputs from other layers of BMS controller366 (e.g., buildingsubsystem integration layer420, integratedcontrol layer418, 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 example embodiment,demand response layer414 includes control logic for responding to the data and signals it receives. These responses can include communicating with the control algorithms inintegrated control layer418, changing control strategies, changing set points, or activating/deactivating building equipment or subsystems in a controlled manner.Demand response layer414 can also include control logic configured to determine when to utilize stored energy. For example,demand response layer414 can determine to begin using energy fromenergy storage427 just prior to the beginning of a peak use hour.
• In some embodiments,demand response layer414 includes a control module configured to actively initiate control actions (e.g., automatically changing set points) 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 layer414 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 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 layer414 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 set points 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 layer418 can be configured to use the data input or output of buildingsubsystem integration layer420 and/or demand response later414 to make control decisions. Due to the subsystem integration provided by buildingsubsystem integration layer420, integratedcontrol layer418 can integrate control activities of thesubsystems428 such that thesubsystems428 behave as a single integrated supersystem. In an example embodiment,integrated control layer418 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 layer418 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 buildingsubsystem integration layer420.
• Integrated control layer418 is shown to be logically belowdemand response layer414.Integrated control layer418 can be configured to enhance the effectiveness ofdemand response layer414 by enablingbuilding subsystems428 and their respective control loops to be controlled in coordination withdemand response layer414. This configuration may advantageously reduce disruptive demand response behavior relative to conventional systems. For example,integrated control layer418 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 layer418 can be configured to provide feedback to demandresponse layer414 so thatdemand response layer414 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 layer418 is also logically below fault detection anddiagnostics layer416 and automated measurement andvalidation layer412.Integrated control layer418 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)layer412 can be configured to verify that control strategies commanded byintegrated control layer418 ordemand response layer414 are working properly (e.g., using data aggregated byAM&V layer412, integratedcontrol layer418, buildingsubsystem integration layer420,FDD layer416, or otherwise). The calculations made byAM&V layer412 can be based on building system energy models and/or equipment models for individual BMS devices or subsystems. For example,AM&V layer412 can compare a model-predicted output with an actual output from buildingsubsystems428 to determine an accuracy of the model.
• Fault detection and diagnostics (FDD)layer416 can be configured to provide on-going fault detection for buildingsubsystems428, building subsystem devices (i.e., building equipment), and control algorithms used bydemand response layer414 andintegrated control layer418.FDD layer416 can receive data inputs fromintegrated control layer418, directly from one or more building subsystems or devices, or from another data source.FDD layer416 can automatically diagnose and respond to detected faults. The responses to detected or diagnosed faults can include providing an alert 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 layer416 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 buildingsubsystem integration layer420. In other example embodiments,FDD layer416 is configured to provide “fault” events tointegrated control layer418 which executes control strategies and policies in response to the received fault events. According to an example embodiment, FDD layer416 (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 layer416 can be configured to store or access a variety of different system data stores (or data points for live data).FDD layer416 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 subsystems428 can generate temporal (i.e., time-series) data indicating the performance ofBMS400 and the components thereof. The data generated by buildingsubsystems428 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 byFDD layer416 to expose when the system begins to degrade in performance and alert a user to repair the fault before it becomes more severe.
Temperature, Pressure, and Humidity System
• As shown inFIG. 5A, asystem500 for controlling TPH is structured to receive user input regarding HVAC systems (e.g., thewaterside system200, theairside system300, theBMS system400, etc.) within thebuilding10, and adjust control based on the user input. Thesystem500 may include any combination of aspects described herein. For example, theHVAC equipment524, as described below, may include thepumps234 and thefan338, described reference toFIGS. 2 and 3 or other components, as desired. Thesystem500 includes aBMS controller502, theHVAC equipment524, abuilding zone526, anetwork530, anapplication532, aserver534, and user devices536-540.
• In some embodiments, theBMS controller502 may be similar toBMS controller366 as described above with reference toFIG. 4. In some embodiments,BMS controller502 incorporates additional features or functionality that allow for improved TPH control. TheBMS controller502 includes aprocessing circuit504 communicably connected to acommunications interface522 so that theprocessing circuit504 can send and receive data via thecommunications interface522. Theprocessing circuit504 includes aprocessor506 and amemory508.
• Theprocessor506 can be implemented as a general purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable electronic processing components. The memory508 (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 processes, layers and modules described in the present application.Memory508 can be or include volatile memory or non-volatile memory. Thememory508 can include database components, object code components, script components, or any other type of information structure for supporting the activities and information structures described in the present application. According to an example embodiment, thememory508 is communicably connected to theprocessor506 via theprocessing circuit504 and includes computer code for executing (e.g., by theprocessing circuit504 and/or the processor506) one or more processes described herein.
• In some embodiments, theBMS controller502 is implemented within a single computer (e.g., one server, one housing, etc.). In some embodiments, theBMS controller502 is distributed across multiple servers or computers (e.g., that can exist in geographically separated locations). Thememory508 includes atraining data storage510, amachine learning engine512, afault detector circuit514, awork order circuit516, adata collector518, and aprofile database520. While the systems and methods disclosed herein generally refer to building control within hospitals and clinics, other types of buildings, campuses, and floorplans may implement the systems and methods disclosed herein, including data centers, fish hatcheries, pharmaceutical labs, and office buildings. Additionally, while theBMS controller502 is shown to handle processing related to collecting data, storing profile databases, artificial intelligence, etc., some or all of this functionality may be performed in a distributed group of processors, memories, etc., or within cloud processed applications (e.g., the application532).
• Thetraining data storage510 may be configured to store data used for training one or more machine learning components within thesystem500. For example, thetraining data storage510 is shown providing training data to themachine learning engine512. In some embodiments, training data includes previous fault data related to thesystem500 allowing themachine learning engine512 to develop intelligence that predicts solutions to faults in HVAC systems. For example, thetraining data storage510 may include hundreds of previous faults (e.g., stuck dampers, failed pumps, overheating boilers, stuck valves, incorrect installations, etc.) fromHVAC equipment524. In some embodiments, thetraining data storage510 includes a remote database that can be queried by theBMS controller502 to receive the training data or a portion of the training data. In some embodiments, thetraining data storage510 is located locally within theBMS502 and stores a local set of training data.
• Themachine learning engine512 is structured to receive the training data from thetraining data storage510 and determine trends in which solutions were implemented for correlated faults. For example, restarting a controller/actuator assembly in response to a stuck damper fault. Upon developing the intelligence for predicting solutions for particular faults, theBMS controller502 may then be able to provide theapplication532 with a recommended solution to a fault. The fault solution functionality described herein may be similar to fault prediction systems and methods described in U.S. Patent Publication Application No. 2019/0041882 filed Aug. 3, 2017, the entire disclosure of which is incorporated by reference herein.
• In some embodiments, the training data includes previous fault data related to thesystem500 such that themachine learning engine512 can develop intelligence for predicting solutions to work orders in HVAC systems. Work orders may be submitted via one or more building occupants (these and other information and/or requests are submitted via theapplication532, which is described in greater detail below) or generated automatically either locally by a component that recognizes service is required, a central service prediction system, a fault detection system, or other automated systems. The work orders may include standard equipment updates such as “Pump A requires an oil change” or “Calibrate Actuator C.” However, the work orders may also include specific requests from building occupants. For example, a nurse on a hospital floor may send a request from theiruser device536 via theapplication532 to replace a lightbulb in a patient room. TheBMS controller502 may receive the user request via thenetwork530 and provide a recommended solution for the work order to a technician. The solution may be based on one or more previously filed work orders that may be similar to the current work order. In the above example, this solution may be “Replace single light bulb in Room A5—GE U-Bend Fluorescent Bulb (T8/Medium).” The inclusion of the recommended solution within the work order facilitates a quicker completion time of the work orders.
• In some embodiments, themachine learning engine512 utilizes decision trees, generated models via a model predictive architecture, trend analyses, neural networks, deep neural networks, reinforcement learning, and other machine learning and artificial intelligence schemes that improve over time and improve predictions of theBMS controller502. No matter the specific implementation of themachine learning engine512, the training data is utilized to develop a machine learning scheme structured to receive inputs in the form of faults or work requests, and provide a recommended solution. As described herein, users may refer to facility managers, technicians, nurse managers, compliance officers, nurses, doctors, and other building occupants.
• Thefault detector circuit514 is structured to determine that a fault has occurred in a system of component. In some embodiments, the fault is a sensed failure of a system or component, a manually entered fault of a system or component, or a user request (e.g., the lightbulb example described above). Thefault detector circuit514 is structured to provide the fault to themachine learning engine512, and to receive a recommended solution from themachine learning engine512. Thefault detector circuit514 then sends the fault and the recommended solution to thework order circuit516. For example, thefault detector circuit514 may send the fault and recommended solution to the interface of auser device536 via theapplication532.
• Thework order circuit516 is structured to receive the fault and recommended solution from thefault detector circuit514 and assemble a work order for distribution to relevant users via thenetwork530 and theapplication532. In some embodiments, thework order circuit516 assigns a priority to the generated work order based on the urgency of the work order. For example, a light bulb change has a significantly lower priority than a work order directed to a chiller fault that may materially affect TPH in a critical area.
• Thedata collector518 receives user requests for work orders, user requests for information, sensor data, queried database information, and other information via thecommunications interface522. In the event that a user requests information (e.g., TPH data for March, 2020 for building zone A, etc.),data collector518 may query a database for the requested information and provide the information to the user via theapplication532.
• Theprofile database520 stores profiles of users of theapplication532. For example, if theapplication532 is implemented for employees of a hospital, the users may include nurses, service technicians, maintenance workers, administrators, doctors, facility managers, utilities managers, etc. may have access to theapplication532. In some embodiments, each individual provided access to theapplication532 is assigned a profile defining what information is available to the individual user. In some embodiments, each user profile defines a dashboard designed to provide information relevant to the user's role. For example, nurses may not need to see predicted fault solutions for faults being detected in a chiller bank. The nurse in this example may access a dashboard that provides available scheduling information related to TPH and room availability, real time monitors of assigned rooms TPH, etc. The profiles generated for each user (e.g., employee, building occupant, etc.) may be stored in a separate database (e.g., server534) or within theBMS controller502. The profiles may be generated for the users upon registration in theapplication532.
• In some embodiments, theprofile database520 allows users to adjust preferences within the assigned profile. For example, displayed TPH parameters and/or other parameters inbuilding zone526 may be adjusted by the user. A doctor may prefer a cold and dry environment during surgery and may enter the preferences within their assigned profile. As such, the OR room in which the doctor is performing surgery is set to their preferred TPH levels, per a request sent via theapplication532. TheBMS controller502 may maintain TPH levels within the OR according to compliant ranges, while making a best effort to satisfy the doctor's preferences. The above example shows how theBMS controller502 maintains compliance that is required per building code (e.g., ASHRAE standard 170, etc.) while also providing custom HVAC control and comfortability to users.
• Thecommunications interface522 can facilitate communications between theBMS controller502 and external systems (e.g., theapplication532, theHVAC equipment524, the monitoring andreporting applications422, theenterprise control applications426, the remote systems andapplications444, the applications residing onclient devices448, etc.) for allowing user control, monitoring, and adjustment to theBMS controller502. Thecommunications interface522 can also facilitate communications between theBMS controller502 and theclient devices448. Thecommunications interface522 may facilitate communications between theBMS controller502 and the building subsystems428 (e.g., the HVAC, the lighting security, the lifts, the power distribution, the business, etc.). Thecommunications interface522 may be configured to facilitate communication between components within thesystem500, including thenetwork530, theHVAC sensors528, theHVAC equipment524, theserver534, and the user devices536-540.
• Thecommunications interface522 can be or include wired or wireless communications interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wire terminals, etc.) for conducting data communications with theapplication532 or other external systems or devices. In embodiments, communications via thecommunications interface522 can be direct (e.g., local wired or wireless communications) or via a communications network such as the network530 (e.g., a WAN, the Internet, a cellular network, etc.). For example, thecommunications interface522 can include an Ethernet card and port for sending and receiving data via an Ethernet-based communications link or network. In another example, thecommunications interface522 can include a Wi-Fi transceiver for communicating via a wireless communications network. In another example, thecommunications interface522 can include cellular or mobile phone communications transceivers. In one embodiment, thecommunications interface522 is a power line communication. In other embodiments, thecommunications interface522 is an Ethernet interface.
• Thebuilding zone526 may be configured to represent a region within building10, including floors, spaces, zones, rooms, hallways, areas, and any other location within building10. In one embodiment, thebuilding zone526 is an operating room (OR) in a hospital. In another example, thebuilding zone526 is a hospital floor. In another example, thebuilding zone526 is a region within a building that spans one or more floors. Thebuilding zone526 may be known to theBMS controller502 such that information may be displayed on theapplication532 that is specific to thebuilding zone526. In some embodiments, thebuilding zone526 spans across several buildings, such that thebuilding zone526 acts as a campus (e.g., a hospital campus, etc.). While only a single building zone (the building zone526) is shown inFIG. 5A, several building zones may be monitored by theBMS controller502. For example, theBMS controller502 is providing TPH data to theapplication532 for 20 different building zones: five pertaining to OR's, five pertaining to administrative areas, five pertaining to waiting rooms, and five pertaining to patient rooms. The number of building zones and types of building zones are non-limiting.
• TheHVAC sensors528 can be or include any number and type of building sensors, including temperature sensors, pressure sensors, humidity sensors, flow sensors, and positional sensors. In some embodiments, theHVAC sensors528 include temperature, pressure, and humidity sensors configured to monitor the TPH levels within thebuilding zone526. TheHVAC sensors528 may be configured to transmit measurements wirelessly or wiredly. In some embodiments, theHVAC sensors528 are plug-n-play (PnP) sensors configured to transmit data wirelessly over a building automation protocol.
• Thenetwork530 may include any combination of computational and/or routing devices configured to move data from one computer or device to another. Thenetwork530 may act as a local network than employs local area network (LAN) functionality. In other embodiments, thenetwork530 includes campus, backbone, metropolitan, wide, cloud, and internet scope. For example, thenetwork530 may be connected to off-premise servers that can implement cloud networking. This may allow theapplication532, for example, to access an off-premise server (e.g., server534) to retrieve data. In other embodiments, theapplication532 is stored inserver534 off-premise and can be hosted on user devices536-540 due to the cloud networking functionality of thenetwork530.
• In some embodiments, thenetwork530 includes building automation protocol functionality (e.g., Building Automation and Control networks (BACnet), Modbus, etc.) such that devices within thesystem500 may communicate with one another with previously implemented software that allows for such. In some embodiments, thesystem500 is configured to operate under Metasys® protocols, as designed by Johnson Controls, Inc. In other embodiments, thesystem500 is configured to operate under Verasys® protocols, as designed by Johnson Controls, Inc. In embodiments, thenetwork530 can facilitate communication across any number of building automation protocols, area networks, on premise networks, off-premise networks, and any combination thereof.
• Theapplication532 may include features and functionality that allow users (e.g., via user devices536-540) to interact with theBMS controller502. In some embodiments, users can place requests for work orders, view TPH data relating to thebuilding zone526, view faults within thesystem500, receive suggested fault solutions, and receive updates related to theapplication532. Theapplication532 may be implemented entirely on a user device, or may merely be hosted on a user device and stored on a server. Theapplication532 may be implemented as a software as a service (SaaS), infrastructure as a service (IaaS), platform as a service (PaaS), mobile backend as a service (MBaaS), or any other cloud computing method.
• Theserver534 may be or include one or more servers, processing circuits, processors, memory, or any combination thereof for storing and hosting software applications, including theapplication532. Theserver534 may be located on premise (e.g., within building10, on a server within building10, on a computer's memory within building10, hosted peer-to-peer between devices within building10, etc.) or off-premise (e.g., via cloud computing, etc.). In some embodiments, the processes for implementing theapplication532 may be distributed across multiple servers.
• User devices536-540 may include any type of smartphone, tablet, computer, workstation (e.g., terminal, etc.), personal display device, or laptop. In some embodiments,user devices536 host theapplication532 and communicate with theBMS controller502 via thenetwork530. User devices536-540, while shown to include only three devices inFIG. 5A, can include more or less that three devices. For example, every employee may be given access and a profile for theapplication532. Each device used by a user to access theapplication532 may be considered a user device as described herein. In some embodiments, the user device may be permanently installed in a physical location and an interactive panel or kiosk. In some embodiments, a user can login into their profile using the user device so that a single user device is usable by more than one user.
• BMS with Work Order Generation
• As shown inFIG. 5B, thesystem500 is structured to generate and provide work order information to theapplication532. Thememory508 of theprocessing circuit504 includes thetraining data storage510, themachine learning engine512, thefault detector circuit514, thework order circuit516, thedata collector518, theprofile database520, and ascheduling circuit542. In some embodiments, thesystem500 is configured to receive sensor data and, in some embodiments, user requests, and generate a work order for a particular user ofapplication532. The data for the work order (e.g., contents of the work order, possible solutions, etc.) may be based on the inputs, machine learning functionality, the user's profile, scheduling conflicts, and any combination thereof. In some embodiments,system500 as shown inFIG. 5B may be a more detailed diagram of thememory508 as described above with reference toFIG. 5A, wherein the processing is more specifically devoted to generating appropriate work orders for one or more users ofapplication532. As described herein,FIGS. 5B-5D may all be considered different embodiments of thememory508 as described above with reference toFIG. 5A, wherein thememory508 may include some or all aspects of the components described therein.
• Thedata collector518 may receive sensor data from theHVAC sensors528. In some embodiments, thedata collector518 may also receive user requests that may affect the generation and/or providing of work orders (e.g., a user requests an update to a previously received work order, a user wishes to update their profile which affects the type of information they receive regarding work orders, etc.). The sensor data may include PTH data regarding thebuilding zone526. Thedata collector518 may provide the sensor data to thefault detector circuit514 and theapplication532. In some embodiments, the data is provided to theapplication532 such that raw PTH data may be displayed on the application in real-time. However, circuitry may be included inmemory508 that selectively provides the sensor data to theapplication532. For example, the dashboard of theapplication532 for a service technician is only provided the PTH data in 10 minute intervals of the PTH data, even though the PTH data is taken by theHVAC sensors528 every 5 minutes.
• Thefault detector circuit514 may receive the sensor data and process the sensor data to determine if any of the sensor data is indicative of a fault, or anything else that would necessitate a work order insystem500. For example, thefault detector circuit514 may determine that the pressure and temperature levels ofbuilding zone526 are out of compliance (e.g., outside of acceptable ranges for pressure and temperature ranges in the buildings, etc.). Accordingly, thefault detector circuit514 provides a signal to workorder circuit516 to begin the process of resolving the non-compliant issues ofbuilding zone526.
• In some embodiments, thefault detector circuit514 provides fault data (e.g., sensor data, an indication of a fault, the type of detected fault, etc.) to themachine learning engine512 so that themachine learning engine512 can determine the appropriate solution and provide that to thework order circuit516.FIG. 5B shows thefault detector circuit514 providing a work order request to workorder circuit516.
• Thework order circuit516 may receive the work order request as an input for providing a work order or a notification of a work order to a user of theapplication532. The work order circuit may also receive a predicted solution of the work order from themachine learning engine512. In the above example regarding non-compliant pressure and temperature levels inbuilding zone526, themachine learning engine512 may use thetraining data510 to develop a neural network that can learn how to solve non-compliant PTH issues in the building zone526 (using AI techniques described above). Thework order circuit516 may provide the issue relating to the work order to the machine learning engine512 (not shown) and, in response, themachine learning engine512 provides the solution of fixing a faulty damper in the air duct312 (e.g., the damper320).
• Thework order circuit516 may also receive profile information as an input. As described above, different amounts or types of information can be provided to theapplication532 depending on which profile is signed in to theapplication532. In some embodiments, thework order circuit516 queries theprofile database520 for profile information relating to the multiple users of theapplication532. In the above example, the work order circuit queries the profiles for a nurse, a doctor, a service technician, and a facility manager. Thework order circuit516 determines that merely a notice (e.g., an alert, a notification, etc.) that there is an issue with pressure and temperature levels inbuilding zone526 is provided to the nurse's and the doctor's profile of theapplication532. The service technician (via the application532) may receive significantly more information, such as all of the relevant pressure and temperature data, wherebuilding zone526 is located, and the predicted solution to resolving the non-compliant PTH levels in the building zone526 (predicted by the machine learning engine512). The facility manager may receive more supervisory information related to the issue, such as the selected service technician who is resolving the issue of the work order, the progress of solving the issue, and the predicted solution.
• In some embodiments, thework order circuit516 includes processing that organizes the predicted solutions, work order requests, and relevant data and appropriately provides the correct information to the users of theapplication532. This correct information may be considered the work order. Using the above example, the nurse may log into theapplication532 by singing into their profile and see that there was a non-compliance issue inbuilding zone526 and, as such, he/she cannot reservebuilding zone526 for an upcoming surgery. The service technician may log into theapplication532 by signing into their profile and see that he/she has been assigned a new work order that needs to be completed and that a potential solution is fixing thedamper320 in theair duct312. The facility manager may log into theapplication532 by signing into their profile and see that he/she has a work order that has almost been completed by the service technician, and that the service technician replaced thedamper320 to resolve the work order. Thework order circuit516 may also receive scheduling information (e.g., scheduling conflicts, etc.) as an input from thescheduling circuit542.
• In some embodiments, work order information, including TPH data, reporting data, summaries regarding one or more work orders, and any other work order information may be reported and/or provided for to other systems (e.g., external and internal) for further analytics. For example, TPH data for a particular week within building10 may be reported to a compliance agency to determine whethersystem500 has been operating within compliance.
• Thescheduling circuit542 may be configured to facilitate reservations made by users of theapplication532 and provide scheduling conflicts to thework order circuit516. These reservations can include location reservations with additional PTH requirements. For example, thescheduling circuit542 may facilitate a reservation request from a nurse to request an OR room from 3:00-5:00 PM on Thursday, and that the OR room be substantially cold and dry, as the surgery is for a burn patient. In some embodiments, thescheduling circuit542 accounts for the time required to adjust from one reservation with certain PTH settings to another reservation with different PTH settings. Using the above example, the scheduling circuit may receive a reservation request to request the same OR room from 5:00 PM-7:00 PM on Thursday, and that the OR room be substantially hot and humid. Thescheduling circuit542 may not allow this to occur, as there is not sufficient time to adjust to the new settings.
• Other examples of scheduling conflicts include maintenance work (e.g., in response to receiving a work order, etc.) inbuilding zone526 while thebuilding zone526 is reserved. For example, an OR room is reserved on Wednesday for an all-day surgery. There is an issue with the chiller that supplies chilled air to the OR room. The work order generated by thework order circuit516 may require that a shutdown of the HVAC operation in the OR room (required to resolve the work order) cannot be performed on Wednesday as it would interfere with the reservation. In other embodiments, the scheduling conflict is resolved by thesystem500 moving the all-day surgery reservation to another date and/or location, such that the service technician can resolve the work order on Wednesday.
• With reference toFIG. 5B, thescheduling circuit542 may provide any number and types of scheduling conflicts, such as those described above, to thework order circuit516. Thework order circuit516 may provide the work orders, work order notification, work order progress updates, and other transmissions related to the work orders to theapplication532.
• BMS with Alert Functionality
• As shown inFIG. 5C, thesystem500 is structured to provide alerts to users of theapplication532 and/or building occupants of thebuilding10. Thememory508 includes thetraining data storage510, themachine learning engine512, thefault detector circuit514, thedata collector518, theprofile database520, and thealert circuit544. Theprocessing circuit504 may be configured to receive sensor data and appropriately detect a fault and generate/provide the appropriate alerts to one or more users of theapplication532. Thedata collector518 may receive sensor data from theHVAC sensors528 and provide the sensor data to thealert circuit544.
• Thealert circuit544 may be configured to detect a problem, issue, or fault insystem500 and facilitate the appropriate corrective action. Thealert circuit544 may be similar to thework order circuit516 as described above with reference toFIG. 5B. In some embodiments, thealert circuit544 is configured to generate an alert and provide the alert information to thework order circuit516 to generate a new work order (not shown). In other embodiments, thealert circuit544 merely provides notifications that there is an issue occurring withinsystem500. For example, in the event that PTH levels are out of compliance inbuilding zone526, thealert circuit544 may turn on a notification light withinbuilding zone526 with an accompanying audio alert. In some embodiments, the notifications are provided to theapplication532 in a selective manner, such that the information is selectively displayed based on the user's profile. Thealert circuit544 may also receive predicted corrective action from themachine learning engine512 as an input.
• In some embodiments, the alert determined by thealert circuit514 requires corrective action for resolving the alert. For example, an alert that determines that temperature levels are significantly low in buildingzone526 due to a boiler failure may require the corrective action of filling up the fuel of a boiler (e.g., heating oil, kerosene, liquid propane (LP), etc.). This is a common task associated with HVAC boilers, and may be predicted as the solution to the generated alert by themachine learning engine512. In some embodiments, themachine learning engine512 is similar to the machine learning engine described above with reference toFIGS. 5A-B. In some embodiments, thealert circuit546 may take in compliance information from thecompliance database546.
• In some embodiments, theBMS controller502 may receive information relating to compliance standards for the particular type of building that building10 is. For example, if building10 is a hospital, building10 needs to conform to at least ASHRAE standard 170. Thealert circuit544 may query thecompliance database546 to gather this information and use the compliance information to determine whether the received sensor data is indicative of a compliance issue. In some embodiments, thealert circuit544 also receives profile information as an input.
• As described above, different amounts or types of information can be provided to theapplication532 depending on which profile is signed in to theapplication532. In some embodiments, thealert circuit544 queries theprofile database520 for profile information relating to the multiple users of theapplication532. This process may be similar to the querying processes viaprofile database520 as described above. In some embodiments, thealert circuit544 includesfault detector circuit514. Thefault detector circuit514 may act as a subset of thealert circuit544, as a portion of the generated alerts by thealert circuit544 are faults withinsystem500. In some embodiments, they are less problematic and only require a notification to be provided to theapplication532. They may not require and fault detection and/or fault correction.
• Thealert circuit544 may provide profile specific alerts to theapplication532. In some embodiments, the alerts include notifications, suggested solutions, selective information related to the alert, safety recommendations, and other alert elements for providing information to the user of theapplication532. In some embodiments, this alert information is selectively provided based on the profile of the user, as described above. Thealert circuit544 may also provide equipment control signals toHVAC equipment524 and notification control signals tolighting442. While not shown inFIG. 5C, thealert circuit544 may also provide signals to a sound system within building10 to provide audible notifications regarding the generated alert.
• In some embodiments, thealert circuit544 includes a display panel positioned in a patient room. In some embodiments, thealert circuit544 includes a display panel positioned in a nurses station. In some embodiments, thealert circuit544 includes an audible alert. The audible alert may include an indication of a problem or a solution. In some embodiments, the alert generated by thealert circuit544 provides information regarding when the temperature, pressure, and humidity will be returned to compliance. The alert may also include a communication sent to a predetermined distribution list. The alert may also include a message (e.g., SMS message, email, text, push notification, etc.) sent to the user.
• BMS with Scheduling System Integration
• As shown inFIG. 5D, thesystem500 is structured to manage scheduling requests while attempting to maintain PTH compliance. Thememory508 includes thedata collector518, theprofile database520, thescheduling circuit542, thecompliance database546 and apreconditioning circuit548. Theprocessing circuit504 may be configured to receive sensor data and scheduling requests, process the requests in light of compliance requirements, preconditioning parameters and scheduling conflicts, and provide information related to the scheduling back to theapplication532. Thedata collector518 may receive sensor data fromHVAC sensors528 and scheduling requests from theapplication532.
• In some embodiments, these scheduling requests include reservations to reserve a room (e.g., an OR room in a hospital, etc.). The scheduling requests may also include requests for particular HVAC parameters, including PTH levels. For example, a doctor requests the reservation of a room where surgery will be performed. He/she prefers a cooler, dryer environment and, as such, request a lower temperature and humidity percentage during the schedule reservation time. Thescheduling circuit542 may also take into consideration whether the requested PTH levees would remain in compliance. Thedata collector518 may provide the sensor data and scheduling requests (not shown) to thescheduling circuit542.
• Thescheduling circuit542 may receive the sensor data and the scheduling requests and determine the allowability of the request. Thescheduling circuit542 may also receive preconditioning parameters from thepreconditioning circuit548. In some embodiments, thepreconditioning circuit548 is configured to organize a schedule for an operating room in coordination with the HVAC control ofsystem500. Integration of the scheduling system with the controller may allow the system to incorporate draw down time (e.g., the time is takes to sufficiently cool the room and stabilize TPH before a surgery) into the schedule to avoid overlap of procedures or delays in the schedule do to a room that is not ready on time.
• In some embodiments, thepreconditioning system548 includes a sanitization system (e.g., UV soak system, a fumigation system, etc.) that executes a preconditioning routine when desired. In some embodiments, the time for preconditioning is accounted for by thescheduling circuit542. Thepreconditioning circuit548 may determine the various preconditioning parameters required for the reservation and provide the parameters to thescheduling circuit542. Thescheduling circuit542 may also receive the compliance information from thecompliance database546.
• In some embodiments, theBMS controller502 may receive information relating to compliance standards for the particular type of building that building10 is. For example, if building10 is a hospital, building10 needs to conform to at least ASHRAE standard 170. Thealert circuit544 may query thecompliance database546 to gather this information and use the compliance information to determine whether the received sensor data is indicative of a compliance issue. In some embodiments, thealert circuit544 also receives profile information as an input.
• Thescheduling circuit542 may also receive profile information from theprofile database520. In some embodiments, different amounts or types of information can be provided to theapplication532 depending on which profile is signed in to theapplication532. In some embodiments, thescheduling circuit542 queries theprofile database520 for profile information relating to the multiple users of theapplication532. This process may be similar to the querying processes viaprofile database520 as described above.
• In an exemplary embodiment, the operating room administrator enters a reservation request via theapplication532. Thescheduling circuit542 receives the request and populates a schedule including any preconditioning and/or draw down required. If the preconditioning or draw down routines will exceed the available time slot requested, an alert will be provided to theapplication532. Once the operation is scheduled, preconditioning and draw down requests are automatically generated by theBMS controller502 and at the scheduled time, the controller operates the HVAC system and the preconditioning system to prepare the room on time for the scheduled operation. Thescheduling circuit542 may provide scheduling confirmations, time delay indications, and scheduling updates to theapplication532. Thescheduling circuit542 may also be configured to provide control signals to HVAC equipment withinbuilding subsystems428.
Application Dashboard
• As shown inFIG. 6A, theuser device540 includes auser interface602. Theuser interface602 displays theapplication532 described above. In some embodiments, theapplication532 includes display icons, interactive buttons, charts, historical data, predictions, schedules, work orders, recommended solutions, potential uses for a building zone, and other information, as desired. In some embodiments, theapplication532 provides adashboard604 or a series ofdisplay windows604 that the user can access to view information and/or interact with theBMS controller502. In one non-limiting example, thedashboard604 includes aprofile header606, asettings widget608, aTPH window610, afault window612, and a selection widgets614-618.
• In some embodiments, theuser interface602 includes thedashboard604 that displays real time TPH information and other information relevant to TPH compliance. In some embodiments, the dashboard includes a display panel mounted in a room. The display panel can provide digital readouts of TPH within the room. In some embodiments, the display panel includes physical sensors (e.g., a ball-in-the-wall pressure sensor, etc.) that hospital rooms have traditionally used for quick confirmation of the readouts displayed on the dashboard. The display panel may include digital displays of temperature, pressure, and humidity shown as speedometer type readouts, bar displays, or other display types. In some embodiments, the display panel shows color coded elements indicating TPH compliance status. For example, a background may change to yellow when TPH is approaching a compliance standard, and red when TPH is out of compliance.
• In some embodiments, thedashboard604 includes a computer monitor at a nursing station or another central location accessible near the monitored rooms. Thedashboard604 may provide audible alerts or instructions regarding TPH compliance when a TPH compliance problem is sensed or predicted by the controller. Thedashboard604 may include a user interface that allows a user to input TPH demands (e.g., a change of temperature) within the allowable range for TPH compliance.
• In some embodiments, thedashboard604 provides the user with available options for temperature, pressure, and humidity so that compliance can be maintained. Additionally, thedashboard604 can include a display or indication of energy consumption and/or cost savings attributed to TPH selections. For example, a warmer room temperature in the summer may lower energy consumption thereby reducing costs associated with TPH and also meeting compliance standards.
• In some embodiments, thedashboard604 can include a mobile device (e.g., a smartphone) structured to interact with the controller. The mobile device can include an executable program stored on a non-transitory storage medium and capable of interacting via a wireless network with the controller to display information and provide feedback from the user to the controller.
• In some embodiments, thedashboard604 can include a parts inventory accessible by a facilities director and a technician. The parts inventory can interface with the work order system to provide a listing of relevant parts in inventory and their location within the work order. The parts inventory can save valuable time by auto-generating a list of required parts and tools to address the work order.
• In some embodiments, thedashboard604 includes head-up-display (HUD) interface that can be used hands free to interact with the controller. The HUD interface may be especially useful for a technician fulfilling a work order. For example, the HUD may allow for augmented reality displays to aid in the completion of the work order. Instructional diagrams, videos, or audio recordings could be displayed via the HUD interface while leaving the technicians hands free to complete work.
• In some embodiments, thedashboard604 includes a help function as described briefly above and structured to convey TPH information and current system status in addition to providing access to other help functions related the TPH (e.g., TPH of a hallway or adjacent rooms). The help function may also include additional details for the facility director or technician to access in depth details of a system or component relevant to a work order.
• In some embodiments, thedashboard604 includes a root cause determination system that is structured to receive input from a large number of rooms and areas service by the HVAC system. The root cause determination system analyzes data from different sources to identify a root cause of a TPH problem. For example, by comparing TPH readings in adjacent rooms, and remote rooms, service by the same HVAC system, a correlation between problematic readings may be found and the controller may be able to identify and common component that is causing the problem. The root cause determination system is capable of analyzing available information to determine a root cause and then generating a work order to address the root cause. In some embodiment, the root cause determination system utilizes artificial intelligence or machine learning to better analyze and understand the HVAC system and efficiently identify the root cause.
• In some embodiments, thedashboard604 includes a compliance standards system that directly links with a third party system to retrieve TPH compliance standards. For example, the dashboard can display the relevant TPH standards set by CMS for the current use of the relevant room. In some embodiments, thedashboard604 includes an audio interface capable of communicating with the user audibly. In some embodiments, thedashboard604 includes a holographic interface capable of displaying a hologram that the user can interact with. The holographic interface can be used for augmented reality when diagnosing a problem and/or completing a work order.
• In some embodiments, thedashboard604 includes a scheduling interface in communication with thescheduling circuit542 to allow interaction with the schedule. Preconditioning times and draw down times may be preprogrammed into thescheduling circuit542 so that the entry of a specific operation includes any TPH preparation time automatically. In some embodiments, thedashboard604 includes an indicator providing visual confirmation that a draw down, or a preconditioning routine is in progress. Thescheduling circuit542 may be integrated with a security or other door control system to inhibit access to the operating room during a preconditioning routine or a draw down.
• Theexemplary dashboard604 shown inFIG. 6A is assigned to Jane Doe, who is a service technician permitted to see TPH data for building zones, fault windows (e.g., showing work orders including faults and recommended solutions), and other information. As discussed above, each user profile may be assigned adifferent dashboard604 so that a different user with a different profile may display different, more, or less information and options. Thedashboard604 may provide general information to all occupants (e.g., real time TPH information, etc.). Theprofile header606 may merely act as an identifier to the specific profile associated with the displayeddashboard604. In some embodiments, theprofile header606 includes a drop-down navigation tree to access more features of theapplication532.
• Thesettings widget608 may act as a selection tool for choosing different settings for theapplication532. In some embodiments, operational criteria may be implemented that is particularly suited for an epidemiological pandemic (e.g., COVID-19). For example, during the COVID-19 pandemic, it may be necessary to maintain the temperature, humidity, and pressure levels within a desired range. In some embodiments, multiple types of selection rules can be considered and are not limited to a single selection that can be turned on or off. Thesettings widget608 may provide instructions to theBMS controller502 to maintain control based on certain criteria that are specific to the current setting. For example, theBMS controller502 may include instructions that, when the COVID-19 setting is set, the TPH parameters of thebuilding zone526 should conform to ASHRAE Standard 170. In some embodiments, the settingwidget608 can be updated universally such that the settings are changed without input from the user and all settings are updated within eachdashboard604. For example, the COVID-19 settings may be updated in view of new studies or new standards (e.g., an advantageous temperature range, a particular humidity threshold, a negative pressure differential, etc.). As disclosed herein, “widget” may refer to any component or interactive item on an interface that a user can interact with, including buttons, scroll devices, windows, calendars, and navigation trees.
• Thesettings widget608 may change depending on the location of theuser device540 and the user profile. For example, the settingwidget608 may be integrated with a scheduling system and recognize that a nurse is accessing the dashboard within an OR. Thesettings widget608 then displays OR specific settings. In some embodiments, thesettings widget608 includes a burn procedure setting that dictates an increased ambient temperature, an orthopedics procedure setting that dictates a lower temperature, or other settings specific to the use of the OR. In some embodiments, thedashboard608 receives information from a scheduling system and determines the room use and provides a room specific setting. For example, if the room is being used for an infection disease control, the dashboard may recognize the use from the scheduling system and provide pressure settings via thesettings widget608.
• TheTPH window610 displays pressure, temperature, humidity measurements, and time stamps. In some embodiments, theHVAC sensors528 provide sensor data to theBMS controller502 at consistent sample rates (e.g., every second, every 10 seconds, every minute, every hour, etc.) and theBMS controller502 provides the time stamp associated with the last received information. In other embodiments, the user of theuser device540 determines the time intervals for display. For example, a nurse may not want real time display of temperature which may fluctuate. The nurse may prefer an average temperature over a five minute interval. The user profile preferences can be updated to reflect the desired display mode. In some embodiments, theTPH window610 displays the ASHRAE Standard 170 TPH values. For example, the ASHRAE Standard 170 may state that temperature measurements are maintained in a temperature range of 20-24° C. and humidity is maintained in a humidity range of 20-60% for a particular room use.
• Thefault window612 displays fault information. In some embodiments, thefault window612 displays potential fault causations and/or solutions that may be determined at least in part by themachine learning engine512 as discussed above. Fault information can include a time of the fault, a raw fault code, a location of fault, a particular controller that discovered the fault, a particular sensor that measured the parameter that the fault was based on, required tools, required replacement parts, inventory of replacement parts on hand, etc.
• Afirst selection widget614 displays “See other zones.” A user may select theselection widget614 to toggle between different zones within building10. While not shown inFIG. 6A, another window may open that allows the user to pick other building zones to view their respective information. For example, while zone A (currently shown inFIG. 6A) may refer to a first OR, and other OR rooms are accessible via theselection widget614. The user may interact with theselection widget614 to access information for a second OR.
• Asecond selection widget616 displays “Fault History.” In some embodiments, thesecond selection widget616 allows a user to access previous fault information related to thesystem500. For example, a service technician may wish to see previous data for building zone A.
• Athird selection widget618 displays “Submit a Work Order.” In some embodiments, thethird selection widget618 allows a user to submit one or more work orders requests. For example, if a TPH issue is identified, the user can interact with the third selection widget to report an issue.
• Theapplication532 may also include functionality to reserve certain building zones and/or operating rooms to avoid cross-contamination. For example, if a COVID-19 patient has been held in a particular room, it may be beneficial to wait until the room is no longer hazardous (e.g., low risk of spreading the disease, etc.) before bringing in a patient that does not have COVID-19. As such, reservation functionality that incorporates “hot-desking” features may be implemented. As described herein, hot-desk functionality may refer to determining when a desk, room, zone, or other location is no longer hazardous such that reservations may be held at or proximate to the location. In some embodiments, this hot desk functionality may take into account the air pathways within thebuilding zone526. For example, if a COVID-19 patient is within a patient room that is directly in an air pathway from an HVAC blower fan, theapplication532 may register this and determine that all reservable locations within the air path are no longer reservable until they are considered no longer hazardous. In some embodiments, flush functionality may be implemented that allows all of the air in between surgeries to be flushed from the rooms. This is described in greater detail with reference toFIG. 5A-D above.
• Systems and methods for incorporating air pathways into HVAC control may utilize systems described in U.S. patent application Ser. No. 16/927,063 filed Jul. 13, 2020, U.S. patent application Ser. No. 16/927,281 filed Jul. 13, 2020, U.S. patent application Ser. No. 16/927,318 filed Jul. 13, 2020, U.S. Provisional Patent Application No. 63/044,906 filed Jun. 26, 2020, U.S. patent application Ser. No. 16/927,759 filed Jul. 13, 2020, U.S. patent application Ser. No. 16/927,766 filed Jul. 13, 2020, and U.S. Provisional Patent Application No. 63/071,910 filed Aug. 28, 2020, the entire disclosures of which are incorporated by reference herein.
• As shown inFIG. 6B, theuser interface602 shows another embodiment ofapplication532 and thedashboard604. Thedashboard604 includes apersonal schedule620, awork order window626, and asettings window630. In some embodiments,FIG. 6B shows more functionality and display features that can be displayed onapplication604. Thepersonal schedule620 includesschedule622 which shows current reservations for the user. In some embodiments, the reservations are specific to the user.Dashboard604 also includesreservation request button624.Reservation request button624 may be selected by a user to request a room reservation, such as the reservations described above with reference toFIG. 5D.
• Work order window626 includesnew work order628. In some embodiments, the user-specific work order is provided to theapplication532, as described above with reference toFIG. 5B. These user-specific work orders may be displayed inwork order window626 for viewing. In some embodiments, the information relating to the work order or other notification (e.g., alert, update, etc.) is specific to the profile of the user signed in to theapplication532.
• Thedashboard604 includessettings window630. In some embodiments, settings window allows a user to set particular settings for thebuilding zone526. In some embodiments,settings window630 is used to provide HVAC settings when making a reservation. For example, a user selectionsrequest reservation button624 and, when prompted for additional information, the user indicates that “Burn Patient” setting from thesettings window630 should be applied during the reservation.
• In some embodiments,dashboard604 includes functionality for viewing or checking the progress of a work order. This may provide real-time status of the completion of the work order or various checkpoints throughout the process. This functionality may be embedded ondashboard604 to be selected by a user via a button or other widget. For example, a user selects a work order progress button to view the status of a pending work order.
TPH Control Processes
• As shown inFIG. 7, aprocess700 for controlling building conditions based on user input is performed by theBMS controller502, or partially or entirely by any other processing device in thesystem500. For example, theBMS controller502 performs steps702-704, and theapplication532 performs steps706-710.
• Atstep702, theprocess700 receives sensor data from one or more sensors. In some embodiments, theHVAC sensors528 can provide sensor data to theBMS controller502 for processing. While not shown inFIG. 5A, theserver534 may handle the processing of all the sensor data and theHVAC sensors528 provide the sensor data to theserver534 for processing. TheBMS controller502 may receive the sensor data wirelessly via plug-n-play functionality or wiredly, which may be performed over BACnet protocol or other building automation protocols.
• Atstep704, theprocess700 provides the sensor data to a user interface. In some embodiments, the user may want to simply view the raw data from theHVAC sensors528 and theBMS controller502 may simply receive the sensor data and provide the data to theapplication532 for display on theuser interface602. In some embodiments, theBMS controller502 may selectively provide data based on the user's request. For example, the user may not want to see all sensor data from all theHVAC sensors528 in thebuilding zone526, and may only wish to see TPH information from a single room.
• Atstep706, theprocess700 receives a request to adjust building conditions from the user device. In some embodiments, a user requests a change in building conditions via theapplication532. For example, a user may want to adjust the TPH levels of an operating room in a hospital, as the surgeon prefers a cooler, more dry room. Accordingly, a nurse requests (via the application532) a TPH change. This change may be requested digitally (e.g., the nurse can select an actual value for the TPH parameters, etc.), or via analog (e.g., the nurse can rotate a dial to adjust TPH parameters, etc.). TheBMS controller502 may receive the request and adjustHVAC equipment524 to satisfy the request.
• Atstep708, theprocess700 adjusts HVAC equipment to satisfy the request while maintaining temperature, pressure, and humidity within a predetermined range. As described above, this step may be performed by theBMS controller502 by sending control signals toHVAC equipment524. In some embodiments, theBMS controller502 takes into account and predictions or trends analyzed by themachine learning engine512 when providing control signals.
• Atstep710, theprocess700 provides a notification to the user interface indicating that the request has been satisfied. Theapplication532 may display a completion notice that the TPH levels have been adjusted accordingly. In some embodiments, notifications to theapplication532 may be provided for completed workers and resolved faults in thesystem500 as well. Notifications may include text messages, picture messages, or a combination of both. In some embodiments, theapplication532 sends a text message to the user device using theapplication532 to notify them that their request was satisfied.
• As shown inFIG. 8, aprocess800 for predicting solutions to faults in an HVAC system is performed by theBMS controller502, or partially or entirely by any other processing device in thesystem500. For example, theBMS controller502 may perform the steps802-810.
• Atstep802, theprocess800 receives the work order training data including previously filed work orders for the HVAC equipment and solutions implemented to satisfy the previously filed work orders. In some embodiments, thetraining data storage510 provides the work order training data to themachine learning engine512 for processing.
• Atstep804, theprocess800 generates a policy based on the work order training data and the solutions implemented to satisfy the work orders within the work order training data. In some embodiments, themachine learning engine512 generates a policy that is initially trained, then continues to learn as new faults are entered and addressed over time. In some embodiments, themachine learning engine512 uses reinforcement learning based on a time to address a fault, a neural network, deep learning networks, or other machine learning architectures. The policy can include mathematical algorithms that are trained using the training data perhaps human input (for verification purposes) to replicate a decision that an expert would make when provided the same information. These algorithms may be supervised or unsupervised.
• Atstep806, theprocess800 receives a new work order from theuser device538. Thefault detector circuit514 provides the work order to themachine learning engine512 may provide an educated guess on how to resolve or complete the work order, as described instep808.Process800 includes predicting an appropriate solution to satisfy the new work order based on the model (Step808).
• Process810 includes providing the new work order and the appropriate solution to the user interface (step810). Step810 may include keeping the user updated throughout the work order process. TheBMS controller502 may provide a notification that the work order has been received, a notification that the work order is being completed, and a notification that the work order has been completed.
• As shown inFIG. 9, aprocess900 for controlling the HVAC control in a building based on machine learning is shown, according to exemplar embodiments.Process900 may be similar toprocess800 in that a machine learning module is being implemented to make predictions on how to solve issues within thesystem500.Process900 may be performed by TheBMS controller502, or partially or entirely by any other processing device in thesystem500. For example, TheBMS controller502 may perform steps all steps902-906.
• Atstep902, theprocess900 receives training data, the training data including satisfied requests and sensor data corresponding to the satisfied requests. Step902 may act as a more generalized embodiment of the processes disclosed above with reference toFIG. 8. Step902 may be implementing machine learning for the entire TPH control within thebuilding zone526. As TPH management may be difficult due to the dependency between the variables: pressure, temperature, and humidity, the machine learning functionality may improve management of TPH levels in necessary regions while maintaining user comfortability for building occupants.
• Atstep904, theprocess900 generates a model of adjustments to the temperature, pressure, and humidity settings based on the plurality of satisfied requests. Atstep906, theprocess900 determines optimized control decisions based on the model to increase energy efficiency or comfortability or both while still satisfying the request. This may be similar to the machine learning described above, where training data is received to train a model. As described herein, machine learning may refer to training algorithms that model a system of data trend. For example, the temperature, pressure, and humidity parameters may have a nonlinear relationship. Due to this, an algorithm (e.g., a neural network matrix, etc.) may be generated to attempt to understand and learn the nonlinear relationship. One method of training the algorithm may include separating the previous data points of the TPH measurements—acting as the training data—and providing them to a neural network as time series data. In this example, the neural network may be a Long Short-Term Model (LSTM), as the inputs are timeseries data. The neural network may provide the predicted outcome of the variables based on the historical data (e.g., the training data). A human may verify the decisions of the neural network via supervised learning. types of artificial intelligence, machine learning techniques, and types of neural networks may be considered.
• As shown inFIG. 10, aprocess1000 determines fault causes in a BMS.Process1000 may be performed by theBMS controller502.Process1000 may implement machine learning to optimizing the mapping process described therein.
• Atstep1002, theprocess1000 includes detecting a fault condition in an HVAC device. In some embodiments, the HVAC device is part of theHVAC equipment524. The fault condition can include any type of fault that would occur in an HVAC system and/or thesystem500. Common faults can include stuck dampers, stuck actuators, inoperable pumps, incorrect temperatures, low operating voltages, and low pump speed. While the systems and methods disclosed herein generally refer to a user using theapplication532 to report information, HVAC sensors measuring parameters in the building zone526 (or operations of HVAC equipment524) may automatically provide fault indications to theBMS controller502.
• At step1004, theprocess1000 includes mapping operational data of the HVAC device to a fault template to determine a potential cause of the fault condition. In some embodiments, a fault causation template may be used that facilitates the relationship between operational data and predicted faults to determine potential fault causations. In other embodiments, machine learning techniques can be used (as described above). Other types of methods to determine solutions to resolve faults may also be considered, such as querying a database of previously resolved faults.
• Atstep1006, theprocess1000 includes providing the detected fault condition and potential cause of the fault condition to the user interface.Step1006 may include keeping the user updated throughout the fault detection and solution process. TheBMS controller502 may provide a notification that the fault detection has occurred, a notification that the fault is in the process of being resolved, and a notification that the fault has been resolved. This may also include the predicted fault solution being provided to a service technician via theapplication532.
• As shown inFIG. 11, aprocess1100 adjusts HVAC parameters based on received scheduling requests. In some embodiments,process1100 is performed byscheduling circuit542.Process1100 may be implemented to determine the appropriate preconditioning requirements for a scheduling reservation requested by a user.
• Atstep1102, theprocess1100 receives a scheduling request form a user interface of an application. In some embodiments, theapplication532 provides a scheduling request to thedata collector518. Thedata collector518 may also receive sensor data fromHVAC sensors528. The scheduling request may be performed by clickingreservation button624 viadashboard604.
• Atstep1104, theprocess1100 populates a schedule based on the request from the user. Thedata collector518 may provide the sensor data and request to thescheduling circuit542. Thescheduling circuit542 may then provide the appropriate updates to the schedule. In some embodiments, the preconditioning parameters related to the scheduling request, compliance thresholds, user's profile, and scheduling conflicts are taken into account prior to providing the scheduling updates to theapplication532.
• Atstep1106, theprocess1100 automatically generates preconditioning requirements based on the request. Atstep1108, theprocess1100 adds preconditioning requirements to the schedule. In some embodiments,preconditioning circuit548 determines the appropriate conditioning services that are required prior to the reservations. These could include different sanitization techniques (e.g., UV wash, disinfecting the room, etc.), PTH changes, equipment changes, and other adjustments. Thepreconditioning circuit548 may determine which of these services are required for the scheduling request and provide these to thescheduling circuit542. Thescheduling circuit542 may take these into consideration when determining whether the request can be approved. For example, the schedule request is for a time in which the room is reserved up to 10 minutes before the requested reservation time and the preconditioning services would take approximately 20 minutes to complete, thescheduling circuit542 may deny the scheduling request.
• Atstep1110, theprocess1100 operates the HVAC equipment to satisfy the preconditioning requirements for the reservation.Scheduling circuit542 may provide control signals toHVAC equipment524 to adjust the HVAC parameters to satisfy the scheduling request. In some embodiments, thescheduling circuit542 may also provide control signals to the lighting subsystem442 (e.g., for a UV wash that is required prior to the reservation, etc.).
Configuration of Exemplary Embodiments
• As utilized herein, the terms “approximately,” “about,” “substantially”, and similar terms are intended to have a broad meaning in harmony with the common and accepted usage by those of ordinary skill in the art to which the subject matter of this disclosure pertains. It should be understood by those of skill in the art who review this disclosure that these terms are intended to allow a description of certain features described and claimed without restricting the scope of these features to the precise numerical ranges provided. Accordingly, these terms should be interpreted as indicating that insubstantial or inconsequential modifications or alterations of the subject matter described and claimed are considered to be within the scope of the disclosure as recited in the appended claims.
• It should be noted that the term “exemplary” and variations thereof, as used herein to describe embodiments, are intended to indicate that such embodiments are possible examples, representations, or illustrations of possible embodiments (and such terms are not intended to connote that such embodiments are necessarily extraordinary or superlative examples).
• The term “coupled” and variations thereof, as used herein, means the joining of two members directly or indirectly to one another. Such joining may be stationary (e.g., permanent or fixed) or moveable (e.g., removable or releasable). Such joining may be achieved with the two members coupled directly to each other, with the two members coupled to each other using a separate intervening member and any additional intermediate members coupled with one another, or with the two members coupled to each other using an intervening member that is integrally formed as a single unitary body with one of the two members. If “coupled” or variations thereof are modified by an additional term (e.g., directly coupled), the generic definition of “coupled” provided above is modified by the plain language meaning of the additional term (e.g., “directly coupled” means the joining of two members without any separate intervening member), resulting in a narrower definition than the generic definition of “coupled” provided above. Such coupling may be mechanical, electrical, or fluidic.
• The term “or,” as used herein, is used in its inclusive sense (and not in its exclusive sense) so that when used to connect a list of elements, the term “or” means one, some, or all of the elements in the list. Conjunctive language such as the phrase “at least one of X, Y, and Z,” unless specifically stated otherwise, is understood to convey that an element may be either X, Y, Z; X and Y; X and Z; Y and Z; or X, Y, and Z (i.e., any combination of X, Y, and Z). Thus, such conjunctive language is not generally intended to imply that certain embodiments require at least one of X, at least one of Y, and at least one of Z to each be present, unless otherwise indicated.
• References herein to the positions of elements (e.g., “top,” “bottom,” “above,” “below”) are merely used to describe the orientation of elements in the FIGURES. It should be noted that the orientation of elements may differ according to other exemplary embodiments, and that such variations are intended to be encompassed by the present disclosure.
• The hardware and data processing components used to implement the processes, operations, illustrative logics, logical blocks, modules and circuits described in connection with the embodiments disclosed herein may be implemented or performed with a general purpose single- or multi-chip processor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a field programmable gate array (FPGA), or other programmable logic device, discrete gate or transistor logic, discrete hardware components, or any combination thereof designed to perform the functions described herein. A general purpose processor may be a microprocessor, or, any conventional processor, controller, microcontroller, or state machine. A processor also may be implemented as a combination of computing devices, such as a combination of a DSP and a microprocessor, a plurality of microprocessors, one or more microprocessors in conjunction with a DSP core, or any other such configuration. In some embodiments, particular processes and methods may be performed by circuitry that is specific to a given function. The memory (e.g., memory, memory unit, storage device) may include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage) for storing data and/or computer code for completing or facilitating the processes, layers and modules described in the present disclosure. The memory may be or include volatile memory or non-volatile memory, and may include database components, object code components, script components, or any other type of information structure for supporting the activities and information structures described in the present disclosure. According to an exemplary embodiment, the memory is communicably connected to the processor via a processing circuit and includes computer code for executing (e.g., by the processing circuit or the processor) the one or more processes described herein.
• The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing 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, 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. 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 and description may illustrate a specific order of method steps, the order of such steps may differ from what is depicted and described, unless specified differently above. Also, two or more steps may be performed concurrently or with partial concurrence, unless specified differently above. Such variation may depend, for example, on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations of the described methods could be accomplished with standard programming techniques with rule-based logic and other logic to accomplish the connection steps, processing steps, comparison steps, and decision steps.
• It is important to note that the construction and arrangement of systems (e.g.,system100,system200, etc.) and methods as shown in the exemplary embodiments is illustrative only. Additionally, any element disclosed in one embodiment may be incorporated or utilized with any other embodiment disclosed herein. Although only one example of an element from one embodiment that can be incorporated or utilized in another embodiment has been described above, it should be appreciated that other elements of the embodiments may be incorporated or utilized with any of the other embodiments disclosed herein.

Claims (20)

What is claimed is:

1. A building management system (BMS) for heating, ventilation, or air conditioning (HVAC) parameters in a building, the BMS comprising:

one or more processing circuits comprising one or more memory devices coupled to one or more processors, the one or more memory devices configured to store instructions thereon that, when executed by the one or more processors, cause the one or more processors to:

institute a policy with a machine learning engine and train the policy using training data,

receive temperature, pressure, and humidity (TPH) sensor data from one or more sensors,

determine a fault based on the TPH sensor data,

provide the TPH sensor data and the fault to the policy of the machine learning engine and output a corrective action to resolve the fault, and

generate a work order for a user based on the TPH sensor data, the determined fault, and the corrective action, and.

2. The BMS ofclaim 1, wherein the user interface includes a first user profile and a second user profile, and

wherein the one or more memory devices are further configured to store instructions thereon that, when executed by the one or more processors, cause the one or more processors to:

generate a first dashboard associated with the first user profile and a second dashboard associated with the second user profile,

provide a first subset of information from the work order to the first dashboard, and

provide a second subset of information from the work order to the second dashboard.

3. The BMS ofclaim 2, wherein the one or more memory devices are further configured to store instructions thereon that, when executed by the one or more processors, cause the one or more processors to:

update the second dashboard based on an action entered on the first dashboard.

4. The BMS ofclaim 2, wherein the work order is stored within the one or more memory devices, and

wherein the one or more memory devices are further configured to store instructions thereon that, when executed by the one or more processors, cause the one or more processors to:

update the work order from either the first dashboard or the second dashboard.

5. The BMS ofclaim 2, wherein the one or more memory devices are further configured to store instructions thereon that, when executed by the one or more processors, cause the one or more processors to:

assign the work order to the second dashboard from the first dashboard.

6. The BMS ofclaim 2, further comprising an application structured to access one of the first user profile or the second user profile and display the associated dashboard on a human machine interface, the associated dashboard displaying at least one of the TPH sensor data or the work order.

7. The BMS ofclaim 6, wherein the human machine interface includes a mobile device, a wall mounted panel, a monitor, a tablet, a kiosk, an augmented reality device, a virtual reality device, or a wearable device.

8. The BMS ofclaim 1, wherein the one or more memory devices are further configured to store instructions thereon that, when executed by the one or more processors, cause the one or more processors to:

retrieve a fault causation template,

map a plurality of operational parameters relating to an associated HVAC device to the fault causation template,

map the corrective action to the fault causation template, and

provide a populated fault causation template to the user interface.

9. The BMS ofclaim 1, wherein the one or more memory devices are further configured to store instructions thereon that, when executed by the one or more processors, cause the one or more processors to:

receive a notification that the work order has been completed, the notification comprising the determined fault and a fault solution, wherein the fault solution is either the corrective action or a different action, and

train the policy with the machine learning engine by providing the determined fault and the fault solution to the machine learning engine.

10. The BMS ofclaim 1, wherein the machine learning engine includes at least one of a neural network, a reinforcement learning scheme, a model-based control scheme, a linear regression algorithm, a decision tree, a logistic regression algorithm, and a Naïve Bayes algorithm.

11. The BMS ofclaim 1, wherein the user is one of a chief compliance officer, a facilities manager, an operating room administrator, a health care professional or a facilities technician.

12. The BMS ofclaim 1, wherein the one or more memory devices are further configured to store instructions thereon that, when executed by the one or more processors, cause the one or more processors to:

provide the work order to a user interface,

receive an indication that the work order has been completed, and

updating the user interface to indicate that the work order has been completed.

13. The BMS ofclaim 1, wherein the one or more memory devices are further configured to store instructions thereon that, when executed by the one or more processors, cause the one or more processors to:

provide assistance functionality to the user interface,

receive a request for assistance from the user interface via the assistance functionality, and

provide additional information related to the corrective action to the user interface.

14. The BMS ofclaim 1, wherein the one or more memory devices are further configured to store instructions thereon that, when executed by the one or more processors, cause the one or more processors to:

provide an alert in the building in response to determining the fault, wherein the alert includes at least one of a visual alert, an audible alert, a fault indication, and corrective action indication.

15. A building management system (BMS) for heating, ventilation, or air conditioning (HVAC) parameters in a building, the BMS comprising:

one or more processing circuits comprising one or more memory devices coupled to one or more processors, the one or more memory devices configured to store instructions thereon that, when executed by the one or more processors, cause the one or more processors to:

receive temperature, pressure, and humidity (TPH) sensor data from one or more sensors,

generate a work order using a machine learning engine that receives the TPH sensor data and fault information and outputs a recommended action,

receive first credentials for a first user and grant access to a first user profile including a first dashboard including first information based at least in part on the TPH sensor data and the work order,

receive second credentials for a second user and grant access to a second user profile including a second dashboard including second information based at least in part on the TPH sensor data and the work order, and

provide communication between the first dashboard and the second dashboard.

16. The BMS ofclaim 15, wherein the first dashboard is configured to:

display one or more customizable features to satisfy a first set of preferences of the first user, and

selectively display the first information according to a type of the first user profile, the type of the first user profile indicating a first amount of detail regarding the TPH sensor data and the work order that can be provided to the first dashboard, and

wherein the second dashboard is configured to:

display the customizable features to satisfy a second set of preferences of the second user, and

selectively display the second information according to a type of the second user profile, the type of the second user profile indicating a second amount of detail regarding the TPH sensor data and the work order that can be provided to the second dashboard.

17. The BMS ofclaim 15, wherein providing communication between the first dashboard and the second dashboard comprises at least one of:

updating the second dashboard based on an action entered on the first dashboard,

updating the work order from either the first dashboard or the second dashboard, and

assigning the work order to the second dashboard from the first dashboard.

18. The BMS ofclaim 15, wherein the first dashboard or the second dashboard or both are configured to:

operate within a heads up display (HUD), and

provide a list of inventory parts currently available for addressing the work order.

19. The BMS ofclaim 15, wherein the first dashboard or the second dashboard or both are configured to:

display regulations and codes related to TPH compliance,

display information related to an interrelation of TPH of one or more building zones in the building, and

display the TPH sensor data and the work order at least in part with color-coded formatting to indicate an intensity of the work order.

20. The BMS ofclaim 15, wherein the first dashboard or the second dashboard or both include:

at least one of an audio interface, a visual interface, a touch screen interface, or a holographic interface, and

a visual indicator proximate to the first dashboard or the second dashboard or both configured to indicate a compliance level of the TPH sensor data.

Images