Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

We're currently implementing the Utility Emissions Channel and Emissions Tokens Network use case cases together. 

If you're interested, please check the calendar for the next call

...

  • Customer contacts Auditor to request that its CO2 emissions from its Utility bill be calculated.
  • Auditor sends an authorization request for data access from the Utility to the Customer.  This could be an emailed link or a paper document, see Green Button standards.
  • Customer grants the authorization request, by clicking on agree or sending back the paper document.
  • Utility grants Auditor access to Customer's bill data.
  • Auditor downloads Customer bill data from Utility, applies the emissions factors from a published database like the Emissions & Generation Resource Integrated Database (eGRID).
  • Auditor publishes the Customer's CO2 emissions on the channel.
  • Customer access channel to obtain his calculated CO2 emissions.

Image RemovedImage Added

Set Up the Channel

...

The emissions data are not tokens and not meant for transactions.  The emissions data can be used to create a token which is suitable for transaction as part of the Net Emissions Tokens Network.  For example, the emissions data from a full month or several months could be used to create a token.  The token may require that the emissions data used covers enough of the time period, and that there are no overlaps of emissions data.

...