Configure the Periodic Action tab on the BatchXfer record

Open the batchXfer record.

For more information on opening a batchXfer record, see Open a BatchXfer record.

Navigate to the Periodic Action tab.

(Optional) To track the hourly, daily, monthly, yearly, and total Indicated Volume (IV) and Gross Standard Volume (GSV) counters for the batchXfer record across batch boundaries, select the Enable Periodic Aggregation checkbox. The state of this checkbox affects aggregations in the RealTime database as well as the Historical database. For more information on Batch Transfer Periodic Aggregation, see Understand Batch Transfer Periodic Aggregation.

Notes: If this checkbox is left cleared, the system will not update Periodic Aggregation fields in the RealTime tables and no records will be sent to the Historical database.
If this checkbox is selected in the middle of an aggregation period (for example, the middle of the hour), aggregation will start volume accumulation from this point on. It will not take into consideration volume that flowed before the configuration was enabled.
If this checkbox is cleared in the middle of an aggregation period, aggregation fields will stop volume accumulation from this point on, but the already accumulated volume will still be sent to the Historical database and reset at the end of the period.
If an inhibited batchXfer record is set to uninhibited while Periodic Aggregation is enabled, the aggregation values will catch up in accordance to the volume reported by the Batch Transfer sources.
The inhibit state of a batchXfer record has no impact on whether its aggregated values are sent to Historical. This is entirely determined by whether Periodic Aggregation is enabled.

(Optional) To track the hourly, daily, monthly, yearly, and total IV and GSV for the active batch, select the Enable Batch Aggregation checkbox. The state of this checkbox affects aggregations in the RealTime database as well as the Historical database. For more information on the Batch Transfer Batch Aggregations, see Understand Batch Transfer Batch Aggregation.

Notes: If this checkbox is left cleared, the system will not update Batch Aggregation fields in the RealTime tables and no records will be sent to the Historical database.
If this checkbox is selected in the middle of an aggregation period (for example, the middle of the hour), aggregation will start volume accumulation from this point on. It will not take into consideration volume that flowed before the configuration was enabled.
If this checkbox is cleared in the middle of an aggregation period, aggregation fields will stop volume accumulation from this point on, but the already accumulated volume will still be sent to the Historical database and reset at the end of the period.
If an inhibited batchXfer record is set to uninhibited while Batch Aggregation is enabled, the aggregation values will catch up in accordance to the volume reported by the Batch Transfer sources.
The inhibit state of a batchXfer record has no impact on whether its aggregated values are sent to Historical. This is entirely determined by whether Batch Aggregation is enabled.

In the Day of Month field, enter the day on which to cut or start a ticket for the preceding contract day or business day.

This is entered as a number from 1 to 31. Enter 0 to disable. The time that this action will occur is defined in the Hour of Day field.

Note: If a Ticket Action for one time period coincides with a Ticket Action for another time period, only the least frequent Ticket Action will be performed. For example, if a Top of Month action and a Top of Day action are enabled, and they occur at the same time, only the Top of Month action will be preformed.

From the Ticket Action dropdown, select the type of ticket action to be performed by Batch Transfer at the top of the month. There are two options:

Ticket Split — Performs a ticket split at the top of the month.
Ticket Start — Starts a new ticket at the top of the month.

To prevent the Ticket Action from being performed at the top of the month, select Inhibit Action.

To inhibit the alarm associated with the selected top of month Ticket Action, select Inhibit Alarm. An event will be generated regardless of the state of this checkbox.

In the Day of Week field, select the day of the week at which to cut or start a ticket for the preceding week.

From the the Ticket Action dropdown, select the type of ticket action to be performed by the Batch Transfer at the top of the week. There are two options:

Ticket Split — Performs a ticket split at the top of the week.
Ticket Start — Starts a new ticket at the top of the week.

To inhibit the selected Ticket Action from being performed at the top of the week, select Inhibit Action.

To inhibit the alarm associated with the selected top of week Ticket Action, select Inhibit Alarm. An event will be generated regardless of the state of this checkbox.

In the Hour of Day field, enter the hour at which to cut or start a ticket for the preceding contract day or business day. This is typed as a number from 0 to 23. Midnight is zero.

Note: Two special cases are identified if the configured Hour of Day coincides with the transition hour of Daylight Saving Time (DST) (varies following regional settings). The following examples illustrate how the ticket split/start will be handled in these cases:

Springing forward — DST comes into effect when local standard time is about to reach 2:00 AM on the second Sunday in March and the Hour of Day is configured to 2:00 AM:
For example, when the time updates from 1:59 AM to 3:00 AM on Mar 13, a Top of Day (TOD) ticket split/start will occur. A completed ticket covering Mar 12, 2:00:00 AM to Mar 13, 1:59:59 AM (24 hours of volume accumulation) will be created and sent to the Historical database.
The next TOD ticket split/start will occur on Mar 14 at 2:00 AM. And a completed ticket covering Mar 13, 3:00:00 AM to Mar 14, 1:59:59 AM (23 hours of volume accumulation) will be created and sent to the Historical database.

Falling back — DST ends when local daylight time is about to reach 2:00 AM on the first Sunday in November and the Hour of Day is configured to 1:00 AM:
For example, when the time updates from 12:59 AM to 1:00 AM on Nov 6, a TOD ticket split/start will occur. A completed ticket covering Nov 5, 1:00:00 AM to Nov 6, 12:59:59 AM (24 hours of volume accumulation) will be created and sent to the database. When the time updates from 1:59 AM to 1:00 AM, a TOD ticket split/start will not occur.
The next TOD ticket split/start will occur on Nov 7 at 1:00 AM. And a completed ticket covering Nov 6, 1:00:00 AM to Nov 7, 12:59:59 AM (25 hours of volume accumulation) will be created and sent to the Historical database.

From the Ticket Action dropdown, select the type of ticket action performed at the top of day. There are two options:

Ticket Split — Splits a ticket at the top of day.
Ticket Start — Starts a new ticket at the top of day.

(Optional) If the Enable Periodic Aggregation or the Enable Batch Aggregation checkbox is selected, do one of the following:

Select the Use Group Top of Day Hour checkbox if you want the Batch Transfer to use the top of day configured at the Group level using the Separate Top of Day (TOD) and Averages Rollup application, rather than the Top of Day > Hour of Day configured on the batchXfer record itself.

For more information on the Separate TOD and Averages Rollup feature, refer to Volume 1 of the AVEVA Enterprise SCADA RealTime Administrator documentation.

Note: If the Use Group Top of Day checkbox is selected, the Batch Transfer looks for a groupTOD record associated with the Group field. Therefore, assigning a Group to the Virtual Flow Computer (VFC) with a valid groupTOD record attached is mandatory, or the Advanced Database Editor (ADE) post validator will throw an error when saving.
In the Top of Day > Hour of Day field, enter the hour of the day (HH) for the TOD to occur for the record. This value is entered as a number from 0 to 23. Midnight is zero.

To inhibit the alarm associated with the selected top of day Ticket Action, select Inhibit Action.

To inhibit the selected Ticket Action alarm from activating at the top of day, select Inhibit Alarm. An event will be generated regardless of the state of this checkbox.

AVEVA Pipeline Operations for Liquids

Configure the Periodic Action tab on the BatchXfer record

Table of Contents

Configure the Periodic Action tab on the BatchXfer record

Related Links