Data services feedback portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about CONNECT products and services. All of the feedback you share here is monitored and reviewed by the CONNECT 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 CONNECT data services. For links to our other feedback portals, please see RESOURCES below.

ADD A NEW IDEA

Clear

Ideas

Showing 43 of 693

Multi Language Support for Attributes

As someone who needs to create displays and other 'artifacts' from context, I need to be able to use different names for Attributes depending on the language of the user SO THAT I don't need to build multiple displays for each language.
Guest about 3 years ago in Assets & Metadata Rules / Assets 2 No status

Table Lookup in OCS Context / Assets

Support Table Lookup functionality in OCS Context, similar to AF where the meaning of a value (Code 7) is deciphered via a lookup table. Support Table Lookup functionality in AF to OCS.
Guest about 3 years ago in Assets & Metadata Rules / Assets 0 No status

versioning/version control to enable

Customer was making changes and wanted to save the previous version in case the updates were not what they wanted/error.
Glenn Moffett 11 months ago in Assets & Metadata Rules / Asset Rules 0 No status

More control on MQTT parameters on the AVEVA Adapter for MQTT

It would be nice to have more control on additional MQTT parameters for the AVEVA Adapter for MQTT. We are especially interested in having control on the QoS of the subscription. Setting this would give us more control in buffering, especially whe...
Guest 11 months ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

Global Context Library & Mapping

Ability to define a global library of asset templates and assets and then map site data structures into it SO THAT we can standardize easier across sites when the underlying systems and equipment structures are different (and focused more on autom...
Guest about 3 years ago in Assets & Metadata Rules / Assets 2 No status

Allow MQTT adapter to parse timestamps in local time without specifying a timezone suffix to each timestamp

We would like the MQTT Adapter to be able to interpret timestamps in local time without needing to explicitly state the timezone or UTC offset in each timestamp, but for the adapter to always interpret the timestamps as being in a specific timezon...
Guest about 3 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

Create stream metadata and asset rules across namespaces

Challenge: We have split our AVEVA Data Hub tenant across different namespaces as of data residency requirements. However, the naming conventions of our tags across the company has been standardized. We would like now to use stream metadata and as...
Guest over 1 year ago in Assets & Metadata Rules / Metadata Rules 0 No status

Asset Hierarchy that changes over time

Be able to specify hierarchical parent/child relationships between assets that also support these relationships changing over time for mobile Assets that get deployed to different locations.
Guest about 3 years ago in Assets & Metadata Rules / Assets 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 about 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 about 3 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 2 Future consideration