G01 · PROCESS · foundryGCRI dossier · service level R0
GCRIWater NexusEstablished
Build in Nexus Foundry

Build in Nexus Foundry

The Nexus Foundry systems that serve Water Nexus, what an authorized project can do with them, and how access is requested.

Publisher
The Global Centre for Risk and Innovation
Field
Water, Climate and hazards, Critical infrastructure
Canvas · scoping to reviewDesign, not a record
Build in Nexus Foundry: build, test and release in Nexus FoundryA request opens a workspace; data are ingested and validated; the model is built and tested on held-out data; an independent gate approves release with limits; the workspace is stood down and the record kept. Design of the process, not a record of a run.

Fig.A programme from scoping to the owner's decision. Design, not a record.

01In brief

The short answer.

Building in Nexus Foundry is how authorized Water Nexus projects use the shared technical systems that serve water: EOP, GRIx, EWS, DSS and OP. Access requires an accountable project owner, data terms and a review plan, and allocations open only when their terms and review capacity exist. Foundry work produces designs and analyses with their limits, not operational services.

02Geography

Water security in Kenya.

Rivers, lakes and how far each division sits from mapped surface water, shown for Kenya as an example geography for this subject.

Rivers, lakes and how far each division sits from mapped surface water.Indicator derived from Natural Earth at map scale; a screening view, not an assessment.
GCRI · Water Nexus · fieldDESIGN FIGURE
03Systems

Foundry systems for this field.

05Access

How a project gets access.

  1. 01

    Enquiry

    Describe the project and its owner to contact@therisk.global.

  2. 02

    Authorization

    Access requires an authorized project with an accountable owner, data terms and a review plan.

  3. 03

    Allocation

    Compute and data allocations open when their terms and review capacity exist.

The current service level is R0: information and enquiries. 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.

06Key terms

Terms used on this page.

Each term as this page uses it. Where a standard-setting body defines the term, the wording follows that body.

TermDefinition
Digital twinA computational representation of a physical system that is updated with data from it and used to explore its behaviour.
ProvenanceInformation about the entities, activities and people involved in producing a record, used to judge its quality and reliability, in the W3C PROV model.
Least privilegeGranting each user or process only the access needed for its current task.
Workflow orchestrationAutomated management of the order, execution and recovery of computational tasks.
07Sources

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.

08Connected

Where this page leads across the Consortium.

09Questions

Questions and answers.

Is Foundry access free?
Terms are set per project when allocations open.
Water Nexus

Bring your expertise to this field.

The current service level is R0: information and enquiries. 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.

Have questions?