Data Center CFD Analysis and Thermal Simulation

Data center CFD analysis is the numerical verification, with computational fluid dynamics, of cooling systems and airflow management (hot and cold aisle arrangement, bypass and recirculation, underfloor distribution), of grey space thermal safety and of transient events such as a grid outage. We explain the underlying concepts, cooling architectures, air conditioning, the temperature and humidity envelope, condensation control, redundancy and PUE, in our data center cooling and airflow management guide; this page describes the service scope, the scenario set and the deliverables.

Data centers are no longer defined only by uptime and PUE. The real difference shows up in how long they keep operating under stress: power loss, extreme heat, wind-driven recirculation, and future climate conditions that exceed today’s design assumptions. At Alkazar we design and evaluate data centers as physical systems exposed to a changing climate, bringing together engineering precision, regulatory compliance and financial risk intelligence in one flow, from CFD-validated airflow to forward-looking climate resilience metrics.

In short: we deliver end-to-end CFD and thermal safety analytics for hyperscale data centers, from external airflow to white space cooling, grey space thermal safety and transient resilience. Boundary conditions are calibrated with site-specific climate data, the solver is chosen from the client’s approved software list, and the result is delivered in a decision-ready format.

Two minutes on how we use CFD and site climate data in data center design. Schematic animation, not a simulation result.

Gulf Site Design Conditions cards

Dubai, Riyadh, Doha. Design temperatures computed from 30 years of station data and carried to the site. Two pages each. Free download.

Download the Gulf design conditions cards

What problem are we solving?

Behind a design that looks “compliant” on paper, the same pattern of gaps tends to surface once the facility is operating:

  • Cooling systems sized for historical weather, not future extremes
  • Bypass and recirculation risks invisible in 2D design tools
  • Undefined system behaviour during grid outages and transient events
  • Investment decisions made without quantified climate exposure

We turn these unknowns into measurable, decision-ready outputs.

Four CFD services

We organise data center CFD work into four service lines. Each has its own scenario group (numbered in the Scenario Library below) and can be commissioned on its own or as part of an integrated package.

1. External Flow & Façade (E)

A meaningful share of cooling performance is lost outside the building. By modelling building geometry and rooftop layout, the exhaust behaviour of generators, dry-coolers, chillers and IEC units, the prevailing wind directions and site-specific meteorology together, external flow CFD shows whether generator exhaust re-enters the fresh air intake, whether the condenser is ingesting its own hot air, and what wind load the façade and roof equipment are exposed to.

  • Prevailing and worst-case wind directions
  • Exhaust plume dispersion and re-ingestion ratio
  • Contaminant concentration at intake louvres
  • Façade/roof wind loading (VDI 3783-12)
  • Pedestrian-level comfort mapping

We cover the method and example outputs for this service on a dedicated page: Data Center Exhaust Dispersion Analysis.

2. White Space / Data Hall (I1–I3)

We model IT halls with high-resolution CFD: rack-level airflow and temperature uniformity, CRAH/CRAC/IEC/In-Row system interactions, LV switchboards, and verification of N, N+1 and N+2 redundancy scenarios.

  • Full-load normal operation baseline
  • AHU failure (N+1 test) and chiller/CHW-loop failure
  • Rack inlet temperature (SIT) tracking, max 35/40°C
  • Layout optimisation iterations
How underfloor equipment layout affects rack airflow distribution
Underfloor equipment and the resulting disruption in airflow distribution can restrict adequate air circulation for some cabinets.

Outcome: verified thermal compliance with hidden hot-spots eliminated, under both steady-state and failure conditions.

3. Grey Space / Electrical Rooms (I4–I5)

Thermal safety in LV switchboard, UPS, battery, transformer and chiller rooms is just as critical as in the white space; a temperature peak in these volumes directly shortens equipment life. The summer peak load (ASHRAE design day + full load) and the battery-room thermal safety envelope are the focus of this service.

  • Summer peak combination and ventilation fan failure scenario
  • Battery room 15–30°C envelope
  • Louvre/vent airflow adequacy
  • Manufacturer-specific equipment tolerances

4. Transient / Resilience (T1)

A steady-state analysis shows the equilibrium reached at the design point, but the critical moment is the transition. Using time-dependent (transient) CFD we simulate grid outages, compressor shutdown/restart sequences, fan-only operation windows, and the full generator failure chain (utility fail → three restart attempts → catcher generator).

Transient Resilience Window: the exact duration during which rack surface temperatures remain within SLA limits (e.g. ≤27°C) after a power loss. This turns resilience from an assumption into a measurable performance indicator.

  • Three-attempt restart rule
  • UPS-supported fan + CHW pump behaviour
  • Thermal Energy Storage (TES) effect
  • Continuous-cooling exemption assessment
  • Conjugate Heat Transfer (CHT) modelling

Five airflow problems, before and after

Schematic animations of five problems we solve with CFD, each shown before and after the design change.

Exhaust re-ingestion in the building wake

When wind rolls over the roof, generator exhaust can be pulled back into the wake behind the building and reach the cooling intake. Moving the intake out of the wake or raising the stack takes the plume clear of the recirculation zone.

Schematic illustration. Colours show cooler and warmer air qualitatively; this is not a simulation result.

Bypass and hot-air recirculation in the data hall

Without containment, part of the supply air returns to the cooling unit without passing through the racks, while warm exhaust curls around the row ends into the cold aisle. Aisle containment closes both paths and keeps the rack inlets cool.

Schematic illustration. Colours show cooler and warmer air qualitatively; this is not a simulation result.

Heat build-up in the UPS and battery room

Equipment heat rises and collects under the ceiling. If ventilation is inadequate or a fan fails, the warm layer thickens and reaches the equipment. Correctly placed supply and exhaust openings with adequate flow carry the heat out of the room.

Schematic illustration. Colours show cooler and warmer air qualitatively; this is not a simulation result.

Cooling interruption and the generator restart chain

When utility power fails, cooling can stop until the generator takes over, and rack inlet temperature climbs through each restart attempt. With fans and chilled-water pumps on UPS and stored chilled water in the loop, air keeps moving and the climb is slower and shallower.

Schematic illustration. Colours show cooler and warmer air qualitatively; this is not a simulation result.

Site climate and the heat rejection margin

Outdoor units reject less heat as the ambient air warms. Sizing against a generic design day can leave no margin in the hottest hours of the year; site-specific design conditions with a forward climate allowance put that margin back.

Schematic illustration. Colours show cooler and warmer air qualitatively; this is not a simulation result.

Scenario library: E1–E5 / I1–I5 / T1

A thorough CFD review needs a complete scenario set. We organise every standard scenario under one roof; each is structured as a mini-package that can be priced per unit and combined according to the site's classification (Hybrid / Core / Edge / Electrical Rooms).

External flow scenarios (E1–E5)

CodeScenarioScope
E1Prevailing wind, exhaust dispersionExhaust plume dispersion at the most frequent wind direction and speed
E2Worst-case direction, re-ingestionThe most critical angle for intake louvres; re-ingestion ratio and intake concentration
E3Contaminant concentration mapSpatial mapping of NOₓ, CO and particulate dispersion
E4Façade & roof wind loadingEquipment surface pressure (ESP) values per VDI 3783-12
E5Pedestrian comfort & safetyPedestrian-level wind comfort criteria

Internal flow, steady state (I1–I5)

CodeScenarioScope
I1Full-load normal operationThermal baseline distribution with all systems at design load
I2AHU failure (N+1 test)Rack inlet temperatures with one cooling unit offline
I3Layout optimisationIteration of rack / layout arrangement
I3.aMitigation recommendations (optional)Additional iteration for identified hotspots
I4Summer peak + full loadFull load under ASHRAE n=50 design-day conditions
I5Grey space thermal safetyTemperature envelope in UPS, battery and transformer rooms

Transient & add-on items (T1+)

CodeScenarioScope
T1Generator failure chainUtility failure → three restart attempts → catcher generator; time-dependent thermal response
OptionalAdditional hall / electrical roomRepeatable per project scale, priced per unit
OptionalRe-run after layout changeRepeat run after a design iteration, priced per unit

Boundary condition chain: from climate to CFD input

The reliability of a CFD result is only as strong as the meteorological data beneath it. A four-step chain produces a location-specific, statistically representative wind / temperature / humidity regime for every project and feeds it directly to the solver.

  1. Reanalysis data (ERA5, 1979+). Hourly ECMWF ERA5 data from 1979 to the present is used for the location; the wind rose, atmospheric stability classes, and temperature/humidity distribution are derived from this record.
  2. Station-to-site correction. A bias correction is applied against the measured gap to the nearest weather station; topography and urban roughness effects are factored in separately.
  3. ASHRAE design-day envelope (n=50). The ASHRAE Fundamentals n=50 temperature envelope is applied to define summer and winter extremes and safety-margined thermal loads.
  4. Calibrated atmospheric boundary-layer profiles. The resulting statistics are converted, per scenario, into an atmospheric boundary-layer profile, turbulence intensity and surface roughness (z₀), and fed to the solver as CFD input.

Why this chain cannot be reduced to a single row of a standard table is shown with numbers in our technical review of ASHRAE design conditions: the measured station-to-site gap leaves the heating design value (99.6%) 2.1 K optimistic at the example site, and the free-cooling window is 454 to 557 hours per year wider than the station suggests; the trend in the cooling design temperature, meanwhile, reads "not significant" in the latest 25-year window alone but is significant and positive over the full record. The station-to-site correction in step two follows the same logic, carrying the measured night/day gap across separately.

Tool-agnostic solver policy

We do not sell software licences. That has two practical consequences: our tool recommendation is not tied to a sales interest, and where a client has an approved software list, delivery can be made in that environment. For contractors working inside hyperscaler and colocation supply chains this removes a procurement obstacle; for operators who already hold a CFD licence but lack capacity, the model is handed over ready to run in their own environment.

We are solver-agnostic. When a client specifies a commercial solver, we license it for that project; otherwise we work on our own compiled and validated open-source solver stack. Every report documents the method, mesh, turbulence model, convergence and acceptance criteria.

Regardless of the tool chosen, every final report documents the same information: tool selection, mesh summary, turbulence model, convergence criteria and monitoring probe locations. The result is delivered at the same level of auditability whichever solver produced it.

Reference standards

All deliverables are assessed against the following reference standards, with acceptance criteria locked with the client before the run starts:

  • ASHRAE TC 9.9 (A1–A2) temperature envelope
  • Maximum SIT (rack inlet temperature) limits of 35/40°C
  • VDI 3783-12 atmospheric dispersion protocol
  • ASHRAE 62.1 and ASHRAE Fundamentals
  • EN 16798-3 and ISO 16817 ventilation standards

Deliverables

The output is not a pretty picture; it is an engineering report that points to a direction.

DeliverableScope
Interim & final report (PDF)Specification-aligned report covering the mesh summary, turbulence model, convergence record, results and acceptance criteria
Native CFD model (optional)Delivered in the native file format of the solver used, ready for future revision in the client's own environment
Management presentationSummary slide deck for non-technical stakeholders; risk map and decision recommendations
Mitigation recommendations + unit-priced re-runLayout/equipment recommendations for critical hotspots; a repeat run available on request at a unit price

Timeline

The sequence imposed by client specifications runs external flow + baseline, then internal flow / layout optimisation, and transient last. We lock this sequence at the start of the project and close out proposal risk early with a 15-day pre-analysis checkpoint. Typical total duration is 10–11 weeks.

WeekPhaseContent
1–2Input & kickoffSpecification lock, geometry, heat-load list, climate data delivery
3–5External flow + baselineE1–E5 & I1–I2 run in parallel; 15-day checkpoint with the client
6–7Layout & mitigationI3 / I3.a / I4 / I5 iterations; two-way design negotiation
8–9TransientT1: utility fail → 3-restart → catcher generator; continuous-cooling exemption assessment
10–11Final & close-outFinal deliverables, presentation, acceptance & sign-off

From CFD to investment decisions: climate intelligence and decision-ready outputs

Every physical model we build can be linked to our UrClimate Tailor platform. This lets the same digital twin be tested under future climate scenarios out to 2100, SSP-based warming pathways, and extreme heat, drought, wind, storm and compound-event conditions. You then know not only today's performance but how safety margins narrow or hold up over the decades ahead. This link shares the same data foundation as our meteorology and climate data infrastructure and our energy modeling service.

We translate engineering results into investment and operating decisions: CAPEX justification (N+1 vs N+2), OPEX projections under hotter climates, and outputs usable by banks, insurers and ESG auditors. The climate exposure computed for the same site feeds risk quantification through UrClimate Score, and from there into TSRS climate risk reporting. The team that validates the cooling design and the team that reports the site's climate exposure are the same. We describe this three-step approach, from physical analysis through future climate projection to financial reporting aligned with IFRS S2 and TSRS, on our climate-resilient data center page.

Why Alkazar

  • Deep CFD expertise proven across telecom, defense, banking, and hyperscale facilities
  • EN 50600-aligned engineering workflows, not generic simulations
  • Climate-ready by design, not retrofitted later
  • One partner from physics → climate → finance

Related calculator: try our bypass/recirculation loss calculation tool.

Selected references

Selected data centre references (Türkiye)

FacilityWhite space modelled (m²)
Turkcell Ankara Data Centre8,000
Turkcell Gebze Data Centre6,000
Vodafone Ankara Data Centre3,000
Kredi Kayıt Bürosu (KKB) Data Centre2,500
Türk Telekom Istanbul Data Centre1,000
TÜBİTAK SAGE Data Centre940
Turkcell Izmir Data Centre500
İşbank Data Centre240
Turkcell Tepebaşı Data Centre40
Two government security facilitiesConfidential

Over 22,000 m² of white space modelled across nine disclosed facilities, plus two confidential government sites. For security and compliance reasons, government projects are not disclosed by name or area and are not included in the total.

Recent work

  • Turkcell Ankara data centre, live data halls (2026): CFD verification of a cooling system replacement while the halls stay in operation, with a baseline model checked against operating data and an N+2 resilience matrix of about 70 scenarios.
  • Turkcell İvedik data centre, Ankara (2025): white space CFD and external airflow around the heat rejection and generator yards.
  • Türk Telekom Başakşehir and Ankara data centres (2025): white space CFD, external airflow and recirculation.
  • QNB data centre, Ankara (2025): white space CFD with containment and layout recommendations.
  • Data centre project in Frankfurt, Germany (2026): external airflow CFD and site climate study.
  • Three hyperscale data centres in Ankara (2026, in progress, client confidential): external airflow, white space and grey space CFD.

Our team

Güven Fidan, Founder and CEO. MSc and BSc in Mechanical Engineering (Özyeğin University; Istanbul University). 18 years in computational engineering. Founded Alkazar in 2011 and is the technical lead on every data centre project: white and grey space CFD, cooling failure and replacement scenarios, external airflow and site climate inputs.

Orhan Külahlı, Technical Manager, CFD. BSc in Mechanical Engineering (Yeditepe University). Data hall and external airflow models, transient scenarios and CFD geometry built from BIM models; project coordination on live data hall work.

Fatih Demirtaş, CFD Analysis Engineer. BSc in Mechanical Engineering (MEF University). Grey space (UPS, battery and electrical rooms) and network rooms, mesh independence studies, post-processing and RCI/RTI reporting.

Ahmet Emin Kaya, Meteorological Engineer. BSc in Meteorological Engineering (Istanbul Technical University). Site climate data, reanalysis and weather model runs, design conditions.

Zehra Binnaz Turgut, Geomatics Engineer. BSc in Geomatics Engineering (Istanbul Technical University). GIS, terrain and site data, hazard mapping.

All analyses are carried out by our in-house engineering team in Istanbul. International contracts are signed and invoiced through Alkazar Limited (UK). CVs are available on request.

Let us discuss your project

A short first call to agree scope, timeline and deliverables. The same team that does the work answers.

Write to us by email Request a call

Frequently asked questions

At which stage should data center CFD analysis be carried out?
It returns most value at concept and scheme design, while layout, air distribution strategy and outdoor unit positions can still change. During construction it is used for verification and pre-commissioning risk reduction. In existing facilities it is run before a capacity uplift.
How is rack inlet compliance demonstrated?
An inlet temperature distribution is produced for every cabinet and compared against the recommended range of the target class. The deliverable is not a single average but the list of cabinets in breach together with the cause: bypass, recirculation or insufficient flow.
Why does generator exhaust re-ingestion need a separate analysis?
When exhaust returns to a fresh air intake or a condenser intake, two risks appear: a loss of cooling capacity and degradation of the generator's own intake air. This cannot be seen in an internal model; it requires an external flow model that includes surrounding buildings and the prevailing wind directions.
Why run a transient analysis instead of a steady-state one?
A steady-state analysis shows the equilibrium reached at the design point. The critical moment is the transition: once utility power is lost, the thermal inertia of the system governs behaviour until the compressors restart. We call this window the Transient Resilience Window; it can only be measured with a time-dependent analysis.
What types of data center cooling systems are there, and why does airflow management matter as much as capacity?
By proximity to the heat source, cooling is room-based (CRAC/CRAH with a raised floor), row-based, cabinet-based or liquid cooled. Whichever architecture is chosen, cold air escaping to the hot side without passing through the servers (bypass) and hot air returning to the inlets (recirculation) heat up cabinets even when capacity looks sufficient; CFD makes these losses visible at cabinet level. See the airflow section of our cooling guide.
How are condensation risk and the temperature and humidity envelope controlled in a data center?
The target is to keep server inlet air within the temperature and humidity envelope defined by the ASHRAE TC 9.9 guideline. Condensation is governed by dew point, not relative humidity: cold surfaces such as chilled-water pipes, coils and transitions admitting outdoor air must stay above the dew point of the hall air. CFD shows the temperature and humidity distribution around those surfaces under design and transition conditions; see the condensation section of the guide.
How does the cooling load calculation relate to CFD analysis?
The cooling load calculation sets capacity: IT load, other internal gains and infrastructure losses are summed with the chosen outdoor design condition. CFD shows how that capacity is distributed in the hall: which cabinet receives enough air, where a hot spot forms in the redundancy scenario and how fast temperature rises during an outage. Neither is complete without the other; the logic of the calculation is explained in the guide.
How do CFD results connect to climate risk reporting?
The climate exposure computed for the same site feeds risk quantification through UrClimate Score, and from there into TSRS climate risk reporting. The team that validates the cooling design and the team that reports the site's climate exposure are the same.
Let's scope your project: share your layout, IT load, cooling schematic and Approved Software List if you have one, and we will define together which scenarios are required and what will be delivered. Get in touch.

Related content

Veri Merkezleri Bilgi Formunu İndir

Solutions

Teklif Alın

Get a quote

Alkazar Technology
Privacy overview

No cookie other than the strictly necessary ones is placed on your device before you opt in. You can switch each category on or off separately and change your choice or withdraw your consent at any time through the "Cookie settings" icon in the corner of the page. Controller: Alkazar Mühendislik ve Danışmanlık Ltd. Şti.