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.

Portfolio area Enterprise SCADA Server
Created by Guest
Created on Feb 8, 2022

Alternate timeseries hourly averaging algorithm

Enhancement request to either allow integrators to modify timeseries averaging algorithm or provide hooks to allow integrator to modify the operation.

We implemented an alternative timeseries averaging algorithm on many installations. Prior to binary release in 2021 this modification was completed through direct modification of the collect code. The integrator would change averaging to be based on GOOD DQ samples only, and storing of average counts (the number of GOOD DQ samples used to calculate the average value) within the TimeSeries summary records


  • Attach files
  • Admin
    Jake Hawkes
    Reply
    |
    Feb 8, 2022

    Seems like an enhancement to make collect only consider good DQ in the average would be simpler and more effective here.

    Are there any other requirements lurking here that aren't listed due to the request to make this extensible?

    There is a new data export framework called HPDEF (High Performance Data Export Framework), which baseline itself will use to develop a new Exception Collect plugin, for the purposes of being able to put any field on exception collect, instead of the hard-coded list it supports today. The HPDEF provides plugins with a complete copy of the record before and after the data change that triggered the framework.

    So, you could implement your own plugin that performs collect according to your desired business logic, and then implement your own historical aggregation in Historical. Coupled with the Krunch Pipeline, you could calculate the same custom aggregates in Realtime.