Integrations · AVEVA PI System
In progressAVEVA PI System integration.
PI System collects and contextualizes operational time-series data across industrial facilities. The PI AF asset framework is where that context is modeled — and its quality depends on an accurate engineering description of the plant. Armeta produces that engineering description directly from the governing P&IDs.
By Armeta Engineering Team, Engineering Team
Last reviewed:
Draft in progress
This page is currently being written. The scope and framing are locked; the full technical write-up is on the editorial calendar. If this page is directly relevant to an active evaluation, the Armeta team can walk through the content with you live.
What this page will cover
- 01What PI System does in this context — time-series collection, PI AF asset framework, and how engineering context anchors tag data to the physical plant.
- 02What structured P&ID data looks like in PI AF — AF elements, attributes, templates, and how the engineering graph Armeta produces maps to the AF hierarchy.
- 03How Armeta's output maps to the PI AF schema — element typing, attribute conventions, cross-drawing connectivity, and the reconciliation of instrument tags to their P&ID source.
- 04Integration pattern — structured export for AF import, or API integration where continuous synchronization is required across drawing revisions.
- 05Implementation approach and typical timeline — discovery of the existing AF configuration, mapping of Armeta output to AF templates, pilot against a single unit, then rollout.
- 06Case considerations — existing AF maturity, integration with dependent PI Vision and PI Datalink analytics, and the governance of AF changes.
Your drawings, your data
Start with ten of your own drawings.
Reference pages describe what Armeta does. The fastest way to know what it does for your team is to run it on your actual P&IDs.