Understand the Batch Split command

The Batch Split command is issued when it has been determined that the data processed so far needs to be saved to a completed ticket record and the next portion of the batch to be processed needs to be in a different completed ticket record. Reasons for this include a change in a property of the batch or a time and date being reached that is the end of a reporting period.

To issue a Batch Split command for a Host-Managed location

1. The operation is validated by confirming that the following conditions are true:

   • An active batch is present.

   • If there is no volume yet accumulated on the active batch, the batch transfer is configured to allow a split of a zero volume batch.

     Note: If any of the conditions are false, the operation is invalid and is canceled.
     — If Controller initiated, an error message is presented to the Controller.
     — If automatically initiated, an alarm is issued.

2. Batch Completion is executed. For more information on Batch Completion, see Understand the Batch Completion command.

3. A new active batch is initialized from the batch that was completed:

   • Batch ID and product are the same.

   • The same schedule sequence number is used but a suffix is added to differentiate the new record from the record of the completed batch.

   • The Scheduled Volume stays the original scheduled volume for all ticket splits.

   • The Volume to Go for each batch reflects the remaining volume, taking into account the previous split tickets of the same batch.

   • Measurement units are the same.

   • Contaminated flag is the same.

4. Calculated or derived fields for the active batch are initialized:

   • Batch Gross Standard Volume (GSV), Gross Volume (GV), and Batch Flow Rate is set to zero.

   • The Scheduled Volume does not change for the same batch, even after a split.

   • The Volume To Go represents the remaining volume, taking into account the volume flowed on all ticket splits for the batch.

   • Weighted Average Sediment, Water percentage, and Viscosity & Sulphur percentage are set to the observed values at the configured analogs.

   • Hourly volume is set to zero.

   • Start time is set to current time, provided that the batch transfer is not configured to set start time when volume throughput for the batch is first observed.

   • Estimated completion time is blank.

5. Calculated or derived fields from each input device are initialized. Devices that are inhibited are not included.

   1. For all types:

      • Device Batch GSV and Device Batch Flow Rate are set to zero.

   2. For counter types:

      1. Starting and current GSV counters are set to the closing GSV counter from the completed batch.

      2. Starting and current Indicated Volume (IV) counters are set to the closing IV counter from the completed batch.

      3. Weighted Average Temperature, Pressure, Densities, Observed Density, Meter Correction Factor (MCF), Weighted Average Correction for Temperature of a Liquid (CTL), and the Weighted Average Correction for Pressure of a Liquid (CPL) are set to the observed values at the input device.

      4. Meter Correction Factor is set to the configured value for the MCF.

      5. Correction inhibits are the same as from the completed batch.

   3. For tank types:

      • Tank volumes, measurements, and parameters at closing of the completed batch are saved as both start state information and current state information.