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 User Experience
Created by Steve Edwards
Created on Aug 23, 2024

RELATED IDEAS

Elements are not always assets

Elements are not always assets but PIVIsion always calls elements, assets. (Ex. search criteria for template type. event frames have Reference Assets. But not all EF' come from assets. Can we keep the term element in PIVision instead of asset to align with PIAF and avoid confusion in UX. But could we then add a required attribute to each element that indicates its type [asset, accessory, container, etc...]

A common vocab avoids distracting UX with new terms,

This would reduce search string text entry for all users. And it encourages good architecture. The PI digital twin from PI Practice standards introduced element types [container, asst, Acc]

  • Attach files