Skip to content

GRA · Insurance Nexus

Spatial financeWhere capital meets hazard, exposure and transition

Build in Foundry

Foundry is the governed work environment where Insurance Nexus analysis would be built: hazard and exposure data in The Global Risks Index (NXS-GRX), Earth observation in NXS-EOP (earth observation and digital twins) and scenario comparison in NXS-DSS (decision cases and deliberation). Every workspace needs an authorised project with an accountable owner, data terms for each source and a review plan before anything is computed.

01Nguzo sita

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.

Select pillars · hover lines18 / 18 handoffs

Njia

Around Foundry

The pillars Foundry hands work to and receives it from.

L · F · U · S · R · A

Nguzo
6 kati ya 6
Makabidhiano
18 kati ya 18
Mizunguko
17 imefungwa

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

F01 to F14 are the recorded handoffs of the programme year, each with the artefact that moves and its phase; R1, R2, R3 and R4 carry work around the ring. A loop counts when every pillar on it is selected. Every pillar is led by the Nexus Consortium.
  1. 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
  2. FoundryWhere exposure and scenario evidence is built so supervisors, insurers and investors can read it.Insurance Nexus in FoundryFoundry
  3. UniverseWhere scenarios are tested in controlled exercises, and finance-readiness dialogues read what they mean for capital and cover.Insurance Nexus in Universeuniverse.nexus
  4. Nexus StandardsWhere disclosure and data rules are codified so risk evidence is comparable for finance and insurance.Finance, Insurance and the Economy in Standardsnexustandards.com
  5. ReportsWhere sector analysis and the finance and insurance readiness series are published, with exposure and limits stated.Insurance Nexus in ReportsReports
  6. Risk AcademyWhere finance, insurance and public-finance professionals learn to read risk evidence, on Risk Academy.Faculty of Finance and Economics in Academyrisksacademy.com

Foundry in every area of the work

AreaFoundry
UongoziEach build is led by an authorised project with an accountable owner; leadership is technical and never extends to the decision the build informs.
StrategyThe build plan follows the National Portfolio and the missions admitted for the year.
CadenceWorks all year; the controlled build runs for one month in Q2, and measured capacity results are reviewed in Q4.
OwnershipOwns projects and builds, observations and canonical data, simulation and benchmark runs, the National Portfolio record and evidence seals.
MchakatoWork moves through governed rooms on twenty systems, and every run leaves a record with its limits.
MaendeleoDevelops the cycle’s software, data and environments, and develops each country’s National Portfolio.
SimulationsRuns scenarios, experiments and benchmarks with published method and conditions; a simulated capability is not a validated result.
ReportingSupplies the permitted data bundles and sealed observations behind every edition.
UtawalaShared infrastructure made available to the Consortium for public-good purposes; it holds no vote in the governance of the standards.
Data na ushahidiCanonical observations and provenance are held in NXS-GRX, and every value carries its source and licence.
Finance and resourcingCompute and data allocations open per project when their terms and review capacity exist; temporary capacity is released at stand-down.
Risk and assuranceBuilds are signed and tested for security and interoperability, and accepted for exercise only at gate G3.
UshirikiStakeholders and service providers may establish their presence for non-profit and consortium objectives under the Terms.
CommunicationPublic pages describe each system’s purpose and design, and state what it does only as far as its record shows.
LocalObservations and models keep their place: every value carries the location and boundary it was drawn on.
KitaifaEach country’s National Portfolio is developed and tracked.
KikandaShared systems and cross-border dependencies are modelled across the countries of a region.
PlanetaryGlobal data and Earth observation are held with provenance, so planetary pressures can be read alongside national ones.

What each institution brings

PillarGCRIGRFGRA
FoundryIts 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.
03Workspace

The workspace for Build in Foundry.

Build workspace

Insurance · Build in Foundry · Run R-7855 · Example interface, not a record

Run in progressGRA · Insurance Nexus

Runs

same inputs, versioned

R-2275Actuarial mathematicsv7.70.58Running
R-3202Extreme value theoryv3.50.55Failed test
R-6302Probabilityv5.00.41Drift
R-0511Climate and atmosphericv6.10.82Drift

Model card

Mbinu
Actuarial mathematics
Inputs
Policy administration extract, Claims data
Validation
held-out period, skill reported
Label
IMEUNDWA KIMUUNDO

Run log

  1. 00:00:56InfoIngest policy administration extract
  2. 00:02:12InfoSchema and licence checks passed
  3. 00:06:40WarnGap filled by interpolation, flagged
  4. 00:16:03DoneCalibration complete
  5. 00:24:55GateIndependent test queued
Build workspace.Illustrative interface; not live data.

Insurance Nexus · Build workspace. Build workspace: example names and illustrative values, not a record.

04Data discipline

What enters a workspace.

Only data whose licence allows the intended use enters a workspace, and confidential carrier data is never required: aggregate and public sources are the default. Outputs keep the source chain so that a reviewer can rebuild them. Systems are described at Foundry.

05Mchakato

How the process runs.

Process explorer · Process

Build in Foundry: Layers to published map

7 steps4 stages1 gate

Mchakato

Build in Foundry: Layers to published map

Layers enter with their rights, are aligned, analysed and checked for uncertainty, then released after public-safe review; a map is a governed spatial claim.

  1. 01 Data

    1. 01Source layers with their rightsDataset · NXS-GRX (canonical data, provenance and risk)Spatial views of NXS-GRX products sit under the boundary licence gate. Rights classification sets how a layer may be used.
  2. 02 Oanisha

    1. 02Coordinate reference and boundary versionRecord · NXS-EOP (earth observation and digital twins)The area of interest preserves its coordinate reference system, polygon validity and observation support. Boundary versions are kept.
    2. 03Harmonise units, variables and timeStepUnit metadata, conversion records and transformation logs are required. Alignment is an evidence event, not hidden preprocessing.
  3. 03 Analyse and check

    1. 04Analyse with a recorded processing recipeModel · GIS teamA processing recipe records parameters, calibration, inputs and output lineage. The analysis methods are named in each product’s own record.
    2. 05Spatial uncertainty checkGateSpatial uncertainty is recorded and affects downstream use. A high-uncertainty polygon may suit internal review, not public-safe release.
  4. 04 Publish

    1. 06Spatial metadata bundleRecordThe bundle records boundary type, jurisdiction, geometry version, projection, resolution, source, time window, uncertainty and access class.
    2. 07Public-safe release of the mapDecisionThe output record names the redactions, uncertainty and public-safe reviewer. A map is a governed spatial claim, never merely a picture.

Spatio-temporal intelligence · Data protocols: semantic, jurisdictional and temporal intelligence · NXS-EOPDesigned 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 pages cited are design doctrine.

06Foundry systems for this

Foundry systems for this field.

MfumoWhat it does hereJukumuRead more
NXS-DSSKesi za maamuzi na mashaurianoSets out options and their trade-offs for a financial decision.This fieldDocumentationIntegrated, not bound
NXS-GRXData rasmi, asili ya data na hatariSupplies risk products by place for an exposure reading.

Index data service: unavailable. No public endpoint is published for this site yet.

This fieldDocumentationIntegrated, not bound
NXS-EOPUchunguzi wa Dunia na mapacha wa kidijitaliReads exposure from observation for spatial finance.This fieldDocumentationIntegrated, not bound
NXS-AAPHatua za kutarajia na vichocheziLinks triggers to pre-arranged finance and its records.Tovuti hiiDocumentationIntegrated, not bound
NXS-RLSWashiriki, makubaliano na makabidhianoRecords the agreements and handoffs behind a readiness file.Tovuti hiiDocumentationIntegrated, not bound
NXS-NSFTrust, authorisation and assuranceKeeps the authorisation and assurance trail of a readiness file.Tovuti hiiDocumentationIntegrated, not bound

The release of the Nexus systems is on hold. Each code links its definition in the Nexus Risk Standards.

07Access

How a project gets access.

  1. 01

    Enquiry

    Describe the project and its owner to the contact form.

  2. 02

    Authorisation

    Access requires an authorised 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.

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.

08Vyanzo

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.

09Maswali

Questions and answers.

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

Bring an exposure or capital question to the Alliance.

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.