Efficiency Metrics: PUE, WUE, ERF, REF & the Post-PUE Metric Stack

Power Usage Effectiveness is the most quoted number in the industry and the most quietly broken. It was a brilliant intervention in 2007: a single ratio — total facility energy divided by IT energy — that let an operator see, for the first time, how many watts were burned on cooling, conversion, and lighting for every watt that reached a server. It drove a fifteen-year efficiency campaign that took hyperscale halls from a PUE near 2.0 to design points around 1.1. But PUE was designed for an air-cooled, conversion-heavy, fixed-IT world, and the AI data center is none of those things. The denominator it trusts, "IT energy," is no longer a stable line. Liquid cooling moves fans and pumps across it. Densification makes it swing with utilization. And the questions that now gate a project — how much water, how much carbon, how much useful work — live entirely outside its formula.

This chapter is the canonical home for the efficiency metric stack referenced from Chapter 0.3 and Chapter 5.1. Each metric is a choice of what to make visible, and every choice hides something. We define PUE precisely and show exactly where it breaks for AI; separate WUE-site from WUE-source and the embedded-water trap between them; walk ERF/ERE, REF, and CUE as the carbon-and-reuse layer; introduce the work-based metrics (TUE/ITUE, DCeP, tokens-per-joule) that put real output in the denominator; and close on how to build a measurement plan that survives an audit instead of producing a vanity number for a press release.

Under ISO/IEC 30134-2:2026, PUE is total facility energy divided by IT equipment energy, measured over a full year (an instantaneous or design-point PUE is a different, weaker claim — always ask which one a vendor is quoting). A PUE of 1.20 means that for every 1.0 kWh delivered to IT, another 0.20 kWh went to everything else: cooling plant, UPS and transformer losses, switchgear, lighting. The two 2026 Uptime survey values below use different weighting: the respondent mean counts each facility equally; the capacity-weighted result gives larger facilities proportional weight. Uptime’s August 6, 2026 analysis shows why efficient large facilities pull the weighted result down while older facilities still dilute the per-facility mean. Use the matching population and weighting for a benchmark, then test the project’s own climate and load curve; neither survey result predicts this facility’s PUE. The 2025 survey value below is a historical benchmark.

Three structural problems make PUE actively misleading for AI facilities, and each is a fork an operator must decide how to handle.

1. The liquid-cooling boundary problem. PUE's denominator is "power that crosses into the IT." In an air-cooled hall, server fans sit inside that boundary and CRAH fans sit outside it — clean. Direct-to-chip liquid blurs the line: cold plates, in-rack manifolds, and the pumps that move coolant can be metered as IT or as facility depending on where the CDU sits and how the rack is wired. Move a fan's power from the facility side to the IT side and PUE improves while nothing physical got more efficient — you simply re-labeled a loss. Worse, a genuinely efficient warm-water loop with a big chiller plant can post a higher PUE than a cheaper, hotter air hall, because the liquid plant's parasitic load is honestly accounted while the air hall's server-fan burn hides inside IT. PUE was never meant to compare cooling architectures, and using it to do so is the most common metric error in 2026 procurement.

2. The utilization problem. PUE says nothing about whether the IT is doing useful work. A cluster idling at 15% may still report an acceptable PUE while producing little useful work, but low load does not mechanically improve the ratio. With PUE = 1 + overhead/IT, fixed or sub-linearly falling plant losses usually make PUE worse as IT load falls, and part-load UPS or chiller efficiency may worsen it further. The defect is that PUE never asks whether the IT energy produced useful work; publish the load curve and a work-based denominator alongside it. This is why goodput-aware operators (see Chapter 12.2) refuse to manage on PUE alone.

3. The everything-else-is-invisible problem. PUE is an energy-overhead ratio. It is silent on water (a 1.10-PUE evaporative hall can drink millions of liters a day), silent on carbon (1.10 PUE on coal is dirtier than 1.4 PUE on hydro), and silent on whether heat is wasted or reused. The metrics below exist precisely to make those silences audible.

Water Usage Effectiveness is liters of water per kWh of IT energy — and which liters is the whole argument. Keep three quantities separate: input (everything crossing the boundary), discharge (blowdown returned to a sewer or watercourse), and consumption (input minus discharge and net storage increase, with evaporation dominant in a tower balance). ISO/IEC 30134-9 frames WUE around water used on site; EU reporting under Delegated Regulation (EU) 2024/1364 divides total water input for all data-centre functions — measured to EN 50600-4-9 WUE Category 2 — by IT energy. Evaporate 100 m³ at six cycles of concentration and you draw ~120 m³ of makeup and discharge ~20 m³: reporting one number for all three quantities hides the difference the regulator and the basin each care about. It is the metric that has moved fastest from obscure to board-level, because water is now a siting gate (Chapter 3.7) and a social-license risk, not just an operating cost. The fork that matters is WUE-site versus WUE-source, and operators routinely report the flattering one.

WUE-site counts only the water crossing the property boundary — evaporative tower make-up, adiabatic pre-cooling, humidification — and a site that meters cooling make-up alone will under-report against the EU input boundary, which also captures water used for power, security, and IT functions. Industry averages run ~1.8–1.9 L/kWh for evaporative designs; best-in-class is 0.3–0.7 L/kWh; designs with dry, non-evaporative heat rejection approach zero. Microsoft’s FY2025 cooling-and-humidification WUE is ~0.27 L/kWh for fully owned/controlled sites operating the full fiscal year. Its December 2024 non-evaporative design announcement separately estimates more than 125 million liters of avoided cooling-water consumption per facility; the announced pilots target 2026. WUE-site is the number that lets an arid, power-rich site become viable by designing water out — and it is the number that lets a thirsty evaporative hall look responsible if you stop counting at the fence.

WUE-source adds the water embedded in the electricity the facility consumes — the water evaporated at the power plant to make the megawatts. This is where the trap springs. The US-average energy water-intensity factor (EWIF) is roughly 5.1 L/kWh and ranges from near zero (wind, solar, gas combined-cycle on dry cooling) to roughly 1-3 L/kWh consumed at evaporative-cooled thermoelectric plants, and to tens of L/kWh where reservoir evaporation is allocated to hydro generation — which is what carries the national mean above the thermoelectric range (once-through plants withdraw tens of L/kWh but consume ~1 L/kWh or less). The 2022 modeled US EWIF below is historical context, not a current site factor: multiplying it by an unrelated fleet PUE does not establish a typical campus footprint. Multiply each interval’s purchased electricity by a region- and generation-specific consumption factor, sum those liters, and divide by the same IT-energy total used for the direct-water record. A hall using dry, non-evaporative heat rejection can still carry a large WUE-source if it draws coal- or nuclear-heavy thermoelectric power. A site that goes water-free on cooling but sits on a thirsty thermal grid has not eliminated its water footprint — it has relocated it upstream and out of its own report. Disclose both.

Each metric covers another's silence. PUE is silent on water; WUE fills that gap but is silent on carbon; CUE fills that but is silent on whether the energy did anything; DCeP fills that but is operator-defined and not comparable. No single metric is sufficient, and any single metric reported alone is an invitation to game the boundary. The defense is to report a stack — PUE + WUE(site and source) + ERF + REF + CUE + a work-based denominator — so that improving one at the expense of another shows up immediately. An operator who lowers PUE by raising water use, or lowers WUE-site by ignoring WUE-source, is caught the moment both lines sit on the same page.

ERF (Energy Reuse Factor) is the share of a facility's energy that is beneficially reused outside its boundary — almost always waste heat exported to a district-heating loop or industrial offtaker (engineered in Chapter 5.9, monetized and regulated in Chapter 15.5). Its sibling ERE (Energy Reuse Effectiveness) folds reuse into the PUE frame: ERE = (Total − Reused) / IT, equivalently ERE = (1 − ERF) × PUE. ERE can legitimately drop below 1.0 because its numerator credits exported useful heat; it is a reuse-adjusted ratio, not a thermodynamic efficiency. The consequence to watch: ERF is the metric most prone to intent inflation. A signed MOU with a municipality is not delivered heat; ISO/IEC 30134-6 and EN 50600-4-6 require measured offtake at the boundary, not a press release. In Germany, operative EnEfG § 11(2) (read with the data-centre scope in § 3(24)) requires new in-scope data centres entering operation from 1 July 2026, 2027, and 2028 to achieve planned energy-reuse factors of at least 10%, 15%, and 20%, respectively. The requirement dates from the EnEfG of 13 November 2023 (BGBl. I No. 309); verify the project threshold and commissioning date against the current statutory text.

REF (Renewable Energy Factor) is the renewable share of consumption (ISO/IEC 30134-3). The decision buried inside it is the accounting boundary: an unbundled-REC annual-matching REF of 100% can coexist with a facility that runs on a fossil grid every night, while a 24/7 carbon-free-energy (CFE) score exposes same-hour supply gaps; eligible annual attributes, hourly matching and causal avoided emissions are separate tests. The gap between annual matching and 24/7 CFE is the entire subject of Chapter 15.3; here the point is only that REF without a temporal qualifier is a number that hides its own assumptions.

CUE (Carbon Usage Effectiveness) is total operational CO2e per unit of IT energy (ISO/IEC 30134-8) — the shortcut CUE = CEF × PUE, where CEF is the carbon emission factor in kgCO2e/kWh, holds only when every kWh inside the boundary is purchased grid electricity. A campus running behind-the-meter gas, fuel cells, or its own generation has to compute operational emissions source by source and divide by IT energy — a zero-carbon grid factor does not make a gas-fired hall's CUE zero. It is the metric that finally makes a low-PUE-on-dirty-power facility look as bad as it is. The fork is location-based versus market-based carbon: location-based reflects the physical grid you actually burned; market-based credits contracts and instruments. Both are legitimate under the GHG Protocol, but they answer different questions, and an operator reporting only the flattering one is choosing what to hide. CUE is also silent on embodied carbon — the concrete, steel, and silicon — which can dominate the lifecycle on low-carbon power and short refresh cycles and is treated separately in Chapter 15.6.

Every metric above is an infrastructure-efficiency ratio: it asks how cleanly you delivered energy to IT, never whether the IT produced anything. For AI, where a cluster's value is tokens generated or models trained, this is the deepest blind spot.

TUE and ITUE (proposed by Patterson at Intel with the LBNL Energy-Efficient HPC Working Group) push the boundary inward. ITUE is PUE's logic applied inside the server: total IT energy divided by the energy that actually reaches compute silicon (CPU, GPU, memory, storage), separating out server fans, PSU conversion, and VRM losses. TUE = ITUE × PUE then compares an air-cooled and a liquid-cooled facility without letting the boundary shift hide a loss, which is why you ask for it whenever cooling modality is in question — and it measures the overhead around the compute, not whether that compute did anything useful. Its cost is instrumentation: you need per-server or per-component telemetry, so the telemetry cost must earn its keep by exposing losses that the PUE boundary hides.

DCeP (Data Center Energy Productivity) is the boldest move: useful work divided by total facility energy. The Green Grid deliberately left "useful work" operator-defined — searches served, transactions cleared, or for AI, tokens generated per MWh and training-FLOP-hours per MWh. DCeP exposes under-utilization when accepted work is defined consistently: a half-idle cluster consumes energy while producing little, but counting redundant tokens as useful work can still flatter its score. Its weakness is that operator-defined work is not comparable across operators, so DCeP is an internal optimization metric, not a benchmark. For 2026 AI operators the practical instantiation is joules-per-token — energy in the denominator's place, or equivalently tokens-per-joule with output in the numerator — alongside $-per-million-tokens-at-fixed-carbon, fusing model efficiency, hardware efficiency, and facility efficiency into one number the business actually cares about. Mind the dimensions: tokens-per-watt is not tokens-per-joule unless a time basis is supplied, and tokens-per-second-per-watt is. This is the metric that aligns the efficiency team with the goodput team — both are now optimizing useful output per unit of scarce power, which in a power-bound era is the only ratio that matters.

The recast Energy Efficiency Directive (EU) 2023/1791, Article 12, and operative Delegated Regulation (EU) 2024/1364, Articles 3 and 5, establish annual reporting to the European database for in-scope data centres, including the defined PUE, WUE, ERF, and REF inputs. Operators submit individual-facility information; the relevant Member State and the Commission can access it and must keep individual database records confidential. The database's authorized public output is aggregated at Member-State and Union level. Article 12(1) separately requires Annex VII information to be made public subject to trade-secret and confidentiality protections, and national law may add operator-publication duties.

Germany's EnEfG adds national ERF and publication/reporting obligations. The standards backbone is the ISO/IEC 30134 KPI series and EN 50600 / ISO/IEC 22237. Treat submission, regulator access, operator-publication duties, and aggregate EU publication as four distinct boundaries; do not describe every facility record as public. The wider disclosure stack is in Chapter 15.7.

Trace. IT energy = 6,000 h × 5.0 MW + 2,760 h × 10 MW = 57,600 MWh. Mode A facility energy = 30,000 MWh × 1.20 + 27,600 MWh × 1.10 = 66,360 MWh; its annual PUE is 66,360/57,600 ≈ 1.15. Mode B uses 30,000 × 1.10 + 27,600 × 1.18 = 65,568 MWh, giving 1.14. Select B on energy: about 800 MWh/year less for the same service. The unweighted bin means — 1.15 for A, 1.14 for B — happen to rank the same way here but cannot size the saving; energy, not the number of bins or their hours alone, weights PUE.

Flip. A spends 0.10 more per cool-bin IT MWh but saves 0.08 per warm-bin IT MWh. With warm-bin IT-energy share x, A minus B = 0.10(1 − x) − 0.08x; equality is x = 0.10/0.18 ≈ 56%. The stated share is 27,600/57,600 ≈ 48%, so B wins; above 56%, A wins. Any quality or thermal-failure-state test that B fails also rejects B regardless of its energy result. Annual metering follows ISO/IEC 30134-2; Chapter 5.8 owns the plant/weather curves, and Chapter 15.2 turns the measured saving into an investment decision.

The metric you optimize is a statement about what you are willing to make invisible. Optimize PUE alone and you will be rewarded for moving losses inside the IT boundary while poor useful-work productivity stays invisible; low load commonly worsens the ratio, which still ignores every liter of water and gram of carbon. The 2026-current practice is to commission against a stack: PUE for energy overhead, TUE when cooling modality is in question, WUE-site and WUE-source together, ERF/ERE for reuse, REF and CUE for carbon (with a temporal and location-vs-market qualifier on each), and a work-based denominator — tokens-per-MWh or DCeP — so the whole apparatus is accountable to output. Each metric covers another's silence; reported together on consistent boundaries and periods, a gain bought at another metric's expense shows up on the same page. In a power-bound era, choose the stack that exposes useful work, energy and water on their own denominators; a lower overhead ratio that costs accepted tokens or exhausts the basin’s water allowance is no efficiency win.