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 Declined
Product AVEVA™ PI Server
Categories Analytics & Calculations
Created by Guest
Created on Aug 20, 2022

RELATED IDEAS

Sampled Data with Analysis Data Reference

Customer would like to have Sampled Data with Analysis Data Reference (periodic values output) without creating tags as output for the Analysis.
  • ADMIN RESPONSE
    Aug 20, 2022
    Like all data references in AF, Analysis Data Reference executes on demand by the client. As such, the idea of a periodic output does not agree with the design as there is no scheduler. Similarly, since the "trigger" is by the client, the idea of triggering inputs doesn't agree with the design. We currently have no plans to change this design.
  • Attach files
  • MAl
    Reply
    |     Aug 20, 2022
    Even the ability of selecting a subset of inputs as event-triggered attributes of the Analysis would be useful. Today all inputs participate in triggering the Analysis where the output Attribute is not a PI Point data reference.
  • FranzK
    Reply
    |     Aug 20, 2022
    I agree with MAI, at least there should be the ability to influence what inputs trigger the analysis. In our use case we use an attribute with Point Data Reference. This attribute is showing if we are in a defined process step. if this is the case, we write the value of an attribute with Table Data Reference (linked table, as this value might be changed later) to our output. as the value of the linked table might change, we don't use a point data reference as output. our use case is similar to what you explain in KB01586. There you write "•Their results are not stored, so the result will always use the most up-to-date process data even if the source data is changed later"