Executive summary
This guide turns PUE and WUE into operational routines. The goal is not just to get a number, but to be able to explain where it was measured, over which interval, with which instruments, which loads and flows fell inside the boundary, and what the uncertainty was.
| Indicator | What it answers |
|---|---|
| PUE | How much of the energy entering the data center reaches IT, and how much sustains cooling, electrical distribution, lighting, security and other services. |
| WUE | How many liters of water are consumed for each kWh delivered to IT, within the declared boundary and period. |
Five decisions make both indicators useful:
- Define the boundary: design the physical and accounting boundary before installing meters. In a mixed-use building, submetering shared utilities is mandatory to avoid fragile allocations.
- Use energy, not snapshots: instantaneous kW helps operate the site, but a comparable PUE must use accumulated kWh over the same interval. The annual report reduces climate and load bias.
- Measure IT as close as possible: UPS output is a start. PDU output or equipment input reduces the inclusion of losses and non-IT loads in the denominator.
- Close the water balance: a single general meter does not explain losses. Separate tower makeup, blowdown, humidification, adiabatic use, process water and alternative sources.
- Optimize jointly: lowering PUE with more evaporation can worsen WUE. The right decision weighs climate, water-stress risk, carbon, cost and availability.
Expected outcome: A 15-minute operational dashboard, a monthly consolidation and an annual report, all calculated from the same raw series and the same boundary map.
Editorial rule: numerical examples are didactic and identified as such. Public market figures appear with a source and period. The current PUE edition is ISO/IEC 30134-2:2026; WUE is covered by ISO/IEC 30134-9:2022, currently flagged by ISO as a standard under review. Units used: power in kW, energy in kWh, volume in L or m³, flow in m³/h, temperature in °C and WUE in L/kWh of IT energy. In every example, 1 m³ = 1,000 L.
What PUE and WUE measure — and what they do not measure
| Indicator | Measures | Does not measure |
|---|---|---|
| PUE | Efficiency of the infrastructure that delivers power and removes heat. | Server productivity, GPU/CPU utilization, carbon intensity of the electricity, availability or software efficiency. |
| WUE | Water-consumption intensity associated with operation within the declared boundary. | On its own, local water stress, source quality, water embedded in the energy, or ecosystem impact. |
Example: two sites with a PUE of 1.25 can have very different impacts. One might use dry coolers and almost no water, but consume more electricity on hot days. The other might use evaporative cooling, reduce cooling energy and consume more water. Without WUE, carbon and climate context, the diagnosis stays incomplete.
PUE can also improve without the facility actually becoming more efficient: if IT load rises while the fixed support energy stays roughly the same, the ratio falls. So report absolute energy, average IT load, availability and climate conditions alongside the indicator.
Principle: Compare a site against its own baseline. Cross-site comparisons require normalizing for climate, redundancy, occupancy, age, cooling architecture and measurement category.
Essential formulas
| Indicator | Formula | Note |
|---|---|---|
| PUE | Total data center energy / IT energy | 1.00 is the theoretical limit; lower values are better. |
| Overhead | Total energy − IT energy | Cooling energy, electrical losses and other support loads. |
| DCiE | 1 / PUE | Legacy reciprocal, usually expressed as a %. |
| WUE | Water consumed [L] / IT energy [kWh] | Result in L/kWh for the same period. |
| Thermal load | Q = ρ × cp × flow × ΔT | Water-loop diagnostic; does not replace PUE/WUE. |
| Approximate CoC | Circulating-water conductivity / makeup-water conductivity | Indicates cycles of concentration and guides blowdown. |
Mandatory condition: The numerator and denominator must represent exactly the same interval. Never divide monthly facility kWh by instantaneous IT kW.
The boundary comes before the meter
For a dedicated data center, the accounting and physical boundary needs to include every source that crosses it and the full energy path to IT and to cooling.
| Path | Typical points |
|---|---|
| Input and distribution | Grid (total kWh) → MV/LV service entrance → UPS (input/output) → PDU/rPDU (IT energy) |
| Cooling | Chillers and pumps → towers and fans → CRAH/CDU (cooling) |
Include every source that crosses the boundary: the grid, on-site generation used by the site, fuel, gas and district utilities, converted per the declared methodology. On-site renewable energy should not simply be subtracted from the numerator to produce an artificially lower PUE.
In the denominator, include only servers, storage, networking and telecom associated with computing. Rack fans, in-row cooling or CDUs fed by IT circuits must be measured and treated consistently with the chosen category.
Dedicated data center versus mixed-use building
| Question | Dedicated | Mixed-use |
|---|---|---|
| Boundary | Building and infrastructure dedicated to the data center. | IT area and dedicated services; shared utilities require submetering or a documented method. |
| Electrical service | Utility meter + other sources. | Dedicated feeder or internal fiscal meter. |
| Cooling | The entire dedicated plant enters the total. | Energy and water for the served portion; simple area-based allocation is fragile. |
| Support areas | Include services dedicated to the operation. | Exclude common services only when outside the declared boundary. |
| Main risk | Omitted local sources and auxiliary loads. | Double counting or arbitrary allocation of chiller, pumps and water. |
mPUE and ISO 2026
ISO/IEC 30134-2:2026 adds updated guidance for mixed-use buildings and greater clarity on unaccounted energy and on-site generation. In formal reporting, record the standard version and the allocation method applied.
Coherence test
If the total meter can vary because of offices, retail or areas unrelated to the data center, the boundary is not yet resolved.
Measurement categories: from diagnostics to auditable data
| Historical category | Numerator | IT denominator | Use |
|---|---|---|---|
| 0 | Peak demand in kW | UPS output in kW | Entry-level snapshot; electrical site only. |
| 1 | 12-month energy | UPS output in kWh | Annual baseline with downstream losses inside IT. |
| 2 | 12-month energy | PDU output in kWh | Higher precision; removes PDU losses. |
| 3 | 12-month energy | IT equipment input | Closest to the computing load. |
The categories above come from the sector recommendation consolidated by DOE, The Green Grid, ASHRAE, Uptime Institute and other entities. They remain useful for understanding the maturity of the measurement point. For a current declaration, apply the categories and requirements of the ISO/IEC 30134-2 edition adopted by the organization.
- Operations: calculate 15-minute and daily series to detect deviations. Label them as operational or interval PUE.
- Reporting: consolidate energy over 12 consecutive months to reduce seasonality and make the result comparable.
Don't confuse precision with frequency: A class-0.2S meter collected without synchronization can produce a worse indicator than a well-installed, calibrated and reconciled class-0.5S system.
Minimum architecture of measurement points
| Point | Covers |
|---|---|
| M0 — Total input | Utility + generation + fuels |
| M1 — Electrical plant | Transformers, UPS and distribution |
| M2 — Thermal plant | Chillers, pumps, towers, CRAH, CDU |
| M3 — IT energy | UPS out, PDU out or rPDU |
| M4 — Other | Lighting, security, dedicated offices |
The expected balance is: M0 ≈ M1 + M2 + M3 + M4. A persistent difference larger than the combined uncertainty points to a missing meter, reversed direction, incorrect CT/PT ratio, misaligned interval, or a load classified on the wrong branch.
Collect imported and exported active energy separately. Also store kW, voltage, current, power factor, frequency and THD for diagnostics, but calculate PUE using accumulated energy over coincident intervals.
Recommended granularity: 15 minutes for operations; daily close-out; monthly reconciliation; annual publication. For highly variable AI loads, a 1-minute interval can be useful for investigation, without replacing the official accumulated figure.
Real-world instruments for electrical metering
PUE accuracy depends directly on the class, installation and calibration of the instruments at each boundary point. Three profiles cover most needs: the fixed panel-mount analyzer, the UPS-output measurement point, and the portable commissioning logger.
Fixed power analyzer
A panel-mounted power analyzer measures kWh, kW, voltage, current, power factor, demand and power quality. It can occupy M0, plant feeders or main outputs, depending on CTs/PTs and the accuracy class of the assembly — market reference architectures offer event memory and power-quality features, with the class suited to submetering.
- Configure the CT/PT ratio, 3-wire or 4-wire topology, power direction, time zone, NTP and demand interval.
- Compare the local totalizer against the value received over Modbus. Seal critical parameters and record firmware, serial number and certificate.
- Acceptance test: inject or compare at least three load levels; confirm phase sequence, power sign and energy pulse. The sum of the branches must close with the upstream meter within the declared tolerance.
UPS: a practical point for the IT denominator
UPS output is a common point for Category 1 PUE. It excludes the UPS's internal losses from the denominator, but can still include downstream losses and non-IT loads connected to the same busbars.
- Sum all parallel outputs and A/B paths without duplicating loads.
- During bypass, maintenance or ECO operation, confirm the meter keeps accumulating energy.
- Subtract CRAH, in-row or other infrastructure loads fed by the UPS, when applicable.
Watch out for A/B: Never sum two branches that measure the same transfer at successive points. Redundant paths should only be summed when both actually deliver distinct energy to the load.
UPS efficiency: track input and output to calculate losses. However, only use the output as an IT proxy when that is the declared category. UPS input is not IT energy.
Portable power-quality logger
A portable logger allows validating a fixed meter, studying feeders with no telemetry, measuring load profiles and temporarily confirming losses. It is a commissioning and diagnostic tool, not a permanent substitute for the metering system.
- Install through a qualified professional, with the appropriate safety category.
- Confirm current-probe orientation, phase sequence and reference voltage.
- Record at least one representative operational cycle and compare kWh, not just kW.
- Typical campaign: 7 to 30 days; 1-to-15-minute interval; switching log; photos of the points; raw file preserved; uncertainty report.
From UPS output to the server outlet
| Point | Includes | Advantage | Risk |
|---|---|---|---|
| UPS output | PDU, cables, rPDU and possible non-IT loads | Available at many sites | Overstates IT and artificially lowers PUE |
| PDU output | Cables and rPDU | Removes transformer/PDU losses | Unmetered circuits or mixed branches |
| Metered rPDU | Load connected to the rack | Good per-rack granularity | Communication losses and unmapped outlets |
| Equipment input | Server, storage and network | Highest fidelity | Cost and data volume |
In environments with AI racks and liquid cooling, the boundary gets more sensitive. CDU pumps, rear-door heat exchanger fans and controls can be powered from the rack. Classify them as thermal infrastructure, even when physically installed next to IT.
- Registry: link meter → panel → circuit → rack → equipment → load type. Without a taxonomy, the electrical data does not know what it is measuring.
- Quality: monitor coverage — directly metered kWh / kWh estimated from the inventory. Flag gaps and topology changes.
Rule: If a non-IT load sits on the IT busbar, it does not become IT. Measure it, subtract it, and document it.
Time, totalizers and gaps
| Control | Configuration | Failure detected |
|---|---|---|
| Clock | NTP/PTP, UTC stored, time zone applied only in display | Shifted series and a false PUE |
| Interval | 15 min with a common close-out | Numerator and denominator in different windows |
| Totalizer | Monotonic imported kWh | Reset, rollover, meter swap |
| Quality | Flags: valid, estimated, missing, maintenance | Invisible interpolation |
| Retention | Raw + aggregated + formula version | Non-reproducible indicator |
Calculate interval energy from the difference between totalizer readings. If the totalizer resets, do not accept a negative value: open an event, use the last valid/previous reading, and reset the baseline. For pulse meters, monitor the counter, the pulse constant, and input loss.
- Short gap: flag as estimated and use a transparent method, such as interpolation from an equivalent profile. Never mix estimated with measured data without a flag.
- Long gap: do not publish it as a normal value. Recalculate from a secondary source, disclose the coverage, and record the uncertainty.
Completeness target: Set a data SLA, for example: ≥99.5% of valid intervals per month, and 100% of critical meters with a synchronized clock.
Worked example: monthly PUE step by step
| Component | Energy for the month | Classification |
|---|---|---|
| Total input M0 | 1,152,000 kWh | Numerator |
| IT metered at PDU/rPDU | 870,000 kWh | Denominator |
| Cooling | 190,000 kWh | Overhead |
| Transformer/UPS/distribution losses | 52,000 kWh | Overhead |
| Lighting, security and support | 40,000 kWh | Overhead |
Calculation: PUE = 1,152,000 / 870,000 = 1.324 · DCiE = 75.5%
Interpretation: for every 1,000 kWh of IT, the infrastructure consumed an additional 0.324 kWh.
The balance closes: 870,000 + 190,000 + 52,000 + 40,000 = 1,152,000 kWh. Had the components summed to 1,105,000 kWh, there would be 47,000 kWh unaccounted for — 4.1% of the input.
Don't round early: Keep at least four decimal places in the routine calculation and round only in the presentation. PUE 1.324 and 1.325 can both display as 1.32, yet represent material differences at multi-MW installations.
Interval PUE shows the operation; annual PUE shows performance
In a didactic example, PUE worsens overnight because IT load drops while pumps, UPS losses and minimum services stay active. This does not prove the night shift operates worse; it reveals a fixed portion of infrastructure.
Use the interval chart to find chillers running at low load, pumps without reset, CRAH units simultaneously heating and cooling, or a UPS outside its efficient operating point. For the daily value, sum the kWh of every interval and only then divide; never take a simple average of PUEs.
Correct period formula: Daily PUE = Σ total energy per interval / Σ IT energy per interval. The energy-weighted average is equivalent; the arithmetic average is not.
Reconciliation: the missing number is also a KPI
| Indicator | Formula | Initial target |
|---|---|---|
| Unaccounted energy | M0 − sum of submeters | < 2% of the input |
| Direct IT coverage | Metered IT / estimated total IT | > 95% |
| Temporal completeness | Valid intervals / expected intervals | > 99.5% |
| Clock drift | Meter timestamp − NTP | < 30 s |
| Calibrated meters | Valid / critical | 100% |
The targets above are governance examples, not universal normative limits. Adjust them to the instrument class, topology and criticality. A 0% balance can also be suspicious when every value comes from estimates derived from the same meter.
- Electrical cause: a reversed CT, a missing phase, an incorrect ratio, import/export confused, or a bypassed meter.
- Data cause: duplication, time zone, rollover, Wh/kWh unit mismatch, deactivated points or packet loss.
Acceptance: Close the balance in kWh by day and by month. Investigate the trend, not just a single threshold breach.
The 10 mistakes that most distort the indicator
Formula and boundary
- Mixing instantaneous kW with accumulated kWh.
- Using different intervals in the numerator and denominator.
- Calling UPS input "IT energy."
- Leaving in-row cooling on the IT busbar without subtracting it.
- Subtracting on-site solar from total energy to improve PUE.
Data and comparison
- Ignoring generators, gas or district utilities.
- Allocating a shared chiller only by floor area.
- Summing A/B paths or cascaded meters twice.
- Taking a simple average of hourly PUE.
- Comparing sites without disclosing climate, occupancy and redundancy.
Quick test: If turning off an infrastructure fan makes the IT denominator drop, the electrical classification is wrong. If a day with no water shows up as zero WUE while the tower was running, there is a data or boundary failure.
Fix: maintain a version-controlled diagram, an inclusion/exclusion matrix, and one owner per meter.
Improvement levers and how to prove the gain
| Action | Signal before | Proof measurement |
|---|---|---|
| Containment and sealing | Low ΔT, air bypass | Fan kW and per-aisle temperatures |
| Chilled-water reset | Conservative fixed setpoint | kW/ton, approach and economizer hours |
| VFDs on pumps/fans | Throttled valve, fixed speed | kW versus flow and differential pressure |
| Chiller sequencing | Multiple machines at low load | Operational COP/IPLV per stage |
| UPS at its efficient point | Low load per module | Input, output, losses and operating mode |
| Higher supply temperature | Excessive thermal margin | Thermal compliance and rack alarms |
Take before/after measurements with comparable IT load and outdoor conditions. For complex interventions, use regression or a baseline keyed to wet-bulb/dry-bulb temperature and load. Log simultaneous changes so the entire gain is not misattributed to the wrong action.
Priority: First eliminate unnecessary simultaneous operation and control failures; only then invest in retrofits. Control software usually reveals faster gains, provided reliable instrumentation exists.
Water consumed per unit of energy delivered to IT
ISO/IEC 30134-9 defines WUE as a KPI to quantify a data center's water consumption during its use phase. The common unit is L/kWh. The report should explain sources, uses, exclusions, water quality, interval and measurement category.
In routine practice, distinguish water withdrawal, consumption and discharge. Evaporation is consumption; blowdown sent to the sewer is discharge; water drawn and returned to the same system can increase withdrawal without an equal increase in consumption. The applied definition must be explicit.
- Interval indicator: useful for leaks and tower control. Can vary widely with climate and cycles of concentration.
- Annual indicator: the basis for reporting — sum 12 months of water and divide by the sum of IT energy.
Local context: A WUE of 0.2 L/kWh in a basin under high water stress can warrant more attention than 0.5 L/kWh where abundant reused water is available. Always report the source and the water-stress risk.
Water balance: measuring source, use and destination
| Measurement point | Role in the balance |
|---|---|
| M-W0 · Potable water | Main input source |
| M-W1 · Reused water | Alternative source, reduces potable-water consumption |
| Storage (tanks) | Intermediate stock between source and use |
| M-W2 · Towers | Largest single use — evaporation, blowdown and drift |
| M-W3 · Humidification | Room/thermal-plant use |
| M-W4 · Adiabatic | Seasonal use on hot days |
| M-W5 · Other | Cleaning and other declared processes |
| Discharge (blowdown/sewer) | System output |
The general meter captures the total but does not locate the cause. Sub-meters by use let you separate evaporation, blowdown, leaks, humidification and cleaning. Also measure alternative sources to demonstrate the reduction in potable water without hiding total consumption.
Check the balance: sources = uses + stock change + discharge, respecting the consumption concept adopted. Tank level can create an apparent water consumption or generation over short periods; monthly consolidations reduce this effect.
Real-world instruments for water metering
Electromagnetic flow meter
Electromagnetic meters are well suited to conductive water and effluents. They have no significant internal obstruction, measure bidirectional flow and provide totalizers for BMS/SCADA integration. Market reference models report a standard error on the order of ±0.5% of reading, with a higher-accuracy option — real uncertainty also includes installation, flow profile and parameterization.
- Install in always-full piping, respecting grounding, direction, position and the straight runs specified by the manufacturer.
- Size by the flow range, not just the pipe diameter.
- Log the totalizer, instantaneous flow, status and diagnostics.
- Commissioning: compare the transferred volume against tank level or a reference meter; verify zero flow with the valve closed, and confirm the fault signal reaches the supervisory system.
Battery-powered standalone meter
A battery-powered meter can instrument sources and branches where power or communication is unavailable. It is especially useful for pipelines, reused water, wells and remote points.
- Define the pulse unit and weight, read imported/exported totalizers, monitor the battery and plan communication.
- If using a pulse output, ensure the counter does not lose events during a BMS outage. Perform a manual contingency reading.
- For a continuous KPI, prefer a persistent totalizer and telemetry with diagnostics — the battery solves the infrastructure problem, but demands maintenance governance.
Information redundancy: Keep a monthly photo of the display or a local export. It helps reconstruct periods when the automation network fails.
How to choose the right meter
| Technology | Application | Advantage | Limitation |
|---|---|---|---|
| Electromagnetic | Conductive water, makeup and blowdown | No relevant loss; good range | Requires a full pipe and grounding |
| Clamp-on ultrasonic | Temporary campaigns and retrofits | No pipe cutting required | Sensitive to installation and profile |
| Inline ultrasonic | Clean water | Low maintenance | Bubbles and solids can affect it |
| Mechanical/Woltmann | Utility water | Simple and widespread | Moving parts and a lower range |
| Coriolis | Special fluids and dosing | Mass and density | Cost and pressure drop |
Specify: fluid, conductivity, diameter, pressure, temperature, minimum/normal/maximum flow, available straight run, protection class, power supply, protocol, non-volatile totalizer, accuracy, repeatability and traceable calibration.
- Avoid oversizing: an overly large meter operates near its lower limit and loses resolution exactly during low-consumption periods.
- Zero point: a closed valve should produce zero flow. A recurring offset turns into thousands of liters over a month.
Minimum data: Totalizer in m³ + flow in m³/h + quality/status + timestamp.
Cooling tower: where the water disappears
Tower makeup covers three components: evaporation, blowdown and drift. Leaks and overflows show up as abnormal consumption. Measuring only makeup lets you calculate WUE, but does not reveal treatment efficiency.
Instrument makeup and blowdown; monitor conductivity, level, valve position and cycles of concentration. Drift must be limited by drift eliminators and verified through inspection. Evaporation can be estimated from the thermal balance for cross-checking, not as a substitute for measurement when the KPI is reported.
Failure signal: Makeup grows without a rise in thermal load or wet-bulb temperature; blowdown stays open for long periods; CoC drops; level fluctuates; water shows up in drains or overflow.
Conductivity and cycles of concentration
Operational estimate: CoC ≈ circulating-water conductivity / makeup-water conductivity.
Example: 850 µS/cm ÷ 250 µS/cm = 3.4 cycles.
Raising CoC generally reduces blowdown, but increases the risk of scaling, corrosion and biological growth. The limit depends on water chemistry, materials, temperature, treatment and the guidance of the responsible specialist.
Install representative sensors, with temperature compensation and a cleaning/calibration routine. Compare the online sensor against a bench sample. A dirty sensor can keep the blowdown valve open and worsen WUE for days.
Safe control: Don't chase WUE by reducing blowdown beyond the chemistry window. Water efficiency without asset integrity creates downtime risk and maintenance cost.
Water-cooled cooling: the link between PUE and WUE
A water-cooled chiller consumes electricity; its associated tower can consume water. To diagnose PUE and WUE together, measure chiller kW, pumps and towers, chilled/condenser water flow, and supply/return temperatures.
- Calculate thermal capacity from flow and ΔT, then kW/ton or COP.
- Check tower approach, condensing temperature, fouling and part-load behavior.
- Sequence machines to avoid several units running inefficiently at low load.
Market-reference water-cooled chillers typically operate in a range from a few hundred kW up to a bit over 1,000 kW per unit, with a screw compressor and flooded evaporator — always use the specific data for the actual selection installed, not a generic range.
Don't confuse: Water in a closed loop transports heat and is not necessarily consumed. Consumption occurs mainly through evaporative heat rejection, blowdown, leaks and makeup.
Dry cooler, chiller and evaporation: there is no universal solution
| Architecture | Energy | Local water | Best context |
|---|---|---|---|
| Dry cooler | Can rise in hot climates | Very low | Scarce water; compatible fluid temperature |
| Air-cooled chiller | Higher at high temperatures | Low | Simple deployment and less water infrastructure |
| Tower + water-cooled chiller | Often lower | Higher | Available water and robust treatment |
| Hybrid adiabatic | Intermediate | Seasonal | Optimization by climate and mode |
| Economizer | Very low during favorable hours | Depends on rejection | Suitable climate and setpoints |
Compare alternatives hour by hour using dry-bulb and wet-bulb temperature, thermal load, energy price and carbon, and water cost and risk. A lower PUE is not automatically the most environmentally responsible option.
- Water mode: define the adiabatic activation threshold, expected consumption and source quality.
- Energy mode: define the temperature limit, fan speed and impact on supply temperature.
Decision: Optimize total cost, carbon, water and reliability — not a single ratio.
CDU: the link between the rack and the plant
The CDU (Coolant Distribution Unit) isolates and controls the secondary loop that serves cold plates or rear-door heat exchangers. It adds pumps and controls to PUE, but the closed loop typically consumes little water after the initial fill.
- Measure CDU electrical energy, flow, supply/return temperature, ΔP, reservoir level, conductivity/quality and makeup events.
- On the primary side, account for the chiller, dry cooler or tower that rejects the heat.
Market-reference CDU families offer liquid-to-liquid and liquid-to-air units, with flow monitoring, redundant pumps and different capacities per model.
Critical point: Calling all liquid cooling "zero water" is incorrect. The IT loop can be closed while the primary plant uses evaporation. WUE needs to see the whole facility.
Thermal instrumentation: temperature and humidity
Environmental sensors don't enter the PUE/WUE formula directly, but they let you operate setpoints safely, detect overcooling, and correlate energy with room conditions.
- Position probes at rack intakes at representative heights, avoiding direct airflow, hot surfaces and dead zones.
- Define a map, identification, calibration and tolerance.
- Use dew point when liquid cooling is present, to control condensation risk.
Market-reference temperature and relative-humidity sensors typically cover the full 0-100% RH range, with analog or digital output and traceable calibration.
Use in M&V: Before raising a setpoint or reducing air flow, record per-rack temperatures, alarms and fan power. The gain is only valid if thermal compliance is preserved.
Worked example: monthly WUE step by step
| Water use | Volume | Note |
|---|---|---|
| Tower makeup | 420 m³ | Includes evaporation, blowdown and drift |
| Humidification | 8 m³ | Dedicated meter |
| Adiabatic system | 5 m³ | Operation on hot days |
| Other uses within the boundary | 5 m³ | Declared cleaning/process use |
| Total declared consumption | 438 m³ | 438,000 L |
| IT energy | 870,000 kWh | Same month as the PUE |
Calculation: WUE = 438,000 / 870,000 = 0.503 L/kWh
Reading: every 1,000 kWh of IT was associated with 503 liters of water within the declared boundary.
If 300 m³ came from reused water and 138 m³ from potable water, total consumption is still 438 m³. Also report the complementary potable-water indicator: 138,000 / 870,000 = 0.159 L/kWh.
Transparency: Separating potable and reused sources demonstrates stewardship without redefining WUE to hide consumption. Publish both with clear names.
Detecting a leak from behavior, not the monthly bill
| Signal | Hypothesis | Action |
|---|---|---|
| Continuous overnight flow | Leak, valve or overflow | Isolate branches and confirm level |
| Makeup rises, blowdown does not | Evaporation, drift or leak | Correlate with weather and inspect |
| Blowdown open with low CoC | Dirty sensor or wrong logic | Manual sample and calibration |
| Tank falls with no metered consumption | Missing meter or downstream leak | Tightness test |
| Pulse stops, local flow exists | Input/telemetry failure | Compare local totalizer |
Build simple models per operating mode: expected water = a function of IT load, wet-bulb temperature, tower/adiabatic hours and CoC. The alarm should factor in persistence and deviation from expectation, not just a fixed threshold.
- Fast alarm: flow above minimum for 30 min with consuming systems turned off.
- Trend alarm: daily consumption more than 20% above the model for 3 days, with similar weather and load.
Response: The alarm needs to state the branch, the last valid value, the plant mode and the owner; otherwise it becomes noise.
The PUE x WUE matrix
| Combination | Reading |
|---|---|
| Low PUE / low WUE | Excellent, when reliable. |
| High PUE / low WUE | Higher energy; water saved. |
| Low PUE / high WUE | Energy-efficient evaporation. |
| High PUE / high WUE | Priority for intervention. |
Use the matrix by hour, season or cooling mode. Then add cost, marginal carbon, water-stress risk and capacity. The optimal point can shift throughout the day.
Operational decision: During a drought period, accept a small PUE increase to reduce water. During a carbon-intensive electricity window, the decision can flip — within reliability limits.
Climate, load and occupancy explain more than the ranking
- Dry bulb: affects the dry cooler and the air-cooled chiller.
- Wet bulb: governs evaporation and tower potential.
- IT load: changes the fixed share and part-load efficiency.
- Redundancy: active modules at low load raise losses.
- Occupancy: a new site can have a high PUE before it fills up.
- Setpoints: supply, pressure and ΔT change pump/fan behavior.
For M&V, model infrastructure energy and water as a function of the relevant variables. Compare observed against expected and report confidence intervals. In simpler analyses, split days by load and temperature ranges.
Never present a universal PUE/WUE target with no conditions attached. A Tier III/IV facility, an edge site and a hyperscale campus have very different profiles.
Minimum baseline: 12 months whenever possible; covering seasons, maintenance and different load levels. For a new project, use a calibrated model and review after stabilization.
Real benchmarks — with context
| Source / period | PUE | WUE | Scope |
|---|---|---|---|
| Uptime Institute Survey 2025 | 1.54 | n/a | Annual weighted average of respondents |
| Google fleet-wide 2025 | 1.09 | not published on the page | Global fleet average |
| Microsoft global FY25 | 1.17 | 0.27 L/kWh | Owned/controlled data centers, 12 months |
| Microsoft Americas FY25 | 1.16 | 0.34 L/kWh | Regional aggregate |
| Microsoft EMEA FY25 | 1.16 | 0.03 L/kWh | Regional aggregate |
Uptime reports that facilities commissioned in the five years prior to the 2025 survey had an average PUE of 1.48; sites of 20 MW or larger, 1.44. The analysis itself highlights differences in age, scale and region.
- What to copy: measurement discipline, disclosing the period, and scope transparency.
- What not to copy: a numeric target with no assessment of climate, architecture, redundancy and water-stress risk.
Correct reading: A benchmark is a reference, not a verdict. First compare your site against its own baseline and against genuinely equivalent facilities.
A dashboard that leads from the KPI to the cause
An effective operational dashboard shows, at the same time, the consolidated indicator and the deviations that explain it. The example below reproduces the format used in a typical 24-hour shift.
| 24h indicator | Value |
|---|---|
| PUE | 1.31 |
| WUE | 0.47 L/kWh |
| IT load | 8.7 MW |
| Valid data | 99.8% |
| Alarm | Value | Context | Owner |
|---|---|---|---|
| WUE above model | +24% | Tower 2 / CoC 2.1 | HVAC |
| Unexplained energy | 3.4% | Panel QGBT-B | Electrical |
| Missing data | 6 intervals | rPDU Room 3 | Automation |
Drill-down: Mentally click on PUE: total → cooling → chiller/pump/tower → equipment → control variable. The dashboard should support that sequence.
Actionable alarms for energy and water
| Alarm | Example logic | Avoid |
|---|---|---|
| Anomalous PUE | Model residual > 3σ for 4 intervals | A fixed threshold with no load/climate context |
| Anomalous WUE | L/kWh > baseline + 20% for 3 h | An alarm triggered by a tank-level change |
| Frozen meter | Same totalizer with load > 0 | Confusing a stable value with a communication failure |
| Electrical balance | |M0 − sum| / M0 > 2% for 1 day | Using estimated data as proof |
| Water balance | Sources − uses outside tolerance | Ignoring tank stock |
| Excessive blowdown | Valve open + CoC below target | Acting without checking chemistry |
Every alarm must carry severity, persistence, deadband, affected asset, trend, last maintenance date and a response playbook. Measure the false-positive rate and the time to acknowledgment.
- Priority 1: risk of loss, leak or environmental impact — dispatch operations immediately.
- Priority 2: persistent efficiency deviation — open an investigation and a work order.
Governance: An alarm with no owner and no deadline is just decoration on the dashboard.
Calibration, verification and uncertainty
| Asset | Field verification | Evidence |
|---|---|---|
| Electrical meter | Phase, CT/PT, direction, comparative kWh | Certificate + load test |
| Flow meter | Zero, totalizer, direction, full pipe | Certificate + volume test |
| Temperature/RH | Multi-point comparison | "As found / as left" |
| Conductivity | Certified standard + bench sample | Cleaning/calibration record |
| Clock/gateway | Offset against NTP and packet loss | Automatic log |
KPI uncertainty combines the numerator and the denominator. For a ratio R = A/B, one approximation is: uR/R ≈ √[(uA/A)² + (uB/B)²], when the sources are independent. Include CTs, the meter, data transformation and estimates.
Example: total energy at ±0.7% and IT at ±1.0% yield an approximate relative uncertainty of 1.22% in PUE.
- Periodicity: set it by criticality, stability, contractual requirements and history — not just a generic calendar.
- Meter replacement: record the final reading, the initial reading, serial number, CT/PT ratio, date/time and a post-swap test. Preserve the continuity of the logical totalizer.
FAT, SAT and integrated metering test
- 1. Design: point diagram, load matrix, ranges and protocols.
- 2. FAT: configuration, units, registers, totalizers and alarms.
- 3. SAT: physical installation, direction, grounding, network and local readout.
- 4. Loop check: from the sensor to the BMS/DCIM — value, unit, quality and timestamp.
- 5. Integrated test: UPS, generator, bypass, chiller, tower and CDU transfers.
- 6. Acceptance: closed balance, coverage, certificates and as-built documentation.
Exit criterion: No critical point without a name, unit, scale, owner and test. Electrical/water balance within the agreed tolerance over a representative period.
30-day plan to get started
| Week | Deliverable | Activities |
|---|---|---|
| 1 | Boundary map | Site walkthrough, single-line diagram, P&ID, sources, uses, IT/non-IT loads and gaps. |
| 2 | Meter inventory | Serial number, model, class, CT/PT, protocol, calibration, owner and criticality. |
| 3 | Pipeline and formulas | NTP, collection, flags, totalizers, balances, interval PUE/WUE. |
| 4 | Baseline and backlog | Pilot monthly close-out, loss causes, CAPEX/OPEX and owners. |
Start with existing meters, but treat gaps as an explicit backlog. An initial project can use a portable campaign to validate estimates while permanent submetering is installed.
- Quick wins: synchronize clocks, fix CT/PT ratios, remove non-IT loads from the denominator, and close the balance.
- Investments: plant submetering, rPDU, tower/blowdown flow, conductivity and DCIM/BMS integration.
Result at month's end: A first reproducible PUE/WUE, an uncertainty map, a pilot dashboard and a prioritized list of deviations. Don't force a target before the data stabilizes.
Monthly and annual report template
- Site identification, period, methodology version and technical owner.
- Physical/accounting boundary and diagram of the energy and water points.
- Measurement category, instruments, class, calibration and coverage.
- Total energy, IT energy, water by source/use, PUE, WUE and uncertainty.
- Conditions: IT load, weather, hours per mode, occupancy and outages.
- Missing/estimated data, correction method and impact on the result.
- Balances, deviations, causes, actions, owners and deadlines.
- Comparison against baseline and normalized targets — not just an external benchmark.
- Attachments: raw series, certificates, logs, changes and photographic evidence.
Data signature: The report must let someone else redo the calculation from the totalizers and the versioned formula. If that is not possible, the KPI is not auditable.
Instrumentation list — reference
| Group | Minimum items | Category examples |
|---|---|---|
| Total energy | Appropriate-class meter, CT/PT, gateway | Panel-mounted power analyzer |
| Validation | Three-phase logger and probes | Portable power-quality logger |
| IT | UPS out, PDU out, metered rPDU | Native metering + submeters |
| Water | General, tower, blowdown and source meters | Electromagnetic + battery-powered standalone |
| Chemistry | Conductivity, pH and temperature | Multiparameter transmitter + sensors |
| Environment | Temperature, RH, dew point | Temperature/humidity sensor |
| Liquid cooling | kW, flow, supply/return, ΔP, leak | CDU + sensors |
| Data | Gateway, NTP, historian, BMS/DCIM | Modbus TCP/RTU, BACnet, SNMP |
Brand selection should be driven by engineering, local availability, support, integration, accuracy and lifecycle cost. Require documentation, a register map, certificates and a replacement procedure.
Spares: Plan for CTs, power supplies, communication modules, sensors and a contingency meter. Without spare parts and a saved parameterization, the historical series stays vulnerable.
Quick PUE and WUE audit checklist
- Boundary approved and version-controlled.
- Every energy vector and water source identified.
- Numerator and denominator use the same interval.
- IT point and measurement category declared.
- Non-IT loads on the IT busbar subtracted.
- CTs/PTs, direction, units and totalizers verified.
- Water meters correctly sized and installed.
- Makeup, blowdown, sources and stock reconciled.
- NTP, completeness and quality flags working.
- Unaccounted energy/water within tolerance.
- Calibration and verification traceable.
- Report includes load, climate, mode and uncertainty.
- Actions have an owner, a deadline and result validation.
Stop and fix: If more than three critical items are missing, treat PUE/WUE as a management estimate, not an auditable indicator or public claim.
Operational glossary
| Term | Short definition |
|---|---|
| PUE | Total data center energy divided by IT energy. |
| WUE | Liters of water consumed per kWh of IT, within the declared boundary. |
| DCiE | Reciprocal of PUE, usually expressed as a %. |
| UPS | Uninterruptible power supply system. |
| PDU / rPDU | Room-level / rack-level power distribution. |
| CRAH / CRAC | Computer room air handler / direct-expansion cooling unit. |
| CDU | Coolant distribution unit for liquid cooling. |
| ΔT / ΔP | Temperature / pressure difference between two points. |
| CoC | Cycles of concentration in an evaporative loop. |
| BMS / DCIM | Building management system / data center infrastructure management. |
| M&V | Measurement and verification of performance. |
| CT / PT | Current transformer / potential (voltage) transformer. |
| NTP / PTP | Time-synchronization protocols. |
Convention: always write the unit next to the value, and record whether the indicator is instantaneous, interval-based, monthly or annual.
Sources and references
Priority was given to technical standards, sustainability reports published by the operators themselves, and official manufacturer pages cited as instrument-category references (not as an exclusive brand recommendation).
- ISO/IEC 30134-2:2026 — Power usage effectiveness (PUE) — ISO
- ISO/IEC 30134-9:2022 — Water usage effectiveness (WUE) — ISO
- Recommendations for Measuring and Reporting Overall Data Center Efficiency, Version 2 — U.S. Department of Energy et al.
- WP#35 Water Usage Effectiveness and technical library — The Green Grid
- Global Data Center Survey 2025 — Uptime Institute
- Measuring energy and water efficiency for datacenters — Microsoft
- Operating sustainably — Google Data Centers
- PowerLogic PM8000 — product page — Schneider Electric
- 1736/1738 Series — product page — Fluke
- Proline Promag W 400 — product page — Endress+Hauser
- SITRANS FM MAG 8000 — product page — Siemens
- AquaForce 30XW — product page — Carrier
- Liebert EXL S1 and Liebert XDU — product pages — Vertiv
- HMT120/HMT130 — product page — Vaisala
- Liquiline CM44 — product page — Endress+Hauser
Sources accessed and verified: September 2026. Commercial specifications can change; confirm the current datasheet for the selected model before specifying a project.
Conclusion
PUE and WUE gain value when they point to an operational cause, a design decision or a verifiable action. The path is simple to describe and rigorous to execute: boundary, instrument, time, balance, context and audit.
The mature routine: Continuous collection • daily close-out • monthly reconciliation • annual consolidation • target review • proven improvement.
Next step: Walk your facility's electrical single-line diagram and water P&ID and mark every point that is actually measured. The gap between the drawing and the field is the program's first backlog.