PI AF asset model structure

PI AF objects are organized in a tree structure, similar to the file structure on a Windows computer. In Windows, rather than having thousands of files on your desktop, you typically group files under folders. The same concept applies to PI AF elements. Organizing elements into hierarchies makes navigation of the elements easier, and it also provides insights into how the elements relate to one another.

When you create an asset model, you need to decide on a structure that makes it easy for users to find the different assets. Consider who your users are and what they will be looking for. For example, maintenance engineers might want to use PI System Explorer to find and record maintenance information. For this audience you might want to group assets by equipment type.

For example, if you had three pump elements, you might create an element called Pumps and then place all the pump elements beneath it. If you had two elements representing tanks, you might put them all under a Tanks element.

Asset model organized by equipment type

On the other hand, if you have multiple plants in different locations, that same maintenance engineer might want to see all the equipment located at his own plant. The following illustration shows the same elements organized by plant.

Asset model organized by location

You are not restricted to only one organizational strategy. You can use an element reference to include the same asset in more than one place in the tree. For example, you could choose to organize by equipment type and by plant as well. In the following illustration, the hierarchy includes the geographical tree and the equipment tree side by side.

Mixed asset model

You could alternatively nest the equipment organization under the geographical organization.

Note: Limit the depth of your asset hierarchies to 10 levels or less to maintain the performance and interpretability of your asset data.