HIPsHanzo Proposals
Back to HIPs
HIP-251DraftMeta

AI Compute Carbon Footprint

Methodology for measuring and reporting carbon emissions from AI training and inference.

Hanzo AI Team (@hanzoai)
Created: 2025-12-17
sustainabilitycarboncomputeemissions
Requires: HIP-200, HIP-250

HIP-251: AI Compute Carbon Footprint

Abstract

This HIP establishes the methodology for measuring, calculating, and reporting the carbon footprint of Hanzo AI's training and inference operations. It aligns with the GHG Protocol and provides AI-specific guidance for accurate carbon accounting.

Scope

Operational Boundary

ActivityScopeIncluded
Model trainingScope 2/3✅ Yes
Model inferenceScope 2/3✅ Yes
Data storageScope 2/3✅ Yes
Development computeScope 2/3✅ Yes
Employee devicesScope 3✅ Yes
Cloud servicesScope 3✅ Yes

Emissions Categorization

GHG ScopeAI-Relevant Sources
Scope 1On-site generation (if any)
Scope 2Purchased electricity for owned compute
Scope 3, Cat 1Cloud compute purchases
Scope 3, Cat 3Fuel-related activities
Scope 3, Cat 11Customer inference (if applicable)

Training Emissions

Calculation Methodology

Energy Consumption

Formula:

E_training = Σ(GPU_hours × TDP × PUE) / 1000

Where:

  • GPU_hours = GPU hours used
  • TDP = Thermal Design Power (kW)
  • PUE = Power Usage Effectiveness

Carbon Emissions

Formula:

CO2e_training = E_training × EF_grid × (1 - R%)

Where:

  • E_training = Energy consumption (kWh)
  • EF_grid = Grid emission factor (kgCO2e/kWh)
  • R% = Renewable energy percentage

Reference Values

GPU Power Consumption

GPUTDP (W)Typical UtilizationEffective (W)
H100 SXM70080%560
H100 PCIe35080%280
A100 SXM40080%320
A100 PCIe30080%240

Data Center PUE

Provider/RegionPUESource
Hyperscaler average1.1-1.2Provider reports
Colocation average1.3-1.5Industry benchmarks
On-premise average1.5-2.0Industry benchmarks

Training Tracking

Required Metrics

For each training run:

MetricCollection Method
GPU typeCluster configuration
GPU hoursJob scheduler logs
Data center locationCluster metadata
Time periodJob timestamps

Aggregation

PeriodAggregation
Per runIndividual training job
WeeklyDevelopment activity
MonthlyReporting period
AnnuallyAnnual report

Inference Emissions

Calculation Methodology

Per-Request Emissions

Formula:

CO2e_request = E_request × EF_region / 1000

Where:

E_request = (GPU_power × latency_seconds) + memory_energy + network_energy

Estimation Approach

For large-scale inference:

CO2e_inference = Total_GPU_hours × GPU_power × PUE × EF_avg / 1000

Efficiency Metrics

MetricDefinitionTarget
CO2e/1K tokensEmissions per 1,000 tokensTrack and reduce
CO2e/requestEmissions per API requestTrack and reduce
CO2e/MAUEmissions per monthly active userTrack and reduce

Geographic Distribution

Track inference by region:

Region% of RequestsGrid FactorWeighted Factor
US-WestX%0.35Calculated
US-EastY%0.42Calculated
EUZ%0.28Calculated
AsiaW%0.50Calculated

Data & Emission Factors

Grid Emission Factors

SourceCoverageUpdate Frequency
EPA eGRIDUS regionsAnnual
EEAEU countriesAnnual
IEAGlobalAnnual
Provider-specificCloud providersAs published

Cloud Provider Data

ProviderData AvailableSource
AWSRegion carbon intensityAWS Customer Carbon Footprint Tool
GCPCarbon-free energy %Google Cloud Carbon Footprint
AzureEmissions reportingMicrosoft Sustainability Calculator

Data Quality

LevelDefinitionUse
PrimaryMeasured dataPreferred
SecondaryProvider-reportedAcceptable
TertiaryIndustry averageGap-filling

Reporting Standards

Internal Reporting

Monthly Dashboard

MetricDisplay
Total compute emissionsCO2e (tonnes)
Training vs inference split% breakdown
YoY change% change
Efficiency trendCO2e/request over time

Quarterly Report

SectionContents
SummaryTotal emissions, trends
TrainingMajor training runs, emissions
InferenceVolume, efficiency
InitiativesReduction progress

External Reporting

Annual Disclosure

ReportContents
ESG ReportSummary metrics, targets
CDP ResponseDetailed methodology
Model CardsPer-model training emissions

Model Card Emissions

For each model release:

training_emissions:
  total_co2e_tonnes: X
  gpu_hours: Y
  energy_kwh: Z
  data_centers: [list]
  renewable_percentage: W%
  methodology: "HIP-251"

Reduction Strategies

Training Efficiency

StrategyImpactImplementation
Efficient architectures10-50% reductionArchitecture research
Mixed precision30-50% speedupTraining configuration
Gradient checkpointingMemory vs computeBased on model size
Curriculum learning10-30% reductionTraining methodology

Inference Efficiency

StrategyImpactImplementation
Model quantization2-4x efficiencyINT8/INT4 deployment
Speculative decoding2-3x speedupInference optimization
BatchingImproved utilizationRequest aggregation
CachingVariableResponse caching

Infrastructure

StrategyImpactImplementation
Green regions30-90% reductionRegion selection
Renewable PPAsUp to 100% reductionEnergy procurement
Efficient hardware20-50% per generationHardware refresh
Cooling optimizationPUE improvementData center ops

Targets

Absolute Targets

YearTargetBaseline
2025Establish baselineMeasure all emissions
2027-30% vs baselineReduction
2030Net zeroReduction + offsets

Intensity Targets

YearCO2e/1K tokensCO2e/request
2025BaselineBaseline
2027-50%-50%
2030-80%-80%

Renewable Energy

YearRenewable %
202550%
202780%
2030100%

Verification

Internal Verification

ActivityFrequency
Data validationMonthly
Calculation reviewQuarterly
Methodology auditAnnual

External Verification

ActivityFrequencyStandard
Third-party auditAnnualISO 14064-3
CDP verificationAnnualCDP methodology

Related HIPs

  • HIP-200: Responsible AI Principles
  • HIP-250: Sustainability Standards Alignment
  • HIP-260: Efficient Model Practices
  • HIP-270: AI Supply Chain Responsibility
  • HIP-290: Evidence Locker Index

Changelog

VersionDateChanges
1.02025-12-17Initial draft

Copyright

Copyright and related rights waived via CC0.