Chapter 7.12
In this chapter · 5 sections
On-Package Power Delivery & Power Integrity
At a sub-1 V core rail carrying roughly 2,000 A, a short resistive path still wastes I²R power and excess droop throttles the accelerator; budget the upstream 48 V shelf and the propagated transient separately.
What you'll decide here
- Where you convert 48V to core voltage — board-edge multiphase VRM, lateral power-on-package, or vertical power delivery underneath the die — and therefore how much of your delivered watts you lose to I²R before they ever reach a transistor.
- Whether to design for frontside or backside power delivery (BSPDN) at the silicon level — a process-node decision made years upstream that sets your achievable IR-drop floor and free routing budget.
- Your PDN impedance target across frequency (the sub-milliohm flat-impedance line) and the decoupling hierarchy — bulk, package, on-die MIM/deep-trench — that hits it without anti-resonance.
- How much on-package and on-shelf capacitance to budget against the worst-case di/dt load step — the joules-per-GPU number that buys you ride-through and grid-transient smoothing, and the volume/cost it consumes.
- Whether the load step is mitigated at the chip (capacitance, load-line, adaptive clocking) or pushed upward as a synchronized transient the facility BBU/BESS spine has to absorb — and who owns which decibel of the attenuation budget.
Everything upstream — the substation, the 800 VDC spine, the busbar, the power shelf — exists to deliver clean voltage to the pins of the accelerator package. The accelerator does not run on the 48V it receives there; its core rail sits around 0.6–0.9V, and at the power levels of a 2026-class GPU that means a steady-state core current in the thousands of amps (peak demands reach ~2,000A today, with typical parts in the 500–2,000A band; roadmap parts push past 2,000A). On-package power delivery converts 48V to sub-1V at multi-kiloamp current, as physically close to the die as manufacturing allows, while holding the rail flat through load steps that swing hundreds of amps in nanoseconds — the least-visible, highest-stakes meter of the entire power chain.
The action here plays out at the millimeter and microsecond scale. The path runs from board 48V down to core (multiphase VRMs and smart power stages), through the architectural fork between lateral and vertical power delivery and the silicon-level move to backside power (BSPDN), to the PDN impedance target and the decoupling hierarchy that meets it, and finally to the physics of the load-line, Vdroop, and the di/dt event. That last one reads end-to-end: the on-die di/dt event is the same physical phenomenon that, summed across 72 GPUs stepping in lockstep, becomes the synchronized facility transient the BBU/BESS spine must absorb. Guess wrong at any layer and you either strand silicon performance or present a grid-disturbing load that earns a worse interconnection deal.
Board 48V to core: multiphase VRMs and smart power stages
The conventional answer, inherited from the server world, is the multiphase buck VRM: a digital controller drives N interleaved phases, each phase a high-side/low-side MOSFET pair (now integrated as a smart power stage, or DrMOS, with current/temperature telemetry built in) feeding an inductor, all summing into a shared output rail. Interleaving the phases multiplies the effective switching frequency at the output and shrinks the output ripple, so more phases buy you a tighter rail and more current — at the cost of board area, gate-drive losses, and controller complexity. A modern GPU core rail can demand 16, 20, or more phases just to source the current without melting any single power stage.
Two design moves dominate here. First, 48V direct conversion versus a two-stage 48V→12V→core path: the industry has decisively moved to higher distribution voltage (48V over the legacy 12V) because at constant power, quadrupling the voltage cuts distribution current by 4x and therefore I²R loss in the board copper by 16x. Direct 48V-to-core conversion (single-stage) saves the intermediate-bus-converter losses but stresses the duty cycle; two-stage is more forgiving but adds a conversion. Second, the load-line (also called adaptive voltage positioning): deliberately programming the regulator so the delivered voltage droops with load current along a defined slope. This is counterintuitive — you are intentionally lowering voltage as current rises — but it can reduce the transient excursion by pre-positioning the rail within the negotiated load-line budget, and it lets the silicon run at the lowest voltage that still meets timing, which is pure power savings. The load-line slope is a negotiated number between the silicon vendor (who owns the timing margin) and the power team (who owns the regulator), and getting it wrong either burns power or causes timing failures under transient.
Lateral, vertical, and the move to power-from-below
Where the final 48V-to-core conversion physically sits is the central architectural choice, three placements whose current path, thermal path and service boundary must be compared.
Board-edge multiphase is the legacy position: the VRM lives on the motherboard, current travels through the socket/connector and across the package to the die. Cheap, serviceable, well-understood — and increasingly untenable as core current climbs, because the PDN resistance from board edge to die dominates the loss budget. Lateral power-on-package moves current-multiplier modules onto the package substrate itself, flanking the die on the north/south or east/west edges, so the final conversion happens millimeters away. Vertical power delivery (VPD) is one placement option: the conversion modules sit directly underneath the processor, feeding current straight up into the die with the shortest possible path. ASE patent US11848296B2 (published December 19, 2023) models one embodiment with 66% lower ESR and 42.8% lower ESL. That result cannot establish total-system efficiency: the rail and shelf loss ledger must keep their boundaries separate.
A separate silicon-level choice is backside power delivery network (BSPDN) — routing the power rails on the back of the wafer, beneath the transistors, instead of competing for the same congested metal stack as signal routing on top. Intel ships it as PowerVia on the 18A node (in Panther Lake client parts as of early 2026); TSMC's Super Power Rail arrives with the A16 node, whose volume production slipped to 2027 on TSMC's April-2026 roadmap (from an original 2H-2026 target); Samsung's SF2Z targets 2027. The payoff is twofold: Intel’s particular test chip reported roughly 30% lower IR droop. This is not a converter-efficiency gain. Moving power routing to the backside also frees frontside tracks for signals. Together, lower droop and more signal-routing space improve power integrity and logic density. The catch is thermal — the selected backside stack and cooling orientation determine which layers lie between active devices and the cold plate, complicating the already-tight thermal budget covered in Chapter 5.4.
| Position | Physical boundary | Path resistance / voltage droop (stated boundary) | Reported loss or performance result | Downstream consequence |
|---|---|---|---|---|
| Board-edge multiphase | Motherboard, across socket + package | Depends on actual path | — | Serviceable and cheap; loss budget caps achievable core current |
| Lateral power-on-package | Package substrate, flanking the die | Large reduction (modules at die edge) | No universal system saving | Consumes package edge area; substrate routing complexity rises |
| Vertical power delivery (VPD) | Directly under the die | ASE patent embodiment: ESR −66%; ESL −42.8% | Simulated path; not system efficiency | Highest density; couples power and thermal under the die; serviceability hardest |
| Backside power (BSPDN) | On-wafer, beneath the transistors | Cuts on-die IR droop ~30% | Intel PowerVia test chip: 6% frequency benefit (June 2023); not converter efficiency | Process-node decision (18A / A16 / SF2Z); qualify the complete thermal stack |
The table is a current-path comparison. As core current climbs generation over generation, the loss in any position grows as I², making resistance and transient control more consequential. VPD and BSPDN address different boundaries; a roadmap 600 kW Kyber rack rating cannot by itself choose a GPU converter position. At 2,000 A and an assumed 100 µΩ path, I²R = (2,000 A)² × 100 × 10⁻⁶ Ω = 400 W in that path, not a percentage of rack loss. The density ramp covered in Chapter 7.1 is, at the package level, a rail-current and thermal-budget test of these choices.
The PDN impedance target and the decoupling hierarchy
Power integrity reduces to one specification: hold the core rail inside its noise window across every frequency at which the load draws current. The load is a digital engine that switches at GHz and gates entire tiles on and off at MHz, so its current demand has spectral content from DC up past 100 MHz. The governing design rule is the target impedance: Z_target = ΔV_allowed / ΔI_max. For a sub-1V rail with a tight noise budget and a multi-hundred-amp transient, that target lands in the sub-milliohm range — often well under 1 mΩ out to 100 MHz, and into the microohm range at DC. The job of the PDN is to present a flat impedance below that line across the whole band. Any frequency where impedance pokes above the line is a frequency where a load step produces a droop that violates the noise budget — and droop, in a clocked machine, means a timing failure, which means you either lower the clock (lost performance) or raise the voltage (lost power).
No single component holds sub-milliohm flat across nine decades of frequency, so the PDN is a hierarchy of decoupling, each tier owning a frequency band:
- Bulk capacitance (board, µs–ms band): large electrolytic/polymer caps near the VRM that hold the rail through the regulator's own control-loop response time. This is also where the load-step ride-through energy lives.
- Mid-frequency ceramics (package + board, ~MHz band): MLCCs spread across the package and board backside, bridging the gap between bulk caps and on-die caps. This band is where anti-resonance bites: the parasitic inductance of one tier resonates against the capacitance of the next, producing an impedance peak exactly where you need a valley.
- On-die decoupling (>100 MHz band): MIM and deep-trench capacitors integrated into the silicon, the only thing fast enough to respond to the highest-frequency current steps. As package and board parasitic inductance increasingly dominate, the burden shifts on-die — and the newest accelerators add on-die voltage telemetry to report rail quality in real time so the system can adapt.
The decision here is the on-package capacitance budget: how much die area and package real estate you spend on decoupling versus logic and signal. Spend too little and you fail target impedance and droop; spend too much and you sacrifice die area (the most expensive real estate on the package) or package complexity. This budget is co-designed with the load-line slope and the VRM phase count — three knobs that together must close the impedance target.
Load-line, Vdroop, and the di/dt event
The physics ties it all together. A GPU running a synchronous training step does not draw constant current; it draws current that tracks the workload: when thousands of cores fire together at the start of a matrix-multiply tile, current can step hundreds of amps in nanoseconds to microseconds. That rate of change of current is di/dt, and across the inductance of the PDN it generates a voltage transient: V = L·di/dt. A fast load step pulls the rail down (Vdroop); the sudden release at the end of a compute burst lets it overshoot up. Either excursion outside the noise window is a fault.
Three lines of defense, in order of speed. On-die capacitance handles the fastest edge — it is the only charge reservoir close enough to respond in nanoseconds. The load-line pre-positions the rail so the droop lands inside budget rather than below it. Adaptive clocking / droop detection is the last resort: dedicated on-die circuits sense an impending droop and momentarily stretch the clock to ride it out, trading performance for rail margin within the validated protection behavior; excessive droop can still fault. The accelerator vendor co-designs all three; the data-center engineer inherits the result as a power profile — a characteristic spike-and-idle waveform whose contracted amplitude, duration, repetition and slew must be supplied and tested, because they have consequences three layers up.
Scope & caveats
Separate rail and shelf boundaries. Unsupported sensitivities and rationale are in the opening callout; Chapter 4.7 owns the interface. Ideal screens exclude component tolerance, aging and dynamic validation.
Core output = 0.80 V × 2,000 A = 1.6 kW; path loss = (2,000 A)² × 20 µΩ = 80 W. The 1,000 A step adds 20 mV resistive drop and 10 pH × (1,000 A/1 µs) = 10 mV inductive drop: 30 mV against the 40 mV allowance. Shelf input = 120/0.96 = 125 kW, with 5 kW conversion heat. The added 20 kW for 10 ms needs 200 J. The ideal requirement C ≥ 2×200/(50²−46²) F lies between 1.0 and 1.1 F: 1.0 F supplies 192 J and fails, while 1.1 F supplies about 210 J and clears this ideal screen. At 95% efficiency shelf input is about 126 kW and fails; 96% is the exact input-power threshold. Capacitance does not reduce steady input energy.
Scope & caveats
Core output = 0.80 V × 2,000 A = 1.6 kW; path loss = (2,000 A)² × 20 µΩ = 80 W. The 1,000 A step adds 20 mV resistive drop and 10 pH × (1,000 A/1 µs) = 10 mV inductive drop: 30 mV against the 40 mV allowance. Shelf input = 120/0.96 = 125 kW, with 5 kW conversion heat. The added 20 kW for 10 ms needs 200 J. The ideal requirement C ≥ 2×200/(50²−46²) F lies between 1.0 and 1.1 F: 1.0 F supplies 192 J and fails, while 1.1 F supplies about 210 J and clears this ideal screen. At 95% efficiency shelf input is about 126 kW and fails; 96% is the exact input-power threshold. Capacitance does not reduce steady input energy.
Keep the path and shelf candidates for dynamic validation; measure impedance, control-loop response, capacitor tolerance/ESR, protection and repeated-pulse duty. Do not add the 80 W rail loss to an independently quoted shelf boundary without tracing where that loss is already included. Hand the complete loss ledger to 4.1 and the rack waveform/interface to 4.7.
Method: Texas Instruments, power-management fundamentals. Chapter 4.7 owns the next handoff.
Scope & caveats
NVIDIA's July 2025 demonstration instrumented a GB200 rack carrying the new GB300 power shelf and ran a Megatron workload; it is not a comparison of a GB300 rack against a GB200 rack. One workload and one instrumented setup — qualify the installed load and smoothing controls at L4 rather than budgeting the reduction from a rack choice.
Scope & caveats
backside-power droop cut
Scope & caveats
Specific patent embodiment and comparison; no general rack efficiency, power-loss or availability guarantee.
Scope & caveats
Load loss as seen by the grid. NERC's incident review ('Load Details') found the affected data centers transferred their loads to backup power — static UPS, decentralized rack UPS, or DRUPS — in response to the disturbance. The figure is a loss of demand at the interconnection, not evidence that IT power was interrupted or that training jobs restarted.
The approximately 1,500 MW is the total customer-side load reduction coincident with the six-fault sequence; NERC reports approximately 1,260 MW as the sustained drop at the third voltage depression. The NERC-investigated canonical case. A second, larger occurrence followed on 2026-07-22: ~3.8 GW dropped on a single normally-cleared Ashburn 230 kV fault (see companion key number). Two vintages of the same failure mode, not a replacement figure.
Deep dive: the di/dt attenuation budget as a layered allocation problem
Think of the synchronized transient as a single quantity of 'swing' that must be attenuated by some total factor between the transistor and the utility meter, and the engineering question is which layer absorbs which decibel. The budget is allocated top-to-bottom across five reservoirs, each with a characteristic timescale, and the design discipline is to make each layer absorb the band it is fast enough to handle and no slower.
- On-die MIM/deep-trench caps (ns): the fastest edge. Picofarads-to-nanofarads, but the only thing in the loop fast enough for the leading edge of a tile firing.
- Package + board decoupling (ns–µs): MLCCs and bulk caps that hold the rail through the VRM's control-loop latency.
- On-shelf energy storage (µs–ms): the GB300's 65 J/GPU of electrolytic capacitance in the power shelf — charges during idle, discharges into spikes, smoothing the rack-level waveform and cutting peak grid draw 30%.
- Rack/row BBU (ms–s): battery backup units that ride through brownouts and shave the slower envelope of the load swing.
- Facility BESS + software ramp-rate caps (s+): grid-scale storage plus firmware that deliberately limits how fast the cluster is allowed to ramp, so the utility never sees a step it cannot tolerate.
The consequence is an allocation rule: every joule you do not store low in the stack you must store higher, where it is bulkier and more expensive per joule, or export to the grid, where it costs you in interconnection terms and ride-through compliance. Conversely, over-provisioning on-package capacitance to absorb a slow transient that the BBU handles better is wasted die area. The cheapest design allocates each band to the smallest, fastest reservoir that can hold it. This is the canonical statement of the chip→BBU→BESS spine; the facility end of it — ride-through, ramp-rate compliance, and transient absorption — is engineered in Chapter 4.5, which back-refs here for the physical origin.
Deep dive: why ramp smoothing is a goodput decision, not just a grid courtesy
It is tempting to file power-transient smoothing under 'being a good grid citizen' — soften the spikes so the utility is happy. That framing undersells it: smoothing has a direct goodput consequence. Two reasons. First, an operator whose load presents a violent, synchronized di/dt to the grid is a worse interconnection counterparty: utilities increasingly require ride-through capability and may impose ramp-rate limits or worse terms (or deny capacity) to loads that destabilize the local grid — and interconnection capacity is the scarcest asset in the project, per the interconnection-queue dynamics in Chapter 3.2. Smoothing the transient literally buys you faster, cheaper power.
Second, the on-die end of the same problem caps clock. If the PDN cannot hold the rail through the worst-case di/dt, the silicon must either run at a higher guard-band voltage (burning power, lowering perf/watt) or drop clock under transient via adaptive clocking (lowering throughput directly). A GPU that droops is a GPU that is not computing at its rated rate — pure goodput loss. So the same capacitance and load-line investment that smooths the grid-facing waveform also lets the silicon run at its lowest reliable voltage and highest reliable clock. The chip-side power integrity and the facility-side transient mitigation are two ends of one optimization, and treating them separately is how operators end up over-spending on facility storage to paper over a chip-rail that was under-decoupled — or vice versa.
Where this sits in the power chain
On-package power delivery is the terminal node of a chain that this guide reads end-to-end. Upstream of the package, the 800 VDC spine, the disaggregated sidecar power, and the busbar that feed the shelf are covered in Chapter 4.7; the LV distribution, PDUs, and rack power that deliver 48V to the board are in Chapter 4.6; and the UPS / energy-storage layer that absorbs the slow envelope of the transient — the facility end of the di/dt spine that starts on the die in this chapter — is in Chapter 4.5. The accelerator whose rail we are feeding is taxonomized in Chapter 7.1; the thermal path that now runs through the backside power layer is engineered in Chapter 5.4 against the density wall of Chapter 5.1. The forward roadmap — where core current, VPD adoption, and BSPDN go through 2030 — is consolidated in Chapter 16.2.
Cite this chapter
Fehn, J. (2026). On-Package Power Delivery & Power Integrity (Chapter 7.12). The Definitive Guide to AI Data Centers. https://aidatacenterguide.com/part-7-compute-silicon-and-system-integration/7-12-on-package-power-delivery-and-power-integrity (accessed 2026-09-29).
@misc{aidc-7-12,
author = {Fehn, Jacob},
title = {On-Package Power Delivery & Power Integrity (Chapter 7.12)},
howpublished = {The Definitive Guide to AI Data Centers},
year = {2026},
url = {https://aidatacenterguide.com/part-7-compute-silicon-and-system-integration/7-12-on-package-power-delivery-and-power-integrity},
note = {Accessed 2026-09-29}
}