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 18 of 694

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

Ability to create nested parent/child events using AVEVA Advanced Analytics

Support the ability to trigger events from data including parent/child relationships. Support mapping to Event Types that represent the S88 batch standard.
Todd Brown over 1 year ago in Events 0 Needs review

Add filter to SDS, similar to Asset Explorer

The Asset Explorer has the ability to filter to filter on Status, Asset Type, Metadata key/value and in the Filter Facets box. The ability to filter Streams by StreamType and Metadata would be very helpful
John Marriott 6 months ago in Data Management & Storage / Search & Filtering 0 No status

Higher limitation when querying stream summary data

When querying for summary data on a stream, customer is running into the restriction of 250K records but the streams have millions of records they need to include. Having the count of records would be useful to the customer to know how to chunk up...
Guest about 3 years ago in Data Management & Storage / Search & Filtering 1 No status

Conditional Data Egress for Edge Data Store

Scenario: In a remote monitoring scenario, Edge Data Store is collecting data through OPC UA or ModbusTCP with a certain sampling rate (assumingly 1s). For normal operations, EDS shall egress only an aggregated one minute value of all analogue str...
Guest over 1 year ago in AVEVA™ Edge Data Store / Egress 0 No status

Kerberos Authentication from EDS to PI

Submitting on behalf of a customer concerned about meeting stringent security requirements. Kerberos is a staple in their security architecture and the would very much like to incorporate it here.
Guest about 3 years ago in AVEVA™ Edge Data Store / Egress 0 Future consideration

Add a new diagnostic: the IO rate in bytes or megabytes

The current IO rate diagnostic is helpful, but it only shows events per second. For sites who need to manage their bandwidth and make decisions about how much to buy and support from remote sites, it's very important to be able to monitor exactly ...
Daniel Lopez over 1 year ago in AVEVA™ Edge Data Store / Egress 0 No status

Support retrieving value at start and end of an event for an Asset property of non-numeric data type

As a developer, I'd like to be able to query the value of an asset property at the start or end of an event even when the property is not numeric (Enum, string,etc). Currently, the summaries section of the GraphQL query does not return values for ...
Jessica Rammo over 1 year ago in Events 0 Needs review

Support retrieving stream values at start and end of an event even when the data in the time range exceeds data retrieval limits

As a developer using querying the events database via GraphQL, I'd like the ability to retrieve "property," "start," and "end" summary statistics even when the stream data over my event duration exceeds 250K data events. Currently, I receive the e...
Jessica Rammo over 1 year ago in Events 0 Needs review

OCS query syntax support for wildcards in query string

As a user of both the Portal UI and the REST API, I would like to be able to use multiple wildcards placed where I like within a query string. For instance; something like * abc * 123 * xyz * (without the spaces)
Guest about 3 years ago in Data Management & Storage / Search & Filtering 1 No status