Learn about bottom-up hierarchical configuration (PIBaGen compatibility mode)

In PIBaGen compatibility mode, the start and end of the level 1 event frame (Procedure/PIBatch) is triggered by the level 2 active point and a procedure name tag that associates multiple level 2 event frames.

The procedure name tag corresponds to the PIBatch index point from the legacy PI Batch Generator (PI BaGen) interface. The procedure name tag specifies the PI point containing the name of the parent level 1 event frame. A valid PI Point for this attribute provides the name of the level 1 event frame. However, the point is not the active point for level 1 event frame. In other words, transitions in this PI point do not trigger the start and end of level 1 events. A level 1 event frame is started only when a level 2 event is started and ends when all the level 2 events within the level 1 event frame end. If a new level 2 event frame is added after the level 1 event frame ends, its end time is updated with the new end time.

When a level 2 event starts, the value of the procedure name tag is used as name of the level 1 event frame and as one of the search criteria that the interface uses to determine if a new level 1 event needs to be created. If there are no matching level 1 event frames within the interface’s cache time, a new level 1 event is created. If a valid PI point is not specified for this attribute, the level 2 event frame does not belong to any level 1 event frame.

The following figure illustrates the relationship between level 1 and level 2 events.

The following table lists the events generated as a result of the preceding set of value changes.