Skip to content

GRA · Development Finance Nexus

Spatial financeWhere capital meets hazard, exposure and transition

Analytical and data resources

Development Finance Nexus tools put investment, hazard and need on one map. Spatial finance shows where public investment sits against flood, drought and heat, where people and assets are exposed, and where the evidence for a programme is thin. Every tool states sources, resolution and uncertainty, and values shown before release are design values.

01Workspace

The workspace for analytical and data resources.

Pipeline

Analytical and data resources · Workspace WS-98 · Example interface, not a record

One stage waitingGRA · Development Finance Nexus

Stages

  1. Ingest4 sources
  2. Validateschema · licence
  3. Transformversioned
  4. ImodeliEzomnotho
  5. Testheld-out
  6. Releasewith limits

Artefacts

Project documentsv3.8VulaPublished statistics
Hazard layersv6.3VulaMODELLED
Safeguard reportsv1.6VulaREPORTED
Disbursement recordsv6.4VulaPublished statistics

Compute quota

share used vs alert level

CPU hours75 used of 80 used limitStorage53 used of 90 used limitGPU hours53 used of 70 used limit
Pipeline.Illustrative interface; not live data.

Development Finance Nexus · Pipeline. Pipeline: example names and illustrative values, not a record.

02Amathuluzi

What is published here.

Maps

Released maps

Open the released maps

Models

Reviewed models and scenarios

Open the reviewed models

Scenarios

Sector scenarios

Open the sector scenarios

03Tool set

Maps, models and scenarios, with limits.

ToolWhat it showsUmkhawulo
Need-investment mapHazard, poverty and public investment by districtSubnational investment data is often missing
Robust appraisal sketchHow an investment's net benefit varies across climate and demand scenariosTeaching example; real appraisal uses project data
Dossier completeness checkWhich elements of an appraisal-ready dossier exist and which are missingChecks presence, not quality
Debt shock viewHow a disaster shock moves a stylised debt pathSynthetic; real analysis is the IMF and World Bank's
04Inqubo

How the process runs.

Process explorer · Process

Analytical and data resources: Build, sign and accept

10 steps4 stages2 gates

Inqubo

Analytical and data resources: Build, sign and accept

An admitted mission becomes a cycle project; the build is pinned, verified and signed, and the Global Risks Forum (GRF) records acceptance for exercise, not permission to deploy.

  1. 01 Request and sources

    1. 01Admitted mission becomes a cycle projectRecord · Universe to FoundryAn admitted mission becomes a cycle project with a decision case.
    2. 02Qualify data sources and resourcesStep · the Global Centre for Risk and Innovation (GCRI)GCRI qualifies data sources and resource offers and builds the scenario models. An offer is not an allocation.
  2. 02 Build and verify

    1. 03Source snapshotRecord · NXS-FAC (blueprints, builds and signing)The snapshot pins the commit, dependencies and generator versions.
    2. 04Build contractRecord · NXS-FAC (blueprints, builds and signing)The build contract declares the artefact kind, environment and reproducibility envelope.
    3. 05Integrate and buildModel · GCRIGCRI integrates software and data, signs builds, and tests security and interoperability.
    4. 06Verification suiteGate · NXS-FAC (blueprints, builds and signing)Required and advisory checks stay separate. Reproducibility needs pinned inputs, declared nondeterminism and independent rebuilds.
  3. 03 Sign and admit

    1. 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.
    2. 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.
  4. 04 Accept

    1. 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.
    2. 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.

05Scenarios

Where designs are set out.

Scenario families are at published scenarios. Decision methods: GCRI Systems Modelling.

06Build environment

Working with the tools.

Analysis runs in Foundry for authorised projects. Public pages show released views only, each with its time and space reference and its rights.

07Imithombo

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.

08Pages

Pages in Analytical and data resources.

09Imibuzo

Questions and answers.

Can I use the data?
Each released view states its licence and terms. Data that is not released is not available through these pages.
ImibikoNikela

Nikela ngobufakazi kusuka kuleli khasi.

I-Reports iyincwadi yekota ye-Consortium. Lokho oakwaziyo ngalesi sihloko kungaba ubufakazi, icala noma ukulungisa kuhlelo olulandelayo, kubongwe wena futhi kushicilelwe ngaphansi kwe-CC BY 4.0 lapho kungumsebenzi wakho.

Global Risks AllianceDevelopment Finance NexusFinance and Insurance ReadinessPortfolio and Readiness
Development Finance Nexus: Ezezimali Zentuthuko

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.