Skip to Main Content
AVEVA™ Products Feedback Portal

Welcome to our new feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, select the product of your interest in the left column. Then take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas will first be moderated before they are made visible to other users of this portal.

This page is for feedback for specific AVEVA solutions, excluding PI Systems and Data Hub. For links to these other feedback portals, please see the tab RESOURCES below.

Status Waiting for information
Created by Daniel Bennett
Created on Apr 17, 2024

Automatic Ticket Splits on MCF Changes

Earlier releases of OASyS metering/ticketing allowed a user to configure their logical meters ("batmtrs") to perform a ticket split when the meter correction factor ("MCF") changed. As a result, the completed ticket for the previous accumulation would have the previous MCF, and the new active ticket would have the new MCF.


The MCF may be adjusted over the course of a batch in the event of changes to a physical meter's flowrate or to the flowing product's density. If the ticket is not split at that time, then the final ticket cut for that batch will only contain the final MCF used by the VFC. This can be misleading to accounting staff verifying SCADA-corrected volumes, or to third-party accounting staff if the ticket is being used for custody transfer.

Problem Statement

Status: No known workaround for batchXfers/VFCs.


Personas: Accounting users; third-party customers.


Business impact: Being able to identify MCF changes over the course of a batch provides important forensic data to volume accounting staff. This information is also required as part of a custody transfer ticket.

Expectation

If a VFC's meter correction factor should change, it should be configurable to have a ticket split occur on all associated batchXfers to preserve the previous MCF on the completed ticket.

Idea Type Improvement
Idea Category Sustainability
Idea priority 3 – Some use to my company
User Persona Pipeline Operator, Control Room Supervisor, SCADA Administrator, Corporate User / Analyst, Measurement Analyst
  • Attach files
  • Admin
    Mike Demcoe
    Reply
    |
    Apr 18, 2024

    Given that we have a matrix for the MCF lookup, what would be the expectation when the density or flow rate is hovering around the transition point between values? e.g. density is 800 to 825 kg/m3 but the fluid density is hovering around 825 kg/m3. This could result in a ticket being cut very frequently.

    For this reason, this is why we opted for a weighted average. This is also compliant with API 21.2 section 9.2.10.5

  • Admin
    Mike Demcoe
    Reply
    |
    Apr 18, 2024

    As of 2022 SP1, there is now a weighted average meter factor that is on the ticket so it's no longer reporting the last used meter factor.