Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

AVEVA Pipeline Operations for Liquids

TABLE OF CONTENTS

Understand the new Metering-Ticketing features

Save PDF
Save selected topicSave selected topic and subtopicsSave all topics
Share
Share to emailCopy topic URL
  • Last UpdatedJul 04, 2024
  • 2 minute read

Prior to creating the new applications, Metering-Ticketing (Batch Meter) was analyzed and a full list of operational requirements determined. The new applications were designed to meet all operational requirements. Some features in Metering-Ticketing were re-implemented in the new applications, and others were not. This was because of the following reasons:

  • There were better ways to implement the feature's underlying operational requirement.

  • The feature did not fit any operational requirement. The feature may exist as a side-effect of the Metering-Ticketing design.

  • The feature concerned an operational requirement in an associated application. Applications are now designed without this operational overlap.

  • Use of the feature is unusual. In this case, implementation may be postponed until a customer requiring it appears and the requirement details can be better understood.

The following table describes the most significant Metering-Ticketing features that are absent from the new applications.

Absent Feature

Where Observed in Metering-Ticketing

Reason for Absence

Physical Meter Type (for example, Rolling, Batching)

ADE > Main tab > Physical Meter Type

This field is a mix of different properties and classifications. They are no longer used in the same context.

  • Rolling — No longer needed.

  • Batching — Not yet implemented in Virtual Flow Computer (VFC).

  • Multi-Headed — No longer supported.

  • Orifice — Not yet implemented in VFC.

  • Tank — Not needed. The tank records can be direct input into Batch Transfer.

  • Remote Ticket — Replaced by the Remote Ticket Control field in Batch Transfer (batchXfer > Remote Ticketing tab)

  • Resettable Rolling

Simulated meter can be flagged as fresh

ADE > Main tab > Use simulated flow data in PLM

Needed only for the Pipeline Monitoring (PLM) application. This is now handled in PLM.

Product-type checking

ADE > Ticket Management tab > Prod Type Check Deadband

This concerns cross-checking product information from Batch Tracking.

Note: If this feature is required in the future, it will be handled in another application (probably Product Transfer Checking) that can query Batch Transfer and Batch Tracking for information using an Application Program Interface (API).

MCF Management

ADE > MCF Management tab

Meter Correction Factor (MCF) validation and other management tasks table will be handled in a future application.

Delta/End-Start count calculation selection

ADE > Volume Calculation tab > Calc. Method for Accumulator Input

These are now both used automatically. VFC uses the Delta method to generate its own running volume count. Batch Transfer uses End-Start.

Automatic ticket split when an invalid polled volume counter is read from the rate record.

Automatic operation

There is no operational requirement for this. The combination of meter processing and batch processing made a split necessary to prevent the delta volume caused by a bad counter value from being included with the batch volume. A bad counter is now handled within the VFC without affecting the Batch Transfer.