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 205 of 5258

    Set the order of the root import folders when more than one root folder is defined

    Customer Issue: Import folders are listed in the order they are added which makes it difficult to sort them if more folders need to be included later. Enhancement Request: Allow administrators to set the import folder order. Workaround: If pos...
    Guest over 3 years ago in AVEVA™ PI Vision™ / Administration 0 Declined

    Server maintenance banner to be displayed across all displays

    Have the ability to enable a maintenance banner across all displays. This would allow admins to inform separate user groups that have business critical displays that remain always on to expect a necessary browser refresh to clear "Error: Internal ...
    Mario_B over 3 years ago in AVEVA™ PI Vision™ / Administration 0 No status

    Datalink Search menu not intuitive

    The Search menu in PI Datalink 2016 is confusing for users used to PI Tag searches elsewhere in the PI System. "In a row" and "In a column" are particularly confusing, as they suggest that searches are being performed within the row or column. Thi...
    Guest over 3 years ago in AVEVA™ PI DataLink™ / Search 0 Declined

    Include information from Json body in the stream name created by the MQTT Adapter

    As a system admin I would like to send mqtt messages from multiple devices to a single topic on an mqtt broker. Each message would contain data for the device along with a field to say which device the data has come from. Then I would like to use ...
    Guest over 3 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

    Allow PI Adapter for MQTT to log the raw json payload received from the broker

    For troubleshooting, it can be very helpful to see the raw json payload that the adapter has received from the broker, rather than just the error response from the attempted parsing. It can be difficult to know why a parsing attempt has failed wit...
    Guest over 3 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 2 Future consideration

    Expand PI Adapters to be installed on RedHat/CentOS

    No description provided
    Jessica Fegely over 3 years ago in AVEVA™ Adapters / General 4 Tell us more

    Self-Heal PI Vision post-SQL outage

    When the SQL Server (or listener / AG) are unavailable and restored, PI Vision does not recognize that the database is available / connectable again. This requires restarting PI Vision after a SQL outage to ensure the application is usable again. ...
    Tyler Engelhardt about 2 years ago in AVEVA™ PI Vision™ / Administration 0 No status

    Detailed Display Status Report

    When building displays with a large number of attributes being used it is very easy to make mistakes. Applying the wrong tag, or duplicating tags, is very easy to do but hard to troubleshoot. ProcessBook had a display status report. It is similar ...
    Brian Bolton almost 3 years ago in AVEVA™ PI Vision™ / Administration 1 No status

    Adapters using Text parser be able to dynamically generate the stream name or ID based on fields of the text parsed

    This could be a good feature for any adapters that uses the text parser. MQTT, SDF, Azure Event Hubs. When using JsonPath or Xpath to parse a file or payload the stream name and stream id have to be hardcoded their value cannot be based on a the v...
    Randy Giguere about 2 years ago in AVEVA™ Adapters / General 0 No status

    Improve the message for performing on demand History Recovery on datacollectionmode: "CurrentWithBackfill" and "CurrentOnly"

    Running edgecmd to perform HR on demand on the datasource: datacollectionmode of Non HistoryOnly. will return the following error: Operation Failed: NotFound (404)Unexpected error: Unexpected character encountered while parsing value: 0. path '", ...
    Ee Sheing Lee over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status