Understand Batch Transfer alarms and events
- Last UpdatedApr 24, 2025
- 8 minute read
The following table provides details for configuring the Batch Transfer alarm/event messages.
Note: The messages noted in the table are designated as either alarms that generate identical events or as simple events. In all cases, you can customize the message text and, where applicable, adjust the alarm severity. To update the alarm/event message, refer to the msgInfo table row for the Alarm Message Identifier of interest. For more information on configuration using the msgInfo table, refer to Volume 1 of the RealTime Administrator documentation.
|
Alarm/Event Message |
Alarm/Event Message Configuration |
Alarm Severity Configuration |
Type |
|---|---|---|---|
|
Start ticket validation failed for Batch Transfer <Batch Transfer Name>. The next pending ticket does not have an Action Sequence. |
BATCHXFER_VALIDATION_FAILED_NEXT_TKT_ACTION_SEQ 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 batchXfer record before the ticket can be started. |
Base Message |
Alarm & Event |
|
Start ticket validation failed for Batch Transfer <Batch Transfer Name>. The Action Sequence <Action Sequence Name> is inhibited. |
BATCHXFER_VALIDATION_FAILED_ACT_SEQ_INHIBIT This occurs when the Action Sequence associated with this batchXfer record has been inhibited. Given that Action Sequences can be inhibited by both Controller and Administrator, you may want to check the associated Action Sequence record to see if it was accidentally inhibited or consult the Administrator. |
Base Message |
Alarm & Event |
|
Start ticket validation failed for Batch Transfer <Batch Transfer Name>. The Action Sequence <Action Sequence Name> was not found. |
BATCHXFER_VALIDATION_FAILED_ACT_SEQ_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. |
Base Message |
Alarm & Event |
|
Start ticket validation failed for Batch Transfer <Batch Transfer Name>. There are no pending tickets. |
BATCHXFER_VALIDATION_FAILED_NO_PENDING_TKTS This error occurs when there are no tickets associated with the batchXfer record. To remedy the situation, enter more pending tickets. |
Base Message |
Alarm & Event |
|
New Schedule is available. |
BATXFER_NEW_SCHEDULE |
Use the MsgInfo table row identified with the following name: BATXFER_NEW_SCHEDULE |
Alarm & Event |
|
Entries in pending schedule are low : pend= <pending cnt>, limit=<min pending cnt>. |
BATXFER_LOW_PENDING_SCHEDULE |
Base Message |
Alarm & Event |
|
Ticket <BatchID> doesn’t match schedule: vol=<Gross Standard Volume>, sch=<Scheduled Gross Standard Volume>. |
BATXFER_TICKET_SCHEDULE_VOL |
Base Message |
Alarm & Event |
|
Sediment & water percentage of <Value Read from Analog>% from analog <Analog Name> is out of range (0-100). |
BATCHXFER_SEDIMENT_WATER_ANALOG_OUT_OF_RANGE This message is provided when the analog reading for sediment and water percentage is out of range. |
Configured using the Severity field on the Sediment and Water (%) section of the Batch Transfer ADE form. |
Alarm & Event |
|
Sediment & water percentage of <Value Read from Analog>% from analog <Analog Name> is within range (0-100). |
BATCHXFER_SEDIMENT_WATER_ANALOG_WITHIN_RANGE |
Configured using the Severity field on the Sediment and Water (%) section of the Batch Transfer ADE form. |
Alarm & Event |
|
Batch Transfer auto ticket split failed for batchXfer: <Batch Transfer Name>. |
BATCHXFERALM_GENERAL_BATCHXFER_FAILED The auto ticket split failed 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. |
Base Message |
Alarm & Event |
|
Batch Transfer auto ticket split started for batchXfer: <Batch Transfer Name>. |
BATCHXFERALM_GENERAL_BATCHXFER_PASSED The auto ticket split started alarm is generated when the ticket split is performed successfully at the Batch Transfer location due to the Batch Transfer becoming uninhibited. |
Base Message |
Alarm & Event |
|
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. |
BATXFER_INVALID_ANALOG_CONFIG This alarm/event message is logged when a configured analog record is deleted. |
BATXFER_INVALID_ANALOG_CONFIG |
Alarm & Event |
|
Batch Transfer <Batch Transfer Name> configuration error has been resolved. |
BATXFER_VALID_ANALOG_CONFIG This alarm/event message is provided when the Batch Transfer record recovers from a configuration error. |
BATXFER_VALID_ANALOG_CONFIG |
Alarm & Event |
|
Product mismatch between Batch Transfer <Batch Transfer Name> (<Batch Transfer Product Type Name>) and Tank source <Tank Name> (<Tank Product Type Name>) detected. Product type of the Tank has been overwritten. |
BATXFER_MISMATCH_BTWN_BATXFER_AND_TANK_SOURCE |
BATXFER_MISMATCH_BTWN_BATXFER_AND_TANK_SOURCE |
Alarm & Event |
|
Product mismatch between Batch Transfer <Batch Transfer Name> (<Batch Transfer Product Type Name>) and Virtual Flow Computer source [VFC Name] (<VFC Product Type Name>) detected. Product type of the Virtual Flow Computer source has been overwritten. |
BATXFER_MISMATCH_BTWN_BATXFER_AND_VFC_SOURCE |
BATXFER_MISMATCH_BTWN_BATXFER_AND_VFC_SOURCE |
Alarm & Event |
|
Product type of virtual flow computer source <VFC Name> has been set to the product type of batch transfer <Batch Transfer Name> (<Batch Transfer Product Type Name>). |
BATXFER_PRODTYPE_VFC_SETTO_PRODTYPE_BATCHXFER |
BATXFER_PRODTYPE_VFC_SETTO_PRODTYPE_BATCHXFER |
Alarm & Event |
|
<Batch Ticket ID> Warning Time 1 - less than <Time to Completion> to batch completion. |
BATCHXFER_TRACK_WARNING_TIME_LESS_THAN_ONE The Batch Transfer warning time 1 alarm is generated when a Batch Transfer ticket has a GSV amount that will be completed by the time the warning time is completed. |
Base Message |
Alarm & Event |
|
<Batch Ticket ID> Warning Time 2 - less than <Time to Completion> to batch completion. |
BATCHXFER_TRACK_WARNING_TIME_LESS_THAN_TWO The Batch Transfer warning time 2 alarm is generated when a Batch Transfer ticket has a GSV amount that will be completed by the time the warning time is completed. |
Base Message |
Alarm & Event |
|
<Batch Ticket ID>: Warning Volume - less than <Volume Warning> <Measurement Unit> to batch completion. |
BATCHXFERALM_AUTO_TRK_WRN_VOL The auto-track warning volume alarm is triggered when the current Batch Transfer ticket GSV reaches the threshold set. |
Base Message |
Alarm & Event |
|
<Batch Ticket ID>: Auto split occurred on contaminated batch: pumped <Current Ticket Volume> <Measurement Unit>. |
BATCHXFER_ALARM_CONTAMINATED_BATCH The auto-split on contaminated batch alarm is generated when a Batch Transfer is contaminated and its status is set from Closed, to Open, and back to Closed (twice). |
Base Message |
Alarm & Event |
|
<Batch Ticket ID>: Auto split occurred on batch: pumped <Current Ticket Volume> <Measurement Unit>. |
BATCHXFER_ALARM_SPLIT_BATCH_AUTO The Batch Transfer auto-split on batch alarm is generated when the Top of Day action is set to split, and the Top of Day hour is set to the current hour of the day (0-23)—as well as having the {Lasttime.high} parameter set to itself minus 5000. |
Base Message |
Alarm & Event |
|
<Batch Ticket ID>: Auto start occurred: pumped <Current Ticket Volume> <Measurement Unit>. |
BATCHXFER_ALARM_AUTO_START_OCCURED The Batch Transfer auto-start occurred alarm occurs when a Batch Transfer has one pending ticket and one started ticket with the BatchSwitchCriteria parameter set to OpenToClose with a status that starts as closed. The status is switched from Closed, to Open, and back to Closed (twice). |
Base Message |
Alarm & Event |
|
<Batch Ticket ID>: Unable to start next ticket, Auto split occurred: pumped <Current Ticket Volume> <Measurement Unit>. |
BATCHXFER_ALARM_UNABLE_TO_START The Batch Transfer unable to start alarm occurs when a Batch Transfer has 0 pending tickets and 1 started ticket with the BatchSwitchCriteria parameter set to OpenToClose (status begins as closed). The status is switched from Closed, to Open, and back to Closed (twice). |
Base Message |
Alarm & Event |
|
<Batch Ticket ID>: Automatic track completed: pumped <Processed Ticket Volume> <Measurement Unit>. |
BATCHXFERALM_AUTO_TRK_COMP The Batch Transfer automatic track completed alarm is generated when a Batch Transfer ticket GSV amount is completed. |
Base Message |
Alarm & Event |
|
Issued Command {0}. |
BATCHXFER_GENERATE_CONTROL_COMMAND |
N/A |
Event |
|
<BATCH ID>: Ticket start failed: Batch switch point did not reset within the <time out> second timeout period. |
BATXFER_BATCH_SWITCH_RESET |
Base Message |
Alarm & Event |
|
Ticket <BATCH ID> moves to normal. |
BATXFER_TICKET_NORMAL |
N/A |
Event |
|
Batch Transfer < BATCH ID> ticket start failed. |
BATXFER_TICKET_START_FAILED |
Base Message |
Alarm & Event |
|
Batch Transfer < BATCH ID> ticket start failed. See error log. |
BATXFER_TICKET_START_FAILED_ERROR |
Base Message |
Alarm & Event |
|
Ticket <BATCH ID> moves to completed. Maintenance ticket started. |
BATXFER_MAINTENANCE_TICKET_START |
N/A |
Event |
|
Failed to swap Active Batch <Active BATCH ID> <TKT NUM> with Pending Batch<PEND BATCH ID> <PEND TKT NUM> <USER><FailureInfo>. |
BATXFER_SWAP_BATCH |
N/A |
Event |
|
Completed swap of Active Batch '<Active BATCH ID> ' - Ticket ID '<TKT NUM> ' with Pending Batch '<PEND BATCH ID> ' - Ticket ID '<PEND TKT NUM>' <USER>. |
BATXFER_SWAP_BATCH_COMPLETED |
N/A |
Event |
|
Batch Transfer manual ticket split started for batchXfer: <Batch Transfer Name>. |
BATXFER_TICKET_SPLIT_STARTED |
Base Message |
Alarm & Event |
|
Batch Transfer manual ticket split failed for batchXfer: < Batch Transfer Name>. |
BATXFER_TICKET_SPLIT_FAILED |
Base Message |
Alarm & Event |
|
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. |
BATCHXFER_TOP_OF_DAY_CONFIG_ERROR |
BATCHXFER_TOP_OF_DAY_CONFIG_ERROR |
Alarm & Event |
|
Batch transfer '<Batch Transfer Name>': Top of Day configuration error has been resolved, Top of Day aggregation is using configured hour. |
BATCHXFER_TOP_OF_DAY_CONFIG_RETURN_TO_NORMAL This message is generated as soon as the problem is fixed. |
BATCHXFER_TOP_OF_DAY_CONFIG_RETURN_TO_NORMAL |
Alarm & Event |
|
Batch transfer '<Batch Transfer Name>' hourly, daily, monthly, and yearly periodic aggregation reset. Indicated volumes: <Hourly IV>, <Daily IV>, <Monthly IV>, <Yearly IV> <Volume Unit>. Gross standard volumes: <Hourly GSV>, <Daily GSV>, <Monthly GSV>, <Yearly GSV> <Volume Unit>. |
BATXFER_PERIODIC_AGGREGATION_RESET This message is provided when the periodic counters are reset by clicking Reset Periodic Aggregation Counters. |
N/A |
Event |
|
Batch transfer '<Batch Transfer Name>' periodic aggregation total reset. Indicated volume: <Total IV> <Volume Unit>. Gross standard volume: <Total GSV> <Volume Unit>. |
BATXFER_PERIODIC_AGGREGATION_TOTAL_RESET This message is provided when the total counters are reset by clicking Reset Total Periodic Aggregation Counters. |
N/A |
Event |
|
Batch transfer '<Batch Transfer Name>' hourly, daily, monthly, yearly and total batch aggregation reset due to starting a new batch. Indicated volumes: <Hourly IV>, <Daily IV>, <Monthly IV>, <Yearly IV> <Volume Unit>. Gross standard volumes: <Hourly GSV>, <Daily GSV>, <Monthly GSV>, <Yearly GSV> <Volume Unit>. |
BATXFER_BATCH_AGGREGATION_RESET This message is provided when the Batch Aggregation block is reset and historized due to a ticket Start. |
N/A |
Event |
|
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>. |
BATXFER_MCF_CORRECTED This message is provided when there is a change in the MCF value at the source device <Source type: VFC>. |
N/A |
Event |
|
- Ticket ID '{PendingTicketNumber}'. |
BATCHXFER_TICKET_ID This is a partial text that supports other events that are generated when batch cloning fails and is concatenated with the configuration message. |
N/A |
Event |
|
Failed to clone Batch {PendingBatchId} {PendingTickerNumber} {UserInfo}.{Error}. |
BATCHXFER_CLONE_BATCH_FAILED This event is generated when batch cloning fails. |
N/A |
Event |
|
Completed clone of Batch '{ PendingBatchId }' - Ticket ID '{ PendingTicketNumber }'{UserInfo}. |
BATCHXFER_CLONE_BATCH_COMPLETE This event is generated when batch cloning has succeeded. |
N/A |
Event |
|
Could not execute {remoteTktCommand} on the Remote Ticketing Flow Computer after the Ticket Clone{UserInfo}. |
BATCHXFER_CANT_EXECUTE_RTFC_POST_CLONE This event is generated when the remote ticketing command fails to execute after cloning a ticket. |
N/A |
Event |
|
Could not update the Remote Ticketing Flow Computer after the Ticket Clone{USerInfo}. Error: {Error}. |
BATCHXFER_CANT_UPDATE_RTFC_POST_CLONE This event is generated if the system is unable to update the remote ticketing Flow Computer after cloning a ticket. |
N/A |
Event |
|
Accumulator '{AccumulatorName}' had a reset detected on weighted average density from '{PrevDensity}' to '{CurrDensity}' by {UserName} at {SystemName}. |
BATCHXFER_ACCUM_RESET_DETECT_DENSITY This event is generated when a reset is performed on the Weighted Average Density (WAD). |
N/A |
Event |
|
Accumulator '{AccumulatorName}' had a reset detected on weighted average pressure from '{PrevPressure}' to '{CurrPressure}' by {UserName} at {SystemName}. |
BATCHXFER_ACCUM_RESET_DETECT_PRESSURE This event is generated when a reset is performed on the Weighted Average Pressure (WAP). |
N/A |
Event |
|
Accumulator '{AccumulatorName}' had a reset detected on weighted average temperature from '{PrevTemperature}' to '{CurrTemperature}' by {UserName} at {SystemName}. |
BATCHXFER_ACCUM_RESET_DETECT_TEMPERATURE This event is generated when a reset is performed on the Weighted Average Temperature (WAT). |
N/A |
Event |