290 records
15 · Methodology

How every number here is produced

This Atlas is a modelling exercise built on a documented parameter set. Nothing in it is metered. The value of the work lies in the parameters being explicit, the formulas being simple, and the limitations being stated before the findings.

India and Singapore are covered nationally. The USA, UK, Ireland, Germany and Brazil are each represented by ONE flagship cluster (Northern Virginia, London/Slough, Dublin, Frankfurt Rhein-Main, São Paulo State) — these rows are NOT national totals.

Structural absences: no Scope 1 emissions, no Scope 3 or embodied carbon, no measured noise, no metered energy or water, no systematic complaint register, and no sub-national grid emission factors. These are not gaps to be filled by interpretation — they are boundaries on what this dataset can support.

Core formulas

The full derivation chain

Nine expressions produce every environmental quantity in the Atlas.

Annual energy
Capacity_MW × 8,760 h × Load_Factor × PUE
MWh/yr
Annual water
Energy_MWh × WUE
m³/yr
Scarcity-weighted water
Water_m3 × Water_Stress_Index
m³/yr
Scope 2 carbon (location-based)
Energy_MWh × Grid_CO2_Factor
tCO₂e/yr
Scope 2 carbon (market-based)
Energy_MWh × (1 − Renewable_Matched) × Grid_CO2_Factor
tCO₂e/yr
Waste heat
Energy_MWh ÷ 8,760 (annual-average thermal rejection rate)
MW thermal
Noise screening
Capacity-band source level with distance attenuation to 50 m
dB(A)
Pillar score
Percentile rank of the pillar indicator across all 1,098 records
0–100
Multi-Impact Composite
Weighted mean of the six pillar scores (equal weights by default)
0–100
Per-pillar limitations

Read these before citing any figure

Each dimension fails in its own specific way.

Pillar 1
Carbon Emissions
Unit: tCO₂e/yr · intensity: tCO₂e per MW IT

Location-based Scope 2 only, using national average grid factors. Scope 1 and Scope 3 are absent entirely; sub-national grid variation is not represented.

Pillar 2
Energy Consumption
Unit: MWh/yr · intensity: MWh per MW IT

Every energy value is MODELLED (Capacity × 8,760 × Load Factor × PUE). No facility in this dataset is metered.

Pillar 3
Waste Heat Generated
Unit: MW thermal · intensity: MW thermal per MW IT

Waste heat is an energy-balance proxy (an annual average rejection RATE), never a measured local temperature rise. Cooling technology is inferred from the water ratio.

Pillar 4
Water Consumption
Unit: m³/yr · intensity: m³ per MWh

Water = Energy × WUE and covers ON-SITE cooling only; it excludes upstream water embodied in electricity generation. Water stress is an area-level band, not a coordinate-level lookup.

Pillar 5
Noise
Unit: dB(A) at 50 m · intensity: m to nearest residential land use

THE WEAKEST PILLAR IN THIS WORKBOOK. Noise is a capacity-based engineering proxy and setback is a land-use class band. Neither has been measured at any facility — use for screening only.

Pillar 6
Communities Impacted
Unit: residents within 1 km · intensity: residents within 1 km per MW IT

Zero documented complaints does not mean zero complaints occurred — it means no complaint record was located in the sources consulted.

Parameter register

Every benchmark value and its justification

98 documented parameters — PUE bands, WUE bands, grid factors, noise source levels, employment ratios and population densities.

ParameterTypeApplies toValueUnitSource / justification
Grid emission factorCountry parameterIndia0.710tCO2e/MWhCEA CO2 Baseline Database for the Indian Power Sector (weighted average operating margin ~0.71 tCO2/MWh)
Grid renewable shareCountry parameterIndia22.000%Ember / CEA generation mix ~2024 (renewables incl. large hydro as % of generation)
Benchmark PUECountry parameterIndia1.600ratioUptime Institute Global Data Center Survey - Asia-Pacific regional average; same value as the source workbook
Benchmark WUECountry parameterIndia2.150m3/MWhSource workbook India WUE (2.15 m3/MWh), derived from Indian colocation disclosures
Grid emission factorCountry parameterUSA0.386tCO2e/MWhUS EPA eGRID national annual average generation emission factor
Grid renewable shareCountry parameterUSA23.000%EIA / Ember US generation mix ~2024
Benchmark PUECountry parameterUSA1.500ratioUptime Institute Global Data Center Survey - North America regional average
Benchmark WUECountry parameterUSA0.374m3/MWhLBNL 2024 US Data Center Energy Usage Report: 17.4 bn gal direct cooling water / 176 TWh (2023)
Grid emission factorCountry parameterUK0.207tCO2e/MWhUK DESNZ/DEFRA Greenhouse Gas Conversion Factors, grid electricity generation factor
Grid renewable shareCountry parameterUK45.000%DESNZ Energy Trends / Ember GB generation mix ~2024
Benchmark PUECountry parameterUK1.500ratioUptime Institute Global Data Center Survey - Europe regional average
Benchmark WUECountry parameterUK1.000m3/MWhClimate-based WUE proxy carried from the source workbook - WEAK EVIDENCE, no primary UK national figure
Grid emission factorCountry parameterIreland0.280tCO2e/MWhSEAI Energy in Ireland - electricity CO2 intensity
Grid renewable shareCountry parameterIreland40.000%EirGrid / SEAI renewable share of electricity generation ~2024
Benchmark PUECountry parameterIreland1.400ratioCool-maritime-climate benchmark; free-cooling-dominant Dublin hyperscale fleet
Benchmark WUECountry parameterIreland0.800m3/MWhCool-climate WUE proxy (free cooling reduces evaporative demand) - MODELLED, no Irish national figure
Grid emission factorCountry parameterGermany0.380tCO2e/MWhGerman Environment Agency (UBA) specific CO2 emissions of the German electricity mix
Grid renewable shareCountry parameterGermany55.000%AGEB / Fraunhofer ISE renewable share of public net electricity generation ~2024
Benchmark PUECountry parameterGermany1.450ratioUptime Institute Europe regional average adjusted for the Frankfurt free-cooling window
Benchmark WUECountry parameterGermany0.900m3/MWhTemperate-climate WUE proxy - MODELLED, no German national data-centre figure
Grid emission factorCountry parameterBrazil0.110tCO2e/MWhMCTI / ONS Brazilian national grid emission factor (hydro-dominant system)
Grid renewable shareCountry parameterBrazil87.000%ONS / EPE Brazilian generation mix ~2024
Benchmark PUECountry parameterBrazil1.700ratioSource workbook Brazil PUE (1.7) - warm-humid climate colocation benchmark
Benchmark WUECountry parameterBrazil2.150m3/MWhSource workbook Brazil WUE (2.15 m3/MWh)
Grid emission factorCountry parameterSingapore0.400tCO2e/MWhSingapore EMA grid emission factor (gas-dominant system)
Grid renewable shareCountry parameterSingapore5.000%EMA Singapore Energy Statistics - solar share of generation
Benchmark PUECountry parameterSingapore1.400ratioIMDA Green Data Centre Standard / Singapore new-build PUE requirement (<=1.3 for new; 1.4 fleet benchmark)
Benchmark WUECountry parameterSingapore2.000m3/MWhSingapore regulatory WUE CEILING (<=2.0 m3/MWh) - a ceiling, not a measured mean; likely overstates actual use
Fleet PUEOperator disclosureGoogle1.090ratioGoogle Environmental Report - fleet-wide average annual PUE, average WUE and carbon-free energy percentage
Fleet WUEOperator disclosureGoogle0.990m3/MWhGoogle Environmental Report - fleet-wide average annual PUE, average WUE and carbon-free energy percentage
Matched renewable / CFEOperator disclosureGoogle64.000%Google Environmental Report - fleet-wide average annual PUE, average WUE and carbon-free energy percentage
Fleet PUEOperator disclosureMeta1.090ratioMeta Sustainability Report - fleet PUE/WUE and 100% renewable-energy matching claim
Fleet WUEOperator disclosureMeta0.200m3/MWhMeta Sustainability Report - fleet PUE/WUE and 100% renewable-energy matching claim
Matched renewable / CFEOperator disclosureMeta100.000%Meta Sustainability Report - fleet PUE/WUE and 100% renewable-energy matching claim
Fleet PUEOperator disclosureMicrosoft1.180ratioMicrosoft Environmental Sustainability Report - design PUE/WUE and 100% renewable purchase claim
Fleet WUEOperator disclosureMicrosoft0.300m3/MWhMicrosoft Environmental Sustainability Report - design PUE/WUE and 100% renewable purchase claim
Matched renewable / CFEOperator disclosureMicrosoft100.000%Microsoft Environmental Sustainability Report - design PUE/WUE and 100% renewable purchase claim
Fleet PUEOperator disclosureAmazon AWS1.150ratioAWS Sustainability - global WUE 0.18 L/kWh and 100% renewable-matched claim
Fleet WUEOperator disclosureAmazon AWS0.180m3/MWhAWS Sustainability - global WUE 0.18 L/kWh and 100% renewable-matched claim
Matched renewable / CFEOperator disclosureAmazon AWS100.000%AWS Sustainability - global WUE 0.18 L/kWh and 100% renewable-matched claim
Fleet PUEOperator disclosureEquinix1.420ratioEquinix Sustainability Report - global portfolio PUE and renewable-coverage percentage
Fleet WUEOperator disclosureEquinixm3/MWhEquinix Sustainability Report - global portfolio PUE and renewable-coverage percentage
Matched renewable / CFEOperator disclosureEquinix96.000%Equinix Sustainability Report - global portfolio PUE and renewable-coverage percentage
Fleet PUEOperator disclosureDigital Realty1.450ratioDigital Realty ESG Report - global portfolio PUE and renewable-energy coverage
Fleet WUEOperator disclosureDigital Realtym3/MWhDigital Realty ESG Report - global portfolio PUE and renewable-energy coverage
Matched renewable / CFEOperator disclosureDigital Realty65.000%Digital Realty ESG Report - global portfolio PUE and renewable-energy coverage
Fleet PUEOperator disclosureSTT GDC India1.500ratioSTT GDC India sustainability disclosures - India portfolio design PUE
Fleet WUEOperator disclosureSTT GDC Indiam3/MWhSTT GDC India sustainability disclosures - India portfolio design PUE
Matched renewable / CFEOperator disclosureSTT GDC India%STT GDC India sustainability disclosures - India portfolio design PUE
Fleet PUEOperator disclosureCtrlS Datacenters1.420ratioCtrlS published design PUE for its Indian Tier-IV fleet
Fleet WUEOperator disclosureCtrlS Datacentersm3/MWhCtrlS published design PUE for its Indian Tier-IV fleet
Matched renewable / CFEOperator disclosureCtrlS Datacenters%CtrlS published design PUE for its Indian Tier-IV fleet
Fleet PUEOperator disclosureYotta Data Services1.500ratioYotta NM1 published facility PUE (datacentermap facility specification)
Fleet WUEOperator disclosureYotta Data Servicesm3/MWhYotta NM1 published facility PUE (datacentermap facility specification)
Matched renewable / CFEOperator disclosureYotta Data Services%Yotta NM1 published facility PUE (datacentermap facility specification)
Fleet PUEOperator disclosureAirTrunk1.250ratioAirTrunk published design PUE for its APAC hyperscale fleet
Fleet WUEOperator disclosureAirTrunkm3/MWhAirTrunk published design PUE for its APAC hyperscale fleet
Matched renewable / CFEOperator disclosureAirTrunk%AirTrunk published design PUE for its APAC hyperscale fleet
Operational IT loadMarket capacity anchorIN-Mumbai Metropolitan Region595.000MWCushman & Wakefield India Data Centre Update H1 2025 - Mumbai metro operational IT load (~53% of national)
Operational IT loadMarket capacity anchorIN-Chennai191.000MWCushman & Wakefield India Data Centre Update H1 2025 - Chennai operational IT load
Operational IT loadMarket capacity anchorIN-Delhi NCR146.000MWCushman & Wakefield India Data Centre Update H1 2025 - Delhi-NCR operational IT load
Operational IT loadMarket capacity anchorIN-Pune112.000MWCushman & Wakefield India Data Centre Update H1 2025 - Pune operational IT load
Operational IT loadMarket capacity anchorIN-Hyderabad152.000MWResidual of the Cushman & Wakefield national total (1,280 MW, H1 2025) after the six named metros - DERIVED, not directly reported
Operational IT loadMarket capacity anchorIN-Bengaluru76.000MWCushman & Wakefield India Data Centre Update H1 2025 - Bengaluru operational IT load
Operational IT loadMarket capacity anchorIN-Kolkata110.000MWBuilt up from facility-level disclosures (NTT Kolkata 1 = 40 MW; STT Kolkata DC2 = 34 MW) plus six further operating facilities. The Cushman & Wakefield city figure of 8 MW is irreconcilable with these two disclosures alone and is therefore NOT used - see the 62_QC_Reconciliation sheet
Operational IT loadMarket capacity anchorIN-Other India25.000MWModelled residual for Ahmedabad/Gandhinagar, Kochi, Jaipur, Visakhapatnam, Coimbatore, Indore and Nashik - LOW CONFIDENCE
Operational IT loadMarket capacity anchorUS-Northern Virginia4,000.000MWNorthern Virginia (Loudoun + Prince William + Fairfax) commissioned data-centre IT load, ~4 GW class, per Dominion Energy connected-load reporting and market trackers
Operational IT loadMarket capacity anchorUK-London & Slough1,300.000MWGreater London / Slough Trading Estate operational IT load, ~1.3 GW class, per UK FLAP-D market trackers
Operational IT loadMarket capacity anchorIE-Dublin950.000MWDublin metropolitan operational data-centre IT load, ~0.95 GW class; EirGrid reports data centres at ~21% of national metered electricity demand
Operational IT loadMarket capacity anchorDE-Frankfurt Rhein-Main950.000MWFrankfurt/Rhein-Main operational IT load, ~0.95 GW class, the largest FLAP-D market
Operational IT loadMarket capacity anchorBR-Sao Paulo State600.000MWSao Paulo state operational IT load, ~0.6 GW class (Ascenty, Scala, ODATA, Equinix, Microsoft)
Operational IT loadMarket capacity anchorSG-Singapore1,400.000MWSingapore national operational IT load ~1.4 GW; consistent with the source workbook's 2024 Singapore capacity value
Relative IT loadFacility class weightHYPERSCALE30.000unitlessJudgement-based ratio used only to distribute a market total across facilities; calibrated so market sums reconcile to the published anchor.
Relative IT loadFacility class weightWHOLESALE12.000unitlessJudgement-based ratio used only to distribute a market total across facilities; calibrated so market sums reconcile to the published anchor.
Relative IT loadFacility class weightCOLO_MID6.000unitlessJudgement-based ratio used only to distribute a market total across facilities; calibrated so market sums reconcile to the published anchor.
Relative IT loadFacility class weightCOLO_SMALL1.500unitlessJudgement-based ratio used only to distribute a market total across facilities; calibrated so market sums reconcile to the published anchor.
IT-load utilisationLoad factorHYPERSCALE0.800fractionIT-load utilisation factors. Hyperscale 0.80 reflects operator-reported high average utilisation; colocation 0.60-0.65 reflects Indian and European colocation occupancy and diversity factors reported by JLL/CBRE (India vacancy ~4-8%, but contracted-vs-drawn load is lower). LBNL uses 0.50 for whole-fleet facility power; that value is retained for the smallest/enterprise class.
IT-load utilisationLoad factorWHOLESALE0.650fractionIT-load utilisation factors. Hyperscale 0.80 reflects operator-reported high average utilisation; colocation 0.60-0.65 reflects Indian and European colocation occupancy and diversity factors reported by JLL/CBRE (India vacancy ~4-8%, but contracted-vs-drawn load is lower). LBNL uses 0.50 for whole-fleet facility power; that value is retained for the smallest/enterprise class.
IT-load utilisationLoad factorCOLO_MID0.600fractionIT-load utilisation factors. Hyperscale 0.80 reflects operator-reported high average utilisation; colocation 0.60-0.65 reflects Indian and European colocation occupancy and diversity factors reported by JLL/CBRE (India vacancy ~4-8%, but contracted-vs-drawn load is lower). LBNL uses 0.50 for whole-fleet facility power; that value is retained for the smallest/enterprise class.
IT-load utilisationLoad factorCOLO_SMALL0.500fractionIT-load utilisation factors. Hyperscale 0.80 reflects operator-reported high average utilisation; colocation 0.60-0.65 reflects Indian and European colocation occupancy and diversity factors reported by JLL/CBRE (India vacancy ~4-8%, but contracted-vs-drawn load is lower). LBNL uses 0.50 for whole-fleet facility power; that value is retained for the smallest/enterprise class.
Share of ultimate capacity energised in 2026Status energisation factorOP1.000fractionOperational fully energised; under-construction assumed 35% energised during 2026; announced and planned contribute nothing to 2026 capacity.
Share of ultimate capacity energised in 2026Status energisation factorUC0.350fractionOperational fully energised; under-construction assumed 35% energised during 2026; announced and planned contribute nothing to 2026 capacity.
Share of ultimate capacity energised in 2026Status energisation factorAN0.000fractionOperational fully energised; under-construction assumed 35% energised during 2026; announced and planned contribute nothing to 2026 capacity.
Share of ultimate capacity energised in 2026Status energisation factorPL0.000fractionOperational fully energised; under-construction assumed 35% energised during 2026; announced and planned contribute nothing to 2026 capacity.
Share of ultimate capacity energised in 2026Status energisation factorUNK0.500fractionOperational fully energised; under-construction assumed 35% energised during 2026; announced and planned contribute nothing to 2026 capacity.
Nearest residential receptorResidential setback bandDENSE_URBAN60.000mLand-use class band anchored to Virginia JLARC 2024 (~1/3 of Virginia data centres within 200 ft / 61 m of residential zoning).
Nearest residential receptorResidential setback bandURBAN_INDUSTRIAL150.000mLand-use class band anchored to Virginia JLARC 2024 (~1/3 of Virginia data centres within 200 ft / 61 m of residential zoning).
Nearest residential receptorResidential setback bandSUBURBAN_ITPARK300.000mLand-use class band anchored to Virginia JLARC 2024 (~1/3 of Virginia data centres within 200 ft / 61 m of residential zoning).
Nearest residential receptorResidential setback bandPERI_URBAN800.000mLand-use class band anchored to Virginia JLARC 2024 (~1/3 of Virginia data centres within 200 ft / 61 m of residential zoning).
Nearest residential receptorResidential setback bandRURAL2,000.000mLand-use class band anchored to Virginia JLARC 2024 (~1/3 of Virginia data centres within 200 ft / 61 m of residential zoning).
Community sensitivity weightLand-use sensitivityDENSE_URBAN1.0000-1Judgement weight used in Pillar 5.
Community sensitivity weightLand-use sensitivityURBAN_INDUSTRIAL0.6000-1Judgement weight used in Pillar 5.
Community sensitivity weightLand-use sensitivitySUBURBAN_ITPARK0.4500-1Judgement weight used in Pillar 5.
Community sensitivity weightLand-use sensitivityPERI_URBAN0.3000-1Judgement weight used in Pillar 5.
Community sensitivity weightLand-use sensitivityRURAL0.1500-1Judgement weight used in Pillar 5.
Boundary noise at ~50 mNoise modelAll50 + 10*log10(MW), clipped 45-85dB(A)Engineering proxy anchored to the 60 dB(A) Prince William County (Virginia) ordinance threshold that residents report data-centre noise exceeding.
Population within 1 km / 5 kmPopulation modelAlldensity*pi*1 ; density*pi*25*0.60personsArea density band times circle area, with a 0.60 radial decay factor at 5 km. NOT a raster zonal statistic.
Permanent rolesEmployment modelAll5 per MWFTEIndustry rule of thumb; Confidence 1.
Source workbook

Methodology notes as documented by the authors

Reproduced verbatim from the workbook's methodology sheet.

METHODOLOGY, FORMULAS, ASSUMPTIONS AND LIMITS

1. DATA ARCHITECTURE (layers, in build order)

L0 Raw preserved - the supplied workbook, byte-for-byte, sheets 70-73. Never modified, never overwritten.

L1 Entity resolution - individual facilities identified from operator listings and market directories,

deduplicated by (operator, facility name, area). Multi-building campuses are carried as a

CAMPUS parent row plus child FACILITY rows; the parent is excluded from every sum so that

capacity is never double counted.

L2 Geospatial - each facility mapped to one of 283 reference AREAS (industrial estate / business park /

suburb) carrying coordinates, land-use class, resident density band, basin water-stress

score and mean annual temperature. Sheet 52.

L3 Capacity - reported where published; otherwise allocated from a documented market total. Section 3.

L4 Indicators - the six pillars' underlying quantities, derived from L3 and the benchmark parameters

in sheet 51. Sheets 11-16.

L5 Normalisation - indicators rescaled 0-1 across the whole facility population. Section 4.

L6 Pillar and composite scores, risk classes, sensitivity. Sheets 20-21.

L7 Clusters and aggregates - every aggregate is a SUM or MEDIAN of L3/L4 facility values. Sheets 30-34.

L8 Time series - the 2026 fleet back-cast to 2020. Section 6. Sheets 40-41.

L9 Provenance and quality - sheets 50, 60, 61, 62.

2. EVIDENCE TAXONOMY (inherited from the supplied workbook, extended)

Reported - taken directly from an operator disclosure, regulator, government dataset or facility specification.

Derived - arithmetic on other values in this workbook (e.g. waste heat = annual energy / 8,760).

Modelled - produced by an explicit documented formula anchored to at least one real, cited data point.

Allocated - a documented market or portfolio total distributed across facilities by a stated weighting rule.

Proxy - a real observation from a different scale (area, city, country, operator fleet) used because no

site-specific figure exists. The scale mismatch is the limitation.

Not Available - no value could be established. Left blank, and flagged in 61_Missingness_Matrix.

CONFIDENCE SCALE (as specified in the brief)

5 Directly reported or measured by the operator or a government body FOR THAT FACILITY.

4 Highly credible secondary source, or an operator fleet figure applied to that operator's own site.

3 Reliable estimate from a documented methodology.

2 Weak or incomplete evidence - typically an area-level or class-level band.

1 Inference or highly uncertain estimate.

0 No evidence.

Record_Confidence is the mean of the field confidences for capacity, PUE, WUE, coordinates, status, year and the

two context fields. It is a summary, not a substitute for the per-field confidence columns.

3. CAPACITY METHOD (the single most consequential assumption in this workbook)

Facilities with a published capacity keep it (Evidence_Type = Reported, Confidence 4).

For every other facility in a market:

Capacity_Ultimate_MW = (Market_Anchor_MW - reported capacity in that market)

x Class_Weight(facility) / SUM over the market of [Class_Weight x Energisation_Factor]

Capacity_2026_MW = Capacity_Ultimate_MW x Energisation_Factor(status)

Class weights: Hyperscale 30, Wholesale/purpose-built colocation 12, Mid-tier colocation 6, Small/edge/enterprise 1.5.

Energisation factors: Operational 1.00, Under construction 0.35, Announced 0.00, Planned 0.00.

Market anchors and their sources are in 51_Benchmarks_Reference. This construction guarantees that the facility

records sum back to the published market total, which is exactly what makes the aggregates auditable - and it

also means an individual facility's MW figure is an ALLOCATION and should not be quoted as that site's capacity.

4. INDICATOR FORMULAS

Energy_MWh = Capacity_2026_MW x 8,760 h x Load_Factor(class) x PUE

Energy_Intensity = 8,760 x Load_Factor x PUE (MWh per MW of IT capacity per year)

Water_m3 = Energy_MWh x WUE (1 L/kWh == 1 m3/MWh)

WS_Weighted_Water = Water_m3 x (basin water-stress score / 5)

CO2_Location_t = Energy_MWh x grid emission factor

CO2_Market_t = Energy_MWh x grid factor x (1 - operator matched-renewable %) [only where the operator publishes one]

Waste_Heat_MW_th = Energy_MWh / 8,760 (energy-balance proxy: essentially all electricity leaves as heat)

Heat_Island_Proxy = Waste_Heat_MW_th x resident density / 1,000

Noise_dB(A) @ ~50 m = 50 + 10 x log10(Capacity_MW), clipped to [45, 85]

Engineering proxy only. Anchored so that a ~30 MW site returns ~65 dB(A), consistent with the

60 dB(A) county ordinance threshold that Prince William County (Virginia) residents report

data-centre noise routinely exceeding.

Residential_Distance_m = land-use class band (Dense urban 60, Urban industrial 150, Suburban IT park 300,

Peri-urban 800, Rural 2,000). The dense-urban band is anchored to the Virginia JLARC 2024

finding that ~1/3 of Virginia data centres sit within 200 ft (61 m) of residential zoning.

Population_1km = resident density x pi x 1 km^2

Population_5km = resident density x pi x 25 km^2 x 0.60 (0.60 = radial density-decay factor)

Jobs_Estimate = Capacity_MW x 5 permanent roles per MW (industry rule of thumb, Confidence 1)

Infrastructure_Pressure = facility capacity as a percentage of its cluster's total capacity

5. SIX-PILLAR INDEX

Direction: for every indicator, HIGHER = GREATER environmental or community impact.

Normalisation: volume indicators (energy, water, CO2, waste heat, population, capacity) are min-max scaled on

log10(1+x) because they span five orders of magnitude; ratio and score indicators (PUE, WUE, water stress,

temperature, noise, land-use sensitivity, regulatory flags) are min-max scaled on the raw value. Scaling is

computed across the whole facility population so scores are comparable between countries.

Pillar score = weighted sum of its normalised sub-indicators x 100. Sub-indicator weights are printed in full

on 20_SixPillar_Scores. Composite = weighted mean of the six pillars; the default scheme is equal weights (1/6).

Risk class = quartiles of the composite across all 1098 facilities: Low <54.1, Medium <59.6, High <65.7, Very High above.

KNOWN PROPERTY OF THIS INDEX, STATED PLAINLY: four of the six pillars are dominated by LOCATION CONTEXT (water

stress, climate, density, land use, regulation) and only two by SCALE. A small facility in a dense, water-stressed

city therefore outranks a very large facility in a cool, low-stress rural location. That is a deliberate design

choice for a community-impact index, but it means the composite must NOT be read as 'biggest environmental

footprint'. For footprint, use the absolute columns in sheets 11-16 and the capacity-weighted aggregates.

6. TIME SERIES BACK-CAST (2020-2026)

Operational facilities are ordered by a vintage proxy (hyperscale greenfield later; lower facility numbering

earlier) and assigned a first-power year such that the cumulative fleet capacity reproduces the national capacity

growth curve that the SUPPLIED workbook already sources. Only the SHAPE of that curve is used, never its level,

because this workbook covers one flagship cluster per non-Indian country rather than the whole nation.

Under-construction, announced and planned facilities are given indicative first-power years of 2027, 2028 and 2029.

Every back-cast year carries Confidence 1. Where a real commissioning year was found it overrides the model.

7. SOURCE HIERARCHY APPLIED (highest first)

1 Government datasets and regulatory filings 2 Operator sustainability reports and official disclosures

3 Planning applications and environmental impact assessments 4 Utility and grid-operator information

5 Official company announcements 6 Peer-reviewed literature 7 Established industry datasets and market

trackers 8 Credible institutional research 9 News reporting (labelled wherever used).

Where sources conflict, the higher tier wins and the conflict is recorded in 62_QC_Reconciliation rather than

silently resolved. The Kolkata capacity conflict is the worked example.

8. WHAT THIS WORKBOOK STILL CANNOT TELL YOU

* Any individual facility's actual metered electricity or water consumption.

* Any individual facility's measured noise emission or its measured setback to the nearest dwelling.

* Actual population counts within 1 km (this needs a GHSL/WorldPop raster zonal statistic against real coordinates).

* Whether a community has in fact objected to a specific Indian, Brazilian, Singaporean or German facility.

* On-site generation, storage, heat reuse contracts or water-recycling rates at any site.

The single highest-value next step is to replace the AREA centroids with rooftop coordinates and run a real

GHSL population zonal statistic and a real WRI Aqueduct basin lookup; that alone would move Pillars 2, 5 and 6

from Confidence 1-2 to Confidence 3-4.

Use and misuse

How to cite this Atlas responsibly

Do

State that figures are modelled, and give the parameter basis (PUE, WUE, grid factor) alongside any total.

Do

Use intensity metrics for comparison and absolute metrics for footprint — they answer different questions.

Do

Name the weighting scheme whenever you quote a composite score or rank.

Don't

Treat the USA, UK, Ireland, Germany or Brazil rows as national totals — each is one flagship cluster.

Don't

Use coordinates or setback distances for property-level, boundary or receptor-level conclusions.

Don't

Read zero documented complaints as evidence that no complaints exist.