Let's take a look at a very specific use case: a permissioned Hyperledger Fabric channel where an auditor calcualtes the emissions of a customer's electricity based on its utility bill. The same pattern could be repeated for other data services (travel, commute, shipping, etc.)
Players
Problem Statement
Get an audited GHG emissions for energy purchased from utility.
Audited by whom ?→ GHG Protocol Scope 2, eGRID database
Interactions
Set Up the Channel
The first step is to set up the channel, with the following organizations:
- Utility – utility which generates electricity and provides energy use data
- Auditor Auditors – trusted third-party which calculates CO2 emissions from utility energy use and published data sources
- Customers – customers of the utility who used electricity and need to get their CO2 emissions data
- Channel Operator – a third party which operates the channel, including maintaining the Orderer and Anchor Peer and allowing new organizations into the channel. In real life this Channel Operator would probably operate on behalf of the utilities and the customers who use it, under the supervision of a governance entity.
- Peer Node Operator – third parties whose only role is to operate a Peer Node. In real life these may be independent "validators" who earn a small fee for maintaining the data on the channel.
and roles:
...
Problem Statement
Customer would like to get audited GHG CO2 emissions for the energy it purchased from Utility.
Emissions from energy purchased by a company need to be calculated according to Greenhouse Gas Protocol Scope 2. In GHG Protocol Scope 2 Guidance (see pages 11 and 26), the emissions for purchased energy should be calculated from utility bills and emission factors, which should be based on local source if available, then grid and finally national level data if more precise data is not available.
In the United States, the Emissions & Generation Resource Integrated Database (eGRID) is a source of audited emissions factors for different utilities and grids.
Interactions
Customer requests CO2 emissions from Auditor
- Customer requests CO2 emissions calculation from Auditor
- Customer authorizes the third party auditor to access his data from the utility
- Auditor gets the utility bill and applies government carbon emissions data to calculate emissions and puts them on the channel.
- Auditor grants access to the channel, initially to the customer and the utility, but also to other trusted parties.
- Customer gets data from the channel and uses it for his own total CO2 emissions calculations.
Set Up the Channel
The first step is to set up the channel, with the following organizations:
- Auditor 1
- Auditor 2
Each Auditor will have its own Orderer, Peer Node, and Certificate Authority
...
.
The Use Case
Customer contacts Auditor to request that its CO2 emissions from its Utility bill be calculated.
...