Power usage effectiveness (PUE) is total data center energy divided by IT equipment energy over the same reporting period. A usable PUE value must identify the facility boundary, the IT measurement point, the energy sources included, and the measurement dates. Without those details, a lower reported number may reflect a different accounting boundary rather than more efficient infrastructure.
For annual reporting:
where:
- (E_{\mathrm{DC}}) is total energy attributable to the data center and its supporting infrastructure during the reporting period.
- (E_{\mathrm{IT}}) is energy supplied to the IT load during that same period, measured at a declared point in the power distribution system.
- Both quantities use compatible energy units, normally kWh or MWh. PUE is dimensionless.
The critical choice is the boundary: what enters the numerator and where the denominator is measured. The DOE-hosted Recommendations for Measuring and Reporting Overall Data Center Efficiency, Version 2—Measuring PUE for Data Centers, dated May 17, 2011, provides explicit boundary rules and measurement categories. Those categories are specific to that document; do not apply their labels to a different reporting framework without checking its requirements.
PUE Metric Definitions Reference Table
The table distinguishes the inputs to PUE from related ratios and water metrics. Infrastructure overhead and IT energy share are useful interpretations of the same energy balance, not substitutes for declaring the PUE measurement method.
| Metric or quantity | Numerator | Denominator | Units | Boundary type | Measurement period | Common exclusion or interpretation risk |
|---|---|---|---|---|---|---|
| Annual energy-based PUE | Total data center energy, including IT and supporting infrastructure | IT energy at the declared measurement point | kWh/kWh or MWh/MWh; dimensionless | Dedicated facility or explicitly defined data center boundary within a mixed-use building | Same 12 consecutive months for both quantities | Omitting cooling, fuel, dedicated support spaces, or downstream losses while comparing unlike meter locations |
| Demand-based PUE₀ under the 2011 recommendations | Total data center electric demand under the prescribed peak-demand method | IT electric demand at UPS output under that method | kW/kW; dimensionless | All-electric data center only | Peak-demand assessment over a 12-month period, not cumulative annual energy | Presenting a demand snapshot as annual energy performance or overlooking non-electric energy |
| Infrastructure overhead relative to IT energy: (\mathrm{PUE}-1) | Total data center energy minus declared IT energy | Declared IT energy | Dimensionless; multiply by 100 for a percentage | Same boundary and meter basis as the underlying PUE | Same period as PUE | Calling this the infrastructure share of total facility energy |
| IT energy share: (1/\mathrm{PUE}) | Declared IT energy | Total data center energy | Fraction; multiply by 100 for a percentage | Same boundary and meter basis as the underlying PUE | Same period as PUE | Treating the IT energy share as computational efficiency or useful work per unit energy |
| Site water usage effectiveness, WUE | Annual site water use attributable to data center operations | Annual IT equipment energy | L/kWh | On-site operational water boundary | Matching annual water and IT energy periods | Counting only evaporation, omitting other applicable operational water use, or using facility energy as the denominator |
| Source water usage effectiveness, WUEsource | Annual site operational water use plus off-site water use associated with supplying the energy used | Annual IT equipment energy | L/kWh | Site operations plus energy-supply water boundary | Matching annual period and energy-supply data | Comparing it directly with site-only WUE or mixing incompatible water-accounting factors |
The PUE definitions and demand-based category follow the 2011 task-force recommendations. The water definitions follow The Green Grid’s 2011 Water Usage Effectiveness white paper, which specifies IT equipment energy—not total facility energy—as the WUE denominator. Its operational metrics do not represent the full life-cycle environmental burden of the facility or IT equipment.
For water reporting, identify whether the numerator comes from supply meters, a water balance, or another accounting method. The Green Grid’s operational water description includes humidification and cooling-related evaporation, blowdown, and drift; a cooling-tower evaporation estimate alone does not represent that entire boundary.
Set the Facility Boundary Before Collecting Totals
Dedicated data center
Under the 2011 recommendations, a dedicated data center is a stand-alone building whose spaces and infrastructure serve IT operations and their support functions. Its total-energy boundary includes IT, cooling, electrical distribution, lighting, and dedicated ancillary services such as operational offices, lobbies, and restrooms. It is not limited to the server room.
Include actual energy used by supporting systems, including losses and operating consumption associated with redundant equipment. Installed spare capacity is not itself energy consumption: do not add equipment nameplate ratings to measured kWh.
A facility utility meter can provide much of the numerator, but first check whether it misses another energy supply or includes an unrelated building. Add only energy streams not already counted. For example, downstream UPS output is part of electricity already measured at the incoming supply; adding both would double-count that energy.
Data center within a mixed-use building
A whole-building utility bill is not automatically a data center energy total. Separate the data center’s energy from unrelated office, retail, laboratory, or other building functions.
The 2011 recommendations explicitly address mixed-use data centers with dedicated electrical and cooling infrastructure. They require dedicated ancillary services to remain inside the boundary while allowing shared ancillary spaces, such as common lobbies and elevators, to be excluded. Their treatment should not be mistaken for a complete allocation procedure for every shared central plant.
Where a data center shares cooling or electrical infrastructure, establish the allocation method before reporting a whole-data-center PUE. Identify:
- Which shared equipment serves the data center.
- Which meters measure its delivered service and energy input.
- How plant energy and distribution losses are attributed to that service.
- Which quantities are measured and which are estimated.
A floor-area allocation alone does not establish the data center’s cooling or electrical consumption. If a material shared load cannot be measured or defensibly allocated, disclose the missing load and describe the result as an estimate rather than a complete measured facility PUE.
IT Meter Location Changes the Reported PUE
The denominator should represent the declared IT measurement boundary, not whichever meter produces the lowest ratio. Moving the measurement point downstream removes distribution losses from the denominator while leaving them in total facility energy.
The following categories reproduce the structure of Section 3.2 and Table 1 of the 2011 recommendations.
| Category in the 2011 recommendations | IT measurement point | Measurement basis | What the denominator can include |
|---|---|---|---|
| PUE₀ | UPS output | Electric demand in kW under the document’s peak-demand method | Downstream distribution losses; applicable non-IT loads must be removed |
| PUE₁ | UPS output | Cumulative kWh over 12 consecutive months | Downstream electrical distribution losses, after removing applicable non-IT loads |
| PUE₂ | PDU output | Cumulative kWh over 12 consecutive months | Losses downstream of the PDU measurement point, after removing applicable non-IT loads |
| PUE₃ | IT equipment input | Cumulative kWh over 12 consecutive months | Energy entering IT devices, excluding upstream distribution losses and separate non-IT devices |
UPS means uninterruptible power supply; PDU means power distribution unit.
A UPS or PDU output meter may also supply cooling equipment. The recommendations require those non-IT loads to be metered and subtracted from the output reading used for IT energy. They also distinguish separate rack-mounted fans from the energy entering IT devices. Do not classify every load in an IT rack as IT equipment energy.
These categories describe measurement arrangements, not facility quality grades. Reporting PUE₃ does not prove superior energy performance, reliability, or compliance with another standard.
Example: Same facility, different denominator
Assume an all-electric dedicated data center has these hypothetical readings for the same 12 months:
| Measurement | Annual energy |
|---|---|
| Total facility electricity | 12,000 MWh |
| UPS output serving IT distribution, with no non-IT loads on that output | 9,600 MWh |
| Aggregate IT equipment input | 9,000 MWh |
Using UPS output:
Using IT equipment input:
The 600 MWh difference is downstream distribution energy included in the UPS-output denominator but excluded from the IT-input denominator. No physical efficiency change occurred between the two calculations.
On the IT-input basis, infrastructure energy is:
That is 33.3% of IT energy but 25.0% of total facility energy. Consequently, “PUE minus one” and “infrastructure share of total energy” are different quantities.
These are illustrative inputs, not operating benchmarks or measured results from a particular facility.
Match Units, Energy Sources, and Reporting Periods
Use energy totals for annual PUE
kW measures power; kWh measures energy accumulated over time. Dividing facility kW by IT kWh does not produce PUE.
An annual energy-based result uses cumulative energy for both quantities over the same 12 consecutive months. A shorter-period ratio can support operational tracking, but label its actual dates rather than presenting it as annual PUE. The 2011 recommendations prefer annual energy consumption because it captures changing IT and cooling loads more completely than a demand snapshot.
For interval or monthly data:
=
\frac{\sum_i E_{\mathrm{DC},i}}
{\sum_i E_{\mathrm{IT},i}}
Do not take an unweighted arithmetic average of monthly PUE values. The correct aggregate is equivalent to weighting each interval’s PUE by its IT energy:
=
\frac{\sum_i \left(\mathrm{PUE}_i E_{\mathrm{IT},i}\right)}
{\sum_i E_{\mathrm{IT},i}}
For example, two reporting blocks with facility/IT energy totals of 1,800/1,000 MWh and 10,200/8,000 MWh produce a combined PUE of (12{,}000/9{,}000=1.333\ldots). Averaging their individual ratios gives 1.5375, which incorrectly gives the smaller-energy block equal weight.
When aggregating multiple facilities, use compatible definitions and calculate the ratio of summed facility energy to summed IT energy. Do not average site PUE values without their IT-energy weights.
Declare the treatment of non-electric energy
Electricity, fuel, and purchased thermal services cannot be combined merely by copying their billing numbers into one total. First convert quantities into compatible energy units, then apply the accounting method required by the selected reporting framework.
Section 3.3 of the 2011 recommendations uses source-energy weighting factors normalized to electricity for facilities with multiple energy types. Its Table 2 contains historical factors based on the methodology cited in that edition. Those factors are not universal current conversion constants and should not be silently substituted into a different standard, contract, or reporting program.
For a mixed-energy assessment, retain the original quantity and unit for each input, its conversion to energy, the weighting factor if applicable, and the factor’s source and edition. Purchased chilled water requires particular care: thermal energy delivered is not the same quantity as electricity consumed by a chiller.
On-site generation also requires a consistent boundary. Count an energy stream once, not both a generator’s fuel input and its electrical output as independent incoming energy for the same process. Dedicated combined heat and power has additional accounting provisions in Section 3.5 of the 2011 recommendations; a simple electricity-only ratio does not reproduce that method.
Do not subtract renewable electricity or exported heat from PUE
The 2011 recommendations include electricity from renewable sources on the same basis as grid electricity. Replacing grid supply with renewable electricity does not, by itself, improve PUE because PUE evaluates energy use within the data center rather than the carbon characteristics of its supply.
Likewise, heat exported for use outside the data center is not deducted from the PUE numerator. Energy reuse effectiveness is a separate metric. Internal heat reuse can reduce measured facility energy if it avoids another energy input, but that benefit is already reflected in the meter totals; do not subtract it again.
Record Enough Information to Reproduce the Result
A published PUE should be accompanied by a compact measurement record:
| Record field | Information to retain or report |
|---|---|
| Method | Reporting framework, document edition, and applicable measurement category |
| Facility boundary | Dedicated building or defined mixed-use boundary; included support spaces and shared services |
| Reporting dates | Matching start and end dates for facility and IT energy |
| Facility energy inputs | Each electricity, fuel, or thermal-service input, including on-site generation treatment |
| IT measurement point | UPS output, PDU output, or IT equipment input; meters and feeds included |
| Non-IT corrections | Cooling or other support loads removed from the IT denominator |
| Units and factors | Original units, energy conversions, and any source-energy weighting factors |
| Data completeness | Meter gaps, estimated quantities, allocation methods, and boundary changes |
| Operating context | IT loading, significant outages, commissioning activity, and relevant cooling or redundancy changes |
Under the 2011 recommendations, publication includes the category subscript. If another framework governs the report, use that framework’s required notation rather than claiming equivalence based only on the ratio.
A zero IT-energy denominator makes PUE undefined. Negative energy totals, missing feeds, or an ordinary whole-facility PUE below 1 require investigation of the accounting and meter boundaries before interpreting the result. PUE’s theoretical minimum is 1 when total facility energy includes the IT energy on a consistent basis.
Compare Infrastructure Performance Without Overstating the Result
A lower PUE indicates less total facility energy per unit of declared IT energy under the stated accounting method. It does not establish that the IT equipment performs more useful work per kWh. The DOE’s Best Practices Guide for Energy-Efficient Data Center Design, revised July 2024, distinguishes infrastructure efficiency from overall data center efficiency.
For a before-and-after comparison, retain the same boundary and meter locations, and examine absolute facility and IT energy alongside the ratio. If IT demand falls while some infrastructure consumption remains fixed, total energy can decrease even as PUE rises. Conversely, increasing IT load can reduce the ratio without reducing total facility consumption.
For cross-site comparisons, check measurement basis, climate, load level, and reliability provisions before ranking facilities. The 2011 recommendations specifically caution that climate and reliability differences can affect comparisons. A favorable PUE alone does not establish cooling capacity, backup duration, equipment performance, or the suitability of an infrastructure design.
When comparing cooling alternatives, keep site WUE and source WUE separate from PUE. Reducing on-site water use can increase electricity demand and therefore shift water use to the energy supply chain. Use matching IT-energy denominators and disclose the water and energy boundaries instead of treating any single ratio as a complete environmental assessment.