AVEVA™ Data Hub Feedback Portal

Welcome to our new 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 Data Hub. For links to our other feedback portals, please see RESOURCES below.

ADD A NEW IDEA

All ideas

Showing 18

Stream-level debugging

As a PI System Administrator, I'd like to be able to trace values being received, and subsequently being sent by the Adapter, similar to PI Interfaces. Having the ability to trace/log timestamps and values for specific streams would greatly help ...
Guest over 1 year ago in PI Adapters / General 0 Future Consideration

Provide a streamlined way to rename streams and push the changes to the endpoint

The current process forces the user to modify the adapter configuration (DataSource for the prefix, DataSelection for the stream name) and the endpoint (PIDA, OCS). The adapter should support modifying directly the stream name and push those chang...
Guest over 1 year ago in PI Adapters / General 1 Future Consideration

Kerberos Authentication from EDS to PI

Submitting on behalf of a customer concerned about meeting stringent security requirements. Kerberos is a staple in their security architecture and the would very much like to incorporate it here.
Guest over 1 year ago in Edge Data Store / Egress 0 Future Consideration

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 1 year ago in PI Adapters / AVEVA Adapter for MQTT 2 Future Consideration

Do not bundle PI Adapters with EDS

Reduce the footprint of EDS by not bundling adapters with EDS but instead have them be a separate installation so only the desired adapters end up being installed on the device. It will also allow easier for a clearer process when an adapter needs...
Guest over 1 year ago in Edge Data Store / Installation 1 Future Consideration

Automate dataset selection for each PItoADH Agent

We would end up with more than 60+ PItoADH Agent to configure. We have a strong AF hierarchy across our sites and could perfectly prepare a unique AF rootpath to select the relevant dataset to push from PI/AF to ADH for each 60+ connections. Ideal...
Christian Leroux about 1 year ago in PI to Data Hub / General 1 Future Consideration

Accept HEX numbers for Register offsets in data selection

Most modbus equipment providers provide information using registers in Hex format i.e. 0x0000 ~ 0xFFFF. It would be nice if the offset could accept this to avoid error in conversions HEX to DEC. Would make things alot more seamless/easier.
Guest about 1 year ago in PI Adapters / AVEVA Adapter for Modbus TCP 0 Future Consideration

Allow multiple references to holding register for bit extraction

Given a 16bit integer holding register, in certain instances we only care for specific bits rather the integer value. Using the bitmap allows the selection of those specific bits but you can only reference the register once. i.e. In data selection...
Guest about 1 year ago in PI Adapters / AVEVA Adapter for Modbus TCP 3 Future Consideration