Treat RDHx adoption as a verification and acceptance exercise: performance depends on your water temperatures, available flow, airflow integrity, and dew point margin—not a single brochure number.
For existing chilled-water plants, the safest integration path is usually a clear boundary between facility water and the rack loop (often via a CDU/heat exchanger), plus a commissioning plan that proves stability under realistic load changes.
Your SLA risk is less about “can it cool?” and more about how the system behaves during maintenance, alarms, and failures (single points of failure, electrical dependencies for pumps/fans/controls, and what “concurrently maintainable” means in your environment).
If you want operations to trust the system, require a BMS/DCIM point schedule (temps/flow/DP/leaks/alarms) and acceptance evidence (trend logs + functional tests) as part of the handover.
Verdict (decision-stage)
If you already operate a chilled-water plant with defined redundancy (N+1 or 2N), RDHx can be a practical way to support higher rack densities without rebuilding the entire room-level air system—but only if you confirm four items up front:
Capacity at your real boundary conditions (supply water temperature, flow limits, dew point margin, and rack airflow integrity).
A plant-to-rack interface architecture that matches your maintainability expectations (what can be isolated, drained, repaired, and restarted—without breaking your SLA).
A commissioning plan with measurable acceptance criteria, not a “turn it on and see.”
A controls/telemetry package that makes alarms actionable and trending usable in both BMS and DCIM.
If you can’t meet (2) and (3)—for example, you cannot tolerate any new single point of failure in a row/aisle, or you cannot secure maintenance windows for phased rollout—RDHx may still be viable, but your design will need to be more conservative (smaller deployment zones, more isolation, more redundancy, or a different cooling approach).
Who RDHx is (and isn’t) a good fit for
RDHx is a strong fit when you:
Need a retrofit-friendly path for mixed-density halls and want a rack-by-rack deployment option.
Want to move a meaningful portion of heat to water while keeping room systems for residual loads and humidity control.
Can enforce airflow hygiene (blanking panels, sealing, containment discipline).
RDHx is a weaker fit when you:
Need sustained ultra-high density everywhere and your roadmap strongly favors direct-to-chip for the majority of racks.
Can’t support liquid distribution practices (leak detection, isolation strategy, drains/vents, maintenance procedures).
Have tight dew point constraints with limited ability to control humidity and water temperature boundaries.
For a practical explanation of why RDHx capacity behaves like a curve and what to validate at your site, use Coolnetpower’s guide: Coolnetpower’s explanation of RDHx capacity as a curve (2026).
1) RDHx integration chilled water: what you must confirm at your boundary
A rear door heat exchanger is simple in concept—water cools a coil, the coil cools rack exhaust—but the decision depends on site variables.
Key Takeaway: Don’t approve RDHx on “kW per rack.” Approve it on “kW per rack at our supply water temperature, at our max flow per door, with our airflow integrity, while staying safely above dew point.”
The non-negotiables
Supply water temperature and dew point margin: your controls need a defined condensation-avoidance strategy (setpoint rules + alarms) when humidity and plant modes change seasonally.
Flow per door (verified): you need to know whether the plant and distribution can deliver stable flow per rack/row.
Airflow integrity: bypass air and rack leakage reduce effective heat capture.
Load volatility: a system that looks fine at steady state may behave differently under rapid load ramps.
A procurement-ready “confirm first” table
What to confirm | Why it matters | Evidence to request | Who owns it |
|---|---|---|---|
Max rack heat load at your operating SWT/RWT | Capacity is a curve; boundary conditions drive reality | Sizing worksheet + test plan; vendor capacity curves tied to your inputs | Thermal engineering + vendor |
Flow and ΔP limits at the row/rack | Flow shortfalls become hot spots; excessive ΔP can complicate balancing | Row hydraulic model; balancing procedure; flow meter locations | Facilities + commissioning agent |
Dew point control approach | Condensation risk is an SLA risk | Sequence of operations (SOO), dew point overrides, alarm thresholds | Controls + facilities |
Containment/airflow hygiene standard | Poor airflow reduces effectiveness and predictability | Rack standards (blanking, sealing) + inspection checklist | Data hall ops |
“Out of service” behavior | Maintenance/failures must not cascade | Failure mode review; isolation boundaries; rollback steps | Facilities + ops |
2) Integration architecture: rear door heat exchanger chilled water tie-in
Most SLA issues come from ambiguous boundaries.
Most SLA issues come from ambiguous boundaries. Before you argue about kW, define the thermal and operational boundary between:
Facility chilled-water plant (primary loop)
Plant interface equipment (often CDU/heat exchanger / secondary loop)
Row distribution (headers/manifolds)
Rack doors and local hardware
A common pattern is facility CHW feeding a CDU/heat exchanger, then a secondary loop serves the racks. This helps with hydraulic decoupling, metering, and controls (especially dew point management), and it simplifies isolation for phased rollouts.
Redundancy and maintainability: use “close-coupled cooling” rules of thumb
Close-coupled systems (including RDHx) introduce dependencies that classic room-based cooling didn’t. Uptime Institute’s reliability guidance is useful here because it forces the right questions: can a component be taken out of service without impacting the critical environment, and do failures isolate cleanly?
Use this as a design review lens:
Is any single CDU/loop serving more than the amount of equipment you can afford to lose during maintenance?
Are pumps, fans (if active doors), controls, and valves powered and fed in a way that preserves your redundancy intent?
What happens to airflow when an RDHx door is removed from service?
A readable starting point is Uptime Institute’s close-coupled cooling reliability guidance, especially its definitions of concurrently maintainable vs fault tolerant and its notes on how close-coupled cooling changes failure impact.
3) RDHx commissioning checklist: what “done” looks like (and what evidence ops will accept)
For decision-stage buyers, commissioning isn’t a formality—it’s the mechanism that protects SLAs.
Commissioning phases (high level)
Design review and points list freeze
Lock the point schedule, alarm philosophy, and trend requirements.
Pre-functional checks (dry)
Verify installation, labeling, valve positions, sensor placement, and access clearances.
Hydronic integrity and cleanliness
Flush/clean; pressure/leak test; document results.
Controls point-to-point + alarm tests
Prove every critical sensor and alarm is mapped correctly and actionable.
Thermal functional testing under controlled load
Validate temperatures, flow, DP, and response to load changes.
Operational readiness handover
Train operators; hand over documentation; define maintenance windows and escalation.
Coolnetpower’s RDHx commissioning and instrumentation framing is summarized in its FAQ: RDHx PUE FAQ and commissioning instrumentation checklist (2026).
Acceptance deliverables checklist (the pack procurement should request)
Deliverable | What it should include | Why it matters |
|---|---|---|
As-builts and single-lines | P&IDs, valve schedules, sensor locations, tag map | Makes future maintenance safe and predictable |
Sequence of operations (SOO) | Dew point logic, valve modulation, alarms, fail-safes | Prevents condensation and control surprises |
Point schedule | Point name, units, protocol, alarm, trend interval | Enables BMS/DCIM integration without guesswork |
Test evidence | Pressure/leak tests, point-to-point signoffs, alarm tests | Reduces handoff disputes |
Thermal test report | Boundary conditions, loads, temperatures, flow, ΔP | Proves performance at realistic conditions |
O&M manual + training | Procedures, spares list, maintenance intervals | Prevents “tribal knowledge” ops risk |
SLA/support appendix | response times, dispatch rules, escalation, exclusions | Aligns expectations before a real incident |
4) RDHx BMS integration and RDHx DCIM integration: a points list ops can use
The fastest way to lose trust is to integrate “just enough” points to say it’s connected—without trending, alarms, or clear thresholds.
Recommended minimum telemetry (start here)
Water supply/return temperature (loop and/or door groups)
Flow rate (loop/branch)
Differential pressure (loop/branch)
Valve command/status (where modulating)
Pump run/fail and duty/standby state
Leak detection status (zones)
Dew point / humidity (where condensation risk exists)
Communications fault and controller health
For a practical separation of responsibilities—what belongs in BMS vs what DCIM adds on top—see Modius on DCIM vs BMS responsibilities (2023).
Protocol expectations (typical)
BMS: BACnet and Modbus are common in mechanical integration environments.
DCIM: SNMP is often used for status/telemetry ingestion, with REST APIs increasingly common depending on stack.
(Exact protocol selection should match your existing standards and cybersecurity policy.)
Commissioning tests for integration (don’t skip)
Alarm rationalization: every alarm has an owner and an action.
Trend validation: confirm sampling intervals and that time-series data is reliable.
Failure simulation: comms loss, low flow, abnormal ΔP, dew point risk.
For a broader integration checklist and decision-stage guidance, you can reference Coolnetpower’s internal guide: DCIM/BMS integration decision-stage guide (2026).
5) Liquid cooling retrofit SLA + compliance pack: what to write into the SOW
If you want RDHx to “fit” your SLAs, treat the commercial package as part of the engineering scope.
SLA clauses that reduce operational risk
Include (at minimum):
Response SLAs: acknowledge, remote triage, onsite dispatch, and restoration targets.
Change-control rules: notification lead times, maintenance windows, rollback conditions.
Spares strategy: which components are onsite vs vendor-stocked; restock lead times.
Acceptance criteria: what tests define go-live and what evidence must be delivered.
Ownership boundaries: where facility water ends and vendor scope begins (and who owns sensors and alarms).
Compliance and governance deliverables (audit-ready)
For enterprise teams, procurement often needs a pack that can be filed and reused:
Submittals and as-builts
Sequences of operation
Commissioning and test reports
O&M manuals, training records
Risk register and maintenance SOPs
Metering/telemetry definitions for reporting
Coolnetpower assets to request for your evaluation
If you’re building an internal approval package, start with:
The Coolnetpower brochure: Coolnet Hyper-Cool Liquid Cooling Series brochure (PDF)
A commissioning checklist + points list aligned to your BMS/DCIM standards
A sample SOW appendix covering acceptance tests, documentation deliverables, and support SLAs
FAQ
Can we integrate RDHx into an existing chilled-water plant without a major shutdown?
Usually, yes—if you plan a phased rollout with clear isolation boundaries and maintenance windows. The more your design supports isolation, draining, and rollback, the smaller your operational risk.
Do we need a CDU/secondary loop, or can we connect RDHx directly to facility chilled water?
Many designs prefer a clear plant-to-rack boundary (often via a CDU/heat exchanger) for hydraulic decoupling, controls stability, and metering. Direct connection can work, but it tends to demand tighter governance around dew point control, balancing, and maintainability.
How do we prevent condensation risk?
You need a defined dew point strategy: measure humidity/dew point where it matters, keep supply water temperature above dew point with margin, and prove alarm and fail-safe behavior during commissioning.
What’s the minimum BMS/DCIM integration we should require?
At minimum: supply/return temps, flow, differential pressure, leak detection, pump status, and controller health—plus trending and alarm testing. A points list without commissioning tests is usually not enough.
How do we define acceptance criteria for RDHx retrofits?
Define boundary conditions (water temperatures, airflow assumptions, load profiles), then require evidence: pressure/leak tests, point-to-point tests, alarm tests, and thermal test results with trend logs.
What SLA terms matter most for liquid cooling retrofits?
Response/dispatch times, maintenance window rules, spares commitments, escalation paths, and clear scope boundaries. If you can’t isolate and restore quickly, you’re exposed.
Next steps
If you want a procurement-ready package, request:
A commissioning + acceptance checklist (including a BMS/DCIM point schedule and test evidence requirements).
A sample SOW appendix covering scope boundaries, documentation deliverables, and support SLAs.
You can use the internal reference set above (capacity, commissioning instrumentation, retrofit sequencing, and integration guidance) to align stakeholders before you sign off.
