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

AVEVA™ Adapters

Showing 91

Allow PI Adapter for MQTT (Generic) to process non-json payloads

Some MQTT devices do not send json payloads; for example, some devices send a single value as the payload for a specific topic. It would be beneficial for the adapter to be able to handle this rather than to convert these payloads into json befo...
Guest over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 3 Tell us more

PI Adapter for OPC UA Array Support

As a PI System Administrator, I would like for the PI Adapter for OPC UA to support array data types from the OPC UA Server. A large amount of our data may be contained within arrays on our OPC UA Server, so we would not currently be able to colle...
Guest over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 6 No status

Please add a feature for the OPC UA adapter to enable the adapter to only store values with a good status or rather filtering out bad values

When receiving bad values from the OPC UA Server to the adapter there is no option to filter out bad values. So these values get stored in the Data Archive and are causing problems with analyses (e.g. expression or Event Frame generation). At the ...
Timur Eroglu 9 months ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

Sampling/Publishing Interval parameters to be part of Data Selection description

When configuring the AVEVA Adapters in general, we would find more convenient to be able to define the ‘Sampling Interval’ and 'Publishing Interval' parameters inside the ‘Data Selection’ configuration per each data stream. For instance, when desc...
Christian Leroux over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

Enable OmfEgress component to be configurable by instance (by component)

In our process we wish to send a different set of data to different PI environments. For instance we would like all data to egress to the PROD environment while only egress a subset of data to the DEV environment, in which we don't need all the da...
Guest over 2 years ago in AVEVA™ Adapters / General 2 Future consideration

PI Adapter for AspenTech IP21

We have customers who are using AspenTech IP 21 and would like to have data replicated in both PI DataArchive and OCS in the future. Since the PI Interface is a bit outdated, a new PI Adapter would make perfect sense (since there is already a PI C...
Guest over 2 years ago in AVEVA™ Adapters / New Connectivity 4 Tell us more

PI Adapter for OPC UA should preiodically retry to subscribe to each node for which subscription failed at startup

Currently the PI Adapter for OPC UA tries to subscribe to all the OPC UA nodes configured in the Data Selection configuration at startup. However, when as issue occurs during the subscription to an OPC UA node, that node will not be included in da...
Bernard Lafrance 9 months ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

Allow the PI Point description to not be populated by the adapter

Implement a configuration flag that allows one to NOT synchronize description from OPC UA server into PI Tag. In instances where the description is empty "", the description cannot be set in PI. Similarly, the description on the OPC UA Server sid...
Gabriel Verreault over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 3 No status

displayname/localname for identifier that excludes namespace and data type

Example: OPC UA Server 'Name': 2.0:W-HVAC-AC-1-IO!Wtot Namespace: 2 Datatype: 0 Identifier: W-HVAC-AC-1-IO!Wtot OPC UA Server 'DisplayName': W-HVAC-AC-1-IO!Wtot OPC UA Adapter {Identifier} returns: 2.0:W-HVAC-AC-1-IO!Wtot Required stream name: W-H...
Guest 4 months ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

option to not collect quality

Quality is not supported by the OPC UA Server/always zero.
Guest 4 months ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status