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 12

Allow Definition of Point Attributes via OMF to PI Web API

When creating containers via OMF the PI Points are created with default Point Attributes - if these need to be changed it is a manual process to subsequently change the attributes appropriately. As OMF solutions can be easily deployed it would be ...
Guest about 3 years ago in Developer Resources / Open Message Format (OMF) 2 No status

Allow EdgeCmd to set null or empty string parameter values

As per KB000042993, setting parameters with EdgeCmd that are <null> or "" (empty string) is not possible. Instead the JSON configuration file must be created and used in place. It would be more intuitive if executing commands such as: edgecm...
Mike Horrocks over 1 year ago in AVEVA™ Edge Data Store / General 1 No status

Provide GUI for Configuration

Edge Data Store would require a GUI for configuration and health status to work more efficiently to set it up with too many efforts. The GUI should allow to set up the connection to the Data sources of the included PI Adapters, provide OPC UA brow...
Guest over 1 year ago in AVEVA™ Edge Data Store / General 0 No status

OMF should accept the use of special characters like / : @ ! + % < > ( ) when writing to PI WebAPI OMF endpoint

The OMF 1.1 spec does not allow certain special characters that are indeed accepted in the PI Core system like these here: / : @ ! + % < > ( ) When OMF is used to write to PI Core via the PI WebAPI OMF endpoint, this hinders the migration p...
Guest about 3 years ago in Developer Resources / Open Message Format (OMF) 0 No status

Improve throughput

I am not sure if this is a limitation connected to the OMF, WebAPI, or https itself, but in the manual it is given that the maximum message size is 192KB. I am aware that compression is recommended and applied by default by the adapters. For the r...
Guest about 2 years ago in Developer Resources / Open Message Format (OMF) 0 No status

Conditional Data Egress for Edge Data Store

Scenario: In a remote monitoring scenario, Edge Data Store is collecting data through OPC UA or ModbusTCP with a certain sampling rate (assumingly 1s). For normal operations, EDS shall egress only an aggregated one minute value of all analogue str...
Guest over 1 year ago in AVEVA™ Edge Data Store / Egress 0 No status

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

Add a new diagnostic: the IO rate in bytes or megabytes

The current IO rate diagnostic is helpful, but it only shows events per second. For sites who need to manage their bandwidth and make decisions about how much to buy and support from remote sites, it's very important to be able to monitor exactly ...
Daniel Lopez over 1 year ago in AVEVA™ Edge Data Store / Egress 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