Templates › Operational response prioritisation
Operational response prioritisation
Which affected areas to prioritise in the first 24–72 hours — exposure, impact, Montandon history and operational data, written back to Montandon as a STAC collection.
Use Case 3 · Action · first 24–72 hours. Normalises component signals (observed severity, vulnerability &
coping capacity, historical burden, operational gap) to 0–1, combines them into a transparent composite index,
attaches a confidence score and a plain-language rationale per area, and publishes the ranking as a
response-prioritisation STAC collection tied to the event by monty:corr_id.
Component signals are illustrative here (synthetic severity / vulnerability; Montandon history is queried when a token is available). The composite, confidence and write-back contract are real.
Parameters schema · 7 fields
| Parameter | Type | Default | Description |
|---|---|---|---|
Areas to flagtop_n |
integer | 10 | |
Weight · operational gap & accessibilityw_gap |
number | 0.1 | |
Weight · historical burdenw_history |
number | 0.2 | |
Aggregationweighting |
string · 2 options | geometric | |
Weight · observed severityw_severity |
number | 0.4 | |
Weight · vulnerability & coping capacityw_vulnerability |
number | 0.3 | |
Stand-in extent radius (km)extent_radius_km |
number | 60 |
Automatic triggers
- New event → response prioritisation — watches reference-events disabled
Recent runs 1 total
| Run | Target | Parameters | Status | Created | |
|---|---|---|---|---|---|
84481c51Operational response prioritisation |
Karnali Nepal · Admin 2 |
Areas to flag: 10 · Weight · operational gap & accessibility: 0.1 · Weight · hi… | Published | an hour ago Manual (UI) |
Open |