> ## Documentation Index
> Fetch the complete documentation index at: https://docs.planeconnection.com/llms.txt
> Use this file to discover all available pages before exploring further.
# Configure Safety Alerts
> Set up alert thresholds, notification rules, and escalation paths for safety performance indicators and anomaly detection.
By following this guide, you will configure alert thresholds for safety performance indicators, set up notification rules to reach the right people, and define escalation paths for unacknowledged alerts.
Alert configuration requires the **Safety Manager** role or higher. Alert thresholds apply
workspace-wide. Changes take effect immediately for future data points.
## Configure SPI Alert Thresholds
Safety Performance Indicators (SPIs) trigger alerts when values cross defined thresholds. Each SPI can have multiple threshold levels.
### Step 1: Open SPI alert configuration
Navigate to **Safety > SPIs > Configure**. The configuration page lists all active SPIs with their current threshold settings.
### Step 2: Select an SPI to configure
Click an SPI row to expand its threshold settings. Each SPI supports three alert levels:
| Level | Color | Purpose |
| ------------ | ------ | --------------------------------------------------------- |
| **Watch** | Yellow | Early warning that a metric is trending toward a concern. |
| **Warning** | Orange | The metric has reached a level requiring attention. |
| **Critical** | Red | The metric has breached the safety action trigger. |
### Step 3: Set threshold values
Enter the numeric value for each alert level. For upward-trending metrics (e.g., incident rate), the Watch threshold is the lowest value. For downward-trending metrics (e.g., training completion rate), the Watch threshold is the highest value.
### Step 4: Configure the evaluation window
Set the time period over which the SPI is evaluated:
* **Rolling 30 days** -- standard for high-frequency indicators.
* **Rolling 90 days** -- smooths seasonal variation.
* **Calendar quarter** -- aligns with management review cycles.
* **Custom** -- any number of days.
### Step 5: Save the configuration
Click **Save**. Thresholds apply to future evaluations immediately. Historical alert states are not retroactively changed.
## Set Up Notification Rules
Alerts are only useful if they reach the right people at the right time. Configure notification channels for each alert level.
### Step 1: Open notification settings
Navigate to **Safety > Settings > Notifications**. The notification matrix shows alert levels on one axis and recipients on the other.
### Step 2: Assign recipients by alert level
For each alert level (Watch, Warning, Critical), specify who should be notified:
| Recipient type | Example |
| --------------- | ----------------------------------------------------- |
| **Role-based** | All safety managers, the Accountable Executive |
| **Named users** | Specific individuals by name |
| **Department** | All members of a department (e.g., Flight Operations) |
### Step 3: Select notification channels
Choose how each recipient group is notified:
* **In-app notification** -- appears in the notification center (always on for all alerts).
* **Email** -- sends a formatted email with alert details and a link to the relevant dashboard.
* **SMS** -- sends a text message for time-sensitive alerts (requires Twilio integration).
* **Push notification** -- sends a browser push notification.
### Step 4: Save notification rules
Click **Save**. New rules apply to future alerts. Existing unacknowledged alerts are not re-notified.
## Define Escalation Paths
Escalation paths ensure that unacknowledged alerts automatically escalate to higher authority after a defined period.
### Step 1: Open escalation configuration
From **Safety > Settings**, select the **Escalation** tab.
### Step 2: Define escalation tiers
Set up escalation tiers for each alert level. A typical configuration:
| Tier | Trigger | Escalates to |
| ------ | ----------------------------------- | -------------------------- |
| Tier 1 | Alert unacknowledged after 4 hours | Safety Manager |
| Tier 2 | Alert unacknowledged after 24 hours | Director of Safety |
| Tier 3 | Alert unacknowledged after 48 hours | Accountable Executive (AE) |
### Step 3: Set escalation timing
For each tier, specify the time delay before escalation. Critical alerts should have shorter escalation windows than Watch alerts.
### Step 4: Save the escalation path
Click **Save**. Escalation timers begin when an alert is generated and reset when the alert is acknowledged.
14 CFR 5.71 requires continuous monitoring of safety performance. Ensure that Critical alerts
always escalate to the Accountable Executive within a timeframe that allows for timely corrective
action. Document your escalation policy in your SMS manual.
**AI suggestions are advisory only.** Per 14 CFR Part 5, all safety assessments, investigation
findings, and risk evaluations require independent human evaluation by qualified personnel. AI
recommendations should be used as one factor among many in decision-making, not as the sole basis
for any safety, operational, or maintenance action. See [Legal
Notices](/en/reference/legal-notices#ai-and-automated-features-disclaimer).
## Related
Define and manage Safety Performance Indicators.
Automated anomaly detection that generates alerts.
All available SPIs, their formulas, and default thresholds.
Supported notification channels and integration requirements.