PI Notifications and ProcessBook 3.1 John Messinger Product Specialist OSIsoft Australia

Agenda PI Notifications ProcessBook 3.1 2

PI Notifications A new alerting paradigm from OSIsoft Historized alerting Highly available scheduling Escalation Extensible delivery Integration with OSIsoft client tools

Feature Map PI Notifications Real Time Alerting Workflow Integration Auditing/ Reporting Deployment / Maintenance Data Integration PI Server Event Archiving PI Notifications AF 2.0 Highly Available Extensible History Viewer Centralized Content Evaluation Message Delivery This feature map describes how the value propositions of the PI Notifications platform are achieved through features. <Click through the individual columns and just say how each piece is achieved> Now different PI Products cover these feature sets including <click> the PI Server which stores all the alert events and <click> AF 2.0 which supports the centralized content, template structures, and allows us to trigger notifications off of different types of data. <click> all of this together comprises the PI Notifications architecture, which leverages the strengths of both AF and PI while bringing a world class notification engine to the PI System platform. For those of you interested in the details of this architecture, I would recommend you come talk to us at the Demo Lab…. <whenever that is> Comment: Instead of this and next slides, we should describe more features in terms of use cases. Similar to the five demos but without demos. It can be framed as What about this? This can be accomplished … What about that? That is supported out of box… Etc. It may not be a bad idea to get rid of the conclusion and future slides and frame them as above. So the whole talk has the following structure: Goal/Use Case Describe and/or Demo Repeat 1 and 2 This structure fits perfectly with that two of us are presenting Period/Natural Asset/ Notification Templates Versatile Data Sourcing Escalation SDK Access Rule Evaluation

PI Notifications Architecture

PI Notification Notification Process Trigger Contacts Content Delivery Acknowledgement The process is to establish first a trigger – some even that happens to start a notification. Maybe a 10 minute average temperature exceeds a specified limit. Next there are contacts – names, phone numbers, email addresses, and these can come from active directory. Then there is the content – what should the notification say? It can include many things, standard and customized, including dynamically created links to web pages showing the data that triggered the notification. Finally, there is delivery by email or text message. Optional features include acknowledgement requirements, and if there is failure to acknowledge, escalation. 6 6

Notifications: Result

Demo Demo Demonstration Adding Contacts and creating Notifications Acknowledging Notifications Demo Open PB Create a new display Add a trend with multiple traces Use formatting toolbar to change the trace colors Use formatting toolbar to change trend settings (font size and background color) Create a new vertical trend Use format paint brush to apply trend settings from trend 1 to trend 2 Open preferences dialog so that format paintbrush won’t need to be used for creating future trends. Change font size and trend background color. Demo 9

Visualization for PI Notifications Here’s a view of some of the notifications desktop client. A ProcessBook add-in on the left, and on the right the IM-like pop-up notification manager. 10

Migration Migration Options RtAlerts Migration tool available to convert all RtAlerts rules to PI Notifications. Web configuration interface replaced by the PI System Explorer PI Alarm/PI SQC Alarm Migration tool available to convert all alarm configuration to PI Notifications PI SQC Alarm Add-In to ProcessBook cannot view notifications PI AlarmView Basic functionality of AlarmView incorporated in the PI System Explorer plug-in MyPI See Migrate to PI Notifications for specific details RtAlerts: RtAlerts will be continuously supported. There is a migration tool to convert all RtAlerts rules to notifications within PI Notifications. The Web configuration interface is replaced by the PI System Explorer. PI Alarm/PI SQC Alarm: PI Alarm will be continuously supported. There is a migration tool to convert all alarm configuration to notifications within PI Notifications. PI SQC Alarm (also known as PI RtSQC) will be continuously supported. There is a migration tool to convert all SQC alarm configurations to notifications within PI Notifications. These notifications will be viewable within the PI System Explorer. However, the PI SQC Alarm Add-In to ProcessBook is not able to view these notifications. PI AlarmView: PI AlarmView will be continuously supported. The basic functionality of AlarmView is covered in PI System Explorer within the view of notifications in MyPI. These functionalities include searching history, acknowledgment, and adding comments. 11

Releases Initial release: Q4 2007 Next major release: 2008 Hierarchical notifications Thin client Root cause Further client integration Down the road Full analysis support Don: Talks release dates

Agenda PI Notifications ProcessBook 3.1 13

High Availability Provided with PR1 PI Server Collective Releases for ProcessBook, ActiveView, SQC and BatchView Primary PI Server Secondary PI Server Secondary PI Server 14

New Features in ProcessBook 3.1 Vertical Trends Details Add-In Statistics ToolTip Add-In PI Notifications Add-In Trend Analysis enhancements User Interface (UI) enhancements

Demo Demo Demonstration Building displays made easier Analysis features Demo Open PB Create a new display Add a trend with multiple traces Use formatting toolbar to change the trace colors Use formatting toolbar to change trend settings (font size and background color) Create a new vertical trend Use format paint brush to apply trend settings from trend 1 to trend 2 Open preferences dialog so that format paintbrush won’t need to be used for creating future trends. Change font size and trend background color. Demo 16

Demo PI Notifications ProcessBook display as content ProcessBook display linked as content Instant trend Pass time context to display Demo 17

No compatibility layer AF 1.X AF Clients 1.X AF 2.0 18

With the AF 1.5 compatibility layer AF 1.X AF Clients 1.X AF 1.5 AF 2.0 19

AF Integration Shipping with ProcessBook 3.1 AF Modeler (1.3) AF Client (1.3) AF Compatibility Layer (1.5) 20

SIG Requests Addressed Linear regression line Tooltip statistics Easier display building and formatting Vertical trend Annotations 21

Future - PI ProcessBook 3.2 The next planned version No schedule yet Planned enhancements: Cursor synchronization across trends Easier symbol configuration Enhanced Notification integration Time playback functionality Data dictionary support Other time handling improvements

Thank You