Cooling economics / Measured plant power
Data Center Cooling Cost per kW: Measure and Compare
A lower facility cooling-meter reading does not always mean lower total electricity use. This guide keeps the accounting boundary visible.
Sections in this article
A retrofit proposal says the new cooling design will save $180 per kW every year. The number sounds precise, but the proposal does not specify whether “kW” means installed IT capacity, average operating IT demand or thermal rejection capacity. It also omits fan electricity inside servers. The project cannot be compared fairly until its numerator and denominator describe the same operating period and scope.
Useful definition: annual cooling electricity cost per average IT kW equals metered cooling energy cost during the period ÷ average IT demand in kW during that same period. Keep cooling plant energy separate from server energy and from PUE. This is an operating-expense allocation, not a universal equipment efficiency rating.
Cooling cost per IT kW calculator
Enter metered or scenario-average electrical power drawn by the cooling plant before and after a proposed change, along with average IT load and annual operating hours. The extra server-fan field captures an otherwise hidden shift across the meter boundary: positive means server-fan power increases in the proposal; negative means it decreases.
Savings include the entered server-fan power difference but exclude maintenance, demand charges and capital finance.
Which meters belong in cooling cost?
Chiller compressors, cooling towers, mechanical fans, facility cooling pumps, CRAHs or CRACs, CDUs and associated auxiliaries, consistently measured for the same site boundary.
GPU/CPU chips, IT network switches and the internal server fans ordinarily included in IT energy metering. These can still affect the net change in facility electricity and are handled explicitly.
Suppose the baseline has 440 kW of measured cooling machinery serving a 2,000 kW average IT load. At $0.11/kWh and 8,000 operating hours, annual plant electricity costs 440 × 8,000 × 0.11 = $387,200. The cost allocation is $193.60 per IT kW-year. Its instantaneous cooling power ratio is 0.22 kW of cooling per kW of IT load; that ratio alone is not a standard PUE measure.
The retrofit case with a hidden fan penalty
A new plant design is projected to use 320 kW rather than 440 kW over equivalent operating conditions. That is 120 kW less cooling-plant draw. However, a new operating mode increases the sum of internal server-fan power by an estimated 20 kW. The net electrical reduction is therefore 100 kW, not 120 kW.
At an illustrative $350,000 capital cost, simple payback is 350,000 ÷ 88,000 ≈ 4.0 years before maintenance, financing, incentives and other operating changes.
The input fields are not a recommendation to use a particular cooling architecture. The example assumes a common IT demand and representative average draw in each scenario. A real investment comparison must also model peak summer performance, equipment redundancy, weather, fan control, workload mix and necessary cooling capacity at failure conditions.
Four reasons an attractive cooling number can be wrong
| Comparison error | What goes wrong | Practical correction |
|---|---|---|
| Comparing different IT loads | A lower-load month appears more efficient merely because less heat was created | Normalize results to comparable IT energy and representative operating conditions |
| Ignoring server fans | Cooling plant saves power while IT-side airflow consumes more | Track net site kWh and IT-side fan changes separately |
| Using a single PUE reading | Power and energy ratios are confused; non-cooling overhead is included | Measure annual cooling plant kWh and matched IT kWh |
| Excluding seasonal behavior | Winter economizer operation looks better than peak summer service | Use weather- and load-adjusted periods rather than one flattering day |
Cooling capacity is usually expressed in kW of heat rejected, while electric cooling draw is kW consumed by machinery. Do not mix them in the same cost ratio. Also distinguish cost per IT kW-year from cost per IT kWh: they have different units and answer different questions. In a colocation contract, neither figure should automatically be treated as a tenant tariff without agreed allocation and submetering terms.
A measurement plan that can withstand review
- Document every included meter and identify chilled-water, dry-cooling and in-room equipment shared with other loads.
- Collect at least enough data to represent variable IT demand and outdoor conditions; avoid single-day comparisons.
- Use a consistent electricity price model, including peak charges where material.
- Record whether a retrofit changes IT fan draw, water use, maintenance, reliability or available rack capacity.
- Present baseline, uncertainty and proposed measurement plan before approving payback.
Measurement and verification frameworks such as IPMVP offer structured approaches to baselines, adjustments and reporting uncertainty. Use them when the estimated savings become a contractual claim or capital authorization. The calculator provides a transparent first-pass cost model; site evidence determines whether the claimed reduction is real.
How to report savings without overclaiming
For every claimed retrofit saving, publish the baseline period, post-change period, measured IT energy, weather conditions, equipment modifications and excluded costs. Report cooling electricity in kWh as well as dollars and disclose whether the change affected server fan power. If conditions differ, apply a defensible baseline adjustment rather than simply comparing two invoices. Independent review becomes easier when the measurement method was agreed before equipment was installed, not reconstructed after a favorable month.
Sources and further reading
Primary frameworks and reference materials. Engineering decisions require site-specific validation; legal classifications require assessment of the actual use case.
- PUE measurement boundaries and interpretationThe Green Grid / Lawrence Berkeley National Laboratory
- International Performance Measurement and Verification ProtocolEfficiency Valuation Organization
- Guide to Operational Technology Security, SP 800-82 Rev. 3NIST