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.
The inability for PI Web API OMF to send data to multiple PI Systems is a significant limitation in both PI Adapters and PI Web API. To address this, either:
The PI Adapter egress configuration should allow specifying the target PI Server or collective, or
PI Web API should provide a dedicated OMF endpoint for each configured PI System.
The expected workflow is that multiple edge adapters could send data to a single PI Web API instance, which would then route the data to the appropriate downstream PI System.
Currently, each PI Adapter requires its own dedicated PI Web API instance, creating unnecessary complexity and infrastructure overhead. This limitation is a critical blocker for migrating from PI Interfaces to PI Adapters.