GCRI · Energy Nexus
Build in Foundry
The Foundry systems that serve Energy Nexus, what an authorised project can do with them, and how access is requested. Foundry’s public home is therisk.global/nexus-foundry.
Foundry among the six pillars.
Where things are built, simulated and prepared: every output of the Global Centre for Risk and Innovation (GCRI), the Global Risks Forum (GRF) and the Global Risks Alliance (GRA), under the Nexus Consortium. It is led by the Nexus Consortium; its home is therisk.global/nexus-foundry.
handoff in playrecorded handoffno direct handoff
Programme yearAll phases
Route
Around Foundry
The pillars Foundry hands work to and receives it from.
L · F · U · S · R · A
- Pillars
- 6 of 6
- Handoffs
- 18 of 18
- Loops
- 17 closed
Handoffs in play
- F01Universe → Foundry · Admitted mission becomes a cycle project with a decision caseReadiness preparation
- F02Foundry → Universe · Core Build Report and go or no-go evidenceControlled build
- F03Foundry → Reports · Sealed observations and indicator series behind a profileCloseout
- F04Universe → Reports · After-action and scenario findings for chapters 10 and 13After-action review
and 14 more
- LabsWhere questions become experiments and prototypes: new methods, data and tools are tried in the open, with their limits on record, before the Foundry builds them, under the Nexus Consortium.Labs
- FoundryWhere methods, data and models become reproducible builds, each run with its inputs, version and limits on record.Energy Nexus in FoundryFoundry
- UniverseWhere a build is tested under controlled conditions with independent evaluators, so a method’s skill is measured, not assumed.Energy Nexus in Universeuniverse.nexus
- Nexus StandardsWhere methods, identifiers and data schemas are codified in the open and corrected when a test finds a fault.Energy and Critical Infrastructure in Standardsnexustandards.com
- ReportsWhere findings are published with their method, uncertainty and evidence class, and corrected as new versions.Energy Nexus in ReportsReports
- Risk AcademyWhere methods and systems are taught on real data and real places, by working the case, on Risk Academy.Faculty of Infrastructure, Energy and Industry in Academyrisksacademy.com
Foundry in every area of the work
| Area | Foundry |
|---|---|
| Leadership | Each build is led by an authorised project with an accountable owner; leadership is technical and never extends to the decision the build informs. |
| Strategy | The build plan follows the National Portfolio and the missions admitted for the year. |
| Cadence | Works all year; the controlled build runs for one month in Q2, and measured capacity results are reviewed in Q4. |
| Ownership | Owns projects and builds, observations and canonical data, simulation and benchmark runs, the National Portfolio record and evidence seals. |
| Process | Work moves through governed rooms on twenty systems, and every run leaves a record with its limits. |
| Development | Develops the cycle’s software, data and environments, and develops each country’s National Portfolio. |
| Simulations | Runs scenarios, experiments and benchmarks with published method and conditions; a simulated capability is not a validated result. |
| Reporting | Supplies the permitted data bundles and sealed observations behind every edition. |
| Governance | Shared infrastructure made available to the Consortium for public-good purposes; it holds no vote in the governance of the standards. |
| Data and evidence | Canonical observations and provenance are held in The Global Risks Index (NXS-GRX), and every value carries its source and licence. |
| Finance and resourcing | Compute and data allocations open per project when their terms and review capacity exist; temporary capacity is released at stand-down. |
| Risk and assurance | Builds are signed and tested for security and interoperability, and accepted for exercise only at gate G3. |
| Participation | Stakeholders and service providers may establish their presence for non-profit and consortium objectives under the Terms. |
| Communication | Public pages describe each system’s purpose and design, and state what it does only as far as its record shows. |
| Local | Observations and models keep their place: every value carries the location and boundary it was drawn on. |
| National | Each country’s National Portfolio is developed and tracked. |
| Regional | Shared systems and cross-border dependencies are modelled across the countries of a region. |
| Planetary | Global data and Earth observation are held with provenance, so planetary pressures can be read alongside national ones. |
What each institution brings
| Pillar | GCRI | GRF | GRA |
|---|---|---|---|
| Foundry | Its science and technical platforms bring the methods, data and evidence that the Foundry builds on. | Admits missions and accepts the build for exercise at a recorded gate, so Foundry work enters the programme on the record. | Brings finance-readiness questions, so builds produce evidence that financial institutions can read. |
The Foundry systems that energy work draws on.
- NXS-COR (compute, nodes and runtimes)NXS-CORCompute for large adequacy and capacity expansion runs
- NXS-NET (network topology and continuity)NXS-NETTelecom dependencies of grid control and restoration
- NXS-DSS (decision cases and deliberation)NXS-DSSInvestment and policy options across weather and demand scenarios
- NXS-NSTNXS-NSTCommon operating picture for restoration exercises
- NXS-GRXNXS-GRXEnergy indicators with other country indicators
The workspace for Build in Foundry.
Build workspace
Energy · Build in Foundry · Run R-1667 · Example interface, not a record
Runs
same inputs, versioned
| R-4483 | Energy generation | v3.5 | 0.85 | Running |
| R-4829 | Power systems | v5.4 | 0.57 | Passed |
| R-6725 | Reliability | v9.5 | 0.45 | Passed |
| R-6513 | Optimisation | v8.0 | 0.45 | Drift |
Model card
- Method
- Energy generation, storage and grid technology
- Inputs
- Outage register, Demand forecast
- Validation
- held-out period, skill reported
- Label
- MODELLED
Run log
- 00:00:14InfoIngest outage register
- 00:02:12InfoSchema and licence checks passed
- 00:05:40WarnGap filled by interpolation, flagged
- 00:14:03DoneCalibration complete
- 00:27:55GateIndependent test queued
Energy Nexus · Build workspace. Build workspace: example names and illustrative values, not a record.
Foundry systems for this field.
| System | What it does here | Role | Read more |
|---|---|---|---|
| NXS-CORCompute, nodes and runtimes | Runs compute, nodes and runtimes behind authorised projects. | This field | DocumentationNot bound |
| NXS-NETNetwork topology and continuity | Maps network topology and continuity for infrastructure studies. | This field | DocumentationNot bound |
| NXS-DSSDecision cases and deliberation | Turns evidence into decision cases with stated uncertainty. | This field | DocumentationIntegrated, not bound |
| NXS-NSTCivilian common operating picture | Shows the common operating picture as a map on the page. | This field | DocumentationIntegrated, not bound |
| NXS-GRXCanonical data, provenance and risk | Holds the canonical data, provenance and risk records the field cites. Index data service: unavailable. No public endpoint is published for this site yet. | This field | DocumentationIntegrated, not bound |
| NXS-EOPEarth observation and digital twins | Brings Earth observation scenes and digital twins into the field. | This site | DocumentationIntegrated, not bound |
| NXS-EWSMulti-hazard monitoring and warning | Carries monitoring and warning layers for the hazards of the field. | This site | DocumentationIntegrated, not bound |
| NXS-LABResearch, experiments and simulations | Runs research, experiments and simulations before anything is built. | This site | DocumentationIntegrated, not bound |
| NXS-PORPublic, client and partner delivery | Delivers released views and maps into the page. | This site | DocumentationIntegrated, not bound |
The release of the Nexus systems is on hold. Each code links its definition in the Nexus Risk Standards.
How the process runs.
Process
Build in Foundry: Build, sign and accept
An admitted mission becomes a cycle project; the build is pinned, verified and signed, and GRF records acceptance for exercise, not permission to deploy.
01 Request and sources
- 01Admitted mission becomes a cycle projectRecord · Universe to FoundryAn admitted mission becomes a cycle project with a decision case.
- 02Qualify data sources and resourcesStep · GCRIGCRI qualifies data sources and resource offers and builds the scenario models. An offer is not an allocation.
02 Build and verify
- 03Source snapshotRecord · NXS-FAC (blueprints, builds and signing)The snapshot pins the commit, dependencies and generator versions.
- 04Build contractRecord · NXS-FAC (blueprints, builds and signing)The build contract declares the artefact kind, environment and reproducibility envelope.
- 05Integrate and buildModel · GCRIGCRI integrates software and data, signs builds, and tests security and interoperability.
- 06Verification suiteGate · NXS-FAC (blueprints, builds and signing)Required and advisory checks stay separate. Reproducibility needs pinned inputs, declared nondeterminism and independent rebuilds.
03 Sign and admit
- 07Sign the exact artefactStep · NXS-FAC (blueprints, builds and signing)NXS-FAC builds, attests and requests a signature via a scoped signer identity. It holds no key material.
- 08Package admissionStep · NXS-NXQ (software, models and capability lifecycle)NXS-NXQ receives the signed package and keeps admission evidence that binds the task, data class, evaluation suite and expiration.
04 Accept
- 09Core Build ReportRecord · GCRIThe Core Build Report is the go or no-go record. Universe assembles the Core and holds the decision for the exercise.
- 10G3 · Build accepted for exerciseGate · The Global Risks ForumGRF records whether the build is accepted for exercise. A signed build or release candidate is not permission to deploy to production.
The programme year · NXS-FAC · UniverseDesigned 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 record order follows the Builds and Releases room lists of NXS-FAC.
How a project gets access.
- 01
Enquiry
Describe the project and its owner to the contact form.
- 02
Authorisation
Access requires an authorised project with an accountable owner, data terms and a review plan.
- 03
Allocation
Compute and data allocations open when their terms and review capacity exist.
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.
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.
Is Foundry access free?
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.