Patent Publication Number: US-11029654-B2

Title: Building management system with searching using aliased points from equipment definitions

Description:
CROSS-REFERENCE TO RELATED PATENT APPLICATION 
     This application claims the benefit of U.S. Provisional Patent Application No. 62/678,159, filed May 30, 2018, which is incorporated herein by reference in its entirety. This application is also related to (i) U.S. patent application Ser. No. 14/251,414, filed Apr. 11, 2014, now U.S. Pat. No. 9,703,276; (ii) U.S. patent application Ser. No. 15/870,500, filed Jan. 12, 2018, now U.S. Pat. No. 10,644,897; (iii) U.S. patent application Ser. No. 16/100,962, filed Aug. 10, 2018, published as U.S. Patent Publication No. 2019/0052479; and (iv) U.S. patent application Ser. No. 16/406,996, filed May 8, 2019, published as U.S. Patent Publication No. 2020/0358630; all of which are incorporated herein by reference in their entireties. 
    
    
     BACKGROUND 
     The present disclosure relates generally to the field of building management systems. A building management system (BMS) is, in general, a system of devices configured to control, monitor, and manage equipment in or around a building or building area. A BMS can include, for example, an 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. 
     SUMMARY 
     One implementation of the present disclosure is a building management system. The building management system includes (i) one or more building systems including equipment configured to serve one or more spaces in a building and (ii) one or more circuits. The one or more circuits are configured to receive an input to invoke a control strategy to modify a condition of the one or more spaces; define an output of the control strategy where the output relates to a modification that impacts at least one of a location, an equipment type, or a point type; perform a query to identify one or more points associated with the output where the one or more points are defined in terms of at least one of the location, the equipment type, or the point type; and automatically modify one or more values of the one or more points to implement the control strategy. 
     Another implementation of the present disclosure is a building management system. The building management system includes (i) one or more building systems including one or more pieces of equipment configured to serve one or more spaces in a building and (ii) one or more circuits. The one or more circuits are configured to invoke a control strategy following a change in a configuration of at least one of (i) at least one of the one or more spaces or (ii) at least one of the one or more pieces of equipment; perform a query to identify at least one of (i) equipment of the one or more pieces of equipment or (ii) points associated with the equipment that are associated with the change in the configuration; and at least one of (i) automatically modify the points or (ii) automatically operate the equipment based on the change in the configuration to execute the control strategy. 
     Another implementation of the present disclosure is a method for automatically implementing a control strategy. The method includes receiving, by one or more circuits, an input to invoke the control strategy following a change in a configuration of at least one of (i) one or more spaces of a building or (ii) one or more pieces of equipment of the building; performing, by the one or more circuits, a query to identify at least one of (i) equipment of the one or more pieces of equipment or (ii) points associated with the equipment that are associated with the change in the configuration; and at least one of (i) automatically modifying, by the one or more circuits, one or more values of the points or (ii) automatically operating, by the one or more circuits, the equipment based on the change in the configuration to execute the control strategy. 
     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. 
    
    
     
       BRIEF DESCRIPTION OF THE DRAWINGS 
         FIG. 1  is a drawing of a building equipped with a building management system (BMS) and a 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 of  FIG. 1 , according to some embodiments. 
         FIG. 3  is a block diagram of an airside system which can be used as part of the HVAC system of  FIG. 1 , according to some embodiments. 
         FIG. 4  is a block diagram of a BMS which can be used in the building of  FIG. 1 , according to some embodiments. 
         FIG. 5  is a block diagram of a global search and control system, according to some embodiments. 
         FIG. 6A  is an illustration of a search graphical user interface (GUI) provided by the global search and control system of  FIG. 5  having a filter area and a results area, according to some embodiments. 
         FIG. 6B  is an illustration of the search GUI of  FIG. 6A  with an additional equipment definition dropdown menu and aliased point search box and selector, according to some embodiments. 
         FIG. 7  is an illustration of the search GUI of  FIGS. 6A-6B  having search results in the results area, according to some embodiments. 
         FIG. 8  is an illustration of a drop down actions menu of the search GUI of  FIGS. 6A-6B , according to some embodiments. 
         FIG. 9  is an illustration of a bulk command modal window provided over the search GUI of  FIGS. 6A-6B , according to some embodiments. 
         FIG. 10  is an illustration of a report creator modal window provided over the search GUI of  FIGS. 6A-6B , according to some embodiments. 
         FIG. 11  is a flow diagram of a method for performing a global search, according to some embodiments. 
         FIG. 12  is a flow diagram of a method for performing a single command on an item from global search results, according to some embodiments. 
         FIG. 13  is a flow diagram of a method for viewing a network page associated with an item from global search results, according to some embodiments. 
         FIG. 14  is a flow diagram of a method for viewing a space or equipment page associated with an item from global search results, according to some embodiments. 
         FIG. 15  is a flow diagram of a method for generating a report based on global search results, according to some embodiments. 
         FIG. 16  is a flow diagram of a method for performing a bulk command process on a plurality of items from global search results, according to some embodiments. 
         FIG. 17  is an illustration of a bulk command modal window provided over the search GUI of  FIGS. 6A-6B , according to some embodiments. 
         FIG. 18  is an illustration of a future report generation window, according to some embodiments. 
         FIG. 19  is a flowchart of a process for searching using aliased points and equipment definitions, according to some embodiments. 
         FIG. 20  is a flowchart of a process for implementing a control strategy by automatically finding points to be modified by the control strategy, according to some embodiments. 
         FIG. 21  a flowchart of a process for automatically adapting a control strategy to account for a changed configuration of building equipment and/or building spaces, according to some embodiments. 
     
    
    
     DETAILED DESCRIPTION 
     Building Management System and HVAC System 
     Referring now to  FIGS. 1-4 , an example building management system (BMS) and HVAC system in which the systems and methods of the present disclosure can be implemented are shown, according to an example embodiment. Referring particularly to  FIG. 1 , a perspective view of a building  10  is shown. Building  10  is served by a 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 building  10  includes an HVAC system  100 . HVAC system  100  can include a plurality of HVAC devices (e.g., heaters, chillers, air handling units, pumps, fans, thermal energy storage, etc.) configured to provide heating, cooling, ventilation, or other services for building  10 . For example, HVAC system  100  is shown to include a waterside system  120  and an airside system  130 . Waterside system  120  can provide a heated or chilled fluid to an air handling unit of airside system  130 . Airside system  130  can use the heated or chilled fluid to heat or cool an airflow provided to building  10 . An example waterside system and airside system which can be used in HVAC system  100  are described in greater detail with reference to  FIGS. 2 and 3 . 
     HVAC system  100  is shown to include a chiller  102 , a boiler  104 , and a rooftop air handling unit (AHU)  106 . Waterside system  120  can use boiler  104  and chiller  102  to heat or cool a working fluid (e.g., water, glycol, etc.) and can circulate the working fluid to AHU  106 . In various embodiments, the HVAC devices of waterside system  120  can be located in or around building  10  (as shown in  FIG. 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 can be heated in boiler  104  or cooled in chiller  102 , depending on whether heating or cooling is required in building  10 . Boiler  104  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  102  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  102  and/or boiler  104  can be transported to AHU  106  via piping  108 . 
     AHU  106  can place the working fluid in a heat exchange relationship with an airflow passing through AHU  106  (e.g., via one or more stages of cooling coils and/or heating coils). The airflow can be, for example, outside air, return air from within building  10 , or a combination of both. AHU  106  can transfer heat between the airflow and the working fluid to provide heating or cooling for the airflow. For example, AHU  106  can include one or more fans or blowers configured to pass the airflow over or through a heat exchanger containing the working fluid. The working fluid can then return to chiller  102  or boiler  104  via piping  110 . 
     Airside system  130  can deliver the airflow supplied by AHU  106  (i.e., the supply airflow) to building  10  via air supply ducts  112  and can provide return air from building  10  to AHU  106  via air return ducts  114 . In some embodiments, airside system  130  includes multiple variable air volume (VAV) units  116 . For example, airside system  130  is shown to include a separate VAV unit  116  on each floor or zone of building  10 . VAV units  116  can include dampers or other flow control elements that can be operated to control an amount of the supply airflow provided to individual zones of building  10 . In other embodiments, airside system  130  delivers the supply airflow into one or more zones of building  10  (e.g., via supply ducts  112 ) without using intermediate VAV units  116  or other flow control elements. AHU  106  can include various sensors (e.g., temperature sensors, pressure sensors, etc.) configured to measure attributes of the supply airflow. AHU  106  can receive input from sensors located within AHU  106  and/or within the building zone and can adjust the flow rate, temperature, or other attributes of the supply airflow through AHU  106  to achieve setpoint conditions for the building zone. 
     Referring now to  FIG. 2 , a block diagram of a waterside system  200  is shown, according to an example embodiment. In various embodiments, waterside system  200  can supplement or replace waterside system  120  in HVAC system  100  or can be implemented separate from HVAC system  100 . When implemented in HVAC system  100 , waterside system  200  can include a subset of the HVAC devices in HVAC system  100  (e.g., boiler  104 , chiller  102 , pumps, valves, etc.) and can operate to supply a heated or chilled fluid to AHU  106 . The HVAC devices of waterside system  200  can be located within building  10  (e.g., as components of waterside system  120 ) or at an offsite location such as a central plant. 
     In  FIG. 2 , waterside system  200  is shown as a central plant having a plurality of subplants  202 - 212 . Subplants  202 - 212  are shown to include a heater subplant  202 , a heat recovery chiller subplant  204 , a chiller subplant  206 , a cooling tower subplant  208 , a hot thermal energy storage (TES) subplant  210 , and a cold thermal energy storage (TES) subplant  212 . Subplants  202 - 212  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  202  can be configured to heat water in a hot water loop  214  that circulates the hot water between heater subplant  202  and building  10 . Chiller subplant  206  can be configured to chill water in a cold water loop  216  that circulates the cold water between chiller subplant  206  building  10 . Heat recovery chiller subplant  204  can be configured to transfer heat from cold water loop  216  to hot water loop  214  to provide additional heating for the hot water and additional cooling for the cold water. Condenser water loop  218  can absorb heat from the cold water in chiller subplant  206  and reject the absorbed heat in cooling tower subplant  208  or transfer the absorbed heat to hot water loop  214 . Hot TES subplant  210  and cold TES subplant  212  can store hot and cold thermal energy, respectively, for subsequent use. 
     Hot water loop  214  and cold water loop  216  can deliver the heated and/or chilled water to air handlers located on the rooftop of building  10  (e.g., AHU  106 ) or to individual floors or zones of building  10  (e.g., VAV units  116 ). The air handlers push air past heat exchangers (e.g., heating coils or cooling coils) through which the water flows to provide heating or cooling for the air. The heated or cooled air can be delivered to individual zones of building  10  to serve the thermal energy loads of building  10 . The water then returns to subplants  202 - 212  to receive further heating or cooling. 
     Although subplants  202 - 212  are shown and described as heating and cooling water for circulation to a building, it is understood that any other type of working fluid (e.g., glycol, CO2, etc.) can be used in place of or in addition to water to serve the thermal energy loads. In other embodiments, subplants  202 - 212  can provide heating and/or cooling directly to the building or campus without requiring an intermediate heat transfer fluid. These and other variations to waterside system  200  are within the teachings of the present invention. 
     Each of subplants  202 - 212  can include a variety of equipment configured to facilitate the functions of the subplant. For example, heater subplant  202  is shown to include a plurality of heating elements  220  (e.g., boilers, electric heaters, etc.) configured to add heat to the hot water in hot water loop  214 . Heater subplant  202  is also shown to include several pumps  222  and  224  configured to circulate the hot water in hot water loop  214  and to control the flow rate of the hot water through individual heating elements  220 . Chiller subplant  206  is shown to include a plurality of chillers  232  configured to remove heat from the cold water in cold water loop  216 . Chiller subplant  206  is also shown to include several pumps  234  and  236  configured to circulate the cold water in cold water loop  216  and to control the flow rate of the cold water through individual chillers  232 . 
     Heat recovery chiller subplant  204  is shown to include a plurality of heat recovery heat exchangers  226  (e.g., refrigeration circuits) configured to transfer heat from cold water loop  216  to hot water loop  214 . Heat recovery chiller subplant  204  is also shown to include several pumps  228  and  230  configured to circulate the hot water and/or cold water through heat recovery heat exchangers  226  and to control the flow rate of the water through individual heat recovery heat exchangers  226 . Cooling tower subplant  208  is shown to include a plurality of cooling towers  238  configured to remove heat from the condenser water in condenser water loop  218 . Cooling tower subplant  208  is also shown to include several pumps  240  configured to circulate the condenser water in condenser water loop  218  and to control the flow rate of the condenser water through individual cooling towers  238 . 
     Hot TES subplant  210  is shown to include a hot TES tank  242  configured to store the hot water for later use. Hot TES subplant  210  can also include one or more pumps or valves configured to control the flow rate of the hot water into or out of hot TES tank  242 . Cold TES subplant  212  is shown to include cold TES tanks  244  configured to store the cold water for later use. Cold TES subplant  212  can also include one or more pumps or valves configured to control the flow rate of the cold water into or out of cold TES tanks  244 . 
     In some embodiments, one or more of the pumps in waterside system  200  (e.g., pumps  222 ,  224 ,  228 ,  230 ,  234 ,  236 , and/or  240 ) or pipelines in waterside system  200  include an isolation valve associated therewith. Isolation valves can be integrated with the pumps or positioned upstream or downstream of the pumps to control the fluid flows in waterside system  200 . In various embodiments, waterside system  200  can include more, fewer, or different types of devices and/or subplants based on the particular configuration of waterside system  200  and the types of loads served by waterside system  200 . 
     Referring now to  FIG. 3 , a block diagram of an airside system  300  is shown, according to an example embodiment. In various embodiments, airside system  300  can supplement or replace airside system  130  in HVAC system  100  or can be implemented separate from HVAC system  100 . When implemented in HVAC system  100 , airside system  300  can include a subset of the HVAC devices in HVAC system  100  (e.g., AHU  106 , VAV units  116 , duct  112 , duct  114 , fans, dampers, etc.) and can be located in or around building  10 . Airside system  300  can operate to heat or cool an airflow provided to building  10  using a heated or chilled fluid provided by waterside system  200 . 
     In  FIG. 3 , airside system  300  is shown to include 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, AHU  302  can receive return air  304  from building zone  306  via return air duct  308  and can deliver supply air  310  to building zone  306  via supply air duct  312 . In some embodiments, AHU  302  is a rooftop unit located on the roof of building  10  (e.g., AHU  106  as shown in  FIG. 1 ) or otherwise positioned to receive both return air  304  and outside air  314 . AHU  302  can be configured to operate exhaust air damper  316 , mixing damper  318 , and outside air damper  320  to control an amount of outside air  314  and return air  304  that combine to form supply air  310 . Any return air  304  that does not pass through mixing damper  318  can be exhausted from AHU  302  through exhaust damper  316  as exhaust air  322 . 
     Each of dampers  316 - 320  can be operated by an actuator. For example, exhaust air damper  316  can be operated by actuator  324 , mixing damper  318  can be operated by actuator  326 , and outside air damper  320  can be operated by actuator  328 . Actuators  324 - 328  can communicate with an AHU controller  330  via a communications link  332 . Actuators  324 - 328  can receive control signals from AHU controller  330  and can provide feedback signals to AHU controller  330 . Feedback signals can include, for example, an indication of a current actuator or damper position, an amount of torque or force exerted by the actuator, diagnostic information (e.g., results of diagnostic tests performed by actuators  324 - 328 ), status information, commissioning information, configuration settings, calibration data, and/or other types of information or data that can be collected, stored, or used by actuators  324 - 328 . AHU controller  330  can be an economizer controller configured to use one or more control algorithms (e.g., state-based algorithms, extremum seeking control (ESC) algorithms, proportional-integral (PI) control algorithms, proportional-integral-derivative (PID) control algorithms, model predictive control (MPC) algorithms, feedback control algorithms, etc.) to control actuators  324 - 328 . 
     Still referring to  FIG. 3 , AHU  302  is shown to include a cooling coil  334 , a heating coil  336 , and a fan  338  positioned within supply air duct  312 . Fan  338  can be configured to force supply air  310  through cooling coil  334  and/or heating coil  336  and provide supply air  310  to building zone  306 . AHU controller  330  can communicate with fan  338  via communications link  340  to control a flow rate of supply air  310 . In some embodiments, AHU controller  330  controls an amount of heating or cooling applied to supply air  310  by modulating a speed of fan  338 . 
     Cooling coil  334  can receive a chilled fluid from waterside system  200  (e.g., from cold water loop  216 ) via piping  342  and can return the chilled fluid to waterside system  200  via piping  344 . Valve  346  can be positioned along piping  342  or piping  344  to control a flow rate of the chilled fluid through cooling coil  334 . In some embodiments, cooling coil  334  includes multiple stages of cooling coils that can be independently activated and deactivated (e.g., by AHU controller  330 , by BMS controller  366 , etc.) to modulate an amount of cooling applied to supply air  310 . 
     Heating coil  336  can receive a heated fluid from waterside system  200  (e.g., from hot water loop  214 ) via piping  348  and can return the heated fluid to waterside system  200  via piping  350 . Valve  352  can be positioned along piping  348  or piping  350  to control a flow rate of the heated fluid through heating coil  336 . In some embodiments, heating coil  336  includes multiple stages of heating coils that can be independently activated and deactivated (e.g., by AHU controller  330 , by BMS controller  366 , etc.) to modulate an amount of heating applied to supply air  310 . 
     Each of valves  346  and  352  can be controlled by an actuator. For example, valve  346  can be controlled by actuator  354  and valve  352  can be controlled by actuator  356 . Actuators  354 - 356  can communicate with AHU controller  330  via communications links  358 - 360 . Actuators  354 - 356  can receive control signals from AHU controller  330  and can provide feedback signals to controller  330 . In some embodiments, AHU controller  330  receives a measurement of the supply air temperature from a temperature sensor  362  positioned in supply air duct  312  (e.g., downstream of cooling coil  334  and/or heating coil  336 ). AHU controller  330  can also receive a measurement of the temperature of building zone  306  from a temperature sensor  364  located in building zone  306 . 
     In some embodiments, AHU controller  330  operates valves  346  and  352  via actuators  354 - 356  to modulate an amount of heating or cooling provided to supply air  310  (e.g., to achieve a setpoint temperature for supply air  310  or to maintain the temperature of supply air  310  within a setpoint temperature range). The positions of valves  346  and  352  affect the amount of heating or cooling provided to supply air  310  by cooling coil  334  or heating coil  336  and may correlate with the amount of energy consumed to achieve a desired supply air temperature. AHU controller  330  can control the temperature of supply air  310  and/or building zone  306  by activating or deactivating coils  334 - 336 , adjusting a speed of fan  338 , or a combination of both. 
     Still referring to  FIG. 3 , airside system  300  is shown to include a building management system (BMS) controller  366  and a client device  368 . BMS controller  366  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  300 , waterside system  200 , HVAC system  100 , and/or other controllable systems that serve building  10 . BMS controller  366  can communicate with multiple downstream building systems or subsystems (e.g., HVAC system  100 , a security system, a lighting system, waterside system  200 , etc.) via a communications link  370  according to like or disparate protocols (e.g., LON, BACnet, etc.). In various embodiments, AHU controller  330  and BMS controller  366  can be separate (as shown in  FIG. 3 ) or integrated. In an integrated implementation, AHU controller  330  can be a software module configured for execution by a processor of BMS controller  366 . 
     In some embodiments, AHU controller  330  receives information from BMS controller  366  (e.g., commands, setpoints, operating boundaries, etc.) and provides information to BMS controller  366  (e.g., temperature measurements, valve or actuator positions, operating statuses, diagnostics, etc.). For example, AHU controller  330  can provide BMS controller  366  with temperature measurements from temperature sensors  362  and  364 , equipment on/off states, equipment operating capacities, and/or any other information that can be used by BMS controller  366  to monitor or control a variable state or condition within building zone  306 . 
     Client device  368  can include one or more human-machine interfaces or client interfaces (e.g., graphical user interfaces, reporting interfaces, text-based computer interfaces, client-facing web services, web servers that provide pages to web clients, etc.) for controlling, viewing, or otherwise interacting with HVAC system  100 , its subsystems, and/or devices. Client device  368  can be a computer workstation, a client terminal, a remote or local interface, or any other type of user interface device. Client device  368  can be a stationary terminal or a mobile device. For example, client device  368  can be a desktop computer, a computer server with a user interface, a laptop computer, a tablet, a smartphone, a PDA, or any other type of mobile or non-mobile device. Client device  368  can communicate with BMS controller  366  and/or AHU controller  330  via communications link  372 . 
     Referring now to  FIG. 4 , a block diagram of a building management system (BMS)  400  is shown, according to an example embodiment. BMS  400  can be implemented in building  10  to automatically monitor and control various building functions. BMS  400  is shown to include BMS controller  366  and a plurality of building subsystems  428 . Building subsystems  428  are shown to include a building electrical subsystem  434 , an information communication technology (ICT) subsystem  436 , a security subsystem  438 , a HVAC subsystem  440 , a lighting subsystem  442 , a lift/escalators subsystem  432 , and a fire safety subsystem  430 . In various embodiments, building subsystems  428  can include fewer, additional, or alternative subsystems. For example, building subsystems  428  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 control building  10 . In some embodiments, building subsystems  428  include waterside system  200  and/or airside system  300 , as described with reference to  FIGS. 2 and 3 . 
     Each of building subsystems  428  can include any number of devices, controllers, and connections for completing its individual functions and control activities. HVAC subsystem  440  can include many of the same components as HVAC system  100 , as described with reference to  FIGS. 1-3 . For example, HVAC subsystem  440  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  10 . Lighting subsystem  442  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 subsystem  438  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 to  FIG. 4 , BMS controller  366  is shown to include a communications interface  407  and a BMS interface  409 . Interface  407  can facilitate communications between BMS controller  366  and external applications (e.g., monitoring and reporting applications  422 , enterprise control applications  426 , remote systems and applications  444 , applications residing on client devices  448 , etc.) for allowing user control, monitoring, and adjustment to BMS controller  366  and/or subsystems  428 . Interface  407  can also facilitate communications between BMS controller  366  and client devices  448 . BMS interface  409  can facilitate communications between BMS controller  366  and building subsystems  428  (e.g., HVAC, lighting security, lifts, power distribution, business, etc.). 
     Interfaces  407 ,  409  can be or include wired or wireless communications interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wire terminals, etc.) for conducting data communications with building subsystems  428  or other external systems or devices. In various embodiments, communications via interfaces  407 ,  409  can be direct (e.g., local wired or wireless communications) or via a communications network  446  (e.g., a WAN, the Internet, a cellular network, etc.). For example, interfaces  407 ,  409  can include an Ethernet card and port for sending and receiving data via an Ethernet-based communications link or network. In another example, interfaces  407 ,  409  can include a Wi-Fi transceiver for communicating via a wireless communications network. In another example, one or both of interfaces  407 ,  409  can include cellular or mobile phone communications transceivers. In one embodiment, communications interface  407  is a power line communications interface and BMS interface  409  is an Ethernet interface. In other embodiments, both communications interface  407  and BMS interface  409  are Ethernet interfaces or are the same Ethernet interface. 
     Still referring to  FIG. 4 , BMS controller  366  is shown to include a processing circuit  404  including a processor  406  and memory  408 . Processing circuit  404  can be communicably connected to BMS interface  409  and/or communications interface  407  such that processing circuit  404  and the various components thereof can send and receive data via interfaces  407 ,  409 . Processor  406  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  408  (e.g., memory, memory unit, storage device, etc.) can include one or more devices (e.g., RAM, ROM, Flash memory, hard disk storage, etc.) for storing data and/or computer code for completing or facilitating the various processes, layers and modules described in the present application. Memory  408  can be or include volatile memory or non-volatile memory. Memory  408  can include database components, object code components, script components, or any other type of information structure for supporting the various activities and information structures described in the present application. According to an example embodiment, memory  408  is communicably connected to processor  406  via processing circuit  404  and includes computer code for executing (e.g., by processing circuit  404  and/or processor  406 ) one or more processes described herein. 
     In some embodiments, BMS controller  366  is implemented within a single computer (e.g., one server, one housing, etc.). In various other embodiments BMS controller  366  can be distributed across multiple servers or computers (e.g., that can exist in distributed locations). Further, while  FIG. 4  shows applications  422  and  426  as existing outside of BMS controller  366 , in some embodiments, applications  422  and  426  can be hosted within BMS controller  366  (e.g., within memory  408 ). 
     Still referring to  FIG. 4 , memory  408  is shown to include an enterprise integration layer  410 , an automated measurement and validation (AM&amp;V) layer  412 , a demand response (DR) layer  414 , a fault detection and diagnostics (FDD) layer  416 , an integrated control layer  418 , and a building subsystem integration later  420 . Layers  410 - 420  can be configured to receive inputs from building subsystems  428  and other data sources, determine optimal control actions for building subsystems  428  based on the inputs, generate control signals based on the optimal control actions, and provide the generated control signals to building subsystems  428 . The following paragraphs describe some of the general functions performed by each of layers  410 - 420  in BMS  400 . 
     Enterprise integration layer  410  can be configured to serve clients or local applications with information and services to support a variety of enterprise-level applications. For example, enterprise control applications  426  can be configured to provide subsystem-spanning control to a graphical user interface (GUI) or to any number of enterprise-level business applications (e.g., accounting systems, user identification systems, etc.). Enterprise control applications  426  can also or alternatively be configured to provide configuration GUIs for configuring BMS controller  366 . In yet other embodiments, enterprise control applications  426  can work with layers  410 - 420  to optimize building performance (e.g., efficiency, energy use, comfort, or safety) based on inputs received at interface  407  and/or BMS interface  409 . 
     Building subsystem integration layer  420  can be configured to manage communications between BMS controller  366  and building subsystems  428 . For example, building subsystem integration layer  420  can receive sensor data and input signals from building subsystems  428  and provide output data and control signals to building subsystems  428 . Building subsystem integration layer  420  can also be configured to manage communications between building subsystems  428 . Building subsystem integration layer  420  translate communications (e.g., sensor data, input signals, output signals, etc.) across a plurality of multi-vendor/multi-protocol systems. 
     Demand response layer  414  can be configured to optimize resource usage (e.g., electricity use, natural gas use, water use, etc.) and/or the monetary cost of such resource usage in response to satisfy the demand of building  10 . The optimization can be based on time-of-use prices, curtailment signals, energy availability, or other data received from utility providers, distributed energy generation systems  424 , from energy storage  427  (e.g., hot TES  242 , cold TES  244 , etc.), or from other sources. Demand response layer  414  can receive inputs from other layers of BMS controller  366  (e.g., building subsystem integration layer  420 , integrated control layer  418 , etc.). The inputs received from other layers can include environmental or sensor inputs such as temperature, carbon dioxide levels, relative humidity levels, air quality sensor outputs, occupancy sensor outputs, room schedules, and the like. The inputs can also include inputs such as electrical use (e.g., expressed in kWh), thermal load measurements, pricing information, projected pricing, smoothed pricing, curtailment signals from utilities, and the like. 
     According to an example embodiment, demand response layer  414  includes control logic for responding to the data and signals it receives. These responses can include communicating with the control algorithms in integrated control layer  418 , changing control strategies, changing setpoints, or activating/deactivating building equipment or subsystems in a controlled manner. Demand response layer  414  can also include control logic configured to determine when to utilize stored energy. For example, demand response layer  414  can determine to begin using energy from energy storage  427  just prior to the beginning of a peak use hour. 
     In some embodiments, demand response layer  414  includes a control module configured to actively initiate control actions (e.g., automatically changing setpoints) which minimize energy costs based on one or more inputs representative of or based on demand (e.g., price, a curtailment signal, a demand level, etc.). In some embodiments, demand response layer  414  uses equipment models to determine an optimal set of control actions. The equipment models can include, for example, thermodynamic models describing the inputs, outputs, and/or functions performed by various sets of building equipment. Equipment models can represent collections of building equipment (e.g., subplants, chiller arrays, etc.) or individual devices (e.g., individual chillers, heaters, pumps, etc.). 
     Demand response layer  414  can further include or draw upon one or more demand response policy definitions (e.g., databases, XML files, etc.). The policy definitions can be edited or adjusted by a user (e.g., via a graphical user interface) so that the control actions initiated in response to demand inputs can be tailored for the user&#39;s application, desired comfort level, particular building equipment, or based on other concerns. For example, the demand response policy definitions can specify which equipment can be turned on or off in response to particular demand inputs, how long a system or piece of equipment should be turned off, what setpoints can be changed, what the allowable set point adjustment range is, how long to hold a high demand setpoint before returning to a normally scheduled setpoint, how close to approach capacity limits, which equipment modes to utilize, the energy transfer rates (e.g., the maximum rate, an alarm rate, other rate boundary information, etc.) into and out of energy storage devices (e.g., thermal storage tanks, battery banks, etc.), and when to dispatch on-site generation of energy (e.g., via fuel cells, a motor generator set, etc.). 
     Integrated control layer  418  can be configured to use the data input or output of building subsystem integration layer  420  and/or demand response later  414  to make control decisions. Due to the subsystem integration provided by building subsystem integration layer  420 , integrated control layer  418  can integrate control activities of the subsystems  428  such that the subsystems  428  behave as a single integrated supersystem. In an example embodiment, integrated control layer  418  includes control logic that uses inputs and outputs from a plurality of building subsystems to provide greater comfort and energy savings relative to the comfort and energy savings that separate subsystems could provide alone. For example, integrated control layer  418  can be configured to use an input from a first subsystem to make an energy-saving control decision for a second subsystem. Results of these decisions can be communicated back to building subsystem integration layer  420 . 
     Integrated control layer  418  is shown to be logically below demand response layer  414 . Integrated control layer  418  can be configured to enhance the effectiveness of demand response layer  414  by enabling building subsystems  428  and their respective control loops to be controlled in coordination with demand response layer  414 . This configuration may advantageously reduce disruptive demand response behavior relative to conventional systems. For example, integrated control layer  418  can be configured to assure that a demand response-driven upward adjustment to the setpoint for chilled water temperature (or another component that directly or indirectly affects temperature) does not result in an increase in fan energy (or other energy used to cool a space) that would result in greater total building energy use than was saved at the chiller. 
     Integrated control layer  418  can be configured to provide feedback to demand response layer  414  so that demand response layer  414  checks that constraints (e.g., temperature, lighting levels, etc.) are properly maintained even while demanded load shedding is in progress. The constraints can also include setpoint or sensed boundaries relating to safety, equipment operating limits and performance, comfort, fire codes, electrical codes, energy codes, and the like. Integrated control layer  418  is also logically below fault detection and diagnostics layer  416  and automated measurement and validation layer  412 . Integrated control layer  418  can be configured to provide calculated inputs (e.g., aggregations) to these higher levels based on outputs from more than one building subsystem. 
     Automated measurement and validation (AM&amp;V) layer  412  can be configured to verify that control strategies commanded by integrated control layer  418  or demand response layer  414  are working properly (e.g., using data aggregated by AM&amp;V layer  412 , integrated control layer  418 , building subsystem integration layer  420 , FDD layer  416 , or otherwise). The calculations made by AM&amp;V layer  412  can be based on building system energy models and/or equipment models for individual BMS devices or subsystems. For example, AM&amp;V layer  412  can compare a model-predicted output with an actual output from building subsystems  428  to determine an accuracy of the model. 
     Fault detection and diagnostics (FDD) layer  416  can be configured to provide on-going fault detection for building subsystems  428 , building subsystem devices (i.e., building equipment), and control algorithms used by demand response layer  414  and integrated control layer  418 . FDD layer  416  can receive data inputs from integrated control layer  418 , directly from one or more building subsystems or devices, or from another data source. FDD layer  416  can automatically diagnose and respond to detected faults. The responses to detected or diagnosed faults can include providing an 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 layer  416  can be configured to output a specific identification of the faulty component or cause of the fault (e.g., loose damper linkage) using detailed subsystem inputs available at building subsystem integration layer  420 . In other example embodiments, FDD layer  416  is configured to provide “fault” events to integrated control layer  418  which executes control strategies and policies in response to the received fault events. According to an example embodiment, FDD layer  416  (or a policy executed by an integrated control engine or business rules engine) can shut-down systems or direct control activities around faulty devices or systems to reduce energy waste, extend equipment life, or assure proper control response. 
     FDD layer  416  can be configured to store or access a variety of different system data stores (or data points for live data). FDD layer  416  can use some content of the data stores to identify faults at the equipment level (e.g., specific chiller, specific AHU, specific terminal unit, etc.) and other content to identify faults at component or subsystem levels. For example, building subsystems  428  can generate temporal (i.e., time-series) data indicating the performance of BMS  400  and the various components thereof. The data generated by building subsystems  428  can include measured or calculated values that exhibit statistical characteristics and provide information about how the corresponding system or process (e.g., a temperature control process, a flow control process, etc.) is performing in terms of error from its setpoint. These processes can be examined by FDD layer  416  to expose when the system begins to degrade in performance and alert a user to repair the fault before it becomes more severe. 
     Global Search and Control System 
     According to the exemplary embodiment shown in  FIG. 5 , a search and control system, shown as global search and control system  500 , is configured to communicate with a building network  530 . Building network  530  may include BMS  400  (e.g., BMS controller  366 , building subspaces  428 , etc.) and/or any items (e.g., spaces, equipment, objects, points, etc.) of a building that global search and control system  500  is associated with. Global search and control system  500  may be configured to provide various reporting capabilities regarding the items and/or facilitate providing commands (e.g., bulk commands, individual commands, etc.) to one or more of the items (e.g., spaces, equipment, objects, points, etc.) connected therewith. 
     As shown in  FIG. 5 , global search and control system  500  includes a communications interface  502  and processing circuit  504  having a processor  506  and a memory  508 . Processing circuit  504  can be communicably connected to communications interface  502  such that processing circuit  504  and the various components thereof can send and receive data via communications interface  502  (e.g., to/from building network  530 , etc.). Processor  506  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  508  (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  508  can be or include volatile memory or non-volatile memory. Memory  508  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 example embodiment, memory  508  is communicably connected to processor  506  via processing circuit  504  and includes computer code for executing (e.g., by processing circuit  504  and/or processor  506 ) one or more processes described herein. In some embodiments, global search and control system  500  is implemented within a single computer (e.g., one server, one housing, etc.). In various other embodiments, global search and control system  500  can be distributed across multiple servers or computers (e.g., that can exist in distributed locations). 
     Still referring to  FIG. 5 , memory  508  is shown to include a data module  510 , a search module  512 , a command module  514 , a modification module  516 , and a report module  518 . Modules  510 - 518  can be configured to receive inputs from and/or send outputs to building network  530  (e.g., building subsystems  428 , BMS controller  366 , etc.), a user input/output (I/O) device  540 , and other data sources and provide searching, reporting, and/or command capabilities. The following paragraphs describe some of the general functions performed by each module  510 - 518  of global search and control system  500 . 
     Data module  510  may be configured to receive and/or store various data regarding components of the building network  530 . By way of example, data module may  510  have access to information regarding spaces, equipment, objects, items, points, etc. of building network  530  and the associations therebetween. Data module  510  may receive the information directly from the components of building subsystems  428  and/or BMS controller  366 . 
     Search module  512  may be configured to perform a search request of an operator based on filter criteria inputted by the operator and/or an authorization level of the operator. Search module  512  may perform the search by accessing the information received and/or stored by data module  510  and/or by communicating directly with building network  530  to receive the requested information. 
     Referring to  FIGS. 6A-7 , search module  512  may provide a search GUI  600  on user I/O device  540  having a filter section  602  and a results section  700 . Filter section  602  is configured to facilitate an operator with inputting the filter criteria for the search request. As shown in  FIG. 6 , filter section  602  of search GUI  600  includes various fillable, selectable, and/or drop-down dialog boxes and buttons such as a space and equipment box  610 , an object type button  620 , an equipment definition button  630 , a name box  640 , a network items button  650 , a search button  660 , and a filter button  670 . 
     Space and equipment box  610  may facilitate an operator in entering a name of a space and/or a name of equipment that information/data is desired (e.g., if known by the operator, etc.). Search module  512  may be configured to return information/data regarding all of the points associated with the space and/or equipment. Object type button  620  may facilitate an operator in selecting one or more object types from a selectable drop down menu. The object types may be software objects that represent devices or points. The object types may include analog, binary, engines, meter, field devices, alarm extensions, trend extensions, etc. Search module  512  may be configured to return information/data regarding the selected object type(s). Network items button  650  may facilitate an operator with selecting any items connected to building network  530  from a building network tree. Search module  512  may be configured to return information/data regarding the selected items form the building network tree. 
     Equipment definition button  630  may facilitate an operator in selecting one or more equipment definitions from a selectable drop down menu. An equipment definition is an abstraction of a particular piece of building equipment or type of building equipment that defines the various points typically associated with equipment of that type. Each general type of building equipment (e.g., chiller, boiler, air handling unit (AHU), variable air volume (VAV) unit, fan coil unit, etc.) can be defined using a different equipment definition specific to that type of building equipment. For example, a chiller equipment definition can be used to define a chiller and may specify the various points typically associated with chillers, whereas an AHU equipment definition can be used to define an AHU and may specify the various points typically associated with AHUs. An equipment definition and the points associated therewith are generalized across models, manufacturers, vendors, or other differences between building equipment of the same general type. In various embodiments, an equipment definition can define a general type of equipment, a specific piece of equipment, or a group of equipment. Additional details regarding equipment definitions and how equipment definitions can be used by system  500  can be found in (i) U.S. patent application Ser. No. 14/251,414, filed Apr. 11, 2014, (ii) U.S. patent application Ser. No. 15/870,500, filed Jan. 12, 2018, and (iii) U.S. patent application Ser. No. 16/100,962, filed Aug. 10, 2018, the entire disclosures of which are incorporated by reference herein. 
     Each piece of equipment or group of equipment can be associated with (e.g., linked to) a particular equipment definition. Similarly, each equipment definition can be associated with (e.g., linked to) one or more pieces of equipment or groups of equipment. Search module  512  can be configured to maintain a database of the various equipment definitions and the pieces of equipment or groups of equipment linked to each equipment definition. When one or more equipment definitions are selected using equipment definition button  630  and an operator clicks search button  660 , search module  512  may be configured to return information/data regarding all of the points associated with the selected equipment definition(s). For example, search module  512  may identify all of the pieces of equipment or groups of equipment associated with the selected equipment definition(s) and may return all of the points of the identified equipment as search results, along with the information/data describing each point returned as a search result. Additional details regarding determining relationships between equipment, spaces, etc. can be found in U.S. patent application Ser. No. 16/406,994, filed May 8, 2019, the entire disclosure of which is incorporated by reference herein. 
     In some embodiments, each equipment definition defines one or more aliased points typically associated with equipment of a particular type. The aliased points may have names (e.g., short names, aliases, etc.) that designate a particular type of point. For example, an equipment definition for an AHU may define a first aliased point named “OA-T” that designates an outdoor air temperature point, a second aliased point named “DA-T” that designates a discharge air temperature point, a third aliased point named “RA-T” that designates a return air temperature point, etc. Each aliased point defined by an equipment definition may have a name or alias that identifies a particular type of point (e.g., outdoor air temperature, discharge air temperature, etc.) in a general manner such that the same equipment definition can be applied to many different pieces of equipment. Additionally, the aliased points can be searched, read, and written in a consistent manner by system  500  (or by external systems or applications) to facilitate monitoring and control of such equipment via the aliased points. 
     Name box  640  may allow an operator to enter or select a specific point name or alias. The point names or aliases entered or selected via name box  640  may function as a filter or search parameter on the search performed by search module  512 . For example, search module  512  may limit the search results to points that have the specified names or aliases. In the embodiment shown in  FIG. 6A , name box  640  requires the operator to type the point name or alias into name box  640 . In the embodiment shown in  FIG. 6B , search GUI  600  is shown to include an equipment definition dropdown menu  642  that displays all of the aliased points  648  associated with the selected equipment definition(s). The operator can select one or more of aliased points  648  via dropdown menu  642  such that the operator does not need to know the specific point name or alias when specifying point names or aliases via name box  640 . Search module  512  may be configured to return information/data regarding all of the points entered and/or selected via name box  640 . 
     In some embodiments, dropdown menu  642  includes an equipment definition selector  644  that allows the operator to specify one or more of the equipment definitions selected via equipment definition button  630  (shown in  FIG. 6B  as “AHUs” and “Chiller Plant—507 B4RF”). The aliased points  648  displayed in dropdown menu  642  may be limited to only the aliased points associated with the equipment definition(s) specified via equipment definition selector  644 . In some embodiments, dropdown menu  642  includes an aliased points search box  646  that allows the operator to search aliased points  648  (e.g., for a specific point type, for point names having a specific text string, etc.). The aliased points  648  displayed in dropdown menu  642  may be limited to only the aliased points that match the search criteria entered via search box  646 . 
     In some embodiments, search module  512  is configured to automatically populate one or more of the fields or boxes in search GUI  600  with data pertaining to a user selected item. The automatic population can be initiated from any of the user interfaces or widgets used to present information to a user. For example, a user can view all of the equipment serving a space and all the energy meters associated with a space via an “equipment serving space” (ESS) widget (e.g., VAV→AHU→Central Plants). When viewing the ESS widget, the user can select an item of equipment, a meter, or other data in the widget. In response to the user selecting an item (and clicking a link to automatically populate search GUI  600 ), search module  512  can automatically populate data associated with the selected equipment, meter, or other data in advanced search GUI  600 . For example, assume a user wants to generate a report for an entire building or floor. The user can simply select that building or floor via a filter and click an option (e.g., a link, a button, a drop-down menu, etc.) to create a report. 
     Advantageously, the automatic population feature may make the searching and reporting features described herein more discoverable as the user is entrenched in daily operational workflows. By creating quick links to populate search GUI  600 , the user can take advantage of reports, bulk commands, and modifications easily from any of the widgets used to present information to a user without requiring all of the data to be manually entered or selected via search GUI  600 . This feature may reduce time searching for information and allows the user to quickly generate a report for a selected item (e.g., a space, a device of equipment, etc.). Reports can be created across a space (e.g., building, floor, campus, room, etc.) with minimal number of clicks. 
     Search button  660  may facilitate an operator with initiating a search based on the filter criteria entered by the operator via space and equipment box  610 , object type button  620 , equipment definition button  630 , name box  640 , and/or network items button  650 . Search module  512  may be configured to perform the requested search to return information/data for one or more items based on the filter criteria entered through filter section  602  of search GUI  600  and/or the authorization level of the operator. By way of example, search module  512  may only provide search results that are returned based on the filter criteria that the operator has permission to access. For example, the authorization of the operator may be based on (i) space authorization such that an operator without authorization to a space does not receive search results related to equipment associated with the space, (ii) equipment authorization such that an operator with authorization to a space, but not some of the equipment within the space, only receives search results for the equipment within the space he or she is authorized for, and/or (iii) object authorization such that an operator with authorization to a space and equipment within the space, but not some of the objects associated with the equipment, only receives search results for the objects of the equipment within the space he or she is authorized for. Search module  512  may therefore be configured to selectively pre-filter search results based on the authorization or permission level of an operator such that results the operator is not authorized to see are not returned to users without such a permission or clearance level. 
     As shown in  FIG. 7 , results section  700  of the search GUI  600  includes a header row  702  and results rows  704 . Header row  702  includes a plurality of headers associated with a selection column  710 , a name column  720 , an item reference column  730 , a value column  740 , a units column  750 , a status column  760 , and a space(s)/equipment column  770 . Search module  512  is configured to return a set of search results having a quantity of search results based on the filter criteria and/or the authorization level of the operator for display in results rows  704  including information associated with each of the headers of columns  710 - 770 . If search module  512  is unable to return any search results based on the filter criteria and/or the authorization level of the operator, search module  512  may be configured to display a notification on search GUI  600  indicating that the filter criteria needs to be refined. The operator may then enter new or revised filter criteria via filter section  602 . When results are returned by search module  512 , results rows  704  may be sorted by selecting one of the headers of columns  710 - 770  (e.g., selecting the header of name column  720  will sort the results rows alphabetically by name, etc.). 
     According to an exemplary embodiment, search module  512  is configured dynamically update the set of search results in results section  700  based on the quantity of results rows  704 . By way of example, search module  512  may be configured to determine whether the quantity of results rows  704  is greater than a first threshold. In one embodiment, the first threshold is 200 results rows  704 . In other embodiments, the first threshold is greater than or less than 200 results rows  704  (e.g., 100, 300, 500, 800, 1000, etc. results rows  704 ). Search module  512  may be configured to dynamically update results rows  704  in real time within the results section  700  in response to the quantity of results rows  704  being less than the first threshold. Search module  512  may be configured to determine whether the quantity of results rows  704  is greater than a second threshold in response to the quantity of results rows  704  being greater than the first threshold. In one embodiment, the second threshold is 1000 results rows  704 . In other embodiments, the second threshold is greater than or less than 1000 results rows  704  (e.g., 500, 750, 800, 1200, 2000, 3000, etc. results rows  704 ). Search module  512  may be configured to display a notification in search GUI  600  indicating results rows  704  are not being dynamically updated in response to the quantity of results rows  704  being greater than the first threshold, but less than the second threshold. Search module  512  may be configured to display a notification in search GUI  600  indicating that the quantity of results rows  704  exceeds a maximum number of search results and that the filter criteria needs to be refined in response to the quantity of results rows  704  being greater than the second threshold. The operator may then enter new or revised filter criteria via filter section  602 . 
     As shown in  FIG. 7 , selection column  710  includes a plurality of selectable boxes  712 . The plurality of selectable boxes  712  may facilitate an operator with selecting specific rows of items presented within results section  700 . Name column  720  provides the names of each item presented within results section  700 . As shown in  FIG. 7 , item reference column  730  includes a selectable link  732  for each of the items presented in the results section  700 . According to an exemplary embodiment, each selectable link  732  of item reference column  730  is associated with a network page for a respective item presented in results section  700 . Search module  512  may thereby be configured to redirect an operator from search GUI  600  to the network page of an item (e.g., containing various information regarding the item, etc.) associated with a respective selectable link  732  in response to the selection of the respective selectable link  732 . 
     As shown in  FIG. 7 , value column  740  includes a selectable link  742  for each of the items presented in the results section  700 . According to an exemplary embodiment, each selectable link  742  of value column  740  provides (e.g., displays, etc.) the current set point or mode the associated item is operating at or in. By way of example, the current set point or mode may include active, inactive, unknown, a current set point value (e.g., a speed set point value, a temperature set point value, a pressure set point value, etc.), and the like. Command module  514  may be configured to provide a single command modal window over search GUI  600  in response to a selection of a respective selectable link  742  by an operator from search GUI  600 . The operator may thereby be able to provide a single command to the item associated with the respective selectable link  742  to change the current set point or mode of operation of the item. As shown in  FIG. 7 , the status column  760  displays the current status for each items presented in the results section. The current status may include normal, online, offline, standby, derate, fault, etc. 
     As shown in  FIG. 7 , space(s)/equipment column  770  includes a selectable link  772  for each of the items presented in the results section  700 . According to an exemplary embodiment, each selectable link  772  of space(s)/equipment column  770  is associated with a space or equipment page for each of the spaces and/or equipment the respective item is associated with. Selectable links  772  may be associated with multiple spaces and/or equipment for a respective item. By way of example, when a selectable link  772  is associated with more than one space and/or equipment (e.g., two, three, four, etc.), search module  512  may be configured display a pop-up window with direct links to each of the spaces and/or equipment pages associated with the respective item in response to an operator hovering over or selecting the associated selectable link  772 . If only one space or equipment is associated with the respective item, the associated selectable link  772  may be a direct link to the associated space page or equipment page. 
     As shown in  FIGS. 6A-8 , filter section  602  of search GUI  600  includes a filter button  670  and an actions button  680 . According to an exemplary embodiment, the filter button  670  facilitates expanding filter section  602  (e.g., as shown in  FIGS. 6A-6B , etc.) and retracting filter section  602  (e.g., as shown in  FIG. 7 , etc.). As shown in  FIG. 8 , selecting actions button  680  causes a drop down menu to be provided including a bulk command button  682  and a create report button  684 . According to an exemplary embodiment, a bulk command may be provided to a plurality (e.g., two or more, etc.) of the items of result rows  704  via bulk command button  682  and/or a report may be generated for a plurality of the items of result rows  704  via create report button  684 . 
     Command module  514  may be configured to provide a command to one or more items returned by search module  512  within results section  700  based on various user inputs. By way of example, command module  514  may be configured to provide a command to a single item based on an operator selecting a respective selectable link  742  of value column  740 , as described above. By way of another example, command module  514  may be configured to provide a bulk command to one or more items returned by search module  512  within results section  700  based on an operator selecting one or more of results rows  704  and bulk command button  682 . Referring now to  FIG. 9 , command module  514  may provide a bulk command modal window  800  (e.g., over search GUI  600 , etc.) in response to an operator selecting bulk command button  682 . Bulk command modal window  800  is configured to facilitate an operator with inputting command criteria for a bulk command to be provided to one or more of the items associated with the selected results rows  704 . 
     As shown in  FIG. 9 , command module  514  is configured to provide a command interface  810  on bulk command modal window  800 . The command interface  810  includes various fillable, selectable, and/or drop-down dialog boxes and buttons such as a command button  812 , a value button  814 , and an expiration section  816 . The command button  812  may facilitate the operator with inputting and/or selecting an available command (e.g., command capable of being provided to the selected items, etc.) to provide to one or more of the items associated with the selected results rows  704 . The value button  814  may facilitate the operator with providing a value (e.g., active, inactive, an operating parameter, etc.) for the command to one or more of the items associated with the selected results rows  704 . The expiration section  816  may facilitate the operator with providing a duration for the command to remain in effect before expiring. 
     Command module  514  is configured receive command criteria (e.g., via command button  812 , value button  814 , expiration section  816 , etc.) regarding a bulk command to provide to the one or more items of the selected results rows  704  that are capable of receiving the chosen bulk command. According to an exemplary embodiment, command module  514  has a smart command/detect capability such that command module  514  may detect and identify whether a bulk command can be provided to each of the items associated with the selected results rows  704 . By way of example, command module  514  may be configured to recognize class IDs for each of the items of the selected results rows  704  and determine whether the chosen bulk command can be applied to each of the class IDs present in the selected results rows  704 . For example, a certain type of command may not be compatible with one or more class IDs. Command module  514  may therefore be configured to return a notification indicating that the chosen bulk command cannot be completed for all of the selected results rows  704  in response to the chosen bulk command not being capable of being applied to all of the represented class IDs. 
     After receiving the command criteria and the operator pressing next button  822 , command module  514  may be configured to provide a preview interface  830  on bulk command modal window  800 . Preview interface  830  may provide an indication of the number of items the bulk command will affect (e.g., the items with class IDs compatible with the bulk command, etc.), the command being provided, a table showing the items that will be affected (e.g., object, name, item reference, present value, etc.), etc. Command module  514  may be configured to receive an indication from the operator to proceed with the bulk command (e.g., a next button on the preview interface  830 , etc.). Command module  514  may then provide the bulk command to the compatible items associated with the selected results rows  704 . 
     Command module  514  may be further configured to provide a confirmation interface  850  on bulk command modal window  800  in response to the bulk command being provided to the items associated with the selected results rows  704 . Confirmation interface  850  may provide various information such as the number of items the bulk command affected, the command that was provided, a table showing successful commands and failed commands, etc. The successful command may be grouped together and the failed commands may be grouped together separately. By way of example, a plurality of air handling units (e.g., two, three, etc.) may have been provided a bulk command by command module  514 . Confirmation interface  850  may provide information regarding the value prior to the bulk command (e.g., inactive, etc.), the command that was provided thereto (e.g., operator override, etc.), the value of the command (e.g., active, etc.), and an indication of which of the plurality of air handling units were successfully commanded and which failed. 
     Modification module  516  may be configured to facilitate modifying a plurality of points (e.g., one, two, five, ten, one hundred, etc.) returned by search module  512  within results section  700  based on various user inputs simultaneously. By way of example, modification module  516  may be configured to facilitate changing alarm limits across hundreds of points simultaneously. Referring now to  FIG. 17 , modification module  516  may provide a bulk modify modal window  1000  (e.g., over search GUI  600 , in response to an operator selecting a bulk modify button, etc.). Bulk modify modal window  1000  is configured to facilitate an operator with inputting modification criteria for a bulk modification to be provided to one or more of the items associated with the selected results rows  704 . 
     As shown in  FIG. 17 , modification module  516  is configured to provide a modification interface  1010  on bulk modify modal window  1000 . The modification interface  1010  includes an attribute column  1012  identifying various attributes of the selected items, a value column  1014  including fillable, selectable, and/or drop-down dialog boxes and buttons that facilitate inputting a value for the attributes in attribute column  1012  that an operator would like to modify, and a units column  1016  identifying the units for the value of the attributes in the value column  1014 . The attributes in the attribute column  1012  may include a name, an alarm value, a differential value, a high alarm limit, a high warning offset, a low alarm limit, a low warning offset, alarm setup attributes including whether alarm acknowledgment is required, alarm message text, and alarm priority, and/or still other attributes. 
     Modification module  516  is configured receive modification criteria (e.g., via value column  1014 , etc.) regarding at least one attribute of the one or more items associated with the selected results rows  704  to be modified. After receiving the modification criteria and the operator pressing next button  1022 , modification module  516  may be configured to provide a preview interface  1030  on bulk modify modal window  1000 . Preview interface  1030  may provide an indication of the number of items the bulk modification will affect, the attributes being modified, the old value and/or the new value of the attributes being modified, etc. Modification module  516  may be configured to receive an indication from the operator to proceed with the bulk modification (e.g., a next button on the preview interface  1030 , etc.). Modification module  516  may then perform a modification on the at least one attribute of the one or more items associated with the selected results rows  704 . The modification may cause the at least one attribute of the one or more items to update to the new value. 
     Modification module  516  may be further configured to provide a confirmation interface  1050  on bulk modify modal window  100  in response to the bulk modification being provided to the items associated with the selected results rows  704 . Confirmation interface  1050  may provide various information such as the number of items the bulk modification affected, the attributes that were modified, a table showing successful modifications and failed modifications, etc. The successful modifications may be grouped together and the failed modifications may be grouped together separately. 
     Report module  518  may be configured to generate a report for one or more items returned by search module  512  within results section  700  based on various user inputs. Referring now to  FIG. 10 , report module  518  may provide a report modal window  900  (e.g., over search GUI  600 , etc.) in response to an operator selecting create report button  684 . Report modal window  900  is configured to facilitate an operator with inputting report criteria for a report to be generated regarding one or more of the items associated with the selected results rows  704 . 
     As shown in  FIG. 10 , report modal window  900  includes various fillable, selectable, and/or drop-down dialog boxes and buttons such as a start date and time box  910 , an end date and time box  920 , a report type box  930 , and an export type box  940 . The start date and time box  910  may facilitate the operator with inputting a start date and/or a start time at which report module  518  should gather data from (e.g., from the data module  510 , etc.) for the requested report. The end date and time box  920  may facilitate the operator with inputting an end date and/or an end time at which report module  518  should gather data up to (e.g., from the data module  510 , etc.) for the requested report. The report type box  930  may facilitate the operator with selecting a type of report that is desired from a drop-down menu. The type of report may include an activity report, an alarm report, an audit report, and/or a trend report. The export type box  940  may facilitate the operator with selecting a type of export file that is desired for the report from a drop-down menu. The type of export file may include a csv file, a pdf file, an excel file, a text file, and/or still another type of suitable file format. 
     The activity report may present activity information regarding alarms and audits for items selected from results section  700  of search GUI  600  within the selected time frame provided through start date and time box  910  and end date and time box  920 . The alarm report may present alarm information regarding alarms for items selected from results section  700  of search GUI  600  within the selected time frame provided through start date and time box  910  and end date and time box  920 . The audit report may present audit information for items selected from results section  700  of search GUI  600  within the selected time frame provided through start date and time box  910  and end date and time box  920 . The trend report may present trend information including time series data for the selected items. 
     According to an exemplary embodiment, report module  518  is configured to select a specific granularity to present the data for the selected items based on the selected time frame. The time series data may thereby be presented in various different levels of granularity based on the duration of time selected via start date and time box  910  and end date and time box  920 . By way of example, if the duration of time is less than a first threshold (e.g., seven days or less, etc.), report module  518  may be configured to display raw data. By way of another example, if the duration of time is greater than the first threshold, but less than a second threshold (e.g., fifty days or less, etc.), report module  518  may be configured to display data that is aggregated on a daily basis. By way of yet another example, if the duration of time is greater than the second threshold (e.g., more than fifty days, etc.), report module  518  may be configured to display data that is aggregated on a monthly basis. 
     In some embodiments, report module  518  is configured to aggregate data in a report according to the equipment associated with the data. For example, report module  518  can aggregate multiple alarms for a single device or group multiple alarms for a single device to be shown adjacent to each other in the report. Similarly, report module  518  can aggregate or group audits in an audit report and/or trends in a trend report by the corresponding device or devices of equipment. 
     Report module  518  may thereby be configured to generate a report based on the report criteria received via start date and time box  910 , end date and time box  920 , report type box  930 , and export type box  940  in response to an operator selecting the create report button  684 . In some embodiments, report module  518  facilitates downloading the generated report onto an end user device (e.g., laptop, computer, tablet, smartphone, etc.) in the format chosen in export type box  940 . The report may thereafter be saved, viewed, manipulated, printed, etc. on the end user device. In some embodiments, report module  518  is configured to facilitate saving the report for future use. 
     In some embodiments, report module  518  is configured to facilitate scheduling a report for future generation (e.g., periodic report generation, etc.). Referring now to  FIG. 18 , report module  518  may provide a report editor window  960 . Report editor window  960  is configured to facilitate an operator with setting up and scheduling a report for future and/or periodic generation. As shown in  FIG. 18 , report editor window  960  includes a report type box  962 , a date range box  964 , a format box  966 , a scheduling box  968 , a report name box  970 , a run report on box  972 , a stop running box  974 , and a send to box  976 . The report type box  962  may facilitate the operator with selecting a type of report that is desired from a drop-down menu (e.g., an activity report, an alarm report, an audit report, a trend report, etc.). The date range box  964  may facilitate the operator with selecting a date range for which data for the report should be gathered (e.g., prior day, prior week, prior month, prior quarter, prior year, all history, etc.). The format box  966  may facilitate the operator with selecting a format type of export file that is desired for the report from a drop-down menu (e.g., a csv file, a pdf file, an excel file, a text file, etc.). The scheduling box  968  may facilitate an operator in scheduling the report to be generated on a periodic basis (e.g., weekly, bi-weekly, monthly, quarterly, etc.) from a drop-down menu. The report name box  970  may facilitate an operator in providing a name for the report such that the report may be easily identifiable. The run report on box  972  may facilitate an operator is selecting on which day of the week and/or time the report is to be generated. The stop running box  974  may facilitate an operator in identifying how many times the report should be automatically generated (e.g., once, twice, ten times, infinite, etc.) and/or a future date on which the automatic generation should stop (e.g., Sep. 1, 2020; Dec. 31, 2017; etc.). The send to box  976  may facilitate an operator in identifying who the automatically generated future report(s) should be sent to (e.g., via email, etc.). A save button  978  may facilitate an operator in saving the parameters defined via boxes  962 - 976  for the future report generation. 
     As an example, global search and control system  500  may be implemented in a hospital. An operator may be able to search by spaces and/or equipment (e.g., via space and equipment box  610  of search GUI  600 , etc.) for an emergency room within the hospital. The operator may further narrow the search to find pressure and temperature measurements within the emergency room over time. Such narrowing may be completed by selecting a pressure monitor and/or temperature sensor from within the drop down menu presented when selecting equipment definition button  630 , entering the name(s) thereof into name box  640 , and/or selecting the corresponding devices from the building network tree presented when selecting network items button  650 . The operator may then proceed to generate a trend report for the pressures and/or temperatures within the emergency room for a given time period by selecting the create report button  684  and filling report criteria into report modal window  900 . Global search and control system  500  therefore provides users with the capability of generating reports for any items connected to building network  530  (e.g., any buildings, spaces, systems, equipment, devices, points, etc. connected to the building network  530  within a few steps). 
     As another example, global search and control system  500  may facilitate validating changes to equipment connected to building network  530 . By way of example, an operator may select a building (e.g., via space and equipment box  610  of search GUI  600 , etc.). Thereafter, the operator may select all air handling units (e.g., via equipment definition button  630 , etc.) and search set points for the air handling units. Global search and control system  500  may return all the set points for all the air handling units of the selected building. Thereafter, the operator can bulk select any number of the set points and have an activity/audit report generated by selecting the create report button  684  and filling report criteria into report modal window  900 . The activity/audit report may provide information such as who has made changes to the set points of the air handling units over time. 
     Referring to  FIG. 11 , a method  1100  for performing a global search is shown according to an exemplary embodiment. According to an exemplary embodiment, method  1100  is performed by global search and control system  500 . Method  1100  may therefore be described in regards to global search and control system  500 . At step  1102 , a search system (e.g., global search and control system  500 , etc.) is configured to receive a search request from an operator (e.g., while on a site management portal, etc.) via a user device (e.g., user I/O device  540 , etc.). At step  1104 , the search system is configured to display a GUI (e.g., search GUI  600 , etc.) having a filter area (e.g., filter section  602 , etc.) and a results area (e.g., the results section  700 , etc.). At step  1106 , the search system is configured to receive filter criteria from the operator. The filter criteria may include space information, equipment information, an object type, an equipment definition, a point name, a network item, etc. 
     At step  1108 , the search system is configured to perform a search based on the filter criteria and/or an authorization level of the operator. By way of example, the search system may only return search results that the operator has permission to access. For example, the authorization of the operator may be based on (i) space authorization such that an operator without authorization to a space does not receive search results related to equipment associated with the space, (ii) equipment authorization such that an operator with authorization to a space, but not some of the equipment within the space, only receives search results for the equipment within the space he or she is authorized for, and/or (iii) object authorization such that an operator with authorization to a space and equipment within the space, but not some of the objects associated with the equipment, only receives search results for the objects of the equipment within the space he or she is authorized for. The search system may therefore be configured to selectively pre-filter search results based on the authorization or permission level of an operator such that results the operator is not authorized to see are not returned to users without such a permission or clearance level. 
     At step  1110 , the search system is configured to return a set of search results having a quantity of search results based on the filter criteria and/or the authorization level of the operator. At step  1112 , the search system is configured to determine whether there are any search results based on the filter criteria and/or the authorization level of the operator. If there are no search results, the search system is configured to display a notification indicating that the filter criteria needs to be refined (step  1114 ). The operator may then enter new or revised filter criteria and the search system may repeat steps  1106 - 1112 . 
     At step  1116 , the search system is configured to determine whether the quantity of search results is greater than a first threshold (e.g., 200, 300, 500, 800, 1000, etc. search results) in response to there being at least one result. At step  1118 , the search system is configured to display the search results in the results area and dynamically update the search results in real time in response to the quantity of search results being less than the first threshold. At step  1120 , the search system is configured to determine whether the quantity of search results is greater than a second threshold (e.g., 500, 750, 800, 1000, 1200, 2000, 3000, etc. search results) in response to the quantity of search results being greater than the first threshold. At step  1122 , the search system is configured to display the search results in the results area and display a notification indicating the search results are not being dynamically updated in response to the quantity of search results being greater than the first threshold, but less than the second threshold. At step  1124 , the search system is configured to display a notification indicating that the quantity of search results exceeds a maximum number of search results and that the filter criteria needs to be refined in response to the quantity of search results being greater than the second threshold. The operator may then enter new or revised filter criteria and the search system may repeat steps  1106 - 1124 , as necessary. 
     Referring to  FIG. 12 , a method  1200  for performing a single command on an item from global search results is shown according to an exemplary embodiment. According to an exemplary embodiment, method  1200  is an extension of method  1100 . By way of example, the operator may provide a command to an item of the search results displayed by the search system (e.g., after step  1118 , step  1122 , etc.). At step  1202 , the search system is configured to receive a selection of a link in a value column (e.g., value column  740 , etc.) for a single item of the search results in the results area. At step  1204 , the search system is configured to provide a single command dialog box (e.g., in the same window as search GUI  600 , etc.). At step  1206 , the search system is configured to receive a command for the single item from the operator via the command dialog box. At step  1208 , the search system is configured to implement the command on the single item. 
     Referring to  FIG. 13 , a method  1300  for viewing a network page associated with an item from global search results is shown according to an exemplary embodiment. According to an exemplary embodiment, method  1300  is an extension of method  1100 . By way of example, the operator may view the network page of an item in the search results displayed by the search system (e.g., after step  1118 , step  1122 , etc.). At step  1302 , the search system is configured to receive a selection of a link in an item reference column (e.g., item reference column  730 , etc.) for a single item of the search results in the results area. At step  1304 , the search system is configured to provide a navigate away message indicating that the search system has to navigate away from the current interface (e.g., search GUI  600 , etc.) to display the network page associated with the selected link in the item reference column. At step  1306 , the search system is configured to receive a request to navigate away (e.g., from search GUI  600 , etc.). In some embodiments, the search system does not complete step  1304  and/or step  1306  (e.g., the operator has previously selected to not receive the navigate away message, etc.). At step  1308 , the search system is configured to navigate to a corresponding network page associated with the single item. 
     Referring to  FIG. 14 , a method  1400  for viewing a space or equipment page associated with an item from global search results is shown according to an exemplary embodiment. According to an exemplary embodiment, method  1400  is an extension of method  1100 . By way of example, the operator may view the space and/or equipment page of an item in the search results displayed by the search system (e.g., after step  1118 , step  1122 , etc.). At step  1402 , the search system is configured to receive a selection of a link in a space/equipment column (e.g., space/equipment column  770 , etc.) for a single item of the search results in the results area. At step  1404 , the search system is configured to provide a navigate away message indicating that the search system has to navigate away from the current interface (e.g., search GUI  600 , etc.) to display the space and/or equipment page associated with the selected link in the space/equipment column. At step  1406 , the search system is configured to receive a request to navigate away (e.g., from search GUI  600 , etc.). In some embodiments, the search system does not complete step  1404  and/or step  1406  (e.g., the operator has previously selected to not receive the navigate away message, etc.). At step  1408 , the search system is configured to navigate to a corresponding space or equipment page associated with the single item. 
     Referring to  FIG. 15 , a method  1500  for generating a report based on global search results is shown according to an exemplary embodiment. According to an exemplary embodiment, method  1500  is an extension of method  1100 . By way of example, the operator may generate a report from the search results displayed by the search system (e.g., after step  1118 , step  1122 , etc.). At step  1502 , the search system is configured to receive a selection of one or more rows from the search results in the results area. At step  1504 , the search system is configured to receive a selection of an “actions” button (e.g., actions button  680 , etc.) in the filter area which causes the search system to display an actions drop-down menu. At step  1506 , the search system is configured to receive a selection of a “create report” button (e.g., create report button  684 , etc.) in the actions drop-down menu. 
     At step  1508 , the search system is configured to provide a “report creator” modal window (e.g., report modal window  900 , etc.) over the search results (e.g., in the same window as search GUI  600 , etc.). The report creator modal window may include various fillable, selectable, and/or drop-down dialog boxes that are configured to receive various information or parameters used for generating a desired report. The dialog boxes may include a start date and time box (e.g., start date and time box  910 , etc.), an end date and time box (e.g., end data and time box  920 , etc.), a report type box (e.g., report type box  930 , etc.), and/or an export type box (e.g., export type box  940 , etc.). The start date and time box may facilitate the operator with inputting a start date and/or a start time at which data for the report should be gather from. The end date and time box may facilitate the operator with inputting an end date and/or an end time at which data for the report should be gather up to. The report type box may facilitate the operator with selecting a type of report that is desired from a drop-down menu. The type of report may include an activity report (e.g., alarms and audits for items selected in the advanced search and selected time frame, etc.), an alarm report, an audit report, and/or a trend report. The export type box may facilitate the operator with selecting a type of export file that is desired for the report from a drop-down menu. The type of export file may include a csv file, a pdf file, an excel file, a text file, and/or still another type of suitable file format. 
     At step  1510 , the search system is configured to receive report criteria including at least one of (i) a start date and/or time (e.g., via start date and time box  910 , etc.), (ii) an end date and/or time (e.g., via end date and time box  920 , etc.), (iii) a report type (e.g., via report type box  930 , etc.), and/or an export type (e.g., via export type box  940 , etc.) from the operator. At step  1512 , the search system is configured to generate a report to be downloaded onto the user device of the operator based on (i) the start date and time, (ii) the end date and time, (iii) the report type, (iv) the export type, and/or (v) the one or more selected rows. At step  1514 , the search system is configured to receive a request to export and download the report in the selected export type onto the user device. The report may thereafter be saved, viewed, manipulated, printed, etc. via the user device. In some embodiments, the search system is configured to facilitate saving the report for future use. In some embodiments, the search system is configured to facilitate scheduling a report for future generation (e.g., periodic report generation, etc.). 
     Referring to  FIG. 16 , a method  1600  for performing a bulk command process on a plurality of items from global search results is shown according to an exemplary embodiment. According to an exemplary embodiment, method  1600  is an extension of method  1100 . By way of example, the operator may provide a bulk command to a plurality of the search results displayed by the search system (e.g., after step  1118 , step  1122 , etc.). At step  1602 , the search system is configured to receive a selection of a plurality of rows from the search results in the results area. At step  1604 , the search system is configured to receive a selection of an “actions” button (e.g., actions button  680 , etc.) in the filter area which causes the search system to display an actions drop-down menu. At step  1606 , the search system is configured to receive a selection of a “bulk command” button (e.g., bulk command button  682 , etc.) in the actions drop-down menu. 
     At step  1608 , the search system is configured to provide a “bulk command” modal window (e.g., bulk command modal window  800 , etc.) over the search results (e.g., in the same window as search GUI  600 , etc.). The bulk command modal window may provide various interfaces that include fillable, selectable, and/or drop-down dialog boxes that are configured to receive various information or parameters used for providing a command to each of the items associated with the plurality of selected rows. 
     At step  1610 , the search system is configured to determine whether a bulk command process is capable of being applied to one or more of the items associated with the plurality of selected rows. At step  1612 , the search system is configured to display a notification indicating that the bulk command process cannot be completed for the selected rows within the bulk command modal window in response to determining that the bulk command process cannot be applied to one or more of the items associated with the plurality of selected rows. At step  1614 , the search system is configured to provide a command interface (e.g., command interface  810 , etc.) on the bulk command modal window in response to determining that the bulk command process can be applied to one or more of the items associated with the plurality of selected rows. The command interface may include a command button (e.g., command button  812 , etc.), a value button (e.g., value button  814 , etc.), and an expiration section (e.g., expiration section  816 , etc.). The command button may facilitate the operator with inputting and/or selecting an available command (e.g., common commands provided to the selected items, etc.) to provide to one or more of the items associated with the plurality of selected rows. The value button may facilitate the operator with providing a value (e.g., active, inactive, an operating parameter, etc.) for the command to one or more of the items associated with the plurality of selected rows. The expiration section may facilitate the operator with providing a duration for the command to remain in effect before expiring. 
     At step  1616 , the search system is configured to receive command criteria (e.g., via the command box, the value box, the expiration section, etc.) regarding a bulk command to provide to the one or more items. In some embodiments, the search system is configured to proceed to steps  1618 - 1622 . In some embodiments, the search system is configured to proceed to step  1624 . At step  1618 , the search system is configured to provide a type interface on the bulk command modal window in response to determining the plurality of selected rows are associated with different types of items. The type interface may provide an indication of the different types of items and what can be performed dependent upon the type of item. At step  1620 , the search system is configured to receive type criteria from the operator (e.g., a selection of at least one of the types provided, etc.). At step  1622 , the search system is configured to determine which of the items the bulk command can be applied to based on the type criteria. 
     At step  1624 , the search system is configured to provide a preview interface (e.g., preview interface  830 , etc.) on the bulk command modal window. The preview interface may provide an indication of the number of items the bulk command will affect, the command being provided, the type (if applicable), a table showing the items that will be affected (e.g., object, name, item reference, present value, etc.), etc. At step  1626 , the search system is configured to receive an indication from the operator to proceed with the bulk command. At step  1628 , the search system is configured to provide the bulk command to the items associated with the plurality of selected rows. At step  1630 , the search system is configured to provide a confirmation interface (e.g., confirmation interface  850 , etc.) on the bulk command modal window. The confirmation interface may provide the number of items the bulk command affected, the command that was provided, a table showing successful commands and failed commands, etc. 
     Global Search and Control Processes 
     Referring now to  FIG. 19 , a flowchart of a process  1900  for searching using aliased points and equipment definitions is shown, according to an exemplary embodiment. In some embodiments, process  1900  is performed by one or more components of global search and control system  500 . For example, process  1900  can be performed by search module  512  and/or report module  518  as described with reference to  FIGS. 5-18 . In some embodiments, process  1900  is performed in response to a user submitting a query via search GUI  600 . In other embodiments, process  1900  can be triggered by an automated process or algorithm to identify and/or command relevant points and/or equipment (described in greater detail with reference to  FIGS. 20-21 ). 
     Process  1900  is shown to include receiving a query specifying an equipment type, a location, and/or a point type (step  1902 ). In some embodiments, the query is submitted by a user via search GUI  600 . The user can specify an equipment type or location via space and equipment box  610 , or can select an equipment model associated with a particular type of equipment via equipment definition button  630 . The user can specify a point type by selecting one or more of aliased points  648  displayed in dropdown menu  642  or by selecting a particular type of point object via object type button  620 . For example, suppose the user wants to see all of the zone temperature setpoints for any variable air volume (VAV) unit that serves Floor A. The user can interact with search GUI  600  to specify the equipment type “VAV,” the location “Floor A,” and the point type “ZNT-SP.” In various other embodiments, the query parameters (i.e., equipment type, location, and/or point type) can be specified using any other type of input. For example, the query parameters can be specified by an automated process or algorithm and provided as an input to process  1900 . 
     Process  1900  is shown to include identifying 1 to N equipment serving the specified location (step  1904 ). The equipment identified in step  1904  may include any type of equipment that directly or indirectly serves the location specified in step  1902 . For example, if the location is specified as Floor A, step  1904  may include identifying any equipment that monitors, controls, affects, or otherwise interacts with Floor A. The equipment may include VAV units that regulate airflow to Floor A, AHUs that provide airflow into Floor A, chillers or boilers that provide a heated or chilled fluid for use in heating or cooling Floor A, sensors that measure the temperature, pressure, or other environmental condition of Floor A, or any other type of equipment that interacts with Floor A either directly or indirectly. In some embodiments, step  1904  includes identifying the equipment models for all equipment and reading a “Spaces/Equipment” attribute of each equipment model to determine which of the equipment serves the specified location. 
     Process  1900  is shown to include sub-filtering the identified equipment by the specified equipment type (step  1906 ). Step  1906  may include filtering the set of equipment identified in step  1904  to include only equipment having the equipment type specified in step  1902 . For example, if the equipment type specified in step  1902  is “VAV,” step  1906  may include filtering the set of equipment identified in step  1904  to include only VAVs. Accordingly, any equipment having an equipment type not matching the specified equipment type may be removed or filtered from the set of equipment identified in step  1904 . In some embodiments, step  1906  includes identifying the equipment models for all equipment identified in step  1904  and reading a “Type” attribute of each equipment model to determine which of the equipment have the specified equipment type. 
     Process  1900  is shown to include using equipment serving relationships to recursively identify all equipment serving the specified location or child spaces of the specified location (step  1908 ). Step  1908  may include identifying any child locations contained within the specified location. For example, if the specified location is “Floor A,” step  1908  may include identifying any zones, rooms, or other spaces located on Floor A. In some embodiments, each space within a building is represented by a data object that contains various attributes (e.g., “contains,” “contained by,” etc.). The data object that represents Floor A may have a “contains” attribute which identifies any child spaces located within or on Floor A. Each of those child spaces may also have a “contains” attribute which identifies any smaller child spaces located within the corresponding larger child space (e.g., a room within a particular zone). Step  1908  can be performed recursively to identify all of the child spaces located within the specified location at any level of the space hierarchy (e.g., building, floor, zone, room, etc.). Once the set of spaces has been generated, step  1908  can filter the set of equipment generated in step  1906  to include only the equipment that serves the specified location (e.g., “Floor A”) or any of the child spaces within the specified location. For example, the set of VAVs generated in step  1906  can be filtered to include only the VAVs that serve Floor A or any of the child spaces within Floor A. 
     Process  1900  is shown to include determining whether all equipment have been identified (step  1910 ). Step  1910  may include determining whether any of the spaces identified in step  1908  have child spaces and whether any of the equipment identified in step  1906  serves any of those child spaces. If any of the spaces identified in step  1908  have child spaces, step  1908  can be repeated for those child spaces. Steps  1908  and  1910  can be repeated recursively until all child spaces within the specified location have been identified and all equipment (of the specified type) that serve the specified location or any space within the specified location have been identified. For example, if the specified location is “Floor A,” steps  1908  and  1910  can be performed once to identify all of the equipment that serve Floor A (e.g., have a “serves” attribute that explicitly identifies Floor A). If Floor A contains any child spaces (e.g., Zone X, Zone Y, and Zone Z), steps  1908  and  1910  can be repeated to identify any equipment that serves the child spaces located within Floor A. If any of those child spaces contain further child spaces (e.g., Zone X contains Room P and Room Q, Zone Y contains Room R, etc.), steps  1908  and  1910  can be repeated again until the identified child spaces contain no further child spaces. Once all equipment have been identified, process  1900  may proceed to step  1912 . 
     Process  1900  is shown to include, for each equipment identified, reference the equipment definition point type attribute for the equipment to identify all points having the specified point type (step  1912 ). Step  1912  may include identifying the equipment model for each equipment identified in steps  1908  and  1910 . Each equipment model may specify a set of points having various point types. Step  1912  may include searching the point types specified by the equipment models to find any points having the point type specified in step  1902 . For example, if the point type specified in step  1902  is “zone temperature set point” or “ZNT-SP,” step  1912  may include searching the point types or point names specified by the equipment definitions for the string “#ZNT-SP” where the “#” symbol is a wild card. Accordingly, the search performed in step  1912  may identify all of the zone temperature set points for the set of VAVs that serve Floor A or any child space within Floor A. 
     Process  1900  is shown to include normalizing the values of the identified points based on other equipment attributes (step  1914 ) and presenting a list of the identified points and normalized values as a result of the query (step  1916 ). The normalization performed in step  1914  can normalize the values of the search results to account for differences between equipment from different manufacturers or having different models. For example, the set of point values can be normalized to have the same units, the same scale, the same offset, etc. Once the point values have been normalized, a list of the normalized point values can be generated and output as a result of the query. The query result can be displayed to a user via search GUI  600  (e.g., in results section  700 ) or provided as a data output to an automated process or algorithm that triggered process  1900  to be performed. 
     Although process  1900  is described in the context of finding zone temperature setpoints for VAV units, it should be understood that the VAV setpoint example is merely one of a large set of potential use cases that are enabled by process  1900 . For example, process  1900  can be performed to find any type of points, equipment, or spaces within a building or building system. It is appreciated that process  1900  can be applied to any equipment type (e.g., HVAC, lighting, security, fire, etc.) based on the equipment type specified in step  1906  and any point type (e.g., temperature setpoints, measured values, operating parameters, etc.) based on the point type specified in step  1912 . 
     Referring now to  FIG. 20 , a flowchart of a process  2000  for automatically implementing a control strategy is shown, according to an exemplary embodiment. In some embodiments, process  2000  is performed by one or more components of global search and control system  500 . For example, process  2000  can be performed by search module  512 , command module  514 , modification module  516 , and/or report module  518  as described with reference to  FIGS. 5-18 . In some embodiments, process  2000  is performed automatically by global search and control system  500  without requiring any user intervention. 
     Process  2000  is shown to include receiving input invoking a control strategy (step  2002 ). In some embodiments, step  2002  includes receiving a user input that invokes the control strategy. For example, a user can select a checkbox provided via a graphical user interface to enable a corresponding control strategy. As another example, the user input may be provided via a user interface into a natural language processing system. One example of such a control strategy is an energy optimization strategy in which energy savings are achieved by widening temperature setpoints for a building or portion of a building. The control strategy can be invoked across an entire building or a portion of a building (e.g., one or more floors, zones, rooms, etc.) based on the parameters and scope of the control strategy. In other embodiments, step  2002  includes receiving a control signal from a supervisory controller or other automated system or process. For example, step  2002  may include receiving an input from a supervisory controller that causes a controlled system to switch into a different operating mode (e.g., an energy saving mode, a low power mode, etc.) or transition into a different operating state. 
     Process  2000  is shown to include defining outputs of the control strategy including equipment type, location, and/or point type (step  2004 ). Step  2004  may include defining a particular type of point that needs to be modified to implement the control strategy. For example, if the control strategy is an energy optimization strategy that widens zone temperature setpoints, step  2004  may include generating one or more parameters that define the zone temperature setpoints. The points to be modified can be defined in terms of equipment type, location, and/or point type. For example, the zone temperature setpoints can be specified as temperature setpoints for VAV units that control airflow into a particular location where the control strategy will be implemented. In some embodiments, the outputs of the control strategy are defined using the same parameters that are specified as inputs to process  1900 . 
     Process  2000  is shown to include performing a query to find all points that meet the definition of the outputs (step  2006 ). Step  2006  may include automatically performing process  1900  using the query parameters generated in step  2004 . Advantageously, process  1900  can be automatically triggered and performed as part of step  2006  without requiring a user to specify query parameters. The outputs of step  2006  may include a list of points that meet the point definitions generated in step  2004 . For example, for the control strategy that widens zone temperature setpoints for a specified building space, the outputs of step  2006  may include a list of VAV zone temperature setpoints for all VAV units that serve the specified building space. 
     Process  2000  is shown to include automatically modifying values of the output points returned as results of the query to implement the control strategy (step  2008 ). Step  2008  may include adjusting the values of the points in a manner consistent with the control strategy. For example, if the control strategy involves widening zone temperature setpoints, step  2008  may include increasing a maximum temperature setpoint and/or decreasing a minimum temperature setpoint to expand the allowable temperature range for a building or portion thereof. In this way, process  2000  can automatically implement the control strategy by modifying the required points without requiring any additional user action or custom programming. 
     Referring now to  FIG. 21 , a flowchart of a process  2100  for automatically adapting a control strategy to account for a changed configuration of building equipment and/or building spaces is shown, according to an exemplary embodiment. In some embodiments, process  2100  is performed by one or more components of global search and control system  500 . For example, process  2100  can be performed by search module  512 , command module  514 , modification module  516 , and/or report module  518  as described with reference to  FIGS. 5-18 . In some embodiments, process  2100  is performed automatically by global search and control system  500  without requiring any user intervention. 
     Process  2100  is shown to include changing a configuration of building equipment and/or a configuration of building spaces (step  2102 ). Step  2102  may include adding new equipment to a building, replacing older building equipment with newer building equipment, removing equipment from a building, upgrading the firmware or system software installed on building equipment, adding new capabilities to building equipment, installing additional components in building equipment (e.g., a new sensor), or otherwise making changes to the number, type, and/or settings of building equipment. One example of changing the configuration of building equipment is installing several new VAV units on a particular floor of a building. Each VAV unit can be associated with an equipment definition that specifies the location served by the VAV unit. Another example of changing the configuration of the building equipment is adding a discharge air temperature sensor or an energy meter after the original equipment is installed and configured in the building. If the sensor becomes available (or set of sensors, parts, components, etc.), the system can be reconfigured based on new data points being available in the equipment objects, and subsequently the equipment definition/profile. Step  2102  may additionally or alternatively include changing the configuration of the space(s) within the building (with or without changing, updating, replacing, removing, or otherwise altering the building equipment already present in the space or building). For example, a café may be converted into office spaces (e.g., with a new space mapping, office walls may be constructed throughout the space that were not previously present, etc.). In such an instance, the BMS may be self-healing and apply new/updated strategies based on updated equipment-to-space mappings received thereby. 
     Process  2100  is shown to include invoking a control strategy that uses the building equipment (step  2104 ). In some embodiments, step  2104  includes receiving a user input that invokes the control strategy. For example, a user can select a checkbox provided via a graphical user interface to enable a corresponding control strategy. As another example, the user input may be provided via a user interface into a natural language processing system. One example of such a control strategy is an energy optimization strategy in which energy savings are achieved by widening temperature setpoints for a building or portion of a building. The control strategy can be invoked across an entire building or a portion of a building (e.g., one or more floors, zones, rooms, etc.) based on the parameters and scope of the control strategy. As another example, the user may provide a new space mapping for the building or space in the building. In other embodiments, step  2104  includes receiving a control signal from a supervisory controller or other automated system or process. For example, step  2104  may include receiving an input from a supervisory controller or other system that causes a controlled system to switch into a different operating mode (e.g., an energy saving mode, a low power mode, etc.), transition into a different operating state, and/or adapt to a new space mapping (e.g., in response to receiving the new space mapping as an input, etc.). 
     Although the control strategy invoked in step  2104  uses the building equipment, the control strategy can be defined in a general manner without requiring knowledge of the specific devices of equipment that the control strategy will use. For example, the control strategy can be defined as a control strategy for adjusting the temperature setpoints for all VAV units that serve a specified location without requiring knowledge of the exact number, names, locations, or other parameters of the VAV units that serve the specified location. In some embodiments, the control strategy is defined using the same parameters that are specified as inputs to process  1900 . In this way, the same control strategy can be executed before and after the configuration of the building equipment changes in step  2102 . Each time the control strategy is executed, steps  2106  and  2108  can be performed to dynamically identify the specific equipment that the control strategy will use without requiring any input from a user to adapt the control strategy to use the additional equipment. 
     Process  2100  is shown to include performing a query to find all equipment/points used by the control strategy, including new or changed equipment/points, if any (step  2106 ). Step  2106  may include automatically performing process  1900  using the query parameters that define the control strategy (e.g., equipment type, location, point type). Advantageously, process  1900  can be automatically triggered and performed as part of step  2106  without requiring a user to specify query parameters. The outputs of step  2106  may include a list of equipment/points that are related or associated with the change in the configuration (e.g., space configuration, equipment configuration, etc.) and used by the control strategy. For example, for the control strategy that widens zone temperature setpoints for a specified building space, the outputs of step  2106  may include a list of VAV units that serve the specified space and/or zone temperature setpoints for all VAV units that serve the specified building space. As another example, the control strategy that updates equipment control based on a new space configuration, the output of step  2016  may include a list of equipment that serve each space in the new space configuration. 
     Process  2100  is shown to include automatically operating the equipment and/or modifying points returned as results of the query to execute the control strategy (step  2108 ). Step  2108  may include adjusting the values of the points in a manner consistent with the control strategy. For example, if the control strategy involves widening zone temperature setpoints, step  2108  may include increasing a maximum temperature setpoint and/or decreasing a minimum temperature setpoint to expand the allowable temperature range for a building or portion thereof. As another example, if the control strategy involves adapting to a new equipment-to-space mapping, step  2108  may include identifying the equipment that serve each of the spaces of the new equipment-to-space mapping (based on the query in step  2106 ), identifying the equipment definitions/profiles for the equipment to understand if there are like pieces of equipment, identify if the equipment is serving or is served by other equipment, and then utilizing the definition/profile of the equipment to modify one of, or a set of, the same type of point on each one of the equipment to accommodate the new equipment-to-space mapping. In this way, process  2100  can automatically implement the control strategy by modifying the required points without requiring any additional user action or custom programming. 
     Configuration of Exemplary Embodiments 
     The construction and arrangement of the systems and methods as shown in the various example embodiments are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.). For example, the position of elements can be reversed or otherwise varied and the nature or number of discrete elements or positions can be altered or varied. Accordingly, all such modifications are intended to be included within the scope of the present disclosure. The order or sequence of any process or method steps can be varied or re-sequenced according to alternative embodiments. Other substitutions, modifications, changes, and omissions can be made in the design, operating conditions and arrangement of the example embodiments without departing from the scope of the present disclosure. 
     The present disclosure contemplates methods, systems and program products on any machine-readable media for accomplishing various operations. The embodiments of the present disclosure can 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 can be performed concurrently or with partial concurrence. Such variation will depend on the software and hardware systems chosen and on designer choice. All such variations are within the scope of the disclosure. Likewise, software implementations could be accomplished with standard programming techniques with rule based logic and other logic to accomplish the various connection steps, processing steps, comparison steps and decision steps.