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

Ideas

Add a parameter to disable NTLM authentication

On the "Health endpoints parameters" page of the documentation of any AVEVA Adapter, it states that Negotiate (i.e. try Kerberos first and fall back to NTLM if that fails) will be used if a username/password pair and a clientId/clientSecret pair a...
Guest about 1 month ago in AVEVA™ Adapters / General 0 No status

Automatic Configuration Sync between failover adapters

When adapters in a failover group, any changes to configuration need to be manually synchronised between the adapters. Without automation, this could lead to misaligned configuration causing data collection issues.
Mike Horrocks 2 months ago in AVEVA™ Adapters / General 0 No status

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 over 1 year ago in AVEVA™ Adapters / General 1 No status

Enable OmfEgress component to be configurable by instance (by component)

In our process we wish to send a different set of data to different PI environments. For instance we would like all data to egress to the PROD environment while only egress a subset of data to the DEV environment, in which we don't need all the da...
Guest almost 4 years ago in AVEVA™ Adapters / General 7 Future consideration

Support outputs/write data from PI Adapters

No description provided
Guest almost 4 years ago in AVEVA™ Adapters / General 4 No status

UOM lost on restart & missing UOM definition at data collection level

Description When using the ModbusTCP adapter (seems other Adapters impacted): Data is ingested into CDS as a stream A Unit of Measure (UOM) can be manually assigned to the stream in CDS or EDS. But on adapter restart, the UOM is automaticall...
Jean-Philippe Tricart 4 months ago in AVEVA™ Adapters / General 0 No status

Adapter to failover when there is egress issue

When connection to the datasource are all good for all the adapter failover members, but the primary adapter having issue connecting to the PI web API (egress) for example, adapter does not failover. Unlike PI Interface UNIINT failover, when there...
Ee Sheing Lee almost 3 years ago in AVEVA™ Adapters / General 2 No status

Classic Mode for Adapters

One of the big issues we have with adapters (outside of the lack of write capability) is not having the same control over creating and editing tags that we have with PI interfaces. As we talked about the adapter automatically creates PI tags or us...
Guest over 3 years ago in AVEVA™ Adapters / General 5 Future consideration

processor rate(s) for Processor properties of Modbus Adapter Service Health

Visualize and understand usage when trended with other diagnostic properties.
Glenn Moffett 2 months ago in AVEVA™ Adapters / General 1 No status

Allow Adaptors to run in Docker

Allow Adaptors to run in Docker. This would ease the roll-out and management of adaptors. Also new Cisco switches now allow Docker instances on the switch, limiting the need for extra hardware.
Erik Prins over 2 years ago in AVEVA™ Adapters / General 2 Already exists