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

Search results: AVEVA™ Adapters

Showing 10 of 35

Allow client-level failover on a per data source component level

Currently the client-level failover for Adapters occur on a per Adapter level. Which means that for instances where multiple data sources are configured, in some circumstances failover may result in an instance with a bad connection to a particula...
Guest 23 days ago in AVEVA™ Adapters / General 0 No status

Ua Server force failover / improve failover logic

Let me preface this by saying that I know it is a workaround for a non-compliance with the OPC UA specifications. The point is that the situation described below is unfortunately all too common and the workaround is needed. It often happens that t...
Guest almost 2 years ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 1 No status

displayname/localname for identifier that excludes namespace and data type

Example: OPC UA Server 'Name': 2.0:W-HVAC-AC-1-IO!Wtot Namespace: 2 Datatype: 0 Identifier: W-HVAC-AC-1-IO!Wtot OPC UA Server 'DisplayName': W-HVAC-AC-1-IO!Wtot OPC UA Adapter {Identifier} returns: 2.0:W-HVAC-AC-1-IO!Wtot Required stream name: W-H...
Glenn Moffett 10 months ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

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 2 years ago in AVEVA™ Adapters / General 0 No status

PI Adapter for (generic) MQTT to enable auto-discovery of key value pairs using wildcards

When reading from a generic MQTT broker, we currently need to specify explicitly each key value pairs we want to collect inside the data selection json configuration file. This prevents us from really being agile at the time of the initial setup a...
Guest over 2 years ago in AVEVA™ Adapters / General 0 Completed

Provide additional time formatting options for RDBMS Queries

Background: Today we are collecting data from our AspenTech IP21 Server thorugh the PI Adapter for OPC UA and the related AspenTech OPC UA Server. This works perfectly fine for analogue data but not for data which is providing us equipment status ...
Hans-Otto Weinhold over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for RDBMS 1 Tell us more

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 almost 2 years ago in AVEVA™ Adapters / AVEVA Adapter for RDBMS 1 Tell us more

Better support of IP21 OPC UA Server with PI Adapter for OPC UA

We have been using the PI Adapter for OPC UA in its current version to collect data from IP21 OPC UA Server during a lighthouse project. However, the configuration was a bit cumbersome since the OPC UA Server of AspenTech uses an opaque mechanism ...
Hans-Otto Weinhold almost 2 years ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

Allow the BACnet Adapter to handle responses with an LVT that does not match the request

Currently the BACnet Adapter expects devices to respond with the same "Length Value, and Type" (LVT) value as the request. When this occurs the BACnet Adapter cannot parse the data in the response. For example: Request from Adapter, LVT=1 Response...
Guest about 1 year ago in AVEVA™ Adapters / AVEVA Adapter for BACnet 0 No status

Add the option "Ignore Bad_WaitingForInitialData Status"

In the connectors there was the option "Ignore Bad_WaitingForInitialData Status", as described here. For gen 1 there was a need to edit the config files directly, and in gen 2 the option was integrated into the UI. Instead for the adapter I recent...
Guest over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status