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 160 of 711

    Allow default settings (eg. disable compression) for tags created by Adapters

    We would like to be able to specify default settings for tags created by the adapters. This would include things such as disabling compression for tags on this adapter (without disabling it as the default for all new tags on the Data Archive). Thi...
    Guest over 3 years ago in AVEVA™ Adapters / General 0 No status

    Adapter for RDBMS to support multiple rows with same "Timestamp" colum as IndexColumn

    As of version 1.x, with the IndexColumn being specified in the dataselection, the Adapter will require that each row in the source Database to have its own unique timestamp. If there are multiple rows with the same timestamp, first value with the ...
    Guest over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for RDBMS 1 Tell us more

    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 2 years ago in AVEVA™ Adapters / General 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 almost 2 years ago in Assets & Metadata Rules / Metadata Rules 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 '", ...
    Guest over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

    Equipment Benchmarking

    The ability to configure a peer group of similar equipment based on properties of the equipment SO THAT equipment KPIs can be benchmarked across multiple customers (and data shared anonymously). For example, a peer group might be all GE7FA gas t...
    Guest over 3 years ago in General / AVEVA Data Hub Scenarios 0 No status

    Scenarios for Stream Multiple Index

    Use this idea to tell us about your scenarios for OCS streams with multiple indices (besides just time). What are your scenarios? How do you need to access the data? How would you like to visualize it? etc.
    Guest over 3 years ago in General / AVEVA Data Hub Scenarios 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 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
    Guest over 3 years ago in AVEVA™ Adapters / General 4 Tell us more