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 54 of 5194

setting the number of  a single account's Multiple concurrent login

The administrator should have permit to set the number of  a single account's Multiple concurrent login.Now my account can login on multiple terminals at the same time without limit.
Guest over 3 years ago in AVEVA™ PI Vision™ / Security 0 Declined

Restrict view of Events details after double-clicking on an Event frame in an Events table

As a PI Vision administrator, I would like to restrict or disable access to view Events details after double-clicking on an Event frame in an Events table on a PI Vision display for specific PI Vision users
Guest over 3 years ago in AVEVA™ PI Vision™ / Security 0 Declined

PI Vision support for OAuth 2.1

PI Vision's current CTP claims implementation is based off of OAuth 2.0. With OAuth 2.1 coming out PI Vision's claims implementation will need to be revised to be compliant with the new version of the framework. Specifically OAuth 2.1 is removing ...
Guest over 3 years ago in AVEVA™ PI Vision™ / Security 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 the number of login failures

Lock the account when entering wrong password 5 times
Guest over 3 years ago in AVEVA™ PI Vision™ / Security 0 Declined

Address the warnings given by the "Developer tools" of Microsoft Edge

PI Vision gives many warnings in the "Developer tools" of Microsoft Edge. There are too many to list here. Please check the "Developer tools" for multiple pages within PI Vision and fix any issues that Microsoft Edge reports to ensure that best pr...
Kenneth Barber over 3 years ago in AVEVA™ PI Vision™ / Security 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

Customer is seeking WW connector to collect data from WW historian but with same naming convention of existing tags

Customer is seeking WW connector to collect data from WW historian but with same naming convention of existing tags. Existing tags were reading from "FxBias interfaces" and in need to let them read from WW historian thru WW connector. WW connect...
Guest over 3 years ago in PI Connectors / PI Connector for Wonderware Historian 1 No status

Optionally not include Galaxy name

Add capability to include Galaxy name or not and include specific areas or not. In the current system I am working with, the primary and backup WW Galaxies are named differently. This causes the Connector to build separate trees in AF.
Guest over 3 years ago in PI Connectors / PI Connector for Wonderware Historian 0 No status