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 59

Fully support local viewing and storage of health and diagnostics streams and assets in EDS

Currently, the health and diagnostics streams for EDS are only viewable at the configured health endpoint such as CDS, or PI System. However, it would be useful for the exact same streams and assets that would be created on those remote endpoints ...
Jason Lu about 2 months ago in Edge Data Store / General 0 No status

Control which PI/AF servers each data source sends data to.

Right now, for one instance of the connector, all configured data sources will send data to all configured PI Data Archives and PI AF Servers. It is all or nothing. Due to the fact that you cannot have multiple instances of the same connector on a...
Guest over 3 years ago in PI Connectors / General 0 No status

Update DataCollectorHealth and StorageHealth Asset type

EDS is pushing at least 2 Health assets (StorageHealth & DataCollectorHealth) with DeviceStatus stream but this stream is not inside the asset type as streamReference. So we are not able to use this stream to map into the Asset Status. Asset S...
Guest 4 months ago in Edge Data Store / General 0 No status

Ability for PI Connectors to create future data point

Add the ability for PI Connectors to create future data point. This is especially useful for the PI Connector for UFL. The current workaround is to manually create the point as a StoredValues=FutureData.
Gabriel Verreault over 3 years ago in PI Connectors / General 0 No status

PI Connector Relay support write modes

While writing data to PI through the connector relay there seems to be no option to control the write mode . E.g."[-109] Value at This Time Already Exists" is shown in the logs if the archive already contains an event with the same timestamp. The ...
Guest over 3 years ago in PI Connectors / General 2 No status

Option to remove/edit template prefix

Allow for connectors to create templates without the fixed prefix. E.g. The option to name an AF template "templatename" and not "UFL.templatename"
Guest over 3 years ago in PI Connectors / General 0 No status

Have option to enable exception on Connectors.

There are use cases where data is sent over networks with latency (satellite link, for example) so being able to filter out noise at the connector is important.  This is also important when a connector sends data to a local PI Server in the f...
Brent Bregenzer over 3 years ago in PI Connectors / General 5 No status

Enable Relay/DCM to allow control over the data streams and destination PI Systems

Currently the Relay will send all data streams to all routed destination. This does not allow customers to have control over what data streams go to a specific destination. The only workaround is to have independent Connector/Relay pairs with spec...
Nico Cha over 3 years ago in PI Connectors / General 1 No status

PI Connectors buffering (Tau) - provide configuration options

As a PI Administrator, I would like to be able to DISABLE or configure Tau buffering SO THAT after a network outage the flood of data doesnt overload my network switch and PI DA. My current use case doesn't require the data that may be lost during...
Guest over 3 years ago in PI Connectors / General 0 No status

Allow the AF root element name to be configurable

The root element in AF is determined by the Connector code.  Allow the name of the root element to be specified by the user.
Clint Ramsey over 3 years ago in PI Connectors / General 4 No status