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

RELATED IDEAS

Ability to track source of AF created PI tag to it's origin (dB/element/attribute/analysis)

I have thousands of tags based on AF analysis, both auto created by AF and some which have been converted from ACE, PE, Totalizers to AF. Looking at the tags in Point Builder, DataLink, or SMT I am able to tell by Point Source that the tag is calculated in AF.  But where?  We use a single AF database for our SCADA, AMI, and Generation groups so browsing for an analysis is quite time consuming. It would be nice to have a PI Tag attribute that would show the "path" to the analysis.  \\Database\Element\Child\Child\Attribute\Analysis and that this information could easily be discovered in all management and analysis tools (DataLink, Builder, SMT...)
  • ADMIN RESPONSE
    Aug 20, 2022
    This is currently possible by using the appropriate substitution parameters when creating output PI Points for your analyses. Please reach out to tech support and they can help you.
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    Thanks for your idea. I understand what you're looking for in terms of a solution, I would be leaning towards not adding an PI Point attribute. If we were to do that, it would increase the size of the database as this would affect all PI Points affecting overall performance. In addition, the impact to backwards compatibility for clients would be unknown and would require a good amount of testing. Having said that, as I mentioned earlier, I understand your needs (thank you for the clear explanation), we'll look at what we can do to help you and others with similar needs.