Field Notes
Rear-door heat exchanger valve and condensate record before energization
A useful rack energization packet ties the rear-door heat exchanger tag, valve position, hose routing, dew point margin, water temperature, leak check, door swing, sensor status, photos, exceptions, and hold points together before IT load is applied.
Direct answer
Before rack energization, a rear-door heat exchanger valve position and condensate risk photo record should identify the rack, RDHx tag, door model, supply and return hose labels, isolation valve positions, balancing or control valve setting, CDU or secondary-loop source, water temperature, room dew point, dew point margin, hose routing, leak check, door swing, drip or condensate evidence, leak-detection status, sensor alarms, exceptions, witness, and energization boundary.
The record should prove that chilled or conditioned water is not being introduced in a way that can create condensation at the rack, that valves are in the intended startup position, and that any door, hose, quick connection, sensor, or access issue is visible before IT load and energized equipment make correction harder.
Use this field note as documentation guidance only. The RDHx manufacturer manual, cooling distribution design, water-quality specification, controls sequence, commissioning procedure, electrical energization plan, leak response plan, rack vendor requirements, owner standard, and site safety procedure control actual filling, valve operation, leak testing, dew point control, and energization.
Why this record fails at energization
Rear-door heat exchangers are close to energized IT gear, but their risk can look ordinary during a pre-start walk. The door is installed, hoses are connected, the rack is labeled, and the cooling loop may be ready. The missing evidence is often valve position, dew point margin, water temperature, hose clearance, leak-detection status, or proof that the door can move without stressing connections.
The weak packet says RDHx installed and no leaks. The strong packet shows each valve position, hose route, connection, drip point, dew point comparison, alarm state, access condition, and hold before the rack is energized.
Lenovo, IBM, and Vertiv rear-door heat exchanger documents all warn in their own ways that water temperature and dew point matter because uninsulated heat exchangers and hoses can condense if water is too cold for the room condition. That makes condensate risk a startup record item, not a later maintenance note.
Start with the cooling-loop basis
The first page of the record should name the approved cooling design, secondary-loop source, CDU or heat-exchanger loop, rack layout, RDHx submittal, hose kit, valve schedule, controls sequence, water-temperature setpoint, humidity or dew point monitoring source, leak-detection plan, and rack energization checklist.
Do not treat a rear-door heat exchanger as a generic chilled-water coil. Lenovo and IBM planning guidance distinguish the secondary loop from primary building chilled water because primary chilled water may be too cold and may create condensation risk. The record should show what loop is serving the rack.
ASHRAE TC 9.9 water-cooled server guidance and DOE/LBNL rear-door heat exchanger material both support the broader context: liquid cooling near IT equipment needs water-temperature, flow, leak, and commissioning evidence that is tied to the actual rack.
Photograph valve position before flow
Photograph every valve that affects the RDHx before and after the startup step: supply isolation, return isolation, balancing valve, control valve, bypass valve, manifold valve, drain valve, vent valve, and any CDU or rack-level valve that is part of the approved sequence.
Each photo should show the valve tag, open or closed position, flow direction where visible, hose label, rack tag, and enough surrounding context to prove the valve belongs to the rack being energized. A close photo of a handle is not enough if it cannot be tied to the correct rack.
The BNL chilled-door specification source includes a project example where a valve fail-safe position is called out. The actual project sequence may differ, so the record should state the intended startup position and who confirmed it.
Record dew point margin
Record room dry-bulb temperature, relative humidity or dew point, supply-water temperature, return-water temperature where available, timestamp, sensor source, and the margin between the coldest exposed water surface and the room dew point. Use the project method for calculating or reading dew point.
Lenovo water specifications state that the water inside the supply hose, return hose, and heat exchanger must be kept above the local dew point because those parts are not insulated. IBM planning guidance and Vertiv rear-door manual context say the same practical thing: avoid operating below dew point if condensation would form.
If the water temperature is below the accepted dew point margin, hold energization. Do not rely on a dry photo at one moment if the control sequence, humidity condition, or water setpoint can move into condensation territory after load is applied.
Check hose routing and door swing
Photograph hose routing at the door hinge side, rack exit, overhead or underfloor path, strain relief, bend radius, quick connections, drip points, and any abrasion or pinch risks. Open and close the rear door through the approved travel range if the commissioning plan allows it, then photograph the final resting condition.
RDHx manuals from Lenovo, IBM, and Vertiv include installation and maintenance steps that make door mounting, hose access, filling, purging, and service panels part of the installation. The field record should prove those features are not blocked by cable trays, power cords, busway drops, containment panels, or adjacent racks.
If the door can only open by stressing a hose or striking a cable bundle, do not energize the rack as if the cooling detail is finished. Hold the issue for mechanical, electrical, and rack integration teams.
Prove leak check and sensor status
The leak record should include dry-before photos, pressurized or flow-test photos, connection closeups, hose fittings, valve bodies, drain and vent points, under-rack areas, drip-tray or containment features where present, and final dry-after photos.
If the site has leak detection cable, point sensors, CDU alarms, rack sensors, or BMS alarms, record the alarm state and test status. A visual no-leak statement is weaker than a packet that shows the monitoring system was normal before energization.
Vertiv's cold-plate leak detection white paper is not a rear-door manual, but it supports the datacenter principle that liquid-cooling leak detection and intervention planning should be explicit. The rear-door packet should therefore include who responds, what alarm is expected, and what remains held.
Separate condensate from leaks
Do not call every water droplet a leak, and do not dismiss condensation as harmless. Record whether moisture appears at the hose, coil, valve, fitting, door surface, drip path, floor, or rack frame, and compare the observation to dew point and water-temperature data.
Condensation risk is controlled differently from a mechanical leak. A leak may require tightening, component replacement, isolation, or draining. Condensation may require water-temperature reset, humidity control, insulation change, control lockout, or a different startup condition.
The record should keep the two conditions separate so the correct team owns the correction.
Confirm airflow and rack loading assumptions
Record whether the rack is empty, partially loaded, fully loaded, blanked, cabled, powered off, in burn-in, or ready for production load. Rear-door performance depends on server exhaust airflow, door coil capacity, water flow, and surrounding room conditions.
The DOE/LBNL rear-door heat exchanger source points to commissioning checks such as airflow leakage, server inlet and outlet temperatures, RDHx outlet temperature, coolant flow, inlet and outlet water temperatures, dew point, and leaks. Those checks should be scaled to the project energization stage.
If the rack will be energized in phases, record which load step the RDHx evidence supports. A dry, stable condition at no IT load may not prove the final production state.
Record table
Use a compact table so mechanical, controls, electrical, IT, and commissioning teams are reviewing the same pre-energization evidence.
| Record field | What to capture | Why it matters |
|---|---|---|
| Rack and RDHx identity | Rack ID, RDHx tag, door model, loop source, commissioning step | Prevents photos from being assigned to the wrong rack |
| Valve position | Supply, return, balance, bypass, drain, vent, manifold, CDU valve state | Shows the cooling loop is in the intended startup configuration |
| Dew point margin | Room condition, dew point, water temperature, margin, timestamp | Controls condensation risk near energized IT equipment |
| Hose and door condition | Routing, strain relief, bend, quick connects, door swing, access panels | Finds mechanical stress before load is applied |
| Leak evidence | Dry-before, flow-test, dry-after photos, alarm state, response owner | Separates no-leak evidence from assumptions |
| Condensate evidence | Any moisture location, dew point comparison, control action | Keeps condensation from being misclassified |
| Exceptions | Low water temperature, blocked access, alarm fault, drip, valve unknown | Makes energization holds explicit |
| Release decision | Ready, ready with exception, held, or retest required | Defines the rack energization boundary |
Before-energization checklist
Run this checklist before IT load is applied to the rack.
- Approved RDHx model, loop source, and rack ID are in the packet.
- Supply and return hoses are labeled and photographed.
- All required valve positions are photographed and tied to rack ID.
- Room dew point and water temperature are recorded with timestamp.
- Water temperature is above the project dew point margin.
- Door swing, hose bend, strain relief, and access panel clearance are photographed.
- Leak check includes dry-before, flow-test, and dry-after evidence.
- Leak detection or alarm status is normal or exception-listed.
- Condensate and leak observations are classified separately.
- Hold points and retest owner are recorded before energization.
Weak versus strong record
Weak record: RDHx connected, valves open, no leaks. Rack ready.
Strong record: Rack R3-C14 RDHx-14 was photographed before energization with supply valve SV-R3-C14 open, return valve RV-R3-C14 open, drain valve closed, vent cap installed, and balance valve set per TAB tag. Supply water was 68.4 degrees F at 10:18 a.m.; room dew point from the white-space sensor was 57.9 degrees F. Hoses were routed through the overhead drop with no pinch at full door swing. Leak cable zone LDC-3-14 was normal, all fittings were dry after 30 minutes of flow, and the rack was held only for missing hose label replacement before final IT load.
The strong record gives the energization reviewer enough evidence to understand valve state, condensation margin, leak status, hose movement, and the single remaining exception.
Common mistakes
The most common mistake is taking a photo of the rear door without capturing the valves and water-temperature context. A closed, dry door does not prove the loop is ready for energized load.
Another mistake is assuming the building chilled-water supply is acceptable because it is available. IBM and Lenovo planning guidance warns against direct use of too-cold primary chilled water in these applications because condensation and leak exposure matter at the rack.
Other mistakes include unlabeled hoses, valve photos without rack context, no dew point timestamp, no final dry-after photo, no alarm-state record, blocked door swing, missing access panels, and unresolved drip evidence.
When to hold rack energization
Hold energization if the valve position is unknown, the loop source is not the approved secondary loop, water temperature is below the accepted dew point margin, room humidity data is missing, a hose is kinked or stressed, door swing is blocked, leak detection is in alarm, or any fitting is wet.
Also hold if supply and return hoses are reversed or unlabeled, the balancing valve has no accepted setting, a drain or vent valve is not secured, drip evidence cannot be classified, the BMS or CDU alarm state is unknown, or the rack will be loaded beyond the condition tested.
A hold should name the rack, RDHx tag, valve or sensor involved, required correction, retest evidence, and whether adjacent racks can proceed.
Owner handoff and monitoring
The owner handoff should include valve-position photos, hose routing, dew point and water-temperature snapshot, leak-check record, leak-detection zone, alarm points, response contacts, access notes, and any accepted exceptions.
If the owner will trend water temperature, room dew point, flow, differential temperature, or leak alarms, preserve the point names and normal startup values. Future operators should not have to rediscover which sensor protected the rack at energization.
Keep the record with the rack turnover packet, not only the mechanical commissioning files. The risk sits at the interface between cooling water and energized IT equipment.
Questions before energization
What is the approved water-temperature limit for this room condition? Which sensor supplies dew point? Who can change the CDU or loop setpoint? Which valves must be open, throttled, closed, or locked before energization?
What leak detection zone covers the rack? Who receives the alarm? Can the rear door swing through the service range with power and network cabling installed? Will the rack be energized at full load or in stages?
Answer those questions before the rack is powered. If a correction requires draining, purging, valve adjustment, sensor work, or cable rerouting, it is easier to handle before production load.
Compliance and safety limits
This article does not approve a cooling-loop design, set a water-temperature limit, operate valves, energize IT equipment, or replace manufacturer commissioning. It is a field-record structure for preserving valve, dew point, hose, leak, condensate, and hold evidence before rack energization.
The RDHx manufacturer manual, cooling design, controls sequence, water-quality plan, electrical energization plan, leak response plan, owner standard, and site safety procedure control the work. If those documents conflict with this checklist, use the controlling project document and record the decision.
Do not fill, drain, purge, pressurize, energize, or troubleshoot around IT racks outside the qualified team's authority. Water near energized equipment, heavy rear doors, pressure, lifting, and access constraints belong under the project safety plan.
Sources checked
- Lenovo, Water specifications for the secondary cooling loopUsed for water-temperature and dew point context for rear-door heat exchanger hoses and heat exchanger surfaces.
- Lenovo, Rear Door Heat Exchanger for 48U Rack User GuideUsed for setup, installation, filling, purging, water-temperature, and condensation-risk context.
- IBM, Planning for installation of rear door heat exchangersUsed for secondary-loop, primary chilled-water, dew point, and leak-risk planning context.
- IBM, Rear Door Heat eXchanger Planning GuideUsed for RDHx planning context around dew point, leaks, water delivery, and secondary cooling loops.
- Vertiv, Liebert DCD Rear Door Heat Exchanger User ManualUsed for RDHx installation, condensation prevention, door mounting, and piping context.
- LBNL and FEMP, Data Center Rack Cooling with Rear-door Heat ExchangerUsed for commissioning check context including coolant flow, temperatures, dew point, leaks, and airflow.
- Lenovo, ThinkSystem Rear Door Heat eXchanger V2Used for RDHx performance context around inlet temperature, flow rate, dew point, and heat load.
- IBM, Rear Door Heat eXchanger for iDataPlex RacksUsed for installation and maintenance context around filling, draining, and safe handling.
- Lenovo, Rear Door Heat eXchanger V2 Installation and Maintenance GuideUsed for installation context around dew point control, water temperature, and rack setup.
- API Heat Transfer, Rear Door Cooler Data Centers SolutionsUsed for current rear-door cooler context around rack-level heat transfer and above-dew-point operation.
- BNL, Chilled Door SpecificationsUsed for project-specification context around rear-door heat exchangers and valve fail-safe position.
- ASHRAE TC 9.9, Water-Cooled ServersUsed for liquid-cooling context around water-cooled IT equipment and facility integration.
- Vertiv, ACS Cold Plate Leak Detection and InterventionUsed for liquid-cooling leak detection and response planning context.