Skip to content

GCRI · Systemic Risk Management

Data and technical methods

The public technical tools of Systemic Risk Management: the models and data behind them, how to reproduce a view and the uncertainty it carries.

01Indawo yokusebenzela

The workspace for data and technical methods.

Build workspace

Systemic risk · Data and technical methods · Run R-8040 · Example interface, not a record

Run in progressGCRI · Systemic Risk Management

Runs

same inputs, versioned

R-7263Decision analysisv5.30.67Running
R-4068Scenario designv7.70.69Passed
R-7209Probabilityv7.70.44Ukutyibilika
R-2861Network sciencev6.60.47Passed

Model card

Indlela yokusebenza
Uhlalutyo lwezigqibo phantsi kokungaqiniseki
Inputs
Risk register, KRI feeds
Ukuqinisekiswa
held-out period, skill reported
Ileyibhile
KUMODELWE

Run log

  1. 00:00:52InfoIngest risk register
  2. 00:04:12InfoSchema and licence checks passed
  3. 00:05:40WarnGap filled by interpolation, flagged
  4. 00:13:03DoneCalibration complete
  5. 00:25:55GateIndependent test queued
Build workspace.Illustrative interface; not live data.

Systemic Risk Management · Build workspace. Build workspace: example names and illustrative values, not a record.

02Izixhobo

What is published here.

Iimephu

Released maps

Open the released maps

Models

Reviewed models and scenarios

Open the reviewed models

Iimeko-mfanekiso

Sector scenarios

Open the sector scenarios

03Fitness for purpose

What every risk management tool should state about itself.

Risk Management’s tools are registers, scenario sets and stress-test templates rather than maps; the maps page shows country risk composites only as context, with their components visible.

  • Which risk taxonomy a register uses.
  • Whether a score is ordinal or quantitative.
  • The scenario set behind any stress result.
04Inkqubo yokusebenza

Indlela inkqubo eqhuba ngayo.

Process explorer · Process

Data and technical methods: Layers to published map

7 steps4 stages1 gate

Inkqubo yokusebenza

Data and technical methods: 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 The Global Risks Index (NXS-GRX) products sit under the boundary licence gate. Rights classification sets how a layer may be used.
  2. 02 Lungelelanisa

    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 Papasha

    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.

05Build 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.

06Imithombo

Where this page’s references lead.

Amaqumrhu namaxwebhu eli phepha elifundwa ngokuthelekiswa nawo. Imeko neenguqulelo ziyatshintsha; ikhonkco ngalinye liya kwiqumrhu elikhuphayo.

07Amaphepha

Pages in Data and technical methods.

08Imibuzo

Imibuzo neempendulo.

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

Faka ubungqina obuvela kweli phepha.

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.

GCRIUlawulo Lomngcipheko WenkquboImeko-mfanekiso noVavanyo loXinzeleloIindlela nezobuGcisaIpotifoliyo noKulungela
Ulawulo Lomngcipheko Wenkqubo

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.