Alerts
Targeting and Filters
Choose between ICAO and airport-type targeting, then refine with category filters or affected elements using effect, type, and identifier wildcards.
Alert quality depends on good targeting. Start with scope, then refine with filters.
Scope: ICAO vs airport type
| Mode | Use when |
|---|---|
| ICAO | The monitored airports are specific and named |
| Airport type | The condition applies across a broad class of airports by size |
Use ICAO mode in most cases. Use airport type only when the condition genuinely applies to all airports of a given size.
Filter: category vs affected element
After scope, choose one filter strategy:
- Category: when the team thinks in NOTAM domains (aerodrome, airspace, navigation, operations).
- Affected element: when the team thinks in operational consequences (closed runway, unavailable fuel, restricted aerodrome) or in identifiers such as ILS, stand names, or fuel service labels.
The UI treats these as distinct modes. Pick the one that matches how operators describe the problem.
Category filter examples
- Aerodrome and airspace changes
- Navigation and communication issues
- Operations and safety changes
Affected element filter examples
- Closed runway
- Restricted taxiway
- Unavailable fuel service
- Restricted aerodrome
- Any identifier containing
ILSusing*ILS* - Any fuel-related identifier using
*FUEL*
Affected element filters can match:
- Effect only
- Type only
- Identifier only
- Or any combination of effect, type, and identifier
Identifier matching is case-insensitive and supports * as a wildcard.
Keep it explainable
If another operator cannot explain the alert in one sentence, it is probably overbuilt.
Good: "Email the OCC when any monitored hub has a closed runway."
Next step
Continue with Time Windows and Lifecycle.