GPU Rack Floor Loading Requirements and Delivery Worksheet

Executive Summary

Graphics processing unit (GPU) rack floor loading requirements involve separate structural, point-load, rolling-load, and anchorage checks. Average rack weight divided by footprint answers only an initial uniform-pressure question. The National Institutes of Health (NIH) distinguishes concentrated, uniform, ultimate, and rolling access-floor loads; its rolling definition includes wheel geometry. A building-floor assessment also differs from an access-floor assessment. ^{[1] [2]}

The decision covers every delivery and operating configuration, from palletized shipment through rolling installation to filled, leveled equipment. NVIDIA’s deployment guidance includes the combined weight of equipment and its conveyances along the loading-dock-to-server-room pathway. Its rack hardware inventory includes power shelves, a bus bar, and liquid manifolds, making a GPU-only equipment count an incomplete physical ledger. ^{[3] [4]} AMD’s current guide discusses 300 to 400 kilowatts (kW) per rack and calls for structural consideration of rack-scale systems; electrical power is context, not a conversion into rack mass. ^[5]

The correct evidence is the purchased configuration’s original equipment manufacturer (OEM) submittal, the building engineer’s assessment, the installed floor system’s test documentation, and the approved installation method. As checked for this report, Open Compute Project (OCP) lists guideline V4.1, whose revision history identifies July 12, 2021 as final publication. Its delivery framework separates corridor, staging, and white-space loading. These are facility-planning references, not automatic approval for a particular NVL72 rack. ^{[6] [7]}

A hypothetical 3,000 kg rack over 1.44 m² produces approximately 20.43 kilopascals (kPa) average pressure using standard gravity. These declared inputs are illustrative, not a product specification or allowable floor load. Equal sharing among four casters would yield 7.35 kilonewtons (kN) each; NIH-style mass-over-three and mass-over-two screens instead produce 9.81 kN and 14.71 kN. These calculated scenarios show why an equal split cannot establish the actual reaction. ^{[8] [1]} Qualification should end with an evidence record showing pass, fail, or unknown for each configuration and route segment. Final placement must address a continuous vertical and lateral load path, with qualified structural engineering and applicable local approvals. ^{[9] [3]}

Introduction and Background

A GPU rack purchase creates two related engineering questions: can the equipment reach its intended bay, and can that bay support the installed and service configurations? A capacity statement for the final room does not document the intervening corridor, staging area, or goods lift. OCP’s deployment guidance treats those access attributes separately, while NVIDIA explicitly includes movement conveyances in pathway loading. ^{[7] [3]}

The distinction matters when different specifications use the same word, “load,” for different things. A cabinet’s equipment capacity describes the cabinet. A raised-floor rating describes a tested floor assembly under specified conditions. A building assessment addresses the supporting structure. Eaton’s separate equipment load ratings and IBM’s floor-planning guidance illustrate these different assessment boundaries. ^{[10] [2]}

For GPU Smith’s engineering audience, this report organizes procurement and facilities evidence into a qualification worksheet. It is a method for assembling a reviewable decision, with named evidence owners and unresolved inputs, rather than a universal allowable-load specification. The intended users include facilities and structural engineers, colocation qualification teams, commissioning agents, and buyers preparing technical acceptance criteria.

The authority boundary starts with product-specific instructions. NVIDIA’s service manual explicitly gives product documentation precedence over conflicting general guidance. The qualification record should identify applicable building, fire, access, and seismic requirements and their approval owners. Building capacity, floor-system suitability, and seismic details then require project-specific review; NVIDIA’s infrastructure guidance assigns relevant seismic engineering to qualified licensed specialists. ^{[11] [3]}

Research was checked on October 22, 2026. The source set combines current vendor documentation with older authoritative design guidance. For example, the British Standards Institution (BSI) identifies BS EN 12825:2001, while OCP’s currently listed colocation guideline carries its own revision history. Publication dates and program names should therefore be recorded individually, not treated as interchangeable indications of the currently adopted local building code. ^{[12] [7]} Where a public page cannot establish the purchased rack’s shipping or operating condition, the worksheet requires an OEM submission instead of filling the gap with another supplier’s number.

Four Separate Floor Loading Checks

Building structure and uniform loading

Uniform loading describes a force distributed over a declared area. NIH’s equipment screening method divides equipment weight by machine area. IBM separately explains that a floor-loading assessment evaluates the concrete subfloor rather than the raised floor. Together, these distinctions establish why a footprint calculation alone cannot qualify the complete support system. ^{[1] [2]}

Record both the rack footprint and the distribution area accepted by the structural engineer. If a proposed calculation includes surrounding aisle area, explain how that area participates in the structural assessment. Changing the denominator on a spreadsheet does not itself provide a physical load-spreading mechanism. The worksheet should request the structural calculation that establishes the relevant distribution, together with the applicable load combinations.

Concentrated loading of the access floor

Concentrated load concerns a local force applied through a specified contact condition. NIH describes a concentrated-load test contact separately from uniform loading. Its ultimate load category concerns failure-threshold capacity, not an allowable operating load. A leveling foot, caster, jack, or support frame therefore needs its own location and reaction record. ^[1]

The floor assembly matters as well as the panel label. NIH discusses additional supports around cutouts, while Tate’s owner’s manual calls for panels to be installed before loading. Lindner identifies structural bridging where pedestals cannot be installed. The panel map must consequently document supports and interruptions, not just the rack outline. ^{[1] [13] [14]}

Rolling loads through the route

Rolling load is a test-conditioned limit, not another name for stationary capacity. NIH identifies wheel diameter and width; Tate additionally describes wheel hardness, vehicle weight, contents, and pass count. Those details belong beside the rating in the worksheet. ^{[1] [13]}

Equipment movement also has a cabinet-side limit. Schneider publishes separate static and dynamic ratings for a specific enclosure. Satisfying a floor rating does not remove the need to satisfy that enclosure’s permitted moving configuration. ^[15]

Installed stability and anchorage

Anchorage provides a designed load path for the installed condition. Federal Emergency Management Agency (FEMA) E-74 guidance calls for continuity under vertical and lateral forces and consideration of overturning for equipment attached to access floors. It describes structural-slab anchorage and properly designed support alternatives. ^[9]

Use these categories as separate worksheet decisions. Their evidence may interact, but one passing comparison cannot silently close the others. This report proposes independent acceptance fields for building structure, local floor support, movement, and installed restraint, followed by an overall release decision owned by the project.

Build the Physical-State Mass Ledger

A model family is an insufficient identifier for the qualification record. NVIDIA’s DGX GB hardware description includes power and liquid-cooling infrastructure alongside compute equipment. HPE also documents an in-row cooling distribution unit (CDU), which is separate equipment requiring its own placement and delivery review. The ledger should reconcile all equipment crossing the route or loading the bay. ^{[4] [16]}

Request the configuration identifier, drawing revision, and mass definition for every state. A statement labeled shipping, dry, fully loaded, or operating should retain that label. Public component weights should remain component weights: Dell, for example, lists an XE8712 sled at up to 33.07 kg, which does not describe the complete rack. ^[17]

Table 1 is a proposed physical-state mass ledger. Its blank values are deliberate submission requirements. NVIDIA’s product-documentation precedence and its inventory of rack components provide the basis for requesting a configuration-specific reconciliation. ^{[11] [4]}

The ledger avoids double counting by identifying what the quoted rack mass already includes. It also prevents omissions by recording what arrives separately. HPE’s separate CDU description is a useful example of why the procurement package and the physical rack are different accounting boundaries. ^[16]

Use the following requested fields in the vendor submission:

• Identity: Purchased system, options, configuration code, drawing number, and revision.
• Mass definition: Shipping, dry, filled, installed, or service condition.
• Inventory reconciliation: Rack, doors, trays, manifolds, coolant, power hardware, cables, and accessories.
• Separate equipment: CDU, sidecars, power cabinets, handling devices, and temporary staging.
• Support geometry: Casters, leveling feet, jack points, contact dimensions, and coordinates.
• Reaction evidence: OEM reaction schedule or an engineer’s approved derivation.
• Movement restrictions: Permitted tilt, handling direction, split sequence, and required equipment.

These are proposed acceptance fields, not assertions that all public manuals publish them. The final service state also needs attention: NVIDIA instructs users to extend only one piece of rack equipment at a time. The worksheet should reference that product-specific service instruction and request review of the associated support condition. ^[11]

Qualify the Complete Delivery Route

The route assessment begins at the receiving interface and ends at the service and eventual removal position. NVIDIA requires the floor and pathway to support equipment plus conveyances; OCP separates corridor loading, unboxing or staging, and white-space loading. A route record should therefore follow the equipment’s actual movement state instead of assigning one room-wide rating to the journey. ^{[3] [7]}

Measure the moving envelope. Dell lists the IR7044 rack height as 2,286 mm, while HPE’s separate GB200 NVL72 specifications list a height of 2,495 mm. These examples establish model-specific dimensional differences, not compatible alternatives or a universal clearance requirement. Neither dimension establishes the crated shipping envelope. ^{[17] [16]}

Table 2 is a proposed route-segment matrix. It extends OCP’s separate access and loading categories into evidence requests. For United States projects, Occupational Safety and Health Administration (OSHA) dockboard provisions specifically require capacity for the maximum intended load; projects elsewhere need their applicable local requirements. ^{[7] [18]}

The matrix makes the controlling segment visible. A capacity statement for an elevator does not close a missing sill assessment, and corridor width does not establish turning clearance. These are proposed independent review fields. OCP’s separation of pathway dimensions and goods-lift capacity supports that approach. ^[7]

The route walk should produce a marked plan and photographs linked to segment identifiers. Include temporary conditions that may differ from the completed hall. Tate’s requirement to install floor panels before loading is particularly relevant when nearby panels are being removed for cabling or commissioning. ^[13]

The proposed survey record should capture:

• Dock interface: The equipment state and conveyance used during each transfer.
• Clear opening: Measured door width and height with hardware and obstructions considered.
• Swept path: The actual turning geometry of the approved moving assembly.
• Transitions: Thresholds, joints, ramp crests, elevator sills, and changes in surface.
• Floor identity: Panel, understructure, finish, and location-specific modifications.
• Adjacent activity: Concurrent deliveries, parked racks, tools, and staged packaging.
• Removal access: The route and working space required for future replacement.

For dockboards, OSHA also addresses securing portable units against movement, subject to the standard’s stated exception, and preventing the supporting transport vehicle from moving while employees occupy the dockboard. Record the applicable requirement and approved dock procedure rather than treating a load number as the complete receiving plan. ^[18]

Calculate Point Loads and Match Rolling Tests

Start with reactions, not a presumed equal split

For a level rack under static gravity loading with no other vertical support, the sum of vertical support reactions equals total weight. The individual reactions still require a justified distribution. IBM discusses nonuniform caster loading and circumstances in which a single caster can impose half the rack weight; NIH presents mass-over-three and mass-over-two caster screens. ^{[2] [1]}

The worksheet should distinguish OEM reactions, engineering results, and screening assumptions. An equal division is useful only as an explicitly idealized comparison. It should never be relabeled as a measured reaction. Where the actual distribution is unknown, enter “unknown” beside the corresponding acceptance criterion.

For a support reaction expressed as force, local average contact pressure equals reaction divided by effective contact area. That arithmetic does not convert a panel’s concentrated-load rating into a pressure allowance. NIH distinguishes test categories. Compare equivalent quantities under matching conditions, retaining the contact condition and installed assembly identified in the floor documentation. ^[1]

Preserve the rolling-test conditions

NIH’s guidance demonstrates why the test basis matters. It distinguishes infrequent equipment rolling loads tested for 10 passes from frequent loads tested for 10,000 passes, and includes wheel diameter and width in its rolling-load definition. These are distinct test conditions, not interchangeable ratings for every caster. ^[1]

NIH similarly distinguishes infrequent and frequent rolling cases, while Tate’s owner guidance includes wheel hardness in the definition of dynamic loading. Request the test report or applicable specification, not just a sales-sheet heading saying “heavy duty.” ^{[1] [13]}

The proposed rolling-load evidence checklist is:

• Force basis: Load per wheel, per contact, per panel, or another explicitly defined basis.
• Wheel geometry: Diameter, tread width, material, and hardness where specified.
• Pass count: The rated number of passes and expected delivery or service traffic.
• Test position: Whether the evidence covers relevant panel centers, edges, and support arrangements.
• Assembly identity: Panel model, finish, pedestals, stringers, and installation configuration.
• Concurrent contacts: Wheel spacing and adjacent wheels that can occupy the same panel.
• Acceptance criterion: Deflection, residual deformation, or other stated test limit.
• Exceptions: Cutouts, damaged components, altered supports, and locations needing engineering review.

Map the panel system and any spreader

A useful panel map overlays rack feet and caster paths on panel seams, cutouts, stringers, and pedestal coordinates. NIH discusses reduced allowable loads near cutouts and additional supports; Tate likewise identifies additional pedestals as a solution when a cut panel must retain design capacity. ^{[1] [13]}

OCP illustrates spreader plates as a possible intervention. The worksheet should request an engineered detail establishing plate material, dimensions, stiffness, support, transitions, and intended load distribution. It should also require the added assembly to be included in the route envelope and handling plan. OCP’s reference to spreaders is a mitigation concept, not approval of a universal plate thickness. ^[7]

Where the raised-floor system cannot provide the required support arrangement, an alternative structural support concept may be considered. Bergvik describes direct mounting of heavy equipment on its self-supporting steel frame, while Lindner identifies bridging where pedestals cannot be installed. Each remains a system-specific design requiring reconciliation with the building structure. ^{[19] [14]}

Validate Final Placement and Release the Move

Installed qualification begins with the support arrangement shown on the approved drawing. Oracle’s Exadata flooring guidance requires the floor to support total rack weight, and advises avoiding floor cutouts that affect casters or leveling feet. This illustrates why the installed support condition must be taken from the relevant product instructions. Do not assume that lowering feet automatically creates the same load path for every rack. ^[20]

Trace the restraint load path. FEMA E-74 addresses vertical and lateral continuity and describes anchorage to the structural slab or other properly designed support arrangements. NVIDIA’s infrastructure guidance calls for cabinet fastening according to manufacturer recommendations and qualified seismic design where applicable. The worksheet should identify the selected arrangement, its calculation, and the installation inspection. ^{[9] [3]}

The following proposed qualification record should make the decision reproducible:

• Criterion: The exact building, floor, equipment, or installation requirement.
• Rating basis: Units, contact condition, test method, revision, and applicable configuration.
• Demand: Submitted reaction, mass, geometry, or engineered load case.
• Comparison: Capacity and demand on a common, justified basis.
• Evidence: Drawing, calculation, test report, survey, or OEM instruction with revision.
• Owner: The party responsible for closing the criterion.
• Disposition: Pass, fail, or unknown, with the reason recorded.
• Mitigation: Approved detail, responsible installer, and completion evidence.
• Release: The required engineering, landlord, colocation, and operational acceptance.

A numerical margin should be recorded only when demand and capacity are comparable. The proposed worksheet may express margin as capacity minus demand, or as a consistently defined ratio. Neither presentation creates an additional design allowance. For example, Lindner publishes point-load and breaking-load figures separately, so a breaking-load value must retain its label rather than being used as an operating capacity. ^[14]

The delivery-day release should use explicit hold points:

• Before receipt: Confirm approved shipment state, route revision, and receiving equipment.
• Before movement: Inspect the route and verify required panels and temporary supports.
• Before transitions: Confirm the approved dock, ramp, and elevator handling arrangements.
• Before placement: Verify support coordinates, cutouts, spreaders, and anchor locations.
• After placement: Record leveling, support engagement, restraints, and inspected deviations.
• Before handover: Close required evidence and attach the service and removal method.

These are proposed commissioning controls. Tate’s panel-installation instruction and NVIDIA’s fastening guidance are relevant source requirements to incorporate into the project’s actual checklist. A hold point remains open when the required evidence is unknown; a reviewer should not turn a blank cell into a passing result. ^{[13] [3]}

Data Analysis and Evidence

Published ratings are model-specific evidence

The available primary specifications demonstrate differences in both quantity and purpose. Schneider’s AR3105 enclosure lists 3,750 lb static and 2,250 lb dynamic capacity. Eaton’s SRH423246W lists 5,000 lb static and 3,500 lb dynamic. These are enclosure ratings for those products, not floor capacities or permissions to move an NVL72 assembly. ^{[15] [10]}

Lenovo’s heavy-duty rack guide separately lists static and dynamic capacities of 1,588 kg for its referenced 42 rack-unit (42U) models and 1,814 kg for its referenced 48U models. That source provides another reason to retain model and rating labels instead of inferring a moving limit from a generic cabinet category. ^[21]

Floor documentation uses different categories again. Lindner’s LIGNA power page lists point loads from 6 to 7 kN, with corresponding breaking loads from 12 to 14 kN. Bergvik identifies EN 12825 as a testing basis for its panels. BSI’s listing establishes the standard identifier, while the Ceilings and Interior Systems Construction Association (CISCA) catalog lists its access-floor test procedures. None of these listings establishes the capacity of an unidentified installed floor. ^{[14] [19] [12] [22]}

Screening calculation: hypothetical example

The following example uses assumed inputs, not an OEM rack specification: installed mass M = 3,000 kg; rack footprint A = 1.44 m²; and an idealized four-caster arrangement. Standard gravity is 9.80665 m/s² according to the National Institute of Standards and Technology (NIST). Thus weight W = M × g / 1,000 = 29.42 kN, and average footprint pressure q = W / A = 20.43 kPa. These results are rounded calculations from the declared assumptions. ^[8]

Table 3 records the calculated screens and their unresolved acceptance evidence. NIH provides the uniform-load concept and general caster scenarios, but the table intentionally makes no claim that its assumed rack satisfies a floor rating. ^[1]

Changing the assumed distribution area changes average pressure but leaves total weight unchanged. Likewise, the calculated half-weight caster screen is twice the ideal quarter-weight result. These are arithmetic observations about this hypothetical example. They do not establish real reactions or a universal screening factor. IBM and NIH’s nonuniform-load discussion explains why the purchased configuration still needs its own evidence. ^{[2] [1]}

Implications and Future Directions

The procurement implication is to request physical and handling data alongside electrical and cooling data. AMD’s current discussion of 300 to 400 kW rack-scale systems includes structural considerations and potentially nonstandard footprints. That does not yield a mass formula, but it makes the physical submittal a material part of site qualification. ^[5]

The standards implication is to preserve editions and scope. OCP’s currently listed V4.1 guideline is distinct from the OCP Ready program’s certification names. BSI provides a specific raised-access-floor standard identifier, and CISCA lists test procedures whose exact project-used revision should be requested in the floor submission. A source catalog is useful for identifying documents; it cannot substitute for the applicable test report or adopted code review. ^{[6] [12] [22]}

For engineering teams, the proposed deliverable is a controlled evidence package: configuration ledger, route matrix, floor and support map, calculation references, and acceptance record. Future moves should update that package when the moving mass, wheels, service method, floor assembly, or route changes. Tate’s definition of dynamic loading and NVIDIA’s product-documentation precedence both support retaining those configuration details. ^{[13] [11]}

For buyers, an unresolved structural or route criterion should remain visible in technical acceptance. The useful decision is whether a documented configuration can follow a documented route and occupy a documented support arrangement. Any mitigation should return to those records so its effect can be reviewed. Examples of available support concepts include additional pedestals, bridging, and independent equipment-support framing; none has a universal capacity independent of its designed assembly. ^{[13] [14] [19]}

Conclusion

GPU rack floor loading qualification is a chain of documented decisions. The building structure, local floor assembly, rolling route, and installed restraint each need an applicable demand, a comparable rating or engineered result, and a responsible reviewer. The source guidance used throughout this report supports keeping those checks separate while reconciling their shared physical configuration.

The worksheet starts with the purchased system. It preserves mass definitions, distinguishes shipment from operation, inventories associated equipment, and requests actual support reactions. It then follows that system through dock transfer, staging, corridors, ramps, elevators, raised-floor panels, and final placement. Missing information remains unknown until the responsible party supplies evidence.

The hypothetical calculation illustrates the limitation of a single average-pressure value. The same assumed rack weight can produce different pressure screens depending on the declared area, and different caster screens depending on the assumed distribution. None of those calculations establishes the actual reactions or approves a floor assembly.

The completed qualification record should identify every controlling document, configuration, route segment, mitigation, inspection, and sign-off. A passing result belongs to that defined arrangement and installation method. Changes should return to the relevant checks. Final structural acceptance rests with qualified project engineers and the authorities responsible for the site, using the purchased equipment documentation and applicable local requirements.