In brief
Cooling commissioning verifies installation quality, fluid cleanliness, design flow and temperature, and performance under load and fault conditions. Agreed acceptance criteria, recorded tests and baseline readings make handover auditable.
A cooling system remains a design until it is started up. Commissioning is the stage where it becomes clear whether the design works, whether the installation follows it, and whether the system holds together when something fails. If that does not become clear during commissioning, it becomes clear in production.
In data center projects commissioning is also where two ways of working collide. An international owner brings commissioning levels L1 to L5 and an integrated systems test, while the Finnish contractor works to the established quality assurance practice for building services. Both describe the same thing in different words, and the difference in vocabulary causes more confusion on a project than the technical work does. The wider picture is in our complete guide to data center cooling.
What a buyer should provide
Share the phasing plan, P&ID, OEM fill and flush instructions, test loads, acceptance criteria and interface responsibilities. Finkova can agree the practical tests and handover records with the owner and other suppliers.
Commissioning levels and their Finnish equivalents
L1: design and factory equipment checks before delivery.
L2: receipt and installation checks on site.
L3: pre-functional checks including pressure testing, flushing and contractor self-checks.
L4: system-level functional and controls tests.
L5: integrated systems test including relevant fault and power-transfer scenarios.
These levels do not map perfectly to Finnish contractual duties. Agree a project-specific test and sign-off matrix.
What matters is not which vocabulary is used, but that it is agreed once which one applies and who signs off each stage.
What liquid cooling adds to commissioning
A liquid-cooled hall brings stages that an air-cooled one does not have at all. They are the same stages known from process industry, and they have to be done in the right order.
Pressure testing and leak verification come before any equipment is connected. A leak is cheap to fix in an empty loop and expensive to fix under the servers.
Flushing and verification of cleanliness is the most important work in this phase. The loop is flushed and its cleanliness measured before it is connected to the cold plates. The procedure and the fluid specification are covered in the article on liquid cooling water chemistry, filtration and material compatibility.
Filling and air removal are done with the specified fluid. Air removal is easy to do carelessly, and the air left behind shows up later as unstable flow measurement and poor heat transfer.
Loop balancing and flow verification confirm that every rack row receives its design flow. This is established by measurement, not by calculation. The methods are covered in the article on flow and energy metering in data center cooling loops.
Control testing against load steps shows whether the supply temperature holds its setpoint when load changes quickly. In AI compute those changes are faster than in a conventional hall.
Fault scenario testing is the reason the whole exercise exists. Pump failure, CDU failure, power supply transfer and standby generator start are tested for real, not on paper.
The handover baseline
At handover, the values against which the site’s entire later life is compared are measured and documented. Without them every later measurement gives a value but not a change, and any discussion of performance becomes an exchange of opinions.
The baseline should include at least:
- Record loop flows, differential pressures, temperatures and temperature differences.
- Record energy meter readings and the measurement boundaries.
- Record vibration baselines, fluid analysis and clean-filter pressure drops.
- Record alarm limits, protection settings and accepted test results.
Of these, vibration levels and fluid analysis are the ones most often skipped, because they do not belong to a traditional building services handover package. Both are exactly what is needed at the first suspicion of a fault.
The handover documentation
Handover documentation is what later warranty and liability discussions rest on. In a data center it includes, alongside the usual building services package, the documentation specific to liquid cooling: the fluid specification, flushing and filling records, cleanliness verification results, the approved materials list and the CDU settings.
The practical requirement is that this material is available to the maintenance team, not merely archived. A materials list that sits in the client’s folder but not in the service engineer’s hands does not prevent the wrong seal being fitted.
Common problems
Commissioning gets squeezed at the end of the schedule. This is by far the most common problem. When installation runs late, commissioning is cut, because it comes last. The cut lands almost invariably on flushing and fault scenario testing, which are precisely the stages whose cost surfaces only in production.
Responsibilities are unclear. Who approves which stage, who takes the measurements, and whose sign-off allows the next stage to begin. These are agreed before commissioning starts, not during it. Scope splits are covered in more detail in the article on TCS and FWS: data center cooling loop architecture and scope splits.
Fault scenarios are only partly tested. A single pump failure gets tested, but a simultaneous power transfer and cooling load step does not. That combination is what takes a site down in production.
The baseline is never measured. The cheapest stage there is, skipped because it appears to produce nothing at the time.
Two vocabularies run in parallel. When one party talks about L4 and the other about functional tests, both can believe the stage is complete.
Finkova’s scope and next step
Finkova installs and commissions data center cooling in the Nordics, with instrumentation and lifecycle support. The work scope, OEM requirements and acceptance criteria are agreed for each project.
Contact Finkova with the project inputs above to discuss the relevant installation, testing and handover interfaces. See the Finkova delivery scope for the practical work package.
Frequently asked questions
What are commissioning levels L1 to L5?
They are internationally used commissioning stages. L1 covers factory testing, L2 site receipt and installation inspection, L3 pre-functional checks and flushing, L4 system-by-system functional testing, and L5 an integrated systems test across the whole site.
How do commissioning levels map to Finnish practice?
Finnish building services quality assurance has its own vocabulary: equipment approval, installation inspections, the contractor’s functional checks and self-inspection, the client’s functional tests, and the integrated test run with load testing. The correspondence is not exact, so the vocabulary is best agreed at project start.
What is an integrated systems test?
An integrated systems test checks the systems working together rather than separately. It is the L5 level of commissioning. In a data center it includes testing power supply transfers and standby generator starts together with the cooling.
What does liquid cooling add to commissioning?
Pressure testing and leak verification before equipment is connected, flushing and cleanliness verification, filling and air removal, loop balancing and flow verification, control testing against load steps, and fault scenario testing. An air-cooled hall has none of these stages.
What should be measured at handover?
At minimum: flows and differential pressures per loop, temperatures and temperature differences, energy meter readings and measurement boundaries, vibration levels of rotating machinery, fluid analysis results, clean filter differential pressures, and alarm limits and protection settings. All later performance is judged against these.
What goes into data center handover documentation?
Alongside the usual building services package: the fluid specification, flushing and filling records, cleanliness verification results, the approved materials list and the CDU settings. The documentation must be available to the maintenance team, not merely archived.
Why does commissioning get cut on data center projects?
Because it comes last, and when installation runs late, it is what gets trimmed. The cut almost always lands on flushing and fault scenario testing, which are exactly the stages whose cost surfaces only in production.
Which fault scenarios should be tested at commissioning?
At minimum pump failure, CDU failure, power supply transfer and standby generator start. Combinations are worth testing too, such as a power transfer during a cooling load step. Combinations are what take sites down in production, and they are the ones most often left untested.
Why is flushing done before the cold plates are connected?
Because weld scale, swarf and gasket debris from installation otherwise end up directly in the cold plate channels, where they cannot be removed. Flushing is done on the empty loop and cleanliness is verified by measurement. It is the single most important quality step in a liquid cooling project.
Who signs off the commissioning stages?
This has to be agreed before commissioning begins. Unclear responsibility is a common problem: who takes the measurements, whose sign-off allows the next stage, and what each party means by a stage. When one side talks about L4 and the other about functional tests, both can believe a stage is complete.
