โ›ฝVerra VMR0006: Energy Efficiency and Fuel Switch Measures in Thermal Applications

Table of Contents

Introduction

Need and Use

Standard Stove Performance Testing

Different Cookstove Methodologies: Pros and Cons

Overview of Cookstove Methodologies

Policy Workflow

Policy Import

Available Roles

Token (Verified Carbon Unit)

Step By Step

Introduction

This policy focuses on the VMR0006 methodology, "Energy Efficiency and Fuel Switch Measures in Thermal Applications, v1.2." Developed as an extension of CDMโ€™s AMS-II.G, VMR0006 is particularly relevant for improved cookstove projects. This methodology revision aims to provide monitoring parameters and quantification methods, resulting in emission reductions. It provides alternative methods for monitoring parameters and quantifying emission reductions, largely allowing for the increased use of defaults and less frequent monitoring, therefore, maintaining lower project costs.

Need and Use

The VMR0006 methodology can be used by project developers working on improved cookstove projects. By utilizing default values and less frequent monitoring, VMR0006 helps reduce project costs while ensuring reliable data. The methodology focuses on several key areas, including adoption, usage, stacking (the use of multiple types of stoves within the same household), fuel consumption, fraction of non-renewable biomass (fNRB), and emission factors.

VMR0006 uses short cross-sectional surveys to establish adoption, usage, and stacking rates, similar to AMS-II.G but with more lenient monitoring requirements. Fuel consumption is determined using default values, historical data, or project-led surveys, with options for annual water boil tests to obtain stove efficiency or assume default efficiency depreciation rates. The methodology directs projects to use global averages, CDMโ€™s Tool 33, or CDM's Tool 30 for fNRB, with a 26% emission reduction discount for using Tool 30. Emission factors include point-of-use and upstream emissions for various gases, using IPCC values, which may lead to larger over-crediting compared to AMS-II.G. Rebound effects in the carbon market refer to increased technology usage due to improved energy efficiency, which can lead to higher overall emissions and offset some anticipated savings. In this methodology, rebound effects are not captured, leading to similar over-crediting. Additionality is granted if stoves are free or use the CDM's tool for demonstration, with leakage adjustments like AMS-II.G.

Standard Stove Performance Testing

Monitoring and evaluating improved cookstove performance is crucial for developing effective cookstove programs. There are three main types of stove performance tests: Water Boiling Test (WBT), Controlled Cooking Test (CCT), and Kitchen Performance Test (KPT).

Water Boiling Test (WBT): WBT is a laboratory test that evaluates stove performance during a controlled task (boiling and simmering water). It is simple, quick, and cost-effective but does not accurately reflect real cooking conditions. WBT is conducted by trained technicians in a controlled environment, revealing technical performance rather than actual household use.

Controlled Cooking Test (CCT): CCT measures stove performance when a local meal is prepared, either in a lab or field setting. It assesses performance under ideal conditions, simulating local practices. However, CCT still doesn't capture the full range of real-world variables like fuel variability and operator behavior differences.

Kitchen Performance Test (KPT): KPT is the primary field test used to evaluate stove performance in real-world settings, conducted in users' homes to assess actual impacts on household fuel consumption. KPTs provide the most accurate understanding of stove performance but are labor-intensive and intrusive, with results influenced by the less controlled environment.

Overall, improved cookstove performance testing involves balancing logistical complexities and realistic reflection of outcomes. While each test type has strengths and weaknesses, a combination of laboratory and field testing is recommended for comprehensive evaluation. This approach ensures that performance testing accounts for local food preparation and real-world usage, enhancing the reliability of results.

Different Cookstove Methodologies: Pros and Cons

VMR0006: VMR0006 provides a cost-effective solution by utilizing default values and less frequent monitoring, which helps reduce project costs while maintaining reliable data. However, this approach may not capture real-time variations in fuel use and emissions as precisely as continuous monitoring methods.

Gold Standard Metered Methodology: The Gold Standard Metered Methodology offers robust monitoring of stove usage and fuel consumption, ensuring high data accuracy and transparency. However, it involves higher costs due to the need for continuous monitoring equipment and may require more technical expertise to implement.

Clean Development Mechanism (CDM) AMS-II.G: The CDM AMS-II.G methodology is well-established and widely recognized, using conservative estimates to ensure credibility. However, it can be complex and costly to implement due to rigorous data requirements and may not be as flexible as other methodologies in adapting to local conditions.

Overview of Cookstove Methodologies

Various methodologies are used to quantify emissions reductions in cookstove projects, each with its own approach to monitoring and verification. These methodologies include cross-sectional surveys, kitchen performance tests (KPTs), and continuous monitoring systems (CMS). Cross-sectional surveys and KPTs are commonly used to gather data on stove adoption, usage, and fuel consumption, while CMS provides real-time data but at a higher cost. The methodologies also address issues such as stove stacking, rebound effects, and leakage to ensure accurate emissions reductions. More details on these methodologies can be found on the Berkeley Carbon Trading Project's website.

Policy Workflow

Policy Import

This policy is published to Hedera network and can either be imported via Github (.policy file) or IPFS timestamp.

Available Roles

  • Project Proponent - The project proponent is responsible for executing the emission reduction project. The project proponent must adhere to the requirements outlined by Verraโ€™s VCS program and provide evidence of the emission reductions achieved. Upon successful verification, the project proponent receives Verified Carbon Units (VCU) as an incentive for their emission reductions.

  • Verification and Validation Body (VVB) - The VVB plays a critical role in independently verifying and validating the project data submitted by the project proponent. They thoroughly assess the project's emission reduction potential, methodologies, and adherence to the policy guidelines. Based on their evaluation, the VVB either approves or rejects the project for registration.

  • Registry (Verra) โ€“ With Verra as the registry they take on responsibilities that encompass project intake, pipeline management, and final review of project descriptions and monitoring reports. This process ensures that emission reduction projects meet the highest standards before tokens are issued.

Token (Verified Carbon Unit)

Verified Carbon Unit (VCU) credits, each equivalent to one tonne of CO2.

Step By Step

  1. Import the policy using IPFS or Policy File. Once imported, you will be redirected to the policy configurator.

  1. Set the policy to Dry Run or Publish it using the dropdown. Then select โ€œGoโ€ or โ€œRegisterโ€.

  1. Create a new user and assign their role as the Project Proponent.

  1. Create a new project by clicking on the "New Project" button and enter all the required details.

  1. Once the project details are submitted, Verra can add it to the project pipeline.

  2. The Standard Registry can now add the project to the project pipeline by selecting โ€œAddโ€.

  1. Now, we create a new user and assign its role as the VVB.

  1. The VVB must now give their name. Once the VVBโ€™s name is set, the VVB waits for SR to approve it.

  1. Now we log in as SR and approve the VVB.

  1. Log in as the Project Proponent and assign the VVB to the project using the dropdown.

  1. Once the VVB is assigned, the VVB will now have access to the project for validation/verification.

  1. Once validated, we log in as Project Proponent and add a monitoring report.

  1. Once the report is submitted, we now log in as the VVB and validate the monitoring report by clicking on the โ€œVerifyโ€ button.

  2. Once the monitoring report is validated, we log in as the SR and click on โ€œMintโ€ to mint the tokens.

  3. Once minting is completed, we can view tokens in the โ€œVPsโ€ tab.

  4. The Trust Chain can also be viewed by clicking on the โ€œView Trust Chainโ€ button:

Last updated