Summary of Batch Transfer messages and alarms

<Batch ID>: Warning Time 1 – less than <Warning Time 1> to batch completion.

Metered volume is at the first warning time (away from completion). The first warning time is configured by the Administrator.

<Batch ID>: Warning Time 2 – less than <Warning Time 2> to batch completion.

Metered volume is at the second warning time (away from completion).The second warning time is configured by the Administrator.

<Batch ID>: Warning Volume – less than <Warning Volume><Units> to batch completion.

The metered volume has reached the warning volume amount that was configured to trigger an alarm.

<Batch ID>: Automatic track completed: pumped <Gross Standard Volume><Units>.

The Batch Transfer has completed its automated transfer amount.

<Batch ID>: Auto split occurred on contaminated batch: pumped <Pumped Volume><Units>.

The Batch Transfer detected a contaminated batch with auto-splitting enabled.

<Batch ID>: Auto split occurred on batch: pumped <Pumped Volume><Units>.

The Batch Transfer was configured to split on one of the following:

• Status point changes

• Top-of-day/week/month

• Split-on-volume

  This message indicates that the assigned condition has been achieved.

<Batch ID>: Unable to start next ticket, Auto split occurred: pumped <Pumped Volume><Units>.

An error condition has prevented the automatic start of a new ticket, and a split has occurred instead.

<Batch ID>: Auto start occurred: pumped <Pumped Volume><Units>.

Automatic switching has been enabled for a Batch Transfer and the ticket’s scheduled volume has been reached.

Batch Transfer <Batch Transfer Name> ticket start failed: Blank batchID.

The ticket failed to start because the batch ID was blank.

Batch Transfer <name> ticket start failed: Blank batchID, Invalid scheduled GSV.

The ticket failed to start because there was an invalid scheduled Gross Standard Volume (GSV).

Batch Transfer <Batch Transfer Name> ticket start failed: Blank prodtype.

The ticket failed to start because the prodtype was blank.

Batch Transfer <Batch Transfer Name> ticket start failed: Invalid prodtype.

The ticket failed to start because the prodtype was invalid.

Ticket <Batch ID> doesn’t match schedule: vol=<Gross Standard Volume>, sch=<scheduled Gross Standard Volume>.

The batch delivered does not amount to the amount of volume that was scheduled, even after accounting for potential time when no movement might take place.

Entries in pending schedule are low : pend=<Pending Ticket Count>, limit=<Minimum Pending Ticket Count>: <Description>.

There are fewer pending tickets remaining in the queue then the configured minimum-allowed value permitted by your Administrator.

Batch Transfer <Batch Transfer name> completed ticket queue has reached its maximum of 10 tickets within a single processing cycle. Dropping batch <Batch ID> from the queue to accommodate a new incoming batch.

For each processing cycle, the system inspects a queue of completed tickets that have yet to be recognized by Batch Tracking. In the unlikely scenario that within a single processing cycle the maximum queue size of 10 is exceeded, the system generates this event to let the Controller know that the first batch in the queue will be replaced by the new incoming batch.

Product mismatch between Batch Transfer <Batch Transfer Name> (<Batch Transfer Product>) and <Table Name> source <Record Name> ( <Product Type>) detected. Product type of the <Table Name> has been overwritten.

This occurs when a Batch Transfer source has a different product than the associated ticket on a Batch Transfer.

Start ticket validation failed for Batch Transfer "<Batch Transfer Name>". The next pending ticket does not have an Action Sequence.

This occurs when the Batch Transfer ticket fails to start because it does not have an associated Action Sequence. Your Administrator has required that an Action Sequence be associated with this Batch Transfer (batchXfer) record before the ticket can be started.

Start ticket validation failed for Batch Transfer "<Batch Transfer Name>". The Action Sequence "<Action Sequence Name>" is inhibited.

This occurs when the Action Sequence associated with this Batch Transfer record has been inhibited. Given that Action Sequences can be inhibited by both you and Administrator, you may want to check the associated Action Sequence record to see if it was accidentally inhibited or consult the Administrator.

Start ticket validation failed for Batch Transfer "<Batch Transfer Name>". The Action Sequence "<Action Sequence Name>" was not found.

This occurs when the defined Action Sequence cannot be found in the database. This may be the result of an error in the entry of the Action Sequence name.

Start ticket validation failed for Batch Transfer "<Batch Transfer Name>". There are no pending tickets.

This occurs when there are no tickets associated with the batchXfer record. To remedy the situation, enter more pending tickets.

Attempting to start an action sequence '<Action Sequence Name>'.

This message is provided when an attempt is being made to start an action sequence.

Ticket start failed: Batch switch point did not reset within the timeout period.

This message is provided if the field device does not reset within the Administrator-defined time period. At this point, if the field device resets after the timeout period has ended, the Batch Transfer does not start a new ticket.

However, you will be able to override this functionality if Start Ticket Immediately on the Batch Transfer Control window is selected.

Completed ticket <Ticket Name> <Value> has been modified from <Value> to <Value>.

This message is provided when a modification is made to a completed ticket.

Sediment & water percentage of <Value Read from Analog>% from analog <Analog Name> is out of range (0-100).

This message is provided when the analog reading for sediment and water percentage is out of range.

Batch Transfer <Batch Transfer Name> is detected with a configuration error, due to an invalid analog path for Sediment and Water, Sulphur and/or Viscosity. Please contact your administrator and see error log for more details.

This alarm/event message is logged when a configured analog record is deleted.

Batch Transfer <Batch Transfer Name> configuration error has been resolved.

This alarm/event message is provided when the Batch Transfer record recovers from a configuration error.

<Batch Transfer Name>: Ticket <Batch ID> moves to completed. Maintenance ticket started: <Description>.

Once the stop action is performed, the current ticket gets completed and a new maintenance ticket is automatically started.

<Batch Transfer Name>: Ticket <Batch ID> moves to normal: <Description>.

When the maintenance to normal action is performed, the current maintenance ticket is updated to a normal ticket.

Batch Transfer '<Batch Transfer Name>': The MCF value associated with Accumulator <Accumulator Name> has changed from <Old MCF Value> to <New MCF Value>. This may affect the GSV calculations for ticket <Active Batch ID>.

This message is provided when there is a change in the MCF value at the source device <Source type: VFC>.

Batch transfer '<Batch Transfer Name>' configuration error. A valid Top of Day should be set or it should have a Group with a valid Group Top Of Day. Until this issue is resolved, Top of Day aggregation will use midnight as default hour.

This alarm is generated when an invalid Top of Day (TOD) is configured (it can be an invalid GroupTOD or an incorrect TOD hour).

The alarm will be generated at the next Top of Hour.

Batch transfer '<Batch Transfer Name>': Top of Day configuration error has been resolved, Top of Day aggregation is using configured hour.

This Return-to-Normal alarm is generated when the invalid TOD configuration is resolved.

The alarm is generated as soon as the problem is resolved.

Batch transfer '<Batch Transfer Name>' hourly, daily, monthly, and yearly periodic aggregation reset. Indicated volumes: <Hourly Indicated Volume>, <Daily Indicated Volume>, <Monthly Indicated Volume>, <Yearly Indicated Volume> <Volume Unit>. Gross standard volumes: <Hourly Gross Standard Volume>, <Daily Gross Standard Volume>, <Monthly Gross Standard Volume>, <Yearly Gross Standard Volume> <Volume Unit>. Masses: <Hourly Mass>, <Daily Mass>, <Monthly Mass>, <Yearly Mass> <Mass Unit>.

This event is generated when the periodic counters are reset by clicking Reset Periodic Aggregation Counters.

Batch transfer '<Batch Transfer Name>' periodic aggregation total reset. Indicated volume: <Indicated Volume Quantity> <Volume Unit>. Gross Standard Volume: <Gross Standard Volume Quantity> <Volume Unit>. Mass: <Mass Quantity> <Mass Unit>.

This event is generated when the total counters are reset by clicking Reset Total Periodic Aggregation Counters.

Batch transfer '<Batch Transfer Name>' hourly, daily, monthly, and yearly batch aggregation reset due to starting a new batch. Indicated volumes: <Hourly Indicated Volume>, <Daily Indicated Volume>, <Monthly Indicated Volume>, <Yearly Indicated Volume> <Volume Unit>. Gross standard volumes: <Hourly Gross Standard Volume>, <Daily Gross Standard Volume>, <Monthly Gross Standard Volume>, <Yearly Gross Standard Volume> <Volume Unit>. Masses: <Hourly Mass>, <Daily Mass>, <Monthly Mass>, <Yearly Mass> <Mass Unit>.

This event is generated when the Batch Aggregation block is reset and historized due to a ticket Start.

Batch Transfer auto ticket split started for batchXfer: <Batch Transfer Name>.

This alarm is generated when an automatic ticket split is performed successfully at the Batch Transfer location due to the Batch Transfer becoming uninhibited.

Batch Transfer auto ticket split failed for batchXfer: <Batch Transfer Name>.

This alarm is generated when an automatic ticket split is attempted at the Batch Transfer location due to the Batch Transfer becoming uninhibited, but it fails because no volume has accumulated. This alarm is only raised when the Batch Transfer is configured to not allow zero volume splits.

- Ticket ID '{PendingTicketNumber}'.

This partial error event is generated when batch cloning fails and is concatenated with the configuration message.

Failed to clone Batch {PendingBatchId} {PendingTickerNumber} {UserInfo}.{Error}.

This event is generated when batch cloning fails.

Completed clone of Batch '{ PendingBatchId }' - Ticket ID '{ PendingTicketNumber }'{UserInfo}.

This event is generated when batch cloning has succeeded.

Could not execute {remoteTktCommand} on the Remote Ticketing Flow Computer after the Ticket Clone{UserInfo}.

This event is generated if the system is unable to update the remote ticketing Flow Computer after cloning a ticket.

Could not update the Remote Ticketing Flow Computer after the Ticket Clone{USerInfo}. Error: {Error}.

This event is generated if the system is unable to update the remote ticketing Flow Computer after a ticket clone.

Accumulator '{AccumulatorName}' had a reset detected on weighted average density from '{PrevDensity}' to '{CurrDensity}' by {UserName} at {SystemName}.

This event is generated when a reset is performed on the Weighted Average Density (WAD).

Accumulator '{AccumulatorName}' had a reset detected on weighted average pressure from '{PrevPressure}' to '{CurrPressure}' by {UserName} at {SystemName}.

This event is generated when a reset is performed on the Weighted Average Pressure (WAP).

Accumulator '{AccumulatorName}' had a reset detected on weighted average temperature from '{PrevTemperature}' to '{CurrTemperature}' by {UserName} at {SystemName}.

This event is generated when a reset is performed on the Weighted Average Temperature (WAT).