Metering, Power Quality, Monitoring & Electrical Operations

Everything upstream of this chapter built the electrical machine: the substation (Chapter 4.2), the transformers and harmonic mitigation (Chapter 4.4), the UPS and storage spine that absorbs transients (Chapter 4.5), the DC distribution revolution (Chapter 4.7), and the grid-interactive obligations that keep a gigawatt load online through a fault (Chapter 4.10). This chapter is about seeing and operating that machine — the metering that tells you where the power went, the power-quality instrumentation that tells you whether the waveform is healthy, the telemetry-driven control loops that make GPU load steps survivable, and the commissioning and day-2 electrical operations that keep the whole thing safe and inside spec. Observability is the precondition for every other decision in Part 4 actually holding in production.

Every fork here carries a downstream cost: how deep to meter, how fast to sample, open- versus closed-loop smoothing, converged versus federated DCIM/EPMS, and the commissioning level you hand over against. Underneath all of them is one break: AI loads broke the assumptions that classic data-center metering and power-quality practice were built on. A legacy hall drew a smooth, diversified, slowly-varying load that a monthly revenue meter and an annual power-quality audit described adequately. A training cluster swings a power-electronic, sub-second-synchronized load tens of megawatts in milliseconds, and instrumentation built for the old world is blind to exactly the events that matter.

Metering in an AI factory is a hierarchy, and the first decision is how far down it reaches. At the top sits the revenue meter at the point of interconnection — utility-owned or customer-owned per Chapter 4.3, accuracy-class 0.2S or 0.5S, the meter the tariff is settled against and the only one the utility cares about. Below it, the question is how many layers of sub-metering you instrument: the medium-voltage feeders, the pod/block transformers, the LV switchboards and busway runs, the rack PDUs, and — at the deepest tier — branch-circuit and outlet-level metering inside the PDU (Chapter 4.6).

Each layer costs money and bandwidth, and the payoff is attribution. Meter only at the POI and you know your bill but nothing else — you cannot tell a tenant what they owe, cannot attribute a PUE excursion to a pod, cannot see which busway is approaching its ampacity, and cannot reconcile the IT-reported power draw against what the facility actually delivered. The deepest tier — per-outlet metering at the PDU — is what makes a multi-tenant colo billable, what lets you enforce a rack-level power budget, and what feeds the energy-attribution that Chapter 15.1 needs to compute a defensible PUE/TUE. The downstream cost of under-metering is a permanent inability to answer questions the business will ask later, potentially requiring planned isolation and de-energized switchgear work to retrofit; reserve safe metering access during design.

A second axis is what each meter measures. A cheap meter reports kWh and maybe RMS current. A power-quality-capable meter reports per-phase voltage and current, real/reactive/apparent power and power factor, individual harmonic magnitudes and THD, and — critically for AI — sag/swell/transient events with timestamps. The decision to specify PQ-capable meters at the right tiers (typically the MV feeders and the main LV boards) is what turns a metering hierarchy into a power-quality monitoring network without a second parallel instrumentation buildout.

The first balance does not prove a meter fault. Synthetic residual is 1,000 − 950 − 30 = 20 kWh, or 2.0% of input. Worst-case meter uncertainty is 0.005 × (1,000 + 950 + 30) ≈ 10 kWh. Its 8 kWh difference from the 12 kWh loss estimate lies within the unrounded bound 0.005 × (1,000 + 950 + 30) + 4, displayed conservatively as 14 kWh. Record the synthetic result as consistent with the assumed balance, not a calibration or efficiency certificate.

The decision flips when the residual differs from the model by more than the combined bounds. If IT energy is instead 935 kWh, residual becomes 35 kWh; 23 kWh above the loss estimate exceeds 0.005 × (1,000 + 935 + 30) + 4 before display rounding, conservatively 14 kWh. Hold billing allocation and investigate polarity/ratios, omitted feeders, timestamp windows and the loss model before changing tariffs or blaming the load.

The acceptance test procedure must separately inject stale BBU/BESS telemetry, loss of the EPMS network and a protection test input in a controlled test environment. Expected outcomes are inhibited new supervisory smoothing, preservation of reachable outage reserve, and the independently approved protective action; no software alarm substitutes for a trip test. The meter engineer signs the reconciled energy evidence; the protection engineer signs settings and witnessed clearing; the controls integrator signs command/failure-state traces; commissioning joins them in the ATP and Chapter 14.7 receives the operating response. All actual results remain HOLD — no field test performed. Schneider Electric PME 8.1 User Guide (March 2016), 7EN02-0379-00 explicitly separates its monitoring software from critical protection/control duties; the project must verify the same boundary for its offered system.

AI halls contain a high share of power-electronic loads. Active-PFC front ends can draw near-sinusoidal current, while aggregate distortion varies with topology, loading, controls and upstream impedance, and the aggregate injects harmonic current back toward the source. IEEE 519-2022 is the recommended-practice that governs this, and its structure drives a specific monitoring decision: it sets limits at the point of common coupling (PCC) — the boundary between you and the utility, or between you and a shared tenant bus — not at every individual load. Voltage distortion at the PCC is capped (for 1–69 kV systems, 5% THD-V and 3% per individual harmonic; below 1 kV, 8% THD-V), and current distortion (TDD) is bounded on a sliding scale keyed to the short-circuit-to-load ratio I_sc/I_L — from 5% TDD on a weak bus to 20% on a stiff one. → distortion mitigation (for example, active front ends, active filters or a validated multipulse arrangement) is the canonical subject of Chapter 4.4. A K-rated transformer or IEEE C57.110 derating provides thermal withstand/capacity for the measured spectrum; it does not reduce harmonic current or establish IEEE 519 compliance. Here the decision is how you measure compliance.

Measurement is where the problem bites. IEEE 519 compliance is conventionally demonstrated as a snapshot — a power-quality engineer parks an analyzer at the PCC for a week, captures 10-minute aggregated statistics per Class A methods in IEC 61000-4-30:2025 (corrected 2026-07), and produces a report. Whether that demonstrates compliance depends on the applicable assessment window, site agreement and instrument setup. It does not replace event capture for equipment diagnostics. A synchronized training step is a millisecond-scale event; the voltage sag it induces on a stiff-but-not-infinite bus lives and dies inside a single cycle. A 10-minute aggregate alone cannot characterize every sub-cycle event; compliant instruments also use shorter aggregation and event functions depending on the standard and configuration. If you want to see the events that actually throttle accelerators and trip undervoltage ride-through, you need continuous waveform capture with sub-cycle resolution and event triggering, not a compliance snapshot. The functions can coexist in one correctly specified instrument or use separate devices; the cost fork is continuous multi-point capture, storage and integration versus a periodic survey, and conflating them is the most common power-quality blind spot in AI facilities.

The physics and mitigation of GPU power transients — the synchronized load steps, the chip-to-BBU-to-BESS absorption spine — are the canonical subject of Chapter 4.5. This chapter owns the observability and control half: the telemetry that feeds smoothing, and the decision of whether smoothing runs open- or closed-loop. That decision determines whether your facility is a passive victim of its own load steps or an actively-managed grid citizen.

Open-loop smoothing bakes the behavior in at commissioning: firmware ramp-rate limits, idle-time floors, and power caps set once and left. NVIDIA's GB300 NVL72 ships the building blocks for this — roughly 65 J/GPU of capacitive energy storage in the power shelf, a GPU-burn mechanism that bleeds energy on ramp-down, and ramp-rate controls that together cut peak grid demand by up to ~30%. Configured open-loop, those features run on fixed parameters regardless of grid state. Closed-loop smoothing is a facility integration layer above NVIDIA's exposed controls: SMI and Redfish set GPU power parameters, while Mission Control provides cluster power management and building-management integration. Before assigning that path FRT or grid-services duty, the controls specification must bind command cadence and latency, controller/scheduler arbitration, RBAC, loss-of-signal state, observability and witnessed end-to-end tests.

The cost runs in both directions. Open-loop is simpler and fixes its supervisory policy. Interacting firmware limits, source impedance and recovery can still create dynamic problems. Tuning for the worst case also leaves goodput on the table whenever the actual conditions would permit more useful output. Closed-loop recovers that goodput but introduces a genuine governance problem: when grid stress and a training deadline collide, something decides whether to throttle the GPUs or stress the grid, and that authority must be explicitly assigned — to the EPMS, to the workload scheduler, or to a negotiated handshake between them. Leaving it implicit is how a facility ends up either silently throttling revenue workloads or violating a grid-services commitment it forgot it had made. → the grid-side obligation that constrains this loop is Chapter 4.10; the goodput-vs-availability framing is Chapter 12.2; demand-response revenue that closed-loop control unlocks is Chapter 15.8.

Two platforms describe the electrical machine, and the decision is how they relate. The EPMS (Electrical Power Monitoring System) is the SCADA-grade supervisory system that watches the power chain in real time — breakers, relays (IEC 61850), meters, ATS/STS state, fault events — and is the system of record for electrical events. What the name does not confer is deterministic execution, a safety integrity level, or protective authority: tripping lives in the protective relays, the trip circuits and the breaker logic, and the major EPMS vendors say plainly in their own documentation that their software and communications are unsuitable for time-critical protection. DCIM (Data Center Infrastructure Management) is the broader operational layer: asset and capacity management, power/cooling/space, environmental sensors, increasingly a digital twin, and the home of cross-domain analytics and predictive maintenance. They overlap on power telemetry, and the seam between them is where most operational blind spots live.

The choice is converged versus federated. A converged platform — one vendor's DCIM ingesting the EPMS natively — gives a single pane and one data model, at the cost of lock-in and the risk that real-time electrical supervision is now entangled with a non-deterministic IT platform. Federated systems keep the EPMS as an independent, hardened, real-time system and define an explicit data contract by which it publishes to DCIM (commonly over a message bus or a historian, with protection left where it belongs — in the relays, trip circuits and breaker logic, whose required operation must be independent of the historian, the analytics and the supervisory network). Federated is the more defensible posture for anyone who takes the view that protection must never depend on the analytics layer being up — but it only works if the data contract is real: defined tags, defined latencies, defined failure modes. An undocumented seam between EPMS and DCIM is the place where a meter reads one number, the IT stack reports another, and nobody can say which is right.

The hardest part of the integration is facility-to-IT, not facility-to-facility. The EPMS speaks Modbus, IEC 61850, and BACnet; the IT fleet speaks Redfish, IPMI, SNMP, DCGM/Prometheus, and PMBus down at the power shelf. SoC management across hundreds of rack BBUs is a concrete instance: the facility BESS state-of-charge lives in the EPMS, but each rack BBU's SoC is reported out-of-band via Redfish to the IT management plane. Closed-loop smoothing requires both views to be reconciled in one place at one cadence — which is precisely the converged-vs-federated decision made concrete. → the IT-side telemetry pipeline (DCGM, Prometheus) and the digital-twin layer are built out in Chapter 14.2; the agentic-ops direction is Chapter 14.13.

Commissioning is where all of the above is proven — or where the gap between design and reality is discovered, ideally before handover and not during a production training run. The industry runs a five-level (L1-L5) taxonomy: L1 factory acceptance testing of individual components, L2 site acceptance on delivery, L3 pre-functional checks, L4 functional performance testing of each system, and L5 integrated systems testing (IST) — the full, coordinated, failure-injection exercise where utility, generator, UPS, BESS, cooling, and IT load are run together through loss-of-power and load-step scenarios. The handover decision is which level you accept against, and for an AI factory the answer must be L5: the failure modes that matter are interactions, not component faults.

The defining commissioning fork for AI is the load profile you validate against. Traditional commissioning uses resistive load banks — a steady, linear, well-behaved load that proves the power chain can carry rated current and reject heat. That is necessary and insufficient. A default resistive load-bank test does not reproduce the two things that define an AI load: it is non-linear (a resistive bank injects no harmonics, so it tests nothing about IEEE 519 behavior or the active front ends), and it is stepped (switched resistive banks can execute coordinated steps across networked units, but only to the rise time, step resolution and repetition rate you wrote into the specification, and never with the constant-power response of a GPU front end — so a steady-state resistive test proves nothing about transient ride-through, BBU/BESS response, or the closed-loop smoothing logic). Specify rise time, resolution, repetition, power factor and waveform first, then select equipment against them. A cluster that passes a resistive load-bank test at rated power can still trip on the first 50-megawatt synchronized training step, because the step was never in the test plan.

Step-load validation closes that gap. The mature practice uses reactive and electronic load banks that can both inject harmonics (proving PQ behavior under realistic non-linearity) and execute programmed load steps that emulate the GPU ramp profile — validating that capacitance, BBUs, BESS, and the smoothing control loop actually catch the transient as designed, and that ride-through holds through the induced sag. The downstream cost of skipping step-load validation is the worst kind: the facility passes commissioning, the SLA clock starts, the first real workload lands, and the transient behavior that was never tested takes the cluster down — now a production incident with a customer attached, not a punch-list item.

The protection studies that produce a safe, selectively-coordinated electrical system — short-circuit/fault-duty analysis, time-current-curve coordination (the active IEEE 3004 series; IEEE 242 has been inactive since 2021), and arc-flash incident-energy calculation (IEEE 1584 / NFPA 70E) — are deliverables of the design phase, canonically Chapter 4.2. This chapter owns the acceptance handoff: transfer approved studies, settings and test evidence to Chapter 14.12, which owns change control and the procedures that govern day-2 electrical work. Selective coordination is a property that degrades every time a breaker setting is changed, a transformer is added, or a source configuration shifts. The operational discipline is a maintained coordination study and an as-operated single-line that the EPMS reflects in real time — so that a fault clears at the nearest device and takes down one pod, not the whole hall.

Arc-flash operations follow the same pattern: the IEEE 1584 study yields predicted incident energy at the working distance and the arc-flash boundary for equipment within its scope; NFPA 70E then requires PPE selection by either the incident-energy method or the PPE-category method, as applicable — not both. The operational requirement is that the labels track the as-operated configuration and that energized work follows the NFPA 70E hierarchy of controls — which, for an AI factory at scale, increasingly means designing for de-energized maintenance (redundant paths that let you isolate and lock out a section without dropping load) rather than relying on PPE for live work.

The genuinely new operational hazard is DC touch-safety. The shift to ±400 V and 800 VDC distribution (Chapter 4.7) introduces a class of risk that AC-trained electrical operations teams have not internalized: DC fault current offers no periodic zeros for a breaker to exploit, so DC arc-flash and sustained-arc behavior differ fundamentally; the selected system may be solid-midpoint, HRG or isolated; a first ground fault can itself be hazardous, and an opposite-pole second fault can create a high-energy short (canonical DC grounding and isolation monitoring in Chapter 4.11); and solid-state DC breakers behave nothing like the electromechanical devices technicians know. The operational consequence is that the metering and monitoring network must surface DC isolation status and first-fault alarms as first-class operational signals, and the safety program must retrain for DC — because the most likely failure is not a design error but an experienced AC technician applying AC-correct instincts to a DC bus.