Systems and methods for multi-tiered data storage abstraction layer

1. A multi-tiered data storage system for building management system (BMS) data, the data storage system comprising:

a plurality of data stores comprising:

a first data store configured to store the BMS data, the BMS data comprising (1) a value of a variable state or condition represented by the BMS data and (2) a timestamp indicating a time at which the variable state or condition represented by the BMS data occurs; and

a second data store configured to store a redundant copy of at least a portion of the BMS data stored in the first data store; and

a data access router configured to:

provide a consistent endpoint for the BMS data to an application that provides or consumes the BMS data regardless of whether the BMS data is stored in the second data store or the first data store;

obtain a requested data object of the BMS data from the second data store in response to a determination that the requested data object is available in the second data store;

obtain the requested data object from the first data store in response to a determination that the requested data object is not available in the second data store; and

determine whether to store the BMS data in the first data store or the second data store based on the timestamp of the BMS data indicating the time at which the variable state or condition represented by the BMS data occurs.

2. The multi-tiered data storage system of claim 1 , wherein:

the first data store is an operational data store;

the second data store is a cache data store;

the plurality of data stores further comprise a reporting data store; and

the data access router is configured to provide the consistent endpoint to the application that provides or consumes the BMS data regardless of whether the BMS data is stored in the first data store, second data store, or the reporting data store.

3. The multi-tiered data storage system of claim 1 , wherein the requested data object comprises at least one of:

a point data object comprising metadata describing a point in the BMS; or

a sample data object comprising a value of the point in the BMS.

4. The multi-tiered data storage system of claim 1 , wherein the data access router is configured to write the requested data object to the second data store after retrieving the requested data object from the first data store.

5. The multi-tiered data storage system of claim 1 , wherein the data access router is configured to write the requested data object to the second data store response to a determination that the requested data object is a most recent version of the requested data object.

6. The multi-tiered data storage system of claim 1 , wherein the data access router is configured to:

receive a new data object of the BMS data from the application; and

write the new data object to both the second data store and the first data store.

7. The multi-tiered data storage system of claim 1 , wherein:

the first data store is configured to store multiple values of a data object of the BMS data, the multiple values comprising a most recent value of the data object and one or more outdated values of the data object; and

the second data store is configured to store only the most recent value of the data object.

8. The multi-tiered data storage system of claim 1 , wherein the data access router is configured to:

determine a data storage capability of each of the plurality of data stores, the data storage capability of a data store indicating one or more types of data objects that the data store is capable of storing;

in response to receiving a new data object of the BMS data, determine a type of the new data object; and

store the new data object in each data store of the plurality of data stores for which the data storage capability of the data store indicates that the data store is capable of storing the type of the new data object.

9. The multi-tiered data storage system of claim 1 , wherein the data access router is configured to:

determine whether the requested data object is a most recent version of the requested data object in response to a determination that the requested data object is available in the second data store; and

remove the requested data object from the second data store in response to a determination that the requested data object is not the most recent version of the requested data object.

10. A method for storing data for a building management system (BMS), the method comprising:

providing a consistent endpoint for BMS data to an application that provides or consumes the BMS data regardless of whether the BMS data is stored in a first data store or a second data store, wherein the BMS data comprises (1) a value of a variable state or condition represented by the BMS data and (2) a timestamp indicating a time at which the variable state or condition represented by the BMS data occurs;

obtaining a requested data object of the BMS data from the second data store in response to a determination that the requested data object is available in the second data store;

obtaining the requested data object from the first data store in response to a determination that the requested data object is not available in the second data store; and

determine whether to store the BMS data in the first data store or the second data store based on the timestamp of the BMS data indicating the time at which the variable state or condition represented by the BMS data occurs, wherein:

the first data store is configured to store the BMS data; and

the second data store is configured to store a redundant copy of at least a portion of the BMS data stored in the operational data store.

11. The method of claim 10 , wherein:

the first data store is an operational data store;

the second data store is a cache data store; and

the method further comprises providing the consistent endpoint to the application that provides or consumes the BMS data regardless of whether the BMS data is stored in the cache data store, the operational data store, or a reporting data store.

12. The method of claim 10 , wherein the requested data object comprises at least one of:

a point data object comprising metadata describing a point in the BMS; or

a sample data object comprising a value of the point in the BMS.

13. The method of claim 10 , wherein the method further comprises writing the requested data object to the second data store after retrieving the requested data object from the first data store.

14. The method of claim 10 , wherein the method further comprises writing the requested data object to the second data store response to a determination that the requested data object is a most recent version of the requested data object.

15. The method of claim 10 , wherein the method further comprises

receiving a new data object of the BMS data from the application; and

writing the new data object to both the second data store and the first data store.

16. The method of claim 10 , wherein:

the first data store is configured to store multiple values of a data object of the BMS data, the multiple values comprising a most recent value of the data object and one or more outdated values of the data object; and

the second data store is configured to store only the most recent value of the data object.

17. The method of claim 10 , wherein the method further comprises:

determining a data storage capability of each of the plurality of data stores, the data storage capability of a data store indicating one or more types of data objects that the data store is capable of storing;

in response to receiving a new data object of the BMS data, determining a type of the new data object; and

storing the new data object in each data store of the plurality of data stores for which the data storage capability of the data store indicates that the data store is capable of storing the type of the new data object.

18. The method of claim 10 , wherein the method further comprises:

determining whether the requested data object is a most recent version of the requested data object in response to a determination that the requested data object is available in the second data store; and

removing the requested data object from the second data store in response to a determination that the requested data object is not the most recent version of the requested data object.

19. A building management device for storing building management system (BMS) data, the building management device comprising one or more processing circuits configured to:

provide a consistent endpoint for BMS data to an application that provides or consumes the BMS data regardless of whether the BMS data is stored in a first data store or a second data store, wherein the BMS data comprises (1) a value of a variable state or condition represented by the BMS data and (2) a timestamp indicating a time at which the variable state or condition represented by the BMS data occurs;

obtain a requested data object of the BMS data from the second data store in response to a determination that the requested data object is available in the second data store;

obtain the requested data object from the first data store in response to a determination that the requested data object is not available in the second data store; and

determine whether to store the BMS data in the first data store or the second data store based on the timestamp of the BMS data indicating the time at which the variable state or condition represented by the BMS data occurs,

wherein:

the first data store is configured to store the BMS data; and

the second data store is configured to store a redundant copy of at least a portion of the BMS data stored in the first data store.

20. The device of claim 19 , wherein:

the first data store is an operational data store;

the second data store is a cache data store; and

the one or more processors are further configured to provide the consistent endpoint to the application that provides or consumes the BMS data regardless of whether the BMS data is stored in the cache data store, the operational data store, or a reporting data store.

21. The system of claim 1 , wherein determining whether to store the BMS data in the first data store or the second data store based on the timestamp of the BMS data comprises:

comparing the timestamp to a time threshold; and

determining whether to store the BMS data in the first data store or the second data store based on whether the timestamp is before or after the time threshold.

22. The system of claim 1 , wherein determining whether to store the BMS data in the first data store or the second data store based on the timestamp of the BMS data comprises:

comparing the timestamp to a time threshold; and

moving the BMS data from the second data store to the first data store responsive to determining that the timestamp is before the time threshold.