Targeting and Filters

Alert quality depends on good targeting. Start with scope, then refine with filters.

Scope: ICAO vs airport type#

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.

We strongly recommend using Affected element filters instead of category filters whenever possible. Affected elements are closer to the operational consequence you care about, so they usually produce alerts that are easier to explain and less noisy than broad category matching.

For more background on the affected-element model, see Affected Elements V2.

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 ILS using *ILS*
• Any fuel-related identifier using *FUEL*

Affected element filters can match:

• Effect only
• Type only
• Identifier only
• Applies-to scope for operational profiles such as aircraft type, traffic type, operational use, and operation phase
• Or any combination of effect, type, subtype, identifier, and applies-to scope

Identifier matching is case-insensitive and supports * as a wildcard.

Applies-to presets#

Affected element filters also support scope presets. Presets are currently marked Preview in the alert editor because the available profiles and applies-to dimensions may still change as the affected-element model evolves.

Use a preset when you want an affected element filter to reflect an operational profile, such as airline IFR, alternate planning, business jet IFR, GA VFR, or helicopter HEMS.

To set a preset:

1. Create or edit an alert.
2. Set Additional filter to Affected element(s).
3. Choose the main affected element fields first, especially Effect and Element type.
4. In Scope preset, choose a profile.
5. Click Apply preset.
6. Review the generated Applies to scope, then save the alert.

Presets add structured applies-to scope such as aircraft type, traffic type, operational use, and operation phase. A NOTAM matches only when it applies to that requested scope. If the NOTAM interpretation has an exception that overlaps the scope, such as an aerodrome closure except scheduled flights, that exception prevents the match for scheduled-traffic alerts.

For that reason, do not use presets as a replacement for the main affected element fields. Use effect and type as the stable baseline, then add a preset to improve operational relevance.

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.