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

    Rename services to reflect the renaming of the product

    AVEVA Adapters were previously called "PI Adapters", but the name of any AVEVA Adapter service begins with "PIAdapter". The PI To CONNECT Agent was previously called the "PI To Data Hub Agent", but the service name is still "PIToDataHubAgent". I'm...
    Kenneth Barber 2 months ago in AVEVA™ Adapters / General 0 No status

    Report Tuning Parameter changes in the PI Message Log

    Changes to Tuning Parameters should be reported in the PI Message Log with the identity of the user who made the change.
    kliffhopson 9 months ago in AVEVA™ PI Server / System Management 0 No status

    Wrap text option in value object

    The Value symbol, and others such as table, etc., that can display the value of an attribute do not allow for the value to be wrapped. For long string values this can result in a long horizal value that messes with the layout of a display. Having ...
    Mike Horrocks over 1 year ago in AVEVA™ PI Vision™ / Look & Feel / Styling 0 No status

    Row/variable information to AF Analysis errors

    When we built complex analysis and evaluate in PI System explorer we get general error messages without any information where the error occurs. This makes troubleshooting painful. Adding row/variable information would already help a lot!
    Philipp Even almost 2 years ago in AVEVA™ PI Server / Asset Framework (AF) 0 No status

    if then else in Analysis still checking/executing both parts

    If then else clauses are often used for input filtering for our analysis in AF. We often face the issue that analysis cause errors although the part which should not be executed according to the condition is causing errors.Example: "if BadVal('att...
    Philipp Even almost 2 years ago in AVEVA™ PI Server / Asset Framework (AF) 1 No status

    Classic Mode for Adapters

    One of the big issues we have with adapters (outside of the lack of write capability) is not having the same control over creating and editing tags that we have with PI interfaces. As we talked about the adapter automatically creates PI tags or us...
    Brian Rock over 3 years ago in AVEVA™ Adapters / General 5 Future consideration

    Add DATEADD and DATEDIFF functions to PI SQL Commander

    When any time related functions need to be performed against timestamp columns in PI SQL Commander, one needs to utilize a significant amount of conversions to make this work. For example, if one needs to round timestamps to the nearest minute or ...
    Guest about 4 years ago in AVEVA™ PI System Access (PSA) / PI OLEDB Enterprise 0 Declined

    PI SQL Client to make use of the RecordedValue method and Retrieval Modes for the GetValue transposed function

    When making use of the GetValue transposed function when creating a new Template specific Data Model, we can see that under the hood it makes us of the AF SDK call AFData.InterpolatedValue method to capture the data at a specified timestamp provid...
    Guest about 4 years ago in AVEVA™ PI System Access (PSA) / PI SQL Client 1 No status

    Add Annotations support for RTQP Engine

    I would like the RTQP Engine to be able to read annotations. My use case is the following : I have user that enter manual values into PI along with these values the operator will specify the reason for this manual input. The comment is stored in ...
    cvallee about 4 years ago in AVEVA™ PI System Access (PSA) / General 0 Declined

    21 CFR Part 11 Electronic Signatures for manual data entry

    Support 21 CFR Part 11 regulatory requirements for Electronic Signatures when manually entering data.
    Guest about 4 years ago in AVEVA™ PI Vision™ / Manual Data Entry 2 No status