PI EF Configuration
Aveva PI Event Frames are treated as an external data source and must be configured in the Data Source section of ConfigHub. You can either add a new data source with asset capabilities using the PI Asset Framework provider or enable asset capabilities on an existing asset data source.
Important
In Aveva PI, PI Event Frames are linked to the PI Asset Framework through the primary element property, which connects an event frame to an asset framework element. Because of this relationship, TrendMiner’s integration with PI Event Frames depends on its integration with the PI Asset Framework.
For everything to work correctly, both TrendMiner integrations for Event Frames and Asset Framework must be active and have the same configuration. If they are not aligned, TrendMiner cannot properly link a context item to its corresponding TrendMiner component, which represents the PI primary element of an event frame.
In summary, you can only use event frames from a PI Event Frame data source if the linked PI Asset Framework data source is also configured in TrendMiner for asset framework integration.
You can either:
Add a data source with asset capabilities (using the PI asset framework provider)
If the Event Frames are on the same host as the PI Asset Framework, enable context capabilities on your existing PI AF data source. To do this, edit the PI AF data source configuration in ConfigHub and check the "Context" capability box.
Supported versions
To synchronize your Aveva PI event framework, TrendMiner needs to have access to the PI AF SDK. The SDK is included in the PI AF Client and the PI OLEDB Enterprise driver.
We recommend using release 2017 R2, 2.9.0 or later of the Aveva PI AF Client or PI OLEDB Enterprise packages for compatibility. Syncing older versions is possible but won't achieve optimum performance and might lose events in specific cases as the PI API in the older versions don't support the necessary query parameters TrendMiner needs. Contact TrendMiner support (support@trendminer.com) for more information.
How does the sync work?
Last synced
Live synchronization: TrendMiner offers live synchronization (with a 2 minute interval) of ALL event frames that are modified or created. If a lot of items are edited at the same time (e.g. a bulk action in PI EF), this interval is synced in a separate thread (excessive interval thread) to avoid a delay on the live sync. Synchronization is considered "excessive" when more than 800 event frames need to be processed within a single interval.
The live sync can be enabled in the context properties section of the data source. Enabling live synchronization will start synchronizing context items from the moment of enablement onwards. For historical data, please use a historical sync.
Historical synchronization
Start historical sync: TrendMiner offers a historical synchronization of ALL event frames that are edited or created within a predefined timeframe. The start and end date can be selected in the data source detail panel.
Resume historical sync: If the last historical sync did not complete successfully and is therefore in a FAILED or CANCELLED state this action will appear to allow the user to resume the sync manually. The sync will start back from where it left off, in contrast to "Start historical sync" which restarts the synchronization from the start date.
Cleanup
Resync all open items: This process checks whether open context items are still present in the source system and determines if they can be updated. If a context item lacks an associated component, it is automatically resynced. The status of these resync operations is displayed as scheduled jobs on the diagnostics screen.