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

Notifications

Showing 122

XML or other flat file Delivery channel

Would like to see the ability to create XML or other flat files from PI Notifications as was available in previous versions. We have seen cases where the network that the PI system resides on is locked down to the point that only flat files can b...
Guest almost 2 years ago in AVEVA™ PI Server / Notifications 0 No Status

Notification delay setting similar to True For on EF Gen analysis

Allow the ability to configure a delay in sending Notifications so that they would only send if the triggering event frame is open for a configurable amount of time. This is possible at the analysis level using the True For setting; however, this...
Guest almost 2 years ago in AVEVA™ PI Server / Notifications 0 No Status

PI Notifications: Run exe on notification trigger

When a trigger condition is satisfied run an executable. This might be possible using Custom Delivery Channel but Custom Delivery Channels are no longer supported in PI Notifications 2.x
Guest almost 2 years ago in AVEVA™ PI Server / Notifications 0 Declined

Custom time formats for specific notifications

Customer would like a specific Notification to use a 24 hour time format, while all other Notifications use the 12 hour time format. For Example: Notifications A sends out emails in a 24 hour time format. All other notifications sends out emails ...
Nico Cha almost 2 years ago in AVEVA™ PI Server / Notifications 1 Declined

Dependency between Notifications

It would be nice to have a dependency between Notification in a way that if one Notification is sent other Notifications are not sent. My use case is this. I have a corporate AF Server that monitors multiple sites. If a site loses power, I would...
Guest almost 2 years ago in AVEVA™ PI Server / Notifications 0 No Status

Include Creation date in event frame properties for Notifications

We see issues where notifications appear to be delivered late but then find the event frame was created at a later time than the actual event because of connectivity issues. Having the creation date of the event frame exposed for a notification wo...
Guest almost 2 years ago in AVEVA™ PI Server / Notifications 2 No Status

Enable headers for SOAP web service end point

As a PI Administrator I need PI Notifications to support custom headers for SOAP web service end points. Some external systems require specific headers and currently it is only possible to customize headers for REST end points. As an example of an...
Guest almost 2 years ago in AVEVA™ PI Server / Notifications 0 No Status

Notifications Subscriptions Notify Option defaults to "Start and End"

Many EFs are poor health in nature such that notifying the user when the event is ended is very important. Many users don't realize that this is an option. Either make start and end the default or present all choices more visibly to the user. This...
Guest almost 2 years ago in AVEVA™ PI Server / Notifications 0 No Status

Ability to modify SOAP xml format

There are some cases when the sender wants to modify the format of the SOAP xml itself. Currently Notifications service constructs a XML request including all the variables provided by the wsdl.
Guest almost 2 years ago in AVEVA™ PI Server / Notifications 0 No Status

Allow dots in JSON property names when using REST Delivery Endpoints

When configuring a Noification with a REST Delivery Endpoint, there is no way to escape a dot (".") so it doesn't gets interpreted as a path delimiter. There are cases when the dot must be part of the property name. One way to solve it would be to...
Guest almost 2 years ago in AVEVA™ PI Server / Notifications 2 No Status