Electrical Power Acceptance (L3/L4)

By the time a cluster reaches electrical acceptance, the power chain has been designed, studied, manufactured, installed, and point-to-point checked. Every component has a datasheet that says it works. Electrical acceptance — Levels 3 and 4 in the commissioning taxonomy of Chapter 13.1 — is where that paper is converted into instrumented evidence. L3 is standalone (pre-functional): each subsystem is energized and operated on its own (the switchgear racks and trips, the generator starts and assumes load, the UPS transfers and rides through), proving the component does what its sequence of operations says it does. L4 is functional performance: the electrical subsystems are operated together under load within the discipline, proving that a utility loss, a generator start, a transfer, and a UPS ride-through chain into one another without a gap the IT load can feel — cross-discipline integration is reserved for the L5 IST (Chapter 13.6). The question here is what "under load" must mean for an AI facility, because the load this building was designed for sits outside anything a conventional data-center commissioning script was written to test.

At every gate there is a choice between a cheaper, faster acceptance that proves the steady-state case and a more expensive, slower one that proves the dynamic case. The cheap path collects its bill months later, at the first real workload, when a synchronized load step the load banks never reproduced trips an under-voltage relay, sags a UPS, or de-syncs a generator paralleling scheme, and the operator discovers that an L4 sign-off certified a building that cannot actually hold its design load. The sections below walk the chain in energization order (utility, switchgear, generators, UPS/BESS), then the three decisions specific to AI: load-bank realism, redundancy-topology validation under load, and protection/arc-flash verification against the study. It closes on the acceptance criterion conventional commissioning has no vocabulary for: dynamic-load-swing tolerance.

Electrical acceptance follows the direction power flows, and each stage is a prerequisite for the next — you cannot commission the UPS until the switchgear that feeds it is accepted, and you cannot commission the switchgear until the utility or generators can energize it. The sequence is a dependency chain, and a deficiency anywhere upstream stalls everything below it.

Utility energization (backfeed / first energization). The interconnect and on-site substation (Chapter 4.2) are energized for the first time — often by backfeeding the customer transformer from the utility side, with the utility's protection and the customer's relays both live. This is the single highest-energy moment in the build: the first time full fault current is available behind the customer's breakers. Acceptance here is dominated by protection — relay settings loaded and verified, CT/PT ratios and polarity confirmed, the trip scheme proven to operate before the bus is left energized. Get the polarity of a differential CT wrong and the first through-fault, not the commissioning team, finds it.

Switchgear commissioning. Medium- and low-voltage switchgear and the busway/PDU distribution (Chapter 4.6) are tested to ANSI/NETA ATS — the acceptance-testing specification that the industry treats as the as-installed bar. Insulation resistance and the equipment/OEM-approved dielectric test establish the tested insulation condition after shipping and installation; DC hi-pot is not a universal choice for every cable or electronic assembly; contact-resistance (ductor) testing on every bolted joint catches the loose lug that becomes a hot spot; breaker timing and trip verification prove the mechanism operates within spec; and, critically, primary injection proves the protective relays trip on real current, not just on a settings file. NETA ATS-2025 is explicit that data centers, with thousands of low-voltage breakers, generate a substantial deficiency count even at a small per-device failure rate — the punch-list management of Chapter 13.2 is the only way to track which of 3,000 breakers has been proven and which has not.

Generator commissioning. Each generating set is started, run, and load-tested — first on its own load bank (L3), then in parallel and onto the building (L4). Cold-start time to accept load, voltage and frequency recovery on a block load step, fuel-system and exhaust acceptance, and protection (reverse-power, loss-of-field, over/under-frequency) are all proven. For AI sites that lean on on-site generation as prime or island power, the paralleling and load-sharing acceptance is deep enough to warrant its own treatment in Chapter 13.4; here the gate is simply that the gensets can pick up the design block load within the voltage and frequency window the UPS downstream can tolerate.

UPS and BESS commissioning. The ride-through layer (Chapter 4.5) is the last electrical subsystem and the one the IT load is most intimate with. The acceptance set is the battery/capacitor discharge test to proven autonomy, the transfer tests (normal-to-bypass, bypass-to-normal, and the all-important loss-of-utility transfer that hands off to the generator), the harmonic and power-factor behavior under non-linear load, and — for the increasingly common BESS layer — the fast-response transient-absorption behavior that conventional double-conversion UPS was never asked to provide. This is where the AI-specific acceptance criteria start to bite, because it is the UPS/BESS that must absorb the GPU load swing the gensets and the grid cannot follow fast enough.

A load bank is how you put load on the power chain before the GPUs arrive (or before you dare put them at risk). The choice of load-bank technology is a choice about which question you are answering, and the answers overlap: impedance, switching capability and heat-rejection path are separate specifications.

Resistive load banks dissipate real power (kW) as heat through resistive elements at unity power factor. They are the workhorse of data-center commissioning: cheap, robust, and sufficient to prove that the transformers, switchgear, busway, and cooling can carry the design kW and reject the design heat. What they cannot do is load the power chain reactively — they draw no VARs — so they exercise the real-power capability of the chain and nothing about how it behaves under the leading/lagging and harmonic-rich conditions a real GPU power supply imposes.

Reactive load banks add inductive (and sometimes capacitive) load, letting the commissioning team test the chain at a realistic, non-unity power factor — at the specified lagging or leading power factor. Generator sets and UPS are rated in kVA, not kW: for an illustrative 0.8 PF load, 100% rated kW requires 1/0.8 = 1.25 times that kW in kVA; compare this apparent load to the actual generator/UPS rating. Reactive load banks prove the generator's automatic voltage regulator, the UPS's VAR handling, and the transformer's heating under the apparent-power load the equipment is actually rated for. Whether a resistive or reactive bank also proves the transient is a question about its switching granularity, control bandwidth and slew rate — conventional banks do perform load-step tests — so specify the step size, rate and repetition you need rather than letting the technology class settle it.

AI-load-emulating (dynamic) load banks are the newest and least standardized class. They are designed to reproduce the workload's electrical fingerprint — programmable, fast load steps that mimic the synchronized ramp-up, steady-state oscillation, and abrupt ramp-down of a GPU cluster entering and leaving collective operations. They exercise the di/dt the power chain was designed to survive only where their measured step size, slew and repetition cover it; switched resistive and reactive banks also prove transients inside their switching envelope: the under-voltage and frequency excursions on a step load, the UPS/BESS transient-absorption response, the generator's load-acceptance and load-rejection recovery, and the interaction between rack-level capacitance and facility-level storage. They are more expensive and harder to source, and they do not perfectly reproduce the target cluster. Use them to prove the declared surrogate transient envelope, then close residual normal-operation evidence with a staged production-representative run in Chapter 13.9; keep hazardous protective-function tests in injection/HIL or an isolated controlled scope.

The practical pattern at a 2026 AI site is layered, not single-choice. Resistive banks prove capacity and that the cooling can reject the heat (the resistive banks most facility scopes specify reject to air, which is itself a realism limit — liquid-cooled banks exist and are the tool for the loop-side proof, treated in Chapter 13.5). Reactive banks prove the generator and UPS at their kVA ratings. Then fixtures capable of the required steps prove the transient envelope; any remaining duty is explicitly assigned to a valid test at IST (Chapter 13.6) and ultimately to the first proxy training run (Chapter 13.9), which loads the chain with the real, software-synchronized cluster after its protective functions pass. The decision a strategist signs off is how much of the transient risk to retire at L4 (expensive, but caught before GPUs are at risk) versus how much to carry into IST and first-workload (cheaper to commission, but discovered with $100M+ of accelerators energized).

A redundancy topology — N+1, 2N, distributed-redundant, or the catalog of fault-domain designs in Chapter 12.1 — is a claim that the load survives the loss of any one (or any block of) components. The drawing makes the claim; L4 acceptance is where you make the claim true by proving isolation and transfer behavior with secondary injection, simulation, test sources, and staged load banks before any specifically approved live-load demonstration and watching whether the load notices. The scoping question is how aggressively you test: which transfers and source losses you genuinely trip versus which you accept on the single-line diagram's authority.

The acceptance set, in ascending order of how much it tells you and how much it risks: (1) controlled transfers — operate every static transfer switch, automatic transfer switch, and breaker tie through its full sequence under load, confirming break/make timing and that no downstream bus drops; (2) single-source loss — simulate or open an approved test source at a defined boundary, a UPS module, a CDU power feed, or a PDU and confirm the redundant path picks up within the IT load's ride-through window; (3) approved single-fault and specifically justified combined-fault cases — the IST-grade test (Chapter 13.6) where you stack faults to confirm the topology survives the design-basis worst case, up to the whole-system utility-loss proof selected by the approved risk-based test plan. For an AI cluster, workload recovery changes the consequence of a failed test state but does not erase the state from the acceptance basis. Checkpoint-and-resume after a node failure is not proof that a distribution-path or whole-hall interruption meets the service objective. L4 must prove the named topology states—transfer interruption, post-event loading, path and control independence, common modes, and recovery—while workload and fleet resilience are proven separately and then exercised end to end.

The protection coordination study and the arc-flash incident-energy study (produced in Chapter 4.11) are analytical artifacts: they specify relay settings, breaker trip curves, and PPE/labeling on the assumption that the as-built plant matches the model. Electrical acceptance is where that assumption is tested. Verification depth is the real choice: confirm coordination by reading settings back from the relays (fast, cheap, and proves only that someone typed the right numbers) versus proving it by primary injection and recorded event data (slow, expensive, and proves the device actually trips at the studied current in the studied time).

The acceptance set is concrete. Settings verification: every protective relay's pickup, time-dial, and curve is read back and reconciled against the coordination study — and against the device labeling, because NETA ATS is explicit that mislabeled or mis-addressed devices are a primary cause of lost selective coordination. Primary/secondary injection: current is injected to confirm the relay operates within the study's time-current band, so that a downstream fault is cleared by the nearest upstream device and not by one two levels up that would needlessly drop a whole bus. Coordination proof under fault: controlled functional demonstrations — injected or simulated fault current at the study's coordination points, with the relay event records showing which device operated first — close the gap between a correct settings file and selective behaviour. Creating a real high-energy fault in the installed plant is not the required final proof; the evidence package is the as-built study inputs, the settings and wiring verification, the device and chain injection tests, and those demonstrations, each named against the uncertainty it closes and the one it leaves open. Arc-flash verification: the as-built clearing times from those injection tests feed back into the incident-energy calculation, because arc-flash energy scales with clearing time — a relay that trips slower than the study assumed raises the incident energy at that bus, which can invalidate the PPE category on the label a technician is relying on. Acceptance is therefore not just "the relay trips"; it is "the relay trips fast enough that the arc-flash labels on this gear are still true."

Conventional data-center commissioning has no script for this criterion, which also makes it the one most likely to be skipped — because the load banks that most scopes specify cannot produce it and the relays that would trip on it are upstream of the IT the script focuses on. A modern rack actively fights its own transients: the GB300 NVL72 power shelf carries roughly 65 J/GPU of electrolytic capacitance — about half the PSU volume — and combines it with power-capping on ramp-up and a deliberate "GPU burn" on ramp-down to taper the load gracefully, cutting peak grid demand by up to 30% in NVIDIA's instrumented GB200/Megatron demonstration of those GB300 power-shelf features. The Vera Rubin generation pushes rack storage to ~400 J/GPU (≈6x) with closed-loop state-of-charge control. Behind the rack, facility BESS provides the next layer of fast-response absorption (Chapter 4.5). Together these form a layered mitigation stack — rack capacitance, then BBU/UPS, then facility BESS — and electrical acceptance is where you prove the stack actually engages and that the residual swing it does not absorb stays inside the power chain's tolerance.

The acceptance criteria, written as quantitative pass/fail gates in the L4 script (the script anatomy is Chapter 13.2): the voltage excursion at the bus on a defined load step stays within band; the frequency excursion (on generator or island power) stays within the relay's no-trip window; the UPS/BESS sources the swing without dropping to bypass or sagging the output; the rack-level smoothing holds the contracted upstream peak and slew under the declared waveform and initial storage state; and no protective relay anywhere in the chain trips on the largest synchronized step the cluster can produce. A load bank — even a dynamic one — can approximate these steps but cannot reproduce the exact, software-driven, thousands-of-GPUs-in-lockstep spectrum of a real workload. That is why this gate spans complementary evidence: dynamic load banks at L4 retire the bounded gross-transient case; IST combines only the approved interactions inside an isolated or otherwise protected test boundary; and product-representative emulation or a staged workload validates the remaining electrical/thermal behavior, with live high-energy testing exceptional and governed by explicit authority, hold points, and abort criteria (Chapter 13.6; Chapter 13.9). Where to draw that line is the call; draw it too early and the cluster's first real all-reduce is also its first real transient test.

E-01 trace. The electrical lead freezes the one-line boundary, protection/settings version, fixture waveform and storage state; the test authority verifies isolation, backfeed prevention, abort and restore paths. Simulate loss of the upstream test source at t = 0 while commanding the load step. Energy delivered by the UPS is (1.00 MW × 2.0 s) + (0.80 MW × 10.0 s) = 10 MJ, below the assumed 30 MJ usable output reserve. Apply uncertainty to the captured extrema: 0.925 − 0.005 = 0.920 pu ≥0.90 pu; 59.6 − 0.1 = 59.5 Hz and 60.3 + 0.1 = 60.4 Hz stay inside the frequency band; 12.0 + 0.1 = 12.1 s ≤15.0 s. Simulated bypass and unexpected-trip counts are zero.

Result and action. The simulated profile passes the stated gates; the installed release remains HOLD until attributable raw waveforms, relay/breaker events, storage telemetry, calibration and witness records exist. Stop on a boundary violation, unexpected trip or excursion; restore the approved source state, remove the step, recharge the UPS and repeat the baseline before further tests. The example roles are electrical lead, CxA and owner's release authority; none has signed this record. The method follows NETA's equipment-scoped acceptance framework and Chapter 13.2's evidence contract, not an invented NETA voltage threshold.

Flip. With ±0.005 pu uncertainty, the indicated minimum must be at least 0.905 pu. A simulated 0.904 pu gives 0.899 pu and fails even if transfer completes at 12.0 s. Correct the transfer response and repeat dependent tests; carrying that miss into a GPU run buys an earlier start at the cost of an unproven ride-through boundary. Chapter 13.4 adds the separate island reference and reconnection record.

For an AI facility, electrical acceptance is a recurring gate the density ramp re-opens with every GPU generation, not a one-time event. A power chain accepted for GB300 NVL72 at NVIDIA's facility design basis of up to 142 kW and Lenovo's 155 kW peak faces a different acceptance problem for VR200 NVL72, now in full production, at NVIDIA's 330 kW cabinet TDP facility design basis and Pegatron's 228 kW Max P; Rubin Ultra/Kyber adds an announced ~600 kW H2 2027 roadmap planning point on 800 VDC. GB200 is the installed base the substrate was originally accepted against, not the generation setting today's gate. Every density change requires a new normal-load and transient-load acceptance profile; recalculate short-circuit duty, protection coordination, relay-injection scope, and arc-flash energy only when the source/network model, equipment, settings, or operating configuration changes. The irreversible electrical substrate — the interconnect capacity, the voltage class, the switchgear fault rating, the busway ampacity — has to be accepted not just for today's load but for the ramp it must absorb (the density-ramp trap of Chapter 12.1). The strategist's acceptance decision is therefore forward-looking: do you commission the protection and the transient envelope against the generation you are installing, or against the headroom the substrate must eventually carry? Accepting only to today's load is cheaper and re-opens the gate at every refresh; accepting to the substrate's ceiling is more expensive now and retires that capacity test early; a new rack generation still requires its own transient and interface acceptance.