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

Search results

    Showing 15 of 3182

    Send CONNECT data services (Data Hub) stream data to PI System

    The ability to collect data directly into CONNECT data service (Data Hub) but then route some data back to on premises PI Systems for merging with that data.
    Guest over 3 years ago in CONNECT to PI 13 Completed

    Compression on CONNECT to PI related tags

    The tags use the default compression settings since they are automagically created through PI WebAPI if CONNECT to PI agent starts sending the transfer. This can mean that there is another compression applied to the tags. But as we are already cop...
    Hans-Otto Weinhold 10 months ago in CONNECT to PI 0 No status

    Specify stream properties in a CONNECT to PI transfer

    Include a way to select (or filter out) different properties of a stream used in a CONNECT to PI transfer so that we can control the PI tag/s created.
    Guest 8 months ago in CONNECT to PI 0 No status

    Log bad timestamps for the PI RDBMS Interface

    When the PI RDBMS Interface gets a bad timestamp from the source RDB that it cannot coerce into a PI Timestamp, the actual bad timestamp received from the RDB should be logged as part of the error message. This would coincide with the following e...
    Guest over 3 years ago in PI Interfaces / PI Interface for RDBMS 0 Future consideration

    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

    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

    Alert user when the interface discards values

    Example:  When using a distribution tag, the number of tags returned and number of values sent to PI can be mismatched, due to missing aliases or data that does not need to be collected. It would be helpful to identify what values are droppe...
    Guest over 3 years ago in PI Interfaces / PI Interface for RDBMS 0 No status

    RDBMS time stamp precision

    Currently the ODBC connection is configured with a SQL date time parameter when retrieving the TS parameter (snapshot time stamp). Due to the fact lots of sources system having more precision in their time stamps, it makes it hard to compair sourc...
    meierke1 over 3 years ago in PI Interfaces / PI Interface for RDBMS 0 No status

    Add option to select interface behavior for bad timestamps (PI RDBMS)

    When the PI RDBMS Interface gets a bad timestamp from the source RDB that it cannot coerce into a PI Timestamp, the interface attempts to use the current timestamp instead and logs the following error: "pitm_settime() error - 15002. Using current...
    Guest over 3 years ago in PI Interfaces / PI Interface for RDBMS 0 No status

    Accept weeks and years in the relative time syntax for history recovery start and end times

    For whatever reason, times such as *-1w or *-1y are not accepted, but times such as *-1mo and *-1d are OK. Please make the PI Interface for RDBMS accept the same relative times that other PI programs accept.
    Kenneth Barber over 3 years ago in PI Interfaces / PI Interface for RDBMS 0 No status