Seperate Notifications PI Server

Discussion created by RJKSolutions on Jun 2, 2009
Latest reply on Jun 4, 2009 by andreas

When researching into providing a solution that incorporates PI-Notifications are there any best practice recommendations for the PI server element of Notifications?  So although Notifications looks at Attributes and not concerned where the source data is coming from, it still uses PI to archive the Notification items history.  Further to this there isn't just a single PI tag created for a single notification but multiple PI tags.


In heavy usage of Notifications it seems to point towards having a seperate PI server purely for hosting the Notification items history, especially if for example you have a 200,000 point system of which you are planning to monitor say 10,000 points. 


Could OSI confirm "best practice" for Notification PI servers - use existing PI system or seperate dedicated PI system?
Are there any figures for number of PI tags created per notification item life cycle?