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 Daniel Marlowe
Created on Aug 20, 2022

RELATED IDEAS

Retrieve an Attribute Reference from a String variable

Because some functions in PI AF Analytics require an attribute reference (instead of a tag number or tag value), it would be useful to be able to retrieve an attribute reference using a String variable. This functionality would allow dependent attributes to be referenced using the Concat() function. In the attached example, entering the parent attribute once is all that's required, as opposed to having three separate tag entries restating the hierarchy of attributes. While it is trivially easy to write this hierarchy out for one analytic, it gets cumbersome when you write a significant amount more.
  • ADMIN RESPONSE
    Aug 20, 2022
    Thank you very much for sharing your feedback on the PI Server. After further evaluation, we have decided to decline this item, as we are not planning on implementing it in the near future due to other high priority items across the PI System. Thank you for your feedback, and know that we are listening and reviewing every item that gets submitted!
  • Attach files
  • Guest
    Reply
    |     Aug 20, 2022
    This is problematic as you can have more than one AF attribute that is referencing the same PI Point within a given Element. In addition, if you use indirect reference within the configuration of a PI Point Data Reference attribute, this becomes even more confusing. On thing you might consider doing is if you only want to work with PI Point names, is to simply name your attribute the same as your PI Point name. In general we don't recommend this as you would then not be using your AF as effectively as possible.