Skip to Main Content
AVEVA™ PI System™ 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, 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 and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Status No Status
Created by Guest
Created on Aug 20, 2022

split analysis is real-time and recalculation part (different logic to be used)

It would be nice if we could have a "real-time" and "recalculate" part in an analysis. As source data could have changed you probably want sometimes the analysis to act in another way. Example: 2 attributes are used to trigger an event-triggered analysis and assume they write both a value for the same time stamp. in real-time this would mean that the analysis is triggered only once (1 trigger possible per time stamp) and is missing the value of one of the 2 attributes (depends who writes first). but with a recalculation both values are present and because of that the result can be different. so it would be nice if we can anticipate on this by allowing a different analysis setup taking the differences into account
  • Attach files
  • Guest
    Reply
    |
    Aug 20, 2022
    Bart, real time calculation with analyses include a default wait time of 5 seconds (configurable). Therefore in your scenario of both triggers arriving at the same time, both values would be included in the calculations. More importantly, if real time calculations and recalculations use different logic, then which result is correct? Perhaps in your case you should have two analyses with different logic generating two different result sets.
  • Guest
    Reply
    |
    Aug 20, 2022
    Stephen, if I'm correct then CalculationWaitTimeInSeconds is only valid for scheduled analyses.