← Catalogue
World Models · legacy example

Natural Phenomenon & Hazard

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. 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. Response operations and casualty management belong to X3, and the atmospheric or hydrological measurements themselves stay in P4 and P3.

AI YAMLAGENTS.mdSource
IDworld.p9-natural-phenomenon-and-hazard
Version history0.2.0-legacy
CategoryReference example
IndustryCross-industry
Domainplanet-nature
Tagsnatural, phenomenon, hazard
Data structure

Bundles and layers

Bundle

hazardCharacterization

What can happen here and how it is measured

Layers

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

Bundle

occurrence

What actually happened and what it cost

Layers

occurrenceRecord`: dated events with location, extent and measured intensity · `impactAndLoss`: attributed damage, disruption and affected counts

Bundle

exposure

Who and what stands in the way

Layers

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

Bundle

alerting

What was communicated, to whom and when

Layers

alertMessage`: graded alerts with area, onset, certainty, expiry and status · `disseminationChannel`: the routes an alert travelled and their delivery confirmations

Findings

Catalogue-native findings must describe the information grouped by each layer. This legacy version does not declare them separately.

Questions & artifacts

Questions, artifact requirements and serial naming rules are required by Vercy vNext; they remain unassigned in this reference version.

Service layers

How this specification operates

Dimension & namespace

  • REFERENCE `world.atmosphereWeatherAndClimate` (P4): meteorological warnings and observed intensities feed occurrence and alerting here
  • REFERENCE `world.waterBodyAndHydrology` (P3): flood and drought occurrences are characterized against flow regimes and thresholds
  • REFERENCE `world.terrainAndLandform` (P1) and `world.soilAndAgriculturalLand` (P10): slope, relief and soil state underpin susceptibility surfaces
  • REFERENCE `world.subsurfaceAndMineralResource` (P5): seismic and volcanic source zones rest on the structures modelled there
  • REFERENCE `world.ecosystemAndBiome` (P8): disturbance records there are the ecological face of occurrences here
  • REFERENCE `world.buildingAndStructure` (U1), `world.physicalInfrastructureNetwork` (U3) and `world.populationGroupAndCommunity` (H3): elements at risk are referenced, never copied in full
  • REFERENCE `world.incidentAndEmergency` (X3): response, deployment and casualty management continue there from the occurrence recorded here
  • REFERENCE `world.insuranceAndRiskPooling` (C8): pooled cover and claims consume scenarios and loss records without being part of this model
  • REFERENCE `world.disclosureScopeAndProjectionPolicy` (S3): the aggregation rules protecting exposed parties are defined there
  • imports: oasis-cap (EXTEND): the alert message structure, severity, urgency and certainty this model specializes
  • imports: em-dat (ALIGN): event and loss recording categories for comparability of occurrence statistics
  • imports: undrr-isc-hazard-information-profiles (REFERENCE): the hazard type catalogue referenced rather than re-invented

Canon, patches & standards

  • REFERENCE `world.atmosphereWeatherAndClimate` (P4): meteorological warnings and observed intensities feed occurrence and alerting here
  • REFERENCE `world.waterBodyAndHydrology` (P3): flood and drought occurrences are characterized against flow regimes and thresholds
  • REFERENCE `world.terrainAndLandform` (P1) and `world.soilAndAgriculturalLand` (P10): slope, relief and soil state underpin susceptibility surfaces
  • REFERENCE `world.subsurfaceAndMineralResource` (P5): seismic and volcanic source zones rest on the structures modelled there
  • REFERENCE `world.ecosystemAndBiome` (P8): disturbance records there are the ecological face of occurrences here
  • REFERENCE `world.buildingAndStructure` (U1), `world.physicalInfrastructureNetwork` (U3) and `world.populationGroupAndCommunity` (H3): elements at risk are referenced, never copied in full
  • REFERENCE `world.incidentAndEmergency` (X3): response, deployment and casualty management continue there from the occurrence recorded here
  • REFERENCE `world.insuranceAndRiskPooling` (C8): pooled cover and claims consume scenarios and loss records without being part of this model
  • REFERENCE `world.disclosureScopeAndProjectionPolicy` (S3): the aggregation rules protecting exposed parties are defined there
  • imports: oasis-cap (EXTEND): the alert message structure, severity, urgency and certainty this model specializes
  • imports: em-dat (ALIGN): event and loss recording categories for comparability of occurrence statistics
  • imports: undrr-isc-hazard-information-profiles (REFERENCE): the hazard type catalogue referenced rather than re-invented

Artifact formats & serial data

Format-independent core. Concrete artifact formats and naming prefixes are not declared in this legacy version.

Policies & accepted processes

  • `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

Read / add / edit / delete

CRUD procedures and interface bindings are not declared in this legacy version.

Ownership, roles & access

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

Existing assembly

Objects, relationships, events and projections

Objects

  • `hazardType`: a kind of hazard; key attributes: identifier, definition, onset speed, typical duration, source classification
  • `hazardSourceZone`: an area or feature capable of generating a hazard; key attributes: geometry, hazard type reference, recurrence characterization, susceptibility class
  • `hazardOccurrence`: a dated event; key attributes: hazard type reference, start and end time, footprint geometry, peak intensity, confidence of attribution
  • `intensityObservation`: a measurement of severity during an occurrence; key attributes: measure reference, value, location, timestamp, source of measurement
  • `exposureZone`: an area exposed at a stated level; key attributes: geometry, hazard type reference, return level, delineation method, version
  • `elementAtRisk`: a thing exposed within a zone; key attributes: element reference, element class, vulnerability class, replacement or capacity descriptor
  • `riskScenario`: a modelled hazard and exposure combination; key attributes: hazard level, exposure set, expected consequence, model reference, assumptions
  • `impactRecord`: attributed consequence of an occurrence; key attributes: impact category, quantity, unit, area, attribution confidence, reporting source
  • `alert`: a graded public notice; key attributes: hazard type, severity, urgency, certainty, area, onset, expiry, status, message reference

Relationships

  • `hazardOccurrence` -> ofType -> `hazardType` (n:1): every event is an instance of a catalogued hazard kind
  • `hazardOccurrence` -> originatesIn -> `hazardSourceZone` (n:1): events are attributed to a source where one is identifiable
  • `intensityObservation` -> measures -> `hazardOccurrence` (n:1): severity values attach to the event, with their own measurement source
  • `exposureZone` -> delineatedFor -> `hazardType` (n:1): zones are always zone for a specific hazard and return level
  • `elementAtRisk` -> locatedIn -> `exposureZone` (n:m): an element can fall in several zones for different hazards
  • `impactRecord` -> attributedTo -> `hazardOccurrence` (n:1): losses are booked against the event that caused them
  • `alert` -> warnsOf -> `hazardType` (n:1): alerts name the hazard and the area they cover
  • `riskScenario` -> combines -> `elementAtRisk` (n:m): scenarios join a hazard level with a defined exposure set

Events

  • `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

Projections

  • `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