ANVILFIELD Try FieldOS

Datacenter

GPU power transient tests for UPS and generators: field procedure

A repeatable field procedure for dynamic workloads, synchronized measurements, source-state tests and separate UPS, generator and bypass acceptance.

GPU power transientsUPS commissioningGenerator testingAI load steps

Direct answer

Accept the installed UPS and generator path only when critical-bus continuity, recovery, bypass synchronization and workload performance meet documented equipment limits and project requirements. Replay a defined workload while recording synchronized voltage, current, power, frequency and source-state signals. Repeat on utility, stored energy, generator supply, and approved transfers or degraded configurations.

On this pageHow do you test GPU power transients?GPU transient versus resistive load bank: what changes?Which standards and documents set acceptance?Which workload profiles should the field procedure use?How do you capture synchronized UPS and generator waveforms?Which source states and transfers must you test?What is a pass, hold, or stop?Worked example: what does the published 2.4 MW test show?Where should smoothing act: GPU, rack, or UPS?What must the synchronized recovery plots show?When must you retest?What should the scope, schedule, and estimate include?Field checklist and turnover dataset

How do you test GPU power transients?

Use six stages: freeze requirements, qualify input, verify measurement, run source states, judge requirements, and restore the plant. These stages follow Anvilfield procedure v1 (November 5, 2026). Add this electrical-demand test to the integrated systems test for whole-plant sequencing and cooling ride-through.

Mark the generator bus, every tested UPS rectifier input, UPS output and representative rack feeders on the installed one-line. Measure the actual bypass source, including a separate bus when fitted. Generator-terminal voltage does not establish conditions at another bypass bus.

Measure A and B demand and record PSU mode for dual-corded racks. Losing one path redistributes demand, so verify surviving-path headroom at that path rather than from aggregate hall power.

Freeze the configuration and the stop conditions

Record one-line revision, model/serial numbers, firmware, module count, governor/AVR mode, rectifier walk-in, charging limit, battery state and temperature, bypass window, synchronization settings and IT power caps. Complete generator acceptance and turnover and standalone UPS checks before integrated switching. Identify the standby generator boundary.

Write abort actions for critical-bus excursions, lost cooling, protection operation, depleted reserve and lost instrumentation. A missing limit holds the affected test. The test conductor directs the operator-approved switching sequence; the owner accepts results against the signed script.

For U.S. general-industry work, OSHA 29 CFR 1910.333(a), (b) and (c)(2), checked November 5, 2026, requires exposed live parts to be deenergized before work unless an allowed exception applies, with electrical isolation, lockout/tagout and qualified-person verification for deenergized work. Identify utility, generator, bypass and storage backfeeds before attaching or removing probes. Energized testing uses qualified personnel and the employer's applicable electrical work practices [P18].

OSHA 1910.334(c) requires qualified testers, inspected instruments/accessories, and ratings suitable for the circuit and environment; 1910.335 requires appropriate electrical protective equipment and guarding [P19, P20]. Use installed test points and a measurement chain with the required voltage, category and isolation ratings.

GPU transient versus resistive load bank: what changes?

A GPU workload adds edge speed, repetition and correlation to the sustained loading covered by conventional load-bank acceptance. Separate kW, kVA, true power factor, fundamental displacement PF with leading/lagging sign, and current distortion. Lagging reactive loading does not reproduce leading server-input behavior. A programmable bank represents only the characteristics actually delivered and measured.

What each load method proves
Load methodControlled inputsUseful evidenceMissing proofSource/basis
Steady resistive bankkW; nominal unity PFSustained engine/electrical loading and thermal holdGPU edge, repeated oscillation, leading PF, actual applicationP08/P09 for load-dependent response; Anvilfield comparison
Resistive/reactive bankkW and kVAR; specified leading/lagging configurationAlternator/excitation response at declared PFActual GPU timing unless switching/profile is qualifiedP17 pp. 6-9; Anvilfield comparison
Dynamic replay systemCommanded waveform, edge, dwell, repetitions; measured delivered PFRepeatable stimulus across source statesReal software behavior and rack storage unless representedP17 pp. 4-9
Actual GPU workloadVersioned application, GPU count, batch/concurrency, capsDelivered AC profile and workload continuity togetherIdentical repeated electrical input unless measured and boundedP03/P04/P15

Why average power and GPU nameplate are insufficient

NVIDIA describes synchronized compute/communication phases and different roles for caps, storage and power burn in its July 2025 GB300 article, updated August 27 [P03]. Its DGX H100/H200 guide lists 10.2 kW maximum system power, six PSUs and 4+2 redundancy; three powered PSUs permit reduced-performance operation [P15]. Rate feed-loss throughput separately.

NVIDIA SMI's Average Power Draw field reports the preceding second on Ampere devices (except GA100) and newer devices; its separate instantaneous field reports the last board-power reading [P04, live documentation checked November 5, 2026]. Neither measures the AC feeder. Use feeder waveforms for delivered input and telemetry for workload context.

Which standards and documents set acceptance?

IEC 62040-3:2021 edition 3 removed the nonlinear step-load type test, so a UPS performance classification alone does not establish how an installed UPS and generator will respond to repeated GPU load transients [P05].

Authority, edition, and conflicts
Reference checkedEdition/versionGoverns/supportsScope and distinctionUse in this procedure
IEC 62040-32021, edition 3UPS performance/test frameworkAC ≤1,000 V; storage ≤1,500 V DC; nonlinear step type test removedRecord declared UPS classification; add site workload test [P05]
IEC 61000-4-302025, edition 4; July 2026 correctionIn-situ AC PQ measurement methods50/60 Hz systems; classes A and S; transducer effects not addressed in detailRecord method/edition and separate sensor-chain qualification [P06]
ISO 8528-52025 current, per BSIGenset design/performanceSupersedes 2022; actual load schedule needs an agreed performance basisUse contracted performance sheet [P13]
Cummins 5544386Rev. 2/25, discusses ISO 2018Load dependence and older class interpretation2018 G3 discussion: 3 s frequency/4 s voltage recovery under defined conditionsHistorical explanation, not current GPU criteria [P08]
Caterpillar LEXE22885-00September 2024, cites ISO 2022Standard steps versus custom stepsIts custom 0-to-60% example requires agreed custom performanceWrite the actual load schedule and limits [P09]
Vertiv SL-8061707/26Particular AI test system20% smoothing and 2 Hz/s discussed for tested setup; synchronization still scenario-dependentSite-specific comparison, not defaults [P17]

Resolve differences without averaging incompatible limits

Apply adopted obligations, contracts and OEM constraints at their specified locations. Resolve conflicting windows and load schedules before testing; choosing the smallest percentage does not resolve different definitions.

Which workload profiles should the field procedure use?

The Anvilfield v1 library uses a 400 kW test boundary. Qualify the recipe at low approved capacity before scaling. W6, the captured deployment workload, supplies the application-specific evidence alongside AI cluster commissioning and burn-in. Record application/data hash, batch size, precision, concurrency, GPU count, scheduler, caps, software versions and smoothing.

Workload profile library, Anvilfield procedure v1
IDLow/high kWTransitionHigh/low dwellRepetitions/capturePurpose and provenance
W0100/100None60 s steadyOne baseline per stateInstrument/load baseline, Anvilfield v1
W1100/3001 ms rise; 1 ms fallHigh and low each at least 10 s and until electrical recoveryThree up/down pairs; 10 s pre, at least 30 s postIsolated pickup/rejection, Anvilfield v1
W2100/3001 ms rise/fall19 ms high + 19 ms low + two 1 ms ramps = 40 ms cycle60 s burst, 1,500 cycles; three valid burstsRepeated interaction, Anvilfield v1; timing chosen, not copied from P01
W3100/3001 ms rise/fall499 ms high + 499 ms low + ramps = 1 s cycle60 s burst, 60 cycles; three valid burstsSlower envelope response, Anvilfield v1
W4Four groups, each 25/75Same as W240 ms per group, offsets 0/10/20/30 ms60 s burst; three valid burstsCorrelation control against W2; ideal aggregate constant 200 kW, Anvilfield v1
W5100 to 300 then 300 to 10010 s ramp each way, 20 kW/sHigh at least 10 s and until electrical recovery; low until recoveryThree pairsCompare ramp control, Anvilfield v1
W6Actual captured deployment profileMeasured edge and delivered profile retainedNative workload timingThree complete matching workload windows under proposed methodDeployment acceptance: record real input; retain actual measurements [P03/P04]

Record wiring, PF control/sign, rack correlation and AC phase; vary approved edge phase to test unbalance. Apply OEM derating using recorded ambient, altitude, fuel and coolant/inlet conditions.

Qualify the delivered edge and plateau

For W0-W5, Anvilfield v1 requires plateau error within ±2% of target and applicable 10-to-90% duration within ±10% of its reference, including uncertainty. A full linear 1 ms ramp therefore has a 0.8 ms transition target and a 0.72 to 0.88 ms allowed interval; W2 plateaus are 100 ±2 kW and 300 ±6 kW. Declare the simultaneous three-phase power-envelope algorithm, passband, filter delay and plateau mask; use the installed three-wire or four-wire measurement method. Apply it to both reference and delivered signals; cycle-average power cannot qualify these edges.

Add expanded uncertainty to the absolute measured error and compare the sum with the allowed bound. The sum must not exceed the bound, L. A proven excess is invalid input; overlapping uncertainty is unresolved. Set the isolated-event time origin, t0, at the measured 50% crossing.

W2 averages 200 kW. W4 pairs half-cycle-offset groups to produce an ideal constant 200 kW after startup, testing correlation cancellation rather than another 300 kW aggregate peak. Preserve its startup and shutdown separately.

Approve W6’s measured peak, edge, repetition and correlation envelope before comparing runs. A workload-file hash alone cannot establish identical electrical demand.

Keep repetition and thermal conditions reproducible

Restore electrical, battery and thermal conditions between repeats. Extend capture through recovery/recharge with 1 s environmental trends. Three repeats expose variation, not statistical reliability.

How do you capture synchronized UPS and generator waveforms?

Anvilfield v1 starts its 1 ms program at 100 kS/s per simultaneous voltage/current channel and 20 kHz usable measurement-chain bandwidth with documented anti-alias filtering. Revise acquisition for faster edges; this millisecond recipe is not an IEC minimum or an emissions test. EPMS and power metering provide operational context.

Instrument bandwidth and timing register
Channel/productRateBandwidth/windowExport/timingRequired record or actionAuthority
Proposed electrical waveform chainAt least 100 kS/s per simultaneous channelDocumented 20 kHz usable chain for the 1 ms recipe; anti-alias filter recordedRaw file; measured inter-channel offset ≤100 microsecondsConfirm probe/sensor range, phase delay, isolation/category, clipping and calibrationAnvilfield v1 choice
Derived AC voltage/frequencyFrom raw waveformDeclare cycle-based algorithm; 50 Hz cycle = 20 ms, 60 Hz cycle ≈16.667 msPlot using actual window/latency; do not claim 1 ms independent frequency resolutionRetain raw and calculated data togetherArithmetic; measurement framework P06
PW8001 + U700515 MS/s ADCDC, 0.1 Hz to 5 MHzNumerical updates 1/10/50/200 ms; optional 1 MS/s D/A waveform feed to external loggerQualify output/logger accuracy, delay and raw-export durationP14, PW8001E15-5XB, Oct. 3, 2025, pp. 15, 17, 21, 24-25
PW8001 + U70012.5 MS/s ADCDC, 0.1 Hz to 1 MHzSame update choices; waveform recorder holds/interpolates source samples on its internal 15 MS/s gridInterpolation adds no information; qualify export/compressionP14, pp. 17, 24
PW8001 internal waveform memory5 Mword per signal0.333 s at 15 MS/s, calculatedPeak-to-peak compression available; waveform file save distinct from streamingDemonstrate duration and raw fidelity; 100 s at 100 kS/s needs 10 M samples per signalP14 pp. 24, 28; Anvilfield arithmetic
Multi-instrument timingCommon-marker test before/after≤100 microseconds proposed offset boundOptical link or validated acquisition synchronizationStore offset measurement and drift; clock labels alone do not passAnvilfield v1; optical feature P14
NVIDIA SMI average board powerAverage over preceding 1 s on supported devicesGPU board metric; not AC feeder powerRetain timestamp and fieldContext and cap status only for the 1 ms recipeP04, live version checked Nov. 5, 2026
Controller/EPMS/thermal context1 s trend plus native eventsNative filter/scan recordedCommon time; stated uncertaintyContext, not raw captureAnvilfield v1

Prove timing before interpreting causality

Verify common-clock or supported synchronized acquisition with an isolated marker before/after each run. Report measured skew and sensor delay. Ordering within combined timing/filter uncertainty is unresolved; UTC does not remove controller scan delay.

Do not confuse instrument specifications

HIOKI's PW8001E15-5XB brochure separates ADC sampling, numerical updates and optional D/A waveform output [P14]. Qualify sensor, analyzer, output and logger together, including rented synchronization options and firmware.

Anvilfield estimates 0.96 GB for 24 waveform signals over 100 s at 100 kS/s and four bytes per value, excluding timestamps and copies. Method: four three-phase locations require twelve voltage/current pairs. Multiply the number of signals by capture seconds, samples per second and bytes per value: 24 × 100 × 100,000 × 4 bytes.

Add bypass, A/B, DC and marker channels to the acquisition plan. Rehearse gap-free capture and readable export; segmented or compressed data cannot establish uncaptured fast extrema.

Which source states and transfers must you test?

Qualify acquisition on utility first; compare identical input hashes and starting conditions across states. In parallel plants, record each set’s kW/kVAR and sharing mode using the generator paralleling and load-sharing procedure; aggregate bus power hides unequal loading.

Source-state matrix
StateConfigurationInput/profile setSmoothing comparisonMandatory observationsGate
UUtility, UPS double conversionW0-W6 applicable setApproved baseline versus approved enabled settingsInput/output/feeder demand; job resultEstablish valid stimulus
BUPS stored-energy operationW0, W1, W2, W6 within approved runtimeAs designed for battery operationDC current/voltage, reserve, critical busStop at defined storage reserve, not exhaustion
GGenerator stable, UPS onlineW0-W6 applicable setBaseline/enabled, identical inputSource V/f, UPS input/output, bypass trackingSeparate source and output verdicts
GCGenerator plus UPS rechargeW1/W2/W6 after approved dischargeAs-left charge limit and walk-inGenerator demand includes rechargeNo overload or repeated input rejection
UGUtility loss and generator pickupW2 or W6 active within scriptApproved operating settingSource loss, storage, genset available, transfer, rectifier rampTiming and continuity against site sequence
GUUtility restoration/retransferSame profile as UGSame configurationReturn timers, load transition, chargingRecord through full sequence
DGOne generator unavailable in approved parallel topologyRequired subset of W1/W2/W6As-left settingPer-set kW/kVAR sharing and bus behaviorRemaining plant capability prechecked
DUApproved UPS module/path unavailableRequired subset of W1/W2/W6As-left settingRemaining module current and storage demandOnly tested redundancy proven
BPGenerator bypass synchronization/approved transferOnly separately authorized profileRecord actual bypass control statePhase/frequency match and transfer permissiveDo not force out-of-window transfer

Capture pickup, recharge, and retransfer separately

Mark source loss, discharge, generator availability, ATS state, rectifier walk-in and charging separately. Include conversion losses, recharge and non-IT generator loads. Follow the full return sequence and controller timers. For gas engines, rotary UPS or DC UPS, replace limits and state definitions with the installed architecture; IEC 62040-3:2021 excludes rotary and DC UPS from its scope [P05].

Bypass and degraded capacity are separate scenarios

Use UPS and STS hold points for approved transfer acceptance. Verify phase/frequency tracking and bypass permissive. Precheck remaining capability before removing a generator, module or path. Vertiv SL-80617 recommends double conversion and avoiding maintenance bypass directly onto generators with high AI fractions [P17]; the installed operating procedure still defines authorized switching.

What is a pass, hold, or stop?

Anvilfield's GPU transient procedure v1 judges critical-load continuity, generator response and bypass synchronization separately; a powered load alone does not prove synchronized-transfer availability. Pass requires every mandatory criterion to be met. A recorded breach fails; deficient input/data invalidates evidence.

Use hold for a missing prerequisite or limit. Not applicable needs a topology reason; omitted applicable cases remain unproven. Stop identifies the operating action.

Acceptance, stop, and retest decisions
CriterionFilled decision ruleVerdict/actionAuthority
Script input fidelityW0-W5: plateau and applicable edge bounds from the workload register; W6: approved deployment envelopeProven excess: invalid; uncertainty overlaps: unresolvedAnvilfield v1, not equipment tolerance
Timing validityMeasured alignment ≤100 microseconds for 1 ms recipeExcess offset: no cross-device timing claim; correct/retestAnvilfield v1
Critical-bus electrical envelopeUse installed load/UPS/project time-voltage and frequency limits, with measurement windowsMissing limit: hold; excursion: fail and execute defined stop actionApplicable project/OEM documents; P05 scope
Generator responseUse approved site-specific load step, ambient derating, extrema and recovery requirementsDo not substitute old G3 figures for custom repeated stepsP08/P09/P13
Required bypass availabilityPermissive, voltage match and phase/frequency requirements met for the prescribed operating state, duration and actual bypass sourceOutput continuity alone cannot pass this criterion; no forced transfer to prove availabilityP17 pp. 10-12
Protection and IT continuityZero unintended protective trips, IT resets, or job failuresStop affected scenario, retain full recordAnvilfield v1
StorageNamed DC current, temperature and reserve limitsApproach stop threshold: stop using defined sequenceInstalled storage limits; no generic SOC substituted
Measurement completenessAll required channels present, unclipped, correctly scaled and time checkedInvalid dataset, repeat after correctionAnvilfield v1
Recovery calculationIsolated: 1 s analysis dwell; burst: envelope and post-burst settling; contract governs acceptanceReport “not recovered within record” when appropriateAnvilfield analysis method
Retest closureThree valid corrected repetitions plus affected transition regression under proposed methodKeep prior failures and setting deltas; close after passAnvilfield v1

OSHA 1910.334(b)(2), checked November 5, 2026, prohibits repetitive manual reclosing after protective operation and requires determining that the circuit can be safely reenergized [P19]. A protection trip stops the scenario for that determination; it is not a request to reset and repeat.

Put every numerical limit on the signed script

Sign the location, units, reference, window, excursion duration, recovery band/deadline, authority/revision, decision owner and stop action. Select project bands before testing. Anvilfield estimates a project-selected ±5% band at 415 V as 394.25 to 435.75 V and a project-selected ±1% band at 50 Hz as 49.5 to 50.5 Hz.

Recovery begins at band re-entry sustained for the declared dwell. Use the table's analysis dwell unless the contract specifies another. For W2, judge the burst envelope and persistent oscillation, then settling after its final edge. Its 25 Hz input has no quiet second between steps.

Treat uncertainty straddling a limit as unresolved. Retain the uncertainty with the recovery result.

Worked example: what does the published 2.4 MW test show?

Vertiv SL-80617 (07/26) supplies the worked example’s inputs and results. Calculations use its load-side boundary.

Method: Anvilfield estimates total nominal IT power by adding AI and other IT power. Divide AI power by total IT power or generator nameplate to find each AI fraction. Multiply nominal AI power by the 1.5 peak factor, then add other IT power to find peak total IT power.

Subtract nominal IT power from peak IT power to find the increment, then divide by nominal IT power for the percentage increase. Divide peak IT power by generator nameplate for the nameplate comparison. Divide real power by the assumed 0.95 leading power factor to find apparent power: S = P / PF. The load-side boundary includes IT demand; account separately for losses, charging and non-IT demand when calculating generator output.

Published inputs, calculated results, and observed outcomes
QuantityValue/resultProvenance and interpretation
Test system2,400 kW genset; 2 × 1,250 kW UPS units in textP17 pp. 4/9 disagree on kW/kVA; retain the unit discrepancy
Test voltage / assumed PF415 V; 0.95 leadingP17 p. 9; test-specific PF
Scenario 2 nominal componentsAI 1,440 kW; other IT 560 kWP17 p. 9
Total nominal IT1,440 + 560 = 2,000 kWAnvilfield estimates (arithmetic)
AI fraction of IT1,440 / 2,000 = 72%Anvilfield estimates; denominator is IT
AI fraction of generator nameplate1,440 / 2,400 = 60%Anvilfield estimates; different denominator
Peak AI / peak total IT1,440 × 1.5 = 2,160 kW; +560 = 2,720 kWP17 factor/values; arithmetic
Nominal-to-peak increment2,720 - 2,000 = 720 kW, or 36% of nominal ITAnvilfield estimates
Peak/nameplate comparison2,720 / 2,400 = 113.33%; excess 320 kWPlanning comparison, not measured output
Apparent power at assumed PFNominal 2,000/0.95 = 2,105.26 kVA; peak 2,720/0.95 = 2,863.16 kVAAnvilfield estimates at assumed constant PF
Scenario 2 without smoothingApprox. ±10% voltage; -10% frequency; asynchronous alarm presentP17 p. 10 reported results
Scenario 2 with smoothingApprox. ±0.5% voltage; -4% frequency; shorter asynchronous alarmP17 p. 10; alarm shortened
Frequency conversion at 50 Hz-10% : 45 Hz; -4% : 48 HzAnvilfield estimates; screenshot readings are not verified nadirs
Recovery durationNumerical recovery duration not publishedAlarm duration is not recovery

The denominator changes the meaning of “75% AI”

Vertiv's approximate 75% synchronization threshold uses total IT load as its denominator. The scenario table also gives AI fractions of generator rating. Use the denominator shown in each row; the threshold is specific to this test system.

Use the detailed result, not the simplified summary

Vertiv's September 2026 blog combines voltage and frequency in an approximate ±0.5% summary; the full paper separates them as shown above [P01, P17]. Its worst-case bypass difficulty despite small frequency variation shows why phase tracking needs separate evidence.

Where should smoothing act: GPU, rack, or UPS?

Locate each control before comparing results. GPU controls change demand; rack energy storage and ride-through buffers the rack boundary; UPS storage changes upstream input. The measurement boundary determines which improvement is visible.

Smoothing location and required evidence
LocationMechanismVerified number/unitsEvidence required to compare
GPU controlsCeiling/floor, ramp up/down, hysteresisNVIDIA SMI/DCGM ramp mW/s; hysteresis msConfiguration export, workload progress and feeder waveform [P04/P12]
GB300 power shelfCapacitor energy storage; accompanying cap/burn controlsNVIDIA reports 65 J/GPU storage in the new PSU design; 30% peak reduction in the Megatron comparison used an instrumented GB200 rackSame workload and measurement boundary; no automatic fleet credit [P03, 2025]
Vertiv UPSStorage-assisted input smoothingUp to 20% tested setting discussed; 2 Hz/s tracking recommendationActual upstream waveform, battery current, bypass phase/permissive [P17, 07/26]
Generator/plant controlsLoad staging, sharing, rectifier walk-in coordinationInstalled equipment's approved ramp and step valuesPer-generator kW/kVAR, voltage/frequency, state trace [P08/P09/P17]

Freeze controls and change one variable at a time

Export the supported controls and units, recording unavailable fields rather than substituting zero. NVIDIA DCGM smoothing fields require the documented access privileges [P12]. For UPS comparisons, match downstream demand; for GPU or rack controls, repeat the same workload request and measure the changed feeder profile. Hold source state and battery starting condition fixed.

Judge throughput alongside power using power capping and oversubscription criteria. Record workload progress for each compared setting.

Size the power exchange and repeated energy separately

Anvilfield estimates that flattening W2 at 200 kW requires up to 100 kW discharge and 100 kW absorption, with 1.95 kJ discharged per cycle and 0.81 kWh discharge throughput over 1,500 cycles. Method: integrate 100 kW over the 19 ms high dwell plus two positive half-ramp triangles, each 0.5 ms wide and 100 kW high; multiply by cycles and divide kJ by 3,600 for kWh. Equal ideal charging yields zero net energy change.

Measure DC pulse-current capability and assess battery life from the installed storage duty. Measure storage current, temperature and energy in both directions, then quantify recharge peak and restoration time. Conversion losses, reserve, control behavior and OEM limits determine actual storage duty.

What must the synchronized recovery plots show?

Align fast-event, burst and transfer views. This chart compares reported extrema; use Vertiv's source screenshots for the recorded traces.

Reported deviation magnitude (%)Voltage, standardVoltage, smoothingFrequency, standardFrequency, smoothing100.5104010%
Manufacturer-reported approximate values, Vertiv SL-80617 (07/26), p. 10. Voltage bars show deviation magnitude; frequency bars show dip magnitude.

Fast view: use -10 to +50 ms around the measured W1 edge, with per-phase raw V/I, instantaneous three-phase p(t), marker and trigger. Overlay the commanded ramp and qualified envelope separately, marking 10/50/90% crossings. Annotate bandwidth, sampling, probe delay, skew and clipping. Anvilfield estimates 6,000 sample intervals across that window at 100 kS/s.

Recovery view: start at -1 to +10 s and extend until recovery is established. Align feeder kW, per-phase RMS voltage, frequency, DC current and bypass permissive/phase error. Draw approved bands and mark extrema, first and sustained re-entry. Declare RMS/frequency algorithms, windows and latency.

Flag frequency as invalid when voltage loss or distortion defeats the estimator. Never plot a held last value as continued synchronization.

Burst view: show -10 to +90 s for W2, distinguishing burst onset from its final edge. Preserve extrema in long views and label continuous raw, segmented or compressed coverage. Extend the separate transfer view through pickup, walk-in, recharge and retransfer; mark source availability, ATS contacts, UPS mode and smoothing state.

Separate likely causes with a discriminating trace

Source-frequency oscillation with stable UPS output points upstream; compare rectifier demand and bypass state before blaming governor or AVR alone. Good source voltage with a feeder excursion requires UPS-output comparison. A smaller-than-commanded step with job slowdown requires cap, thermal and application logs. Immunity to an input never delivered remains unproven.

When must you retest?

Repeat affected profile/state combinations after relevant workload, control, storage or topology changes. Anvilfield v1 proposes an evidence review every 12 months, not mandatory annual GPU testing. Preserve failed and invalid runs with corrective-action IDs; one attractive replacement waveform does not close a finding.

Change-triggered retest scope, Anvilfield procedure v1
TriggerWhat must be reacquiredClosure evidence
GPU, application, batch/concurrency or power-cap changeW6 at affected load boundaries; compare with earlier profile envelope; rerun affected source statesVersioned manifest, actual delivered waveform and workload results
Smoothing, rectifier walk-in or charging setting changeSame failing/limiting profiles on G and GC; affected UG/GU/BP transitionsBefore/after settings, upstream and storage traces, critical output and bypass verdicts
Generator/UPS firmware, module count, batteries, sharing or topology changeApplicable G/GC/DG/DU and source transitions; both rack feeds when path loading changesUpdated one-line and capacity basis; three valid corrected cases plus related transitions
Sensor ratio, polarity, clipping, clock or export gapReacquire affected channels and any dependent timing/acceptance resultCorrected calibration/setup and common-marker rehearsal; retain invalid original
New design ambient or operating envelopeRecheck OEM site capability and repeat affected limiting cases at the approved conditionMeasured environment, actual load and stated remaining untested conditions
Twelve-month evidence review without relevant changesReview configuration, workload and incident evidence; select tests only where the operating envelope lacks proofDated review and justified repeat scope; no claim of mandated annual GPU testing

Close a finding with evidence

Close findings after required results pass, exclusions are explicit, as-left settings match and automatic operation is restored. Retain failed originals; missing samples require reacquisition.

What should the scope, schedule, and estimate include?

Anvilfield estimates $24,000 for this two-shift support package or $31,050 with one retest shift, before excluded site costs.

Method: multiply labor hours by the hourly rate, then add instrument and travel allowances. Anvilfield selected these estimating inputs on November 5, 2026; vendor quotations must be obtained separately.

The support scope excludes load equipment, temporary distribution, fuel, switching crew, OEM attendance, taxes, premiums, outage cost and owner fees. Allow for access and battery restoration.

Anvilfield scope estimate, USD, November 5, 2026
ItemQuantityEstimating rate/inputExtended value
Script and coordination16 hours$185/hour$2,960
Field team3 people × 2 shifts × 10 hours = 60 hours$185/hour$11,100
Analysis and report24 hours$185/hour$4,440
Instrument package1 allowance$4,000$4,000
Travel/mobilization1 allowance$1,500$1,500
Base support package100 labor hours plus allowancesSum$24,000
One retest shift3 × 10 hours plus $1,500 instrument/mobilization allowance$5,550 + $1,500$7,050
Planning total including retestBase + retest$24,000 + $7,050$31,050
Labor sensitivity, base package100 hours at $150 to $225/hour plus unchanged $5,500 allowancesExplicit alternative inputs, not market percentiles$20,500 to $28,000

Find and qualify the commissioning work

An AI hall addition, GPU-generation change, altered generator topology or revised power-control strategy defines a commissioning scope trigger. Commissioning teams planning generator service territories use PorchRocket Asset Search for reviewed lists of visible generator sites and their owners of record. Operating drawings, baseline records and GPU rack power and cooling readiness define the technical work package.

Build the schedule by multiplying the number of profiles by repetitions and compared settings within each source state. Add the captures across states, then add transitions. Anvilfield estimates W2/W3/W4 across U and G, three repeats and two settings at 36 captures. At 100 s each, recorder time alone is one hour.

Add other profiles, switching, battery restoration, setup and reruns to establish the full schedule. More measurement boundaries, permitted switching windows and recovery time determine schedule and cost.

Field checklist and turnover dataset

Check each state change and turnover.

  • Confirm electrical work controls, qualified testers and inspected/rated equipment; missing controls hold setup.
  • Match the one-line, boundary and prerequisite generator/UPS records; mismatches hold the scenario.
  • Name each limit’s source, revision, units, location and window; undefined criterion holds acceptance.
  • Hash workload/replay inputs; changed input gets a new run ID.
  • Qualify measured input fidelity; wrong profile invalidates the run.
  • Measure both affected rack feeds and actual bypass source; unmeasured paths remain unproven.
  • Rehearse channel count, duration, export and gap-free capture; inadequate coverage requires correction.
  • Verify sensor IDs, ratios, orientation, calibration and marker alignment; clipping or failed timing requires reacquisition.
  • Capture UPS mode, charging, walk-in, bypass and smoothing settings; undocumented changes restart comparison.
  • Record generator count, sharing and environmental state; capability changes require script review.
  • Verify battery starting condition and reserve; inadequate reserve defers testing.
  • Record cooling, workload progress and errors; investigate throttling and service failure separately.
  • Record output, generator and bypass verdicts for each state; unrun applicable states remain unproven.
  • Retain failed files and issue IDs; repeat corrected cases and affected transitions.
  • Match final settings and automatic state to turnover record; mismatch holds release.

Reusable input CSV and readme

The CSV defines W0-W5: each row starts a linear ramp to command_kw over ramp_ms, then holds. W4 offsets are already in time_s; wrap rows modulo 40 ms for the steady pattern after approved startup. Revise file/hash for extended W1/W5 dwells. W6 retains its acquired waveform.

Download W0-W5 command CSV and input readme. Terminal rows mark endpoints; the next cycle takes precedence. W2/W3 start at 100 kW. W4's startup begins with four 25 kW groups, then establishes the cyclic pattern before steady capture.

Copyable command CSV and SHA-256
profile_id,time_s,group_id,command_kw,ramp_ms,repeat_count
W0,0,all,100,0,1
W0,60,all,100,0,1
W1,0,all,100,0,3
W1,10,all,300,1,3
W1,20.001,all,100,1,3
W1,30.002,all,100,0,3
W2,0,all,300,1,1500
W2,0.02,all,100,1,1500
W2,0.04,all,100,0,1500
W3,0,all,300,1,60
W3,0.5,all,100,1,60
W3,1,all,100,0,60
W5,0,all,100,0,3
W5,10,all,300,10000,3
W5,30,all,100,10000,3
W5,50,all,100,0,3
W4,0.000,1,75,1,1500
W4,0.020,1,25,1,1500
W4,0.040,1,25,0,1500
W4,0.010,2,75,1,1500
W4,0.030,2,25,1,1500
W4,0.050,2,25,0,1500
W4,0.020,3,75,1,1500
W4,0.040,3,25,1,1500
W4,0.060,3,25,0,1500
W4,0.030,4,75,1,1500
W4,0.050,4,25,1,1500
W4,0.070,4,25,0,1500

SHA-256: f8f9d1cc5bd025d55150cfce5708264f342ee87a2cd2d4fca68e1e58a41b8dc5

Preserve a reconstructable record

Store run_id, profile_id, state_id, repeat, t_utc, t_rel_s, channel, location, phase, quantity, unit, value, sample_interval_s, window_s and quality_flag. Metadata include nominal voltage/frequency, ratios, signs, timing uncertainty/method, marker origin, delay corrections, gaps, source availability and bypass state.

Keep the limits register with criterion_id, source_document, revision, state_id, location, quantity, window_s, limit_curve, excursion_duration_s, recovery_band, recovery_deadline_s, uncertainty, decision_owner and stop_action. Preserve its approved version with every run. Retain hashed binaries, CSV exports, configurations, scripts, logs, calibration, time checks, defects and as-left settings; version corrections. Define RMS/frequency/settling calculations in the readme and distinguish observed, manufacturer-reported and Anvilfield-calculated data.

How to cite this page: Anvilfield, GPU power transient tests for UPS and generators: field procedure, 2026, https://anvilfield.com/field-guides/datacenter/gpu-power-transient-test-plan/.

Related tools

Next step: Monitor generator sites

FAQ

How do you perform GPU power transient testing for UPS and generators?

Replay a defined workload across approved source states and compare synchronized source, UPS and feeder records with the signed acceptance limits.

How is a GPU transient different from a resistive load-bank step?

GPU workloads can repeat correlated power changes with electrical characteristics and timing a steady resistive bank does not reproduce.

How do you synchronize UPS and generator waveforms?

Use common-clock or validated synchronized acquisition and verify end-to-end timing with the same marker before and after the test.

What are AI load-step acceptance criteria?

They are the documented input-fidelity, output-continuity, equipment-envelope, recovery, synchronization and workload requirements for the installed system.

Is 75% AI load a universal generator limit?

No; Vertiv's threshold is specific to its tested system and stated IT-load denominator.

Does a UPS remaining online mean bypass is available?

No; critical-load continuity and bypass synchronization are separate results.

Can NVIDIA SMI replace a waveform recorder?

No; its Average Power Draw field averages board power over a second on supported devices. Board telemetry supplies workload context; the waveform recorder measures the AC feeder.

Does enabling smoothing eliminate the need for testing?

No; compare the approved workload and source states, measuring the effect at each control boundary and checking storage duty, bypass tracking and job performance.

How often should GPU transient tests be repeated?

Retest after relevant workload, firmware, storage or topology changes; Anvilfield proposes a 12-month evidence review, not a universal annual test requirement.

How much does the support package cost?

Anvilfield estimates $24,000 for the defined 100-hour support scope, or $31,050 including its one-shift retest allowance, before excluded load-bank and site costs.

People also ask

Codes cited in this guide

This guide is written and reviewed against the published standards below. Always confirm the current adopted edition with the authority having jurisdiction.

Sources checked