> ## 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.
# How to Configure Safety Performance Indicators
> Set up SPI targets and thresholds, configure alert levels, assign review cycles, and monitor safety performance trends.
By following this guide, you will configure Safety Performance Indicators (SPIs) with targets and thresholds, assign review cycles, and set up alerting to monitor safety performance trends.
**Who should read this:** Safety managers and admins who configure
and monitor SPIs. The accountable executive should review SPI
dashboards during management reviews.
**Prerequisites:** Safety manager or admin role. Your organization
should have baseline safety data (reports, incidents, flight hours)
to set meaningful targets.
## SPI Dashboard Overview
Navigate to **SPIs** in the Safety sidebar. The dashboard displays
all configured indicators with their current values, targets,
thresholds, alert status, and trend direction.
## Indicator Categories
PlaneConnection organizes SPIs into five categories covering the
full scope of your safety management activities:
| Category | Examples |
| ----------------- | ------------------------------------------------------------------------- |
| Flight Operations | Unstable approach rate, go-around rate, TCAS RA rate. |
| Maintenance | Unscheduled maintenance rate, MEL deferral rate, repeat discrepancy rate. |
| Ground Operations | Ramp incident rate, ground damage rate, FOD incident rate. |
| SMS Effectiveness | Report submission rate, investigation closure time, CPA on-time rate. |
| Human Factors | Fatigue report rate, CRM event rate, training completion rate. |
## Configure an SPI
### Step 1: Open the SPI configuration
From the SPI dashboard, open the configuration for any indicator, or add a new indicator.
### Step 2: Set the target value
The target represents the desired performance level. Base targets on historical baseline data, industry benchmarks, regulatory guidance, and organizational safety objectives.
### Step 3: Set alert thresholds
Define the values that trigger escalating levels of management attention. For the full alert level definitions, see [SPI Definitions](/en/reference/spi-definitions).
Set Watch thresholds at approximately 80% of the Warning value. This gives you early warning
before performance degrades to a level requiring formal action.
### Step 4: Assign a review cycle
Select how frequently this indicator should be formally reviewed -- daily, weekly, monthly, quarterly, or annual depending on the metric type.
### Step 5: Set the data source
Indicators can pull data automatically from PlaneConnection modules (reports, investigations, CPAs, flight logs) or accept manual data entry for metrics tracked externally.
### Step 6: Save the configuration
Save to apply. The indicator appears on the SPI dashboard with its current value calculated from the configured data source.
## Monitor SPI Trends
The SPI dashboard shows a trend indicator for each metric:
| Trend | Meaning |
| --------- | -------------------------------------------------- |
| Improving | Performance is moving toward the target. |
| Stable | Performance is consistent within the normal range. |
| Degrading | Performance is moving away from the target. |
Click on any indicator to view its detail page with historical
charts, threshold breach history, and related safety data.
## Respond to SPI Alerts
When an SPI breaches a threshold:
1. **Review the alert.** Navigate to the SPI detail page to
understand the scope and duration of the threshold breach.
2. **Investigate the cause.** Examine underlying data -- recent
reports, investigation findings, and operational changes -- to
determine why performance has degraded.
3. **Take corrective action.** Depending on the alert level:
| Alert Level | Recommended Response |
| ----------- | ------------------------------------------------------------------------------------------------------------------- |
| Watch | Increase monitoring frequency. Note in next committee meeting. |
| Warning | Conduct a focused review. Consider opening an investigation or risk assessment. |
| Critical | Escalate to the accountable executive. Initiate immediate corrective action. May require operational modifications. |
4. **Document the response.** Record what was found, what action
was taken, and any changes to the SPI target or thresholds.
Critical SPI alerts that persist for more than 7 days without documented management response
are flagged on the compliance dashboard and may indicate a gap in Safety Assurance processes
per 14 CFR 5.71.
## SPI Review in Committee Meetings
Include SPI performance in Safety Review Board (SRB) and Safety
Action Group (SAG) agendas. The recommended review approach:
* **Monthly SAG meetings** -- review all SPIs with Watch or higher
alerts. Discuss trends and assign follow-up.
* **Quarterly SRB meetings** -- review the full SPI dashboard.
Evaluate whether targets and thresholds remain appropriate.
Approve any changes to SPI configurations.
* **Annual management review** -- assess the overall SPI program.
Add or retire indicators based on operational changes and
safety priorities.
## Related
Complete catalog of indicators, categories, and alert system reference.
How SPI monitoring supports Part 5 Subpart D compliance.
Risk assessments triggered by degrading SPI performance.
Reviewing SPI performance in committee meetings.