← Back to catalogue
Previous version

Natural Phenomenon & Hazard

vr.wm-ear-005 · world-p9-natural-phenomenon-and-hazard

Earthquakes, floods, droughts and hazard exposure

World Models Physical world and living systems PHY.EAR.HAZ

Bundle → Layer → Finding → Questions Incomplete

4 bundles · 10 layers · 0 findings · 0 questions

hazardCharacterization What can happen here and how it is measured

hazardType

the catalogue of hazard kinds with definitions and onset behaviour

sourceAndSusceptibility

source zones, fault traces, susceptibility surfaces and triggering conditions

intensityMeasure

the scales and units in which severity is expressed

occurrence What actually happened and what it cost

occurrenceRecord

dated events with location, extent and measured intensity

impactAndLoss

attributed damage, disruption and affected counts

exposure Who and what stands in the way

exposureZone

mapped zones for a hazard type and return level

elementAtRisk

the assets, networks and population units within a zone

riskScenario

modelled combinations of hazard level and exposure with expected consequence

alerting What was communicated, to whom and when

alertMessage

graded alerts with area, onset, certainty, expiry and status

disseminationChannel

the routes an alert travelled and their delivery confirmations

Note: Legacy card: layers named, findings and questions never written.

Classifiers Filled

Family
World Models
Category
Physical world and living systems
Entry kind
standalone-mm
Navigation path
NAV.PHY.EAR.HAZ
Domain
PHY.EAR.HAZ
Industry
Cross-industry
Tags
naturalhazardphy.ear.haz
Also called
P9

What it is Derived, awaiting review

This meta-model describes hazards and what they do: the kinds of hazard and where they can originate, the occurrences that actually happened with their measured intensity and attributed impact, the zones and elements exposed to them, and the alerts issued to people at risk.

Note: First sentence of the legacy card introduction.

Why it exists Filled

Earthquakes, floods, droughts and hazard exposure

Distinguishing features Derived, awaiting review

  • It is its own model because a hazard is a standing property of a place while an occurrence is a dated event and an alert is a communication act, and confusing the three is the classic failure of risk data.

What robots and AI may and may not do Missing, in the backlog

Not described yet. This gap is in the card backlog.

Moral aspects Missing, in the backlog

Not described yet. This gap is in the card backlog.

Owners Filled

Steward

A hazard monitoring steward maintains the characterization, occurrence and exposure register and an emergency management operator issues and withdraws alerts, each accountable for what it publishes.

Links to other meta-models Filled

references

  • world.atmosphereWeatherAndClimate - meteorological warnings and observed intensities feed occurrence and alerting here
  • world.waterBodyAndHydrology - flood and drought occurrences are characterized against flow regimes and thresholds
  • world.terrainAndLandform - slope, relief and soil state underpin susceptibility surfaces
  • world.soilAndAgriculturalLand - slope, relief and soil state underpin susceptibility surfaces
  • world.subsurfaceAndMineralResource - seismic and volcanic source zones rest on the structures modelled there
  • world.ecosystemAndBiome - disturbance records there are the ecological face of occurrences here
  • world.buildingAndStructure - elements at risk are referenced, never copied in full
  • world.physicalInfrastructureNetwork - elements at risk are referenced, never copied in full
  • world.populationGroupAndCommunity - elements at risk are referenced, never copied in full
  • world.incidentAndEmergency - response, deployment and casualty management continue there from the occurrence recorded here
  • world.insuranceAndRiskPooling - pooled cover and claims consume scenarios and loss records without being part of this model
  • world.disclosureScopeAndProjectionPolicy - the aggregation rules protecting exposed parties are defined there

imports

  • oasis-cap - EXTEND: the alert message structure, severity, urgency and certainty this model specializes
  • em-dat - ALIGN: event and loss recording categories for comparability of occurrence statistics
  • undrr-isc-hazard-information-profiles - REFERENCE: the hazard type catalogue referenced rather than re-invented

requires

  • vr.wm-act-019
  • vr.wm-blt-005
  • vr.wm-ear-001
  • vr.wm-ear-004
  • vr.wm-eco-003
  • vr.wm-liv-006
  • vr.wm-plc-001
  • vr.wm-plc-003

What else AI and robots need to interact with it Incomplete

Identity and identifiers required Derived, awaiting review

  • hazardType: a kind of hazard; key attributes: identifier, definition, onset speed, typical duration, source classification

Direct properties not applicable Not applicable

Not applicable

Institutional or informational subject: no invented physical properties.

Recognition optional Missing, in the backlog

Not described yet. This gap is in the card backlog.

Capabilities and actions required Derived, awaiting review

  • hazardOccurrenceDetected: monitoring or report established that an event was underway
  • alertIssued: a graded notice was published for an area with onset, certainty and expiry
  • alertUpdated: severity, area or timing of an active notice changed
  • alertCancelled: an active notice was withdrawn or allowed to expire
  • hazardOccurrenceClosed: the event was declared over and its footprint finalized
  • impactAssessmentFiled: attributed damage and affected counts were reported for an occurrence
  • exposureZoneRevised: a zone was redrawn after new occurrence data or a new model version
  • returnPeriodRecalculated: frequency statistics for a hazard and area were updated with a longer record

Legacy events listed as state transitions.

Hazards and failure modes optional Missing, in the backlog

Not described yet. This gap is in the card backlog.

Standards and interfaces required Derived, awaiting review

  • alertFeedContract: terms for redistribution of alerts to broadcasters, applications and neighbouring registers, including no-alteration and timeliness conditions
  • exposureContributionContract: terms under which asset registers contribute elements at risk, including grain, refresh and confidentiality limits
  • lossReportingContract: terms for reporting attributed impact into the occurrence record, including definitions and revision windows
  • sensorAndDetectionFeedContract: terms for real-time detection feeds from monitoring networks operated by others
  • publicAlertFeed: current alerts with area, severity and plain-language guidance; omits internal deliberation and contributing sensor diagnostics
  • planningHazardZoneMap: zones and return levels for planning use; omits identified elements at risk and their holders
  • lossStatisticsSeries: impact totals per occurrence and period; omits per-holder and per-address detail

Context of use required Filled

  • Exposure contributions stay owned by the registers that supplied them under S1, disclosure of identified elements at risk happens only through S2 access contracts shaped by S3, and every read is logged in S4.

Sources Missing, in the backlog

Not described yet. This gap is in the card backlog.

Open questions

  • Superseded by a researched world model? Map this legacy card to its successor or retire it.

Machine files

Provenance

legacy MMAS card (world-models v0.2) · legacy

Built from: models/world-p9-natural-phenomenon-and-hazard/spec.yaml, models/docs/planet-nature/P9-natural-phenomenon-and-hazard.md