DATACENTER TWIN LAB

Infrastructure Engineering · Lesson 22 of 24 · 25 minutes

Review spatial capacity and phased development

A rack count is not a facility plan. Equipment requires service space, replacement routes, structural capacity and coordinated boundaries through every construction phase. Use the manuscript’s historical operating account to practise reporting what was actually stated without turning different area descriptions into one misleading density metric.

Run this lesson interactively

Learning objectives

Source statement

Treat access as part of capacity

A workable plan includes equipment footprint, service clearances, replacement and lifting routes, cable and pipe paths, and coordinated fire/security boundaries. A final campus drawing can conceal first-phase dependencies on temporary supplies or routes that later work will disturb. A live migration also adds dual-running demand and configuration risk. Review each phase as an operating state instead of assuming final-state redundancy already exists.

Illustrative assumption

Use the structural screen for what it measures

Average gravity pressure equals mass × gravitational acceleration / area. A 1,000 kg assembly uniformly distributed over 1 m² gives 9.81 kPa using 9.81 m/s². Actual rack feet, wheels, transport loads, raised-floor panels, supporting structure and restraint are not captured by that average. Similarly, installed cooling nameplates are not automatically firm post-failure capacity at actual ambient and fluid conditions.

Source statement

Preserve the historical account

The manuscript reports a 2019 Metro Data Center account with different site, tenant and raised-floor areas, rack provision and pod descriptions. These refer to different boundaries, not interchangeable denominators. Seven 30-ton air handlers yield approximately 738.54 kW thermal nameplate sum. Do not transfer an N+1 statement about some glycol components to every air handler. Preserve “Dublink 100GB” as a historical label; the supplied account does not resolve it into a verified bit rate.

Predict → run → explain

  1. Read the declared boundary and units. Predict the selected result before calculating.
  2. Run the starting case and inspect the ledger, assumptions and model limits.
  3. Apply the challenge, run again, and explain the difference. Export only the last completed inputs and results.

Average kPa = mass kg × gravity m/s² / area m² / 1,000; installed thermal kW = cooling unit count × tons per unit × kW/TR. Neither is a qualified firm-capacity or point-load result.

Declared starting inputs

{
  "massKG": 1000,
  "areaM2": 1,
  "gravityMS2": 9.81,
  "coolingUnits": 7,
  "tonsPerUnit": 30,
  "kwPerTon": 3.51685
}
Worked default — unrounded educational outputs
QuantityValueUnit
averageKPa9.81kPa
installedThermalKW738.5385kW

Challenge

What average pressure does the new rack screen produce?

{
  "massKG": 1500,
  "areaM2": 1.2
}

12.2625 kPa. The result still does not resolve individual foot or wheel reactions.

Worked challenge
QuantityValueUnit
averageKPa12.2625kPa
installedThermalKW738.5385kW

A phase-aware building cutaway — static equivalent

  1. Reveal gross building, tenant, technical and access boundaries as distinct layers.
  2. Show a maintained replacement route beside a rack field.
  3. Move through initial occupancy, expansion works, tie-in and final configuration.
  4. Select a historical datum and show its reported date, boundary and limitation.

Phase-state matrix, boundary glossary and historical-data table without a current-operation claim.

Switch phases, inspect temporary dependencies and compare distributed versus point-load descriptions.

Narrative steps are not physical seconds. Essential states and quantities remain available without animation.

Assessment and answer criteria

10.1 · Find average pressure for 1,500 kg over 1.2 m².

Read answer and marking criterion

12.2625 kPa; point reactions need separate assessment.

Criterion: Use the declared gravity and convert Pa to kPa.

Source: DCIE-R1 Appendix A, PDF pp.59-61

10.2 · Convert five 40-ton cooling units using 3.51685 kW/TR.

Read answer and marking criterion

703.37 kW thermal nameplate sum.

Criterion: Do not relabel installed nameplate as firm capacity.

Source: DCIE-R1 Appendix A, PDF pp.59-61

10.3 · What prevents a historical test frequency from becoming current compliance evidence?

Read answer and marking criterion

Check adopted requirements, actual test scope and loading, current configuration, records and acceptance authority.

Criterion: Distinguish historical observation from present-day requirement.

Source: DCIE-R1 Appendix A, PDF pp.59-61

Source and model boundaries

Data Centre Infrastructure Engineering, reference manuscript revision 1 (DCIE-R1), 11 October 2026, chapter 10, PDF pp.46–49. PDF page 1 includes the cover. manuscript-derived; not independent source verification.

Original educational adaptation. The private PDF and missing archive are not public downloads. Source statement, Editorial derivation, Illustrative assumption and Unresolved remain distinct.

Result schema: infrastructure-screen-1; content 2.0.0; model 1.0.0. Raw inputs, outputs, units, assumptions, source locators and canonical hashes. No supported in-browser Python verification protocol exists for this result family.