On Premise
Interpolates between idle and maximum power according to utilisation, then adds storage power, annual operating hours, PUE, and the electricity grid emission factor.
The application implements the calculation logic of the DPC Carbon Footprint Calculation Tool v1.0 workbook and recalculates project data on the server before saving it.
Official reference: DPC — Calculating your carbon footprint ↗
Interpolates between idle and maximum power according to utilisation, then adds storage power, annual operating hours, PUE, and the electricity grid emission factor.
Uses annual emissions reported or estimated by the provider. The application does not invent instance-hour factors that are not available in the workbook.
Daily data volume × network energy intensity × grid factor, using the 365/12 factor exactly as implemented in the DPC v1.0 workbook.
Website use estimates annual page and download data transfer. Travel accepts tCO₂e or kgCO₂e results from external calculators and records the source.
The web calculator starts from the same reference values used by the workbook Datasheet. Users may replace them when a better documented value is available for their context.
0.0065 kWh/GB — DIMPACT global-average energy intensity.
0.1 kWh/GB — DIMPACT global-average energy intensity.
0.05325 kWh/GB — simple average of the fixed-line and mobile values, matching Website Use cell B12.
0.45 kgCO₂e/kWh — the workbook Datasheet global-average electricity emissions factor.
The Grid Factors reference table is copied from the v1.0 workbook. The separate Cloud Factors sheet in the workbook is reference data only and is not linked into the workbook calculation formulas; cloud emissions remain values reported or estimated for the service and documented by the user.
Embodied carbon of devices is not included. Results are estimates, not a verified GHG inventory or assurance audit. Result quality depends on the completeness and quality of activity data and emission factors used.
The methodology version, inputs, results, sources, confidence levels where applicable, assumptions, and update time are stored with the project.