How PI EFGen works

In addition to triggering an event frame start and end time, PI EFGen can also populate attributes to record data that accompanies the event frame (such as its name). Event frame templates can be used to represent different types of events such as downtime, startups and shutdowns, process excursions, or batch data. PI EFGen includes a graphical configuration tool, the PI Event Frames Interface Manager. You can migrate PIBaGen configurations to PI EFGen using this tool.

At startup, PI EFGen creates any required event frame templates. During operation, PI EFGen scans the PI Server data archive for changes to specified active points. When an active point indicates that an event or one of its child events has begun, PI EFGen generates an event frame, populating its attributes. If the event frame requires an asset (such as a unit) that does not exist in the AF database, PI EFGen creates the asset. When the active point indicates that the event has concluded, PI EFGen records the end time in the event frame.

The following diagram shows how PI EFGen interacts with the PI Server and PI AF Server.

PI EFGen data flow

For best performance and to minimize competition for system resources, install PI EFGen on a dedicated interface node. Ensure that it can access port 5450 on the PI Server node and port 5457 on the PI AF Server node. If you cannot run PI EFGen on a dedicated node, it is preferable to install it on the PI AF Server node rather than the PI Server node, to minimize contention.