Skip to Main Content
CONNECT 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. For links to our other feedback portals, please see RESOURCES below.

ADD A NEW IDEA

Clear

Sequential Data Store (SDS)

Support different data retention via OCS

Some customers need to store (retain) some, but not all, data for extended periods of time. For example, there can be a need to store any data used in regulatory reports for 5-7 years. Going forward, could OCS be an option for collecting/aggregati...
Guest almost 4 years ago in Streams / Sequential Data Store (SDS) 0 No status

Segregate Data from Different Customers within a Namespace

Ability to segregate and view information (Data Ingress, Streams, Assets, etc.) from multiple customers/clients within a Namespace SO THAT it's very clear what data and system artifacts are related to each customer and SO THAT information doesn't ...
Guest almost 4 years ago in Streams / Sequential Data Store (SDS) 0 No status

Data Update Mechanism

Have a mechanism to subscribe to data change updates on the platform so applications don't need to constantly poll for changes.
Guest almost 4 years ago in Streams / Sequential Data Store (SDS) 2 No status

Simple file import through AVEVA Data Hub Portal

Challenge: Customers would like to have the possibility to do a simple import of a CSV, JSON, XML, Excel file by uploading it to the Data Hub portal and store the data into Streams without taking the efforts on installing and configuring an instan...
Jeff Branfield over 2 years ago in Streams / Sequential Data Store (SDS) 1 No status

Allow Asset Rules to support multiples of Id, Name or Description

When creating an Asset Rule, you are forced to extract tokens from either the Stream ID, Stream Name or Stream Description (not multiples). Often, information will be required from all of these fields. Being able to tokenise all inputs allows for ...
Sam Pride 10 months ago in Streams / Sequential Data Store (SDS) 0 No status

Spectral Data

Be able to handle the storage, context, and retrieval / visualization of spectral data.
Guest almost 4 years ago in Streams / Sequential Data Store (SDS) 1 No status

Store Images & Pictures into OCS

Ability to store images as time bound data into OCS, and retrieve the images for viewing or modeling/analysis. Example scenario: a thermal camera takes a picture of a furnace and the image is used to extract data and performance KPIs about the f...
Guest almost 4 years ago in Streams / Sequential Data Store (SDS) 1 No status

provide a sample dataset

Enable a new user to explore an existing dataset and get ideas for their own implementation
Glenn Moffett almost 2 years ago in Streams / Sequential Data Store (SDS) 0 No status

Batch Tracking Data Storage & Visualization

Ability to capture Batch Tracking data into OCS and visualize it. The data could be coming from an existing PI System with using Event Frames.
Guest almost 4 years ago in Streams / Sequential Data Store (SDS) 0 No status

rename/change stream id

typo/configuration change
Glenn Moffett almost 2 years ago in Streams / Sequential Data Store (SDS) 0 No status