๐ŸŒฉ๏ธAMS-I.E Switch from Non-Renewable Biomass for Thermal Applications by the User

Table of Contents

Introduction

Need and Use

Standard Stove Performance Testing

Different Cookstove Methodologies: Pros and Cons

Overview of Cookstove Methodologies

Demo Video

Policy Workflow

Policy Import

Available Roles

Tools Referenced

Token (Carbon Emission Reduction)

Step By Step

Introduction

This policy focuses on the AMS-I.E methodology, "Switch from Non-Renewable Biomass for Thermal Applications by the User." The methodology is designed to facilitate the generation of thermal energy by introducing renewable energy technologies for end-users, thereby displacing the use of non-renewable biomass. These technologies include, but are not limited to, cookstoves using renewable biomass, biogas stoves, bio-ethanol stoves, and electric cookstoves powered by renewable energy sources. By providing clear guidelines for monitoring parameters and quantifying emission reductions, AMS-I.E aims to ensure reliable data and effective implementation of renewable energy solutions in households, communities, and institutions.

Need and Use

The AMS-I.E methodology can be utilized by project developers aiming to reduce greenhouse gas (GHG) emissions through renewable energy technologies in thermal applications. This methodology supports the displacement of more GHG-intensive, non-renewable biomass-fueled applications by introducing renewable energy technologies. Key applications include cookstoves using renewable biomass, biogas stoves, bio-ethanol stoves, and electric cookstoves powered by renewable energy systems.

AMS-I.E encompasses activities that replace the use of non-renewable biomass with renewable energy technologies in households, communities, and institutions such as schools, prisons, and hospitals. Additionally, it outlines the requirements for electric cookstoves to ensure a high percentage of renewable energy use and limits the use of backup diesel generators.

By adhering to the AMS-I.E methodology, project developers can achieve significant emission reductions, promote the use of renewable energy, and contribute to sustainable development. This methodology also includes provisions to prevent double counting of emission reductions and ensures the safety and compliance of bio-ethanol cookstoves with relevant standards.

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.

Demo Video

Youtube

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 Participant - The project participant is responsible for executing the emission reduction project. The project participant must adhere to the requirements outlined by the CDM and provide evidence of the emission reductions achieved. Upon successful verification, the project participant receives certified emission reduction (CER) tokens 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 participant. 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 (UNFCCC) - The United Nations Framework Convention on Climate Change (UNFCCC) serves as the registry for the CDM. They oversee the multiple workflow steps involved in the project's approval, including the verification and validation process by the VVB. The UNFCCC's approval is necessary for the project's successful registration and issuance of CER tokens.

Tools Referenced

  • Methodological Tool 03 - Tool to calculate project or leakage CO2 emissions from fossil fuel combustion.

  • Methodological Tool 16 - Project and leakage emissions from biomass.

  • Methodological Tool 19 - Demonstration of additionality of microscale project activities

  • Methodological Tool 21 - Demonstration of additionality of small-scale project activities

  • Methodological Tool 30 - Calculation of the fraction of non-renewable biomass

  • Methodological Tool 33 - Default values for common parameters.

Token (Carbon Emission Reduction)

Certified Emission Reduction (CER) credits, each equivalent to one tonne of CO2.

Step By Step

  1. Log in as the Standard Registry and import the policy either by file or through IPFS timestamp by selecting the third button at the top right.

  1. Once the policy has successfully imported, you will be redirected to the policy configurator. The policy configurator can be used to edit the policy using the workflow blocks. There will also be a tab for the โ€œToolsโ€ used within this policy as illustrated in the image below. To start using the policy you must first change the status of the policy from โ€œDraftโ€ to โ€œDry Runโ€ or โ€œPublishโ€, then select the โ€œRegisterโ€ or โ€œGoโ€ button. This can be done through the policy configurator page or though the โ€œPoliciesโ€ page.

  1. Create a new user by clicking the โ€œCreate Userโ€ button and assign their role as โ€œProject Participantโ€.

  1. The Project Participant can now provide their name or the name they would like to see reflected when registering for this project (i.e. their organizationโ€™s name).

  1. ะกreate a new user again and assign their role as โ€œVVBโ€.

  1. The VVB can now provide their name or the name they would like users to see when reviewing projects (i.e. their organizationโ€™s name).

  1. Log in as the SR and select the โ€œProject Participantsโ€ or the โ€œVVBsโ€ tab to view the documents submitted by the Project Participant and by the VVB. The SR can approve their requests by clicking on the โ€œApprove" button.

  1. Log in as the Project Participant and create a new project by clicking on the "New Project" button. This form is used to collect information about the project, organization, and all the data needed to run the emission reduction calculations. Once all the required fields have been filled the โ€œCreateโ€ button will turn dark blue. By selecting the โ€œCreateโ€ button all the data will be sent to the SR for review/approval.

  1. Log back in as the SR and after reviewing the document located in the โ€œProjectsโ€ tab, the SR can validate the project submitted by the Project Participant by clicking the โ€œValidateโ€ button. If the data does not satisfy the rules set by the SR, then the โ€œRejectโ€ button can be used.

  1. Log in as the Project Participant and create a monitoring report by clicking on the โ€œAdd Reportโ€ button then fill out the monitoring report form.

  1. After creating the monitoring report, the project participant assigns the VVB to verify it by navigating to the โ€œMonitoring Reportsโ€ tab and selecting the dropdown under โ€œAssignโ€.

  2. Log in as the VVB and click the โ€œMonitoring Reportsโ€ tab to review the document submitted by the Project Participant. After reviewing the monitoring report by selecting โ€œView Documentโ€, the VVB can select โ€œVerifyโ€.

  3. Log in as the SR to review the monitoring report by selecting the โ€œView Documentโ€ button in the โ€œMonitoring Reportsโ€ tab. The SR can approve the monitoring report by selecting โ€œApproveโ€. This will also trigger the minting process. You can see the minting status under โ€œStatusโ€ change from โ€œMintingโ€ to โ€œMintedโ€.

  4. Once the minting process is completed, you can view the token amount by navigating to the โ€œVPsโ€ tab.

  5. The TrustChain can also be viewed by clicking on the โ€œView TrustChainโ€ button. Please note that the token amount may show โ€œ8380/54167โ€ when the tokens are still minting like the example provided below. Once all the tokens have been minted the token transfer will begin.

Last updated