You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 15 Next »

Join our Peer Programming Call-In

We're going to start implementing the Utility Emissions Channel use case together to demonstrate the idea described here.  Join our zoom call to code with us:

When:
Tuesday, 18 August 2020
9:00am to 10:00am
(UTC-07:00) America/Los Angeles

Where:
https://zoom.us/my/hyperledger.community



This Minimum Viable Product will use these key concepts from the Multi Channel Data Architecture to build applications described in Carbon Accounting and Certification Working Group

  1. Access data from several permissioned channels.
  2. Use standard model-factors to calculate emissions from the data.  
  3. Record the emissions results on a permissioned channel for the next entity to consume.
  4. Minimalist apps which
    1. run as serverless micro services, for example on Amazon Lambda or Cloud Functions from Google or IBM;
    2. pass through customer authentication keys to the permissioned channels

In each process, it will simulate the roles of:

  • Data source, which provides product use data
  • CO2 emissions auditor, which calculates CO2 emissions from the product use data
  • Data consumer, which uses the CO2 emissions data to calculate their own emissions, purchase offsets, etc.

The MVP will allow self-contained carbon emissions calculators for different purposes, as well as simulate how carbon emissions data could be shared across a supply chain with multiple parties.

Potential data sources include:

  • Utility bills 
  • Shipping data
  • Travel data
  • Vehicle trip data
  • Renewable Energy Certificates
  • Carbon offsets 

By combining these data sources together, we could build many different types of carbon emissions calculators fairly easily, including:

There are probably a lot of other examples, so feel free to add more ideas here!

  • No labels