PI install kit inheritance

Blog Post created by Kenneth_Barber Champion on Jul 27, 2020

The PI install kits contain all of the programs that the program of interest depends on. Running an install kit is clearly much easier than tracking down and installing all of these programs separately. However, this is no reason to get complacent. If one of these programs is updated, exactly which programs will need that update? On which computers do you need to install the updated program?


To answer these questions, we must understand the dependence between the PI programs and their install kits, which is shown in the diagram below. Each block represents an install kit. The arrows represent the inheritance of components, and so only the non-inherited components are listed under each install kit.


Diagram showing the inheritance structure of the PI install kits


Some things to note about the diagram:

  • Some of the arrows have labels of the form "−program". This means that a program from earlier in the inheritance chain is not inherited. For example, "−PIBufSS" means that the PI Buffer Subsystem (just the program, not everything from the PI Buffer Subsystem install kit) was not inherited. The meanings of the abbreviations that are used for the arrow labels should hopefully be obvious.
  • I excluded the PI Server install kit due to the difficulty in including it. Unlike the other install kits, the PI Server install kit provides great freedom in which programs you install.
  • I excluded install kits that do not or barely have any relationship with another install kit. These include PI API, PI Connectors (Generations 1 & 2), PI Connector Relay, PI Data Collection Manager, PI Diagnostics, PI SQL Client, PI System Directory Publisher, and AF Transformer.
  • I excluded install kits for superseded PI programs (e.g. PI ProcessBook).
  • The diagram is based on the most recent versions of the install kits as of October 6, 2020. I will update as necessary.
  • I used UMLet to create the diagram. However, this was not intended to be a proper UML diagram. I know that my arrows are pointing the wrong way.


It is also worth noting that the PI AF Client program contains several components, which the user can choose to install or not install. These components are:

  • PI AF SDK .NET 4
  • PI System Explorer (optional: Management Plug-In, AF Collective Manager)
  • PI Builder
  • PI AF User Documentation


I will refer to this blog post in future posts and I hope that you will find it useful too!