Exercise set
Data Center Power and Cooling Exercises
Worked engineering exercises for data center power and cooling covering IT heat load, PUE, airflow, liquid-cooling flow, UPS autonomy, redundancy, and commissioning evidence.
These exercises practise data center power and cooling calculations from an engineering point of view. The goal is not only to compute loads, flow rates, or efficiency ratios. The goal is to connect each numerical result to equipment sizing, operating margin, redundancy, commissioning evidence, and failure response.
Assume steady operation unless an exercise states otherwise. In real data centers, the final design must also consider workload ramps, power quality, harmonic current, cooling-control delay, containment leakage, water quality, maintenance bypass states, fire and leak response, sensor calibration, and the operating envelope specified by equipment manufacturers.
How to Use These Exercises
For each calculation, keep the boundary explicit:
- Define whether the boundary is a rack, data hall, cooling loop, UPS output, switchboard, or full facility.
- Separate IT load from cooling, lighting, controls, pumps, fans, and power-conversion losses.
- State whether the result is a normal operating value, design peak, failure case, or commissioning acceptance value.
- Check units before interpreting the number.
- Convert the numerical answer into an engineering decision.
The most common mistake is treating a data center as a single electrical load. A useful calculation must also show where the heat goes, how fast the system can respond, which component becomes limiting, and what evidence proves that the installed system behaves as expected.
For each result, state whether it supports capacity sizing, operating-envelope definition, redundancy claim, energy-performance assessment, commissioning acceptance, or a failure-response procedure. A data center margin is credible only when power, cooling, controls, and distribution evidence agree at the same boundary.
Exercise 1: IT Load and Heat Rejection
A data hall contains 24 racks. Each rack is planned for an average IT load of 18\ \text{kW} and a peak IT load of 26\ \text{kW}. The cooling design also includes 18\ \text{kW} of heat from lighting, controls, and local distribution losses inside the cooled boundary.
Find:
- the average IT load;
- the peak IT load;
- the peak cooling load inside the cooled boundary.
Solution
Average IT load:
Peak IT load:
Nearly all IT electrical power becomes heat inside the data hall. The peak cooling load inside the cooled boundary is therefore:
The cooling system should not be sized from the average IT load if rack deployment can reach the peak case. The average value is useful for energy estimates, but the peak value controls thermal capacity, air or liquid distribution, alarm thresholds, and failure response.
Exercise 2: Facility Power and PUE
A facility operates with an IT load of 1.20\ \text{MW}. Measured total facility power at the utility meter is 1.62\ \text{MW}.
Find the power usage effectiveness and the non-IT power demand.
Solution
Power usage effectiveness is:
The non-IT demand is:
The result means that 420\ \text{kW} is being used by cooling, power conversion, lighting, controls, pumps, fans, security, and other supporting systems at that operating point.
Engineering Comment
PUE is a boundary metric, not a thermal-design proof. A low PUE can still hide rack hot spots, poor redundancy, insufficient liquid-cooling flow, or weak commissioning evidence. Engineers should use PUE with rack temperature, coolant temperature, airflow, pressure, UPS efficiency, power quality, and failure-mode tests.
Exercise 3: Annual Energy Impact of a PUE Change
A data center has a steady average IT load of 850\ \text{kW}. An efficiency retrofit is expected to reduce annual average PUE from 1.48 to 1.32. Estimate the annual electrical energy reduction.
Solution
Facility power before retrofit:
Facility power after retrofit:
Power reduction:
Annual energy reduction:
The retrofit saves about 1.19\ \text{GWh/year} if the average IT load and average PUE values are sustained.
Engineering Comment
This screening estimate is not enough for final business approval. A defensible retrofit case should also check seasonal operation, measurement uncertainty, chiller staging, water use, maintenance risk, control stability, redundancy during transition, and whether IT load growth changes the baseline.
Exercise 4: Airflow for a Data Hall Cooling Load
A data hall has a sensible cooling load of 520\ \text{kW}. The air-cooling design uses a supply-to-return air temperature rise of 12^\circ\text{C}. Take:
Estimate the required air volume flow rate.
Solution
Use the sensible heat balance:
Rearrange:
Use \dot Q=520\ \text{kJ/s} because 1\ \text{kW}=1\ \text{kJ/s}:
The required airflow is approximately:
Engineering Comment
This value is a theoretical heat-balance airflow. Real design must include bypass air, recirculation, containment quality, fan curves, filter loading, coil approach temperature, rack inlet limits, pressure control, and failed-fan operation. A large airflow number does not guarantee correct rack inlet temperature if the air path is poorly controlled.
Exercise 5: Liquid-Cooling Flow Rate
A direct-to-chip liquid-cooling loop removes 360\ \text{kW} from high-density racks. The coolant temperature rise across the load is limited to 8^\circ\text{C}. Use an effective coolant heat capacity:
Assume coolant density is approximately:
Find the required mass flow rate and volume flow rate.
Solution
Use:
Rearrange:
Volume flow rate:
Convert to litres per minute:
Engineering Comment
The flow calculation does not complete the liquid-cooling design. The engineer must also check pressure drop, pump redundancy, manifold balancing, leak detection, materials compatibility, water quality, filtration, service isolation, condensation margin, heat-exchanger approach temperature, and safe response when one pump or coolant distribution unit is unavailable.
Exercise 6: UPS Autonomy and Usable Energy
A critical IT load is 450\ \text{kW}. The design requires 10\ \text{minutes} of battery autonomy at that load. The UPS and battery path has a combined discharge efficiency of 92\%. Only 80\% of nominal battery energy is allowed to be used to protect battery life and reserve margin.
Find the minimum nominal battery energy capacity.
Solution
Required delivered energy:
Account for discharge efficiency:
If only 80\% of nominal capacity is usable:
The nominal battery capacity should be at least about:
Engineering Comment
Battery autonomy calculations should be checked against end-of-life capacity, ambient temperature, discharge rate, battery management limits, maintenance bypass, generator start reliability, transfer sequence, and the actual load during the outage. A nominal kWh rating alone does not prove ride-through capability.
Exercise 7: N+1 Cooling Capacity Under Maintenance
A data hall has a design cooling load of 900\ \text{kW}. It uses four identical cooling units, each rated at 330\ \text{kW} under the expected supply and return conditions.
Check:
- total installed cooling capacity;
- available capacity with one unit out of service;
- whether the system meets the 900\ \text{kW} load with one unit unavailable.
Solution
Total installed capacity:
Capacity with one unit unavailable:
Margin during one-unit outage:
Percentage margin:
The system meets the nominal N+1 capacity check with a 10\% margin.
Engineering Comment
This is only a capacity-screening result. The real N+1 claim must also prove that the remaining units can deliver air or coolant to the right racks, controls remain stable, electrical feeds can support the failed-unit state, valves and dampers move correctly, and no single distribution failure removes more capacity than assumed.
Exercise 8: Commissioning Evidence for a Cooling Step Test
During commissioning, a data hall step test increases IT load from 300\ \text{kW} to 520\ \text{kW}. The measured increase in facility power is 305\ \text{kW} after cooling controls settle.
Find the incremental facility power per incremental IT power and interpret the result.
Solution
Incremental IT load:
Incremental facility power:
Incremental ratio:
For this operating step, each additional kilowatt of IT load increased facility power by about 1.39\ \text{kW}.
Engineering Comment
This ratio is not the same as annual PUE, but it is useful commissioning evidence. It shows how the facility responds to an incremental load at a specific operating point. Engineers should compare the result with expected fan, pump, chiller, economizer, UPS, and control behaviour. If the ratio is much higher than expected, likely causes include poor containment, unnecessary chiller staging, unstable control loops, high fan power, or measurement boundary error.
Review Checklist
Before accepting a data center power and cooling calculation, check:
- whether the boundary is clearly defined;
- whether load values are average, peak, diversified, or failure-case values;
- whether all units are consistent;
- whether electrical power has been translated into heat at the correct boundary;
- whether airflow or coolant flow reaches the rack, not only the plant;
- whether redundancy is proven for distribution as well as capacity;
- whether PUE is supported by temperature, flow, pressure, power-quality, and reliability evidence;
- whether maintenance bypasses, single failures, workload ramps, sensor calibration, and control-loop delays are included in acceptance evidence;
- whether commissioning step tests verify rack inlet conditions and coolant or airflow delivery, not only plant capacity;
- whether commissioning tests measure the same quantities assumed in design.
Good data center engineering turns power and cooling calculations into operating proof. A correct arithmetic result is only the first step; the design is credible when the installed facility can demonstrate the same behaviour under load, maintenance, fault, and recovery conditions.