---
sourceDocument: Xanadu Platform Analytics
sourceDocumentLink: https://www.servicenow.com/docs/r/xanadu/now-intelligence

 Release :

    - xanadu

ft:locale :

    - en-US

ft:publication_title :

    - Xanadu Platform Analytics

ft:clusterId :

    - par

bundleId :

    - par

workflow :

    - Platform


---

# Signal, no signal, and anti-signal

# Signal, no signal, and anti-signal {#ariaid-title1}

* Release version: Xanadu
* 
* Updated August 1, 2024
* 
* ![](https://www.servicenow.com/docs/portal-asset/ico-clock) 2 minutes to read

When KPI Signals detects abnormal variation in the scores of a KPI, it
generates a signal. When KPI Signals does not detect abnormal variation for a
significant amount of time, it generates an "anti-signal." The anti-signal lets you know that
your workflow is under control.  
Both the presence and absence of signals conveys information:

* The presence of signals lets you know that a workflow has changed, or at least is not statistically stable.
* The long-term absence of signals indicates that a workflow is statistically stable. With this information you can decide to launch a process improvement initiative, for example.

{#signal-no-signal-anti-signal__ul_xtz_vpd_vkb}  
Note:  
By default, dashboards that show indicators with KPI Signals enabled have insight cards for signals that get generated. For more information, see [Proactive analytics insights on dashboards](https://www.servicenow.com/docs/CthCs~Qo6E0kKEfdseL96Q "Proactive analytics automates the extraction of insights from your Performance Analytics indicators. Receive notifications on your Platform Analytics dashboards of potentially interesting changes and events in your processes.").

## Signals {#signal-no-signal-anti-signal__section_d5f_rtk_tnb}

The KPI Signals application considers the following behaviors to 'signal' special cause variation:

Outlier
:   Every score beyond a three standard deviation (3-sigma) upper or lower limit.

Short run
:   Four consecutive scores on the same side of the central line, with three of the
    scores close to the upper or lower limit. "Close to the limit" is defined as outside
    two standard deviations.

Long run
:   Seven consecutive scores on the same side of the central line. That is, seven scores
    in a row all greater than or all less than the average value.
{#signal-no-signal-anti-signal__dl_fvc_vfw_lkb}  
Note:  
The KPI Signals app counts outliers (dismissed or not) when calculating whether a short or long run has occurred.

In the following example, you see a "Long run" signal: seven consecutive scores above or
below the central line.

Note:  
The KPI Signals application can detect signals for an indicator with no more than one first-level [breakdown element](https://www.servicenow.com/docs/KzO1fGsm6GUEygdn1yjLBA#gloss-breakdown-element "The values for a breakdown. For example, the Priority breakdown may have the elements Critical, High, and Low."). The application does not support multiple breakdown elements or a second-level breakdown.

## Anti-signals {#signal-no-signal-anti-signal__section_pxw_stk_tnb}

The application issues an anti-signal when it has not detected a signal for a length of time equal to the following formula:

    Length of time to calculate the baseline for the KPI * Anti-signal factor

The application takes 14 days by default to calculate the baseline for a daily indicator.
The default anti-signal factor is two. Thus, the default length of time to detect an
anti-signal on a daily indicator is 28 days. For more information about setting the time to
calculate a baseline, see [Configure signal detection](https://www.servicenow.com/docs/BBAjQpgNswI1ubceEEc8kA "You can set the start date of the current baseline calculation, the number of scores used to calculate the baseline, and the trend method. You also can deactivate or reactivate KPI Signals monitoring for a KPI."). For more
information about setting the anti-signal factor, see [Configure signal notifications](https://www.servicenow.com/docs/Jk7ozT8BphdyMfWkrcW5EA "As a responsible user, you receive email reminders about signals that have not been resolved. You can configure how frequently you get these reminders and the maximum number of reminders to get for a signal.").

In this example, the default configuration values apply to a daily indicator. The
application has not detected a signal for 28 days, so it shows a 28-day anti-signal.

Although responsible users are notified when an anti-signal is generated, no action is
required.

## No signal {#signal-no-signal-anti-signal__section_aw3_vtk_tnb}

Usually no signal is detected for a shorter amount of time than it takes to detect an
anti-signal. In this case, the application shows a simple "No signal" message. No
notifications are sent and no action is necessary.

In the following example, no signal is detected for five days after the baseline was most
recently reset. The baseline has been reset three times in the period being shown.