How to Find AF Attributes Referencing a PI Point
To find AF attributes referencing a PI Point, identify the source tag and Data Archive, then search the AF data-reference configurations across the databases you administer. PI Builder exports can help with a manual search. At enterprise scale, a searchable reference inventory is more practical.
The important word is all. A text search that finds an exact tag name is useful, but it may not capture every attribute whose configuration eventually resolves to that point.
Why a tag search inside AF is tricky
AF attributes can use the PI Point data reference, templates, configuration strings, and substitutions. The relationship between an attribute and its source PI Point may be defined at the template level and resolved for each element.
That means two questions need separate answers:
Which AF attribute configurations explicitly mention this PI Point?
Which attributes actually resolve to this PI Point for the elements we're reviewing?
The second question may require evaluating template substitutions and inspecting configured relationships, not just searching strings.
A manual approach using PI Builder
Start by exporting the relevant AF elements, templates, and attributes through PI Builder. Retain each attribute's AF database, element path, template, data-reference type, and configuration. Search for the PI Point and related configuration patterns.
Next, resolve candidate references against actual elements. If the environment uses multiple Data Archives, confirm server names. Repeat for the other AF databases in scope. Save your export as a dated snapshot and review it again before making production changes.
This workflow works, but it can become tedious across very large AF deployments.
Make the result useful to operations
A good reference report doesn't stop at the attribute name. It shows the full element path, template, AF database, source server, and linked PI Point. That's what an engineer needs to assess a change or hand the issue to the right site owner.
Osprey can help create and export discovered PI Point-to-AF attribute relationships so administrators aren't rebuilding the same lookup with Excel every time.
Frequently asked questions
Why doesn't a text search find every AF reference?
Some data references use templates, substitutions, or indirect paths rather than a literal PI Point name.
Can the same PI Point be referenced by multiple AF attributes?
Yes. This can be intentional, but it is important context for troubleshooting, cleanup, and change impact.
Is it safe to query the PI AF SQL database directly?
Prefer supported AF access methods, exports, and APIs. Direct database queries can be brittle and may be unsupported for production administration.