# Run & Review Signal Alerts
Learn how to manually run the Signal Alert Rule Engine and review _Statistical Data_ records.
## About Signal Alerts
A signal alert indicates that a _Product-Event Combination_ (PEC) of a _Statistical Data_ record qualifies as a potential signal based on predefined Alert rules. To determine whether a PEC qualifies as a potential signal, Signal uses a Signal Alert Rule Engine to detect when the signal calculations of a _Statistical Data_ record meet a certain threshold or criteria. Signal alert criteria are compliant with industry standards; for example, Vault flags the _Statistical Data_ record when the PEC is unlisted, and can be customized depending on your business needs. To set specific custom thresholds for signal alerts, contact your Admin.
You can manually run _Signal Alert Rules_ from a _Signal Reporting Period_. When the Signal Alert Rule Engine runs, Vault evaluates _Signal Alert Rule Sets_, which include _Signal Alert Rules_ configured by your Admin.
Your Admin can configure your Vault to execute a job that runs _Signal Calculations_ and the Signal Alert Rule Engine on a scheduled basis. For more information about scheduling the signal detection process, see Scheduled Signal Calculations & Alerts. If this job is in progress, Vault will prevent you from manually triggering the Signal Alert Rule Engine.
## Prerequisites
Before Vault can use the Signal Alert Rule Engine to flag _Statistical Data_ records, your Admin must complete the following:
* Enable the Signal Alert Rule Engine
* Configure _Signal Product Profiles_
* Configure _Signal Alert Rules_ and _Signal Alert Rule Sets_
## Manually Run the Signal Alert Rule Engine
On a _Signal Reporting Period_, you can manually trigger an action to run the Signal Alert Rule Engine:
1. Navigate to the **Reporting Periods** tab.
2. Hover over the applicable _Signal Reporting Period_ and select the **All Actions** menu.
3. Select **Run Signal Alert Rules**.
**Results**
The Signal Alert Rule Engine runs and evaluates _Signal Alert Rules_ for each _Statistical Data_ record referenced under this _Signal Reporting Period_. For more information about how the Signal Alert Rule Engine runs and how Vault updates the _Statistical Data_ records after the run, see the [How the Signal Alert Rule Engine Runs][1] section.
## How the Signal Alert Rule Engine Runs
A _Signal Product Profile_ defines a _Product Family_ or _Aggregate Reporting Group_ and the parameters used in signal detection. When you manually run the Signal Alert Rule Engine for a _Signal Reporting Period_, Vault looks at the reporting period's referenced _Signal Product Profile_, regardless of its data source, and evaluates each active _Signal Alert Rule Set_ linked to the _Signal Product Profile_. Each active _Signal Alert Rule_ is evaluated against each _Statistical Data_ record in the _Initial_ lifecycle state type.
A _Statistical Data_ record stores the signal calculation results, which the Signal Alert Rule Engine uses to determine whether the record meets the _Signal Alert Rule_ criteria.
### Scenarios
The sections below describe the different scenarios and Vault behavior that occur when you run the Signal Alert Rule Engine.
#### A Statistical Data Record Meets the Criteria for a Signal Alert Rule
If a _Statistical Data_ record meets the criteria of at least a single _Signal Alert Rule_, Vault sets:
* The _Alert_ field on the _Statistical Data_ record to _Yes_.
* The _Alert Category_ field on the _Statistical Data_ record to indicate the _Signal Alert Rule_ that was met. The standard options are:
* _Unlisted_: When the PEC is not listed as indicated on the _Case Assessment_.
* _EB05 >= 2_: When the _EB05_ signal calculation score is larger than or equal to two (2). \
If the _Statistical Data_ record meets the criteria for multiple _Signal Alert Rules_, Vault sets multiple values in the _Alert Category_ field. If you would like to add custom _Signal Alert Rules_ based on your business needs, contact your Admin.
* The lifecycle state of the _Statistical Data_ record to the _Ready_ state type.
After the Signal Alert Rule Engine evaluates all _Statistical Data_ records without error, Vault sends you a notification and an email.
#### A Statistical Data Record Does Not Meet Any Signal Alert Rule Criteria
If the _Statistical Data_ record does not meet the criteria for any _Signal Alert Rules_, Vault sets:
* The _Alert_ field on the _Statistical Data_ record to _No_.
* The lifecycle state of the _Statistical Data_ record to the _Complete_ state type.
#### Vault Cannot Evaluate a Signal Alert Rule
If Vault cannot evaluate a _Signal Alert Rule_ due to an error:
* Vault sends you a notification and an email with the following information:
* A link to the associated _Signal Reporting Period_ record.
* A CSV file with a list and description of the errors encountered by the _Signal Alert Rules_.
* Vault sets the lifecycle state of the _Signal Reporting Period_ record to the _Error_ state type.
* Vault does not update the _Statistical Data_ record and the record remains in the _Initial_ lifecycle state type.
For more information about reviewing records after the Signal Alert Rule Engine runs, see the [Review Statistical Data Records][2] section.
## Review Statistical Data Records
After the Signal Alert Rule Engine flags _Statistical Data_ records as signal alerts, you can manually review the records from the applicable _Signal Reporting Period_:
1. Navigate to the **Reporting Period** tab and select the applicable record. You can also navigate to the applicable _Signal Reporting Period_ from the email or Vault notification.
2. Expand the **Statistical Data** section and select **Show in Tab** to display records in tab view.
3. Optional: Set the _Alert_ filter to _Yes_ to narrow the view to only signal alerts.
4. Select the applicable **Statistical Data** record.
5. Review the _Alert Category_ and the record.
6. Do one (1) of the following:
* If the _Statistical Data_ record requires further investigation, open a _Safety Investigation_ and set the lifecycle state to _Complete_.
* If the _Statistical Data_ record requires further monitoring, set the **Current Disposition** field to _Monitor_ and set the lifecycle state to _Complete_.
[1]: #how-the-signal-alert-rule-engine-runs
[2]: #review-statistical-data-records