Here I am again already working on the draft (final version by the time you are reading this) of my 3rd blog about the PowerShell Tools for the PI System within the space of a week. That has to be some kind of record for me to maintain my attention on one topic for so long.
So far I covered a couple of aspects to the PowerShell Tools for the PI System; Connecting to the PI Server and AF Server (collectively known as the PI System), and some real world PI Server archive management issues that I've had to deal with. Hopefully you've enjoyed reading them so far.
For this next blog post I want to talk about PI Interfaces with particular emphasis on two of the most commonly used, the PI Interface for OPC and the PI Interface for Performance Monitor. Now the fact that I am going to focus on those two interfaces in my post doesn't mean you should only carry on reading if you have a particular interest or heavy use of those 2 PI Interfaces, the point of this post is to show you once again how easy, simple and somewhat relaxing it is to automate changes/auditing of PI Interfaces in general with the PowerShell Tools for the PI System. Yes, I did say "relaxing", not sure why but that's just how it feels sometimes working with these OSIsoft CmdLets you just don't need to think too much about it as OSIsoft have done most of the hard work. Anyway feels like I am waffling again so lets get on with it.
PI Interface design changes to 50+instances
Okay, here is the scenario. Imagine you are working in an environment when you have a blueprint of a complete PI System, how the various aspects of the PI System (AF Server, PI Interfaces, PI Server, ...) interact with each other. That blueprint is then used to produce numerous replica PI Systems that are deployed to numerous geographical locations - if you have an interest in how to do that type of deployment then check out my UC 2013 presentation on that very topic. Each of the deployed PI Systems are then merrily doing their job, collecting data, visualizing data, and replicating data back to a single central PI System (via PI to PI).