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 185 of 5259

Write an error message to logs when no destination PI Data Archive is specified

Ran into this problem when configuring a new UFL connector. After install, I went straight to configuring my .ini--forgetting to add the PI Data Archive (in fact, the connector was actually installed on the DA node). I had the text files coming ...
Guest over 3 years ago in PI Connectors / General 0 No status

Make "Cancel" a button, not a link

In the configuration page of any data source, there is a "Save" button and a "Cancel" link. This is unnecessarily inconsistent. Please make "Cancel" a button.
Kenneth Barber over 3 years ago in PI Connectors / General 0 No status

Use units in the attribute templates of the element templates that PI Connectors create

Currently, all of the attribute templates of the element templates that PI Connectors create have their unit stated in their description but do not have a Default UOM assigned to them. Please assign Default UOMs to the attribute templates to save ...
Kenneth Barber over 3 years ago in PI Connectors / General 1 No status

Better error handling in DCM UI

For some cases where disallowed or poor configuration causes unexpected behavior, the UI should give a visual indicator and explanation.  Two examples: 1. No write access for Relay to AF DB when using the PSC.  Result: replication of AF ...
Brent Bregenzer over 3 years ago in PI Connectors / General 1 No status

OMF Support PI Connector Relay

Keep the OMF support in PI Connector Relay, also add the new OMF Versions to it not just only OMF 1.0. Not just leave the OMF support to the PI WebAPI. In many customer scenarios, the PI Connector relay is an easier solution than PI WebAPI.
Guest over 3 years ago in PI Connectors / General 0 Declined

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 3 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

Allow PI Adapter for MQTT to log the raw json payload received from the broker

For troubleshooting, it can be very helpful to see the raw json payload that the adapter has received from the broker, rather than just the error response from the attempted parsing. It can be difficult to know why a parsing attempt has failed wit...
Guest over 3 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 2 Future consideration

Expand PI Adapters to be installed on RedHat/CentOS

No description provided
Jessica Fegely over 3 years ago in AVEVA™ Adapters / General 4 Tell us more

Adapters using Text parser be able to dynamically generate the stream name or ID based on fields of the text parsed

This could be a good feature for any adapters that uses the text parser. MQTT, SDF, Azure Event Hubs. When using JsonPath or Xpath to parse a file or payload the stream name and stream id have to be hardcoded their value cannot be based on a the v...
Randy Giguere about 2 years ago in AVEVA™ Adapters / General 0 No status

Improve the message for performing on demand History Recovery on datacollectionmode: "CurrentWithBackfill" and "CurrentOnly"

Running edgecmd to perform HR on demand on the datasource: datacollectionmode of Non HistoryOnly. will return the following error: Operation Failed: NotFound (404)Unexpected error: Unexpected character encountered while parsing value: 0. path '", ...
Ee Sheing Lee over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status