Ten boundaries. Three questions each. That is the turnover package.
Was it tested? Against what acceptance criteria? Where is the record? Below is the minimum we hand over for a liquid-cooled deployment, boundary by boundary. A package should answer all three for all ten.
Definition
The turnover package (turnover package · 交付资料包) is the set of records handed over with a liquid-cooling system at commissioning. In its minimum form it answers three questions for each of the ten leak points, thirty answers in all: was the boundary tested, against what acceptance criterion, and where is the record. It also carries the metering boundary drawing, fluid chemistry at fill, flow balance per branch and the CDU approach at a stated load.
Swipe sideways to see all columns.
| # | Boundary | Was it tested? | Against what? | Where is the record? |
|---|---|---|---|---|
| 01 | Cold plate joints At the server | Factory pressure / helium test per plate | Manufacturer spec, traceable to serial | Supplier FAT certificate, indexed by rack position |
| 02 | Quick disconnects At the server | Leak test after every mate/de-mate during install | Zero visible weep at test pressure, held time stated | Connection log: date, technician, QD serial, result |
| 03 | Hose crimps At the server | Crimp dimensional check, sample pull test | Assembler process spec: crimp diameter, concentricity | Batch record with crimp-tool calibration |
| 04 | Manifold branches In the rack | Manifold pressure test as an assembly | Rated pressure × factor, hold time, decay limit | Rack integrator test sheet |
| 05 | Elastomeric seals In the rack | Material certification, fluid compatibility statement | Named elastomer grade vs named fluid, temperature range | Material cert file, cross-referenced to BOM |
| 06 | Threaded, compression and adapter fittings In the rack | Torque verification, thread sealant record | Torque table by size and material | Fitting log with torque wrench calibration |
| 07 | Internal boundaries In the CDU | CDU FAT: pump seal, HX gasket, filter housing | Manufacturer FAT protocol | CDU FAT report with serial |
| 08 | Field welds and hot work Between the CDU and the facility | Weld inspection, flush, passivation, sample | Weld procedure spec; cleanliness class; passivation confirmation | Weld map, flush log, lab sample result |
| 09 | Balancing and isolation valves Between the CDU and the facility | Stem and body leak check under operating pressure | Zero weep, valve position recorded | Valve schedule with as-left positions |
| 10 | Fill, drain, vent and sample ports Between the CDU and the facility | Cap and plug verification after every use | All ports capped, valves closed, tagged | Port log; last-disturbed date per port |
Indicative structure. Test pressures, hold times and cleanliness classes are set per project in the acceptance criteria and are not published here.
Beyond the joints: the system-level records
The ten-boundary table covers leak risk. A complete package also carries the records that make the system's performance defensible later:
- IT power and facility power, metered separately, with the metering boundary drawn
- Supply and return temperature with calibrated flow on each loop boundary
- CDU approach at rated load, with the fouling allowance stated
- Make-up and blowdown as separate water streams where evaporative rejection is used
- Local dry-bulb and wet-bulb, from a station you can name
- Delivered heat, where reuse exists: flow, supply and return, contract-grade meter
- Equipment staging, bypass position and maintenance windows, as an event log
- Tested compute-and-liquid isolation sequence, with the test date
None of that is expensive at design time. All of it is close to impossible to reconstruct afterwards.
Questions this page answers
What should a liquid-cooling turnover package contain?
For each of the ten leak points: the test that was done, the acceptance criterion it was judged against, and where the record lives. Plus the single-line diagram with the metering boundary signed, fluid chemistry at fill, flow balance per branch, the CDU approach at a stated load, and the connection log closed out for every disturbance since fill. Self-check your package →
How is a turnover package scored?
Three questions for each of ten boundaries gives a maximum of 30 points. Count only what could be handed to an auditor today, not what is believed to have been done. A boundary that was tested but has no retrievable record scores one, not three. Turnover self-check tool →
What if a boundary was tested but the record is missing?
Treat it as untested for acceptance purposes and re-test before handover if the boundary can still be isolated; if it cannot, record the gap explicitly in the package so the operator's service-life clock starts from a known state rather than an assumed one. How the acceptance criteria are written →