Summary of Batch Tracking messages and alarms

Batch Alarm Messages

main_batch_track():Closed loop checking failed in pipeline <name>. Deactivated. See OASErrLog.

Routes cannot exist where flow returns to the starting point. The pipeline is deactivated.

Handles instances where pipeline misconfiguration has occurred.

In consultation with your Administrator, correct the configuration of the pipeline to avoid a circular route.

PIPE MODEL ERR: Deactivating pipeline <name>. Contact SCADA Admin. See oasErrLog.

Fragment records represent portions of batches in the pipeline and are dynamically created and removed. If a problem occurs with the process of managing these records, the pipeline is deactivated and the alarm is issued.

Contact your Administrator. Consult the oasErrLog.log in %DNADataRoot%\Shared\Log for more information.

Clearing any PIPE MODEL ERR alarms on pipeline [PipelineName].

This alarm indicates clearing any pipe model ERR alarms on pipeline.

No response required.

Batch <batchId> is off route at pipe <pipe name>.

The batch will not reach its intended destination based on the current operation.

This could be caused by a pipeline edit or incorrect timing of a ticket start/split at the receipt meter.

For more information, see Access the Batch Edit dialog.

Unexpected Flow Difference - IN =<volume in> OUT = <volume out>dband=<flow difference deadband>: @<remote name>: node <node name>.

The batch is reporting an unexpected flow difference. The volume-in and the volume-out values exceed the deadband threshold and, as such, an unexpected flow difference is being reported at the associated remote location and node.

This can provide an indication that something is wrong. Investigate to discover the source of the problem.

Unexpected Flow Difference -IN =[volume in] OUT = [volume out]dband=[flow difference deadband].

The batch is reporting an unexpected flow difference. The volume-in and the volume-out values exceed the deadband threshold.

This can provide an indication that something is wrong. Investigate to discover the source of the problem.

Invalid configured merge pipe <pipe name> at node <node>.

If the configured merge pipe cannot be used, the alarm is triggered.

Investigate the configuration of the merge pipe so it can be used successfully.

Batch <batch ID> merging into Batch <batch ID> at node <node name>, Product Type differs.

The product types at the merge node are not the same. This is an indication of merging incompatible product.

Anomalies are created marking the start and end of the blending problem as well as the node where it is being blended. When this occurs, the alarm is triggered.

Ensure that you are not mixing incompatible product or change the product type (if it is incorrect).

Pressure is above maximum allowable pressure in pipeline <name>.

The pressure is above the maximum allowable pressure in the pipeline.

Investigate the reason behind the increase in pressure in the pipeline.

Pressure returned to normal in pipeline <name>.

The pressure has returned to normal in the pipeline.

No response required.

Pressure is [value] from ground elevation in pipeline [name].

Indicates the value where the pressure is away from ground elevation in the pipeline.

No response required.

Pressure is [value] from maximum allowable pressure in pipeline [name].

Indicates the value where the pressure is away from maximum allowable pressure in the pipeline.

No response required.

Pressure is below ground elevation in pipeline [name].

Pressure is below ground elevation in the pipeline.

Investigate the reason behind the pressure below ground elevation in the pipeline.

Pipe Segment <pipe name>: Unable to reconcile telemetered and calculated downstream pressures.

The pipe segment was unable to reconcile the difference between the telemetered and the calculated downstream pressure.

Investigate why there was a difference in the telemetered and calculated downstream pressure.

Batch Tracking for <pipeline name> inactive longer than <inactive limit> minutes.

Batch Tracking has not been performing any Batch Tracking calculations for a period longer than the inactive time limit.

In conjunction with your Administrator, investigate why the Batch Tracking calculation has not been performed recently.

Anomaly Detect triggered: <anomaly detect name>: Detected <number of anomalies>.

If enabled, the anomaly detection feature has indicated that it has detected a number of anomalies in the pipeline.

Investigate the source of the anomaly. For more information, see View information about a single Anomaly.

Anomaly <name> has arrived at node <name> in pipeline <name>.

Anomaly has arrived at the destination node.

No response required.

Anomaly Detect triggered: <anomaly detect name>: VOL DB-<exceeded deadband> early.

If enabled, the anomaly detection feature has detected the anomaly early based on the configured volume warning deadband.

Investigate the source of the anomaly. For more information, see View information about a single Anomaly.

Anomaly Detect triggered: <anomaly detect name>: VOL DB-<exceeded deadband> late.

If enabled, the anomaly detection feature has detected the anomaly late based on the configured volume warning deadband.

Investigate the source of the anomaly. For more information, see View information about a single Anomaly.

Anomaly Detect triggered: <anomaly detect name>: TIME DB-<time deadband> early.

If enabled, the anomaly detection feature has detected the anomaly early based on the configured time warning deadband.

Investigate the source of the anomaly. For more information, see View information about a single Anomaly.

Anomaly Detect triggered: <anomaly detect name>: MISSED <number of anomalies not found>.

Indicates the number of anomalies that the anomaly detection feature was not able to detect. This means that there was a lack of information in the associated ETA record.

Investigate the source of the anomaly. For more information, see View information about a single Anomaly.

Unable to determine downstream segment for anomaly <anomaly original name>. A clone has been created for each downstream segment.

Indicates that the system was unable to determine which downstream segment to move the anomaly into, so it created a clone for each viable downstream segment.

Based on the actual physical location of the pig, determine which anomaly clone to keep and delete the rest.

DETECT [detection point name]: Split a ticket to [meterName] [batch name at detector]: [current batch]/[next batch at detector].

A batch interface has been found. A ticket split for the BatchXfer associated with the detector is issued.

No response required.

DETECT [detection point name]: Started a ticket at [meterName] [batch name at detector]:[current batch]/[next batch at detector].

A batch interface has been found. A ticket start for the BatchXfer associated with the detect is issued.

No response required.

ADETECT: [anomalyDetectorName] - Alarms reset.

If enabled, the anomaly detection feature has detected that all alarms have been reset for anomalies.

No response required.

DETECT: [anomalyDetectorName] - Retry search for [currentbatchwhichismissed/nextbatch]

This alarm indicates that retry search is enabled for missing batch.

No response required.

DETECT: [DetectorName] - Alarms reset.

If enabled, the interface detection feature has detected that all alarms have been reset for interface.

No response required.

Configuration Failure for batch <batch name> in segment <pipe segment name>, please see log for details.

This persistent alarm will be generated if there is a volume correction configuration error. For example, this alarm will be generated if there is a configuration error with a moleper record, or if a Reference Fluid Thermodynamic and Transport Properties Database (REFPROP) prodtype record does not have a moleper record.

Consult the oasErrLog.log in %DNADataRoot%\Shared\Log, and then contact your Administrator to correct the issue with the moleper record.

Volume Correction Error for Pipeline: [PipelineName] - Please see events and logs for details.

This persistent alarm will be generated if there is a volume correction error.

Consult the oasErrLog.log in %DNADataRoot%\Shared\Log, and then contact your Administrator.

Volume Correction Error Returned to Normal for Pipeline: [PipelineName].

This is a Return-to-Normal (RTN) alarm to indicate that the volume correction-associated alarm condition has returned to normal.

No response required.

Volume Calculation Error Returned to Normal for Segment [SegmentName].

This is a Return-to-Normal alarm to indicate that the volume correction-associated alarm condition has returned to normal.

No response required.

Volume Calculation Failure for Segment [SegmentName] - Please see log for details.

This persistent alarm will be generated if there is a volume correction configuration error.

Consult the oasErrLog.log in

%DNADataRoot%\Shared\Log, and then contact your Administrator.

An unknown failure occurred when attempting to invoke VolumeCorrectionLibrary for batch <batch name> in pipe_segment <pipeline segment name>.

An unknown failure has occurred when attempting to calculate volume correction.

Consult the oasErrLog.log in %DNADataRoot%\Shared\Log, and then contact your Administrator to correct the issue.

Changed davg from [Old Value] to [New Value] in batch id [BatchID Name].

This alarm message occurs when the average density is changed in batch.

No response required.

Product Type: [ProductTypeSlotNumber] not found within [dband][unit] upstream of [tableName].[meterName]

This alarm message occurs if the product type is not found within the volume deadband upstream of the pipeline.

Correct the error that led to the failure.

Product Type: [ProductTypeSlotNumber] not found within [dband][unit] downstream of [tableName].[meterName]

This alarm message occurs if the product type is not found within the volume deadband downstream of the pipeline.

Correct the error that led to the failure.

RealTime Database Replication

Failed to load replicated pipeline <pipeline name>.

Failure details are logged into %DNADataRoot%\RealTime\Logcmxrepsvr.log. For example:

"List used to hold pipeline children too small. Resize.";

"Cannot lock fragment table."

Consult the cmxrepsvr.log in the %DNADataRoot%\RealTime\Log, and then contact your Administrator to correct the issue.

Revert Save

REVERT failed - <error message> - on file <filename>.

In this case, attempting to revert to a snapshot by importing or exporting your Batch Tracking pipeline information has failed.

Revertsave is the utility used to import / export the contents of the Batch Tracking database into / out of a file.

The <error message> will detail the failure. For example:

"Unable to read pipeline name";

"Pipeline still active."

Correct the error that led to the failure.

Pipeline reverted using file [Filepath and Filename].

The alarm message occurs if pipeline is reverted using file.

No response required.

Unable to read pipeline name.

This alarm is generated if the system is unable to read pipeline name.

Correct the error that led to the failure.

Unable to delete pipeline associated child records.

This alarm is generated if the system is unable to delete pipeline associated child records.

Correct the error that led to the failure.

Could not determine group on Pipeline [pipelineName].

This alarm is generated if the system is unable to determine group on pipeline.

Correct the error that led to the failure.

Cannot lock pipeline [pipelineRecordNumber.

This alarm is generated if the system is unable to lock the pipeline.

Correct the error that led to the failure.

Pipeline [pipelineName] still active.

This alarm indicates that pipeline is still active.

Correct the error that led to the failure.

Pipeline [pipelineName] not found in database.

This alarm is generated if the pipeline is not found in database.

Correct the error that led to the failure.

Use BTC -r [pipelineName] to reload.

This alarm indicates that pipeline to be reloaded.

Execute specified command.

Database locking problems. See batErrLog.

This alarm is generated if the database is locked.

Consult the oasErrLog.log in

%DNADataRoot%\Shared\Log, and then contact your Administrator.

Unable to read file.

This alarm is generated if the system is unable to read a file.

Correct the error that led to the failure.

Corrupt pipeline record.

This alarm is generated when the pipeline record is corrupted.

Correct the error that led to the failure.

Corrupt record. See batErrLog.

This alarm is generated when the pipeline record is corrupted.

Correct the error that led to the failure.

Node [nodeName] has corrupt pipeline reference.

This alarm is generated when the node has corrupt pipeline reference.

Correct the error that led to the failure.

Detect [detectName] has corrupt pipeline reference.

This alarm is generated when the detect has a corrupt pipeline reference.

Correct the error that led to the failure.

Adetect [anomalyDetectName] has corrupt pipeline reference.

This alarm is generated when the adetect has a corrupt pipeline reference.

Correct the error that led to the failure.

Section [sectionName] has corrupt pipeline reference.

This alarm is generated when the section has a corrupt pipeline reference.

Correct the error that led to the failure.

Pipe [pipelineName] has corrupt pipeline reference.

This alarm is generated when the pipe has a corrupt pipeline reference.

Correct the error that led to the failure.

Connectivity [recordNumber] has corrupt pipeline reference.

This alarm is generated when the connectivity has a corrupt pipeline reference.

Correct the error that led to the failure.

Database is full. See batErrLog.

This alarm is generated if the database is full.

Correct the error that led to the failure.

Revert file not current.

This alarm is generated if the revert file is not current.

Correct the error that led to the failure.

Record creation problems. See batErrLog.

This alarm is generated if pipeline record creation has problems.

Correct the error that led to the failure.

Batch Tracking Messages

Anomaly <name> arriving in <minutes> minutes in pipeline <pipeline name>.

Indicates the time that an anomaly will arrive at the destination node.

No response required.

Anomaly <name> is <volume>bbl<upstream | downstream> from <node> in pipeline <pipeline name>.

Indicates how many barrels of volume that an anomaly is away from the destination node that is upstream.

Alternatively, if it is downstream, or has passed the destination node, that information will be provided as well.

No response required.

Deleting Fragment [Fragment name] from batch ID [Batch name].

The alarm message occurs when the fragment is deleted from the batch.

No response required.

Fragment [Fragment name] changed from batch [Batchname] to batch [BatchName].

The alarm message occurs when the fragment name is changed.

No response required.

Attempt to save backup file for pipeline [Pipeline name] failed.

The alarm message occurs if an operation is failed while attempting to save the backup file for the pipeline.

Contact your Administrator. Consult the oasErrLog.log in %DNADataRoot%\Shared\Log for more information.

Interface Detection

<interface> FOUND On time.

The alarm message occurs if the interface is detected within the volume deadband of the detector location and a good threshold exists to detect the interface.

No response required.

<interface> too close.

The alarm message occurs if the batch properties are too close to determine a good detection threshold.

No response required.

<interface> Early-<volume offset from detector location>bbl.

The alarm message occurs if the interface is detected upstream and outside the detector location threshold.

No response required.

<interface> Late-<volume offset from detector location>bbl.

The alarm message occurs if the interface is detected downstream and outside the detector location deadband.

No response required.

Gave up on interface detection for <interface>.

This alarm message occurs if the interface that was predicted by Batch Tracking has passed the detector and the deadband zone without a detection event.

Investigate why the Batch Tracking application failed to detect the interface.

Threshold calc OK.

This alarm message occurs if the bad threshold was previously calculated for the interface but the threshold is now good. This can only happen if the configured property value limit has been edited or a batch property has been edited.

No response required.

Interface Detect triggered: [detectName]:

[alarmState]: Threshold calc OK :[currentBatch]/

[nextBatch] Not found in [abs_vol] [Volume Unit].

This alarm message occurs if the batch is not found within the volume deadband of the detector location to determine a good detection threshold.

No response required.

Interface Detect triggered:[detectName]:[alarmState]:[currentBatch]/

[nextBatch] MISSED beyond downstream node.

This alarm message occurs if the batches are missed beyond the downstream node.

Investigate the source of the interface detect. For more information, see Access the Interface Detect Control dialog.

Interface Detect triggered:[detectName]:[alarmState]:[currentBatch]/[nextBatch] FOUND beyond downstream node.

This alarm message occurs if the batches are found beyond the downstream node.

No response required.

Interface Detect triggered:[detectName]:[alarmState]:[currentBatch]/[nextBatch] FOUND before upstream node.

This alarm message occurs if the batch is found before the upstream node to determine a good detection threshold.

No response required.

Estimated Time of Arrivals

Batch <ID > arriving at <node name> in<no.> minutes in pipeline <pipeline name>.

or

Anomaly <name> arriving at <node name> in <no.> minutes in pipeline <pipeline name>.

This alarm occurs when the predicted arrival time is within a configured warning time for the node.

No response required.

Batch <ID > is <no.> bbls from <node name> in pipeline <pipeline name>.

or

Anomaly <name> is <no.>bbls from <node name> in pipeline <pipeline name>.

This alarm occurs when the batch is within a configured volume away from the node in the pipeline.

No response required.

Batch <ID > has arrived at <node name> in pipeline <pipeline name>.

or

Anomaly <name> has arrived at <node name> in pipeline <pipeline name>.

This alarm occurs when the batch or anomaly has arrived at the node.

No response required.

Batch [batchid] arriving in [no of minutes] minute/s in pipeline [pipelineName].

This alarm occurs when the predicted arrival time is within a configured warning time for the pipeline.

No response required.

Pipeline (<pipeline name>) has an invalid Unit Profile configuration in (<pipe segment count>) pipe segment(s). Pipeline deactivated. See oasErrLog for detail.

One or more of the pipe_segment records in the pipeline have an invalid Unit Profile configuration. The pipeline has been deactivated as it cannot be safely processed without a valid Unit Profile configuration on all of its pipe_segment records.

Contact your Administrator. Consult the oasErrLog.log in %DNADataRoot%\Shared\Log for more information.

Pipeline (<pipeline name>) has an invalid Unit Profile configuration in (%d) pipe segment(s). Attempt to deactivate pipeline failed. See oasErrLog for detail.

One or more of the pipe_segment records within the pipeline has an invalid Unit Profile configuration.

The attempt to deactivate pipeline was unsuccessful.

Please contact a system Administrator immediately.

Flow Rate

Configuration error. Pipeline <name> Segment <name> has invalid or unsupported type on Flow Rate Source Path. Contact your system administrator.

The Flow Rate Source Path field must point to a primitive numeric data type in the RealTime database (for example, analog.curval or rate.currate).

When this constraint is violated, Batch Tracking will raise this alarm and default to the system calculated flow rate.

Please contact a system Administrator.

Pipeline <name> Segment <name> Flow Rate Source path configuration error has been resolved.

This Return-to-Normal alarm indicates when the erroneous Flow Rate Source Path condition is resolved.

No response required.

Plugin Alarm Messages

Configuration error. Pipeline <name> has invalid enumeration value of <value> on Linepack Calculation Method. Contact your system administrator.

Given the extended linepack algorithm enumeration value (that is, lpackalg), the Batch Tracking application cannot find the plugin method.

Please contact a system Administrator.

Pipeline <name> Linepack Calculation Method configuration error has been resolved.

The linepack configuration error is resolved.

No response required.

Conditional Transmitter

Configuration error. Pipeline <name> Segment <name> has invalid auto inhibit path on pressure downstream transmitter input. Contact your system administrator.

The Pressure Downstream Transmitter Auto Inhibit Path field must point to a valid Status, Multistate, or AlpConfig record in the RealTime database (RTDB).

When the constraint is violated, Batch Tracking raises this alarm (it will not inhibit the corresponding analog).

Please contact a system Administrator.

Pipeline <name> Segment <name> pressure downstream transmitter input configuration error has been resolved.

The system generates a Return-to-Normal alarm when the erroneous Pressure Downstream Transmitter Auto Inhibit Path condition is resolved.

No response required.

Configuration error. Pipeline <name> Segment <name> has invalid auto inhibit path on pressure upstream transmitter input. Contact your system administrator.

The Pressure Upstream Transmitter Auto Inhibit Path field must point to a valid Status, Multistate, or AlpConfig record in the RealTime database (RTDB).

When the constraint is violated, Batch Tracking raises this alarm (it will not inhibit the corresponding analog).

Please contact a system Administrator.

Pipeline <name> Segment <name> pressure upstream transmitter input configuration error has been resolved.

The system generates a Return-to-Normal alarm when the erroneous Pressure Upstream Transmitter Auto Inhibit Path condition is resolved.

No response required.

Configuration error. Pipeline <name> Segment <name> has invalid auto inhibit path on temperature downstream transmitter input.

The Temperature Downstream Transmitter Auto Inhibit Path field must point to a valid Status, Multistate, or AlpConfig record in the RealTime database (RTDB).

When the constraint is violated, Batch Tracking raises this alarm (it will not inhibit the corresponding analog).

Please contact a system Administrator.

Pipeline <name> Segment <name> temperature downstream transmitter input configuration error has been resolved.

The system generates a Return-to-Normal alarm when the erroneous Temperature Downstream Transmitter Auto Inhibit Path condition is resolved.

No response required.

Configuration error. Pipeline <name> Segment <name> has invalid auto inhibit path on temperature upstream transmitter input. Contact your system administrator.

The Temperature Upstream Transmitter Auto Inhibit Path field must point to a valid Status, Multistate, or AlpConfig record in the RealTime database (RTDB).

When the constraint is violated, Batch Tracking raises this alarm (it will not inhibit the corresponding analog).

Please contact a system Administrator.

Pipeline <name> Segment <name> temperature upstream transmitter input configuration error has been resolved.

The system generates a Return-to-Normal alarm when the erroneous Temperature Upstream Transmitter Auto Inhibit Path condition is resolved.

No response required.

Anomaly Detect launched: [anomaly Name].

If enabled, the anomaly detection feature has detected a signal to launch an anomaly.

No response required.

Anomaly Detect received: [anomaly Name].

If enabled, the anomaly detection feature has detected that an anomaly has arrived at the designated Receiver.

No response required.

Anomaly Detect error occurred - please see log for details.

If enabled, the anomaly detection feature has detected that an error occurred.

This is an indication that something is wrong.

Investigate to discover the source of the problem by reviewing the oasErrLog.log.

Anomaly Detect triggered: [anomaly Name] (UPS-NORMAL [anomaly location] {2}).

If enabled, the anomaly detection feature has detected the anomaly upstream of the adetect record within the configured Normal window.

No response required.

Anomaly Detect triggered: [anomaly Name] (DNS-NORMAL [anomaly location] {2}).

If enabled, the anomaly detection feature has detected the anomaly downstream of the adetect record within the configured Normal window.

No response required.

Anomaly Detect triggered: [anomaly Name] (UPS-EARLY [anomaly location] {2}).

If enabled, the anomaly detection feature has detected the anomaly upstream of the adetect record within the configured Early or Late window.

This can provide an indication that something is wrong. Investigate to discover the source of the problem.

Anomaly Detect triggered: [anomaly Name] (DNS-LATE [anomaly location] {2}).

If enabled, the anomaly detection feature has detected the anomaly upstream of the adetect record within the configured Early or Late window.

This can provide an indication that something is wrong. Investigate to discover the source of the problem.

Anomaly Detect triggered: [anomaly Name] (UPS-TOO-EARLY [anomaly location] {2}).

If enabled, the anomaly detection feature has detected the anomaly upstream of the adetect record outside of the configured Early or Late window.

This can provide an indication that something is wrong. Investigate to discover the source of the problem.

Anomaly Detect triggered: [anomaly Name] (DNS-TOO-LATE [anomaly location] {2}).

If enabled, the anomaly detection feature has detected the anomaly upstream of the adetect record outside of the configured Early or Late window.

This can provide an indication that something is wrong. Investigate to discover the source of the problem.

Anomaly Detect triggered: MISSING-ETA [anomaly Name].

If enabled, the anomaly detection feature did not find an ETA for an anomaly to associate a detection with.

This can provide an indication that something is wrong. Investigate to discover the source of the problem.

Anomaly Detect missing: [anomaly Name] (MISSING-SIGNAL [anomaly location] {2}).

If enabled, the anomaly detection feature had an anomaly move outside of the Early or Late window that was too late—without being detected.

This can provide an indication that something is wrong. Investigate to discover the source of the problem.

Anomaly [anomaly Name] is [volume quantity] [volume unit] away from downstream segment [segment name] which leads to segment(s) that do not expect anomalies of type [anomaly type]: [list of segment names].

Warning that if the anomaly enters the specified downstream segment, either that segment or one further downstream of that segment does not expect this type of anomaly.

Monitor flow conditions in the pipeline to ensure the anomaly will move down a flow path that does not contain the specified segment.

Anomaly [anomaly Name] has entered segment [segment name] which is or leads to segment(s) that do not expect anomalies of type [anomaly type]: [list of segment names].

The anomaly is currently in a segment that does not expect this type of anomaly, or this segment will lead to a segment that doesn’t expect this type of anomaly.

Confirm if the simulated location of the anomaly reflects the real location in the pipeline and follow the appropriate procedure to manage this situation.

Anomaly [anomaly Name] is [volume quantity] [volume unit] away from downstream segment [segment name] which does not lead to the designated receiver: [adetect name] on node [node name].

Warning that if the anomaly enters the specified downstream segment, it will not reach its designated receiver.

Monitor flow conditions in the pipeline to ensure the anomaly will move down a flow path that leads the anomaly to its designated receiver.

Anomaly [anomaly Name] has entered segment [segment name] which does not lead to the designated receiver: [adetect name] on node [node name].

The anomaly is currently in a segment that will not lead the anomaly to its designated receiver.

Confirm if the simulated location of the anomaly reflects the real location in the pipeline and follow the appropriate procedure to manage this situation.

Slip factor for anomaly [anomaly name] changed from [previous slip factor] to [current slip factor], because anomaly moved from [previous segment] to [current segment].

This event is generated when the anomaly is configured to use pipe segment slip factor, and the anomaly has moved into a new pipe segment that has a slip factor that is different than the previous pipe segment.

No response required.