Put an Asset into Offline Mode which stops related analyses and notifications
Have a way to manually (or automatically via another calculation/analytic) put the status of an asset/equipment into an offline/maintenance mode that has the effect of turning any analyses and notifications for that asset off.
Guest
Oct 19, 2026
I've been working with the PI Monitor templates that the PI team created a few years ago. There were some templates that had a standard Status Attribute. In this case, it just covered preventing the generation of Event Frames.
If the Notifications Suppressed attribute = True, then the Event Frame triggers would be set to False. IF Suppressed=True, then the Event Frame Variable Send_Notifcations = FALSE. Each Trigger contains "AND Send_Notifcations"
They also added a Analytics that looked at the Parent element for the same Attribute and/or the Operational Status of the Parent. Either could disable the child Elements. If you set your elements up hierarchically, this Status eventually flows down to the bottom elements.
I added a table that can match all the element under a sub-tree. A function allows all the children to set Notifications Suppress = False at the same time. With a time stamp, I can do the same thing that the OSI NOC could do. i.e. quiet alarms until a certain date. This prevents the notification suppression from being forgotten.
I've been working with the PI Monitor templates that the PI team created a few years ago. There were some templates that had a standard Status Attribute. In this case, it just covered preventing the generation of Event Frames.
If the Notifications Suppressed attribute = True, then the Event Frame triggers would be set to False.
IF Suppressed=True, then the Event Frame Variable Send_Notifcations = FALSE.
Each Trigger contains "AND Send_Notifcations"
They also added a Analytics that looked at the Parent element for the same Attribute and/or the Operational Status of the Parent. Either could disable the child Elements. If you set your elements up hierarchically, this Status eventually flows down to the bottom elements.
I added a table that can match all the element under a sub-tree. A function allows all the children to set Notifications Suppress = False at the same time. With a time stamp, I can do the same thing that the OSI NOC could do. i.e. quiet alarms until a certain date. This prevents the notification suppression from being forgotten.