EP3711262A1

EP3711262A1 - Building energy management system

Info

Publication number: EP3711262A1
Application number: EP18812011.7A
Authority: EP
Inventors: Rajesh C. NAYAK; Mukul V. Vashisth; Kaustubh DEVASTHALI; Fajil Sutar; Jayesh Shirish PATIL; Sujit Fulse; Abhigyan Chatterjee; Barkha SHAH; Dilip Divila Raju; Ashok Sridharan; Satish Pandhari Vaidya
Original assignee: Johnson Controls Technology Co
Current assignee: Johnson Controls Tyco IP Holdings LLP
Priority date: 2017-11-15
Filing date: 2018-11-13
Publication date: 2020-09-23
Also published as: WO2019099367A1

Abstract

Systems and methods of automatic synchronization of point read frequency are provided. The system can include data sources that receive data point values at respective deposit frequencies and a building enterprise managing device that performs an automatic synchronization process. The building enterprise managing device can receive a user configuration setting indicating a read frequency and obtain the data point values from a data source at the read frequency. The building enterprise managing device can identify a deposit frequency at which the data point values are received at the data source. The building enterprise managing device can determine whether the read frequency matches the deposit frequency. The building enterprise managing device can adjust the read frequency to match the deposit frequency in response to determining that the read frequency does not match the identified deposit frequency and obtain the data point values from the data source at the adjusted read frequency.

Description

BUILDING ENERGY MANAGEMENT SYSTEM

CROSS-REFERENCE TO RELATED APPLICATIONS

[0001] This application claims priority to and the benefit of Indian Provisional Patent Application No. 201741040766 filed November 15, 2017, Indian Provisional Patent Application No. 201721040778 filed November 15, 2017, Indian Provisional Patent Application No. 201741040785 filed November 15, 2017, Indian Provisional Patent Application No. 201741040781 filed November 15, 2017, Indian Provisional Patent Application No. 201741040780 filed November 15, 2017, U.S. Patent Application No. 16/026,621 filed July 3, 2018, U.S. Patent Application No. 16/051,992 filed August 1, 2018, U.S. Patent Application No. 16/052,038 filed August 1, 2018, U.S. Patent Application No. 16/052,083 filed August 1, 2018, and U.S Patent Application No. 16/052,115 filed

August 1, 2018. The entire disclosure of these patent applications is incorporated by reference herein.

BACKGROUND

[0002] The present disclosure relates generally to a building management system (BMS) and more particularly to a BMS with automatic synchronization of data point frequency. 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 heating, ventilating, and air conditioning (HV.AC) 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.

[0003] A BMS may involve monitoring facilities/buildings within a portfolio which might be located in disparate geographies. The BMS may need to ingest data points from many sources to get data and derive meaningful insights. When mapping a large number of data points (e.g., several thousand or more), there may be difficulty in synchronizing the read frequency to match that which is coming from the data source. If not done right, for example due to the mismatch of time stamps, the data will not be fetched at the required time from the data source. In existing systems, the read frequency is generally configured manually, which is a time-consuming and difficult process. SUMMARY

[0004] One implementation of the present disclosure is a system including a plurality of data sources and a building enterprise managing device. Each of the plurality of data sources can be configured to receive respective data point values associated with a respective data point at a respective deposit frequency. The building enterprise managing device can be configured to perform an automatic synchronization process. The building enterprise managing device can receive a user configuration setting comprising a read frequency at which data point values are to he obtained by the building enterprise managing device from a data source among the plurality of data sources. The building enterprise managing device can obtain, via a network, the data point values from the data source at the read frequency. The building enterprise managing device can identify a deposit frequency at which the data point values are received at the data source by analyzing the obtained data point values. The building enterprise managing device can determine whether the read frequency matches the identified deposit frequency. The building enterprise managing device can adjust the read frequency to match the identified deposit frequency in response to determining that the read frequency does not match the identified deposit frequency. The building enterprise managing device can obtain, via the network, the data point values from the data source at the adjusted read frequency.

[0005] In some embodiments, the building enterprise managing device can be configured to repeat the automatic synchronization process according to a predetermined frequency. In some embodiments, the predetermined frequency is one day.

[0006] In some embodiments, the building enterprise managing device can identify the deposit frequency by analyzing historical data relating to previous data point values. In some embodiments, each data point value can include a timestamp.

[0007] In some embodiments, the data source can include a data repository, and the data point values can be deposited at the deposit frequency into the data repository of the data source. In some embodiments, the building enterprise managing device can identify the deposit frequency by scanning for an interval that the data point values are deposited into the data repository of the data source

[0008] In some embodiments, the data source can correspond to a HVAC equipment.

[0009] In some embodiments, the plurality of data sources are first data sources and the system can further include a plurality of second data sources. Each of the second data sources can provide the respective data point values to the respective first data source at the respective deposit frequency.

[0010] Another implementation of the present disclosure is a method for automatic synchronization. The method includes obtaining, by a building enterprise device having one or more processors, a user configuration setting comprising a read frequency at which data point values are to he read by the building enterprise device from a data source. The method includes obtaining, by the building enterprise device via a network, the data point values from the data source at the read frequency. The method includes identifying, by the building enterprise device, a deposit frequency at which the data point values are received at the data source by analyzing the obtained data point values. The method includes determining, by the building enterprise device, that the read frequency does not match the identified deposit frequency. The method includes adjusting, by the building enterprise device, the read frequency to match the identified deposit frequency in response to determining that the read frequency does not match the identified deposit frequency. The method includes obtaining, by the building enterprise device via the network, the data point values from the data source at the adjusted read frequency.

[0011] Another implementation of the present disclosure is an apparatus for automatic synchronization. The apparatus includes a processor and a memory coupled to the processor. The memory stores computer-executable instructions, which when executed by the processor, cause the apparatus to receive a user configuration setting comprising a read frequency at which data point values are to be read by the apparatus from a data source.

The computer-executable instructions, when executed by the processor, can cause the apparatus to obtain, via a network, the data point values from the data source at the read frequency and to identify a deposit frequency at which the data point values are received at the data source by analyzing the obtained data point values. The computer-executable instructions, when executed by the processor, can also cause the apparatus to determine that the read frequency does not match the identified deposit frequency and adjust the read frequency to match the identified deposit frequency. The computer-executable instructions, when executed by the processor, can further cause the apparatus to obtain, via the network, the data point values from the data source at the adjusted read frequency.

[0012] Another implementation of the present disclosure is a building management system. The building management system includes a plurality of meters configured to provide data samples of a plurality of points relating to a building. The building includes a plurality of spaces. Each of the points is associated with at least one of the plurality of spaces. The building management system also includes a space hierarchy database configured to store a sibling relationship for each of the points. Each sibling relationship identifies two or more of the points as sibling points. The building management system also includes a batch metrics engine configured to receive a first data sample of a first point, access the sibling relationship for the first point to identify one or more sibling points of the first point, aggregate the first data sample with one or more other data samples of the sibling points to generate a batch, and calculate an aggregate metric using the first data sample and the one or more other data samples in the batch. The building management system also includes a controller configured to adjust an operation of building equipment based on the aggregate metric. The building equipment is operable to affect the plurality of points.

[0013] In some embodiments, the first point is provided by a first meter of the plurality of meters and the one or more sibling points are provided by one or more sibling meters of the plurality of meters. The first meter is associated with a first space and the one or more sibling meters are associated with one or more sibling spaces. The first space and the one or more sibling spaces are located within a common parent space.

[0014] In some embodiments, the batch metrics engine is configured to generate the batch and calculate the aggregate metric in response to receiving the first data sample. In some embodiments, the building management system also includes a timeseries storage database configured to store the data samples of the plurality of points. Each of the data samples include a time stamp and a value of at least one of the one or more points

[0015] In some embodiments, the bath metrics engine is configured to aggregate the first data sample and the one or more data samples of the sibling points to generate the batch by determining a relevant time period for calculating the aggregate metric, selecting one or more of the data samples of the sibling points that have timestamps within the relevant time period in the timeseries storage database, and retrieving the selected data samples from the timeseries storage database.

[0016] In some embodiments, the building management system also includes a current metrics database configured to store the aggregate metric. In some embodiments, the building analytics and presentation circuit is configured to access the aggregate metric in the current metrics database and generate a graphical user interface that presents the aggregate metric to a user. [0017] In some embodiments, the building management system also includes a building analytics and presentation circuit configured to access the aggregate metric and a plurality of additional metrics in the current metric database and calculate an advanced metric based on the aggregate metric and the plurality of additional metrics.

[0018] Another implementation of the present disclosure is a method for managing a building. The method includes providing, by a plurality of meters, data samples of a plurality of points relating to the building. The building includes a plurality of spaces.

Each of the points is associated with at least one of the plurality of spaces. The method also includes storing, by a space hierarchy database, a sibling relationship for each of the points. Each sibling relationship identifies two or more of the points as sibling points. The method also includes receiving, at a batch metrics engine, a first data sample of a first point, accessing, by the batch metrics engine, the space hierarchy database to identify one or more sibling points of the first point based on the sibling relationship for the first point, aggregating, by the batch metrics engine, the first data sample with one or more other data samples of the sibling points to generate a batch, calculating, by the batch metrics engine, an aggregate metric using the first data sample and the one or more data samples in the batch, and adjusting an operation of building equipment based on the aggregate metric to affect the plurality of points.

[0019] In some embodiments, the first point is provided by a first meter of the plurality of meters and the one or more sibling points are provided by one or more sibling meters of the plurality of meters. The first meter is associated with a first space and the one or more sibling meters are associated with one or more sibling spaces. The first space and the one or more sibling spaces are located within a common parent space.

[0020] In some embodiments, receiving the first data sample triggers the batch metrics engine to generate the batch and calculate the aggregate metric using the data samples in the batch. In some embodiments, the method includes storing the data samples provided by the plurality of points in a timeseries storage database. Each of the data samples includes a time stamp and a value of at least one of the plurality of points.

[0021] In some embodiments, aggregating, by the batch metrics engine, the first data sample and the one or more data samples of the sibling points to generate the batch includes determining a relevant time period for calculating the aggregate metric, selecting one or more of the data samples of the sibling points that have timestamps within the relevant time period in the timeseries storage database, and retrieving the selected data samples from the timeseries storage database

[0022] In some embodiments, the method also includes storing the aggregate metric in a current metrics database. In some embodiments, the method also includes accessing the aggregate metric in the current metrics database and generating a graphical user interface that presents the aggregate metric to a user.

[0023] In some embodiments, the method also includes accessing the aggregate metric and a plurality of additional metrics in the current metric database and calculating an advanced metric based on the aggregate metric and the plurality_' of additional metrics.

[0024] Another implementation of the present disclosure is a method for managing a building. The method includes collecting, by a plurality of meters, data samples

corresponding to a plurality of points associated with a plurality of spaces of the building. The spaces are arranged in a space hierarchy. The method also includes determining sets of sibling points based on the space hierarchy. Each set of sibling points corresponds to a metric for a space in the space hierarchy. The method also includes aggregating, for each set of sibling points, data samples corresponding to the sibling points, calculating the metrics based on the aggregated data samples to generate calculated values for the metrics, and controlling building equipment based on the calculated metrics to operate to affect a variable state or condition of the building.

[0025] In some embodiments, the method also includes storing the calculated values for the metrics in a database, receiving a request from a user to view one or more of the metrics, in response to the request, retrieving the calculated values for the one or more metrics from the database, and providing the calculated values for the one or more metrics on a graphical user interface.

[0026] In some embodiments, the method includes associating each data sample with a time stamp and a point, and storing the data sample, the time stamp, and the point in a timeseries storage database. In some embodiments, aggregating, for each set of sibling points, data samples corresponding to the sibling points includes determining a relevant time period for calculating a first metric, and identifying the data samples from the relevant time period based on the time stamps.

[0027] Another implementation of the present disclosure is a building management system. The building management system includes at least one of a meter or equipment configured to provide data samples for a point and a point mapping system. The point mapping system is configured to store a point object corresponding to the point and including a unit attribute, store a template object corresponding to a building equipment metric and including an allowed units attribute, access the point object to read the unit attribute, access the template object to read the allowed units attribute, in response to a request to map the point object to the template object, determine whether the unit attribute matches the allowed units atribute, and, in response to a determination that the unit attribute matches the allowed units attribute, automatically map the point object to the template object. The building management system also includes a system manager configured to calculate the building equipment metric using the samples for the point in response to mapping the point object to the template object and operate building equipment using the building equipment metric to affect a variable state or condition of a building.

[0028] In some embodiments, the point mapping system is configured to prevent the mapping of the point object to the template object in response to a determination that the unit attribute does not match the allowed units attribute. In some embodiments, mapping the point object to the template object includes updating a mapping attribute of the point object to reference the template object.

[0029] In some embodiments, the building management system includes a graphical user interface generator to generate a graphical user interface that allows a user to input the request to map the point object to the template object. In some embodiments, the graphical user interface generator is configured to provide an error notification on the graphical user interface in response to a determination that the unit attribute does not match the allowed units atribute.

[0030] In some embodiments, the graphical user interface includes a points tree widget that includes a list of a plurality of points and an equipment template tree widget that includes a list of a plurality of templates. The graphical user interface allows a user to drag the point from the list of the plurality of points onto a template in the list of the plurality of templates to input the request to map the point object to the template object.

[0031] In some embodiments, the allowed units attributes identifies a plurality of allowed units and the unit attribute identifies a first unit. The point mapping validation circuit may be configured to determine whether the unit atribute matches the allowed units attribute by determining whether the plurality of allowed units comprise the first unit. [0032] Another implementation of the present disclosure is a method for managing a building. The method includes providing, by a meter, data samples for a point, and storing, by a point mapping system, a point object corresponding to the point. The point object includes a unit attribute. The method also includes storing, by the point mapping system, a template object corresponding to a building equipment metric. The template object includes an allowed units attribute. The method also includes accessing the point object to read the unit attribute, accessing the template object to read the allowed units attribute, determining whether the unit attribute matches the allowed units attribute in response to a request to map the point object to the template object, automatically mapping the point object to the template object in response to a determination that the unit attribute matches the allowed units attribute, calculating, by a system manager, a building equipment metric using the samples for the point in response to mapping the point object to the template object, operating building equipment using the building equipment metric to affect a variable state or condition of the building.

[0033] In some embodiments, the method includes preventing, in response to a determination that the unit attribute does not match the allowed units attribute, a mapping of the storage the point object to the template object. In some embodiments, mapping the point object to the template object comprises updating a mapping attribute of the point object to reference the template object.

[0034] In some embodiments, the method includes generating a graphical user interface that allows a user to input a request to map the point object to the template object. In some embodiments, the method includes providing an error notification on the graphical user interface in response to a determination that the unit attribute does not match the allowed units attribute

[0035] In some embodiments, the method includes providing, on the graphical user interface, a points tree widget that includes a list of a plurality of points and an equipment template tree widget that includes a list of a plurality of templates, and allowing, on the graphical user interface, a user to drag the point from the list of the plurality of points onto a template in the list of the plurality of templates to input the request to map the point object to the template object.

[0036] In some embodiments, the allowed units attribute identifies a plurality of allowed units and the unit attribute identifies a first unit. Determining whether the unit attribute matches the allowed units attribute includes determining whether the plurality of allowed units compri se the first unit.

[0037] Another implementation of the present disclosure is a building management system. The building management system includes building equipment operable to affect a vari able state or condition of a building, a meter configured to provide data samples for a point, the point relating to the building equipment, and a point mapping system. The point mapping system includes a point object database configured to store a point object corresponding to the point. The point object includes a unit attribute. The point mapping system also includes a template object database configured to store a template object corresponding to a building equipment metric. The building equipment metric includes an allowed units attribute. The point mapping system also includes a point mapping validation circuit configured to receive a user request to map the point to the template, access the point object to read the unit attribute, access the template object to read the allowed units attribute, in response to the request to map the point to the template, determine whether the unit attribute matches the allowed units attribute, and in response to a determination that the unit attribute matches the allowed units attribute, automatically map the point object to the template object. The building management system also includes a system manager configured to calculate the building equipment metric using the samples for the point in response to mapping the point object to the template object and control the building equipment using the building equipment metric to affect a variable state or condition of a building

[0038] In some embodiments, the point mapping validation circuit is further configured to, in response to a determination that the unit attribute does not match the allowed units attribute, prevent a mapping of the point object to the template object. In some

embodiments, the building management system also includes a graphical user interface generator configured to generate a graphical user interface that allows a user to input the user request.

[0039] In some embodiments, the graphical user interface includes a points tree widget that includes a list of a plurality of points and an equipment template tree widget that includes a list of a plurality of templates. The graphical user interface allows a user to drag the point from the list of the plurality of points onto the template in the list of the plurality of templates to input the request to map the point object to the template object. [0040] In some embodiments, the allowed units attribute identifies a plurality of allowed units and the unit attribute identifies a first unit. The point mapping validation circuit is configured to determine whether the unit attributed matches the allowed units attributed by determining whether the plurality of allowed units comprise the first unit.

[0041] Another implementation of the present disclosure is a building management system. The building management system includes a meter configured to provide data samples of a real point. The real point corresponds to a first physical parameter measured by the meter. The building management system also includes an analytics circuit configured to store a real point object representing the real point and store a meter object representing the meter. The meter object includes a points attribute that lists one or more point objects associated with the meter object including at least the real point object. The analytics circuit is also configured to store a virtual point object representing a virtual point. The virtual point corresponds to a second physical parameter not measured by the meter. The analytics circuit is also configured to update the points attribute in the meter object to list the virtual point object as one of the point objects associated with the meter object, receive a data sample of the real point from the meter, calculate a value of the virtual point, and calculate a metric based on the data sample of the real point and the value of the virtual point. The building management system also includes a system manager configured to control building equipment using the metric to affect the first physical parameter and the second physical parameter.

[0042] In some embodiments, the analytics circuit is configured to calculate the value of the virtual point using a formula stored in the virtual point object. In some embodiments, the analytics circuit is configured to calculate the value of the virtual point using a formula stored in the virtual point object. In some embodiments, the formula defines the value of the virtual point as a function of the data sample of the real point. In some embodiments, the first physical parameter and the second physical parameter characterize operation of the building equipment.

[0043] In some embodiments, the analytics circuit is further configured to generate a graphical user interface that includes a graphical representation of the operation of the building equipment. The graphical representation is generated based on the data sample of the real point and the value of the virtual point. In some embodiments, the graphical user interface comprises a first indicator identifying the real point as real and a second indicator identifying the virtual point as virtual. [0044] Another implementation of the present disclosure is a method for managing a building. The method includes collecting, by a meter, data samples of a real point. The real point corresponds to a first physical parameter measured by the meter. The method includes storing a real point object representing the real point and storing a meter object representing the meter. The meter object includes a points attribute that lists one or more point objects associated with the meter object including at least the real point object. The method includes storing a virtual point object representing a virtual point. The virtual point corresponds to a second physical parameter not measured by the meter. The method includes updating the points attribute in the meter object to list the virtual point object in as one of the point objects associated with the meter object, receiving a data sample of the real point from the meter, calculating a value of the virtual point, calculating a metric based on the data sample of the real point and the value of the virtual point, and controlling, based on the metric, building equipment to affect the first physical parameter and the second physical parameter.

[0045] In some embodiments, calculating the value of the virtual point includes storing a formula in the virtual point object and calculating the value using the formula. In some embodiments, the method includes generating a graphical user interface that allows the user to input the formula. In some embodiments, the formula defines the value of the virtual point as a function of the data sample for the real point. In some embodiments, the first physical parameter and the second physical parameter characterize operation of the building equipment.

[0046] In some embodiments, the method includes generating a graphical user interface that includes a graphical representation of the operation of the building equipment based on the data sample of the real point and the value of the virtual point. In some embodiments, the method includes providing, on the graphical user interface, a first indicator identifying the real point as real and a second indicator identifying the virtual point as virtual.

[0047] Another implementation of the present disclosure is a building management system. The building management system includes building equipment operable to affect a variable state or condition of a building, a plurality of meters configured to collect data samples of a plurality of real points relating to an operation of the building equipment, and an analytics circuit configured to generate a graphical user interface. The graphical user interface includes a points tree widget comprising a list of the plurality of real points, a meter distribution tree widget comprising a list of the plurality of meters, and a meter details widget configured to allow a user to add a virtual point to the list of real points. The analytics circuit is also configured to receive data samples of the plurality of real points, calculate a value of the virtual point, and calculate a metric based on the data samples of the plurality of real points and the value of the virtual point. The building management system also includes a system manager configured to control the building equipment based on the metric.

[0048] In some embodiments, the graphical user interface includes a virtual point definition widget configured to allow a user to input a formula that defines the virtual point. In some embodiments, the analytics circuit is configured to generate the value of the virtual point using the formula and a first data sample of a first real point of the plurality of real points. In some embodiments, the analytics circuit is configured to generate a graphical representation of an operation of the building equipment using the formula and the data samples of the plurality of real points.

[0049] In some embodiments, the virtual point definition widget comprises a formula field and a list of the plurality of real points. Each real point on the list of real points is selectable to add the real point to the formula field. The virtual point definition widget also includes a plurality of operator buttons. Each operator button is selectable to add an operator to the formula field. The formula includes one or more real points and one or more operators to defi ne the virtual point as a function of the one or more real points. In some embodiments, the analytics circuit is configured to check the formula input by the user for syntax errors.

[0050] Another implementation of the present disclosure is a building management system. The building management system includes building equipment located in a plurality of locations and configured to provide data relating to operation of the building equipment and a fault notification system. The fault notification system is configured to collect the data from the building equipment, detect a fault in the operation of the building equipment based on the data, identify a fault location of the fault from the plurality of locations, identify a user location of the user from the plurality of locations, determine whether the user location matches the fault location, and in response to a determination that the user location matches the fault location, provide a graphical user interface to a user. The graphical user interface identifies the fault. [0051] In some embodiments, the fault notification system is configured to prevent the user from accessing information about the fault in response to a determination that the user location does not match the fault location.

[0052] In some embodiments, the fault notification system is configured to verify the user location by receiving GPS coordinates of a user device from the user device receiving an IP address of the user device accessing a look-up table that associates a set of IP addresses with the GPS coordinates of the user device and determining whether the IP address of the user device is included in the set of IP addresses with the GPS coordinates of the user device.

[0053] In some embodiments, the fault notification system is configured to generate a fault data object for the detected fault and include the fault location as an attribute of the fault data object. In some embodiments, the fault notification system is configured to receive consent from the user to use a location of the user device and cause a GPS chip of the user device to activate and provide the GPS coordinates to the fault notification system in response to receiving the consent from the user.

[0054] Another implementation of the present disclosure is a method for managing and controlling building equipment. The method includes operating building equipment to provide data relating to operation of the building equipment. The building equipment is located in a plurality of locations. The method also includes detecting a fault in the operation of the building equipment based on the data, identifying a fault location of the fault from the plurality of locations identifying a user location of the user from the plurality of locations, determining whether the user location matches the fault location, and in response to a determination that the user location matches the fault location, providing a graphical user interface to a user. The graphical user interface provides information relating to the fault.

[0055] In some embodiments, the method includes preventing the user from accessing information about the fault in response to a determination that the user location does not match the fault location.

[0056] In some embodiments, the method also includes verifying the user location by receiving GPS coordinates of a user device from the user device, receiving an IP address of the user device, accessing a look-up table that associates a set of IP addresses with the GPS coordinates of the user device, and determining whether the IP address of the user device is included in the set of IP addresses with the GPS coordinates of the user device

[0057] In some embodiments, the method includes determining whether the user is authorized to access fault notifications for the fault location. In some embodiments, the method includes generating a fault data object for the detected fault and including the fault location as an attribute of the fault data object.

[0058] In some embodiments, identifying a user location of the user from the plurality of locations comprises receiving GPS coordinates of a user device from the user device and determining that the GPS coordinates of the user device are within a present distance of the GPS coordinates of a first location of the plurality of locations. In some embodiments, the method includes receiving consent from the user to use the location of the user device and causing a GPS chip of the user device to activate and provide the GPS coordinates in response to receiving the consent from the user.

[0059] Another implementation of the present disclosure is a building management system. The building management system includes building equipment located in a plurality of locations and configured to provide data relating to operation of the building equipment and a fault notification system. The fault notification system is configured to collect the data from the building equipment, detect a plurality of faults in the operation of the building equipment based on the data, identify, for each of the plurality of faults, a fault location from the plurality of locations, identify a user location of a user device from the plurality of locations by causing a GPS chip of the user device to activate and provide the user location to the fault notification circuit, identify a set of faults from the plurality of faults for which the fault location matches the user location, generate a graphical user i nterface that identifies each fault of the set of faul ts, and provide the graphical user interface to the user device.

[0060] In some embodiments, the graphical user interface includes a list of the faults from the set of faults. The list is organized based on a priority of each fault. In some embodiments, the graphical user interfaces includes a list of each of the plurality of faults. The set of faults for which the user locati on matches the fault location is positioned at a top of the list.

[0061] In some embodiments, the plurality of locations include a plurality of buildings and the building equipment is operable to affect variable states or conditions of the plurality of buildings. In some embodiments, the building equipment includes HVAC equipment. In some embodiments, the fault notification system is configured to receive a security token from the user device and, in response to receiving the security token, allow the user to access the graphical user interface.

BRIEF DESCRIPTION OF THE DRAWINGS

[0062] The accompanying drawings are not intended to be drawn to scale. Like reference numbers and designations in the various drawings indicate like elements. For purposes of clarity, not every component may be labeled in every' drawing. In the drawings:

[0063] FIG. 1 is a drawing of a building equipped with a HVAC system, according to some embodiments.

[0064] FIG. 2 is a block diagram of a waterside system which can be used to serve the building of FIG. I, according to some embodiments.

[0065] FIG. 3 is a block diagram of an airside system which can be used to serve the building of FIG. 1, according to some embodiments.

[0066] FIG. 4 is a block diagram of a building management system (BMS) which can be used to monitor and control the building of FIG. 1, according to some embodiments.

[0067] FIG. 5 is a block diagram of another BMS which can be used to monitor and control the building of FIG. 1, according to some embodiments.

[0068] FIG. 6 is a block diagram of a point mapping synchronization system, according to some embodiments.

[0069] FIG. 7 is a flow diagram depicting a method of automatic synchronization of point read frequency which can be performed by the BMSs of FIGS. 4-5, according to some embodiments.

[0070] FIG. 8 is flow diagram depicting a method of automatic synchronization of point read frequency, according to some embodiments.

[0071] FIG. 9 is a block diagram of a space hierarchy, according to some embodiments. [0072] FIG. 10 is a block diagram of a metric generation system, which can be

implemented as a component of the BMSs of FIGS. 4-5, according to some embodiments.

[0073] FIG. 1 1 is flowchart of a method of batch processing building metrics, which can be performed by the BMSs of FIGS. 4-5, according to some embodiments.

[0074] FIG. 12 is a block diagram of a point mapping system which can be used in the BMSs of FIGS. 4-5, according to some embodiments.

[0075] FIG. 13 is a flowchart depicting a method of automated point mapping validation which can be performed by the BMSs of FIGS. 4-5, according to some embodiments.

[0076] FIG. 14 is a depiction of an equipment configuration interface which can be generated by the BMSs of FIGS. 4-5, according to some embodiments

[0077] FIG. 15 is a block diagram of a BMS with a point virtualization circuit, according to some embodiments.

[0078] FIG. 16 is a block diagram of an object database which can be used in the BMSs of FIGS. 4-5, according to some embodiments.

[0079] FIG. 17 is a flowchart of a process for point virtualization under online meters, according to some embodiments

[0080] FIG. 18 is a depiction of a meter configuration interface which can be generated by the BMS of FIG. 15, according to some embodiments.

[0081] FIG. 19 is a depiction of virtual point definition widget which can be generated by the BMS of FIG. 15, according to some embodiments

[0082] FIG. 20 is a depiction of a building scorecard dashboard which can be generated by the BMS of FIG. 15, according to some embodiments.

[0083] FIG. 21 is a block diagram of an automated system for geolocation-based fault notification, which can be implemented as a component of the BMSs of FIGS. 4-5, according to some embodiments.

[0084] FIG. 22 is a flowchart of a method for presenting fault notifications based on a user’s location, which can be performed by the BMSs of FIGS. 4-5, according to some embodiments. [0085] FIG. 23 is a depiction of a building management dashboard with a fault notification indicator, which can be generated by the BMSs of FIGS. 4-5, according to some embodiments.

[0086] FIG. 24 is a depiction of a fault notification interface, which can be generated by the BMSs of FIGS. 4-5, according to some embodiments.

DETAILED DESCRIPTION

[0087] Following below are more detailed descriptions of various concepts related to, and implementations of systems, methods, and apparatuses of automatic synchronization of point read frequency. Before turning to the more detailed descriptions and figures, which illustrate the exemplary implementations in detail, it should be understood that the application is not limited to the details or methodology set forth in the descriptions or illustrated in the figures. It should also be understood that the terminology is for the purpose of description only and should not be regarded as limiting.

Building HVAC Systems and Building Management Systems

[0088] Referring now to FIGS. 1-5, several building management systems (BMS) and HVAC systems in which the systems and methods of the present disclosure can be implemented are shown, according to some embodiments. In brief overview, FIG. I show's a building 10 equipped with a HVAC system 100. FIG. 2 is a block diagram of a ^waterside system 200 which can be used to serve building 10. FIG. 3 is a block diagram of an airside system 300 which can be used to serve building 10. FIG. 4 is a block diagram of a B1V1S which can be used to monitor and control building 10. FIG. 5 is a block diagram of another BMS which can be used to monitor and control building 10.

Building and HVAC System

[0089] 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 B S 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.

[0090] The BMS that serves building 10 includes a 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 sendees for building 10. For example, HVAC system 100 is shown to include a waterside system 120 and an airside system 130. Waterside system 120 may provide a heated or chilled fluid to an air handling unit of airside system 130. Airside system 130 may use the heated or chilled fluid to heat or cool an airflow provided to building 10. An exemplary' waterside system and airside system which can be used in HVAC system 100 are described in greater detail with reference to FIGS 2-3.

[0091] HVAC system 100 is shown to include a chiller 102, a boiler 104, and a rooftop air handling unit (AHU) 106. Waterside system 120 may use boiler 104 and chiller 102 to heat or cool a working fluid (e.g., water, glycol, etc.) and may 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 may 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 may place the circulated fluid in a heat exchange relationship with another fluid (e.g., a refrigerant) in a heat exchanger (e.g., an evaporator) to absorb heat from the circulated fluid. The working fluid from chiller 102 and/or boiler 104 can be transported to AHU 106 via piping 108.

[0092] AHU 106 may 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 may 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 may then return to chiller 102 or boiler 104 via piping 110.

[0093] Airside system 130 may deliver the airflow supplied by AHU 106 (i.e., the supply airflow) to building 10 via air supply ducts 112 and may 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 i nclude a separate VAV unit 116 on each floor or zone of buil ding 10. VAV units 1 16 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 1 16 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 may receive input from sensors located within AHU 106 and/or within the building zone and may adjust the flow rate, temperature, or other attributes of the supply airflow through AHU 106 to achieve setpoint conditions for the building zone.

Waterside System

[0094] Referring now to FIG. 2, a block diagram of a waterside system 200 is shown, according to some embodiments. In various embodiments, waterside syste 200 may 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 may 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.

[0095] In FIG. 2, waterside sy stem 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 thermal energy loads (e.g., hot water, cold water, heating, cooling, etc.) of a building or campus. For example, heater subpl ant 202 can be configured to heat w'ater in a hot water loop 214 that circulates the hot w'ater 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 may 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 may store hot and cold thermal energy, respectively, for subsequent use.

[0096] Hot water loop 214 and cold water loop 216 may 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 thermal energy loads of building 10. The water then returns to subplants 202-212 to receive further heating or cooling.

[0097] 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, C02, etc.) can be used in place of or in addition to water to serve thermal energy loads. In other embodiments, subplants 202-212 may 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 disclosure.

[0098] 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.

[0099] 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 recover}- 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 w¾ter loop 218 and to control the flow rate of the condenser water through individual cooling towers 238.

[0100] 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 may also include one or more pumps or valves confi gured 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 may 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.

[0101] 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.

Air side System

[0102] Referring now to FIG. 3, a block diagram of an airside system 300 is shown, according to some embodiments. In various embodiments, airside system 300 may 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, ducts 112-114, fans, dampers, etc.) and can be located in or around building 10. Airside system 300 may operate to heat or cool an airflow provided to building 10 using a heated or chilled fluid provided by waterside system 200.

[0103] In FIG. 3, airside system 300 is shown to include an economizer-type air handling unit (AHU) 302 Economizer- type AHIJs vary the amount of outside air and return air used by the air handling unit for heating or cooling. For example, AHU 302 may receive return air 304 from building zone 306 via return air duct 308 and may 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.

[0104] 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 may communicate with an AHU controller 330 via a communications link 332.

Actuators 324-328 may receive control signals from AHU controller 330 and may 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.

[0105] 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 may 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.

[0106] Cooling coil 334 may receive a chilled fluid from waterside system 200 (e.g., from cold water loop 216) via piping 342 and may 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 coi l 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.

[0107] Heating coil 336 may receive a heated fluid from waterside system 200(e.g., from hot water loop 214) via piping 348 and may 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 acti vated and deactivated (e.g., by AHU controller 330, by BMS controller 366, etc.) to modulate an amount of heating applied to supply air 310.

[0108] 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 may communicate with AHU controller 330 via communications links 358-360. Actuators 354-356 may receive control signals from AHU controller 330 and may 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 may also receive a measurement of the temperature of building zone 306 from a temperature sensor 364 located in building zone 306.

[0109] 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 330 may 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.

[0110] 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 may 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

[0111] 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 may provide BMS controller 366 with temperature measurements from temperature sensors 362- 364, equipment on/off states, equipment operating capacities, and/or any other information that can be used by BMS controller 366 to monitor or control a variable state or condition within building zone 306.

[0112] 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 devi ce. 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 may communicate with BMS controller 366 and/or AHU controller 330 via

communications link 372,

Building Management Systems

[0113] Referring now to FIG. 4, a block diagram of a building management system (BMS) 400 is shown, according to some embodiments. 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 may also or alternatively include a refrigeration subsystem, an advertising or signage subsystem, a cooking subsystem, a vending subsystem, a printer or copy sendee 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-3.

[0114] 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 controllab!y 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 and servers, or other security-related devices

[0115] Still referring to FIG. 4, BMS controller 366 is shown to include a

communications interface 407 and a BMS interface 409. Interface 407 may 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 may also facilitate communications between BMS controller 366 and client devices 448. BMS interface 409 may facilitate communications between BMS controller 366 and building subsystems 428 (e.g , HVAC, lighting security, lifts, power distribution, business, etc.).

[0116] 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.

[0117] 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.

[0118] 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 memo!}_' 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 some embodiments, 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.

[0119] 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).

[0120] Still referring to FIG. 4, memory 408 is shown to include an enterprise integration layer 410, an automated measurement and validation (AM&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 lay ers 410-420 in BMS 400.

[0121] 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 may 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.

[0122] 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 may 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 may 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.

[0123] 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 may 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 may 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.

[0124] According to some embodiments, 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 may also include control logic configured to determine when to utilize stored energy. For example, demand response layer 414 may determine to begin using energy from energy storage 427 just prior to the beginning of a peak use hour

[0125] 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 may represent collections of building equipment (e.g., subplants, chiller arrays, etc.) or individual devices (e.g , individual chillers, heaters, pumps, etc.).

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

[0127] 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 some embodiments, integrated control layer 418 includes control logic that uses inputs and outputs fro a plurality of buil ding 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.

[0128] 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 w¾ter 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 WOUM result in greater total building energy use than was saved at the chiller.

[0129] 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 may 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

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

[0131] 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 may 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 may 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.

[0132] FDD layer 416 can be configured to output a specific identification of the faulty component or cause of the fault (e.g., loose damper linkage) using detailed subsystem inputs available at building subsystem integration layer 420. In other exemplary embodiments, FDD layer 416 is configured to provide“fault” events to integrated control layer 418 which executes control strategies and policies in response to the received fault events. According to some embodiments, FDD layer 416 (or a policy executed by an integrated control engine or business rules engine) may shut-down systems or direct control activities around faulty devices or systems to reduce energy waste, extend equipment life, or assure proper control response. [0133] 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 may 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 may 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.

[0134] Referring now to FIG. 5, a block diagram of another building management system (BMS) 500 is shown, according to some embodiments. BMS 500 can be used to monitor and control the devices of HVAC system 100, waterside system 200, airside system 300, building subsystems 428, as well as other types of BMS devices (e.g., li ghting equipment, security equipment, etc.) and/or HVAC equipment.

[0135] BMS 500 provides a system architecture that facilitates automatic equipment discovery and equipment model distribution. Equipment discovery can occur on multiple levels of BMS 500 across multiple different communications busses (e.g., a system bus 554, zone buses 556-560 and 564, sensor/actuator bus 566, etc.) and across multiple different communications protocols. In some embodiments, equipment discovery is accomplished using active node tables, which provide status information for devices connected to each communications bus. For example, each communications bus can be monitored for new devices by monitoring the corresponding active node table for new nodes. When a new device is detected, BMS 500 can begin interacting with the new device (e.g., sending control signals, using data from the device) without user interaction.

[0136] Some devices in BMS 500 present themselves to the network using equipment models. An equipment model defines equipment object attributes, view definitions, schedules, trends, and the associated BACnet value objects (e.g., analog value, binary_' value, multi state value, etc.) that are used for integration with other sy stems. Some devices in BMS 500 store their own equipment models. Other devices in BMS 500 have equipment models stored externally (e.g., within other devices). For example, a zone coordinator 508 can store the equipment model for a bypass damper 528. In some embodiments, zone coordinator 508 automatically creates the equipment model for bypass damper 528 or other devices on zone bus 558. Other zone coordinators can also create equipment models for devices connected to their zone busses. The equipment model for a device can be created automatically based on the types of data points exposed by the device on the zone bus, device type, and/or other device attributes. Several examples of automatic equipment discovery and equipment model distribution are discussed in greater detail below.

[0137] Still referring to FIG. 5, BMS 500 is shown to include a system manager 502; several zone coordinators 506, 508, 510 and 518; and several zone controllers 524, 530,

532, 536, 548, and 550 System manager 502 can monitor data points in BMS 500 and report monitored variables to various monitoring and/or control applications. System manager 502 can communicate with client devices 504 (e.g., user devices, desktop computers, laptop computers, mobile devices, etc.) via a data communications link 574 (e.g., BACnet IP, Ethernet, wired or wireless communications, etc.). System manager 502 can provide a user interface to client devices 504 via data communications link 574. The user interface may allow' users to monitor and/or control BMS 500 via client devices 504.

[0138] In some embodiments, system manager 502 is connected with zone coordinators 506-510 and 518 via a system bus 554. System manager 502 can be configured to communicate with zone coordinators 506-510 and 518 via system bus 554 using a master- slave token passing (MSTP) protocol or any other communications protocol. System bus 554 can also connect syste manager 502 with other devices such as a constant volume (CV) rooftop unit (RTU) 512, an input/output module (IOM) 514, a thermostat controller 516 (e.g., a TEC5000 series thermostat controller), and a network automation engine (NAE) or third-party controller 520. RTU 512 can be configured to communicate directly with system manager 502 and can be connected directly to system bus 554. Other RTUs can communicate with system manager 502 via an intermediate device. For example, a wired input 562 can connect a third-party RTU 542 to thermostat controller 516, which connects to system bus 554.

[0139] System manager 502 can provide a user interface for any device containing an equipment model. Devices such as zone coordinators 506-510 and 518 and thermostat controller 516 can provide their equipment models to system manager 502 via system bus 554. In some embodiments, system manager 502 automatically creates equipment models for connected devices that do not contain an equipment model (e.g , IOM 514, third party' controller 520, etc.). For example, system manager 502 can create an equipment model for any device that responds to a device tree request. The equipment models created by system manager 502 can be stored within system manager 502. System manager 502 can then provide a user interface for devices that do not contain their own equipment models using the equipment models created by system manager 502 In some embodiments, system manager 502 stores a view definition for each type of equipment connected via system bus 554 and uses the stored view definition to generate a user interface for the equipment.

[0140] Each zone coordinator 506-510 and 518 can be connected with one or more of zone controllers 524, 530-532, 536, and 548-550 via zone buses 556, 558, 560, and 564. Zone coordinators 506-510 and 518 can communicate with zone controllers 524, 530-532, 536, and 548-550 via zone busses 556-560 and 564 using a MSTP protocol or any other communications protocol. Zone busses 556-560 and 564 can also connect zone

coordinators 506-510 and 518 with other types of devices such as variable air volume (VAV) RTUs 522 and 540, changeover bypass (COBP) RTUs 526 and 552, bypass dampers 528 and 546, and PEAK controllers 534 and 544.

[0141] Zone coordinators 506-510 and 518 can be configured to monitor and command various zoning systems. In some embodiments, each zone coordinator 506-510 and 518 monitors and commands a separate zoning system and is connected to the zoning system via a separate zone bus. For example, zone coordinator 506 can be connected to VAV RTU 522 and zone controller 524 via zone bus 556. Zone coordinator 508 can be connected to COBP RTU 526, bypass damper 528, COBP zone controller 530, and VAV zone controller 532 via zone bus 558. Zone coordinator 510 can be connected to PEAK controller 534 and VAV zone controller 536 via zone bus 560 Zone coordinator 518 can be connected to PEAK controller 544, bypass damper 546, COBP zone controller 548, and VAV zone controller 550 via zone bus 564.

[0142] A single model of zone coordinator 506-510 and 518 can be configured to handle multiple different types of zoning systems (e.g., a VAV zoning system, a COBP zoning system, etc.). Each zoning system can include a RTU, one or more zone controllers, and/or a bypass damper. For example, zone coordinators 506 and 510 are shown as Verasys VAV engines (WEs) connected to VAV RTUs 522 and 540, respectively. Zone coordinator 506 is connected directly to VAV RTU 522 via zone bus 556, whereas zone coordinator 510 is connected to a third-party VAV RTU 540 via a wired input 568 provided to PEAK controller 534. Zone coordinators 508 and 518 are shown as Verasys COBP engines (VCEs) connected to COBP RTUs 526 and 552, respectively. Zone coordinator 508 is connected directly to COBP RTU 526 via zone bus 558, whereas zone coordinator 518 is connected to a third-party COBP RTU 552 via a wired input 570 provided to PEAK controller 544.

[0143] Zone controllers 524, 530-532, 536, and 548-550 can communicate with individual BMS devices (e.g., sensors, actuators, etc.) via sensor/actuator (SA) busses. For example, VAV zone controller 536 is shown connected to networked sensors 538 via SA bus 566. Zone controller 536 can communicate with netw-orked sensors 538 using a MSTP protocol or any other communications protocol. Although only one SA bus 566 is shown in FIG. 5, it should be understood that each zone controller 524, 530-532, 536, and 548-550 can be connected to a different SA bus. Each SA bus can connect a zone controller with various sensors (e.g., temperature sensors, humidity sensors, pressure sensors, light sensors, occupancy sensors, etc.), actuators (e.g., damper actuators, valve actuators, etc.) and/or other types of controllable equipment (e.g., chillers, heaters, fans, pumps, etc.).

[0144] Each zone controller 524, 530-532, 536, and 548-550 can be configured to monitor and control a different building zone. Zone controllers 524, 530-532, 536, and 548-550 can use the inputs and outputs provided via their SA busses to monitor and control various building zones. For example, a zone controller 536 can use a temperature input received from networked sensors 538 via SA bus 566 (e.g., a measured temperature of a building zone) as feedback in a temperature control algorithm. Zone controllers 524, 530-532, 536, and 548-550 can use various types of 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 a variable state or condition (e.g., temperature, humidity, airflow, lighting, etc.) in or around building 10.

[0145] Referring now to FIGS. 6-8, systems and methods for automatic synchronization of point read frequency are shown according to some embodiments. In order to ingest data and provide meaningful building information to a user, a BMS requires that points provided by data sources in the system are properly mapped and the read frequency for each point is synchronized to match a deposit frequency. As used herein, a deposit frequency is the rate at which a data source receives data point values. A read frequency is the rate at which data point values of a point are received or obtained from a data source. For example, a data source corresponding to a chiller can receive and store a temperature measurement values of the chiller at a deposit frequency of once per thirty minutes. A system manager preferably receives each temperature measurement at a read frequency that matches the deposit frequency, i.e. , once every' thirty minutes. Traditionally a user would manually configure the read frequency to match the deposit frequency. However, a deposit frequency may change, and the user may not be aware of the change to the deposit frequency.

Furthermore, the process may be time-consuming because a BMS may involve several thousand points, and if not done correctly, the data will not be fetched at the required time from the data sources, causing a mismatch of time stamps. The system for automated synchronization of data points described herein allows for synchronization errors between the deposit frequency and read frequency to be automatically recognized and corrected.

[0146] Referring to FIG. 6, a block diagram of a point mapping synchronization system 600 is shown, according to an exemplary embodiment. The syste 600 is shown to include a building enterprise manager 602 communieably coupled to a user interface 620 and a set of data sources 630-634 Any number of data sources can be provided in various implementations of system 600. In some embodiments, the building enterprise manager 602 can be the system manager 502.

[0147] In some embodiments, each of the data sources 630-634 is configured to receive data point values from one or more building devices, such as described above with reference to FIGS. 1-5. Each of the data sources 630-634 can be configured to receive data point values at a deposit frequency. For example, a data source 630 can be configured to receive a temperature measurement of a chiller every thirty minutes. In some embodiments, each of the data sources 630-634 can be configured to include a database or a data repository for storing the data point values. In other embodiments, some of the data sources (e.g., 632 and 634) may utilize a. common data repository or database. In some

embodiments, data point values can be deposited at the deposit frequency into the data repository of a data source. In some embodiments, each data point value can be stored along with a time stamp. In some embodiments, the deposit frequency can be configured by a user through a user interface. In some embodiments, a data source can correspond to a building device, including a 1 1 V AC device. In some embodiments, a data source can include a controller, such as a zone controller or other controllers as described in relation to FIGS 1-5. For example, the controller of the data source may include a processor, a memory and a communication interface for transmitting data point values to the building enterprise manager 602. In some embodiments, the data sources 630-634 can receive data point values from HVAC equipment or other building devices.

[0148] The building enterprise manager 602 is shown to include a processing circuit 604 having a processor 606 and memory 608. Processor 606 can be implemented as a special purpose processor, a general purpose processor, an application specific integrated circuit (ASIC), one or more field programmable gate arrays (FPGAs), a group of processing components, or other suitable electronic processing components. The processor 606 may be configured to execute computer code or computer-executable instructions stored in memory or received from other non-transitory computer readable media (e.g., CDROM, network storage, a remote server, etc.). Memory' 608 (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 608 can be or include volatile memory or non-volatile memory . Memory 608 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. Memory' 608 may be communicably connected to the processor via the processing circuit and may include computer code for executing (e.g , by the processor) one or more processes described herein

[0149] In some embodiments, the memory 608 can include a data collector module 610, a data analyzer module 612, an automatic synchronization module 614, and a user interface generator module 616. In some embodiments, one or more of the data collector module 610, data analyzer module 612, automatic correction module 614, and user interface generator module 616 are provided in one or more processing circuits external to the building enterprise manager. In some embodiments, modules 612-616 stored in a non- transitory computer readable medium (e.g., memory' 608) can be executed by the processor 606 to perform operations as described herein

[0150] The data collector module 610 can be configured to obtain or receive data point values from one or more data sources 630-634. The data collector module 610 can be configured to obtain or receive data point values at a read frequency, such as once every five minutes, thirty minutes, etc. The read frequency may be based on a user setting, for example, provided by and received from a user interface 620. In some embodiments, the data collector module 610 is configured to retrieve historical data from a data source. For example, the data collector module can be configured to retri eve a set of data point values and associated timestamps over a one week period. In some embodiments, the data collector module 610 can be communicably coupled to the data sources via a

communications interface. The communications interface can be or include wired or wireless communications interfaces (e.g., jacks, antennas, transmitters, receivers, transceivers, wire terminals, etc.). The communications interface can be via a

communications network (e.g., a WAN, a LAN, the Internet, a cellular network, etc.). In some embodiments, the communications interface can include a Wi-Fi transceiver for communicating via a wireless communications network, and/or a cellular or mobile phone communi cati on s transeei v er s .

[0151] The data analyzer module 612 can be configured to receive data obtained by the data collector module 610 for one or more data analysis operations. In some embodiments, the data analyzer module 612 is configured to identify a deposit frequency at a data source. For example, the data analyzer module can be configured to determine a deposit frequency by analyzing historical data, e.g., by analyzing a series of timestamps of data point values.

In some embodiments, data analyzer module 612 can be configured to scan for an interval that the data point values are deposited into the data repository' or database of the data source. In some embodiments, the data collector module 612 can also be configured to detect any changes to the deposit frequency by identifying a time interval change between timestamp values. In some embodiments, the data analyzer module 612 is configured to determine whether a frequency at which a data point value is received at a data source (i.e., the deposit frequency) matches a frequency at which the building enterprise manager 602 receives a data point value from the data source (i.e., the read frequency). In some embodiments, the read frequency is determined by a user setting. In some embodiments, the data analyzer module 612 is configured to perform one or more data analysis operations according to a predetermined frequency, such as daily, weekly, bi-weekly, etc.

[0152] The automatic synchronization module 614 can be configured to automatically correct a read frequency to match the deposit frequency. In some embodiments, the automatic synchronization module 614 can be configured to compare a deposit frequency to a read frequency to identify a mismatch. In response to identifying a mismatch, the automatic synchronization module 614 can be configured to change or adjust the read frequency to match the deposit frequency (e.g., instruct the data collector module to update a read frequency). In some embodiments, the automatic synchronization module 614 can be configured to update a start time of the read frequency

[0153] The user interface generator module 616 can be configured to generate a user interface, for example the user interface 620. In some embodiments, the user interface 620 may allow a user to monitor and/or control a BMS system via one or more client devices (e.g. client devices 504). The user interface 620 can include information relating to data sources, data points, and other components of the building management system. In some embodiments, the user interface 620 allows a user to set one or more read frequencies at which data point values are to be obtained by the building enterprise manager 602 from the data sources 630-634. In some embodiments, the building enterprise manager 602 can communicate with the user interface 620 via a communications interface. In other embodiments, the building enterprise manager 602 includes the user interface 620 In some embodiments, the user interface generator module 616 can be configured to provide a dashboard layout of a building management system. In some embodiments, the user interface generator module 616 is configured to receive one or more commands from a user and generate the user interface in response to the received commands. For example, the user interface generator module 616 can be configured to receive a user setting relating to a read frequency. In some embodiments, the user interface generator module 616 may revise a user interface, such as a dashboard layout, in response to the user setting. In some embodiments, the building enterprise manager 602 may not include the user interface generator module 616, and the user interface 620 can be generated by a user interface generator external to the building enterprise manager 602.

[0154] Referring now to FIG. 7, a flow diagram depicting a method 700 of automatic synchronization of point read frequency is shown, according to an exemplary' embodiment. In some embodiments, a user configuration setting of a data source is received (step 702). The user configuration setting can relate to a read frequency. In some embodiments, the user configuration setting can relate to a deposit frequency. The user configuration setting may be provided by a user via a user interface. In some embodiments, the building enterprise manager may receive data from one or more data sources (step 704). The data can relate to data point values of a data point. The data can include information relating to a deposit frequency at which data point values of a data point are received at the data source.

[0155] In some embodiments, the building enterprise manager can analyze the data frequency (step 706) to determine whether the deposit frequency matches the read frequency (step 708). When a mismatch is determined, the building enterprise manager can automatically correct the read frequency (step 710). On the other hand, when it is determined that the read frequency matches the deposit frequency at step 708, the building enterprise manager can continue to read the data at the existing read frequency (step 712).

[0156] In some embodiments, the building enterprise manager can retrieve historical data relating to data point values received at a data source. The historical data may correspond to a predetermined time period, such as a day, a week, a month, etc. The building enterprise manager can use the historical data to determine a deposit frequency. For example, a user may have adjusted a deposit frequency at a data source (e.g. via a user interface), but the read frequency may have not been updated. In this example, the building enterprise manager can detect the frequency change by analyzing the historical data to identify changes in the deposit frequency. For example, the building enterprise manager can retrieve and analyze the historical data each day. A deposit frequency change can be recognized by identifying a time interval change between time stamps of data point values. In response to detecting a deposit frequency change, the building enterprise manager can autonomously update the read frequency to automatically synchronize with the deposit frequency.

[0157] FIG. 8 illustrates another flow diagram depicting a method 800 of automatic synchronization of point read frequency, according to an exemplary embodiment. The method 800 can include receiving a user configuration setting comprising a read frequency at which data point values are to be obtained from a data source (Step 802). For example, a building enterprise device can receive or obtain a user configuration setting from a user interface. The user interface can be at a client device and allow a user to enter a setting indicating a read frequency at which data point values are to be read by the building enterprise device from the data source. In some embodiment, the user interface can be part of the building enterprise device

[0158] The method 800 can include obtaining the data point values from the data source at the read frequency (Step 804). For example, the building enterprise device can obtain or receive the data point values at the read frequency (e.g , every 10 minutes) from the data source via a communications network. The data source can be among a plurality of data sources that can each be configured to receive respective data point values associated with a respective data point at a respective deposit frequency. For example, a data point can be a chiller inlet temperature, and the values of the chiller inlet temperature can be received by a data source associated with or corresponding to a chiller inlet at a deposit frequency (e.g., every 20 minutes.) In some embodiments, the data sources can be first data sources that receive data point values from second data sources (e.g., HVAC equipment or other building devices) at the respective deposit frequencies. In some embodiments, the data source can include a database or a data repository, and the data point values are deposited at the deposit frequency (e.g., every 20 minutes) into the data repository of the data source. In some embodiments, each data point value can be stored into the data repository along with a time stamp indicating the time that the data point value is deposited into the data repository.

[0159] The method 800 can include identifying a deposit frequency at which the data point values are received at the data source by analyzing the obtained data point values (Step 806). For example, the building enterprise device can identify or determine the deposit frequency at which the data point values are received at the data source. In some embodiments, the data point values obtained by the building enterprise device can include timestamps indicating the time that the data point values were deposited into the data repository of the data source. In such a case, the building enterprise device can store the obtained data point values into a memory or data store at the building enterprise device over a period of time. The building enterprise device can analyze the timestamps of the data point values to identify the deposit frequency. In some embodiments, the building enterprise device can directly retrieve a plurality of historical data relating to previous data point values that have been stored at the data repository of the data source from the data repository of the data source. The building enterprise device may use this method when, for example the data point values obtained by the building enterprise device do not carry timestamps, or when the building enterprise device does not store data point values over a period of time at the building enterprise device. The building enterprise device retrieves the historical data point values along with the timestamps indicating the time that those data point values were deposited into the data repository of the data source. The building enterprise device can analyze the timestamps associated with the historical data point values to identify the deposit frequency. For example, the building enterprise device can scan for an interval that the data point values were deposited into the data repository of the data source.

[0160] The method 800 can include determining that the identified deposit frequency does not match the read frequency (Step 808). For example, the building enterpri se device can compare the deposit frequency identified at step 806 with the read frequency received at step 802 to determine whether the read frequency matches the deposit frequency. When the building enterprise device determines that the read frequency does not match the deposit frequency, the building enterprise device can adjust the read frequency to match the deposit frequency (Step 810). After the building enterprise device adjusts the read frequency, the building enterprise device can obtain the data point values via the network from the data source at the adjusted read frequency which matches the deposit frequency at which the data point values are received at the data source (Step 812)

[0161] In some embodiments, the methods 700 and 800 can be automatically run according to a predetermined time period. For example, the building enterprise manager can run the method 700 or 800 each day to determine the need for automatic

synchronization. In some embodiments, the building enterprise manager continuously repeats the operation of analyzing the deposit frequency after a reoccurring time period.

For example, for a point associated with a HVAC device (e.g. a chiller inlet), data point values are received at a data source at a frequency of once per twenty minutes, but a user configured the frequency at which data is received at the building enterprise manager as once every five minutes. By reading historical data relating to the frequency at which data point values are received at a data source (i.e., twenty minutes), the building enterprise manager can determine to automatically synchronize the read frequency from five minutes to twenty minutes. This service can run for every fifteen minutes to accommodate for the new points configured by the user.

Metrics Generation System with Optimized Processing of Meter Data

[0162] Referring generally to FIGS. 9-1 1, a system and method for optimized processing of building automation system data are shown, according to exemplary embodiments. A BMS, for example as described above with reference to FIGS. 4-5, includes a range of sensor and controllers connected to a central system for collection and analysis of data. For the puipose of measurement, meters can be installed in multiple spaces of the building or buildings. Meters may contain one or more sensors that measure a metric like electric demand, consumption, power factor, and occupancy, among other possible metrics. Each sensor may correspond to a point against which its metric is recorded periodically. Each point may be periodically recorded resulting in a sample that includes the point, a timestamp, and the metric value at the time of measurement. Spaces, meters, and points may be arranged hierarchically. The spaces, meters, and points that contribute to a space may be termed the children of the space, and the space may be termed the parent of the spaces, meters, and points that contribute to it. All points that measure the same metric and are children of the same space may be labelled as siblings.

[0163] Referring now to FIG. 9, a block diagram of a BMS space hierarchy is shown, according to an exemplary embodiment. A portfolio 900 managed by a BMS (e.g., BMS 500, BMS 400) includes equipment (e.g., HVAC system 100) located in multiple buildings 902, shown as Building A and Building B. Building A and Building B are both made up of multiple floors 904, arranged one level below to indicate that the floors 904 are subspaces of the buildings 902. For example, Floor Al, Floor A2, . . . , and Floor An are children of Building A. Within each floor are one or more wings 906, arranged to indicate that each wing is a subspace of a specific floor 904 as well as a subspace of a building 902. For example, Wing Al l, Wing A12, and Wing A13 are shown as children of Floor Al and Building A Building B is arranged similarly. It should be understood that the hierarchy of FIG. 9 is included for illustrative purposes and that the systems and methods disclosed herein are suitable for application with various collections of campuses, enterprises, buildings, spaces, subspaces, sub-subspaces and so forth.

[0164] Meters 908 may be positioned at various levels in the hierarchy, including at the level of the Floors in the hierarchy and at the level of the Wings in the hierarchy. The meters 908 may include sensors that measure one or more physical parameters relating to the corresponding floor or wing to generate data samples of points corresponding to the physical parameters. Meters 908 may also generate data samples directly at the building 902 or portfolio 900 level, or various other levels in a hierarchy of any embodiment. Meiers 908 may be physically located at an associated space as well as virtually associated with the space in a space hierarchy database, for example as described in detail below

[0165] FIG. 9 illustrates that at least two scenarios are possible when determining a value of a metric for a space in the BMS space hierarchy (i.e., for a portfolio 900, a building 902, a floor 904, a wing 906, etc.). First, if a relevant meter 908 is directly associated with a space on the level of that space (e.g., shown on that space in FIG. 9), then the value of a metric for the space may be equal to a sample from that meter. For example, a metric for Floor Al of Building A is directly measured by the meter 908 shown as associated with Floor Al . Second, if no relevant meter 908 is connected to the space at the level of the space, then the value of a metric may be derived by aggregating values measured by meters 908 of children of that space. For example, a metric for Building 2 may be calculated based on measurements the meters 908 at Floor Bl, Floor B2, Wing Bnl, and Wing Bn3. [0166] For purposes of effective analytics in a BMS, metrics may be required at every level and for different time aggregations (e.g , hourly, daily, monthly, yearly). For a large BMS with complex hierarchies, computation of these metrics traditionally becomes cumbersome and slow, resulting in poor performing user interfaces, slow calculation of key performance indicators, and difficulty in applying business rales to the metrics. As discussed in detail with respect to FIGS. 10-11, metrics for each space and each level of time aggregation may he pre-calculated and stored using a batch processing approach to address these challenges.

[0167] Referring now to FIG. 10, a block diagram of a metrics generation system 1000 is shown, according to an exemplary embodiment. In some embodiments, the metrics generation system 1000 is a component of a BMS, such as BMS 400 or BMS 500 described with reference to FIGS. 4-5 The metrics generation system 1000 includes a space hierarchy database 1002, a timeseries storage database 1004, a current metrics database 1006, and a batch metrics engine 1 1 1008. The metrics generation system 1000 is communicably coupled to multiple meters 908, a building analytics and presentation circuit 1010 and an equipment controller 1012.

[0168] Meters 908 are shown within a building sub-space 1050 and a building 1051. In other embodiments, more meters and/or more buildings and/or building sub-spaces may be included. The meters 908 take readings (i.e., measure physical parameters) to generate data samples corresponding to points, label the samples with timestamps, and transmit those samples to the metrics generation system 1000 periodically or non-peri odically. Raw data samples and the corresponding point and timestamp data are stored in a timeseries storage database 1006.

[0169] The space hierarchy database 1002 is configured to store a space hierarchy for the spaces managed by a BMS. As described above in reference to FIG. 9, buildings, spaces, subspaces, meters, and points are arranged hierarchically based on parent and child relationships. These relationships may be stored in the space hierarchy database 1002. That is, the space hierarchy database 1002 may store a list of parents and children for each entity- in the space hierarchy.

[0170] The space hierarchy database 1002 also stores sibling relationships between sibling points. Sibling points are points that provide the same metric and that share a common parent space. Sibling points may be initially defined by a user or may be automatically recognized by the metrics generation system. Various data models and/or data objects may be used in various embodiments to indicate sibling relationships. For example, the space hierarchy database 1002 may store a list of sibling points for each point in the hierarchy, a list of sibling spaces of each space in the hierarchy, etc.

[0171] The timeseries storage database 1004 receives and stores timeseries data samples for points from the meters 908. The timeseries storage database 1004 may be

communicable with the batch metrics engine 1008 to allow the batch metrics engine 1008 to access (i.e., use, copy, etc. ) the timeseries data in the timeseries storage database 1004.

[0172] The batch metrics engine 1008 is configured to calculate metrics for all levels of the space hierarchy and store them in the current metrics database 1006 where the metrics can be accessed on demand by the building analytics and presentation circuit 1010. The batch metrics engine 1008 calculates metrics using a batch processing method, for example as described below in reference to FIG. 11. The batch metrics engine 1008 may be triggered to calculate one or more updated metrics when the metrics generation system 1000 receives a new data sample from a meter 908. In other embodiments, updates to metrics may be prescheduled or repeated after a set time interval. The batch metrics engine 1008 accesses the space hierarchy database 1006 to determine if calculating the metric requires aggregating data from multiple meters 908. The determination may include checking whether the space is a parent of multiple meters that provide samples of that metric, or by- checking if a point has at least one sibling. If aggregation is required (i.e., if the space is a parent of multiple meters or if the point has one or more sibling points), the batch metri cs engine accesses the sibling relationships in the space hierarchy database to identify all siblings of the point. By using stored sibling relationships, the batch metrics engine 1008 avoids re-analyzing the parent-child hierarchy to locate sibling points for every calculation. The batch metrics engine 1008 also identifies a time period over which to run the calculation, which may be based on the timespan of the corresponding metric (e.g., one hour, one week, one month, three months, one year). The batch metrics engine 1008 then pulls data samples for each of the siblings for this time period from the timeseries storage database 1004. For example, if the identified time period is one hour, the batch metrics engine 1008 will access data samples from all sibling points with a timestamp from the last hour. The batch metrics engine 1008 calculates an updated metric based on the data samples, and stores the result in the current metrics database 1006. [0173] Up-to-date metrics are thereby stored in the current metrics database 1006. A building analytics and presentation circuit 1010 may access the current metrics database 1006 at any time to run higher-level analytics on the up-to-date metrics without

recalculating metrics from raw data samples. The building analytics and presentation circuit 1010 may also access the up-to-date metrics for inclusion in a graphical user interface generated by the building analytics and presentation circuit 1010 for presentation to a user without the need to calculate metrics from raw data on demand. A user may therefore have a quicker, smoother experience viewing metrics for the building, building sub-space, etc. in a graphical user interface.

[0174] The equipment controller 1012 may also access the current metrics database 1006 to receive one or more metrics from the current metrics database 1006. The equipment controller 1012 may generate control signals for building equipment based on the one or more metrics. For example, the equipment controller 1012 may turn building equipment on or off, increase or decrease an operating power of the building equipment, adjust a setpoint (e.g., a temperature setpoint) for the building equipment, etc. The building equipment may be operable to affect the points and/or metrics, such that the equipment controller 1012 may control the building equipment to cause a change in the value of one or more points and/or one or more metrics over time.

[0175] Referring now to FIG. 11, a flowchart showing a process 1100 for batch processing of building metrics is shown. When new data samples are received for a point, the values for the metrics for all of the point’s parents may be updated. Batch data processing as shown in the FIG. 11 is used to group together data received for different children of a space for the purpose of reducing the number of updates to the parent space’s metrics. This batch data processing 1 100 of FIG. 1 1 is therefore more efficient, requires less computing resources, and provides up-to-date metrics accessible to a user or other system.

[0176] To start, at step 1102, new data samples for a point are taken (i.e., collected by a meter 908 and received by the metric generation system 1000). Receiving a new data sample initiates process 1 100, i.e., triggers the metrics generation system to calculate one or more updated metrics. At step 1104, the batch metrics engine 1008 determines whether data aggregation is required, i.e , whether data from more than one meter is required to calculate a metric based on the new data sample. If data aggregation is not required— for example, when the metric is directly measured by a single meter-then the relevant sample is enough to determine a value of the metric and the process ends.

[0177] If space aggregation is required (i.e., multiple points are all relevant to a desired metric), then the batch processing method is initiated following step 1104. At step 1106, sibling points of the point of the new data sample are identified based on space hierarchy information stored in the space hierarchy database 1002. Siblings include all other points for the same metric that are children of the same space, i.e., children of the space for which a metric is to be calculated. In some embodiments, the space hierarchy database 1002 stores a list of sibling points for each point, such that at step 1104 the batch metrics engine 1008 looks up the point in the space hierarchy database 1002 to determine the other points that are used to calculate a metric. This provides substantial efficiencies over other approaches which may require reanalysis of the hierarchy to re-identify such points each time a metric is to be calculated.

[0178] At step 1108, a period of calculation is identified, corresponding to a time period over which samples from all siblings will be collected. The period of calculation may be dependent on the type of metric to be calculated. At step 1110, the data for all siblings (as identified at step 1 106) over the period of calculation (as identified at step 1 108) is fetched from the timeseries storage database 1004. This data is collected in a batch of data along with the new data sampl e received at step 1102. At step 1112, a mapping of the points (i.e , the collection of sibling points) to a parent space is retrieved from the space hierarchy database 1002. That is, the batch metrics engine 1008 identifies the parent space corresponding to a metric calculated based on the aggregation of data corresponding to the sibling points identified at step 11 10.

[0179] At step 1114, an aggregate metric for the parent space identified at step 11 12 is calculated based on the batch of data. The aggregate metric may be a sum of the metrics for child spaces of the parent space or may be calculated using any other algorithm.

[0180] At step 1 1 16, the aggregate metric for the parent space is stored in the current metrics database 1006. The current metrics database 1006 may then be accessed by the building analytics and presentation circuit 1010 for use in meta-analysis and/or for integration into a graphical user interface accessible by a user.

[0181] Using this method, the value of all metrics at all levels within a portfolio may be automatically updated to be available for use. The time required to fetch the metrics (e.g., in response to a user request, for the purpose of running business rules) is reduced by the pre-calculation, and the batching method may substantially reduce the calculation load on the BMS processors.

Automated Point Mapping Validation

[0182] Referring now to FIGS. 12-14, systems and methods for automated point mapping validation are shown, according to exemplary' embodiments A BMS (e.g., BMS 500 of FIG. 5, BMS 400 of FIG. 4) includes a variety of sensors, meters, and equipment that provide data relating to a building and to the operation building equipment. Each sensor, meter, or equipment provides data corresponding to one or more points. To properly process data from the sensors, a BMS may require the points to be properly mapped to the correct building equipment devices and to the correct metrics related to those devices to ensure that data corresponding to each point is used to calculate the correct metrics or performance indicators.

[0183] In some BMSs, initial mapping of points to devices and metrics is a manual process, whereby a user maps points to metrics via a user interface. As a result of the manual mapping process, mapping errors are often not discovered until metric

miscalculations or error messages appear during the operational stages of the BMS. The system for automated point mapping validation described herein allows for mapping errors to be recognized and prevented immediately during the mapping process, improving the usability of the BMS, reducing the risk of errors, and improving the efficiency of set-up and installation of the BMS.

[0184] Referring now to FIG. 12, a block diagram of a point mapping system 1200 is shown, according to an exemplary' embodiment. In some embodiments, the point mapping system 1200 is a component of a BMS, such as BMS 400 or BMS 500 as described with reference to FIGS. 4-5, for example included in system manager 502. The point mapping system 1200 is shown to include a point mapping validation circuit 1202, a point object database 1204, a template object database 1206, and a user interface generator circuit 1208

[0185] The point object database 1204 can store a representation of a point as a point object (data object). The point object may include point attributes, including a name attribute, a location attribute, a unit attribute, and a mapping status. The unit attribute indicates the units of the data provided by the point, including, for the sake of non-limiting example, degrees Celsius (DegC), degrees Fahrenheit (DegF), Amps (A), Volts (V), Watts (W), kilowatts (kW), rotations per minute (RPM), miles per hour (MPH), etc. For example, if the point provides a temperature measurement, the unit attribute for the point may be “DegF.”

[0186] The template object database 1206 can store template objects that correspond to equipment device metrics or building management metrics to be calculated by the BMS. Each template object may have template attributes including, for example, template name, template equipment category , and allowed units. The allowed units attribute indicates the units (e.g., DegC, DegF, A, V, W, kW, RPM, MPH, etc. ) that the template requires for data provided by a point to generate the corresponding metric. For example, if the template is used to generate a Supply Air Temperature, it may require a point to supply input data in degrees Fahrenheit or Celsius.

[0187] In some embodiments, the point object database 1204 and the template object database 1206 are stored in a system database external to the point mapping system 1200 but accessible via an electronic interface. For example, the point object database 1204 and the template object database 1206 may also or alternatively be stored in a cloud-based datacenter.

[0188] The user interface generator circuit 1208 is configured to generate a graphical user interface that allows a user to request that a point object be mapped to a template object and provide the graphical user interface to a client device 504. An example of such a graphical user interface is shown in FIG. 14 and described in detail with reference thereto. The user interface generator circuit 1208 may be communicably coupled to the point object database 1204 and the template object database 1206 to retrieve lists of points and templates for inclusion in the graphical user interface. The user interface generator circuit 1208 may also be configured to receive a request to map a point object to a template object from a user and forward the request to the point mapping validation circuit 1202.

[0189] The point mapping system 1200 may also include a point mapping validation circuit 1202 The point mapping validation circuit 1202 is configured to receive a request from the user interface generator circuit 1208 to map a point object to a template object. In response, the point mapping validation circuit 1202 is configured to access the point object database 1204 to identify the unit attribute for the requested point (i.e., the unit attribute of the point object to be mapped) and to access the template object database 1206 to read the allowed units attribute for the requested template (i.e., the allowed units attribute of the template object to which the point object is to be mapped). The point mapping validation circuit 1202 then determines whether the units attribute for the point matches the allowed units attribute for the template. It should be noted that the units attribute of the point may match the allowed units attribute of the template if the units attribute matches any (i.e., one or more) of the allowed units specified in the allowed units attribute of the template. If the units attribute for the point matches the allowed units attribute for the template, the point mapping validation circuit 1202 may map the point object to the template object by- updating a mapping attribute in the point object to reference the requested template object and transmits a success message to the user interface generator circuit 1208. If the units attribute for the point does not match the allowed units attribute for the template, the point mapping validation circuit 1202 may prevent the mapping and may send a rejection message to the user interface generator circuit 1208.

[0190] As shown in FIG. 12, the point“pi” has a mapping attribute of“unmapped.” If a user attempts to map point pi to a selected template, the point mapping validation circuit 1202 may access the point object for pi and reads the unit attribute (“DegF”). The point mapping validation circuit 1202 may store the unit attribute in temporary memory. The point mapping validation circuit 1202 may also access the template object database 1206 and look up the template object selected by the user. The point mapping validation circuit 1202 may read the allowed units attribute of the selected template object and compare it to the unit attribute for point pi. If the unit attribute of the point object is included in the allowed units attribute (e.g ,“DegF” is included in the allowed units for“Supply Air Temperature” and“Zone Dew Point”), the point mapping validation circuit validates the mapping. If the unit attri bute is not included in the allowed units attribute of the selected template (e.g., if“pi” and“Chiller Efficiency” are compared), the point mapping validation circuit 1202 prevents the mapping.

[0191] Thus, in the example of FIG. 12, the point mapping validation circuit 1202 would validate a mapping of point pl to templates“Supply Air Temperature” or“Zone Dew Point” due to the inclusion of the unit attribute“DegF” in the allowed units attributes “DegC, DegF” of these templates. However, the point mapping validation circuit 1202 would reject a mapping to templates“Phase A Motor Current” or“Chiller Efficiency” shown in FIG. 12 because the unit attribute“DegF” is not present in the allowed units attribute for those templates. It should be understood that these examples are included for illustrative purposes and are not meant to be limiting. [0192] Referring now to FIG. 13, a flowchart depicting a process 1300 for automated point mapping validation is shown, according to an exemplary embodiment. Process 1300 may be performed by the point mapping system 1200 of FIG. 12 and/or various components of BMS 400 or 500.

[0193] At step 1302, the point mapping system 1200 receives a input from a user mapping a selected point to a selected template on a graphical user interface. For example, the user may provide the mapping via a drag-and-drop input where the user drags (e.g., click and hold) the point from a list of points and drops (e.g., releases the click) the selected point on a selected template on the graphical user interface. Such a drag-and-drop feature may allow the user to quickly and easily place the point in the template on the user interface, improving usability. An example of a graphical user interface which can be used to receive the user input in process 1300 is shown in FIG. 14 and described with reference thereto.

[0194] At step 1304, the point mapping system 1200 looks up the unit attribute for the selected point and the allowed units attribute for the selected template (i.e., in the point object database 1204 and the template object database 1206). At step 1306, the point mapping system 1200 then determines whether the point’s unit attribute is included in the template’s allowed units attribute. If the point’s unit attribute is included in the template’s allowed units attribute (i.e., the result of step 1306 is“yes”), then at step 1308 the point mapping system 1200 validates the mapping and the point is mapped to the template in the BMS. For example, a template attribute of the point object stored by the point object database 1204 may be updated to list the selected template. At step 1308, the point mapping system 1200 also provides a notification of success of the mapping to the graphical user interface.

[0195] If the point’s unit attribute is not included in the template’s allowed units attribute (i.e., the result of step 1306 is“no”), then at step 1310 the point mapping system 1200 prevents the point from being mapped to the template and provides a notification of mapping failure to user via the graphical user interface (i.e., via a client device 504). The user interface may display information related to the reasons for the mapping failure, and the selected point is not mapped to the selected timeline. The process then returns to step 1302, wherein the point mapping system 1200 receives another attempt from a user to correctly map a point to a template. [0196] Referring now to FIG. 14, an equipment configuration interface 1400 is shown, according to an exemplar}_' embodiment. The equipment configuration interface 1400 may be generated by the user interface generator circuit 1208 of FIG. 12 and presented on one or more client devices 504.

[0197] The equipment configuration interlace 1400 includes a points tree widget 1402 and an equipment template tree widget 1404. The points tree widget 1402 provides search tools 1406 for locating a desired point, including drop down options, meter status toggle, and a text-entry search box. A units button 1408 may be used to filter points by associated units. The points tree widget 1402 sho _'s a points tree 1410, in which points are listed by name in a hierarchical list, organized by meter type, unit attribute, location, or other categorization. Point names on the points tree 1410 may be color-coded to indicate whether the point is mapped or unmapped, and configured or not configured. The equipment template tree widget 1404 show_'s an equipment template tree 1412, which may include a list of equipment and templates organized hierarchically and listed by name, with templates shown under corresponding equipment devices. A template may be deleted from this list using a trash button.

[0198] The equipment configuration interface 1400 is configured to allow a user to drag the name of a point from the points tree 1410 in the points tree widget 1402 and drop it on a template name in the equipment template tree 1412 of the equipment template tree widget 1402. The automated points mapping validation system 1202 may then checks whether the point’s unit matches any of the template’s allowed units, as described above with reference to FIGS. 12-13, for example.

[0199] If the point’s unit does not match any of the template’s allowed units, an error notification is presented, shown as error notification 1414, and the point is prevented from being mapped to the template. The error notification may be color-coded to indicate an error (e.g., red), may be positioned on the screen to attract the user’s attention, and/or may include an audible alarm. In the example shown, the error notification 1414 is positioned in an upper-right hand comer of the equipment configuration interface 1400. The error notification 1414 may include a brief explanation of the error, for example stating that the point cannot be mapped due to unit mismatch.

[0200] If the point’s unit does match any of the template’s allowed units, a notification of success may be presented. The point’s entry' on the list of points will be updated to indicate that the point has been mapped to the selected template, and the point mapping system 1200 maps the point to the template. Then, throughout other systems and methods included with a BMS, the point may be used with the selected template to calculate and present building equipment metrics and key performance indicators. The equipment configuration interface 1400 may thereby allow a user to map points to equipment templates for all points and equipment types in the BMS.

Point Virtualization Under Online Meters

[0201] Referring now to FIG. 15-19, several drawings illustrating systems and methods for point virtualization under online meters in a BMS are shown. In some embodiments, the point virtualization systems and methods described herein are implemented with BMS 400 or BMS 500, as described with reference to FIGS. 4-5.

[0202] Referring now to FIG. 15, a block diagram of a BMS 1500 with point

virtualization is shown. The BMS 1500 includes multiple meters 1502 that provide data samples for multiple real points measured by the meters 1502 (e.g , collected by sensors included with the meters 1502). As used herein, the term‘Teal point” refers to a point that is measured or observed by one or more of the meters 1502 A real point may represent a physical parameter of the building and/or building equipment served by BMS 1500 (e.g., a temperature point measured by a temperature sensor of the m eters 1502, a power consumption measured by a power meter of the meters 1502, a flow rate measured by a flow meter of the meters 1502, etc.). Accordingly, the meters 1502 provide raw' data for real points corresponding to physical parameters of the building and/or building equipment served by the BMS 1500. Conversely, the term“virtual point” refers to a point that is not directly measured by the meters 1502 but rather is calculated or simulated based on one or more real points, other virtual points, and/or other parameters or values.

[0203] In many cases the real points measured by the meters 1502 are not sufficient to allow the BMS 1500 to calculate all metrics, key performance indicators, etc. desired by users of the BMS 1500 or necessary for implementing various features of the BMS 1500. Thus, as described in detail below, the BMS 1500 provides for point virtualization under online meters 1502 to provide an efficient, user-friendly, and cost-effective way to cover for deficiencies in the amount or type of data provided by the meters 1502.

[0204] As shown in FIG. 15, the BMS 1500 includes an analytics system 1504 that facilitates point virtualization and provides for the calculation of advanced metrics (e.g., key performance indicators) based on both real points and virtual points. In some embodiments, the analytics system 1504 is a component of BMS 400 or BMS 500, for example included with system manager 502. As illustrated in FIG. 15, the analytics system 1504 includes an object database 1506, a point virtualization circuit 1508, and an advanced metrics circuit 1510

[0205] The object database 1506 is configured to store data objects corresponding to various elements and features of the BMS 1500, for example meter objects 1512 and point objects 1514. Each meter object 1512 is an electronic representation of one of the meters 1502 in the BMS 1500, and each point object 1514 is an electronic representation of a real point (i.e., corresponding to a real-world measurement from a meter 1502) or virtual point (i.e., corresponding to a simulated value not provided directly by a meter 1502). Each point object 1514 includes a set of attributes associated with the corresponding point, and each meter object includes a set of attributes associated with the corresponding meter, as illustrated in FIG. 16 and described with reference thereto below. For example, as an attribute of each meter object, the object database 1506 may store a list of points associated with that meter.

[0206] The point virtualization circuit 1508 is configured to create virtual point objects, store virtual point objects in the object database 1506 as point objects 1514, and alter the attributes of the meter objects 1512 to list virtual point objects 1514 as associated with meter objects 1512, for example as described with reference to FIG. 17 below. The point virtualization circuit 1508 thereby facilitates the creation of virtual points under online meters, i.e., such that a meter 1502 may be associated with both real points and virtual points. The point virtualization circuit 1508 may also communicate with a user device (shown as client device 504) The point virtualization circuit 1508 may generate a user interface for presentation on the user device (e.g., tablet, laptop, desktop computer, smartphone) that allows the user to request the creation of new virtual points, map virtual points to meters 1502, and define derivation formulas for virtual point objects. Examples of such graphical user interfaces are shown in FIGS. 18-20 and described in detail with reference thereto.

[0207] The advanced metrics circuit 1510 is configured to calculate metrics (e.g., key performance indicators, roll-ups, space aggregations, fault detection and diagnostics) relating to the building and/or building equipment served by the BMS 1500. The advanced metrics circuit 1510 may receive data from the meters 1502 and determine a value for each point associated with each meter, including both virtual points and real points. The advanced metrics circuit 1510 may then treat virtual points and real points identically to calculate metrics based on the values of the points. This may allow the advanced metrics circuit 1510 to calculate all desired metrics even where the real points do not directly correspond to the inputs necessary' to calculate that metric and without regard to whether the metric is calculated from real points, virtual points, or some combination thereof. In some embodiments, the advanced metrics circuit 1510 may receive a request to calculate a metric from a client device 504, calculate the metric in response, and provide the metric to the client device 504 for presentation in a graphical user interface.

[0208] As one illustrative example, a building may include a first space served by a first meter and a second space served by a second meter. The first meter may collect a first real point for the first space corresponding to a physical parameter (e.g , power consumption), but the second meter may not be configured to collect data for that physical parameter. In such a situation, a second virtual point corresponding to the physical parameter in the second space may be created under the second meter by creating a virtual point object associated with a meter object for the second meter. Then, the advanced metrics circuit 1510 may calculate an aggregate metric for the building (i.e., for the first space and the second space) using data for the first real point and data for the second virtual point. For example, the advanced metrics circuit 1510 may add a value of the first real point to a value of second virtual point to determine a total value for the building.

[0209] Referring now to FIG. 16, a block diagram of the object database 1506 of the BMS 1500 is shown, according to an exemplary embodiment. In some embodiments, the object database 1506 is a component of BMS 400 or BMS 500. The object database 1506 can store meter objects 1512 corresponding to each physical meter deployed in the buildings or facilities managed by the BMS 1500, illustrated by an example meter object 1516 in FIG. 16. The meter object 1516 may include meter attributes including, for example, the meter name (e.g.,“Ml”), meter location (e.g.,“Building 1 - Floor 4”), and/or the points provided by that meter (e.g.,“pi,”“p2,” and“p3”). The points listed in the meter object 1516 may include both real points (i.e., points directly collected by the physical meter 1502) and virtual points (i.e., simulated points calculated indirectly from data collected by one or more meters 1502).

[0210] The object database 1506 can also store a point object for each of one or more points, including real points provided by a meter 1502 and virtual points associated with a meter 1502 in the object database 1506. FIG. 15 illustrates an example in which three point objects 1518, 1520, and 1522 (representing points“pi,”“p2,” and“p3” respectively) are associated with a meter object 1516 (representing meter“Ml”). Each point object 1518- 1522 includes attributes for the corresponding point, for example the point name, the point location, the point’s units, and point type. The point type may indicate whether the point corresponds to a physical measurement or the point is a virtual point simulated within the BMS 1500. For a real point (i.e., a point corresponding to a physical measurement), the point object 1518-1520 may include the point source, indicating the meter associated with the point. For a virtual point, the point object 1522 may include a derivation formula which defines how a data series associated with the virtual point is derived from data associated with other points, from a model or simulation, or from based on some other dataset.

[0211] FIG. 16 illustrates that the points attribute of the meter object 1516 may list both real points and virtual points. In the example shown, points“pi” and“p2” are real points whereas point“p3” is a virtual point. As shown, by listing real points and virtual points together in the points attribute, the meter object 1516 treats real and virtual point objects identically and makes no differentiation between real and virtual points. Virtual point objects such as point object 1522 need not be organized or stored under separate virtual meter objects or otherwise differentiated at the level of the meter objects 1512. Instead, a virtual point obj ect 1522 is included under the meter obj ect 1516 to associate the virtual point p3 with a physical meter Ml, which is referred to herein as point virtualization under online meters. The BMS 1500 (e.g., the advanced metrics circuit 1510) may then use a virtual point like any other point in calculating meter roll-ups and key performance indicators and generating displays of meter information for users. Point virtualization under online meters thereby facilitates calculation of metrics that require points not provided by real meters, improves efficiency and reduces complexity relative to other potential ways to simulate points (e.g., by creating virtual meters), and provides an intuitive framework that facilitates a user in understanding and configuring virtual points.

[0212] Referring now to FIG. 17, a fl owchart of a process 1700 for point virtualization under online meters is shown, according to an exemplary embodiment. At step 1702, the analytics system 1504 associates a real point object for a real point with a meter object for an online meter 1502. The analytics system 1504 stores the real point object and the meter object in an object database 1506. In some embodiments, the analytics system 1504 associates the real point object with the meter object by listing the real point object or a designation thereof (e.g., point name) in a points attribute of the meter object. In some embodiments, the analytics system 1504 associates the real point object with the meter object by listing the meter object or a designation thereof (e.g., meter name) in a meter attribute of the point objects.

[0213] At step 1704, a virtual point is defined in the analytics system 1504, for example by a formula or other algorithm for calculating a value of the virtual point. For example, the virtual point may be defined as a function of real points, such that a value of the virtual point at a given time step may be calculated based on the values of real points for that time step (i.e., based on data collected by meters 1502). The virtual point may also, or alternatively, be defined to have a value generated by some other simulation, model, dataset, etc. In some embodiments, the analytics system 1504 receives user input defining the virtual point from a client device 504, for example as described with reference to FIGS. 18-20 below.

[0214] At step 1706, the analytics system 1504 associates the virtual point with the meter object. The analytics system 1504 may associate the virtual point with the meter object by listing the virtual point in an attribute of the meter object (e.g., a points attribute that lists the points associated with the meter, including both virtual points and real points). The meter object may thereby treat virtual points and real points identically. Higher-level calculations, roll-ups, etc. may then simply deal with all points in a similar or identical way, avoiding any computational complexity and expense that may be created by other approaches to point virtualization

[0215] At step 1708, the analytics system 1504 receives a data sample from an online meter 1502 for the real point. For example, the analytics system 1504 receives an analog or digital signal, measurement, data value, sample, or other value of the real point from the online meter 1502 associated with the real point. At step 1710, the analytics system 1504 assigns a value for the real point based on the data sample. For example, in an embodiment where the data sample is an analog signal, the analytics system 1504 may determine a digital representation of a numerical value of the real point based on the data sample and store that representation as the value of the real point.

[0216] At step 1712, a value for the virtual point is calculated based on the definition of the virtual point created at step 1704. For example, the virtual point may be calculated based on the data sample for the real point and/or based on data from other meters and/or other data sources (e.g., a weather forecast system, a building model simulation, a building schedule, etc.). For example, a virtual enthalpy point that represents the enthalpy of a fluid can be calculated based on real points that represent the temperature and pressure of the fluid.

[0217] At step 1714, the value for the real point from step 1710 and the value for the virtual point from step 1712 are associated with the meter 1502. That is, based on the association of the real point and the vi rtual point with the meter 1502 represented by the meter object (i.e., as created at step 1702), the analytics system 1504 associates the values for the real point and the virtual point with the meter 1502. At step 1716, the analytics system 1504 calculates a metric based on the values associated with the meter 1502, i.e., the value of the real point and the value of the virtual point. For example, the analytics system 1504 may add, multiply, average, or perform other mathematical operations on the values to calculate the metric. As another example, the values associated with the meter 1502 may be used with values associated with one or more additional meters 1502 to calculate a metric or a key performance indicator, or to generate a graphical representation of the operation of building equipment. In all such calculations, the analytics system 1504 treats the values in a substantially identical way, i.e., without regard to the real or virtual nature of the points.

[0218] Referring now to FIG. 18, a meter configuration interface 1800 for mapping and creating points under an online meter is shown, according to an exemplary embodiment.

The meter configuration interface 1800 may be generated by the analytics system 1504 (e.g., by the point virtualization circuit 1508) of FIG. 15. The meter configuration interface 1800 includes a points tree widget 1802, a meter distribution tree widget 1804, and a meter details widget 1806.

[0219] The points tree widget 1802 includes search features 1808, for example including drop down selections, list toggles, and/or a text search feature to allow- a user to find and select any point already created in the BMS 1500. Search results may be presented in the points tree widget 1802. The points tree widget 1802 thereby allows a user to search for and then select a point to add the point to a meter using the meter distribution tree widget 1804

[0220] The meter distribution tree widget 1804 provides a collapsible list 1810 of facilities and buildings. The collapsible list 1810 indicates that within each building are subcategories of building infrastructure (e.g., electricity, w-eather) or building subspaces (e.g., Floor 2). The collapsible list 1810 further includes entries for meters located with the appropriate subcategory. Listed meters may include a status indicator 1812 that shows whether the meter is online, offline, or virtual. A meter may be selected in order to add or delete a point under that meter. In some embodiments, the meter distribution tree widget 1804 allows the user to move the meter to a different subcategory, building, or facility to reassign the meter. In some embodiments, the meter distribution tree widget 1804 allows the user to delete the meter from the collapsible list 1810.

[0221] The meter details widget 1806 allows a user to add a new meter, a new virtual point, or a new online point. The meter details widget 1806 includes a type selection 1814 that allows a user to select whether they want to add a new meter, a new virtual point, or a new online point. When the user selects to add a new virtual point, the meter details widget displays entry fields 1816 that accept input of a point name, a point description, a unit type, a unit, a point role, and a series type. Some input fields may be indicated as optional, while others may be indicated as required for point creation. The meter details widget may also include a virtual point definition button 1818, wdiich is configured to open a virtual point definition widget 1900 (shown in FIG. 19) when selected by a user.

[0222] Referring now to FIG. 19, a virtual point definition widget 1900 is shown. Virtual point definition widget 1900 may be generated by the analytics system 1504 (e.g., by the point virtualization circuit 1508) of FIG. 15. The virtual point definition widget 1900 may include an equipment and meter tree 1902 that lists all equipment, meters, and existing points, organized hierarchically. The virtual point definition widget 1900 also includes a formula entry portal 1904. The formula entry portal 1904 includes a formula field 1906, a numeric value entry field 1908, and operator buttons 1910. A user may create a formula by selecting a point from the equipment and meter tree 1902 to add the point to the formula field 1906. The user may then select operator buttons 1910 to input mathematical operators (e.g., addition, multiplication, division) or logical operators (e.g., OR, AND, NOT, IF, <, >) to the formula field. The user may also input constant numeric values into the formula field using the numeric value entry field 1908. The user may enter multiple existing points, multiple mathematical and logical operators, and multiple constant numerical values into the formula field 1906 to craft a derivation formula for calculating the data output of the new virtual point.

[0223] The virtual point definition widget 1900 may also include a validate syntax button 1912. When the validate syntax button 1912 is selected, the analytics system 1504 may check the derivation formula in the formula field 1906 for syntax errors. Syntax errors include inoperable combinations of mathematical symbols and failed logical expressions. The system may check all possible point values for points in the formula field to ensure the formula will not encounter any errors and/or will always output a value for the virtual point. In some embodiments, the system highlights particular operators in the formula field that caused a syntax error or suggests corrections.

[0224] The virtual point definition widget 1900 may also include a save button 1914. The save button 1914 may be configured to only be selectable after the analytics system 1504 has validated the syntax of the derivation formula in the formula field. The save button 1914 allows the user to save the derivation formula for a new virtual point and return to the meter configuration interface 1800 shown in FIG. 18. The virtual point definition widget 1900 may also be used to edit derivation formulas for existing virtual points

[0225] Referring now to FIG. 20, a building scorecard dashboard 2000 is shown, according to an exemplary embodiment. The building scorecard dashboard 2000 includes a hierarchical navigation list 2002 of facilities, buildings, building subsystems or subareas, meters, and points. Meters on the navigation list may include a status indietor 2004 configured to show whether that meter is online, offline, or virtual. Points listed under meter include both real points and virtual points. When a meter is selected on the navigation list, a meter visualization widget 2006 may be displayed on the building scorecard dashboard. The meter visualization widget 2006 may include a graphical representation of the data associated with all points under the meter, include real and virtual points. Time selection 2008 may be available in the upper right comer and can be switched easily between one week, one month, three months, six months, one year, and any custom range. The graphical display may then be adjusted to display data from the selected time range. A grid toggle 2010 may also be available to easily switch between the graphical display and a display of the meter data in a grid format

[0226] The meter visualization widget 2006 presents data from a virtual point in the same way it presents data from real points. The building scorecard dashboard 2000 may also include displays of building and facility key performance indicators that include data roll ups from all meters in the buildings or facilities. Virtual points are treated identically to real points in these roll-up calculations and in generating visualizations for the building scorecard dashboard. Geolocation-Based Fault Notification Center

[0227] Referring now to FIGS. 21-24, systems and methods for geolocation-based fault notification are shown, according to exemplary embodiments. In a BMS, a fault notification system provides alerts and information to a user related to building equipment which are not functioning as expected, meters which are reporting points outside an expected range, or other data points which indicate some aspect of the BMS is in a fault condition. Traditionally, alerts and reported information may be organized chronologically, such that the most recent faults appear first on a fault notification interface, or may be organized by priority level or criticality. When the BMS components are located in many buildings or facilities distributed in a variety of geographic locations, a user may have difficulty in identifying the faults from the user’s current location. An automated system for geolocation -based fault notification as described in detail below may be provided to facilitate the presentation to a user of faults from the user’s current location in a BMS.

[0228] Referring now to FIG. 21, a geolocation-based fault notification system 2100 is shown, according to an exemplary embodiment. In some embodiments, the fault notification system 2100 is a component of a BMS, such as BMS 400 or BMS 500 described with reference to FIGS 4-5. For example, the fault notification system 2100 may be included as a component of the system manager 502 of FIG. 5. As shown in FIG. 21, the fault notification system 2100 is comrnunicably coupled to building equipment 2102 (e.g., HVAC system 100), an IP address database 2104, and a user device 2106 (e.g., client device 504).

[0229] Building equipment 2102 is operable to affect a variable state or condition of a building (e.g., temperature, humidity, airflow', lighting) and provide data samples of data points related to the functioning of the building equipment 2102. The user device 2106 may include a smartphone, tablet, laptop computer, desktop computer, and/or other personal computing device. The user device 2106 may include a network interface configured to allow the user device 2106 to communicate with the fault notification system 2100 via a network, for example the internet, a Wi-Fi network, a cellular network, or some other network. The user device 2106 may also include a global positioning system (GPS) chip that detects a location of the user device 2106 (e.g., in terms of GPS coordinates). The IP address database 2104 stores a look-up table that associates IP addresses with geographic location (e.g., with GPS coordinates). The IP address database 2104 may be maintained and operated by an internet service provider. [0230] As shown in FIG. 21, the fault notification system 2100 includes a fault detection circuit 2108, a building identifier circuit 2110, a geolocation filter circuit 2112, an authorization and security check circuit 2114, and a user interface generator circuit 2116. The fault detection circuit 2108 receives the equipment data samples from the building equipment 2102 and analyzes the data samples to detect faults in the operation of the building equipment 2102. Faults may be detected based on a library of fault rules which are applied to the data. Fault rules may be created by a user, provided by the BMS provider, or automatically generated by the BMS, for example as described in“Building Management System with Fault Detection & Diagnostics Visualization,” U.S. Patent Application No. 15/821,630 filed November 22, 2017, incorporated by reference herein in its entirety. The fault detection circuit 2108 may create an equipment fault data object for each detected fault which includes the name of the equipment in a fault condition and details related to the nature of the fault.

[0231] The fault detection circuit 2108 may then forward the list of faults or the equipment fault data objects to the building identifier circuit 2110. The building identifier circuit 2110 may look up the location of each of the faults (i.e., the l ocation of the equipment for which a fault was detected) using the equipment name or other identifier. In some embodiments, the building identifier circuit 2110 may store location information in an equipment location database. The building identifier circuit 21 10 then tags faults with a location indicator, for example by adding a location attribute to an equipment fault object. The building identifier circuit 2110 then sends the location-tagged faults to a geolocation- filter circuit 2112.

[0232] The geolocation filter circuit 21 12 receives the geolocation-tagged faults from the building identifier circuit 2110 and an indication of the user’s location from the user device 2106 and/or the IP address database 2104, and compares the location of the faults to the location of the user. The user’s location may be detected using a GPS chip in the user device 2106, such as a mobile phone, tablet, or personal computer, for example. The user’s location may also be detected by comparing the user’s internet protocol (IP) address (i.e., an IP address utilized by the user in accessing the fault notification system 2100) to an IP address database 2104 provided by internet service providers. In some embodiments, as described in detail with respect to FIG. 22, the user’s location may also be detected and verified by using a combination of both a GPS chip and the user’s IP address. Using the user’s location information, the geolocation filter circuit 21 12 identifies the building where the user is located from among multiple buildings and/or campuses served by the served by the building equipment 2102 For example, the geolocation filter circuit 2112 may compare GPS coordinates of a user to stored GPS coordinates associated with each building served by the building equipment 2102 and determine whether the GPS coordinates of the user (i.e., of the user device 2106) are within a preset distance of the stored GPS coordinates associated with a building.

[0233] The geolocation filter circuit 21 12 then aggregates the faults which are tagged as coming from the building where the user is located, and sends those faults to an

authorization and security check circuit 2114. The geolocation filter circuit 2112 may also prevent all other faults from being presented to the user, or may separate the other faults to be presented to the user separately from the faults from the user’s location. Advantageously, the faults from the building where the user is located are prioritized while other faults are hidden or removed, freeing the user from the inefficiencies, confusion, and errors that may be prevalent in other systems that require a user to read through all faults for all locations managed by a BMS in order to become of aware of a fault important to the user.

[0234] The authorization and security check circuit 2114 then checks whether the user has the authority to view the detected faults for the user’s location. The authorization and security check circuit 2114 may require the user to input a username and password via the user device 2106. The authorization and security check circuit 2114 may include a user ID management system, and may check a security token received from the user device 2106 against information in the user ID management system. If the authorization and security check circuit 2114 determines that the user is authorized to view the detected faults for the user’s location, the detected faults for the user’s location are sent to the user interface generator circuit 21 16.

[0235] The user interface generator circuit 2116 then generates a graphical user interface that presents the detected faults for the user’s location to the user. The user interface generator circuit 2116 may sort the detected faults for the user’s location based on equipment type, commodity type, sub-location, severity, criticality', or chronology (e.g., most recent first, longest-lasting first), or any other organization and present the faults in a list or some other format. The user interface generator circuit 2116 may also access other fault information stored in the fault object and populate the user interface with the information. This information may include a fault type, a fault name, an equipment type, an equipment device name, an equipment location, a fault duration, a fault priority, raw' data samples related to the fault, and fault timing data. An example of such a graphical user interface is shown in FIG. 24 and described in detail with reference thereto. The user interface generator circuit 2116 provides the user interface to the user device 2106. The user is thereby presented with an interface that displays faults from the user’s location and other fault information for those faults, while faults from other locations may he prevented from being shown to the user.

[0236] In some embodiments, the user interface generated by the user interface generator circuit 2116 may also present detected faults for locations other than the user’s location.

The detected faults for other locations may be listed after the detected faults for the user’s location on the user interface. In some embodiments, the list is automatically sorted to show the faults for the building in which the user is located at the top of the list. In some embodiments, the detected faults may be accessed by selecting an indicator for another location or locations on the user interface or by using a drop-down menu. A clear indication of the fault’s location may be presented to facilitate easy navigation of the fault notifications. The authorization and security check circuit 2114 may require a separate authorization and security check before allowing the user to view faults from another location.

[0237] Referring now to FIG. 22, a flowchart of a process 2200 for presenting fault notifications based on a user’s location is shown, according to an exemplary embodiment.

In some embodiments, the process 2200 is performed by the geolocation-based fault notification system 2100 of FIG. 21.

[0238] At step 2202, the fault notification system 2100 asks a user for consent to use the user’s location, for example by generating a prompt for display on the user device 2106. If consent is not received, the user wall be prevented from using the geolocation-based fault notification system. If user consent is received (e.g., via the user device 2106), at step 2204 a GPS chip in the user device 2106 (e.g., personal computer, mobile phone, tablet) is activated, and, at step 2206 the GPS coordinates of the user’s device are collected by the fault notification system 2100. The IP address of the user device 2106 may also be collected from the user device 2106 by the fault notification system 2100.

[0239] At step 2208, the fault notification system 2100 accesses an IP address database 2104 provided by one or more internet sendee providers and look up IP addresses associated with the GPS coordinates of the user’s device. Then, at step 2210, the fault notification system 2100 checks whether the IP address collected from the user’s device matches an IP address associated with the user’s GPS coordinates in the IP address database. The fault notification system 2100 may thereby combine two modalities of determining the user’s location to verify the user’s location. If the user’s GPS coordinates do not match an IP address for that location, the fault notification system 2100 may determine a security risk and prevent the user device from accessing fault notifications in the fault notification system 2100 at step 2212.

[0240] If the user’s GPS coordinates do match an IP address for the user’s location, at step 2214 the user’s location (e.g., the user’s GPS coordinates) is then associated with the building or facility at which the user is located and which is served by the BMS (e.g., BMS 500) and the building equipment 2102. The building or facility may be selected from a list of buildings or facilities served by the BMS. In some embodiments, if the user’s location is not in a building or facility served by the BMS, the fault notification system 2100 may associate the user with the nearest building or facility served by the BMS or may prevent the user from accessing the geolocati on-based fault system.

[0241] If the user’s location is matched to a building or facility served by the BMS, at step 2216 all fault notifications for that building or facility are found and aggregated by the fault notification system 2100. At step 2218, the fault notification system 2100 then determines whether the user has authorized access to view the faults for that building or facility. For example, the fault notification system 2100 may check a security token from the user device 2106 with an ID management system that stores user authorizations. If the user is determined to not have authorized access to the faults, the user is prevented from accessing the geolocati on-based fault syste and no faults are shown at step 2212.

[0242] If the user is determined to have authorized access to view the faults, at step 2220 the fault notifications are provided to the user, for example via a graphical user interface generated by the fault notification system 2100 and provided to the user device 2106. An example of such user interfaces are shown in FIGS. 23-24 and described in detail below.

[0243] Referring now to FIG. 23, a building management dashboard 2300 with a fault notification indicator 2302 is shown, according to an exemplary embodiment. In some embodiments, the building management dashboard 2300 is generated by BMS 400 or BMS 500, as described with reference to FIGS. 4-5 (e.g., by the system manger 502). The building management dashboard 2300 may include multiple widgets that show key performance indicators for the buildings or facilities and/or building equipment served by the BMS (e.g., building equipment 2102). The building management dashboard 2300 may be limited to show key performance indicators for the user’s location only, or may show information related to all facilities in the BMS. The building management dashboard 2300 includes a fault notification indicator 2302, located in the upper right comer in the example of FIG. 23. The fault notification indicator 2302 may be configured to change colors when a fault occurs and may display the number of current faults or the number of new fault notifications. An audible alarm may also be provided to indicate a new fault notification.

In some embodiments, the fault notifications indicated by the fault notification indicator 2302 may include fault notifications only for detected faults from the user’s location. The fault notification indicator 2302 may be selected by the user to access a fault notification interface, for example as shown in FIG. 24.

[0244] Referring now to FIG. 24, a fault notification interface 2400 is shown, according to an exemplary embodiment. In various embodiments, the fault notification interface 2400 is generated by the fault notification system 2100 of FIG. 21 and/or BMS 400 or BMS 500 of FIGS. 4-5. The fault notification interface 2400 may display the name 2402 of the building or facility of the user’s location, i.e., the location for which faults are shown (shown as “Location X - Building Y”). In some embodiments, the fault notification interface 2400 includes a location indictor 905 that states the location of the user. The fault notification interface 2400 may also present information related to each fault from the user’s location, shown as first fault 2401 and second fault 2403. The information for each fault 2401, 2403 may include a fault description 2404, a fault duration 2406, the name 2408 of the equipment in a fault condition, the name 2410 of the space where the fault is located, the latest timestamp 2412 of the fault, and a fault priority level 2414. The fault notification interface may also include other relevant information about the faults. The fault notification interface may also include a priority level drop-down menu 916 which allows a user to select to only view faults of a selected priority level (e.g , high priority, low' priority). The fault notification interface 2400 may thereby provide the user with information about the most relevant faults to the user.

[0245] In some embodiments, the fault notification interface 2400 includes one or more options to input a command relating to the building equipment. For example, the fault notification interface 2400 may allow' a user to input a command to turn off a unit of building equipment in a fault condition, turn on backup equipment, and/or adjust various settings of the building equipment to address a detected fault. The user interface generation circuit 2116 may receive a command input by a user via the fault notification interface 2400 and provide the command to the system manager 502. The system manager 502 may then control the building equipment as commanded by the user. In some embodiments, because the faults provided to the user on the fault notification interface 2400 may be limited to those within a geolocational proximity to the user (e.g., within a particular building), the building equipment controllable by the system manager 502 in response to a user command may also be limited to that geolocational area. Advantageously, the user may thereby be prevented from affecting the operation of bui lding equipment not located proximate to the user.

[0246] The construction and arrangement of the systems and methods as shown in the various exemplary embodiments are illustrative only. Although only a few embodiments have been described in detail in this disclosure, many modifications are possible (e.g., variations in sizes, dimensions, structures, shapes and proportions of the various elements, values of parameters, mounting arrangements, use of materials, colors, orientations, etc.). For example, the position of elements 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 exemplary

embodiments without departing from the scope of the present disclosure.

[0247] The present disclosure contemplates methods, systems and program products on any non-transitory 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 non-transitory machine-readable media for carrying or having machine-executable instructions or data structures stored thereon. Such non-transitory 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 n on-transitory 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 earn,_' 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.

[0248] 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.

Claims

1. A system comprising:

a plurality of data sources, each configured to receive respective data point values associated with a respective data point at a respective deposit frequency, and

a building enterprise managing device configured to perform an automatic synchronization process comprising:

receiving a user configuration setting comprising a read frequency at which data point values are to be obtained by the building enterprise managing device from a data source among the plurality of data sources;

obtaining, via a network, the data point values from the data source at the read frequency;

identifying a deposit frequency at which the data point values are received at the data source by analyzing the obtained data point values,

determining whether the read frequency matches the identified deposit frequency;

adjusting the read frequency to match the identified deposit frequency in response to determining that the read frequency does not match the identified deposit frequency; and

obtaining, via the network, the data point values from the data source at the adjusted read frequency which matches the deposit frequency at which the data point values are received at the data source.

2. The system of claim 1, wherein the building enterprise managing device is configured to repeat the automatic synchronization process according to a predetermined frequency

3. The system of claim 2, wherein the predetermined frequency is one day

4. The system of claim 1, wherein identifying the deposit frequency further comprises: the building enterprise managing device configured to analyze historical data relating to previous data point values, each data point value having a timestamp.

5. The system of claim 1, wherein the plurality of data sources are first data sources, the system further comprising;

a plurality of second data sources, each configured to provide the respective data point values to the respective first data source at the respective deposit frequency.

6. The system of claim 1, wherein the data source includes a data repository, and the data point values are deposited at the deposit frequency into the data repository of the data source.

7. The system of claim 6, wherein identifying the deposit frequency further comprises; the building enterprise managing device configured to scan for an interval that the data point values are deposited into the data repository of the data source.

8. The system of claim 1, wherein the data source corresponds to a heating, ventilating, and air conditioning (HVAC) equipment.

9. A method for automatic synchronization, comprising:

obtaining, by a building enterprise device having one or more processors, a user configuration setting comprising a read frequency at which data point values are to be read by the building enterprise device from a data source among a plurality of data sources; obtaining, by the building enterprise device via a network, the data point values fro the data source at the read frequency,

identifying, by the building enterprise device, a deposit frequency at which the data point values are received at the data source by analyzing the obtained data point values; determining, by the building enterprise device, that the read frequency does not match the identified deposit frequency;

adjusting, by the building enterprise device, the read frequency to match the identified deposit frequency in response to determining that the read frequency does not match the identified deposit frequency; and

obtaining, by the building enterprise device via the network, the data point values from the data source at the adjusted read frequency which matches the deposit frequency at which the data point values are received at the data source.

10. The method of claim 9, wherein the method for automatic synchronization repeats according to a predetermined frequency.

11. The method of claim 10, wherein the predetermined frequency is one day.

12. The method of claim 9, wherein identifying the deposit frequency further comprises: analyzing, by the building enterprise device, historical data relating to previous data point values, each data point value having a timestamp

13. The method of claim 9, wherein the data source includes a data repository, and the data point values are deposited at the deposit frequency into the data repository of the data source.

14. The method of claim 13, wherein identifying the deposit frequency further comprises:

scanning, by the building enterprise device, for an interval that the data point values are deposited into the data repository of the data source.

15. The method of claim 9, wherein the data source corresponds to a heating, ventilating, and air conditioning (HVAC) equipment.

16. An apparatus for automatic synchronization, the apparatus comprising:

a processor; and

a memory coupled to the processor, the memory storing computer-executable instructions, which when executed by the processor, cause the apparatus to:

receive a user configuration setting comprising a read frequency at which data point values are to be read by the apparatus from a data source among a plurality of data sources;

obtain, via a network, the data point values from the data source at the read frequency;

identify a deposit frequency at which the data point values are received at the data source by analyzing the obtained data point values;

determine that the read frequency does not match the identified deposit frequency; in response to determining that the read frequency does not match the identified deposit frequency, adjust the read frequency to match the identified deposit frequency; and

obtain, via the network, the data point values from the data source at the adjusted read frequency which matches the deposit frequency at which the data point values are received at the data source.

17. The apparatus of claim 16, wherein the memory stores the computer-executable instructions, which when executed by the processor, further cause the apparatus to identify the deposit frequency by analyzing historical data relating to previous data point values, each data point value having a timestamp.

18. The apparatus of claim 16, wherein the data source includes a data repository, and the data point values are deposited at the deposit frequency into the data repository of the data source.

19. The apparatus of claim 17, wherein the memory stores the computer-executable instructions, which when executed by the processor, further cause the apparatus to identify the deposit frequency by scanning for an interval that the data point values are deposited into the data repository_' of the data source.

20. The apparatus of claim 16, wherein the data source corresponds to a heating, ventilating, and air conditioning (HVAC) equipment.

21. A building management system compri sing:

a plurality of meters configured to provide data samples of a plurality of points relating to a building, the building comprising a plurality of spaces, each of the points associated with at least one of the plurality of spaces;

a space hierarchy database configured to store a sibling relationship for each of the points, each sibling relationship identifying two or more of the points as sibling points; and a batch metrics engine configured to:

receive a first data sample of a first point;

access the sibling relationship for the first point to identify one or more sibling points of the first point; aggregate the first data sample with one or more other data samples of the sibling points to generate a batch, and

calculate an aggregate metric using the first data sample and the one or more other data samples in the batch; and

a controller configured to adjust an operation of building equipment based on the aggregate metric, the building equipment operable to affect the plurality of points.

22. The building management system of claim 21, wherein:

the first point is provided by a first meter of the plurali ty of meters and the one or more sibling points are provided by one or more sibling meters of the plurality of meters; the first meter is associated with a first space and the one or more sibling meters are associated with one or more sibling spaces; and

the first space and the one or more sibling spaces are located within a common parent space

23. The building management system of claim 21, wherein the batch metrics engine is configured to generate the batch and calculate the aggregate metric in response to receiving the first data sample.

24. The building management system of claim 21, further comprising a timeseries storage database configured to store the data samples of the plurality of points, each of the data samples comprising a time stamp and a value of at least one of the one or more points.

25. The building management system of claim 24, wherein the bath metrics engine is configured to aggregate the first data sample and the one or more data samples of the sibling points to generate the batch by:

determining a relevant time period for calculating the aggregate metric;

selecting one or more of the data samples of the sibling points that have timestamps within the relevant time period in the timeseries storage database; and

retrieving the selected data samples from the timeseries storage database.

26. The building management system of claim 21, further comprising a current metrics database configured to store the aggregate metric.

27. The building management system of claim 26, further comprising a building analytics and presentation circuit configured to:

access the aggregate metric in the current metrics database; and

generate a graphical user interface that presents the aggregate metric to a user.

28. The building management system of claim 26, further comprising a building analytics and presentation circuit configured to:

access the aggregate metric and a plurality of additional metrics in the current metric database; and

calculate an advanced metric based on the aggregate metric and the plurality of additional metrics.

29. A method for managing a building, comprising:

providing, by a plurality of meters, data samples of a plurality of points relating to the building, the building comprising a plurality of spaces, each of the points associated with at least one of the plurality of spaces;

storing, by a space hierarchy database, a sibling relationship for each of the points, each sibling relationship identifying two or more of the points as sibling points;

receiving, at a batch metrics engine, a first data sample of a first point;

accessing, by the batch metrics engine, the space hierarchy database to identify one or more sibling points of the fi rst point based on the sibling relationship for the first point; aggregating, by the batch metrics engine, the first data sample with one or more other data samples of the sibling points to generate a batch;

calculating, by the batch metrics engine, an aggregate metric using the first data sample and the one or more data samples in the batch; and

adjusting an operation of building equipment based on the aggregate metric to affect the plurality of points.

30. The method of claim 29, wherein:

the fi rst point is provided by a first meter of the plurality of meters and the one or more sibling points are provided by one or more sibling meters of the plurality of meters; the first meter is associated with a first space and the one or more sibling meters are associated with one or more sibling spaces; and the first space and the one or more sibling spaces are located within a common parent space

31. The method of claim 29, wherein receiving the first data sample triggers the batch metrics engine to generate the batch and calculate the aggregate metric using the data samples in the batch

32. The method of claim 29, comprising storing the data samples provided by the plurality of points in a timeseries storage database, each of the data samples comprising a time stamp and a value of at least one of the plurality of points

33. The method of claim 32, wherein aggregating, by the batch metrics engine, the first data sample and the one or more data samples of the sibling points to generate the batch comprises:

determining a relevant time period for calculating the aggregate metric;

retrieving the selected data samples from the timeseries storage database.

34. The method of claim 29, further comprising storing the aggregate metric in a current metrics database.

35. The method of claim 34, further comprising:

accessing the aggregate metric in the current metrics database; and

generating a graphical user interface that presents the aggregate metric to a user

36. The method of claim 34, further comprising:

accessing the aggregate metric and a plurality of additional metrics in the current metric database; and

calculating an advanced metric based on the aggregate metric and the plurality of additional metrics.

37. A method for managing a building, comprising:

collecting, by a plurality of meters, data samples corresponding to a plurality of points associated with a plurality of spaces of the building, the spaces arranged in a space hierarchy;

determining sets of sibling points based on the space hierarchy, each set of sibling points corresponding to a metric for a space in the space hierarchy;

aggregating, for each set of sibling points, data samples corresponding to the si bling points;

calculating the metrics based on the aggregated data samples to generate calculated values for the metrics; and

controlling building equipment based on the calculated metrics to operate to affect a variable state or condition of the building.

38. The method of claim 37, further comprising:

storing the calculated values for the metrics in a database;

receiving a request fro a user to view one or more of the metrics;

in response to the request, retrieving the calculated values for the one or more metrics fro the database, and

providing the calculated values for the one or more metrics on a graphical user interface.

39. The method of claim 37, further comprising:

associating each data sample with a time stamp and a point; and

storing the data sample, the time stamp, and the point in a timeseries storage database.

40. The method of claim 39, wherein aggregating, for each set of sibling points, data samples corresponding to the sibling points comprises:

determining a relevant time period for calculating a first metric; and

identifying the data samples from the relevant time period based on the time stamps.

41. A building management system comprising:

at least one of a meter or equipment configured to provide data samples for a point; a point mapping system configured to: store a point object corresponding to the point and comprising a unit attribute;

store a template object corresponding to a building equipment metric and comprising an allowed units attribute;

access the point object to read the unit attribute;

access the template object to read the allowed units attribute; in response to a request to map the point object to the template object, determine whether the unit attribute matches the allowed units attribute; and

in response to a determination that the unit attribute matches the allowed units attribute, automatically map the point object to the template object; and

a system manager configured to:

calculate the building equipment metric using the samples for the point in response to mapping the point object to the template object; and

operate building equipment using the building equipment metric to affect a variable state or condition of a building.

42. The building management system of claim 41, wherein the point mapping system is configured to prevent the mapping of the point object to the template object in response to a determination that the unit attribute does not match the allowed units attribute.

43. The building management system of claim 41, wherein mapping the point object to the template object comprises updating a mapping attribute of the point object to reference the template object.

44. The building management system of claim 41, further comprising a graphical user interface generator configured to generate a graphical user interface that allows a user to input the request to map the point object to the template object.

45. The building management system of claim 44, wherein the graphical user interface generator is configured to provide an error notification on the graphical user interface in response to a determination that the unit attribute does not match the allowed units attribute.

46. The building management system of claim 44, wherein:

the graphical user interface comprises a points tree widget comprising a list of a plurality of points and an equipment template tree widget comprising a list of a plurality of templates; and

the graphical user interface allows a user to drag the point from the list of the plurality of points onto a template in the list of the plurality of templates to input the request to map the point object to the template object.

47. The building management system of claim 41, wherein:

the allowed units attribute identifies a plurality of allowed units; and

the unit attribute identifies a first unit; and

the point mapping validation circuit is configured to determine whether the unit attribute matches the allowed units attribute by determining whether the plurality of allowed units comprise the first unit.

48. A method for managing a building comprising

providing, by a meter, data samples for a point,

storing, by a point mapping system, a point object corresponding to the point, the point object comprising a unit attribute;

storing, by the point mapping system, a template object corresponding to a building equipment metric, the template object comprising an allowed units atribute;

accessing the point object to read the unit attribute;

accessing the template object to read the allowed units attribute;

in response to a request to map the point object to the template object, determining whether the unit attribute matches the allowed units attribute;

in response to a determination that the unit attribute matches the allowed units attribute, automatically mapping the point object to the template object;

calculating, by a system manager, a building equipment metric using the samples for the point in response to mapping the point object to the template object; and

operating building equipment using the building equipment metric to affect a variable state or condition of the building.

49. The method of claim 48, further comprising preventing, in response to a

determination that the unit attribute does not match the allowed units attribute, a mapping of the storage the point object to the template object.

50. The method of claim 48, wherein mapping the point object to the template object comprises updating a mapping attribute of the point object to reference the template object.

51. The method of claim 48, further comprising generating a graphical user interface that allows a user to input a request to map the point object to the template object.

52. The method of claim 51, further comprising providing an error notification on the graphical user interface in response to a determination that the unit attribute does not match the allowed units attribute.

53. The method of claim 51, further comprising:

providing, on the graphical user interface, a points tree widget comprising a list of a plurality of points and an equipment template tree widget comprising a list of a plurality of templates; and

allowing, on the graphical user interface, a user to drag the point from the list of the plurality of points onto a template in the list of the plurality of templates to input the request to map the point object to the template object.

54. The method of claim 48, wherein:

the allowed units attribute identifies a plurality of allowed units; and

the unit attribute identifies a first unit, and

determining whether the unit attribute matches the allowed units attribute comprises determining whether the plurality of allowed units comprise the first unit.

55. A building management system, comprising:

building equipment operable to affect a variable state or condition of a building; a meter configured to provide data samples for a point, the point relating to the building equipment;

a point mapping system comprising: a point object database configured to store a point object corresponding to the point, the point object comprising a unit attribute;

a template object database configured to store a template object corresponding to a building equipment metric, the building equipment metric comprising an allowed units attribute, and

a point mapping validation circuit configured to:

receive a user request to map the point to the template;

access the point object to read the unit attribute;

access the template object to read the allowed units attribute;

in response to the request to map the point to the template, determine whether the unit attribute matches the allowed units attribute; and

a system manager configured to:

control the building equipment using the building equipment metric to affect a variable state or condition of a building.

56. The building management system of claim 55, wherein the point mapping validation circuit is further configured to, in response to a determination that the unit attribute does not match the allowed units attribute, prevent a mapping of the point object to the template object.

57. The building management system of claim 55, further comprising a graphical user interface generator configured to generate a graphical user interface that allows a user to input the user request.

58. The building management system of claim 57, wherein the graphical user interface generator is configured to provide an error notification on the graphical user interface in response to a determination that the unit attribute does not match the allowed units attribute.

59. The building management system of claim 57, wherein:

the graphical user interface allows a user to drag the point from the list of the plurality of points onto the template in the list of the plurality of templates to input the request to map the point object to the template object.

60. The building management system of claim 55, wherein:

the allowed units attribute identifies a plurality of allowed units; and

the unit attribute identifies a first unit; and

61. A building management system cornpri sing:

a meter configured to provide data samples of a real point, the real point

corresponding to a first physical parameter measured by the meter;

an analytics circuit configured to:

store a real point object representing the real point;

store a meter object representing the meter, the meter object comprising a points attribute that lists one or more point objects associated with the meter object including at least the real point object; and

store a virtual point object representing a virtual point, the virtual point corresponding to a second physical parameter not measured by the meter; and

update the points attribute in the meter object to list the virtual point object as one of the point objects associated with the meter object.

receive a data sample of the real point from the meter;

calculate a value of the virtual point, and

calculate a metric based on the data sample of the real point and the value of the virtual point, and

a system manager configured to control building equipment using the metric to affect the first physical parameter and the second physical parameter.

62. The building management system of claim 61, wherein the analytics circuit is configured to calculate the value of the virtual point using a formula stored in the virtual point object.

63. The building management system of claim 62, wherein the analytics circuit is configured to generate a graphical user interface that allows a user to input the formula.

64. The building management system of claim 62, wherein the formula defines the value of the virtual point as a function of the data sample of the real point.

65. The building management system of claim 61, wherein the first physical parameter and the second physical parameter characterize operation of the building equipment.

66. The building management system of claim 65, wherein the analytics circuit is further configured to generate a graphical user interface that includes a graphical representation of the operation of the building equipment based on the data sample of the real point and the value of the virtual point

67. The building management system of claim 66, wherein the graphical user interface comprises a first indicator identifying the real point as real and a second indicator identifying the virtual point as virtual.

68. A method for managing a building, comprising:

collecting, by a meter, data samples of a real point, the real point corresponding to a first physical parameter measured by the meter;

storing a real point object representing the real point;

storing a meter object representing the meter, the meter object comprising a points attribute that lists one or more point objects associated with the meter object including at least the real point object, and

storing a virtual point object representing a virtual point, the virtual point corresponding to a second physical parameter not measured by the meter; and

updating the points atribute in the meter object to list the virtual point object in as one of the point objects associated with the meter object:

receiving a data sample of the real point from the meter; calculating a value of the virtual point;

calculating a metri c based on the data sample of the real point and the value of the virtual point; and

controlling, based on the metric, building equipment to affect the first physical parameter and the second physical parameter.

69. The method of claim 68, wherein calculating the value of the virtual point comprises:

storing a formula in the virtual point object; and

calculating the value using the formula.

70. The method of claim 69, comprising generating a graphical user interface that allows the user to input the formula.

71. The method of claim 69, wherein the formula defines the value of the virtual point as a function of the data sample for the real point.

72. The method of claim 69, wherein the first physical parameter and the second physical parameter characterize operation of the building equipment.

73. The method of claim 68, comprising generating a graphical user interface that includes a graphi cal representation of the operati on of the building equipment based on the data sample of the real point and the value of the virtual point.

74. The method of claim 73 comprising providing, on the graphical user interface, a first indicator identifying the real point as real and a second indicator identifying the virtual point as virtual.

75. A building management system, comprising:

building equipment operable to affect a variable state or condition of a building, a plurality of meters configured to collect data samples of a plurality of real points relating to an operation of the building equipment;

an analytics circuit configured to:

generate a graphical user interface, the graphical user interface compri sing: a points tree widget comprising a list of the plurality of real points; a meter distribution tree widget comprising a list of the plurality of meters; and

a meter details widget configured to allow a user to add a virtual point to the list of real points; and

receive data samples of the plurality_' ^· of real points;

calculate a value of the virtual point, and

calculate a metric based on the data samples of the plurality of real points and the value of the virtual point; and

a system manager configured to control the building equipment based on the metric.

76. The building management system of claim 75, wherein the graphical user interface comprises a virtual point definition widget configured to allow a user to input a formula that defines the virtual point.

77. The building management system of claim 76, wherein the analytics circuit is configured to generate the value of the virtual point using the formula and a first data sample of a first real point of the plurality of real points.

78. The building management system of claim 76, wherein the analytics circuit is configured to generate a graphical representation of an operation of the building equipment using the formula and the data samples of the plurality of real points.

79. The building management system of claim 76, wherein the virtual point definition widget comprises:

a formula field;

a list of the plurality of real points, each real point on the list of real points selectable to add the real point to the formula field; and

a plurality of operator buttons, each operator button selectable to add an operator to the formula field;

wherein the formula comprises one or more real points and one or more operators to define the virtual point as a function of the one or more real points.

80. The building management system of claim 79, wherein the analytics circuit is configured to check the formula input by the user for syntax errors.

81. A building management system comprising:

building equipment located in a plurality of locations and configured to provide data relating to operation of the building equipment; and

a fault notification system configured to:

collect the data from the building equipment;

detect a fault in the operation of the building equipment based on the data; identify a fault location of the fault from the plurality of locations;

identify a user location of the user from the plurality of locations;

determine whether the user location matches the fault location; and in response to a determination that the user location matches the fault location, provide a graphical user interface to a user;

wherein the graphical user interface provides information relating to the fault.

82. The building management system of claim 81, wherein the fault notification system is configured to prevent the user from accessing information about the fault in response to a determination that the user location does not match the fault location.

83. The building management system of claim 81, wherein the fault notification system is configured to verify the user location by:

receiving GPS coordinates of a user device from the user device;

receiving an IP address of the user device;

accessing a look-up table that associates a set of IP addresses with the GPS coordinates of the user device; and

determining whether the IP address of the user device is included in the set of IP addresses with the GPS coordinates of the user device.

84. The building management system of claim 81, wherein the fault notification system is configured to determine whether the user is authorized to access fault notifications for the fault location.

85. The building management system of claim 81, wherein the fault notification system is configured to generate a fault data object for the detected fault and include the fault location as an attribute of the fault data object.

86. The building management system of claim 81, wherein:

the plurality of locations comprises a plurality of buildings; and

the fault notification system is configured to identify the user location of the user from the plurality of locations by:

receiving GPS coordinates of a user device from the user device; and determining that the GPS coordinates of the user device are within a first building of the plurality of buildings.

87. The building management system of claim 86, wherein the fault notification system is configured to:

receive consent from the user to use a location of the user device; and

cause a GPS chip of the user device to activate and provide the GPS coordinates to the fault notification system in response to receiving the consent from the user.

88. A method for managing and controlling building equipment, comprising:

operating building equipment to provide data relating to operation of the building equipment, the building equipment located in a plurality of locations;

detecting a fault in the operation of the building equipment based on the data, identifying a fault location of the fault from the plurality of locations;

identifying a user location of the user from the plurality of locations;

determining whether the user location matches the fault location; and

in response to a determination that the user location matches the fault location, providing a graphical user interface to a user;

89. The method of claim 88, further comprising preventing the user from accessing information about the fault in response to a determination that the user location does not match the fault location.

90. The method of claim 88, further comprising verifying the user location by: receiving GPS coordinates of a user device from the user device;

receiving an IP address of the user device;

91. The method of claim 88, comprising determining whether the user is authorized to access fault notifications for the fault location.

92. The method of claim 88, comprising generating a fault data object for the detected fault and including the fault location as an attribute of the fault data object.

93. The method of claim 88, wherein identifying a user location of the user from the plurality of locations comprises;

receiving GPS coordinates of a user device from the user device;

determining that the GPS coordinates of the user devi ce are wi thin a present distance of the GPS coordinates of a first location of the plurality of locations.

94. The method of claim 93, further comprising;

receiving consent from the user to use the location of the user device; and causing a GPS chip of the user device to acti vate and provide the GPS coordinates in response to receiving the consent from the user.

95. A building management system comprising:

building equipment located in a plurality of locations and configured to provide data relating to operation of the building equipment, and

a fault notification system configured to:

collect the data from the building equipment;

detect a plurality of faults in the operation of the building equipment based on the data;

identify, for each of the plurality of faults, a fault location from the plurality of locations, identify a user location of a user device from the plurality of locations by causing a GPS chip of the user device to activate and provide the user location to the fault notification circuit;

identify a set of faults from the plurality of faults for which the fault location matches the user location;

generate a graphical user interface that identifies each fault of the set of faults; and

provide the graphical user interface to the user device.

96. The building management system of claim 95, wherein the graphical user interface comprises a list of the faults from the set of faults, the list organized based on a priority of each fault.

97. The building management system of claim 95, wherein the graphical user interface includes a list of each of the plurality of faults, the set of faults for which the user location matches the fault location positioned at a top of the list.

98. The building management system of claim 95, wherein:

the plurality of locations comprises a plurality' of buildings; and

the building equipment is operable affect variable states or conditions of the plurality_' of buildings.

99. The building management system of claim 97, wherein the building equipment comprises HVAC equipment.

100. The building management system of claim 95, wherein the fault notification system is configured to:

receive a security token from the user device; and

in response to receiving the security token, allow the user to access the graphical user interface.