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.

Status No Status
Categories Event Frames (EF)
Created by Guest
Created on Aug 20, 2022

Allow EF Comments Egress via Notifications

In critical operations, managing in-field comments made on production EF's is essential to being world class. Customers need the ability to push out their field comments to surrounding systems and messaging. Most notably production critical event frame comments need to be sent to Reliability/CMMS for root cause transactions and OEM services providers via web services. Also there is a broad need across all industries to broadcast EF comments via internal and external email delivery endpoints.
  • Attach files
  • Guest
    Reply
    |
    Aug 20, 2022
    Please clarify if these are random event frames or event frames that normally would have triggered notifications, i.e. they are tied to a Notifications Rule already.
  • Guest
    Reply
    |
    Aug 20, 2022
    Not random. The use-cases are EF's triggered by rules looking for poor health or poor quality. There would be a notification rule with subscribers set to be notified on start and end. At the start of the event all subscribers are notified of the issue. The subscribers work to resolve the issue and post comments to the EF. Then when the event ends, a notification would include all the comments that were made. This serves to broadcast the comments and create buy-in for those entering comments. It also allows PI to deliver "closure" to the subscribers and peace of mind. The comments are critical history stored in PI. What users do now, they "ReplyAll" in the notif email to communicate with each other rather than use PI. This dilutes the value in the pi system as a single sys of record. Many EF's are quite "thin" and uncompelling w/o comments and observations from the field. A related uservoice request is asking for notif email "chatter" to be captured on the EF. That would be even more effective at achieving the same goal. This is not unlike how ITSysman ticket chatter is scraped from email and stored on the ticket. Same use case. This would lead us to consider triggering notifications whenever a comment was entered. Chatter history on critical operations assets is important data alongside sensor data.