Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

PI System Management Tools

View the Module Database tree

  • Last UpdatedFeb 19, 2025
  • 3 minute read

The Module Database tree has the following structure:

  • The root level shows the connected Data Archive servers. Each Data Archive server contains one Module Database.

  • Each Data Archive server may have two types of branches: PI heading sets and PI modules. Each PI module can be associated with a PI heading set and a corresponding PI heading.

    Note: Heading set and heading objects are not migrated to AF, and AF elements are not assigned a PI heading even if the corresponding PI module references a PI heading.

If you don't see all expected objects, right-click in a blank space around the Module Database tree and click Show, then click additional data types you want to display (for example, Properties or Headings).

Heading Sets

The HeadingSets branch contains PI heading sets, which contain PI headings. PI headings are used to promote common naming conventions for modules, for example, equipment. They can also be associated with sub-batches in the PI Batch Database.

For example, a PI heading object may be used to categorize a sub-batch, such as a Phase, or a position in a plant layout, such as a Line.

Each PI heading has two attributes: Description and Level. Description is a text string and Level is an integer. PI headings are for descriptive or informational purposes only, and no hierarchical rules are enforced.

Modules

The Modules branch contains top level PI modules. PI modules can represent various types of information. For example, a module could be used to group PI points that are related to a particular control loop, or PI points used to calculate yield efficiency. Each PI module may contain:

  • Child modules

  • PIUnits , a special type of PI module specifically used for batch tracking

  • Optional Aliases, , used to associate common names with PI points

  • Optional Properties , which store information related to a module

Modules and Properties can be expanded to show individual items. Below is an example of a Module Database tree containing heading sets, headings, modules, aliases, and properties.

Module Database tree in PI System Management Tools showing 'PISRV1' with nested categories like 'Modules' and 'Controllers,' including 'Aliases' and 'Properties' for 'tic-104.

TitleResults for “How to create a CRG?”Also Available in