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

AVEVA Pipeline Operations for Liquids

Access the Interface Detect Control dialog

  • Last UpdatedApr 24, 2025
  • 3 minute read

Interface detection is controlled through the Interface Detect Control dialog.

To access the Interface Control Detect dialog

  • On the Interface Detect Summary window, select the row header of the desired interface detector (detect) record.

    Embedded Image (65% Scaling) (LIVE)

    The Interface Detect Control dialog appears.

    Embedded Image (65% Scaling) (LIVE)

The following table details the items on the Interface Detect Control dialog.

Group Box

Item

Description

Allow Controller Edit

Detect Table Field

Node

Name of node where detector is located.

no

node

Value Type

The value type indicates the type of measurement.

  • Density/Gravity

  • Sonic Velocity

no

anatype

Alarm

The detect record alarm state can be one of the following options:

  • NormalThreshold โ€” Batch property values are too close to a calculated a good detection threshold.

  • Volume โ€” Interface detected outside of the volume deadband for the detector location.

  • Volume + Threshold โ€” Interface detected outside of the volume deadband for the detector location, and the threshold for detection is not good.

no

alm_state

Status

This defines the ability of detect record processing to calculate a threshold. There will be a Check if Batch Tracking is able to calculate a threshold, and the status will be set to Idle if it is not.

no

state

Current Interface Detection

Current Batch

This defines the ID number of the batch currently flowing past.

no

curr_batch

Analog Deadband

This defines the amount of change in the property value reading that must occur to for the batch cut to be declared.

yes

sd_deadband

Cut Type

This defines the type of cut to apply to the end of the batch. That is, where to locate the interface in the transmix zone between the current and next batch. The available options are:

no

cut_type

Gross Standard Volume (GSV) Deadband

The deadband in which the batch interface as predicted by Batch Tracking must be within when detected, either upstream or downstream of the detector location, for the prediction to be considered correct.

yes

vol_deadband

Next Batch

ID of next batch upstream of the current.

no

next_batch

Next Density/Gravity

The property value to use for the next batch, if Density Selection Method configured in the detect Row Edit dialog in Advanced Database Editor (ADE) is Entered.

Note: This can be used for either density or sonic velocity types.

yes

mandens

Previous Missed Detection

Current Batch

If an interface passed the detector without detection, this is the ID of the batch forming the downstream side of the interface.

no

miss_c_batch

Next Batch

If an interface passed the detector without detection, this is the ID of the batch forming the upstream side of the interface.

no

miss_n_batch

Density/Gravity Correction Inhibited

If selected, and if Value Type is Density/Gravity, the value read from the analog will be corrected for temperature.

yes

corrected

Monitoring Inhibited

If selected, detect record is inhibited from processing.

yes

inh

Auto Ticket Cut

If selected, and if a batch transfer (batchXfer) is assigned to the detect record, a command to start a new ticket will be issued to the batchXfer when an interface is detected. If the ticket start command fails, a ticket split command will be issued.

yes

ticket