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 28

OMF: Property Bags

Allow reuse of a set of properties for multiple type definitions in the OSIsoft Message Format (OMF) spec.
Guest about 3 years ago in Developer Resources / Open Message Format (OMF) 0 No status

GitHub samples need updates for OMF 1.2 spec with PI Web API

OMF 1.2 specification have been out now.However, the current samples for OMF w/ PI Web API (BasicAPI, ComplexDynamic and Bart Ingress ) only feature OMF 1.1 versions.PI Developers will need OMF 1.2 samples in GitHub so that they have a reference t...
Guest about 2 years ago in Developer Resources / Open Message Format (OMF) 1 No status

When using debug mode level tracing in opc ua, can we get a dump of the client settings and data source settings in the log file that are being used so we know the context of that session?

it will tell us exactly the full context the adapter is operating in when it starts up and connects to the data source.
Guest over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

Clearly state that a Data message cannot include both a container ID and a type ID

Right now, the documentation: https://omf-docs.readthedocs.io/en/v1.0/Data_Messages.html Mentions that "For each object, either typeid or containerid must be specified". However, it does not clearly state that you CANNOT include both in a data m...
Guest about 3 years ago in Developer Resources / Open Message Format (OMF) 0 No status

Simplify the security configuration for OPC UA

The newer OPC UA protocols have stricter security standards, which is good, but that makes configuring connections more difficult, especially with regard to the need to put in tunneling and open ports. It should be easier to establish a secure con...
Guest 12 months ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

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 over 2 years ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 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 almost 2 years ago in AVEVA™ Adapters / AVEVA Adapter for OPC UA 0 No status

OMF: Response code 200

Response code 200 for OMF or possibility for validating of OMF data. EDS send only ‘accepted’ not ‘finished without error’, even if OMF is malformed and dropped in processing. Customer needs 100% tracking, so we must read all data after sending ...
Guest about 3 years ago in Developer Resources / Open Message Format (OMF) 0 No status