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 30 of 3183

    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

    PI Interface for OPC UA

    While it is understood that adapters are the future of data source connectivity; there is an immediate need for existing PI system users (especially in the Chemical industry) to transition their data sources from using OPC DA to OPC UA. Many of th...
    Brian Rock over 2 years ago in PI Interfaces / General 3 No status

    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

    PI BACnet interface doesn't say which PI point caused the device to return Error 31

    For the PI BACnet interface, the following error can be returned from the device for a particular request and then written into the message logs: " >> BACnet error packet received. Error Code: 31; Error Desc: Unknown Object; InvokeID: 0" H...
    Guest over 3 years ago in PI Interfaces / General 0 Completed

    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

    Add an option to receive real-time data in client during buffer recovery

    Add an option to receive real-time data in the client during recovery of buffered data: The default behaviour of our interfaces / buffering is that after a connection failure the buffer will be flushed and data will be sent in it’s original order...
    Guest over 3 years ago in PI Interfaces / General 5 No status

    Allow PItoPI APS connector to sync "Point Type" changes

    Currently (as of PI to PI Interface AutoPointSync Connector Version 1.5.0.7), it's not possible to sync changes to "Point type". (See pg 5 of user manual). Please make this possible in a future release.
    Guest over 3 years ago in PI Interfaces / General 0 Declined

    PI OPCtoCSV tool to continue running and skip branches in error

    The PI Interface for OPC DA is packaged with the PI OPCtoCSV tool which extracts all OPC Items. When the tool is run into error with certain branches, the tool will stop and disconnected from the OPC server/tunneller. For example: “GetItemProperti...
    Ee Sheing Lee over 3 years ago in PI Interfaces / General 1 Declined

    Uni-Int to write to scan-class health tags on startup

    We've noticed this particularly with the RDBMS-PI interface when configured for failover: Health tags that are only written to when the interface becomes primary or has completed its first scan (eg Point Count, Scan Class I/O Rate etc.) say 'Intf ...
    Guest over 3 years ago in PI Interfaces / General 0 No status

    Separate commonly used PI Interfaces that do not have a successor into read-only and write-only versions

    Currently, it is recommended to use the read-only version of a PI Interface if only reading is required, and to have separate read and write instances of the read-write version of a PI Interface if writing is required. (Reference: https://docs.osi...
    Kenneth Barber over 3 years ago in PI Interfaces / General 1 No status