
Manage design options like a consultant: create model versions and alternates, add cold-aisle containment and solve to see its effect on every cabinet.
In this lecture you will:
Create a new model version for the containment study
Understand versions vs alternates
Add cold-aisle enclosures to the rows
Solve and read the temperature and ASHRAE results
Why it matters: Clients want options, not one answer. Versions let you keep the baseline and each proposal side by side without losing work.
Build the hot-aisle alternative: enclose the hot aisles, add a false ceiling and ceiling ducts on the ACUs, then solve and animate the streamlines.
In this lecture you will:
Create a hot-aisle containment alternate
Add a false ceiling as the return plenum
Duct the ACU returns to the ceiling void
Solve and animate streamlines through the room
Why it matters: Hot-aisle containment changes the whole return-air path. Modelling the ceiling and ducts properly is what makes the comparison fair.
Hot-aisle or cold-aisle containment? Use Compare Models to put both designs side by side, with synchronised views and tables, and make a recommendation.
In this lecture you will:
Open both alternates with Compare Models
Synchronise result planes for a fair comparison
Compare grille flows and cabinet temperatures in tables
Turn the comparison into a client recommendation
Why it matters: A side-by-side picture and a table of numbers is how you present options to a client and justify the one you recommend.
Model a realistic, uneven load: high-density HPC, mixed-use and storage zones, using capacity-planning items and U-slot power in Reality DC.
In this lecture you will:
Create a capacity-planning version of the model
Set up HPC, mixed-use and storage zones
Assign power to cabinets and U slots
Check the load budget against cooling
Why it matters: Real halls are never evenly loaded. High-density HPC rows create local hot spots that an average-kW calculation will never show.
Switch ACUs from fixed speed to pressure-sensor control, solve, and analyse floor-void pressure maps to save fan energy without risking the IT.
In this lecture you will:
Change ACU flow control to pressure control
Place and assign the reference pressure sensors
Solve and compare temperatures with fixed-speed fans
Analyse floor-void pressure in plan and section
Why it matters: Fan energy follows the cube of speed. Pressure control lets fans slow down when they can, but only a CFD check shows the IT stays safe.
Replace generic racks with the client's real equipment: import an IT inventory from CSV with the Populate Cabinets wizard and map every item to library models.
In this lecture you will:
Create a new version for the real IT
Import the IT inventory CSV file
Map CSV columns to Reality DC fields
Match each device to a library model and review the room summary
Why it matters: Generic cabinets are fine for concept design. Real IT, with real airflow and power, is what operators need for day-to-day decisions.
One imported server is blowing hot air the wrong way. Use streamlines and in-cabinet airflow to find the backwards-mounted device, fix it and re-solve.
In this lecture you will:
Solve the model with the imported IT
Spot the abnormal hot cabinet
Use inflow and outflow streamlines to diagnose in-cabinet airflow
Rotate the device, re-solve and confirm the fix
Why it matters: Mis-mounted equipment is a classic real-world fault. CFD finds it in minutes, before it costs a failed server.
Fill every cabinet to capacity and fail an ACU again: does the design still meet N+1 on day N, not just on day 1?
In this lecture you will:
Create a 'fill to capacity' version
Fill cabinets to their power limit
Fail an ACU and re-solve
Compare day-1 and day-N results and report the risk
Why it matters: A hall that passes on day 1 can fail when it fills up. This check protects the client's future, not just the opening day.
The advanced chapter starts: open the cooling-failure model, save your working copy and explore the room before running a transient power-outage study.
In this lecture you will:
Open the Tutorial 7 model and save a working copy
Explore the room, cabinets and cooling units
Understand what will be tested in this chapter
Get ready for transient CFD
Why it matters: Steady-state CFD tells you how a room runs. Transient CFD tells you how long the IT survives when things go wrong.
Build the failure scenario: chilled water and ACUs fail at 0 s, restart at 150 s, chiller back at 210 s. Set chiller availability, coil properties and time steps.
In this lecture you will:
Define the outage timeline (0 s, 150 s, 210 s, 300 s)
Set the chiller availability curve
Configure ACU coil and thermal-inertia properties
Choose the time step and transient output settings
Why it matters: The answer of a transient study is only as good as its timeline and thermal inertia. This is where the physics is set up.
Solve the steady-state starting point, then launch the transient run and watch ACU supply and return temperatures change second by second.
In this lecture you will:
Solve the steady-state initial condition
Start the transient cooling-failure solve
Read ACU supply and return temperature curves over time
Know when the run is complete and trustworthy
Why it matters: A transient run must start from a converged steady state. Skipping that step is one of the most common mistakes in failure studies.
Animate the total power outage and read the over-temperature curves: the IT in cabinet I3 runs 2–3 °C above its limit for about 80 seconds before the cooling restarts.
In this lecture you will:
Animate temperature through the 300 s outage
Read cabinet over-temperature curves
Find the cabinet that exceeds its limit and for how long
Explain the result for the client report
Why it matters: In a real outage the IT heats up in seconds, not minutes. These curves show exactly how much time the facility really has.
Create the second scenario: keep the ACU fans running on UPS during the outage, set up the failure dialog and solve the new transient case.
In this lecture you will:
Create an 'ACU on UPS' alternate
Attach the ACU fans to the UPS
Update the cooling-failure scenario settings
Run the transient solve
Why it matters: Keeping air moving, even without chilled water, uses the thermal mass of the room to buy time. This scenario tests if that is enough.
Compare the UPS scenario with the total outage: ACU curves, animated sections and over-temperature curves show cabinet I3 now stays below its limit.
In this lecture you will:
Read ACU temperatures for the UPS scenario
Animate the room through the outage
Compare over-temperature curves with Scenario 1
Write the conclusion for the client
Why it matters: This is the payoff of the whole series: a clear, evidence-based recommendation that protects the client's IT during a power failure.
This course contains the use of artificial intelligence.
You can build and solve a data center model. Now it’s time to turn it into a design you can defend. In this advanced, hands-on course you continue the data center project from Design Your First Data Center and take on the questions real clients ask: which containment strategy is best? How should the cooling be controlled? Does the design still work with the real IT, at full capacity? And what happens to the servers in the minutes after a power outage?
What you will do in this course
Chapter 1: Containment and version control
Use the version tree to keep your original design safe and manage design options
Build cold-aisle and hot-aisle containment as parallel alternates
Add a false ceiling and ceiling ducts to create a hot-air return path
Compare both designs side by side and justify a recommendation to a client
Chapter 2: Capacity planning and flow control
Model uneven IT loads (HPC, mixed use and storage) with capacity planning items
Check the deployment against the client’s load map with power plots
Switch cooling units to pressure-sensor control
Analyse floor-void pressure and learn why sensor placement matters
Chapter 3: Importing real IT
Import an IT inventory from a CSV file and map spreadsheet columns
Match unknown equipment to library items and fix approximated devices
Diagnose in-cabinet recirculation and find a server mounted backwards
Fill the room to its full design capacity and re-test N+1 redundancy
Chapter 4: Transient cooling-failure analysis
Understand the difference between steady-state and transient CFD
Configure the chilled-water system, chiller availability and cooling-unit failure settings
Choose time steps and output settings that balance accuracy and solve time
Animate the failure, read over-temperature curves and prove that a design change keeps the IT safe
Why this course is different
This course is decision-focused, not just feature-focused:
Every chapter ends with an engineering decision, not just a result
You learn to compare options fairly with version control and the Compare Models view
Worked calculations explain the physics: airflow, pressure, stored cooling and time steps
Each chapter includes a downloadable workbook with instructions, diagrams, extension exercises and self-check questions with answers
Who this course is for
Engineers who have completed Design Your First Data Center and want to go deeper
CFD and HVAC engineers responsible for data center cooling design, upgrades or resilience studies
Consultants who need to compare design options and justify them to clients
Advanced students preparing for work in mission-critical facilities
Prerequisites
Access to Cadence Reality DC Design Pro (this course uses release 2025.1) through your company or organisation licence. The software is not included; for licensing questions, please contact Cadence.
Completion of Design Your First Data Center: Thermal CFD with Reality DC, or equivalent experience. Chapters 1–3 continue from the model built in that course; Chapter 4 uses its own tutorial model.
A basic understanding of hot and cold aisles and of reading CFD temperature results
By the end of this course, you will be able to evaluate containment and control strategies, work with real IT data and run a full transient cooling-failure study, which are the skills behind real data center design and resilience work.