For a short while, OSIsoft had a program called "PI System Directory", which allowed you to monitor, from a web interface, which versions of which PI programs were installed on each PI server, among other things. PI System Directory Publisher had to be installed on each monitored PI server. PI System Directory was also required for a program called "PI System Health", which I think would have replaced the PI Interface For Performance monitor and the PI Connector For PI System Health, but, sadly, this program never made it past the beta stage. It gathered health data on any PI servers that had the PI System Health Connector (not to be confused with the PI Connector For PI System Health) on it.
Some traces of these concepts currently exist on CONNECT. For example, for any server with the PI To CONNECT Agent installed on it, you can view, from within CONNECT, the health of the connection to the server and the version of the PI To CONNECT Agent, and you get a warning if you are using an outdated version of the PI To CONNECT Agent.
Please incorporate more of the concepts of PI System Directory and PI System Health into CONNECT so that we can comprehensively monitor all PI servers or servers that run AVEVA server programs. CONNECT can act like PI System Directory and PI System Health. The PI To CONNECT Agent can act like the PI System Directory Publisher and the PI System Health Connector. Alternatively, a separate program could do this, and this program could apply to AVEVA programs other than the PI ones.
Since PI System Directory and PI System Health have not been available to users for many years, and since they were short-lived, I don't expect this idea to get many votes. Someone at AVEVA will need to review these programs to judge the viability of this idea.
