Server and board
Form factor, height, motherboard and controlled revision.
Server Liquid Cooling Project Input Checklist
Prepare a server cooling inquiry with the hardware, heat load, chassis space, coolant connections and expected quantity. Use this checklist to organize what is known and highlight details that still need discussion.
Start the ChecklistONLINE PROJECT CHECKLIST
Server Module Review
The Minimum Information for an Initial Review
Start with the four groups below. Photos and sketches are useful for an initial discussion; final dimensions and fit require the relevant drawings.
Processors and load
CPU/GPU model, quantity, sustained/peak/concurrent workload.
Chassis and fluid
Available space, routing, connections and external-loop owner.
Testing and timing
Required tests, quantities, project stage and target dates.
Platform, Heat-Source and Chassis Inputs
Accurate platform identification prevents a module from being developed around the wrong board, socket, processor or service space.
- Server form factor, rack height and complete configuration
- Motherboard, processor/socket and GPU/PCB revision
- Heat-source quantity, sustained/peak/concurrent workload
- Allowed temperatures, ambient and performance objective
- 3D assembly, 2D interface drawing and keep-out zones
- Mounting, adjacent components and residual airflow
- Tube route, bend space, connections and support
- Installation/removal sequence and required tools
- Maintenance access and leak-impact area
- Transport orientation and service procedure
Coolant, Connections and External Equipment
For an internal closed-loop module, identify the radiator space, airflow and operating environment. If the module connects to an external loop, include the coolant, inlet temperature, flow and connection requirements below. Mark details that are still to be confirmed.
| Input | Record | Owner |
|---|---|---|
| Coolant and material compatibility | Type, concentration/condition and applicable restrictions | Customer / shared specification |
| Inlet condition | Temperature range and environmental/condensation boundary | System owner |
| Hydraulic condition | Target flow or pressure range and pressure-drop budget | Shared engineering |
| Connections and routing | Type, location, orientation and service process | Defined interface owner |
| Pump / radiator / CDU / facility | Included, customer-provided or third-party | Written project boundary |
| Monitoring and response | Sensors, thresholds, actions and system safety owner | Customer/system owner |
Testing, Quantity and Quotation Requirements
State the tests and pass criteria alongside the components, quantities and delivery schedule you need quoted.
| Validation field | Define |
|---|---|
| Question | What decision must the test support? |
| Condition | Load, duration, environment, coolant, flow and controls |
| Sample | Configuration, quantity and revision |
| Acceptance | Criterion, record and disposition owner |
- Prototype, pilot and production quantity
- Target review, sample and release milestones
- Customer-provided and supplier-provided items
- Tooling, reports, labels and packaging
- NDA, file control and communication route
- Assumptions, exclusions and change/re-quote rules
Check the Brief Before Sending It
Use 0 for missing information, 1 for partial information and 2 for confirmed information in each group. This measures brief completeness only; feasibility, price and timing still need review.
Can photos replace a 3D model for an initial review?
Photos and layout sketches can support an initial discussion when controlled CAD is not yet available. They cannot establish final dimensions, interference, mounting or release geometry, so controlled files are still required before final design.
How should a server thermal target be stated?
State the real processor configuration and workload, duration, ambient and coolant inlet conditions, flow or pressure condition, controls, measurement points, allowed temperatures and the acceptance rule.
What if rack or facility conditions are not finalized?
Record the current assumptions and identify their owner. ThermalBro can perform an initial module-boundary review, but final flow, heat-rejection and system validation decisions remain open until the external conditions are controlled.
Can an NDA be signed before file transfer?
An NDA can be discussed before confidential platform files or drawings are transferred. The project parties, information covered and permitted use are confirmed in the agreement.
Method sources: Open Compute Project Cold Plate Cooling and approved ThermalBro product records. This checklist prepares inputs; it does not guarantee feasibility, quotation or performance.
Send the Brief for a Server Module Review
Attach the available board and chassis files, describe the cooling arrangement and list your open questions. We can begin with an incomplete brief.