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 Vision™
Categories AF Integration
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

View data across AF Element Versions

Handle the ability to trend data from attributes across AF Element Versions.  For example, when old sensors have been replaced with a new control system, new tags are created and customers use AF Element Versions to manage the mapping between the old and new tags.  Users would like to use and visualize data across this versioning time point.
  • Attach files
  • mduncanAnglo
    Reply
    |     Sep 11, 2023

    Where do need this trend of versioned attributes be fixed/applied?
    It works with PI System Explorer trending if the Element is not configured with a template (But it doesn't work in PIVision. PiVision works only if the timeperiod for the display is entirely inside one Version time-period. If the timeperiod crosses a version boundary, then PIVision just shows data for attributes for the first version)

    PI System Explorer trending doesn't work if the element is configured with a Template.
    Versioning for AF Elements should work in all of these situations:
    PIvision, PI System Explorer Time-series-data trend, Trend, PI WebApi , PI RTQP/OLEDB,
    With an Element without a template in both Version1 and version2.
    With an Element without a template in Version1, and with a Template in Version 2
    With an element with a template in Version1 and without a template in Version2.
    With a template A in Version 1 and templateB in Version2.


  • jsaenz210
    Reply
    |     Aug 19, 2022
    Todd, I really like this use case. I would love to see this ability brought online by OSIsoft. The ability to trend an attribute from an element with different versions would be very useful for reviewing asset performance where service life is decades long. During that time, there could be many changes to not only the asset itself, but process conditions upstream and downstream. The ability to conveniently trend/analyze that data would be very powerful from a maintenance and integrity perspective. It would also enable much more accurate forecasted values and machine learning applications.