Aspects addressed by GSN Protocol
GSN protocol includes requirements and guidance on the following aspects:
- How to determine if the project is additional? Would the project have proceeded anyways, without the benefit of the carbon credits? If yes, then the project is not considered additional and it is not eligible to generate carbon credits.
- How to pick an appropriate baseline? The protocol provides guidance to the proponent on how to pick a baseline to compare the project against to determine the emissions reductions. The baseline is what would have happened in the absence of the project. It is not necessarily the status quo. One other important assumption about the project and the baseline is that they need to provide the same level of service. For example if the project is contemplated to provide web services for a new company, then the baseline conditions would be the provisions of the same web services for the new company. The emissions in the project are compared to the emissions in the baseline to determine the emissions reductions attributable to the project.
- What are the sinks sources and reservoirs (SSRs) which need to measured and estimated? The protocol also provides guidance on which SSRs need to be measured and estimated in the project and the baseline in order to determine the emissions reductions.
- How will the emissions reductions be calculated? The protocol also provides guidance to the proponent on how to calculate the emissions in the project and baseline. This is the methodology that needs to be applied to the project and could include formulas, values and other information and parameters that will need to be determined to calculate the emissions in the baseline and the project.
- How does one calculate an equivalent level of service? The protocol also provides guidance and possibly requirements to the proponent on how to calculate the level of service in the project. For many projects this is simply understanding and measuring the number of widgets produced or the number of tonnes of steel produced. For IT projects, this is not quite so simple. At this point in time, we have assumed that workload is the functional level of service and will be the same in the project and the baseline (i.e. the demand for IT services is growing and will be the same).
GSN Protocol development steps
The Greenstar Consortium has been taking a collaborative approach to develop the protocol. This approach includes a number of meetings and other tools (Wiki) to encourage communication and collaboration between the technical teams. The development process, as shown below, has evolved as the team has determined the best way to collaborate, share information, integrate technical details and move the document forward.
Last Updated on Monday, 01 August 2011 19:09