Vai al contenuto principale
VCS avoidance Brazil Vintage 2012, 2016 Registry: Registered Documentazione completa General Methodology v2.0

Engenheiro Ernesto Jorge Dreher And Engenheiro Henrique Kotzian Shps VCS Project (Jun1120)

VCS-708 ↗

5.1 / 10
Integrity
5.2
Transparency
5.0
Claim Safety
4.3
Documentation
6.4

Score Breakdown

Integrity

verified The validation report confirms additionality and applies ACM0002 for grid-connected renewable electricity.

missing Leakage is inconsistently treated across monitoring reports and several corrective actions relate to core monitoring parameters and generation data quality.

Transparency

verified Key project identifiers, VVB name (Earthood), monitoring period (2011–2012), and ER totals are present in the extracted record.

missing Contradictory ER figures and multiple corrective actions reduce confidence that reported numbers are consistently traceable and reproducible.

Claim Safety

verified The claimed and verified ER totals match at 56,202 in the extracted record for the monitoring period.

missing CORSIA and CCP status are not stated in available documents, and contradictions in ER totals and crediting period elevate over-crediting/claims risk.

Documentation

verified A relatively large document set was used (20) with high extraction confidence and named VVB.

missing Several internal inconsistencies across official documents (and within the same dated validation record) indicate documentation control/versioning problems.

Detailed Analysis

Integrity

The validation report confirms additionality via an investment test and the project applies ACM0002, which supports a credible grid-displacement accounting approach. However, leakage is not consistently handled: an older monitoring report deems leakage negligible, while a later monitoring report does not address leakage at all. The 2021 monitoring report also lists multiple corrective actions tied to monitoring plan completeness, spreadsheet calculation errors, and mismatches in net energy generation figures cross-checked against CCEE, which undermines confidence in quantified ERs.

Transparency

The extracted record includes the monitoring period (2011–2012), the VVB (Earthood Services Private Limited), and ER totals, suggesting some core disclosure is available. Transparency is weakened by contradictions in key headline numbers (verified ER totals) and by the monitoring report’s corrective actions indicating that not all required parameters were presented and that some parameters reported were not part of the registered monitoring plan. These issues make it harder for third parties to independently reproduce results from the documentation set.

Claim Safety

Over-crediting risk is elevated by inconsistencies in the ER figures and by MRV issues flagged as corrective actions in the monitoring report (including generation data discrepancies and calculation errors). CORSIA eligibility and CCP status are not stated in available documents, so buyers cannot easily assess alignment with higher-integrity claim frameworks. Leakage treatment inconsistency (negligible vs not addressed across monitoring reports) further increases uncertainty around net climate benefit claims.

Documentation

Documentation coverage is moderate: multiple document types are present (monitoring report, validation report, PDD) and the extraction confidence is high, which supports usability. Nonetheless, the monitoring report includes several corrective actions that point to incomplete or inconsistent presentation of monitoring parameters and spreadsheet errors, indicating documentation quality control issues. Contradictions across documents (and within the same dated validation record) also reduce confidence that the document set is internally consistent and well-versioned.

Overall

Overall quality is mid-range because additionality is VVB-confirmed and the methodology is standard, but MRV reliability and internal consistency are material concerns. For contradictions, I privileged the more recent documents when they are clearly updates (e.g., the 2021 monitoring report over the 2012 monitoring report for whether safeguards/grievance mechanisms are mentioned), but I still penalized the score because the change suggests inconsistent reporting over time. For additionality test type, I privileged the validation report (investment test) over the PDD (barrier) because the VVB’s determination is higher assurance, but the discrepancy still reduces confidence. The most serious issue is the conflicting verified ER totals (56,202 vs 196,522) reported within the same dated validation record (2021-09-06); because this cannot be resolved from the extracted record, I used the 56,202 value consistent with the monitoring-period ERs but applied a significant downward adjustment for reliability. For the crediting period, I privileged the validation report’s later period (2019–2029) as the more authoritative crediting-period statement, while noting the monitoring report’s different period indicates version/control problems.

Audit Analysis

This VCS small hydropower project has VVB-confirmed additionality and uses an established grid-connected renewable methodology (ACM0002), but key MRV elements show reliability weaknesses. Multiple corrective actions and several cross-document inconsistencies (including verified ER figures and crediting period) increase over-crediting and claims risk.

Project Description

This project generates electricity using renewable hydropower plants in Júlio de Castilhos and Salto Jacuí, Brazil. The project includes two plants, the Engenheiro Ernesto Jorge Dreher SHP and the Engenheiro Henrique Kotzian SHP, with installed powers of 17.95 MW and 13.230 MW, respectively. The project aims to reduce the use of fossil fuel-based power generation and provide electricity to the National Interconnected System.

Red Flags

  • Conflicting verified emission reduction totals within the same dated validation record (56,202 vs 196,522), indicating a serious data reliability issue.
  • Monitoring report lists multiple corrective actions, including discrepancies in net energy generation figures cross-checked against CCEE and calculation errors in spreadsheets.
  • Leakage treatment is inconsistent across monitoring reports (previously deemed negligible vs later not addressed), weakening baseline/leakage credibility.

Credit Vintages

Issued Retired Available
2009
6,647 6,647 0
2010
33,088 33,088 0
2011
25,911 25,911 0
2012
30,291 30,291 0
2016
55,518 55,518 0
2017
45,942 33,996 11,946
2018
61,109 61,109 0
2019
52,698 52,698 0
2020
20,160 20,160 0
2021
5,202 5,202 0
Total 336,566 324,620 11,946

Cosa migliorerebbe questo punteggio

  • Publish a reconciled ER accounting package that resolves the conflicting verified ER totals (56,202 vs 196,522) and clearly ties generation data to CCEE sources and corrected spreadsheets.
  • Provide a consistent leakage assessment under ACM0002 (explicitly negligible with justification or quantified deduction) and clearly document safeguards, FPIC approach, and grievance mechanism in a stable, version-controlled set of documents.

Questi suggerimenti indicano quali prove pubbliche aggiuntive potrebbero migliorare il livello di confidenza di questa valutazione. Non garantiscono un punteggio futuro più alto.

Risk Indicators

Additionality

VVB-confirmed additionality

Permanence

Avoidance project; no reversal events reported

Leakage

Leakage treatment inconsistent/unclear

Baseline

Project-specific baseline; reassessment timing unclear

Safeguards

Safeguards/grievance inconsistently documented; no FPIC

Double-claim

CORSIA/CCP status not stated

Where to buy

Marketplaces

+ Know where to buy this?

Listing multiple projects? Send us a CSV at [email protected].

⚑ Dispute this rating
Analysis Provenance Scored 2026-04-02 General Methodology v2.0 Documentazione completa

Sei il proprietario di questo progetto?

Correzione metadati (gratuita)

Nome, paese, marketplace o link errati? Segnalacelo.

Non modifica lo score.

[email protected]

Rivalutazione con nuovi documenti

Hai documentazione aggiornata non ancora inclusa? Puoi richiedere un nuovo run della pipeline con i nuovi input.

Invia Documenti