Understand the Ticket Start function

The Ticket Start function initializes all fields for the active batch. It also cuts the ticket for the batch that was previously active.

If the Administrator has configured the batch transfer to activate an action sequence on batch start, the Batch Transfer application will activate the action sequence that has been configured on the pending batch that is being started. For more information on Action Sequences, see Action Sequence.

When a ticket is started, flow may not begin immediately. The Batch Switch Path field on the Batch Activation tab in the batchxfer Row Edit dialog in Advanced Database Editor (ADE) allows you to update the starting timestamp when flow is initially detected.

The active ticket is populated from the list of pending tickets.

The automatic triggers for a ticket start, which are individually configurable, include:

• When a configured Top of Day/Week/Month is reached.

• When a configurable status point changes state (for example, when an end of batch signal is received from the Remote Terminal Unit [RTU]).

If the Manual Batch Switch has been enabled, any automatic attempts to start a ticket during the timeout period will be prevented. If an automatic ticket start occurs outside of the timeout period, it will proceed as a normal ticket start without the delay.

Once a ticket becomes active, it must remain active for the minimum configurable time period before it can be stopped or a new ticket started. This avoids the problem of having multiple tickets started in a short time period. The minimum time period is configured through the Minimum Time (sec) field on the Batch Activation tab in the batchxfer Row Edit dialog in ADE. For information about the configuration of the Batch Transfer, see Edit the Active Batch on the Batch Transfer Edit dialog.

On a Batch Transfer, there is a configurable deadband that, when exceeded, causes the Batch Tracking application to compare the scheduled batch size and the actual batch size. The deadband is configured through the Volume Threshold Tolerance field on Batch Completion tab in the batchXfer Row Edit dialog in ADE.

Initiating a ticket start will reset any adjustments you have made to the Gross Standard Volume (GSV). As an example, assume that you entered a value for the GSV Adjustment in the Batch Transfer Edit dialog. Starting the ticket will reset these adjustments to zero.

The application compares the scheduled batch size against the actual volume delivered. If the absolute difference between the two sizes is greater than the deadband, an alarm is generated.

Note: Ticket Start works differently depending on whether your Batch Transfer is host-or remote-controlled. If your ticket information is supplied by a Telemetered Flow Computer, you will be able to override the Flow Computer's set controls and select Start. If your ticket information is supplied by a Payload Flow Computer, however, selecting Start will send the command to the Flow Computer to be issued.

For more information about Batch Transfer configuration, refer to the AVEVA Pipeline Operations for Liquids Administrator Guide documentation.