Skip to content

GCRI · Technology

Endezyariya daneyê, hevgirtî û xwedîtî

Data engineering, interoperability and stewardship cover the pipelines, standards and governance that make data usable and trustworthy. They determine whether information from different sectors can be combined for joint risk assessment. Data and Compute stewards this page for the Nexus Consortium.

02Rêbaz

What data engineering, interoperability and stewardship covers.

  1. 01

    Core methods

    data pipeline design; schema and metadata standards; data quality assessment; provenance tracking; master data management; access control and licensing.

  2. 02

    Data and instruments

    data catalogues; application programming interfaces; metadata registries; data lakes and warehouses; open data portals.

  3. 03

    Erêkirin

    Pipelines are tested with automated quality checks, schema validation and lineage audits. Reconciliation against source systems confirms completeness.

  4. 04

    Sînor

    Incompatible standards, missing metadata and restrictive licences block integration. Legacy systems and undocumented transformations introduce silent errors.

  5. 05

    Use in risk decisions

    Sound data engineering allows hazard, exposure and financial data to be linked consistently. It supports transparent and repeatable analysis of interconnected risk.

03Reference practice

Data engineering follows stewardship, provenance and catalogue standards.

ReferansYa ku diyar dike
FAIR principlesFindable, accessible, interoperable, reusable data
W3C PROVProvenance model
W3C DCATData catalogue vocabulary
GSBPMStatistical production process model
04Pêvajo

Pêvajo çawa dimeşe.

Process explorer · Process

Data engineering, interoperability and stewardship: Catastrophe model pipeline

10 steps5 stages

Pêvajo

Data engineering, interoperability and stewardship: Catastrophe model pipeline

Catastrophe models usually have hazard, vulnerability, exposure and financial modules, and produce loss tables, average annual loss, exceedance curves, PML and TVaR.

  1. 01 Hazard

    1. 01Event catalogueDataset · Model developerThe hazard module holds a large catalogue of simulated events that represents a wide range of plausible scenarios.
    2. 03Hazard moduleModel · Model developerFor each event the hazard module gives the local hazard intensity that the vulnerability module reads.
  2. 02 Exposure and damage

    1. 02ExposureDataset · Programme ownerThe exposure module houses the portfolio data, such as location-specific information.
    2. 04Vulnerability moduleModel · Model developerThe vulnerability module quantifies the expected damage to the exposures from an event.
  3. 03 Financial

    1. 05Financial moduleModel · Programme ownerThe financial module calculates losses from all event scenarios. Ground-up, gross and net losses differ as shown below.
    2. 06Event loss tableDataset · Programme ownerAn event loss table lists each event with its annual occurrence probability and its loss for the portfolio.
    3. 07Year loss tableDataset · Programme ownerSome models also sample simulated years from event losses. This outline does not describe their format.
  4. 04 Metrics

    1. 08Exceedance probability curvesModel · Programme ownerThe occurrence curve gives the chance that the largest loss in a year exceeds an amount. The aggregate curve does so for the sum of losses.
    2. 09AAL, PML and TVaRModel · Programme ownerAverage annual loss sums event probability times loss. PML is one point on the occurrence curve.
  5. 05 Use of results

    1. 10Use of resultsDecision · Programme ownerThe tail metrics are used when considering a portfolio’s exposure and the level of catastrophe reinsurance an insurer requires.

Outline of an external standard or method, from its public sources. It describes what the framework says, not a record of any run. It does not show that Nexus or any partner performs, certifies or approves a step. A gate is a step of the method, never a Nexus approval.

05In systemic risk work

The pipeline is part of the evidence.

Every transformation between a source and a published figure (cleaning, joining, imputing, aggregating) is a place where errors and assumptions enter. In cross-system analysis pipelines are long and shared, so provenance records are what make a figure traceable and a correction possible.

  • Record provenance at each transformation.
  • Make imputation visible in outputs.
  • Version datasets so a figure can be regenerated.
  • Applications on Registry and Reports.
07Parastin û serperiştî

Who maintains this page.

Data and Compute stewards data engineering, interoperability and stewardship: it keeps this description current and reviews how the method is applied across the platforms.

08Çavkanî

Where this page’s references lead.

Sazî û belgeyên ku ev rûpel li hember wan tê xwendin. Rewş û çap diguherin; her girêdan diçe ba saziya derxistinê.

09Pirs

Pirs û bersiv.

Why does one institution host every method page?
GCRI hosts the STEM Commons so that each method has one canonical description. Platforms link to it rather than repeat it, which keeps definitions consistent.
How do I suggest a correction to a method page?
Write to the integrity concern form with the passage and the reason.
rêzeya Pergalên StratejîkTevkarî bike

Ji vê rûpelê delîl bidin.

Reports weşana sê mehane ya Konsorsiyûmê ye. Tiştê ku tu li ser vê mijarê dizanî dikare di çapa pêş de bibe delîl, dosya an rastkirin, bi navê te û di bin CC BY 4.0 de weşandî li cihê ku karê te bi xwe be.

GCRI
Global Centre for Risk and Innovation

Rêbazek, danehevek an pirsek bîne.

Agahî û pirs îro vekirî ne. Pirsek referansekê distîne û gava piştî wê dide nasîn; serlêdan, drav, veqetandina hesabkirinê û tomarkirin tenê dema ku tîm, mercên wê û kapasîteya vekolînê hebin vedibin.