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.
The AF dependency for PI Web API warrants serious reconsideration from an architectural standpoint. Requiring a full AF Server and an associated SQL Server instance solely to support PI Web API configuration introduces a heavyweight, stateful infrastructure component into what should be a lightweight, stateless REST interface.
The dependency also complicates edge and hybrid deployments. PI Adapters rely on the PI Web API to communicate back to the PI system. However, the requirement to maintain AF + SQL as a prerequisite means that even minimal edge deployments must maintain connectivity to centralized, stateful infrastructure. This is fundamentally misaligned with edge computing principles, where services must be deployable in isolated, resource‑constrained, or intermittently connected environments.
The AF requirement introduces:
Unnecessary statefulness into a service that should be stateless
Tight coupling between PI Web API and AF schema/SQL persistence layers
Increased operational complexity, including patching, backups, failover, and lifecycle management of SQL + AF
Higher infrastructure cost, even for small‑scale or read‑only PI Web API use cases
A flat‑file configuration store, embedded database, or pluggable configuration provider would eliminate these constraints and align PI Web API with modern edge‑native design patterns.