Time Windows and Lifecycle

Time windows keep alerts aligned with real operations instead of generating noise around the clock.

Time windows

Time windows are optional. Use them when the condition only matters during certain parts of the week or day, or during a specific UTC date range.

Recurring windows

Use recurring windows when the pattern repeats every week:

• Weekdays only
• Overnight operations
• Departure bank monitoring
• Arrival window destination watch

All recurring times are in UTC. Build and review windows in UTC, especially for teams across multiple local time zones.

Absolute ranges

Use an absolute range when the alert only matters for a fixed period, such as:

• A major event week
• A temporary operational campaign
• A known maintenance period
• A one-off disruption window

Absolute ranges also use UTC and accept exact start and end date-times.

Overnight windows

An end time earlier than the start time means the window crosses midnight. Use this for night operations:

• Start 18:00, End 06:00. This means the alert watches overnight, not a short same-day interval.

Lifecycle notifications

Lifecycle notifications send follow-up emails when a NOTAM that already triggered the alert is later cancelled or replaced.

Enable lifecycle when operators act on the original alert and need to know when that condition is removed or superseded. Leave it off when only new activity matters.

Next step

Continue with Managing and Team Alerts.