Glossary

DEFINITION OF IBF SYSTEM

a system that displays and disseminates early warning notifications for an incoming disaster and visualizes relevant information to support decision making, following the country early action protocol.

SYSTEM COMPONENTS & DEFINITIONS

The components of the IBF System are

• IBF dashboard, i.e. the frontend
• IBF API, i.e. the backend
• IBF database
• IBF pipelines, i.e. implementations of trigger models

Additionally, we refer to the IBF portal as the combination of IBF dashboard and IBF API, i.e. frontend and backend.

IBF pipelines

the IBF pipelines roughly follow three steps:

1. ingest hazard and vulnerability data, from external data providers
2. forecast the risk and potential impact of hazards for given lead time(s)
   • compute severity, likelihood, and risk
   • compute exposure, i.e. any data supporting severity
3. send this information to the IBF portal Note: the pipelines upload all information regardless of risk, each time they run.

severity - A continuous number ∈ [0, 1] representing the potential impact of a certain hazard.

likelihood - A continuous number ∈ [0, 1] representing the probability of a certain hazard to occur.

risk - A linear combination of severity and likelihood.

risk level - A discrete classification of risk, e.g. high, medium and low risk.

threshold - A criterion according to which risk classes are attributed.

alert - The action of notifying the user about risk and/or risk class.

TODOS

• list and rationalize exposure layers
• move from fixed lead time to continuous time
• define risk class (country-specific, e.g. high-medium-low) for IBF System
• discuss the notion of "event" --> Blaise, Aki, Gulfaraz (Jacopo to do)
• visualize this in a flowchart (Jacopo to do)