Liquid cooling from China: a server component and a facility's infrastructure are different offers
Distinguish liquid-cooled server components, equipment sets and facility infrastructure before comparing Chinese suppliers.
Article language: English

In this article
A server, a rack and a whole data centre can appear in three offers under the same heading: “liquid cooling”. A buyer sees similar graphics, hears claims about efficiency and tries to compare them. One offer may concern a part inside a device, another a set of equipment, and a third work with the building's infrastructure. Unless that boundary is identified, the conversation with suppliers starts with different things being ordered.
Imagine a Polish company developing its data-centre infrastructure. It is researching Chinese manufacturers but has not yet decided what scope to entrust to an outside partner. One site presents a liquid-cooled server. Another offers a coolant distribution unit, or CDU, for heat exchange and liquid distribution. A third describes a solution covering more components. Each offer may make sense on its own. They should not be entered into one table as three interchangeable units of the same product.
Start by clarifying equipment roles, the boundaries of each offer and the work that remains with the buyer. A public industry report helps show the environment in which Chinese suppliers operate, while a manufacturer's page shows how it presents its own product. Only then can the company ask about a particular configuration. The number of components in a catalogue does not itself prove that a company will take responsibility for the whole project.
What lies between a server component and the building?
CAICT's August 2025 liquid-cooling industry report distinguishes components, IT equipment, technical services and data-centre applications. CAICT is the China Academy of Information and Communications Technology. The map reveals different points of cooperation rather than treating the whole industry as one kind of factory for complete installations.
In describing a system with cold plates, the report lists plates, pipes, connectors, liquid distribution, CDUs and external cooling equipment, among other things. A plate takes heat from an electronic component; a CDU participates in heat exchange between circuits and the distribution of liquid. This explains functions for reading an offer, not how to design or connect the parts.
First establish how far the proposal extends. Does it concern equipment for a particular server? Cooperation among several devices in a rack? A solution requiring coordination with the facility's infrastructure? A component name in a supplier enquiry should lead to its role and boundary. The general phrase “complete cooling” does not yet explain what the buyer must provide.
In our fictional data centre, the person researching the market does not select liquid parameters, temperatures or settings. They prepare material for assessment by responsible specialists. They can ask which part of the system the supplier describes and which document shows its dependencies on the other elements. That organises the contact without pretending that a market report provides design expertise.
A similar need to distinguish roles appears in China's photovoltaic value chain (in Polish). A component supplier, equipment maker and party covering a wider installation scope are not interchangeable names. The comparison concerns the structure of an offer; it does not transfer technology, requirements or conclusions about suitability between the industries.
A catalogue shows a configuration, not your facility's readiness
On the IEIT SYSTEMS i24G7 server page, the manufacturer gives separate designations for air-cooled and liquid-cooled variants. Its deployment description also mentions air-to-liquid and liquid-to-liquid CDU solutions. The manufacturer's own page therefore shows several related scopes; it does not by itself confirm that a particular offer fits a Polish facility.
Suppose the Polish company's comparison contains only the general name of this server family. A later reader may not know which variant underlies the description. Shortening the designation makes a table easier to read but removes a distinction needed for assessment. Keep the model code in the source material even if a short summary uses a clearer family name.
Nor should every visible element be combined into one assumed package. A page describing a server and mentioning a CDU does not say what an offer received by the buyer includes. The recipient needs to know whether it covers one device, several items or a specified service. An element mentioned elsewhere in the catalogue does not automatically fill a gap in the stated scope.
Separate a product description from a claim about results. A component name explains what a manufacturer offers. A claim of savings or simpler deployment requires the conditions of comparison. We do not adopt catalogue promises as a result for the Polish company. Keep them as questions for an appropriate assessment instead of inserting them into a purchase justification.
In Korea's smart-factory ecosystem (in Polish), it is similarly necessary to distinguish a product from the work of an integrator connecting components. A data centre involves a different set of devices and responsibilities. Identifying the boundary helps select contacts who can answer questions about the actual scope, rather than sending the whole enquiry to any company with a broad catalogue.
Three proposals need three different clarifications
The first hypothetical supplier offers only a cooling component. It should be able to identify the product description and intended use associated with its proposal, as well as what the buyer must supply for further assessment. Do not immediately ask it to confirm readiness of the whole facility if that is not its stated scope. A narrow offer may fit a buyer arranging the rest with other parties.

The second supplier proposes a set including a server and related devices. The question is whether the list of items matches the stated scope and what information is needed from the facility. Establish whether a demonstration on a prepared setup concerns the same configuration the buyer would receive. A demonstration can help, but a similar photograph should not replace identification of the offered set.
The third party declares a wider scope of design and commissioning. The buyer should then understand that party's role, its own tasks and the involvement of other partners. This is a different offer from buying a device. “Turnkey solution” alone does not explain which activities are included, who performs them or on what basis completion will be confirmed. These points need agreement for the particular project.
This division does not rank the three models. The Polish company may need each in a different situation. A comparison must nevertheless use the right subject and retain missing conditions. An RFQ to an Asian supplier (in Polish) can help relate answers to the same scope. It should not turn three different offers into three prices for a vaguely named unit of cooling.
Consider two different tasks for a Polish buyer. One company is preparing a new room and is still agreeing its infrastructure. The other wants to introduce a specified group of servers into an operating facility while retaining part of its infrastructure. These are assumptions in the example. The same manufacturer presentation will lead to different questions, even if the server in the photograph has the same name.
The first may need a partner whose scope includes dependencies between new parts of the solution. The second must first explain the boundaries of its existing environment. The buyer's technical team should decide which information about that environment matters to the assessment. A researcher can make sure it reaches the right party and refers to the right proposal, but should not replace it with a guess from a photograph.
Keep the conditions in the responses: what the supplier assumed, what it requested and what has not yet been assessed. If one offer was prepared for a new room, do not present it as an answer to a retrofit simply because the other price looks less favourable. Both parties must first address the same task. Only then can scope and conditions be compared on a common basis.
At this stage Aeneia Oriens can help research the Chinese environment for a specified component or service, organise parties' roles and read public materials. Start with the part of the solution the Polish company wants to examine and what it can already describe. A useful result may be a list of contacts and questions for further assessment.
Handoffs between companies are part of the solution too
Return to the fictional project. The server supplier is responsible for its product, the facility infrastructure party for its own scope, and the operator wants to understand the combined result. Even if each separately demonstrates proper operation, a question remains about the boundary between them. Who collects an ambiguity that emerges only in joint use? Without an addressee, a report may circulate among otherwise clearly described support teams.
Market research can identify whether a supplier describes only sales or also specified support after delivery. Do not add a missing service based on a courteous “we will help”. Your question should show what kind of answer the operator needs. Product research requires different information from explaining an event in an agreed configuration.
The materials passed between parties matter too. A general drawing may show the solution boundary without being enough for a technical decision-maker. An equipment list may identify items without explaining every dependency. Name the type and purpose of missing material in the market report. Appropriate specialists should decide whether the document actually suffices for the project.
A partner may demonstrate suitability on a particular setup while the Polish company plans a different use. Retain the conditions of the earlier result and name the difference. Lack of confirmation cannot be removed by changing the recipient's name in an account of a successful trial. Evidence retains the scope in which it was obtained.
Reading a laboratory's accreditation scope (in Polish) helps here. A component test report and an assessment of an entire configuration can answer different questions. Do not assume a document about one part confirms all dependencies. First establish what was tested, then decide what role the result has in assessing the offer.
A small component can need a broad context
Before the next contact, compare your own contribution with what the other party needs. A Polish company offering a component to a Chinese partner should identify where the part fits in that partner's solution. A Polish company buying a device should identify the infrastructure and scope for which it seeks a partner. In both directions, general interest in liquid cooling only opens the subject.
Compare integrating a Chinese EV charger with a Polish operator's system (in Polish). In both cases a device's public characteristic does not yet describe joint operation with another party's part of the solution. The similarity concerns the question of cooperation scope; it does not claim that the industries use the same protocols or need the same tests.
After research, retain a list of parties according to their actually described roles: component, device, solution covering several parts, or specified service. If a party appears in several places, record the basis for each identification. The next conversation then need not begin by guessing which broad company claim the recipient meant. It can address a specific offer boundary and the information each side needs.







