Support / Technical answers

How should N+1 be defined in liquid cooling?

Direct, data-backed answers to the questions that matter before and during deployment.

N+1 must identify whether pumps, power feeds, controllers, heat exchangers or complete CDUs are redundant and verify remaining flow, pressure and duty after one unit is lost.

Parallel systems also require common-header, check-valve, isolation, bypass, lead-lag and service fault-domain analysis.

Define the decision boundary

N+1 must name the redundant object and assumed failure. Two pumps do not automatically make the system N+1 if common power, controls, exchanger, headers or valves remain single points.

Engineering and selection method

Draw functional and fault-domain diagrams for pumps, feeds, controllers, sensors, exchangers, filters and common piping. Calculate remaining flow, head, duty and allowable derating time after each loss and define parallel control.

Validation, delivery and risk control

Test power removal, stopped pumps, sensor faults, communication loss and valve misposition for changeover, alarm and recovery. Treat maintenance isolation as another acceptance fault state.