GCRI · Energy Nexus
Methods and uncertainty
The methods Energy Nexus relies on: their equations and assumptions, the data they need, how they are validated and the limits of what they can show.
The order things happen in.
- 01Draftsources cited, labels attached
- 02Evidence checkevery value traced
- 03Independent reviewconflicts declared
- 04Editionpublished with its limits
- 05Correctiona new version, never a silent edit
The methods in use.
- 01Energy generation, storage and grid technologyWeather-driven generation profiles · Storage technology comparisonApplied here
- 02Power systems engineeringContingency and load flow studies · Frequency stability with less inertiaApplied here
- 03Reliability and resilience engineeringRestoration curve analysis · Fault trees for critical sites · Fragility curves for grid assetsApplied here
- 04Optimisation and operations researchCapacity expansion planning · Unit commitment and dispatch · Restoration sequencingApplied here
- 05Forecasting and time-series analysisLoad forecasting with weather · Wind and solar power forecasts · Seasonal adequacy outlooksApplied here
- 06Network science and contagionInterdependency mapping · Cascades on multilayer networks · Criticality rankingApplied here
- 07Materials science and chemistryBattery chemistry and thermal runaway · Ageing and corrosion of grid assetsApplied here
- 08Process and industrial safety engineeringNatural hazards triggering accidents · Layers of protection reviewApplied here
Each method, its role in this field and how it is checked.
- Energy technologyRole hereEnergy technology assessment is how this platform reads the hardware of the energy system: what generators, storage devices, converters and grid equipment can deliver, under which conditions and with which failure modes.Checks appliedMetered comparison; Standard test conditions; Degradation tracking
- Power engineeringRole herePower systems engineering is the core discipline of this platform: load flow, contingency, stability and protection analysis show how a grid behaves in normal operation and after a fault, and how a failure in one place reaches dependent services elsewhere.Checks appliedEvent replay; Benchmark networks; Operator review
- Resilience engineeringRole hereReliability and resilience engineering asks how energy assets and systems fail, how quickly they recover, and which components and organisational arrangements set the recovery time.Checks appliedField data comparison; Common-cause review; Exercise and post-event review
- OptimisationRole hereOptimisation and operations research decide how energy systems are built and run at least cost within physical and policy limits: which plants to build, how to dispatch them, how much storage and transmission to add, and in what order to restore service after a failure.Checks appliedOperational feasibility; Sensitivity and robustness; Open model comparison
- ForecastingRole hereForecasting gives energy operators lead time: minutes to days for demand and renewable output, weeks to seasons for hydropower inflows and adequacy outlooks.Checks appliedOut-of-sample verification; Reliability diagrams; Extreme-event performance
- Network scienceRole hereNetwork science maps the energy system as connections: lines and substations, pipelines and terminals, and the dependencies that link them to water, telecommunications, transport and finance.Checks appliedHistorical cascade reproduction; Missing link sensitivity; Disclosure review
- Materials chemistryRole hereMaterials science and chemistry explain how energy equipment ages and fails, and which materials the transition depends on: battery chemistries and their thermal behaviour, corrosion of pipelines and towers, insulation ageing in transformers, and the critical minerals in magnets, cells and electrolysers.Checks appliedLaboratory to field comparison; Traceable measurement; Supply data cross-check
- Process safetyRole hereProcess safety engineering covers the hazards of energy facilities: refineries, gas terminals, hydrogen plants, battery storage sites and nuclear installations.Checks appliedIncident learning check; Independence of barriers; Regulatory boundary
How the process runs.
Process
Methods and uncertainty: Source to evidence record
A source is registered and assessed, its record labelled and classified, and a Digital Evidence Passport carries provenance; a correction reaches every dependent record.
01 Intake
- 01Identify the sourceSource · The source stewardDiscovery is not ingestion. Source identification records the source class, steward, institutional role and jurisdiction.
- 03Register the sourceStepRegistration makes a discovered source a governed participant in the evidence lifecycle. It implies no endorsement or certification.
02 Assessment
- 04Jurisdiction and rights classificationGateRights classification identifies licence, consent, confidentiality and reuse limits. The result determines access and routing.
- 05Evidence quality assessmentStepQuality assessment decides whether a record is fit for a defined use. Quality is multidimensional and never a single score.
- 06Evidence labelStepEvery finding carries one of nine evidence labels. Missing data is shown as missing, never as zero.
03 Record
- 07Evidence classificationRecordClassification gives records lifecycle states, such as source-verified, public-safe or restricted. States can coexist and set evidence use.
- 08Source release and identifierRecord · NXS-GRX (canonical data, provenance and risk)A source release records rights, temporal coverage and source lineage. A UNI is allocated through a catalogue and never typed by hand.
- 09Digital Evidence PassportRecordThe passport records provenance, quality, rights, jurisdiction, permitted use and history, so evidence keeps its context when it travels.
04 Use and correction
- 02Correction reaches dependent recordsStep · NXS-GRX (canonical data, provenance and risk)A source correction propagates to dependent cuts and products without rewriting old results.
- 10Public-safe reviewGatePublic-safe review decides whether a record can be shared publicly. It is a distinct stage and is not validation.
Data protocols: evidence lifecycle · Data protocols: core data objects and evidence records · The Global Risks Index (NXS-GRX)Designed programme process, not a record of operation. No cycle has run and every programme is at service level R0. A gate is a programme decision, never a public-authority approval, certification or deployment authorisation. The data-protocol pages describe a design, not a running system.
Where uncertainty in energy analysis comes from, and how it is shown.
| Source | Why it matters here | How it is reported |
|---|---|---|
| Weather years | Adequacy depends on rare multi-day weather patterns | Many historical and synthetic weather years, not one typical year |
| Demand growth | Electrification and data-centre load are uncertain in size and timing | Demand scenarios with stated drivers |
| Fuel supply | Gas and fuel availability depends on world markets and infrastructure | Supply-disruption scenarios |
| Equipment reliability | Forced outage rates change with age, heat and maintenance | Reliability ranges from operator data |
| Market behaviour | Prices and investment respond to policy and expectations | Policy scenarios rather than price forecasts |
Adequacy results are reported as probabilistic metrics (loss-of-load expectation, expected unserved energy) with the weather and demand sets they rest on.
How uncertainty is reported.
- 01
State assumptions
Each analysis lists its assumptions and the data it depends on.
- 02
Quantify where possible
Ranges and confidence are reported alongside central estimates.
- 03
Validate and compare
Models are checked against observations and, where possible, against other models.
- 04
Publish limits
What an analysis cannot show is stated beside what it can.
Where this page’s references lead.
The bodies and documents this page is read against. Status and editions change; each link goes to the issuing body.
Questions and answers.
Are the methods open?
Contribute evidence from this page.
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.
- EmailGateway GW-GCRISend it from this pageEvidence, a correction, a case, a method, a review, a translation or profile input. It arrives tagged with this page, so the editor who owns it receives it.
- ZenodoOpen depositDeposit it and submit to the communityPublish your own record on Zenodo with your ORCID iD, then submit it to the Reports community there. Curators review it; the DOI stays yours.
- ReportsGCRISee every way to contributeThe contribution types, how each is reviewed, what credit you receive, the licence and what is never accepted.
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.
Bring a method, a dataset or a question.
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.
Legal documents.
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.