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

Clear

Ideas

    Showing 20

    Improve the Agent instance naming UI to clearly display character requirements and the 15-character limit.

    When configuring a CONNECT to PI Agent instance, entering an invalid name results in the message "Field does not fit the character requirements." However, the UI does not specify what the valid character rules are or which character(s) the user ha...
    Guest 6 months ago in CONNECT to PI 0 No status

    Add the capability to create striplines on the trends.

    Having the capability to add striplines to the trend feature could help indicate events that occur on the trends. For example, this could help identify what step or part of a process a batch is in when reading a temperature trend to help induce wh...
    Guest almost 2 years ago in AVEVA™ RtReports / Editor 0 No status

    pop-up to confirm the end of Approval cycle

    It woul be useful to have a pop-up confirming that the approval cycle is properly completed.
    Monica Rattaggi GSK almost 2 years ago in AVEVA™ RtReports / Generator 0 No status

    Ban Russian industries using PI

    Call for AEVA to exit Russian market immediately of obvious reasons, cancel product license and prevent existing users from accessing application. It is confirmed that PI still actively used on Yamal LNG, Arctic LNG2, Sakhalin LNG sites.
    Evgeny Fedorov over 1 year ago in CONNECT to PI 0 No status

    Default batch search terms for all users when they log into the website

    Default filter for all users every time they log into the application. The RtReports generator search page requires a user to enter the filter every time they log into the application. This is especially burdensome as the users are logged out afte...
    Guest over 3 years ago in AVEVA™ RtReports 1 No status

    Modify default parameters for RtReports Generator

    Allow values to be passed into the RtReports Generator URL in order to modify the default Start Time, End Time, BatchID and other parameters.
    Guest over 3 years ago in AVEVA™ RtReports 1 No status

    Have both default PI Data Archive and Asset Framework Server load in generator

    Some customers are using the same RtReports Server to connect to both PI Data Archives (for batches) and Asset Framework Servers (for Event Frames) since they are using both at the same time. They'd like to be able to store both DA and AF/Database...
    Alan Izar over 3 years ago in AVEVA™ RtReports 1 No status

    Parse String Tag Using an AF Attribute as a Filter

    Following the "Parse String Tag Using an AF Attribute as a Filter" KCS is a very complex setup to filter Strings based on AF Attribute values. We would like to see the filter functionality enhanced to allow filtering based on an AF Attribute Valu...
    Guest over 3 years ago in AVEVA™ RtReports 0 No status

    Including the name of the report parameter used in the print-out PDF's file name

    It would be much easier to browse the output print-out PDF files from the RTreports generator if the file's name includes the report paramater under which the report was generated. At the time being, the report only includes a unique GUID for each...
    Guest over 3 years ago in AVEVA™ RtReports 0 No status

    RTReports - cannot handle Unit/Asset filtering when timebased - this is a 'bug'

    RTReports - cannot handle Unit/Asset filtering when timebased - this is clearly a 'bug'. Workaround are to use MDB !!! not - good!!. Please asap make a patch adressing this in RtReports.
    Guest over 3 years ago in AVEVA™ RtReports 0 No status