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 System Management
Created by Guest
Created on Aug 19, 2022

RELATED IDEAS

Provide "Point Last Accessed" information to determine clients' use of PI Points

It would be useful to be able to determine when (or even if) a PI Point was last accessed by a client application to retrieve its data.  This would enable redundant points to be identified and removed. Alternatively/additionally some form of access tracing such as used to be provided by the AAG tool would be useful to determine which clients access which points.
  • ADMIN RESPONSE
    Aug 19, 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 19, 2022
    An example of how I'd like to use it... We have some data that used to be scanned from an analog instrument and passed into PI. This instrument was specialized and expensive to maintain so we investigated calculating the data from simpler, cheaper instrument signals. We end up with two PI tags for comparing the data side by side. Some end users are probably using one point, some the other. We can't tell and they are not savvy enough to be able to tell us! So we point both tags at the new calculated data and forget it. However, it would be nice to be able to determine which users are actually using which point, get the minority to use the majority's point and delete the now unused one.
  • Kenneth Barber
    Reply
    |     Aug 19, 2022
    More context can be found here: https://pisquare.osisoft.com/thread/34116-pi-point-access-tracing I can see some use for a feature like this. Not so much for eliminating redundant tags, but more for eliminating unused tags.