Patent Description:
Document <CIT> discloses assigning spaces in a building based on comfort models.

One implementation of the present disclosure is a method for controlling the environmental conditions of a building in accordance with feedback from the occupants of the building. The method includes detecting, by one or more processors, an occupant within a building space, and transmitting, by the one or more processors, a notification message to an occupant device associated with the occupant. The notification message includes a request to provide occupant feedback. The method includes receiving, by the one or more processors, an occupant feedback message from the occupant device. The occupant feedback message includes one or more quality ratings associated with one or more building conditions. The method includes assigning, by the one or more processors, a weighting factor to the occupant feedback message and performing, by the one or more processors, an action to modify at least one of the building conditions responsive to the weighted occupant feedback message.

Another implementation of the present disclosure is a system for controlling the environmental conditions of a building in accordance with feedback from the occupants of the building. The system includes multiple mobile devices. Each mobile device is associated with an occupant in a building space. The system further includes a supervisory controller communicably coupled to the mobile devices. The supervisory controller is configured to detect the occupant within the building space, transmit a notification message to the mobile device associated with the occupant, receive an occupant feedback message from the mobile device, assign a weighting factor to the occupant feedback message, and perform an action to modify building conditions responsive to the weighted occupant feedback message.

Another implementation of the present disclosure is a method for providing occupant feedback regarding the environmental conditions of a building from an occupant device. The method includes receiving a notification message requesting occupant feedback, opening an occupant feedback application, capturing multiple occupant feedback inputs, and transmitting an occupant feedback message including the multiple occupant feedback inputs.

Those skilled in the art will appreciate that the summary is illustrative only and is not intended to be in any way limiting. Other aspects, inventive features, and advantages of the devices and/or processes described herein, as defined solely by the claims, will become apparent in the detailed description set forth herein and taken in conjunction with the accompanying drawings.

The present disclosure relates generally to the field of building management systems, and more particularly to systems and methods utilizing an internet enabled device (e.g., smartphone) running an APP for occupants to provide feedback to improve their experience, comfort, and satisfaction of a space within a building. Embodiments of an internet enabled device (e.g., smartphone) running a computer application program or "APP" for providing enhanced capabilities to assist with capturing of feedback regarding the conditions of a space from occupants within the space in accordance with the present disclosure will now be described more fully hereinafter with reference to the accompanying drawings, in which illustrative embodiments of the present disclosure are presented. The internet enabled device and APP of the present disclosure may be embodied in many different forms and should not be construed as being limited to the embodiments set forth herein. Rather, these embodiments are provided so that this disclosure will convey certain example aspects of the internet enabled device and/or APP.

The present disclosure relates to an internet enabled device such as, for example, a smartphone, for running a computer program or APP, which can be used by the occupants of a building space to provide feedback regarding the environmental conditions of a building space. Based on the feedback provided by occupants, the environmental conditions of the building space can be manually or automatically modified to improve the comfort, cleanliness, and security of the building space.

It can be difficult to operate buildings in an efficient manner unless the occupants of the building feel comfortable. Comfort is inherently difficult to measure or simulate because it is highly subjective, and can depend upon air temperature, humidity, radiant temperature, air velocity, metabolic rates, clothing levels, and individual experiences of sensations based on physiology. Attempts to mathematically simulate comfort levels using Computational Fluid Dynamics (CFD) can become highly complex and resource-intensive due to the number of potential variables, and the existence of non-uniform conditions.

If a space within a building is uncomfortable, the occupants will often resort to inefficient means of heating or cooling the space, resulting in higher energy costs. These inefficient means might include opening a window or operating a space heater. In some cases, a building occupant may wish to provide feedback regarding the conditions of a building space, but may lack a frictionless or socially desirable means to do so. For example, occupants of a building space may have negative opinions regarding the cleanliness of a building space, but may not wish to provide those opinions in person. Even if an occupant does not mind voicing negative opinions in person, the occupant may not know the identity of the appropriate recipient for those opinions (i.e., a person empowered to modify the conditions of the building).

Systems and methods in accordance with the present disclosure can facilitate soliciting and providing occupant feedback regarding the conditions of a building space using a smartphone or other mobile device. Systems and methods in accordance with the present disclosure can supplementing current occupant feedback procedures to more accurately operate building management systems, including HVAC systems, which can improve comfort and/or energy efficiency.

Referring now to <FIG>, a building management system (BMS) and HVAC system in which the systems and methods of the present disclosure can be implemented is depicted. Referring particularly to <FIG>, a perspective view of a building <NUM> is depicted. Building <NUM> is served by a BMS. A BMS is, in general, a system of devices that can 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 building <NUM> includes an HVAC system <NUM>. HVAC system <NUM> can include a plurality of HVAC devices (e.g., heaters, chillers, air handling units, pumps, fans, thermal energy storage, etc.) that provide heating, cooling, ventilation, or other services for building <NUM>. For example, HVAC system <NUM> is depicted to include a waterside system <NUM> and an airside system <NUM>. Waterside system <NUM> can provide a heated or chilled fluid to an air handling unit of airside system <NUM>. Airside system <NUM> can use the heated or chilled fluid to heat or cool an airflow provided to building <NUM>. A waterside system and airside system which can be used in HVAC system <NUM> are described in greater detail with reference to <FIG>.

HVAC system <NUM> is depicted to include a chiller <NUM>, a boiler <NUM>, and a rooftop air handling unit (AHU) <NUM>. Waterside system <NUM> can use boiler <NUM> and chiller <NUM> to heat or cool a working fluid (e.g., water, glycol, etc.) and can circulate the working fluid to AHU <NUM>. In various embodiments, the HVAC devices of waterside system <NUM> can be located in or around building <NUM> (as depicted in <FIG>) 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 can be heated in boiler <NUM> or cooled in chiller <NUM>, depending on whether heating or cooling is required in building <NUM>. Boiler <NUM> can add heat to the circulated fluid, for example, by burning a combustible material (e.g., natural gas) or using an electric heating element. Chiller <NUM> can 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 from chiller <NUM> and/or boiler <NUM> can be transported to AHU <NUM> via piping <NUM>.

AHU <NUM> can place the working fluid in a heat exchange relationship with an airflow passing through AHU <NUM> (e.g., via one or more stages of cooling coils and/or heating coils). The airflow can be, for example, outside air, return air from within building <NUM>, or a combination of both. AHU <NUM> can transfer heat between the airflow and the working fluid to provide heating or cooling for the airflow. For example, AHU <NUM> can include one or more fans or blowers that pass the airflow over or through a heat exchanger containing the working fluid. The working fluid can then return to chiller <NUM> or boiler <NUM> via piping <NUM>.

Airside system <NUM> can deliver the airflow supplied by AHU <NUM> (i.e., the supply airflow) to building <NUM> via air supply ducts <NUM> and can provide return air from building <NUM> to AHU <NUM> via air return ducts <NUM>. In some embodiments, airside system <NUM> includes multiple variable air volume (VAV) units <NUM>. For example, airside system <NUM> is depicted to include a separate VAV unit <NUM> on each floor or zone of building <NUM>. VAV units <NUM> can include dampers or other flow control elements that can be operated to control an amount of the supply airflow provided to individual zones of building <NUM>. In some embodiments, airside system <NUM> delivers the supply airflow into one or more zones of building <NUM> (e.g., via supply ducts <NUM>) without using intermediate VAV units <NUM> or other flow control elements. AHU <NUM> can include various sensors (e.g., temperature sensors, pressure sensors, etc.) that measure attributes of the supply airflow. AHU <NUM> can receive input from sensors located within AHU <NUM> and/or within the building zone and can adjust the flow rate, temperature, or other attributes of the supply airflow through AHU <NUM> to achieve setpoint conditions for the building zone.

Referring now to <FIG>, a block diagram of a waterside system <NUM> is depicted. In various embodiments, waterside system <NUM> can supplement or replace waterside system <NUM> in HVAC system <NUM> or can be implemented separate from HVAC system <NUM>. When implemented in HVAC system <NUM>, waterside system <NUM> can include a subset of the HVAC devices in HVAC system <NUM> (e.g., boiler <NUM>, chiller <NUM>, pumps, valves, etc.) and can operate to supply a heated or chilled fluid to AHU <NUM>. The HVAC devices of waterside system <NUM> can be located within building <NUM> (e.g., as components of waterside system <NUM>) or at an offsite location such as a central plant.

In <FIG>, waterside system <NUM> is depicted as a central plant having a plurality of subplants <NUM>-<NUM>. Subplants <NUM>-<NUM> are depicted to include a heater subplant <NUM>, a heat recovery chiller subplant <NUM>, a chiller subplant <NUM>, a cooling tower subplant <NUM>, a hot thermal energy storage (TES) subplant <NUM>, and a cold thermal energy storage (TES) subplant <NUM>. Subplants <NUM>-<NUM> consume resources (e.g., water, natural gas, electricity, etc.) 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 subplant <NUM> can heat water in a hot water loop <NUM> that circulates the hot water between heater subplant <NUM> and building <NUM>. Chiller subplant <NUM> can chill water in a cold water loop <NUM> that circulates the cold water between chiller subplant <NUM> building <NUM>. Heat recovery chiller subplant <NUM> can transfer heat from cold water loop <NUM> to hot water loop <NUM> to provide additional heating for the hot water and additional cooling for the cold water. Condenser water loop <NUM> can absorb heat from the cold water in chiller subplant <NUM> and reject the absorbed heat in cooling tower subplant <NUM> or transfer the absorbed heat to hot water loop <NUM>. Hot TES subplant <NUM> and cold TES subplant <NUM> can store hot and cold thermal energy, respectively, for subsequent use.

Hot water loop <NUM> and cold water loop <NUM> can deliver the heated and/or chilled water to air handlers located on the rooftop of building <NUM> (e.g., AHU <NUM>) or to individual floors or zones of building <NUM> (e.g., VAV units <NUM>). The air handlers push air past heat exchangers (e.g., heating coils or cooling coils) through which the water flows to provide heating or cooling for the air. The heated or cooled air can be delivered to individual zones of building <NUM> to serve the thermal energy loads of building <NUM>. The water then returns to subplants <NUM>-<NUM> to receive further heating or cooling.

Although subplants <NUM>-<NUM> are depicted and described as heating and cooling water for circulation to a building, it is understood that any other type of working fluid (e.g., glycol, CO2, etc.) can be used in place of or in addition to water to serve the thermal energy loads. In some embodiments, subplants <NUM>-<NUM> can provide heating and/or cooling directly to the building or campus without requiring an intermediate heat transfer fluid. These and other variations to waterside system <NUM> are within the teachings of the present disclosure.

Each of subplants <NUM>-<NUM> can include a variety of equipment that can facilitate the functions of the subplant. For example, heater subplant <NUM> is depicted to include a plurality of heating elements <NUM> (e.g., boilers, electric heaters, etc.) that add heat to the hot water in hot water loop <NUM>. Heater subplant <NUM> is also depicted to include several pumps <NUM> and <NUM> that circulate the hot water in hot water loop <NUM> and to control the flow rate of the hot water through individual heating elements <NUM>. Chiller subplant <NUM> is depicted to include a plurality of chillers <NUM> that remove heat from the cold water in cold water loop <NUM>. Chiller subplant <NUM> is also depicted to include several pumps <NUM> and <NUM> that circulate the cold water in cold water loop <NUM> and control the flow rate of the cold water through individual chillers <NUM>.

Heat recovery chiller subplant <NUM> is depicted to include a plurality of heat recovery heat exchangers <NUM> (e.g., refrigeration circuits) that can transfer heat from cold water loop <NUM> to hot water loop <NUM>. Heat recovery chiller subplant <NUM> is also depicted to include several pumps <NUM> and <NUM> that can circulate the hot water and/or cold water through heat recovery heat exchangers <NUM> and to control the flow rate of the water through individual heat recovery heat exchangers <NUM>. Cooling tower subplant <NUM> is depicted to include a plurality of cooling towers <NUM> that can remove heat from the condenser water in condenser water loop <NUM>. Cooling tower subplant <NUM> is also depicted to include several pumps <NUM> that can circulate the condenser water in condenser water loop <NUM> and to control the flow rate of the condenser water through individual cooling towers <NUM>.

Hot TES subplant <NUM> is depicted to include a hot TES tank <NUM> that can store the hot water for later use. Hot TES subplant <NUM> can also include one or more pumps or valves that can control the flow rate of the hot water into or out of hot TES tank <NUM>. Cold TES subplant <NUM> is depicted to include cold TES tanks <NUM> that can store the cold water for later use. Cold TES subplant <NUM> can also include one or more pumps or valves that can control the flow rate of the cold water into or out of cold TES tanks <NUM>.

In some embodiments, one or more of the pumps in waterside system <NUM> (e.g., pumps <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, <NUM>, and/or <NUM>) or pipelines in waterside system <NUM> include an isolation valve associated therewith. Isolation valves can be integrated with the pumps or positioned upstream or downstream of the pumps to control the fluid flows in waterside system <NUM>. In various embodiments, waterside system <NUM> can include more, fewer, or different types of devices and/or subplants based on the particular configuration of waterside system <NUM> and the types of loads served by waterside system <NUM>.

Referring now to <FIG>, a block diagram of an airside system <NUM> is depicted. In various embodiments, airside system <NUM> can supplement or replace airside system <NUM> in HVAC system <NUM> or can be implemented separate from HVAC system <NUM>. When implemented in HVAC system <NUM>, airside system <NUM> can include a subset of the HVAC devices in HVAC system <NUM> (e.g., AHU <NUM>, VAV units <NUM>, ducts <NUM>-<NUM>, fans, dampers, etc.) and can be located in or around building <NUM>. Airside system <NUM> can operate to heat or cool an airflow provided to building <NUM> using a heated or chilled fluid provided by waterside system <NUM>.

In <FIG>, airside system <NUM> is depicted to include an economizer-type air handling unit (AHU) <NUM>. Economizer-type AHUs vary the amount of outside air and return air used by the air handling unit for heating or cooling. For example, AHU <NUM> can receive return air <NUM> from building zone <NUM> via return air duct <NUM> and can deliver supply air <NUM> to building zone <NUM> via supply air duct <NUM>. In some embodiments, AHU <NUM> is a rooftop unit located on the roof of building <NUM> (e.g., AHU <NUM> as depicted in <FIG>) or otherwise positioned to receive both return air <NUM> and outside air <NUM>. AHU <NUM> can be that can operate exhaust air damper <NUM>, mixing damper <NUM>, and outside air damper <NUM> to control an amount of outside air <NUM> and return air <NUM> that combine to form supply air <NUM>. Any return air <NUM> that does not pass through mixing damper <NUM> can be exhausted from AHU <NUM> through exhaust damper <NUM> as exhaust air <NUM>.

Each of dampers <NUM>-<NUM> can be operated by an actuator. For example, exhaust air damper <NUM> can be operated by actuator <NUM>, mixing damper <NUM> can be operated by actuator <NUM>, and outside air damper <NUM> can be operated by actuator <NUM>. Actuators <NUM>-<NUM> can communicate with an AHU controller <NUM> via a communications link <NUM>. Actuators <NUM>-<NUM> can receive control signals from AHU controller <NUM> and can provide feedback signals to AHU controller <NUM>. Feedback signals can include, for example, an indication of a current actuator or damper position, an amount of torque or force exerted by the actuator, diagnostic information (e.g., results of diagnostic tests performed by actuators <NUM>-<NUM>), status information, commissioning information, configuration settings, calibration data, and/or other types of information or data that can be collected, stored, or used by actuators <NUM>-<NUM>. AHU controller <NUM> can be an economizer controller that can use one or more control algorithms (e.g., state-based algorithms, extremum seeking control (ESC) algorithms, proportional-integral (PI) control algorithms, proportional-integral-derivative (PID) control algorithms, model predictive control (MPC) algorithms, feedback control algorithms, etc.) to control actuators <NUM>-<NUM>.

Still referring to <FIG>, AHU <NUM> is depicted to include a cooling coil <NUM>, a heating coil <NUM>, and a fan <NUM> positioned within supply air duct <NUM>. Fan <NUM> can be that can force supply air <NUM> through cooling coil <NUM> and/or heating coil <NUM> and provide supply air <NUM> to building zone <NUM>. AHU controller <NUM> can communicate with fan <NUM> via communications link <NUM> to control a flow rate of supply air <NUM>. In some embodiments, AHU controller <NUM> controls an amount of heating or cooling applied to supply air <NUM> by modulating a speed of fan <NUM>.

Cooling coil <NUM> can receive a chilled fluid from waterside system <NUM> (e.g., from cold water loop <NUM>) via piping <NUM> and can return the chilled fluid to waterside system <NUM> via piping <NUM>. Valve <NUM> can be positioned along piping <NUM> or piping <NUM> to control a flow rate of the chilled fluid through cooling coil <NUM>. In some embodiments, cooling coil <NUM> includes multiple stages of cooling coils that can be independently activated and deactivated (e.g., by AHU controller <NUM>, by BMS controller <NUM>, etc.) to modulate an amount of cooling applied to supply air <NUM>.

Heating coil <NUM> can receive a heated fluid from waterside system <NUM>(e.g., from hot water loop <NUM>) via piping <NUM> and can return the heated fluid to waterside system <NUM> via piping <NUM>. Valve <NUM> can be positioned along piping <NUM> or piping <NUM> to control a flow rate of the heated fluid through heating coil <NUM>. In some embodiments, heating coil <NUM> includes multiple stages of heating coils that can be independently activated and deactivated (e.g., by AHU controller <NUM>, by BMS controller <NUM>, etc.) to modulate an amount of heating applied to supply air <NUM>.

Each of valves <NUM> and <NUM> can be controlled by an actuator. For example, valve <NUM> can be controlled by actuator <NUM> and valve <NUM> can be controlled by actuator <NUM>. Actuators <NUM>-<NUM> can communicate with AHU controller <NUM> via communications links <NUM>-<NUM>. Actuators <NUM>-<NUM> can receive control signals from AHU controller <NUM> and can provide feedback signals to controller <NUM>. In some embodiments, AHU controller <NUM> receives a measurement of the supply air temperature from a temperature sensor <NUM> positioned in supply air duct <NUM> (e.g., downstream of cooling coil <NUM> and/or heating coil <NUM>). AHU controller <NUM> can also receive a measurement of the temperature of building zone <NUM> from a temperature sensor <NUM> located in building zone <NUM>.

In some embodiments, AHU controller <NUM> operates valves <NUM> and <NUM> via actuators <NUM>-<NUM> to modulate an amount of heating or cooling provided to supply air <NUM> (e.g., to achieve a setpoint temperature for supply air <NUM> or to maintain the temperature of supply air <NUM> within a setpoint temperature range). The positions of valves <NUM> and <NUM> affect the amount of heating or cooling provided to supply air <NUM> by cooling coil <NUM> or heating coil <NUM> and may correlate with the amount of energy consumed to achieve a desired supply air temperature. AHU controller <NUM> can control the temperature of supply air <NUM> and/or building zone <NUM> by activating or deactivating coils <NUM>-<NUM>, adjusting a speed of fan <NUM>, or a combination of both.

Still referring to <FIG>, airside system <NUM> is depicted to include a building management system (BMS) controller <NUM> and a client device <NUM>. BMS controller <NUM> 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 for airside system <NUM>, waterside system <NUM>, HVAC system <NUM>, and/or other controllable systems that serve building <NUM>. BMS controller <NUM> can communicate with multiple downstream building systems or subsystems (e.g., HVAC system <NUM>, a security system, a lighting system, waterside system <NUM>, etc.) via a communications link <NUM> according to like or disparate protocols (e.g., LON, BACnet, etc.). In various embodiments, AHU controller <NUM> and BMS controller <NUM> can be separate (as depicted in <FIG>) or integrated. In an integrated implementation, AHU controller <NUM> can be a software module configured for execution by a processor of BMS controller <NUM>.

In some embodiments, AHU controller <NUM> receives information from BMS controller <NUM> (e.g., commands, setpoints, operating boundaries, etc.) and provides information to BMS controller <NUM> (e.g., temperature measurements, valve or actuator positions, operating statuses, diagnostics, etc.). For example, AHU controller <NUM> can provide BMS controller <NUM> with temperature measurements from temperature sensors <NUM>-<NUM>, equipment on/off states, equipment operating capacities, and/or any other information that can be used by BMS controller <NUM> to monitor or control a variable state or condition within building zone <NUM>.

Client device <NUM> can include one or more human-machine interfaces or client interfaces (e.g., graphical user interfaces, reporting interfaces, text-based computer interfaces, client-facing web services, web servers that provide pages to web clients, etc.) for controlling, viewing, or otherwise interacting with HVAC system <NUM>, its subsystems, and/or devices. Client device <NUM> can be a computer workstation, a client terminal, a remote or local interface, or any other type of user interface device. Client device <NUM> can be a stationary terminal or a mobile device. For example, client device <NUM> can be a desktop computer, a computer server with a user interface, a laptop computer, a tablet, a smartphone, a PDA, or any other type of mobile or non-mobile device. Client device <NUM> can communicate with BMS controller <NUM> and/or AHU controller <NUM> via communications link <NUM>.

Referring now to <FIG>, a block diagram of a building management system (BMS) <NUM> is depicted. BMS <NUM> can be implemented in building <NUM> to automatically monitor and control various building functions. BMS <NUM> is depicted to include BMS controller <NUM> and a plurality of building subsystems <NUM>. Building subsystems <NUM> are depicted to include a building electrical subsystem <NUM>, an information communication technology (ICT) subsystem <NUM>, a security subsystem <NUM>, a HVAC subsystem <NUM>, a lighting subsystem <NUM>, a lift/escalators subsystem <NUM>, and a fire safety subsystem <NUM>. Building subsystems <NUM> can 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 control building <NUM>. In some embodiments, building subsystems <NUM> include waterside system <NUM> and/or airside system <NUM>, as described with reference to <FIG>.

Each of building subsystems <NUM> can include any number of devices, controllers, and connections for completing its individual functions and control activities. HVAC subsystem <NUM> can include many of the same components as HVAC system <NUM>, as described with reference to <FIG>. For example, HVAC subsystem <NUM> 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 building <NUM>. Lighting subsystem <NUM> can include any number of light fixtures, ballasts, lighting sensors, dimmers, or other devices that can controllably adjust the amount of light provided to a building space. Security subsystem <NUM> can include occupancy sensors, video surveillance cameras, digital video recorders, video processing servers, intrusion detection devices, access control devices and servers, or other security-related devices.

Still referring to <FIG>, BMS controller <NUM> is depicted to include a communications interface <NUM> and a BMS interface <NUM>. Interface <NUM> can facilitate communications between BMS controller <NUM> and external applications (e.g., monitoring and reporting applications <NUM>, enterprise control applications <NUM>, remote systems and applications <NUM>, applications residing on client devices <NUM>, etc.) for allowing user control, monitoring, and adjustment to BMS controller <NUM> and/or subsystems <NUM>. Interface <NUM> can also facilitate communications between BMS controller <NUM> and client devices <NUM>. BMS interface <NUM> can facilitate communications between BMS controller <NUM> and building subsystems <NUM> (e.g., HVAC, lighting security, lifts, power distribution, business, etc.).

Interfaces <NUM>, <NUM> can be or include wired or wireless communications interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wire terminals, etc.) for conducting data communications with building subsystems <NUM> or other external systems or devices. In various embodiments, communications via interfaces <NUM>, <NUM> can be direct (e.g., local wired or wireless communications) or via a communications network <NUM> (e.g., a WAN, the Internet, a cellular network, etc.). For example, interfaces <NUM>, <NUM> can include an Ethernet card and port for sending and receiving data via an Ethernet-based communications link or network. In another example, interfaces <NUM>, <NUM> can include a WiFi transceiver for communicating via a wireless communications network. In another example, one or both of interfaces <NUM>, <NUM> can include cellular or mobile phone communications transceivers. In one embodiment, communications interface <NUM> is a power line communications interface and BMS interface <NUM> is an Ethernet interface. In some embodiments, both communications interface <NUM> and BMS interface <NUM> are Ethernet interfaces or are the same Ethernet interface.

Still referring to <FIG>, BMS controller <NUM> is depicted to include a processing circuit <NUM> including a processor <NUM> and memory <NUM>. Processing circuit <NUM> can be communicably connected to BMS interface <NUM> and/or communications interface <NUM> such that processing circuit <NUM> and the various components thereof can send and receive data via interfaces <NUM>, <NUM>. Processor <NUM> 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.

Memory <NUM> (e.g., memory, memory unit, storage device, etc.) can include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage, etc.) for storing data and/or computer code for completing or facilitating the various processes, layers and modules described in the present application. Memory <NUM> can be or include volatile memory or non-volatile memory. Memory <NUM> can include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present application. According to an embodiment, memory <NUM> is communicably connected to processor <NUM> via processing circuit <NUM> and includes computer code for executing (e.g., by processing circuit <NUM> and/or processor <NUM>) one or more processes described herein.

In some embodiments, BMS controller <NUM> is implemented within a single computer (e.g., one server, one housing, etc.). In various embodiments BMS controller <NUM> can be distributed across multiple servers or computers (e.g., that can exist in distributed locations). Further, while <FIG> shows applications <NUM> and <NUM> as existing outside of BMS controller <NUM>, in some embodiments, applications <NUM> and <NUM> can be hosted within BMS controller <NUM> (e.g., within memory <NUM>).

Still referring to <FIG>, memory <NUM> is depicted to include an enterprise integration layer <NUM>, an automated measurement and validation (AM&V) layer <NUM>, a demand response (DR) layer <NUM>, a fault detection and diagnostics (FDD) layer <NUM>, an integrated control layer <NUM>, and a building subsystem integration later <NUM>. Layers <NUM>-<NUM> can receive inputs from building subsystems <NUM> and other data sources, determine optimal control actions for building subsystems <NUM> based on the inputs, generate control signals based on the optimal control actions, and provide the generated control signals to building subsystems <NUM>. The following paragraphs describe some of the general functions performed by each of layers <NUM>-<NUM> in BMS <NUM>.

Enterprise integration layer <NUM> can be serve clients or local applications with information and services to support a variety of enterprise-level applications. For example, enterprise control applications <NUM> can provide subsystem-spanning control to a graphical user interface (GUI) or to any number of enterprise-level business applications (e.g., accounting systems, user identification systems, etc.). Enterprise control applications <NUM> can provide configuration GUIs for configuring BMS controller <NUM>. In some embodiments, enterprise control applications <NUM> can work with layers <NUM>-<NUM> to optimize building performance (e.g., efficiency, energy use, comfort, or safety) based on inputs received at interface <NUM> and/or BMS interface <NUM>.

Building subsystem integration layer <NUM> can be manage communications between BMS controller <NUM> and building subsystems <NUM>. For example, building subsystem integration layer <NUM> can receive sensor data and input signals from building subsystems <NUM> and provide output data and control signals to building subsystems <NUM>. Building subsystem integration layer <NUM> can also manage communications between building subsystems <NUM>. Building subsystem integration layer <NUM> translate communications (e.g., sensor data, input signals, output signals, etc.) across a plurality of multi-vendor/multi-protocol systems.

Demand response layer <NUM> can optimize resource usage (e.g., electricity use, natural gas use, water use, etc.) and/or the monetary cost of such resource usage in response to satisfy the demand of building <NUM>. The optimization can be based on time-of-use prices, curtailment signals, energy availability, or other data received from utility providers, distributed energy generation systems <NUM>, from energy storage <NUM> (e.g., hot TES <NUM>, cold TES <NUM>, etc.), or from other sources. Demand response layer <NUM> can receive inputs from other layers of BMS controller <NUM> (e.g., building subsystem integration layer <NUM>, integrated control layer <NUM>, 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 embodiment, demand response layer <NUM> includes control logic for responding to the data and signals it receives. These responses can include communicating with the control algorithms in integrated control layer <NUM>, changing control strategies, changing setpoints, or activating/deactivating building equipment or subsystems in a controlled manner. Demand response layer <NUM> can also include control logic to determine when to utilize stored energy. For example, demand response layer <NUM> can determine to begin using energy from energy storage <NUM> just prior to the beginning of a peak use hour.

In some embodiments, demand response layer <NUM> includes a control module that can actively initiate control actions (e.g., automatically changing setpoints) which minimize energy costs based on one or more inputs representative of or based on demand (e.g., price, a curtailment signal, a demand level, etc.). In some embodiments, demand response layer <NUM> uses equipment models to determine an optimal set of control actions. The equipment models can include, for example, thermodynamic models describing the inputs, outputs, and/or functions performed by various sets of building equipment. Equipment models can represent collections of building equipment (e.g., subplants, chiller arrays, etc.) or individual devices (e.g., individual chillers, heaters, pumps, etc.).

Demand response layer <NUM> can further include or draw upon one or more demand response policy definitions (e.g., databases, XML files, etc.). The policy definitions can be edited or adjusted by a user (e.g., via a graphical user interface) so that the control actions initiated in response to demand inputs can be tailored for the user's application, desired comfort level, particular building equipment, or based on other concerns. For example, the demand response policy definitions can specify which equipment can be turned on or off in response to particular demand inputs, how long a system or piece of equipment should be turned off, what setpoints can be changed, what the allowable set point adjustment range is, how long to hold a high demand setpoint before returning to a normally scheduled setpoint, how close to approach capacity limits, which equipment modes to utilize, the energy transfer rates (e.g., the maximum rate, an alarm rate, other rate boundary information, etc.) into and out of energy storage devices (e.g., thermal storage tanks, battery banks, etc.), and when to dispatch on-site generation of energy (e.g., via fuel cells, a motor generator set, etc.).

Integrated control layer <NUM> can use the data input or output of building subsystem integration layer <NUM> and/or demand response later <NUM> to make control decisions. Due to the subsystem integration provided by building subsystem integration layer <NUM>, integrated control layer <NUM> can integrate control activities of the subsystems <NUM> such that the subsystems <NUM> behave as a single integrated supersystem. In an embodiment, integrated control layer <NUM> includes control logic that uses inputs and outputs from a plurality of building subsystems to provide greater comfort and energy savings relative to the comfort and energy savings that separate subsystems could provide alone. For example, integrated control layer <NUM> can use an input from a first subsystem to make an energy-saving control decision for a second subsystem. Results of these decisions can be communicated back to building subsystem integration layer <NUM>.

Integrated control layer <NUM> is depicted to be logically below demand response layer <NUM>. Integrated control layer <NUM> can enhance the effectiveness of demand response layer <NUM> by enabling building subsystems <NUM> and their respective control loops to be controlled in coordination with demand response layer <NUM>. This configuration can reduce disruptive demand response behavior relative to conventional systems. For example, integrated control layer <NUM> can assure that a demand response-driven upward adjustment to the setpoint for chilled water temperature (or another component that directly or indirectly affects temperature) does not result in an increase in fan energy (or other energy used to cool a space) that would result in greater total building energy use than was saved at the chiller.

Integrated control layer <NUM> can provide feedback to demand response layer <NUM> so that demand response layer <NUM> checks that constraints (e.g., temperature, lighting levels, etc.) are properly maintained even while demanded load shedding is in progress. The constraints can also include setpoint or sensed boundaries relating to safety, equipment operating limits and performance, comfort, fire codes, electrical codes, energy codes, and the like. Integrated control layer <NUM> is also logically below fault detection and diagnostics layer <NUM> and automated measurement and validation layer <NUM>. Integrated control layer <NUM> can provide calculated inputs (e.g., aggregations) to these higher levels based on outputs from more than one building subsystem.

Automated measurement and validation (AM&V) layer <NUM> can verify that control strategies commanded by integrated control layer <NUM> or demand response layer <NUM> are working properly (e.g., using data aggregated by AM&V layer <NUM>, integrated control layer <NUM>, building subsystem integration layer <NUM>, FDD layer <NUM>, or otherwise). The calculations made by AM&V layer <NUM> can be based on building system energy models and/or equipment models for individual BMS devices or subsystems. For example, AM&V layer <NUM> can compare a model-predicted output with an actual output from building subsystems <NUM> to determine an accuracy of the model.

Fault detection and diagnostics (FDD) layer <NUM> can provide on-going fault detection for building subsystems <NUM>, building subsystem devices (i.e., building equipment), and control algorithms used by demand response layer <NUM> and integrated control layer <NUM>. FDD layer <NUM> can receive data inputs from integrated control layer <NUM>, directly from one or more building subsystems or devices, or from another data source. FDD layer <NUM> 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 that can attempt to repair the fault or to work-around the fault.

FDD layer <NUM> can output a specific identification of the faulty component or cause of the fault (e.g., loose damper linkage) using detailed subsystem inputs available at building subsystem integration layer <NUM>. In some embodiments, FDD layer <NUM> can provide "fault" events to integrated control layer <NUM> which executes control strategies and policies in response to the received fault events. According to an embodiment, FDD layer <NUM> (or a policy executed by an integrated control engine or business rules engine) can shut-down systems or direct control activities around faulty devices or systems to reduce energy waste, extend equipment life, or assure proper control response.

FDD layer <NUM> can store or access a variety of different system data stores (or data points for live data). FDD layer <NUM> can use some content of the data stores to identify faults at the equipment level (e.g., specific chiller, specific AHU, specific terminal unit, etc.) and other content to identify faults at component or subsystem levels. For example, building subsystems <NUM> can generate temporal (i.e., time-series) data indicating the performance of BMS <NUM> and the various components thereof. The data generated by building subsystems <NUM> can include measured or calculated values that exhibit statistical characteristics and provide information about how the corresponding system or process (e.g., a temperature control process, a flow control process, etc.) is performing in terms of error from its setpoint. These processes can be examined by FDD layer <NUM> to expose when the system begins to degrade in performance and alert a user to repair the fault before it becomes more severe.

Referring now to <FIG>, a block diagram of an occupant feedback system <NUM> is depicted. In various embodiments, system <NUM> may be a subsystem of any of the systems described above with reference to <FIG>, including HVAC system <NUM>, waterside system <NUM>, airside system <NUM>, and BMS <NUM>.

The system <NUM> is depicted to include a supervisory or BAS controller <NUM>, location service devices <NUM>, field controllers <NUM>, client devices <NUM>, a ledger system <NUM>, and administration and reporting devices <NUM>. One or more of the components of system <NUM> may be communicably coupled using network <NUM>. Network <NUM> can be any kind of network such as the Internet, TCP/IP, Ethernet, LAN, WAN, Wi-Fi, Zigbee, BACnet, <NUM>, LTE, Li-Fi, and/or any combination thereof.

The supervisory controller <NUM> can be identical or substantially similar to BMS controller <NUM>, described above with reference to <FIG>. In some embodiments, controller <NUM> can to perform functions related to the solicitation of occupant feedback and the performance of control functions to modify environmental conditions of the building according to the occupant feedback received. For example, in some embodiments, controller <NUM> can perform a process <NUM> to capture occupant feedback, described in greater detail below with reference to <FIG>. Occupant feedback can include feedback regarding environmental conditions of the building space. Occupant feedback can include indications of a comfort level corresponding to the environmental conditions. The supervisory controller <NUM> can determine the occupant feedback can include a quantitative value mapped to a qualitive feedback (e.g., "too hot" can be mapped to a relatively high value, such as a value greater than an average value of a discrete or continuous range of values). Occupant feedback can relate to environmental conditions such as temperature, humidity, and cleanliness.

The supervisory controller <NUM> can calculate a weighted average of the occupant feedback. For example, the supervisory controller <NUM> can assign a weight to each occupant feedback value, and calculate the weighted average based on each weighted occupant feedback value. In some embodiments, the supervisory controller <NUM> assigns the weight based on a credibility corresponding to the occupant from which the occupant feedback was received. The supervisory controller <NUM> can maintain a credibility database (e.g., ledger system <NUM>, described in further detail below) assigning a credibility to each occupant, and can retrieve the credibility corresponding to the occupant from which the occupant feedback was received from the credibility database. The supervisory controller <NUM> can retrieve the credibility using an identifier of the occupant (e.g., the occupant's name, an occupant ID number, an occupant device serial number) mapped to the occupant in the credibility database; the identifier may be received with the occupant feedback, and may include an identifier of the occupant itself and/or an identifier of the client device <NUM> expected to correspond to the occupant.

The supervisory controller <NUM> can determine whether the occupant feedback indicates that the environmental conditions of the building meet one or more corresponding building criteria. The building criteria may correspond to whether the occupant feedback indicates the building space is comfortable. For example, the supervisory controller <NUM> can compare the occupant feedback (e.g., a weighted average of the occupant feedback) to a target value, and determine that the occupant feedback indicates that the environmental conditions of the building space are not comfortable responsive to a difference between the occupant feedback and the target value, determined based on the comparison, is greater than a threshold difference.

The supervisory controller <NUM> generates commands to modify the environmental conditions of the building space responsive to the occupant feedback, such as if the supervisory controller <NUM> determines the occupant feedback to indicate that the environmental conditions of the building space are not comfortable. The supervisory controller <NUM> can evaluate an operating condition of the field controller(s) <NUM> based on the occupant feedback, and modify operation of the field controller(s) <NUM> based on the evaluation. For example, the operating condition may include whether the field controller(s) <NUM> are functioning to modify an environmental parameter (e.g., temperature) relative to a predetermined setpoint of the environmental parameter (e.g., target setpoint of room temperature, such as <NUM> degrees Fahrenheit, for the building space). Responsive to determining that (<NUM>) the field controller(s) <NUM> are not modifying the environmental parameter and (<NUM>) the occupant feedback indicates that the environmental conditions are not comfortable, the supervisory controller <NUM> can cause the field controller(s) <NUM> to adjust the predetermined setpoint. For example, if the supervisory controller <NUM> determines the occupant feedback to indicate that the building space is too hot (or too cold), the supervisory controller <NUM> can cause the field controller(s) <NUM> to adjust a respective temperature setpoint to be lower (or higher), such as to cause the field controller(s) <NUM> to cool the building at relatively higher temperatures (or cool the building at relatively lower temperatures).

In some embodiments, the supervisory controller <NUM> generates commands based on a count of occupant feedback, such as by comparing the count of occupant feedback to a threshold count (which may be a function of a total number of occupants) and generating commands to modify operation of field controller(s) <NUM> and/or HVAC devices responsive to the count exceeding the threshold count. The supervisory controller <NUM> can further determine if a majority of the occupants in a building space provide feedback indicating that the space is uncomfortable. For example, if there are ten occupants in a building space and six of those occupants provide feedback to the supervisory controller <NUM> indicating that the building space is thermally uncomfortable, the supervisory controller <NUM> transmits control signals to operate HVAC devices within the building space (e.g., fans, cooling coils) to reduce the temperature of building space. In some embodiments, the control signals could include modifying a temperature setpoint used in a temperature control algorithm for the HVAC devices.

The supervisory controller <NUM> can generate commands to modify the environmental conditions of the building space based on the severity of the feedback. For example, if, in a building space of ten occupants, two occupants report mild thermal discomfort (which can be mapped to a lower quantitative value) and two occupants report severe thermal discomfort (which can be mapped to a higher quantitative value), the presence of multiple occupants indicating severe discomfort can prompt the supervisory controller <NUM> to transmit control signals to reduce the temperature of the building space. The credibility assigned to the occupant in the credibility database can affect whether a minority of occupants in a building space cause the supervisory controller <NUM> to generate commands to modify the environmental conditions of the building space. Returning to the previous example, if one of the two occupants reporting severe thermal discomfort has a history of providing anomalous and/or suspect feedback when compared with other occupants, the supervisory controller <NUM> can assign a weighting factor to minimize the impact of that occupant's feedback in the weighted average of the occupant feedback. When the supervisory controller <NUM> compares the weighted occupant feedback average to the target value, the presence of the suspect occupant feedback in the weighted average can result in the difference between the average and the target value not exceeding the threshold difference, meaning that the supervisory controller <NUM> does not transmit control signals to modify the temperature of the building space.

The supervisory controller <NUM> can capture feedback from occupants subsequent to generating control signals to modify the environmental conditions of the building space. For example, if the supervisory controller <NUM> transmits control signals to reduce the temperature of the building space, the supervisory controller <NUM> can capture additional feedback from occupants after a specified period of time, or once a thermostat or a sensor located in the building space indicate that the temperature has dropped. If a majority of occupants provide feedback indicating that the building space is now thermally comfortable, the supervisory controller <NUM> can transmit additional control signals to maintain the building space at the current temperature and halt additional cooling. Conversely, if a majority of occupants provide feedback indicating that the building space is still thermally uncomfortable, the supervisory controller <NUM> can transmit control signals to increase cooling to the building space.

The location service devices <NUM> can detect and count the number of occupants within a building space using any suitable method (e.g., cameras, infrared sensors, motion sensors). In some embodiments, the location service devices <NUM> can detect occupants through detection of the presence of occupant devices and can communicate with the occupant devices using Bluetooth Low Energy (BLE) methods. In still further embodiments, the location service devices <NUM> can be devices implemented as part of a Qualcomm Glance system.

The field controllers <NUM> can include various devices located throughout the building that are configured to control subsystems and devices that affect the environmental conditions of the building space. For example, the field controllers <NUM> can control devices and systems including, but not limited to chillers, boilers, rooftop AHUs, VAV units, economizers, heating coils, cooling coils, fans, pumps, valves, and dampers. The field controllers <NUM> control the devices and systems responsive to commands received from the supervisory controller <NUM>. For example, based on control signals received from the supervisory controller <NUM>, the field controllers <NUM> could perform tasks including, but not limited to, modifying an operating load of a chiller or boiler, changing a fan speed, or opening or closing a valve or damper.

The client device(s) <NUM> can be any of various electronic devices, particularly portable electronic devices associated with occupants of a space, such as smartphones or tablets. In some embodiments, the client device <NUM> could also include a smartwatch or other wearable device. The client device <NUM> can include a user interface including a display device and a user input device (not depicted). The client device <NUM> can include a processing circuit including a processor and memory (not depicted).

The client device <NUM> can use the processing circuit to execute an application (APP) <NUM>, such as to execute functions described in further detail with reference to <FIG> and <FIG> below. The APP <NUM> can be an occupant feedback application. In some embodiments, the client device <NUM> can establish a communication link with the BAS controller <NUM> and/or other devices of the system <NUM> via the network <NUM>.

Upon initial launching of the APP <NUM>, the occupant can be presented with a screen requesting that they register to use the APP <NUM>. Registration can include creating a username and password and supplying some basic personal information such as, for example, name and email address. If the occupant works in the building, the personal information can include the occupant's employer and/or department details regarding the building space where the occupant works. Registration information associated with the occupant can be stored in a database accessible by the network <NUM>, for example, the ledger system <NUM>.

A blockchain or immutable ledger of the ledger system <NUM> can maintain or utilize a distributed data chain among a plurality of devices. The plurality of devices can communicate via a network such as a TCP/IP network. In various embodiments, the blockchain <NUM> does not include any kind of central server and/or does not rely on a central server to operate. Rather, the plurality of devices can each store a copy of a data chain that includes information that can be distributed among all of the devices.

The data chain can be a chain of multiple blocks. The ledger system <NUM> links each block to a previous block based on a hash value. The hash value of a particular block relies on the hash of the previous block and the data inside the particular block. Since the blocks are linked in this way, changes to a block in the chain changes that block's hash which breaks the link between blocks. Each of the blocks in the data chain includes a digital signature that can be used to verify that the block is authentic, that is, that the data of the block was created by the device that claims to have created the data. As more blocks are added to the data chain, it becomes exponentially more difficult to compromise the data chain.

Hash functions generate the hash values linking blocks together. Hash functions are not reversible, that is, one cannot predict the output of a hash function of a given input. A hash solution for a block is generated by repeatedly hashing an adjustable value in the block called a nonce, the hash value of a previous block in the data chain, and the data to be added to the data chain. A hash that meets a difficulty criterion is considered a solution to the block and can be added to the data chain. In some embodiments, the difficulty criteria is a hash value that is less than a predefined amount or more than a predefined amount. A device using the data chain receives requests to add new blocks to the data chain from services, devices, or other entities in the system. The device can add the block to the data chain by generating a hash solution. This method may be known as proof of work.

The unpredictable nature of the hash function makes it difficult for a device to find a random input that produces a valid hash of the block. In some cases, depending on the difficulty criterion, it can take trillions of different trials trying nonce values until a valid hash is found. This can make it difficult to change data in a block of the data chain. By distributing the blocks on the network, the disadvantage of having a single point of failure is eliminated and the network is tolerant to hacking attacks at a single node of the network.

In some embodiments, the ledger system <NUM> maintains records of occupants within the spaces of a building. For example, each occupant record can include a credibility rating or weighting factor associated with the occupant. The credibility rating or weighting factor can be assigned to the occupant based on the veracity of the occupant's feedback over time. For example, if a particular occupant consistently provides anomalous feedback when compared with the feedback provided by the other occupants of a space, the credibility rating or weighting factor associated with the occupant may be adjusted so that the occupant's feedback has a smaller effect on the aggregate feedback generated by all occupants of a space. Further details regarding the use of credibility ratings and weighting factors are included below with reference to <FIG>.

In some embodiments, the ledger system <NUM> can maintain records of work requests generated based on occupant feedback. For example, multiple occupants may provide feedback indicating that a building space has insufficient lighting. In some embodiments, this feedback can include pictures of the space taken by the occupants to demonstrate the need for additional lighting. In response to the occupant feedback, a building supervisor may generate a work request to install additional lighting in the building space. Completion of the work request can be tracked and stored on the ledger system <NUM>. Similar work requests can be generated and stored on the ledger system <NUM> in response to occupant feedback regarding the cleanliness of a building space, the security of a building space, or any other condition of the building.

Still referring to <FIG>, system <NUM> is additionally depicted to include administration and reporting devices <NUM>. In various embodiments, administration and reporting devices <NUM> can include a desktop computer, a smartphone, or a tablet computer. Administration and reporting devices <NUM> can perform a variety of tasks related to data analysis, reporting, building visualization and workflow. For example, administration and reporting devices <NUM> can be configured to run or access reporting programs to track the trends of occupant feedback over time. Through access to historical occupant feedback reports, building administrators can perform tasks such as energy forecasting and investing planning. In still further embodiments, administration and reporting devices <NUM> can be configured to display a real time dashboard of the status of the system <NUM>. For example, the dashboard could be configured to display alerts when a device within the system <NUM> is experiencing a fault condition. The dashboard could also be used to configure various parameters within the system <NUM> (e.g., notification message settings, delay periods, occupant detection settings).

Turning now to <FIG>, a user interface <NUM> of an occupant feedback APP is depicted. The APP may be downloaded onto an occupant device by an occupant of a space within a building. In various embodiments, the occupant device can be client device <NUM> and the occupant feedback APP can be APP <NUM>, both described above with reference to <FIG>.

The occupant can download the APP onto a mobile device before or upon entering the building. For example, signage located at the entryways of the building may prompt the occupant to download the APP. In some embodiments, a notification message transmitted to the occupant device upon detection of the occupant within the building can include a hyperlink to download the APP. In still further embodiments, the APP is cloud-based and accessible using an internet browser rather than a program downloaded to the occupant's device.

The user interface <NUM> is depicted to include, among other components, a central feedback selection wheel <NUM>, an outer feedback selection wheel <NUM>, a feedback selection confirmation bar <NUM>, and a navigation bar <NUM>. The central feedback selection wheel <NUM> can permit an occupant to assign a quality rating to a condition of a space. For example, the condition can be overall comfort level, temperature, humidity, air freshness, cleanliness, security, adequacy of lighting, or any other condition that may be associated with a space. In some embodiments, the central feedback selection wheel <NUM> can include a continuous gradient of colors representing the occupant's quality rating regarding the condition. For example, in some embodiments, a green selection can indicate a comfortable condition, a yellow or orange selection can indicate a slightly warmer than comfortable condition, a red selection can indicate a much warmer than comfortable condition, and a purple or blue selection can indicate a much colder than comfortable condition.

In some embodiments, the central feedback selection wheel <NUM> can include a discrete number of colored segments rather than a gradient of colors. In still further embodiments, the central feedback selection wheel <NUM> does not utilize colors to represent the occupant's quality rating regarding the condition. Instead, the selection wheel <NUM> can utilize a numerical scale (e.g., a scale of <NUM>-<NUM>, with a <NUM> selection indicating a fully comfortable condition and a <NUM> selection indicating a fully uncomfortable condition). In further embodiments, the selection wheel <NUM> can utilize emoticons or other images (e.g., a happy face selection indicating a comfortable condition, a sad face selection indicating an uncomfortable condition).

The occupant can assign a quality rating from the central feedback selection wheel <NUM> using the central wheel selector <NUM>. In some embodiments, an occupant can drag and rotate the central wheel selector <NUM> about the central feedback selection wheel <NUM> until the occupant's desired quality rating is contained within the selector <NUM>. In some embodiments, the central wheel selector <NUM> is stationary and the occupant can drag and rotate the central feedback selection wheel <NUM> until the occupant's desired quality rating is contained within the selector <NUM>.

In some embodiments, the central wheel selector <NUM> can highlight multiple colors/numbers/images of the central feedback selection wheel <NUM> simultaneously. For example, as depicted in <FIG>, the central wheel selector <NUM> can include a larger central portion flanked by smaller portions on either side to enable selection of up to five colors from the central feedback selection wheel <NUM> simultaneously. In some embodiments, the central wheel selector <NUM> can enable the selection of a different number of colors from the central feedback selection wheel <NUM> simultaneously (e.g., three colors, seven colors).

The colors highlighted by the central feedback selection wheel <NUM> can be replicated in the feedback selection confirmation bar <NUM>. For example, as depicted in <FIG>, when the central wheel selector <NUM> is configured to highlight five colors simultaneously from the central feedback selection wheel <NUM>, the same five colors can be replicated in the feedback selection confirmation bar <NUM>. In some embodiments, the occupant can slide the confirmation bar selector <NUM> along the confirmation bar <NUM> to confirm the occupant's quality rating selection. Enabling the occupant a second means to consider and confirm the assigned quality rating can ensure thoughtfulness and a high caliber of feedback solicited from occupants.

The outer feedback selection wheel <NUM> can permit an occupant of a space to provide a quality rating to a different building space condition than the condition rated using the central feedback selection wheel <NUM>. In some embodiments, the conditions rated using the selection wheels <NUM> and <NUM> can be related. For example, if the central feedback selection wheel <NUM> is configured to permit an occupant to assign a quality rating to a thermal comfort condition, the outer feedback selection wheel <NUM> can be used to permit an occupant to assign a quality rating to an air freshness condition. Similar to the central feedback selection wheel <NUM>, the outer feedback selection wheel <NUM> can include a continuous gradient of colors, a discrete number of color segments, numbers, icons, pictures, or any other means of representing a quality selection. In some embodiments, assignment of a quality rating can be achieved by the occupant rotating the outer feedback selection wheel <NUM> until the color, image, or number representative of the occupant's quality rating is contained within outer wheel selector <NUM>. In some embodiments, assignment of the quality rating is achieved by the occupant rotating the outer wheel selector <NUM> about the outer feedback selection wheel <NUM> until the desired quality rating is contained within outer wheel <NUM>.

The navigation bar <NUM> can include any buttons, icons, hyperlinks, controls etc. required to navigate within the user interface <NUM>. For example, as depicted in <FIG>, the navigation bar <NUM> can include a check mark used to confirm the occupant's selection of one or more quality ratings, while an "X" can be used to cancel the occupant's selection of one or more quality ratings. The navigation bar <NUM> can further include buttons, etc. to navigate between the various user interface screens of the APP. For example, as depicted in <FIG>, the navigation bar <NUM> can include a back arrow used to navigate away from the user interface <NUM> to a main menu screen or a previous menu screen.

<FIG> depicts a possible user interface <NUM> for providing occupant feedback through the APP; many user interfaces configurations can be utilized by the APP to gather occupant feedback regarding the conditions of a building space. For example, one user interface of the APP could access a camera of the mobile device and permit an occupant to take a picture of a building space to provide feedback regarding the cleanliness or adequacy of lighting in a building space.

User interface configurations could include text boxes that permit an occupant to enter comments regarding a building space. In further embodiments, the APP can directly access sensors integrated into the mobile device (e.g., temperature, light, humidity) to passively gather data regarding the conditions of a building space without the need for active input from the occupant.

Referring now to <FIG>, a computer-implemented method <NUM> for capturing occupant feedback is depicted according to an embodiment of the present disclosure. The method <NUM> may be performed by various systems and devices disclosed herein. For example, the method <NUM> can be performed primarily by a supervisory device (e.g., the BAS controller <NUM> of the system <NUM>).

At <NUM>, the supervisory device (e.g., the BAS controller <NUM>) detects the presence of an occupant within a space. In some embodiments, the supervisory device communicates with dedicated occupant tracking devices (e.g., location service devices <NUM>) in order to detect the presence of one or more occupants within a space via detection of an occupant device. For example, an occupant tracking device can detect a Bluetooth signal emanating from an occupant device (e.g., client device <NUM>). In some embodiments, the occupant tracking devices can detect the presence of occupants using cameras, infrared sensors, or any other suitable method.

At <NUM>, the supervisory device begins a notification delay timer. The notification delay timer permits an occupant time to observe and become acclimated to the environmental conditions of a building space. Put another way, the occupant might be likely to ignore or provide inaccurate feedback if prompted to provide feedback immediately upon entering a building space. By including the notification delay timer, the quality of feedback received from occupants is thereby improved. In various embodiments, the notification delay timer can be configurable. For example, the notification delay timer can be configured to run for a delay period of five minutes, ten minutes, thirty minutes, or any other period before making an attempt to solicit occupant feedback.

At <NUM>, the supervisory device determines whether the notification delay timer has elapsed. If the supervisory device determines that the notification delay timer has not elapsed, method <NUM> reverts to step <NUM> and the notification delay timer continues to run until the configurable delay period has elapsed. If, however, the supervisory device determines that the notification timer has elapsed, method <NUM> proceeds to step <NUM>.

At <NUM>, the supervisory device transmits a notification message to the occupant device. In some embodiments, the supervisory device can apply criteria in addition to the notification delay timer to determine whether to transmit a notification message to the occupant device. For example, if the supervisory device has already received a sufficient amount of feedback from other occupants of the building space, the supervisory device can cease to transmit further notification messages. Determination of the sufficiency of the amount of feedback can depend upon multiple factors. These factors can include, but are not limited to, a total number of feedback messages received, a number of high credibility feedback messages received, a size of a building space, or the environmental condition of interest. In some embodiments, the supervisory device can apply location criteria to determine whether to transmit a notification message to the supervisory device. For example, if the occupant tracking devices detect that an occupant is in a low priority building space, the supervisory device may decline to transmit a notification message soliciting feedback from the occupant in the low priority space.

At <NUM>, the supervisory device receives an occupant feedback message from the occupant device. In some embodiments, the occupant feedback message can include one or more occupant-assigned quality ratings regarding the environmental conditions of a building space. Quality ratings can be assigned using the user interface <NUM> of the APP, described above with reference to <FIG>. In some embodiments, the occupant feedback message includes a picture of a building space taken by the occupant, or a comment regarding one or more environmental conditions entered by the occupant into a text box of the APP.

At <NUM>, the supervisory device assigns a weighting factor to the occupant feedback data contained within the occupant feedback message. The credibility rating or weighting factor can be based on an occupant record stored in a database or immutable ledger (e.g., ledger system <NUM>). For example, the credibility rating or weighting factor for an occupant who works in the building can be higher than the credibility rating or weighting factor for an occupant who is an infrequent visitor. In some embodiments, the weighting factor can be dependent on the occupant's feedback history. For example, an occupant who consistently provides anomalous feedback when compared with other occupants of the building (e.g., an occupant who appears to be attempting to maliciously skew the feedback) can have their credibility rating or weighting factor reduced so that the occupant's feedback has a smaller effect on the aggregated occupant feedback data.

At <NUM>, the supervisory device modifies an environmental property of a building space based on aggregated and weighted occupant feedback data. Step <NUM> can encompass a variety of different actions performed by the supervisory device. For example, in some embodiments, step <NUM> can include the supervisory controller transmitting a control message to a field controller (e.g., field controller <NUM>) to modify the operation of one or more HVAC devices. For example, if a number of occupants in a building space provide feedback indicating a negative air freshness condition in the space, the supervisory device can transmit a control message to a fan controller to cause a fan to be operated. In still further embodiments, step <NUM> can include the supervisory controller integrating the aggregated occupant feedback data as an input into a control algorithm. For example, occupant feedback data could be utilized to modify a setpoint (e.g., a temperature setpoint, a humidity setpoint) of a building space.

In further embodiments, step <NUM> can include the creation of a work request to improve an environmental property. In various embodiments, the work request could include cleaning of a particular building space, installation of additional lighting, or installation of security cameras. In still further embodiments, step <NUM> can include the supervisory device transmitting a message to all occupants of a building space. For example, if multiple occupants of a building space provide feedback indicating that the space is too warm to be comfortable, the supervisory device can transmit a message suggesting that the occupants of the space take a break and temporarily leave the space.

Turning now to <FIG>, a computer-implemented method <NUM> for providing occupant feedback is depicted according to an embodiment of the present disclosure. The method <NUM> may be performed by various systems and devices disclosed herein, such as the system <NUM> (e.g., client device <NUM>).

At <NUM>, a notification message is received by the mobile device from a supervisory device (e.g., the BAS controller <NUM>). The notification message can include a request to provide feedback regarding the quality and/or condition of a building space. For example, the notification message can include text that is identical or similar to the following: "Is this room comfortable? Provide feedback now. " The notification message can be displayed on the mobile device in any suitable format. For example, in various embodiments, the notification message can be received and displayed as a mobile device notification, a text message, an email message, or an in-APP message.

At <NUM>, the mobile device opens the occupant feedback APP (e.g., APP <NUM>). In some embodiments, the notification message received at step <NUM> can include a hyperlink to open the feedback APP. In some embodiments, the occupant can open the occupant feedback APP by navigating to the APP from a home screen or application menu.

At <NUM>, the mobile device captures feedback regarding one or more conditions of a space using the occupant feedback APP. In some embodiments, step <NUM> can include an occupant assigning quality ratings to one or more environmental conditions of the building space using a user interface (e.g., user interface <NUM>) of the APP. In some embodiments, step <NUM> can include the occupant taking a picture of a building space, or entering a comment into a text box.

At <NUM>, method <NUM> concludes as an occupant feedback message is transmitted by the mobile device to the supervisory controller. In some embodiments, the occupant feedback message is transmitted by the mobile device as soon as the occupant assigns a quality rating to a building condition. For example, the mobile device may transmit the occupant feedback message as soon as the occupant clicks a button confirming the assignment of one or more quality ratings. In some embodiments, the occupant feedback message is transmitted as soon as the occupant closes the feedback APP, or at specified time intervals. Upon receipt of the occupant feedback message, the supervisory controller may perform various tasks to modify the environmental conditions of the building space. These tasks are described above with reference to step <NUM> of process <NUM>.

The construction and arrangement of the systems and methods as depicted in the various embodiments are illustrative only. Although only example embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.). For example, the position of elements can be reversed or otherwise varied and the nature or number of discrete elements or positions can be altered or varied. Accordingly, such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps can be varied or re-sequenced according to various embodiments. Other substitutions, modifications, changes, and omissions can be made in the design, operating conditions and arrangement of the embodiments without departing from the scope of the present disclosure.

References to "or" may be construed as inclusive so that any terms described using "or" may indicate any of a single, more than one, and all of the described terms. References to at least one of a conjunctive list of terms may be construed as an inclusive OR to indicate any of a single, more than one, and all of the described terms. For example, a reference to "at least one of 'A' and 'B'" can include only 'A', only 'B', as well as both 'A' and 'B'. Such references used in conjunction with "comprising" or other open terminology can include additional items.

The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure may be implemented using existing computer processors, or by a special purpose computer processor for an appropriate system, incorporated for this or another purpose, or by a hardwired system. Embodiments within the scope of the present disclosure include program products comprising machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such machine-readable media can be any available media that can be accessed by a general purpose or special purpose computer or other machine with a processor. By way of example, such machine-readable media can comprise RAM, ROM, EPROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to carry or store desired program code in the form of machine-executable instructions or data structures and which can be accessed by a general purpose or special purpose computer or other machine with a processor. Combinations of the above are also included within the scope of machine-readable media. Machine-executable instructions include, for example, instructions and data which cause a general purpose computer, special purpose computer, or special purpose processing machines to perform a certain function or group of functions.

Although the figures show a specific order of method steps, the order of the steps may differ from what is depicted. Also two or more steps may be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the appended claims. Likewise, software implementations could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps.

Claim 1:
A system (<NUM>) to control building environmental conditions, comprising:
- a controller (<NUM>) to:
- detect an occupant within a building space;
- transmit a notification message, responsive to expiration of a notification delay timer initiated responsive to detection of the occupant, to an occupant device (<NUM>) of the occupant, the notification message comprising a request for occupant feedback;
- receive an occupant feedback message from the occupant device, the occupant feedback message indicative of feedback regarding one or more environmental conditions of the building space;
- weight the feedback with feedback from another occupant; and
- modify an environmental property of the building space based on the weighted feedback.