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 51

Add parameter to limit the amount of data retrieved in a Get Updates request - Change broker

Add a parameter that we could pass in the Get Updates request to set a maximum number of events returned since the bookmark https://docs.aveva.com/bundle/connect-data-services-developer/page/api-reference/change-broker/change-broker-updates.html
Guest about 1 month ago in Data Management & Storage / Sequential Data Store (SDS) 0 No status

Have streaming updates support Assets

ResourceType = Assets (or any other non-data type)
Guest about 1 month ago in Data Management & Storage / Sequential Data Store (SDS) 0 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 20 days ago in Data Management & Storage / Sequential Data Store (SDS) 0 No status

Egress data to another Edge Data Store

I would like to be able to configure an Edge Data Store to egress data to another Edge Data Store. Due to network limitations, I cannot egress data directly to OCS or PI Web API. Egressing to another Edge Data Store would allow me to configure an ...
Guest about 3 years ago in AVEVA™ Edge Data Store / Egress 4 Future consideration

Edge Data Store Calculations

Enable customers to create real-time calculations on EDS data.
Guest about 3 years ago in AVEVA™ Edge Data Store / Analytics & Calculations 3 Evaluating

Edge Data Store Visualization

Ability to have basic visualization of data from the Edge Data Store for local operations.
Guest about 3 years ago in AVEVA™ Edge Data Store / Visualization 2 Evaluating

remote ingress to EDS

Enable remote access to EDS OMF endpoint to support deployments where Adapter/OMF application is installed on different host/network to EDS because architecture must fit in with tiered networks for critical asset security. For example remote sites...
Guest about 3 years ago in AVEVA™ Edge Data Store / Ingress 3 Future consideration

Support Custom Units of Measure (UOMs)

The ability to define custom units of measure (UOMs) within OCS.
Guest about 3 years ago in Data Management & Storage / Sequential Data Store (SDS) 0 No status

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 about 3 years ago in Data Management & Storage / 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 about 3 years ago in Data Management & Storage / Sequential Data Store (SDS) 0 No status