Understand Interface Detect record Batch Tracking Compiler (BTC) attributes
- Last UpdatedApr 24, 2025
- 2 minute read
The table below shows the detect record’s Batch Tracking Compiler (BTC) attributes.
|
Attribute Name |
Description |
Required |
|---|---|---|
|
DETECT |
Record name. |
Yes. |
|
GROUP |
Group. |
No. If not specified, group will be inherited from the pipeline record. |
|
DESCRIPTION |
Description. |
No. |
|
SEVERITY |
Severity of alarms issued against the detect record.
|
No. Defaults to lowest severity possible. |
|
TICKET |
TRUE or FALSE. If true, a Ticket Start or Ticket Split command is issued to the associated Batch Transfer (batchxfer) when an interface is detected. |
No. |
|
INH |
TRUE or FALSE. If true, processing of record is inhibited. |
No. |
|
CORRECTED |
TRUE or FALSE. If true, density readings are corrected for temperature. |
No. |
|
ANALOG |
Name of analog record polling the detection device. |
Yes. |
|
ANATYPE |
Type of detection device, DENSITY or VELOCITY. |
No. Default is Velocity. |
|
SDDEADBAND |
Minimum change in device reading for interface detection to be considered. |
No. |
|
VOLDEADBAND |
Volume zone upstream and downstream of the detector location. If the interface to a detected batch is tracked as being outside of this zone detection is early or late. |
No. Default is zero (0). A zero value means that a detected interface will always be flagged as early or late. |
|
EVTINH |
TRUE or FALSE. If true, alarm events are inhibited. |
No. Default is false. |
|
ALMINH |
TRUE or FALSE. If true, alarms are inhibited. |
No. Default is false. |
|
CLREVTINH |
TRUE or FALSE. If true, Return-to-Normal (RTN) events are inhibited. |
No. Default is false. |
|
CLRALMINH |
TRUE or FALSE. If true, Return-to-Normal alarms are inhibited. |
No. Default is false. |
|
BATCHXFER |
Name of the batchxfer associated with the device. If a batchxfer is present, the batchxfer schedule will be checked for detected batches. |
No. |
|
DENSEL |
Source of density for next batch to detect. If the density is set to SCHEDULE, density comes from the batch record itself. If set to ENTERED, density is a value manually entered in the detect record. |
No. Default is Schedule. |