Grid connection studies
The effect of a new data centre load on local networks is studied for capacity, voltage and reinforcement needs.
GCRI · Data and Compute
Power engineering connects computing facilities to the grid and keeps them powered. In this field it covers grid connection, reliability of supply, backup power and the flexibility data centres can offer to the grid.
Power systems engineering designs and operates the networks that generate, transmit and distribute electricity. It ensures that supply meets demand reliably as generation mixes and loads change. In data and compute and energy, power engineering shows how grid failures cascade into water, communications, health and finance. It informs investment and operating rules that protect dependent services. The canonical description is on the STEM Commons.
The effect of a new data centre load on local networks is studied for capacity, voltage and reinforcement needs.
Uninterruptible power supplies, generators and dual feeds are assessed for how long and how reliably they carry critical computing loads.
The potential for computing facilities to shift or reduce load to support the grid is estimated with workload and backup constraints.
Night lights, population density and true-colour imagery over the contiguous United States, from NASA GIBS. Each layer carries its own date.
The interactive map needs JavaScript; the layer list and sources are below.
Layers 3
Energy now, for this page
Keyboard, with the map focused
Hold Ctrl or ⌘ and scroll to zoom
Latest available
NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © OpenStreetMap contributors (ODbL) · Natural Earth
Loading the latest NASA imagery.
Drag to move. Ctrl or ⌘ and scroll, pinch or the buttons to zoom; hover for the values under the pointer; reset returns to the region.
Energy now, framed on the contiguous United States.Satellite and model products as NASA publishes them, each with its own date. They are indicators, not assessments of any place.
Layers and dates
Datasets and records used by power systems engineering on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.
| Data | Role | Label |
|---|---|---|
| Grid network data | Connection capacity | Published statistics |
| Facility load profiles | Demand | OBSERVED |
| Backup test records | Resilience | OBSERVED |
A hazard footprint takes out co-located assets in every layer; fragmentation, dependency between layers and overload of the survivors then spread the failure. The 3D view separates the layers by depth. Teaching model with stated illustrative values, not a prediction. The map on this page shows The contiguous United States; the model itself is not tied to a place.
Controls
Readouts
| Step | Data centres working (%) | Networks working (%) | Power working (%) |
|---|---|---|---|
| 0 | 83 | 100 | 89 |
| 1 | 72 | 56 | 50 |
| 2 | 28 | 50 | 50 |
| 3 | 11 | 22 | 39 |
| 4 | 11 | 11 | 17 |
| 5 | 11 | 11 | 11 |
The model runs on the teaching values set by the controls. To calibrate it for a place, read it against these admitted layers and series, which this page's map can draw:
Across the six pillars, led by Nexus Consortium
Models are calibrated against measured system disturbances and operating data. Planning studies are checked through operator review and post-event analysis.
| Check | How it is done |
|---|---|
| Load profile validation | Studies use measured load profiles where available |
| Backup testing | Backup systems are tested under load |
| Flexibility verification | Claimed flexibility is demonstrated in trials |
Rapid growth in inverter-based resources changes system dynamics that legacy models represent poorly. Correlated weather extremes can exceed planning assumptions.
Assembled from the Nexus Standards area profile Digital, telecom and platforms: the hazards it names, the systems and sectors that carry the loss, the controls that dampen it and the data that observe it. Choose the components, pick an initiating hazard and step through the cascade. The Map view places the run on an example geography with open data. Every coupling weight is a stated assumption you can change. A teaching model, not a forecast, an assessment or a certification. To model a place of your own choosing, open the full System Builder.
Hazards
Systems and couplings
Controls
NS-0 Constitution and principlesNS-9 Contextual UNIs (deployments, instances, programme instances)NS-11 Verification and monitoring (evidence, attestations, zero-trust conformance observation)NS-12 Software, model and AI/ML artefacts (supply chain, model cards, dataset sheets)NRS-H86 Hazard family: Telecom and data-centre failure (NHS-1 infra.digital)NRS-H54 Hazard family: Signal and platform disruption (NHS-1 cyber.platform)NRS-H93 Hazard family: Identity, trust and cryptographic failure (NHS-1 cyber.identity)NRS-H94 Hazard family: Systemic cyber events (NHS-1 cyber.systemic-cyber)NRS-T8 Software and supply-chain integrity riskNRS-X6 Cyber and digital security riskObservation
Example geography
The model, its assumptions, its data and its uncertainty, in the form a scientist or engineer would check. Structures follow published methods. The values drawn are illustrative, not findings.
The data classes behind power engineering for data centres and what is recorded about each before it is used.
| Data class | Provenance recorded | Resolution stated | Licence checked |
|---|---|---|---|
| Satellite imagery, optical and radar | sensor, processing level, acquisition date | pixel size and revisit | per scene |
| Reanalysis and climate model output | model, experiment, member, version | grid and time step | per release |
| In-situ sensors and gauges | station, instrument, calibration record | point and sampling rate | per network |
| Population and asset exposure | method, vintage, input sources | cell size and unit | per release |
| Boundaries and reference geography | producer, edition, date | scale | per edition |
Energy Nexus stewards power systems engineering for the Consortium and reviews how it is applied across platforms.
Reports is the Consortium's quarterly publication. What you know about this subject can become evidence, a case or a correction in the next edition, credited to you and published under CC BY 4.0 where it is your own work.
Never send personal data, sensitive infrastructure detail or anything you have no right to share. A contribution is reviewed before use; sending it confers no authorship or editorial rights, and sponsorship never buys a finding.
Information and enquiries are open today. An enquiry receives a reference and names the next step; applications, payments, compute allocations and registrations open only when their team, terms and review capacity exist.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information. We run no advertising. You can review your choices at any time through Privacy choices at the foot of every page.