Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Enterprise SCADA

Adetect table details

  • Last UpdatedApr 24, 2025
  • 2 minute read

Certain devices (represented by a status or multistate record) are used to detect a pig or other type of anomaly that may exist on the pipeline. The Batch Tracking application uses records in the adetect table to link these devices to the pipeline locations. The adetect table contains the following internal fields:

Internal Field Name

Data Type

Description

adetectType

adetectTypeEnum

The nature of the anomaly detector type.

anmtype

anmtypeslot

The nature of the anomaly type.

dataset

doas_dset_slot

This field indicates the dataset to which the record is assigned. Datasets are used to associate the record with the privileges assigned for each system mode. Once a record is assigned to a dataset value, the dataset can only be changed to a value for which the system has a privilege record.

deadband_minus

double

The volume zone downstream of the detector location.

deadband_plus

double

The volume zone upstream of the detector location.

description

description

A description of what this action sequence does, up to 47 characters in length.

downstreamNormalDetectionVolume

double

The downstream normal detection window.

downstreamLateDetectionVolume

double

The downstream late detection volume.

flag.alminh

oas_boolean_t

Prevent alarms from being generated when a sequence fails to complete successfully?

flag.bmsg

messageslot

The message associated with the record.

flag.evtinh

oas_boolean_t

Prevent events from being generated when a sequence fails to complete successfully?

flag.severity

unsigned char

The severity level of the alarm.

group

groupslot

This field shows the group that this point is associated with for alarming.

inh

oas_boolean_t

Inhibit the record?

inhAnomalyLaunchedAlarm

oas_boolean_t

Inhibit alarms for when an anomaly is launched?

inhAnomalyReceivedAlarm

oas_boolean_t

Inhibit alarms for when an anomaly is received?

inhDetectionEarlyOrLateAlarm

oas_boolean_t

Inhibit alarms for early or late detection.

inhDetectionNormalAlarm

oas_boolean_t

Inhibit alarms for normal detection.

inhDetectionTooEarlyOrLateAlarm

oas_boolean_t

Inhibit alarms for too early or too late detection.

inhMissEtaOnSignalAlarm

oas_boolean_t

Inhibit an alarm when a detection occurs but there is no Estimated Time of Arrival (ETA) record for this anomaly.

inhMissSignalOnEtaTooLateAlarm

oas_boolean_t

Inhibit an alarm when an anomaly leaves the late detection window without a signal.

lasttimeStateTriggered

internaltime

This field indicates the last timestamp for when the trigger point transitions to triggered state. When the trigger point transitions out of triggered state, the value is set to zero.

name

pntname

The name of the adetect record.

node

nodeslot

The related node.

pipeline

pipelineslot

The associated pipeline.

receiverAdetectSlot

adetectslot

The Receiver adetect associated with this adetect record—only applicable if this adetect is of type Launcher.

t_deadband

long

The early time limit.

triggerPointPath

path

The path to the status, multistate, or ALPConfig record to be used as the trigger for the anomaly detection.

triggerState

msgstring

The message set state of the status, multistate, or ALPConfig result required to signal the anomaly detection.

triggerStateNumber

int

The ptnum of the message set state of the status or multistate, or the result of the ALPConfig.

upstreamEarlyDetectionVolume

double

Upstream Early Detection Volume.

upstreamNormalDetectionVolume

double

Upstream Normal Detection Volume.

Related Links