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 Subscribe
Status No status
Product General
Categories AVEVA Data Hub Scenarios
Created by Deon van Aardt
Created on Oct 25, 2024

RELATED IDEAS

MQTT Supported natively for cloud brokers

Connect needs to support the most popular IIoT protocol - MQTT. This must all be done within the config environment. I am NOT talking about an agent that sits somewhere else. A number of ideas:

  1. Connect needs to be a native subscriber to cloud based brokers. One should be able to browse a cloud based MQTT broker and create data streams from seleceted topics. Ingest the data from those topics.

  2. Auto creation of new data streams from new topics detected in broker. Using rules it must be possible to let the system automatically create new data streams ingesting data from new topics created on a broker.

  3. Be able to unpack JSON based payloads from the subscribed topics irrespective of the structuring and have customisable configuration on how to send the data into Connect data structuring.

  4. Connect should expose its namespace to the configurator so that the mapping between MQTT sources of data can be easily mapped to Connect.

  5. The configuration environment must allow the user to test the configuration - i.e. see the live values of subscribed topics and the result of unpacking payloads.

  6. Connect must have the ability to publish to cloud based MQTT brokers. This should include the ability to customise the topic structure of the publisher to match the topic structure expected in the broker. The default topic structure should match the Connect namespace structure, but must have the ability to customise the structure.

  7. The publishing capability must have the ability to create customised JSON structures and the ability to map dta strems to the structure.

  8. Auto generated publishing of topics must be supported with defined rules. I.e. under a certain part of the Connect namespace - it should be possible that as new data streams are added these data streams are automatically published to new topics on the broker.

  9. Connect should be partnering with major MQTT brokers like HIveMQ and EMQX to provide native integration from these platforms to connect.

  10. Connect should be an MQTT broker. This has lots of advantage and could simplify things.

  • Attach files