AVEVA™ PI System™ Feedback Portal

Welcome to our new 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

All ideas

Showing 3156

OMF: Property Bags

Allow reuse of a set of properties for multiple type definitions in the OSIsoft Message Format (OMF) spec.
Guest over 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 da...
Guest over 1 year ago in Developer Resources / Open Message Format (OMF) 0 No Status

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 1 year ago in Developer Resources / Open Message Format (OMF) 2 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 1 year 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 1 year ago in Developer Resources / Open Message Format (OMF) 0 No Status

Automatically generate official print after batch completion

Customer would like to be able to automatically generate an official PDF printout at the completion of a batch or at the end of time-periods for time based reports. In the case where MES systems are used, some customers merely need to attach an o...
Guest over 1 year ago in AVEVA™ RtReports 0 No Status

Allow configuration of Trend legend position

As an report designer, I would like to be able to choose the position of the legend on Trends.
Guest over 1 year ago in AVEVA™ RtReports 0 No Status

Have both default PI Data Archive and Asset Framework Server load in generator

Some customers are using the same RtReports Server to connect to both PI Data Archives (for batches) and Asset Framework Servers (for Event Frames) since they are using both at the same time. They'd like to be able to store both DA and AF/Database...
Alan Izar over 1 year ago in AVEVA™ RtReports 1 No Status

RTReports - cannot handle Unit/Asset filtering when timebased - this is a 'bug'

RTReports - cannot handle Unit/Asset filtering when timebased - this is clearly a 'bug'. Workaround are to use MDB !!! not - good!!. Please asap make a patch adressing this in RtReports.
Guest over 1 year ago in AVEVA™ RtReports 0 No Status

RTReports - cannot handle Unit/Asset filtering when timebased - this is a 'bug'

RTReports - cannot handle Unit/Asset filtering when timebased - this is clearly a 'bug'. Workaround are to use MDB !!! not - good!!. Please asap make a patch adressing this in RtReports.
Guest over 1 year ago in AVEVA™ RtReports 0 No Status