The below hypothetical building provides an example to help understand how the Bluenote Protocol and different modules work in the real-world.
The Building first engages with the Bluenote Protocol by establishing its own data streams on its own node to connect with the network. In this case, it is being helped by an energy services company that specializes in the Bluenote Protocol.
1. Uses Bluenote’s template code to create a node on its own cloud server or uses the already-established node of its energy services company.
2. Uses a simple web interface product developed by Bluenote to upload static building information such as size, location, floor plate, building envelope, major mechanicals, and other data.
3. Connects Bluenote-compatible hardware devices with its utility electricity meter and building automation system to provide a direct data upload of its real-time data to a data stream.
4. Chooses to make a further small investment to install sensors to collect temperature, air quality, occupancy, and daylight data throughout its building, and maps the data streams to a 3D building model.
Participants gain tokens based on the uploading and connecting certain types of data to the protocol, with different token values based on the data type, quality, and frequency. In this scenario, the building chooses to share all of its data streams to be used by the data community. It receives the most tokens for its real-time data streams.
The four streams of data that the building has established in the node and connected to the Bluenote Protocol - static data, electric meter data, automation system data, and sensor data - are mapped as separate data streams with their own unique identifier. The decision to combine those data streams together, creating personally identifiable information, can only be made by the building by sharing the data stream keys for each data stream and identifying them as connected.
The building connects to the Module Marketplace developed by Bluenote to shop and compare for building analytics software providers, review ratings and feedback, and compare prices in Bluenote tokens.
The building decides to purchase two Recommendations Modules through the Marketplace.
First, it selects a Recommendations Module that provides the building with an hourly baseline based on its historical electricity usage data, weather patterns, and occupancy patterns. It uses some of its reward tokens for the purchase of this module. The building shares its historical data stream ID, its base building static data stream ID for location data, and its occupancy data stream ID from its sensor data through the smart contract along with enough tokens to pay for the software service.
Once accepted, the third-party module uses those IDs to identify the data locations and run its analysis module, with the output of the module becoming its own data stream with its own unique ID that is shared back with the building.
The building wants to display the hourly baseline data stream from the module provider on a dashboard app, so it can track its performance against the baseline in real time. It adds the data stream to its Bluenote-partnered dashboard simply by entering the baseline data stream ID into the dashboard interface. The building will use this dashboard to display several pieces of relevant data to its building operators on a real time basis, all pulled from various module outputs.
Now, the building wants to compare its energy intensity against substantially similar buildings. It visits the Marketplace to shop for a second Recommendations Module to do just that. This time, however, it doesn’t have enough reward tokens to pay for the module, so the building buys bluenotes on an exchange to pay for the additional service. This module is slightly more expensive than the baseline module, because running this module requires the module service provider to provide small kickbacks to other buildings in the community for using their data to complete the analysis.
The building has partnered with its local utility to enroll in a pay-for-performance energy efficiency program, allowing the building to get paid on a cents-per-kilowatt hour basis for verified whole building energy efficiency reductions.
As part of this program, the utility joins the Bluenote community and chooses an Attributes Module to calculate the verified energy efficiency performance of the building. Because the building has real-time data flowing in to the protocol, the utility is able to use an open source real-time measurement and verification Attributes Module that it has reviewed and trusts, that calculates the building’s real time energy performance vs. its modeled baseline to come up with an hourly kilowatt-hour saved metric. The utility buys bluenotes on an exchange to pay for running this Attributes Module and asks the building to submit its data stream IDs as part of the smart contract.
The utility receives as an output a data stream ID of a verified energy efficiency savings metric that is permanently traceable back to the source data of the building, avoiding the need to run a separate, offline, third-party statistical analysis that does not have access to all the building’s data.