The Definitive Guide toAI Data Centers
Ask the GuideAboutAccount

Chapter 4.6

LV Distribution: Busway, PDUs, RPPs & Rack Power

In the last thirty meters of copper between floor PDU and chip, resistive (I²R) loss quietly sets how much power you can actually land on a 600 kW rack.

POWER-BOUNDDENSITY-RAMP

What you'll decide here

  1. Busway vs cable-and-floor-PDU for the row distribution layer — and therefore whether your density ramp is a tap-off swap or a conduit re-pull.
  2. The busway ampacity and rack-PDU voltage class (208V vs 415V/400V three-phase) you size to — because the ratings you pour into the slab cap the rack power you can ever feed without a rip-and-replace.
  3. Where the AC→DC conversion and the redundancy boundary live: facility-level UPS feeding AC rack PDUs, OCP 48V power shelves at the top of the rack, or a disaggregated sidecar that collapses the chain.
  4. How A/B dual-cording, per-phase branch metering, and outlet-level telemetry expose utilization and imbalance—without changing the continuous-load limit set by equipment listings, circuit ratings, load classification, derating, applicable code, and the project protection basis.
  5. Whether the in-rack power bus is air- or liquid-cooled — the co-design fork that, past ~140 kW, turns a passive copper bar into a thermally-managed component.
Amps to land 600 kW at each voltage class — I²R losses and copper mass, not cooling, set the rack-power ceiling.

Everything upstream of this chapter — the utility tie, the substation, the medium-voltage ring, the transformers, the UPS — exists to deliver clean, redundant low-voltage power to a row of racks. What remains is the last leg: how that LV power gets from floor-level distribution into the rack, into the shelf, onto the busbar, and finally onto the accelerator tray. It is the least glamorous part of the power chain and, in the 2026 density regime, one of the most binding. A GB300 NVL72 rack, the 2026 volume platform, draws roughly 132–140 kW; VR200 NVL72 is in production behind it at an analyst-estimated 190–230 kW, and the published roadmap puts Rubin Ultra Kyber-class racks near 600 kW. Google, Meta, and Microsoft are openly standardizing toward 1 MW racks. At those numbers the humble copper bar stops being plumbing and becomes a thermal and economic constraint in its own right.

The forks in LV distribution are unusually unforgiving because so much of this layer is poured into the slab or bolted to the ceiling at fit-out time. Choose a 400A busway and a 208V PDU standard, and a hall that was perfectly sized for 40 kW air-cooled racks in 2023 cannot feed a 132 kW liquid rack in 2026 — not because the cooling fails first, but because the copper is undersized: √3 × 208 V × 400 A is ~144 kVA theoretical, the standard 125%-continuous-load rule cuts that to ~115 kVA at 320 A, and after power factor and PSU efficiency you are left with roughly 108 kW of usable IT. Only a fully 100%-continuous-rated listed assembly (~140 kW before project derating) even approaches the number. This is the I²R wall: every doubling of current at fixed voltage quadruples resistive loss, and that loss shows up as heat, voltage droop, and copper mass you pay for by the tonne.

The two distribution architectures: busway vs cable-and-PDU

The first fork sits above the rack. Power reaches a row of racks one of two ways. Overhead busway (busbar trunking, "track") runs a continuous enclosed copper or aluminum bus along the top of the row, and each rack draws from a tap-off box that clamps onto the track wherever you need it. Cable-and-PDU runs discrete feeders — conduit and cable, or underfloor whips — from a floor-standing power distribution unit (a floor PDU or remote power panel) to each rack's branch circuit. Both deliver the same electrons; they differ entirely in how the density ramp is serviced.

Busway's decisive advantage is reconfigurability across a density ramp, not routine energized modification. The trunk provides multiple listed tap positions, so a planned outage can relocate or resize branches without pulling a new home-run feeder. The default sequence is to de-load downstream equipment, establish the project electrical safe-work condition and lockout/tagout boundary, install or replace only the listed tap-off under the manufacturer's instructions, inspect engagement and torque, then re-energize and verify. Some assemblies permit insertion or removal while the bus remains energized, but that is an engineered exception, not normal work: it requires the exact listed assembly and procedure, downstream load isolation, an approved energized-work justification, incident-energy assessment, qualified personnel, task-selected PPE and insulated tools, controlled boundaries, stored-energy control, and an approved method of procedure. Cable-and-PDU fixes the branch-circuit count and conductor size at installation; growing a rack past its provisioned feeder requires a new home run, planned circuit and panel isolation, a panel-schedule change, and re-termination. Busway preserves future branch-placement options, but outage avoidance is not the governing safety criterion.

The counter-case is real. Busway can place a high available fault current in one trunk, so tap-off incident energy and bus-fault consequences must be calculated from the project source, protection, clearing time, task, and working distance; the trunking is a long-lead, vendor-specific item with limited cross-compatibility; and for a hall that will never exceed a known, modest density, discrete feeders are cheaper and simpler. The honest reading: busway is the density-ramp instrument, cable-and-PDU is the fixed-density instrument. If there is any chance the hall hosts a generational density step-up — and in 2026 there almost always is — the busway's option value dominates.

Row distribution: busway vs cable-and-PDU
PropertyOverhead busway (tap-off)Cable + floor PDU / RPP
Density-ramp serviceRelocate or resize tap-offs during planned de-energized work; energized insertion/removal only as an engineered exceptionNew home-run feeder per rack; planned circuit and panel isolation
Typical trunking ampacity400 / 630 / 800 / 1000 A bands; AI halls now spec 800–1,000 ASized per branch circuit at install; fixed at the panel
Capital postureHigher upfront trunking cost; cheap incremental tap-offsCheaper upfront for fixed density; expensive to grow
ReconfigurationMultiple tap positions; isolate and de-load by default, then follow the listed assembly procedureRe-pull conduit, change panel schedule, re-terminate
Fault / arc-flash energyProject-specific — high available fault current can make tap-off incident energy severe; calculate itLower per-feeder; contained to one branch circuit
Lead time / lock-inLong-lead, vendor-specific trunking; limited cross-compatCommodity cable and breakers; multi-vendor
Best-fitAny hall facing a generational density rampKnown, capped density; cost-driven fixed deployments
The fork that decides whether a density ramp is a tap-off swap or a conduit re-pull. Ampacity bands are 2026 AI-hall practitioner ranges; arc-flash and lead-time columns are directional.

Inside the rack: PDU voltage class, dual feeds, and metering

Below the tap-off sits the rack PDU — the vertical power strip the IT gear plugs into. The decision that dominates here is voltage class, and it is a pure I²R argument. Legacy halls distribute 208V three-phase to the rack; modern high-density halls distribute 415V/400V three-phase (line-to-line), delivering 240V/230V line-to-neutral to each outlet. At fixed power, raising the rack-PDU voltage from 208V to 415V halves the current, which quarters resistive loss and lets the same conductor and connector carry roughly twice the load. A 60A 208V three-phase PDU tops out around 17–20 kW usable; a 415V three-phase PDU at the same amperage clears the high-30s. That is why 415V (and its 400V European twin) is the de facto rack standard for liquid-density AI rows — busway trunking supporting 415V/480V now represents the majority of new global deployments. Sticking with 208V in a high-density hall is the quiet way to strand half your rack capacity in copper.

The connector layer follows the voltage. AI racks lean on IEC 60309 pin-and-sleeve connectors (the blue/red industrial "ceeform" plugs) for the feed and high-amperage IEC 60320 C19/C21 or the newer C39/C41 outlets for the rack whips, because the legacy C13/C14 ecosystem cannot carry the per-server current modern accelerator trays demand. The rack whip — the flexible cordset from tap-off to PDU — is the field-serviceable reversible element; its connector and amperage are matched to the PDU class, and getting that match wrong is a re-order, not a re-wire.

A/B dual feeds are the rack-level expression of facility redundancy. Two independent PDUs, fed from two independent busways or panels on different UPS branches, let dual-corded equipment ride through the loss of one path. The discipline that breaks operators is the 50% rule: each feed must be loadable to no more than half its capacity, or the survivor cannot pick up the failed path. Single-corded equipment (increasingly common in cost-optimized inference and in some OCP designs that push redundancy down to the shelf) breaks this model and forces a different reliability story — covered in Chapter 4.5 and reframed as goodput-vs-availability in Chapter 12.2.

The OCP path: 48V power shelves and the in-rack busbar

Hyperscale and the OCP ecosystem take a different cut at the same problem. Instead of distributing AC to every server and converting per-PSU, the Open Rack V3 (ORV3) design centralizes conversion in a power shelf at the top (or middle) of the rack: AC in, a bank of hot-swappable rectifier modules (commonly 6 × ~5.5 kW, giving ~33 kW per shelf, ~27.5 kW at N+1), and a vertical 48V DC busbar running the height of the rack. Compute and switch trays blind-mate directly onto that bar — no per-server power cords, no rack whips, no C19 forest. NVIDIA's GB200 NVL72 follows the same philosophy with paired busbars rated at roughly 1,400A each — ~2,800A aggregate at 48V — feeding the 72-GPU tray stack (132 kW ÷ 48 V ≈ 2,750 A; see Chapter 7.13).

The 48V choice is, again, an I²R decision — just relocated. Forty-eight volts is high enough to cut busbar current ~4× versus the legacy 12V server-distribution bus (quartering loss in the bar), while remaining within the stated 60V DC SELV boundary for contact-voltage classification. That boundary does not cap the energy available from a stiff, high-current bus: tray service still requires the listed assembly instructions and a task-specific assessment of arc and thermal burns, short-circuit current, stored energy, conductive tools, isolation, and PPE. It is the sweet spot the OCP ecosystem converged on, and it is the launch pad for everything in Chapter 4.7: once you are already running a DC bus inside the rack, the natural next moves are to raise it (±400V Mt. Diablo / Diablo 400, 800V NVIDIA reference) and to disaggregate the conversion into a sidecar power rack beside the compute, which is exactly what >600 kW Kyber-class racks require because the power shelves no longer fit in the compute rack at all.

The fork for an operator: AC rack PDUs are the commodity, multi-vendor, retrofit-friendly path that any colo can deliver; the OCP 48V shelf path raises e2e efficiency (fewer conversion stages, the rectifier bank runs near its efficiency sweet spot) and slashes the cabling labor and copper of a per-server cord plant, at the cost of committing to the OCP rack form factor and a narrower supply base. Below ~50 kW the AC-PDU path is rarely worth abandoning; above ~100 kW the shelf-and-busbar architecture's efficiency and density advantages compound, and by the time you reach the megawatt rack it is effectively mandatory.

Rack power-delivery architecture by density tier
Density tierDistribution to rackIn-rack conversionBus / connectorWhen it wins
Up to ~30 kW208/415V cable + floor PDUPer-server AC PSUAC whips, C13/C19Legacy air-cooled and enterprise/small-model inference
30–80 kW415V/400V busway + tap-offPer-server AC PSU (415V)IEC 60309 feed, C19/C21Air-at-limit, RDHx, single-rack liquid
80–140 kW415V busway or OCP AC shelf feedOCP 48V power shelf, N+148V blind-mate busbar (~700A)NVL72-class DLC racks; OCP halls
140–600 kWHigher-ampacity busway / DC feed48V shelf or ±400V conversionNVL72-class paired busbars ~2,800A aggregateNext-gen DLC; copper mass climbing
>600 kW (→ 1 MW)MV or 800VDC to a sidecarDisaggregated sidecar power rack800VDC → rail; liquid-cooled busbarKyber-class; shelves leave the compute rack
The conversion-and-distribution choice tracks density. kW bands are 2026 practitioner ranges; busbar/shelf figures are OCP ORV3 and NVIDIA NVL72 reference points (see keynumbers). Frontier inference deploys the same NVL72-class liquid racks as training; the training/inference fork lives in fabric sizing, KV-cache tiering and the failure model, not in rack density.
132 kW nominal TDP: 115 kW liquid + 17 kW air
NVIDIA GB200 NVL72 by HPE: 132 kW nominal rack TDP, with 115 kW liquid and 17 kW air heat-removal duties
~600 kW
Rubin Ultra Kyber-class rack on 800 VDC; shelves disaggregate to a sidecar
33 kW
OCP ORV3 HPR power shelf output (6×~5.5 kW rectifiers; ~27.5 kW at N+1) onto the 48V busbar
800–1,000 A
overhead busway ampacity AI halls now spec (vs legacy 400 A); named product lines top out at 1,000 A (Eaton PowerWave 2: 250–1,000 A)
~2×
rack power per ampere from 208V→415V three-phase: halves current, quarters I²R loss
<60 V DC
48 V OCP rack bus within the <60 V DC SELV boundary; low touch voltage does not waive arc, short-circuit, stored-energy, or tool-control procedures
5,184
in-rack copper NVLink cables in an NVL72 — the copper-mass reality that drives the busbar-cooling fork
~98%
SST efficiency at 400 kW (13.2 kVAC→800 VDC), the single-stage path feeding the in-rack rail

The I²R wall and copper mass

Strip the LV layer to physics and one equation governs it: resistive loss is I²R, and that loss is dissipated as heat inside the very copper that is supposed to deliver power. Hold voltage constant and double the rack power, and current doubles — but loss quadruples. To hold loss and voltage droop flat you must either raise the voltage (the entire rationale for 415V PDUs, 48V busbars, and the ±400/800V roadmap in Chapter 4.7) or add copper cross-section. At 600 kW–1 MW per rack, the second option hits a wall the industry now calls the copper-mass problem: the busbar needed to carry the current at a tolerable loss is so massive and so heavy that it strains the rack structure, costs a fortune by the tonne, and — decisively — cannot reject its own self-generated heat by natural convection. An NVL72's 5,184 in-rack NVLink copper cables are the same lesson at the signal layer; the power layer is hitting it at the bar.

This is the decision that converts a passive component into an engineered one. Past roughly 140 kW, and unavoidably at the megawatt rack, the in-rack power bus must be actively cooled — the liquid-cooled busbar. The same warm-water loop that cools the cold plates is tapped to carry heat out of the busbar itself, so the bar can run at a higher current density without exceeding its thermal limit. NVIDIA's Vera Rubin reference and the OCP megawatt-rack work both make the liquid-cooled busbar a first-class element. It is the cleanest example in the power chain of thermal-electrical co-design: you can no longer size the electrical path and the cooling path independently, because the electrical path is a heat source the cooling path must service.

Deep dive: why 48V and not 12V or 380V inside the rack

The in-rack bus voltage is a three-way optimization between resistive loss, conversion efficiency, and human safety, and 48V is where the OCP ecosystem landed for good reasons. Against 12V (the legacy server-distribution bus): 48V is 4× the voltage, so for the same delivered power it carries one-quarter the current and dissipates one-sixteenth the I²R loss in the bus — a decisive win as rack power climbed past 30 kW. The 12V bus simply could not carry NVL72-class current without absurd copper. Against a higher DC bus (380V/±400V): those raise efficiency further and are exactly where the roadmap is going for rack-to-rack and facility distribution — but they cross the 60V SELV (safety extra-low voltage) line. Above 60V DC, contact-voltage shock controls change materially and DC arc interruption remains a design constraint. Forty-eight volts sits below that voltage boundary, but blind-mate capability is not permission for routine hot service: the available fault current, clearing time, stored energy, conductive-tool exposure, task, and listed manufacturer procedure still determine isolation and PPE.

The architectural consequence is that 48V remains within the stated SELV contact-voltage class, while ±400V and 800V DC add a high-voltage shock regime to hazards already present on the high-current 48V bus. Every voltage class therefore needs its own protection, isolation, grounding, fault-current, stored-energy, tool-control, and service procedure basis; Chapter 4.7 and the protection/grounding treatment in Chapter 4.11 cover the additional requirements once distribution rises above 48V DC.

Deep dive: the liquid-cooled busbar as thermal-electrical co-design

A conventional busbar is sized by two limits: it must carry the current without exceeding a temperature rise (typically holding the bar under ~30°C rise over ambient by natural convection and radiation), and it must hold voltage droop within spec. Both limits relax if you can pull heat out of the bar actively. That is the entire idea of the liquid-cooled busbar: a coolant channel — fed from the same warm-water technology-cooling loop that services the cold plates (see Chapter 5.4) — runs in thermal contact with the conductor, so the bar can run at a higher current density without thermal runaway. The win is double: less copper for the same current (the bar is no longer convection-limited), and a smaller, lighter bus that fits the rack envelope at megawatt power.

The cost is that the busbar is now a wet, serviceable, leak-relevant component sitting next to live conductors and signal cabling. It inherits the entire liquid-cooling reliability burden — quick-disconnects, leak detection, flushing and commissioning — and it couples the electrical and mechanical commissioning sequences that used to be independent. You can no longer energize the bus and fill the loop on separate schedules with separate teams; the bar's current rating is now conditional on coolant flow. This is the LV-distribution face of the broader truth that at AI density the power plant and the cooling plant stop being two systems and become one. The transient-stability and setpoint interaction between the electrical load steps and the cooling controls is treated in Chapter 5.12, and the on-package origin of the load steps the busbar must feed is in Chapter 7.12.

Two cross-cutting practices close the chapter. First, phase balancing can recover capacity otherwise stranded on the most-loaded pole. Three-phase racks draw on three poles, and IT load rarely distributes itself evenly across them; one phase can reach its declared limit while the other two remain below theirs. Intelligent PDUs that report per-phase current let operators rebalance the plug-up and verify every phase against the listing, conductor and breaker ratings, load classification, ambient and grouping derating, applicable code, and project protection basis. Second, grounding and bonding of the busway and rack-PDU chassis is not optional housekeeping: at these fault currents the bonding path determines whether a ground fault clears safely or arcs, and the whole earthing, SPD, and EMC treatment lives in Chapter 4.11. The LV layer is where the power chain finally touches the chip, and it is where small, poured-in-place decisions about copper and voltage decide how much of your expensive upstream capacity ever reaches the GPUs.

This chapter is the LV terminus of the power chain that begins at the utility tie in Chapter 4.2, steps down through the transformers and harmonic-management of Chapter 4.4, and rides through the UPS and energy-storage layer of Chapter 4.5. The voltage-class logic that motivates 415V PDUs and the 48V bus generalizes into the DC revolution — ±400V Mt. Diablo, 800V, and the disaggregated sidecar — in Chapter 4.7; the protection, grounding, and ground-fault monitoring that the bus inherits the moment it exceeds 48V are in Chapter 4.11; and the branch-circuit and outlet metering that recovers stranded rack capacity feeds the power-quality and DCIM layer of Chapter 4.12. The density numbers that drive the I²R wall come from Chapter 5.1; the warm-water loop that cools the liquid busbar is engineered in Chapter 5.4; the load-step transients the busbar must feed originate on-package in Chapter 7.12; and the redundancy rethink behind single- vs dual-corded racks is in Chapter 12.2.
Cite this chapter
Fehn, J. (2026). LV Distribution: Busway, PDUs, RPPs & Rack Power (Chapter 4.6). The Definitive Guide to AI Data Centers. https://aidatacenterguide.com/part-4-electrical-and-energy-infrastructure/4-6-lv-distribution-busway-pdus-rpps-and-rack-power (accessed 2026-08-28).
@misc{aidc-4-6,
  author       = {Fehn, Jacob},
  title        = {LV Distribution: Busway, PDUs, RPPs & Rack Power (Chapter 4.6)},
  howpublished = {The Definitive Guide to AI Data Centers},
  year         = {2026},
  url          = {https://aidatacenterguide.com/part-4-electrical-and-energy-infrastructure/4-6-lv-distribution-busway-pdus-rpps-and-rack-power},
  note         = {Accessed 2026-08-28}
}
Spotted an error? Suggest an edit