Saved only in this browser. No account or cross-device sync.
A developer buys a cooling system. A server supplier defines the conditions its equipment needs. A contractor installs the pipework. An operator inherits the result. The project can have a clear supplier for every component while leaving important decisions between those suppliers unresolved.
Consider a hypothetical rack that develops an abnormal pressure drop after installation. The first useful question is how the team will establish what changed: the delivered assembly, the site connection, the fluid condition, the control settings or the operating load. Without agreed records and escalation authority, a technical investigation can turn into a dispute about where one scope ended and another began.
That is why liquid-cooling procurement should include an explicit responsibility map alongside the equipment schedule.
Draw the operating boundary
OCP's ACS cold-plate requirements document distinguishes the technology cooling system from the facility system and addresses topics including component selection, sensing and leak response. It is a useful foundational reference, but this particular revision dates to 2019; it should not be mistaken for a newly issued requirement. OCP ACS reference
For a specific project, mark the boundary on the actual system drawing. Identify who supplies, connects, cleans, fills, tests and maintains each section. Record who sets the operating limits and who can approve a change. The division of responsibility should follow the installed configuration and contract, rather than an assumption that a CDU automatically resolves every interface.
The most revealing procurement question is simple: if two suppliers' requirements conflict at this connection, who must resolve the conflict before installation proceeds?
Preserve evidence through delivery
OCP's modular technology cooling white paper, revised in August 2025, discusses repeatable delivery, maintainability and preparation of liquid distribution systems. Its scope reaches beyond selecting individual components. OCP modular TCS guidance
Watts & Workloads proposes a project-specific handover record at each transfer of custody. It would identify the assembly, its approved configuration, the work completed, the evidence supplied and any outstanding exception. Factory records should remain traceable when a module arrives on site, is connected and enters service.
The record should also state what could invalidate an earlier result. Opening an assembly, replacing a material or changing a fluid may require further review or testing under the project's approved procedures. Those decisions belong with the responsible engineers and equipment suppliers. A generic checklist cannot set their technical limits.
Agree on response before the first alarm
Responsibility also needs to survive an operating incident. Who receives the alarm? Who can isolate equipment? Who decides whether production can resume? Who preserves the evidence needed for a supplier investigation?
These questions should be resolved with the operator before handover. A named escalation contact is useful only if the contact has the authority, access and response obligation needed for the situation. The acceptance record should make unresolved restrictions visible to the people running the facility.
For international deployments, including projects linking Chinese suppliers with overseas developers and operators, the same discipline should extend to document revisions, units, language, local service coverage and approved substitutions. Translating a specification does not establish that both parties accepted the same scope.
Make a China-to-overseas handoff explicit
For a Chinese equipment supplier and an overseas developer or operator, the practical question is what evidence must travel with the equipment and who takes responsibility after it arrives. The map below is a proposed discussion tool, not a report of a completed project or a statement that any supplier has been qualified.
| Handoff | Decision to settle | Evidence and owner to name |
|---|---|---|
| Manufacturer to integrator | Which exact configuration, document revision and substitutions are accepted? | Configuration record, approved interface data and test records; a named technical approver on each side |
| Factory to overseas site | Who controls preservation, storage, installation and the release for site work? | Shipping/storage instructions, inspection records and site acceptance responsibility; qualified local parties determine applicable requirements |
| Integrator to operator | Who proves the assembled cooling loop meets this project's approved conditions? | Site-specific commissioning plan, exception list, operating training and the person authorized to accept the result |
| Supplier to local service team | Who investigates a fault and how do warranty, spares and escalation work across the boundary? | Documented service scope, exclusions, local contacts, access and replacement arrangements |
Ask each party to identify the gap it can actually close. Equipment supply, integration, local service and joint development are different roles. An initial partnership discussion should name the proposed role and remaining evidence rather than imply that an equipment quotation includes overseas delivery capability.
Ask for the missing decision
The upcoming OCP program includes a Vertiv discussion of modular cooling delivery and another on computing-load commissioning. These are scheduled discussions, not evidence that a new industry acceptance regime already exists. Vertiv's 2026 program
The useful outcome of a supplier meeting is therefore a specific decision: which boundary is unresolved, what evidence will close it and who must sign off? That gives developers, operators and suppliers a shared basis for the next step. For capital providers reviewing delivery progress, it also makes the remaining technical dependencies easier to understand without confusing equipment arrival with operational readiness.
Source-linked reporting and an editorial framework for project discussions. Technical limits and acceptance procedures belong to the responsible project teams. Event agendas and proposal status can change.
About · Editorial standards · Send a correction or questionFor Chinese readers: 智算通鉴 · 中文相关分析. This is related coverage, not a word-for-word translation.