AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA 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 AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

ADD A NEW IDEA

Open Message Format (OMF)

Showing 7

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 over 2 years ago in Developer Resources / Open Message Format (OMF) 2 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...
sahilp over 1 year ago in Developer Resources / Open Message Format (OMF) 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 over 2 years ago in Developer Resources / Open Message Format (OMF) 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 over 2 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...
Jinmo Yi about 1 year ago in Developer Resources / Open Message Format (OMF) 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 over 2 years ago in Developer Resources / Open Message Format (OMF) 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 over 2 years ago in Developer Resources / Open Message Format (OMF) 0 No status