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.

Add a new idea Subscribe
Status Declined
Product AVEVA™ PI Server
Categories Analytics & Calculations
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

Write to output before analysis trigger initially

The customer has created some PI AF analyses these analyses trigger based on Event-Triggered. However, the customer his wondering if she can write a value to the output attribute before the analysis triggering for the first time. As of now, we only see “Pt. Created”, she would like the value that we see when pressing “evaluate” on the analysis written to the tag instead of “Pt. Created”.
  • ADMIN RESPONSE
    Aug 20, 2022
    As mentioned earlier, Pt. Created accurately represents the initial condition. Zero is a value and injecting a Zero into the output can have unintended consequences. Given that analyses are "triggered" either by a new input or periodically, a value of Zero can be inferred as having had a triggering event. As such, when you perform backfills or recalculations or summaries, this artificially injected Zero value would cause unintended results. We currently have no plans to implement this request.
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    I support this suggestion since there is a customer which after the Analysis Creation, sometimes the input values do not change for months - which the output attribute values are stuck on "Pt Created" during that time period.
  • Guest
    Reply
    |     Aug 20, 2022
    May be with additional feature like initialize to 0 when the tag is created instead of PT created and manual initialization, for cases where we want to the tag as a counter for analysis
  • Guest
    Reply
    |     Aug 20, 2022
    Pt. Created accurately reflects the fact that the point has been created but no values have been received. We should not put in a value when there is not. A Zero is a value.
  • Brent Bregenzer
    Reply
    |     Aug 20, 2022
    Couldn't the user backfill the calculation to the last triggering event before tag creation (or earlier)?  This should delete the Pt Created event and they would see the output from time of the previous the triggering event.
  • Guest
    Reply
    |     Aug 20, 2022
    In response to Brent Bregenzer, "Couldn't the user backfill the calculati..." what you say is true, but imagine I have created 100 tags for the sole purpose of using them in analysis where I would want the initial value to be 0 so that I can use it for Math operations. IN case there is pt created in these tags and I try to add a 1, it would throw calc failed.  So I have to initialize it to zero manually and then start my operations
  • Brent Bregenzer
    Reply
    |     Aug 20, 2022
    In response to Vinit Shah, "what you say is true, but imagine I have..." For these types of cases, I will typically build the initialization into the expression logic with If-Then-Else and either a badval check or an explicit check for a value of "Pt Created." It's typically a good practice to build in some sort of bad value checking when configuring analytics since source data can often suffer from digital states caused by a variety of interruptions.