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 Subscribe
Status No Status
Product Assets & Metadata Rules
Categories Metadata Rules
Created by Guest
Created on Mar 29, 2024

RELATED IDEAS

Improve Stream Meta Data rules

Some potential improvements to Stream Meta Data rules:

- Improve on how to 'filter' which streams are associated to a particular rule. One way this is possible today is by the use of the String Literal, but that then means I cannot use the same portion of Stream Name to build a meta data.

- Allow for 'hard-coded' meta data to be added, independent of a stream name 'portion'.

- Allow for use of both Stream Name or Stream ID to build meta data rules.

Overall, if a similar approach to Asset rules (Tokens) were used for stream meta data rules, many if not all these potential enhancements would be addressed as a consequence. Moreover, this would also simplify the user learning curve to build rules (Stream meta data or asset rules). As part of my role, I currently support the use of DataHub/Connected Data Services for different types of partners (including OEMs, machine builders, etc), these 2 functionalities are very powerful for their use cases, so aligning/improving on it would be a great selling point for these partners.

  • Attach files