Skip to Main Content
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

Clear

Ideas

Showing 142 of 5219

Show "Subscriber Escalation Timeout" parameter in PI System Explorer

In PI System Explorer's UI, you can configure time intervals for escalation groups. If the SubscriberEscalationTimeout parameter is different from the escalation group's interval, the notification will not deliver on the right interval and there w...
Guest over 3 years ago in AVEVA™ PI Server / Notifications 0 No status

add support for client certificate authentication in PI Notifications

Add support for client certificate authentication in PI Notifications
Guest over 3 years ago in AVEVA™ PI Server / Notifications 1 No status

Add option to select interface behavior for bad timestamps (PI RDBMS)

When the PI RDBMS Interface gets a bad timestamp from the source RDB that it cannot coerce into a PI Timestamp, the interface attempts to use the current timestamp instead and logs the following error: "pitm_settime() error - 15002. Using current...
Guest over 3 years ago in PI Interfaces / PI Interface for RDBMS 0 No status

Accept weeks and years in the relative time syntax for history recovery start and end times

For whatever reason, times such as *-1w or *-1y are not accepted, but times such as *-1mo and *-1d are OK. Please make the PI Interface for RDBMS accept the same relative times that other PI programs accept.
Kenneth Barber over 3 years ago in PI Interfaces / PI Interface for RDBMS 0 No status

RDBMS Interface - Full Sync and Annotations

The PI SDK writes required for setting annotation values with the exdesc and RDBMS interface are not compatible with Full Synchronization. Make this compatible.
Matt Voll over 3 years ago in PI Interfaces / PI Interface for RDBMS 0 No status

Pi Notifications should have smarts to exclude or N/A message body content for excluded attributes created from templates.

Pi Notifications should have smarts to exclude or N/A message body content for excluded attributes created from templates. Currently if we have say 4 attributes in an element template, and some instance elements have a couple of those "excluded", ...
Zubin Najmi almost 2 years ago in AVEVA™ PI Server / Notifications 0 No status

Subscription Templates

I'm currently working on a project to push notifications immediately to a database, via REST delivery endpoint. However, each delivery endpoint needs to be subscribed per notification rule, AND also configured. Configuration can take awhile to do,...
Milin Roshan over 2 years ago in AVEVA™ PI Server / Notifications 0 No status

Create Analysis and Notifications when limits are set on attributes

As a Notification user I would like a one-click way of configuring a notification on the limits I have set on the attribute so that I spend less time configuring a simple notification such as this.
Guest over 3 years ago in AVEVA™ PI Server / Notifications 0 No status

Show different status icon for Notification when it's Event Frame is not Running

For notifications triggered off of an event frame analysis, it is possible for the event frame analysis to be turned “off” (not showing green checkmark) while the corresponding notification still shows a green checkmark. This seems slightly mislea...
Guest over 3 years ago in AVEVA™ PI Server / Notifications 0 Declined

Specific Number of Required Acknowledgements for an Escalation Team

A way to require a certain number of acknowledgments for an escalation team? (ie: Only stop notifying if 3 or more people of my 5 person escalation have acknowledged the notification)
Guest over 3 years ago in AVEVA™ PI Server / Notifications 0 Declined