Rack Civil Integration: Mass, Floor-Loading & Seismic Anchoring

Most of the AI-density story is told in kilowatts and litres per minute. This chapter is told in kilograms and kilonewtons. The rack that draws 132 kW and needs 80 L/min of coolant also weighs — a fully populated GB200 NVL72 compute rack lands around 1,500 kg in a footprint under one square metre, and the full system (compute rack, NVLink switch rack, CDU, in-rack PDUs, the coolant inventory itself) totals roughly 3,000 kg of concentrated, plumbed, hard-to-move mass. That is no longer IT furniture sitting on a floor. It is a structural-civil load case, and the decision of how to carry it — slab, floor system, anchorage, and move route — is one of the least reversible in the building. You can re-plumb a cooling loop and re-pull a busway. You cannot un-pour a slab that was cast 50 mm too thin or reinforced for the wrong point load.

This is the civil scope of rack integration: the rack as a load on the structure. It is deliberately distinct from the rack as an IT integration unit — cabling, RU geometry, factory build, and burn-in — which is owned by Chapter 7.13. It inherits its design basis from the structural engineering of the hall (Chapter 6.2) and the geotechnical and seismic basis established at siting (Chapter 3.8). Here we walk the decisions a project actually faces when steel meets concrete meets a 3-tonne rack on casters: how to verify floor loading, whether to keep a raised floor, how to anchor against an earthquake and a tip-over, and how to get the thing from the loading dock to its final position without cracking the slab or the schedule.

Start with the number that breaks legacy assumptions. The compute rack of a GB200 NVL72 concentrates about 1,500 kg into roughly 0.8 m-squared of footprint — a uniformly-distributed equivalent of approximately 1,875 kg/m-squared (about 384 psf) just under that one cabinet, before you add the live load of people, the temporary load of a lift, or the dynamic amplification of moving it (Introl, NVIDIA OCP datasheets, 2025). A great many existing data halls were designed to a raised-floor rating on the order of 1,000 kg/m-squared and a per-rack limit of 2,000-2,500 lb. A loaded NVL72 is over that limit by itself — and the next-generation Kyber-class racks heading toward ~600 kW will be heavier still. The floor is, quietly, one of the first things the density ramp breaks. → the density wall in Chapter 5.1.

The civil engineer does not design to a single number; they design to a load combination. Two limits matter and you must clear both: the uniformly-distributed live load the floor can carry across the whole hall (so that aisles full of racks, plus PDUs, CDUs, busway, and people, do not overload the structure in aggregate), and the concentrated point load under each caster or leveling foot (so that a single heavily-loaded rack does not punch through a floor tile, crush a pedestal, or exceed the local bearing of the slab). A rack that passes the uniform-load check can still fail the point-load check, because the mass is delivered through four small contact patches. This is why the right artifact is a rack-by-rack floor-loading verification tied to the structural model — not a single headline psf rating for the building.

For two decades the raised access floor was the default: a 600-900 mm plenum delivered cold air, routed power whips, and carried liquid and data under the white space. AI density attacks that model from two directions at once. First, direct-to-chip liquid cooling removes the reason the plenum existed — you are no longer pushing the bulk of the heat through under-floor air, so the deep cold-air plenum is largely vestigial (overhead air handling and overhead or in-rack liquid distribution do the work). Second, the mass went up faster than access floors can economically carry it. A pedestal-and-tile system engineered to safely hold a 3-tonne plumbed rack at a high point load, plus the lateral bracing that seismic codes then demand of that elevated structure, is expensive and fragile compared with simply putting the rack on the ground. → the cooling rationale in Chapter 5.4.

The consequence is a clear industry drift toward slab-on-grade (or a heavily-reinforced structural floor poured to the rack basis) for dense liquid-cooled halls, with services run overhead or in dedicated trenches/cable troughs rather than a continuous deep plenum. Slab carries heavier equipment with simpler anchoring, removes the pedestal-movement and tile-deflection failure modes, and makes seismic compliance materially cheaper because you are anchoring directly into structural concrete instead of bracing an elevated platform. The trade is flexibility: a slab gives up the under-floor service flexibility and the easy reconfigurability that made raised floors attractive, and it forces you to commit to a service-distribution strategy (overhead) up front. This is a genuine fork, and it interacts with the hall typology in Chapter 6.1.

The fork is not absolute. Plenty of halls keep a shallow raised floor for cable management and leak containment while abandoning it as the primary cooling path, and some operators reinforce the access-floor grid (heavier pedestals, stringer systems, structural load-spreading) specifically to land dense racks on it. The point is to decide deliberately: if you keep a raised floor in a liquid-cooled hall, you owe a point-load verification per rack and a containment plan for the coolant inventory now living above an electrified plenum. If you go slab, you owe an overhead-services design and you accept reduced reconfigurability. What you cannot do is inherit a legacy raised floor and assume it will carry the new racks — it almost certainly will not.

A 3-tonne rack with a high centre of gravity, plumbed to a coolant loop and cabled to a fabric, is exactly the object seismic codes exist to restrain. The governing question is not whether to anchor — for any meaningful seismicity you must — but to what standard and with what scheme. Two regimes dominate. In the US and IBC jurisdictions, ASCE 7-22 Chapter 13 governs nonstructural-component anchorage, and data centers are classified as Risk Category IV essential facilities, which sets the component importance factor Ip = 1.5. That single factor multiplies directly into the seismic design force F_p, so every anchored rack, PDU, CDU, and cable tray must resist roughly 50% more lateral force than the same equipment in an ordinary commercial building. In telecom-derived practice, equipment is qualified to Telcordia GR-63-CORE (NEBS) Zone 4, the most severe tier, which requires the rack to keep operating through the event without component replacement or manual intervention.

The design force F_p is a function of the site spectral acceleration, the component amplification and response-modification factors, the height of the component within the structure, and Ip. The consequences of getting the anchorage wrong are concrete and well-catalogued: using non-seismic-qualified anchors, and setting anchors too close to a slab edge — which can strip 30-50% of the concrete breakout capacity — are the recurring failures. Post-installed anchors must be designed to ACI 318 Chapter 17 with ICC-ES-evaluated products (AC193 for mechanical, AC308 for adhesive), with edge distance, spacing, and group effects all verified, and special inspection on the install. This is also where the slab-vs-raised-floor choice pays off: anchoring into structural concrete is straightforward; anchoring a heavy rack through an elevated access floor means restraining the floor system too. → the structural basis in Chapter 6.2; the site seismic basis in Chapter 3.8.

The most overlooked civil load is the one that exists only for an afternoon: getting the rack from the dock to its position. A 3-tonne rack does not teleport. It is rolled, sometimes lifted, across a load path that must bear not just the rack's static weight but the dynamic and concentrated temporary loads of casters in motion, hydraulic lifts (commonly rated to 2,000 kg), pallet jacks, and roller systems — loads that frequently exceed the rack's final resting load on a small contact area. If the move route crosses a raised floor, a temporary ramp, a trench cover, or a slab section poured to a lower spec, that is where the floor cracks. The rigging plan is a civil document, not a logistics afterthought.

The plan must resolve, end to end: the dock-to-position load path and every floor section it crosses (verified against the moving load, with steel road plates or load-spreading where needed); door, corridor, and turning clearances — standard data-hall doors often cannot pass an NVL72-width rack, forcing door-frame or wall removal designed in advance rather than improvised; floor protection (Masonite, steel plate, protective matting) to prevent caster point loads from marring or cracking the finished surface; and the sequencing against construction and other equipment sets. None of this is exotic, but all of it is high-stakes on a 3-tonne plumbed object, and it is tightly coupled to construction sequencing and phased turnover in Chapter 6.6 and to the heavy-rigging EHS program in Chapter 6.9.

Sort the decisions by the cost of changing your mind. The civil substrate is the most irreversible layer in the building, and the density ramp is the thing it must anticipate.

Irreversible (size to the ramp now): the slab thickness and reinforcement, the structural grid and bay spacing, the floor-system choice (slab vs raised), embedded anchorage provisions, and the geotechnical/foundation basis. These are poured or framed once. If there is any chance the hall hosts the next density generation — and a 132 kW NVL72 today points at ~600 kW Kyber-class racks tomorrow — the floor-loading basis, the anchorage scheme, and the move-route capacity should be designed to the heavier future case, because retrofitting a slab mid-life under live, plumbed, energized racks is punishing and often impossible without decommissioning the hall.

Reversible (defer, keep cheap): the per-rack spreader-plate detail, the specific anchor product within a qualified family, the exact rack positions within a verified grid, and floor-protection logistics for a given move. These you decide rack-by-rack and move-by-move. The strategic play is the same as the cooling cliff: reserve the structural headroom you cannot retrofit, defer the rack-level detail you can. A slab and an anchorage scheme designed for the heavier generation cost a modest premium today; a slab that cannot carry the ramp is a concrete husk. → the density-ramp framing in Chapter 1.1; reliability economics that justify (or don't) over-building in Chapter 12.2.