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

AVEVA™ Adapters

Showing 10

GUI Front End for UA Adapter

The OPC UA Adapter is a replacement for the OPC UA Connector and should thus provide similar functionality by providing a GUI.
Jonathan Brutt over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 4 Future consideration

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 over 2 years ago in AVEVA™ Adapters / General 2 Future consideration

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 1 year ago in AVEVA™ Adapters / General 5 Future consideration

Transformation and Scaling for OPC UA Adapter

Implement transformation and scaling for OPC UA adaptor the way it exists for PI OPC DA interface tags. The user can modify egressed tags and the data will be transformed / scaled when egressed.
Guest over 2 years ago in AVEVA™ Adapters 2 Future consideration

Detect and monitor which OPC UA server the PI Adapter is connected to

When configuring a PI Adapter to leverage server-level redundancy, it is not currently possible to monitor which server instance the PI Adapter is connected to. Surfacing this information would allow server administrators to better monitor the hea...
Giulio Cattarin over 1 year ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 3 Future consideration

Stream-level debugging

As a PI System Administrator, I'd like to be able to trace values being received, and subsequently being sent by the Adapter, similar to PI Interfaces. Having the ability to trace/log timestamps and values for specific streams would greatly help ...
Guest over 2 years ago in AVEVA™ Adapters / General 0 Future consideration

Provide a streamlined way to rename streams and push the changes to the endpoint

The current process forces the user to modify the adapter configuration (DataSource for the prefix, DataSelection for the stream name) and the endpoint (PIDA, OCS). The adapter should support modifying directly the stream name and push those chang...
Guest over 2 years ago in AVEVA™ Adapters / General 1 Future consideration

Allow PI Adapter for MQTT to log the raw json payload received from the broker

For troubleshooting, it can be very helpful to see the raw json payload that the adapter has received from the broker, rather than just the error response from the attempted parsing. It can be difficult to know why a parsing attempt has failed wit...
Guest over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 2 Future consideration

Allow multiple references to holding register for bit extraction

Given a 16bit integer holding register, in certain instances we only care for specific bits rather the integer value. Using the bitmap allows the selection of those specific bits but you can only reference the register once. i.e. In data selection...
Guest almost 2 years ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 8 Future consideration

Accept HEX numbers for Register offsets in data selection

Most modbus equipment providers provide information using registers in Hex format i.e. 0x0000 ~ 0xFFFF. It would be nice if the offset could accept this to avoid error in conversions HEX to DEC. Would make things alot more seamless/easier.
Guest almost 2 years ago in AVEVA™ Adapters / AVEVA Adapter for Modbus TCP 0 Future consideration