Skip to Main Content
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

Showing 64 of 5222

PI Connector for Wonderware to be able to detect dll files in other drives other than C drive

Had a customer that just installed PI Connector for wonderware of current version (v1.6.9.14) and his connector is unable to start. Upon discussion after troubleshooting, it was noted that the directory where dll files can be located on customer's...
Chaur Ann Poh over 2 years ago in PI Connectors / PI Connector for Wonderware Historian 0 No status

AVEVA Adapter for WITSML

We need an Adapter for WITSML to get data from drilling, completions, and interventions of oil wells to CONNECT data services, so the data can be shared between multiple stakeholders.
Guest over 1 year ago in AVEVA™ Adapters / New Connectivity 0 No status

CONNECT Agent for AVEVA Plant SCADA (Citect)

AVEVA Plant SCADA 2020r2 and newer, has an OPC UA Server, so the AVEVA Adaptor for OPC UA can be used to send data to CONNECT data services (AVEVA Data Hub). However native connectivity like the PI-to-CONNECT Agent or the System Platform Connector...
Guest over 1 year ago in AVEVA™ Adapters / New Connectivity 0 No status

Disable Meta data collection for the PI Connector for Wonderware Historian

We would like to have a way to disable the PI Connector for Wonderware Historian's ability to  collect descriptions and engineering units in the historian.  These can be incorrect at times in the Wonderware Historian.
Guest over 3 years ago in PI Connectors / PI Connector for Wonderware Historian 1 No status

PI Connector for Cygnet - Historical Data Recovery

The PI Connector for Cygnet is normally used for real-time data acquisition. But, some times it becomes necessary to migrate large volumes of historical data between Cygnet and PI. There is a back filling application that can be used to do this, ...
Guest over 3 years ago in PI Connectors / PI Connector for Wonderware Historian 0 No status

Limit IP ranges on nodes

As a PI Cloud Connect user, I would like to screen receiving Vendors via their account, but by also by limiting connections to a specific IP or IP range for connections.
Guest over 3 years ago in PI Cloud Connect 0 No status

PICC Admin Portal Log Availability

It would be useful for the PI Cloud Connect (PICC) portal to include logs related to user activity on the portal such as subscriptions, users, or publications added or removed. The current logs are local and service specific. An enhancement of PIC...
Guest over 3 years ago in PI Cloud Connect 0 No status

Identify a subscription's name from its GUID

- When PI Cloud Connect (from subscriber end) create PI tags on a destination PI server, the exDesc of those tags show the GUID of the subscription that owns it. But there's no built-in way to identity the subscription's name based on the GUID. -...
Guest over 3 years ago in PI Cloud Connect 0 No status

Use Wonderware tags MinimumEUValue and MaximumEUValue to configure AF attributes limits/traits

In addition to historian tags, the PI Connector for Wonderware Historian collects many metadata (see attached screen shot about a tank). Part of these are MinimumEUValue MaximumEUValue It could be really worth if connector could come with...
David_CHATEL almost 3 years ago in PI Connectors / PI Connector for Wonderware Historian 0 No status

Allow PICC to use the PI Server name with the Point Id# to stop conflicting data streams when multiple PI servers are combined in a PIAF structure

Currently only the point id is used in PICC to track data streams. This is not an issue a single PI server data source. With PIAF multiple PI servers are used to collect data stream. We are now seeing data streams being overwritten by multiple PI ...
TimS about 3 years ago in PI Cloud Connect / General 0 No status