Today we covered some important topics from deployment of the utility emissions channel to the set up of the net emissions channel.
Deploying the Utility Emissions Channel
We're currently working on deploying the utility emissions channel using docker swarm to Amazon web services cloud.
...
Will there be one Fabric network or multiple Fabric networks, one for each region? This we'll have to see. On each Fabric network there will only be one version of chain code running, so all members of the network have to be running with the same business logic and base data set. As long as the same business logic and data set can be used to map electricity used (KWH) to emissions (MtCO2e), we can all be on the same network. If it's a question of getting different data sets we can expand the data set. But if there will be different business logic altogether, then we'll have to have different networks. In that case, the networks would have to collaborate together on the net emissions channel, which is denominated in MtCO2e, instead of the utility emissions channel, which is denominated in KWH.
Net Emissions Channel
Then the question of how to develop a net emissions channel. The first question is: What exactly is the net emissions channel? After some discussion, the best analogy (from Sijo@ibm.com) was a "Climate Fitness App". Like a personal fitness app, it gathers data from many sources, then aggregates it together, and reports your overall fitness, in this case for climate-changing emissions. So remember – If the potato chips don't get you, climate change will. 
...
How do utility emissions relate to net emissions? Utility emissions are not really non-fungible tokens but immutable data. They should be grouped together, with the net data stored as a hash on the emissions token.
Cloud vs Distributed Resources
Finally we had a fun discussion about using cloud vs distributed resources, specifically where to store archival copies of utility bills and backup data. We can store a hash of the utility bill and supporting data on the ledger, but that will not get us back the original bill or data in case we need to verify the emissions calculations. So where do we store the original bills and data inputs?
...
Or should we go towards a fully distributed setup, with peer to peer nodes and storage eventually?
Upcoming Development
In case you'd like to join our development, we're working on quite a few things.
...