Basic anomaly detection deadbands

Basic anomaly detection is enabled when the Anomaly Detect Type is configured as Unspecified. This configuration uses a volume deadband window (Upstream Early and Downstream Late) and a time deadband window.

Using this configuration, the following scenarios are possible:

Scenario 1: The detection occurs when the simulated location of the anomaly is within the deadband window. Batch Tracking will not perform any adjustments to the simulated location. Also, there will be no events or alarms at this point—an alarm and an event will only be raised when the simulated anomaly passes through the Anomaly Detect. The following diagram depicts this scenario where detection occurs at adetect N2_AD while anomaly A1 is within the deadband window.

Scenario 2: The detection occurs when the simulated location of the anomaly is outside the deadband window. In this case, the anomaly is cloned to the adetect location and adjusted by an offset to account for the time elapsed since the detection has occurred. Both the original and cloned anomaly maintain their simulated movement depending on the flow and slip factor. The Controller can then delete or adjust each of the simulated anomalies to reflect the actual location of the anomaly in the pipeline. The following diagram depicts this scenario where detection occurred at adetect N2_AD while anomaly A1 was Upstream Early based on the configured deadband window (250, -100). The detection caused the creation of a clone A1_Cloned. This behavior also applies if the A1 anomaly is located Downstream Late.

Scenario 3: The detection occurs but there is no simulation equivalence of the anomaly in the pipeline. In this case, an anomaly is automatically created at the adetect location and adjusted by an offset to account for the time elapsed since the detection has occurred, and the anomaly will continue to move with the flow in the pipeline. The Controller can then choose to keep the simulated anomaly or delete it in case the detection was trigged by a false signal.

Scenario 4: A simulated anomaly leaves the downstream end of the deadband window without a detection signal being received. In this case, the anomaly will continue to move down the pipeline. The Controller can then choose to keep the anomaly in case the detection signal was missed, or delete it in case the simulated anomaly was erroneously created or is no longer in the pipeline.

Alarm states

Alarms and events associated with the basic anomaly detection configuration will be raised, unless inhibited by the administrator. The following table details the adetect alarm states for when an Anomaly Detect Type is configured as Unspecified: