How does the integration work
PI event frames
Events are time periods that represent important activities or changes in your process or operations, such as equipment downtime, process excursions, or product batches. Each event has a defined start and end time.
Aveva PI Event Frames allow you to capture these events along with their name, start and end time, and related details called event attributes. By using templates, you can standardize the data collected for different types of events.
TrendMiner context items
TrendMiner context items allow you to annotate and classify process events directly on your time-series data, providing deeper insights into your operations. When linked to PI Event Frames, context items inherit all event frame properties, including name, start and end times, and attributes.
If you have pre-defined context item types with fields that match the PI Event Frame attributes, the attributes will be mapped. Any attributes without matching fields are added as additional properties to the TrendMiner context item, similar to how other referenced elements are handled. You can later map these attributes manually by using the PI Event Frame name as the technical name for the context item field.
Linking PI event frames to TrendMiner context items
The table below shows an overview of how properties of PI event frames are mapped to properties of context items.
PI Event Frame | TrendMiner context item |
|---|---|
Template | Type |
Name | Context field: EVENT_FRAME_NAME |
Description | Description |
Start time | Time of start-event (EFStarted) |
End time | Time of end-event (EFEnded) |
Primary element (PI AF Element) | Component (asset or attribute) |
Attributes | Fields |
Other referenced elements | Additional properties |
PI Event Frame Templates and Context Item Types in TrendMiner
For each PI Event Frame template, TrendMiner automatically creates a corresponding context item type, which appears in the context item type configuration screen. Admin users can rename these types within TrendMiner without affecting the data stored in your PI system.
The "primary element" in a PI Event Frame links to an element in the PI Asset Framework. Similarly, in TrendMiner, the component of a context item links to an asset or attribute in the TrendMiner Asset Framework.
Tip
Handling PI Event Frame Elements in TrendMiner
If a PI Event Frame element doesn’t have a corresponding context item field in TrendMiner, it will be treated as a property of the context item. You can view these unmatched elements under "Other Properties" in the context item details.
To use elements in context view filters or other analyses, it’s recommended to create matching context item fields. Just make sure the technical name of the context item field matches the name of the referenced element. This can still be done after the elements are processed in TrendMiner.
PI Asset Framework
The PI Asset Framework (AF) synchronization in TrendMiner focuses on importing attributes with linked tags. During the synchronization process, TrendMiner identifies attributes in the PI AF hierarchy that include a data reference linking them to a specific PI tag. Only these attributes with linked tags are imported into TrendMiner as assets with a linked tag. Attributes without a data reference are excluded, and their child attributes are not processed further.
The connection between an asset and context items is established through the PI Event Frame’s primary element, which corresponds to the PI tag linked to the PI attribute. The context item belongs to a TrendMiner tag, and this tag is in turn linked to the asset.
This relationship between the PI tag referenced in the event frame and the TrendMiner tag linked to context items enables you to correlate context items with their corresponding time-series data.