AVEVA™ PI System™ Feedback Portal

Welcome to our 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 No status
Product AVEVA™ PI Server
Categories Asset Framework (AF)
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

Option to write Default Value to PI tags created through AF Templates

When creating PI points through AF Templates, there should be an option to "Write Default Value after Point Creation", or some other way to initialize the value of an automatically created PI tag. Right now, there is no way to replace the Pt Created value with a default value upon creation, and the "Default Value" in the AF Template serves no real purpose for PI Point Data References.
  • Attach files
  • Guest
    Reply
    |     Aug 19, 2022
    Since these are PI Points, we tend to consider them to be time series data. Is that true in this situation or is the data fundamentally different? Ideally, where would these default values come from?
  • Nathan Skitt
    Reply
    |     Aug 19, 2022
    This would be beneficial for a template I just created that is a counter. I needed to initialize the PI Point on the PI Data Archive, but if this functionality was there AF would be able to perform the entire procedure.
  • Guest
    Reply
    |     Aug 19, 2022
    The described use case for calculations make sense. At the same time, there are other considerations. When a point is created, Pt. Created accurately represents the initial condition. Typically with a PI Point, it's important to have traceability when values are written to the PI Point. For a PI Point receiving values from a data source, like a control system, we definitely don't want to inject in a default value since you would have no traceability. In the case of a Lab value, we have the same situation. In the case of a PI Point used exclusively for calculation, within the boundary of AF, when a PI Point is created from template and you need a value for calculations, would it make more sense to embed the logic into the calculations rather than artificially inject a value into the PI Point?