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

AVEVA™ Adapters

Showing 59

Permit non-protected references

The secrets references is a very useful addition but they are only permitted for "protected" parameters. It would be useful to also create references for non-protected parameters. Using references for non-protected parameters would help with creat...
Mike Horrocks over 1 year ago in AVEVA™ Adapters / General 0 No status

Expand Healthpoint (Device Status) Information of the PI Adapter for Modbus TCP from Component to "Device" Level

When configuring PI Modbus TCP adapter you first define a component level and under this type you define your different devices/machines/sensors. In case of a broken connection to one of the devices the healthpoints currently only deliver the stat...
Mario Amrhein 12 months ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 No status

Allow restricting access to the Adapter to only allow configuration by specific users

We want to make sure that we have more control over who can update an Adapter. Is there a way to add a login or other restriction to only permit certain users to be able to modify Adapters, similar to how, with PI Connectors, only specific Windows...
Daniel Lopez about 1 year ago in AVEVA™ Adapters / General 1 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 6 months ago in AVEVA™ Adapters / New Connectivity 0 No status

Include information from Json body in the stream name created by the MQTT Adapter

As a system admin I would like to send mqtt messages from multiple devices to a single topic on an mqtt broker. Each message would contain data for the device along with a field to say which device the data has come from. Then I would like to use ...
Guest over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

Support for "RTU over TCP" for Modbus Adapter using MBAP header

Challenge: Today, the PI Adapter for Modbus TCP does not natively support " RTU over TCP". It does support Modbus TCP, so as long as the "bridge" properly converts Modbus RTU to Modbus TCP (including the MBAP header), it should work fine. If the b...
Hans-Otto Weinhold about 1 year ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 No status

Provide possibility to create stream metadata from table data

Today we are collecting data from our AspenTech IP21 Server thorugh the PI Adapter for OPC UA and the related AspenTech OPC UA Server. This works perfectly fine for analogue data but not for data which is providing us equipment status information ...
Hans-Otto Weinhold about 1 year ago in AVEVA™ Adapters / AVEVA Adapter for RDBMS 0 No status

Better support of IP21 OPC UA Server with PI Adapter for OPC UA

We have been using the PI Adapter for OPC UA in its current version to collect data from IP21 OPC UA Server during a lighthouse project. However, the configuration was a bit cumbersome since the OPC UA Server of AspenTech uses an opaque mechanism ...
Hans-Otto Weinhold over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

Include [optional] unit of measure in the data selection configuration.

Some data sources do not provide a unit of measure. It would be useful to be able to specify the unit of measure as part of the data configuration so that this information is provided to EDS/PI/ADH through the data flow.
Mike Horrocks 8 months ago in AVEVA™ Adapters / General 0 No status

Allow the BACnet Adapter to handle responses with an LVT that does not match the request

Currently the BACnet Adapter expects devices to respond with the same "Length Value, and Type" (LVT) value as the request. When this occurs the BACnet Adapter cannot parse the data in the response. For example: Request from Adapter, LVT=1 Response...
Nico Cha 8 months ago in AVEVA™ Adapters / AVEVA Adapter for BACnet 0 No status