OSIsoft is committed to providing customers with a more manageable system. We are working hard to solve the problems of deployment, security, and standardized health messaging within our products.
PI System Health and PI System Directory were early steps in the manageability story, and we learned a lot thanks to significant customer testing and feedback. We also discovered that there is much more to making a truly manageable system through these engagements. In order to pursue these larger needs surrounding manageability, we will not be releasing PI System Health, and we are putting PI System Directory on maintenance so that our engineering resources can be allocated toward these bigger efforts. As such, there are no additional enhancements for PI System Directory planned at this time.
As a result, the status of this suggestion will be changed back to “No status” for the time being. Future status updates will be communicated here.hooper commented
The 'solution' we currently use involves a Python script on a Scheduled Task, AF SDK, various counters mapped into PI points, and a dedicated analysis and notification that fires at the top of every hour. We look to see that the analysis counter and successful notifications emailed counter each increment and send email if not.
This is not as timely as we'd like. And it is a somewhat unique and obscure solution. I'd like to see something that mPI would pick up on, and a 'health' tag for each system (analysis and notifications) that could be monitored, put on a dashboard, or used to more easily trigger emails outside of Notifications.
Further, our "solution" simply tells us Analysis or Notifications are not working. Anything you can do to provide information about why it isn't working would also be great.
75 voteshooper commented
I agree. While I understand annotations can be added to Event Frames, engineers in my company often annotate PI Tags to explain data anomalies both slight (difficult or not worth capturing via event frames) and major (that do generate Event Frames). We deliver our PB 'dashboards' to many users via Coresight as Coresight performs much better on mobile devices and regional offices where internet connectivity is not a good as at the corporate offices (PI headquarters).
Our users rarely visit Event Frames as all the data they need is available in the PB dashboard. The fact annotations are absent in the Coresight view discourages use of Coresight.
We are currently researching this item and evaluating it for a future release.