Requirements for decision models
The questions a model must answer, the accuracy needed and the conditions it must cover are written as requirements before modelling begins, then traced to tests.
GCRI · Systems Science and Modelling
Systems engineering is the method this platform stewards for the network. It brings requirements, architecture, interfaces, verification and life cycle management to models and coupled systems, so that complex modelling efforts are defined, built and tested deliberately.
Systems engineering is an interdisciplinary approach to designing and managing complex systems over their life cycle. It focuses on requirements, interfaces and interactions so that the whole performs as intended. In methods and modelling, risk management and systemic risk and research and evidence, systems engineering exposes interfaces where failures propagate between components and organisations. It supports designing interconnected infrastructure with explicit dependency management. The canonical description is on the STEM Commons.
The questions a model must answer, the accuracy needed and the conditions it must cover are written as requirements before modelling begins, then traced to tests.
Variables, units, time steps and owners at each model interface are documented, so coupling errors can be found and fixed.
Models are managed from design through use to retirement, with versions, reviews and change control recorded.
Population density, flood water and night lights over North America, from NASA GIBS. Each layer carries its own date.
Imephu esebenzisanayo idinga i-JavaScript; uhlu lwezendlalelo nemithombo luphansi.
Izendlalelo 3
Hazards and exposure, for this page
Ikhibhodi, kugxilwe emephini
Bamba u-Ctrl noma u-⌘ bese uskrola ukuze usondeze
Okutholakala kwakamuva
NASA GIBS / EOSDIS · ASTER GDEM (METI, NASA) · Blue Marble (NASA) · © abanikele ku-OpenStreetMap (ODbL) · Natural Earth
Iyalayisha izithombe zakamuva ze-NASA.
Donsa ukuze unyakazise. U-Ctrl noma u-⌘ bese uskrola, ucindezele ngeminwe emibili noma izinkinobho ukuze usondeze; beka isikhombi ukuze ubone amanani aphansi kwaso; ukusetha kabusha kubuyisela esifundeni.
Hazards and exposure, framed on North America.Satellite and model products as NASA publishes them, each with its own date. They are indicators, not assessments of any place.
Izendlalelo nezinsuku
Datasets and records used by systems engineering on this platform, with the role each plays and the label its values carry. Sources are listed in the source register.
| Idatha | Indima | Label |
|---|---|---|
| Requirements documents | Purpose and accuracy | DECLARED |
| Interface control documents | Coupling specifications | DECLARED |
| Test and review records | Ukuqinisekiswa | OBSERVED |
Assembled from the Nexus Standards area profile Compound and cascading hazard standards: the hazards it names, the systems and sectors that carry the loss, the controls that dampen it and the data that observe it. Choose the components, pick an initiating hazard and step through the cascade. The Map view places the run on an example geography with open data. Every coupling weight is a stated assumption you can change. A teaching model, not a forecast, an assessment or a certification. To model a place of your own choosing, open the full System Builder.
Izingozi
Systems and couplings
Controls
NS-0 Umthethosisekelo nezimisoNS-3 Ama-UNI amarekhodi obungozi (uhlelo lolimi, ukuqhathanisa nezinhlelo ezindala, igunya lokwabela)NS-9 Ama-UNI omongo (ukufakwa, izibonelo, izibonelo zohlelo)NS-11 Ukuqinisekisa nokuqapha (ubufakazi, izifakazelo, ukuqapha ukuhambisana ngaphandle kokwethembana)NRS-H61 Umndeni wezingozi: Ukwehluleka okulandelanayo (NHS-1 sys.cascade)NRS-H62 Umndeni wezingozi: Izehlakalo ezihlangene nezezingozi eziningi (NHS-1 sys.compound)NRS-H60 Umndeni wezingozi: Ukuphazamiseka kochungechunge lokuhlinzeka nokugeleza (NHS-1 sys.supply-chain)NRS-H94 Umndeni wezingozi: Izehlakalo ze-inthanethi zesistimu (NHS-1 cyber.systemic-cyber)NRS-H107 Umndeni wezingozi: Ukugxila nokufana kwengqalasizinda yedijithali (NHS-1 tech.digital-concentration)NRS-H7 Umndeni wezingozi: Ukungajwayeleki kokujikeleza okukhulu komoya (NHS-1 atmo.climate-mode)Observation
Example geography
Each requirement is traced to verification evidence from analysis, inspection, demonstration or test. Independent reviews check completeness at life cycle gates.
| Check | How it is done |
|---|---|
| Requirements traceability | Each requirement is traced to a verification activity |
| Interface review | Interface specifications are reviewed by both model owners |
| Change impact analysis | Changes are assessed for effects on validated results |
Emergent behaviour in open or socio-technical systems may not be captured by requirements. Rigid processes can slow adaptation to change.
The model, its assumptions, its data and its uncertainty, in the form a scientist or engineer would check. Structures follow published methods. The values drawn are illustrative, not findings.
The model structure used for systems engineering for models, the assumptions it makes and how each is tested.
Ri = f(Hi, Ei, Vi, Ci)hazard, exposure, vulnerability and coping capacityEAL = ∑k pk · Lkover events k with annual probability pkxt+1 = A xt + B ut + εtA carries the couplings, u the shock, ε the error| Assumption | Why it is made | How it is tested |
|---|---|---|
| Hazard and exposure are independent within an event | Keeps the loss integral tractable | Compare with a copula fit on joint records |
| Couplings are linear near the operating point | Lets shocks propagate through A | Perturb beyond the linear range and compare |
| Vulnerability curves transfer between places | Local curves are rarely available | Validate against observed losses where they exist |
Process explorer · Process
8 steps·4 stages
Inqubo
An initial hazard can trigger later risks and events; this illustration draws one cascade across systems such as energy, water, ICT, health and transport.
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. The dependencies are examples. A dependency survey for the place sets them.
Systems Science and Modelling stewards systems engineering for the Consortium and reviews how it is applied across platforms.
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.
Ungalokothi uthumele idatha yomuntu siqu, imininingwane ebucayi yengqalasizinda noma noma yini ongenalo ilungelo lokuyabelana ngayo. Umnikelo ubuyekezwa ngaphambi kokusetshenziswa; ukuwuthumela akunikezi ubuqambi noma amalungelo okuhlela, futhi ukusekela akuthengi muphumela.
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.
Maps, data and figures on this site are shown for context and general information. They are not advice, forecasts or warnings; the limits of the information are set out in the Disclaimers and Data Notices.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information.
This site uses only strictly necessary cookies to work and to remember your privacy choices. Nothing loads from other companies, and we never sell or share your personal information. We run no advertising. You can review your choices at any time through Privacy choices at the foot of every page.