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

Enable subscribe using wildcard for AVEVA Adapter for MQTT

It would be handy to have the PI Adapter for MQTT to be able to subscribe to a broker by using wildcards only. Right now, we need to specify each individual topics on the data selection rule, and this eventually comes as individual subscription as...
Guest almost 2 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

Allow session persistence to support true QoS 2 data collection and backfill of events after a data source disconnection

It appears that regarding Session Persistence (persistent vs clean session), the Adapter hardcodes setting the Clean Session Flag for the generic data source (Sparkplug doesn’t QoS 2 nor session persistence) to true. This should be a user-defined ...
Daniel Lopez 6 months ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

PI Web API OMF renaming of PIPoints without having to delete on API -> rename on PI-> readd on API

When we have an existing PIPoint with a given name, we can't rename it through OMF (which is a pity), requiring the operator of the system to delete the ExDesc from the point, renaming the Point in the PI Server and them readding them through the ...
Guest 6 months ago in Developer Resources / Open Message Format (OMF) 0 No status

OMF: Binary data format support

Provide a binary data format option in addition to JSON in the OSIsoft Message Format (OMF) spec.
Guest about 4 years ago in Developer Resources / Open Message Format (OMF) 0 Declined

OMF: Ability to patch data messages

Add the ability to provide partial information for an existing data point. This is meant as a partial update which replaces values for some properties of a type without affecting others.
Guest about 4 years ago in Developer Resources / Open Message Format (OMF) 0 Planned

OMF: the possibility to set/create security settings (groups …) by using OMF

After creating Elements and Tags in AF by using OMF standard, I don´t want to manually configure security settings in AF. The possibility to set/create security settings (groups …) by only using OMF standard would be very helpfull.
Guest about 4 years ago in Developer Resources / Open Message Format (OMF) 0 Declined

Configurable Hostname/IP Identifier for OMF Health Egress

The health tags and AF structure is created with the following naming pattern by default: <machine hostname>.<adapter type> To support modern containerized deployment models, please consider adding a configurable field that allows cust...
Guest 7 months ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status

Streaming API - for real time visualization

As a OCS real-time-visualization-client I require a Streaming API so that I can avoid continuously polling the REST API. Similar to the WSS Chanels in PI WebAPI Or something like PI WebAPI Stream Updates could also work
Guest about 4 years ago in Developer Resources / CONNECT data services API 1 No status

Expose REST API for PI to OCS configuration

Provide a documented REST API for PI to OCS connection and data transfer configuration. This would enable scripting against these configurations, allowing users to update their data transfers automatically, and manage them in a customer-specific way.
Guest about 4 years ago in Developer Resources / CONNECT data services API 0 No status

Allow MQTT adapter to parse timestamps in local time without specifying a timezone suffix to each timestamp

We would like the MQTT Adapter to be able to interpret timestamps in local time without needing to explicitly state the timezone or UTC offset in each timestamp, but for the adapter to always interpret the timestamps as being in a specific timezon...
Guest about 4 years ago in AVEVA™ Adapters / AVEVA Adapter for MQTT 0 No status