Where Is My PI Tag Used? Find References in AF and PI Vision
To find where a PI tag is used, check three main places: AF attributes that reference the PI Point, analyses that read from or write to it, and PI Vision displays that show it. For a complete change-impact review, also check interfaces, reports, and applications outside PI. No single manually maintained list is guaranteed to capture every consumer.
It's a simple question that can turn into a long afternoon for a PI administrator: If I change this tag, what breaks?
Start with the tag, not the display
Record the PI Point name, Data Archive, point type, description, and any recent configuration changes. The server matters. A similarly named tag on another archive is not the same source.
Next, build a reference inventory. At minimum, capture the object type, object name, server, AF database, element or attribute path, and where that reference was found. Keep direct references separate from indirect ones.
Find references in PI Asset Framework
Open the relevant AF databases in PI System Explorer and inspect attributes that use the PI Point data reference. PI Builder can export AF attributes for searching and filtering in Excel. That works for a targeted review, but exporting and joining large databases can be slow.
Watch for attributes based on templates, substituted point names, and other data references that resolve indirectly. A literal text search for one tag name can miss references assembled at runtime.
Check AF Analyses and PI Vision
Search analyses for input attributes that ultimately refer to the point, then inspect outputs that may write to it. A tag can be consumed by an analysis without its name appearing directly in the analysis expression.
For PI Vision, inventory both direct PI Point sources and AF attribute sources. If a display is based on an asset context or collection, the saved display configuration may not identify every resolved point that a user could see.
Turn the inventory into a change-impact list
Classify what you find: operational displays, calculations, reporting feeds, and other consumers. Confirm which objects are still active. For a proposed rename or deletion, ask an owner to validate the downstream effects before proceeding.
This is the workflow we focus on with Osprey: making discovered relationships across PI tags, AF, analyses, and PI Vision easier to inspect without repeatedly exporting and searching by hand. It is still important to validate external systems outside the scan scope.
Frequently asked questions
Can PI System Explorer search everywhere a PI tag is used?
Not in one comprehensive view covering all AF databases, PI Vision displays, calculations, and external clients. Use multiple inventories or a dependency-mapping approach.
Does a PI tag with no AF references mean it is unused?
No. It may be used directly in a display, interface, report, script, or third-party application.
What should I check before deleting a PI tag?
Its source, recent activity, AF and analysis references, PI Vision references, external consumers, and a rollback or recovery plan.