G09 · PAGE · grixGCRI dossier · service level R0
GCRINexus FoundryEstablished
Nexus Foundry · GRIx

GRIx

GRIx, the Global Risks Index system, is the risk data fabric: indicators, datasets and derived risk products for countries and sectors, each with its source, method, version and evidence label.

Publisher
The Global Centre for Risk and Innovation
Field
Data and compute, Methods and modelling
Canvas · the Nexus cycleDesign, not a record
The Nexus cycle on Nexus FoundryA question from a programme becomes evidence, a governed build, an organized community, a controlled test, a reviewed publication and a decision taken by the competent authority. Design of the cycle, not a record of a run.

Fig.The Nexus cycle, from question to renewal. Design, not a record of a run.

01In brief

The short answer.

GRIx Ontology and Semantic Risk Studio is the Nexus Foundry system for the risk ontology, indices and evidence packs that register, standardize, link and score risk data. It serves 34 platforms, among them Water Nexus and Food Nexus, and its stated limit is that source rights and limitations persist in every product. Access is through an authorized project with an accountable owner, data terms and a review plan.

02Geography

Digital demand and connectivity in Kenya.

Urban demand centres and the hubs that anchor digital and data infrastructure, shown for Kenya as an example geography for this subject.

Urban demand centres and the hubs that anchor digital and data infrastructure.Indicator derived from Natural Earth at map scale; a screening view, not an assessment.
GCRI · Nexus Foundry · fieldDESIGN FIGURE
04The problem it addresses

Risk indicators from different sources do not join cleanly.

Country risk analysis combines official statistics, Earth observation, model outputs and expert assessments with different definitions, units and update cycles. A risk data fabric harmonises them while keeping each value's lineage, so that a composite never hides what it is made of.

  • Indicator definitions and metadata in a shared register.
  • Lineage from source to derived product.
  • Evidence labels carried into every output.
05Reference practice

The standards a design like this is read against.

ReferenceRelevance
SDMXExchange of statistical data and metadata
UN Fundamental Principles of Official StatisticsQuality and independence of official data
W3C PROVProvenance of derived products
06Neighbouring systems

What it exchanges with the other systems.

  • Supplies DSS and Portals.
  • Takes observation from EOP and OP.
07Access

Authorized projects only.

Access requires an authorized project with an accountable owner, data terms and a review plan. Enquiries go to contact@therisk.global.

08Key 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
Controlled vocabularyAn agreed list of terms used to describe data consistently.
Semantic interoperabilityAgreement on the meaning of exchanged data so that systems interpret it the same way.
Data provenanceA record of where data came from and how it was changed on its way to an analysis.
09Sources

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.

10Questions

Questions and answers.

Is the system available now?
Allocations open when their terms and review capacity exist; the current service level is R0, information and enquiries.
Nexus Foundry

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?