Ability to track source of AF created PI tag to it's origin (dB/element/attribute/analysis)
I have thousands of tags based on AF analysis, both auto created by AF and some which have been converted from ACE, PE, Totalizers to AF.
Looking at the tags in Point Builder, DataLink, or SMT I am able to tell by Point Source that the tag is calculated in AF. But where? We use a single AF database for our SCADA, AMI, and Generation groups so browsing for an analysis is quite time consuming.
It would be nice to have a PI Tag attribute that would show the "path" to the analysis. \\Database\Element\Child\Child\Attribute\Analysis and that this information could easily be discovered in all management and analysis tools (DataLink, Builder, SMT...)
ADMIN RESPONSE
Aug 20, 2022
This is currently possible by using the appropriate substitution parameters when creating output PI Points for your analyses. Please reach out to tech support and they can help you.
Guest
Oct 27, 2026
We've seen this exact issue in large AF environments. Knowing a tag comes from an Analysis is one thing, but finding the actual analysis can take a surprising amount of digging.
We've been working on this with Osprey, automatically mapping calculated tags back to their originating AF analysis, including the element and attribute path. Makes troubleshooting and impact analysis a lot easier.
I visited your booth at AVEVA World 2025 and I second the need for this improvement. Point source "AF" is ambiguous for organizations that have multiple Asset Frameworks.
Thanks for your idea. I understand what you're looking for in terms of a solution, I would be leaning towards not adding an PI Point attribute. If we were to do that, it would increase the size of the database as this would affect all PI Points affecting overall performance. In addition, the impact to backwards compatibility for clients would be unknown and would require a good amount of testing. Having said that, as I mentioned earlier, I understand your needs (thank you for the clear explanation), we'll look at what we can do to help you and others with similar needs.
We've seen this exact issue in large AF environments. Knowing a tag comes from an Analysis is one thing, but finding the actual analysis can take a surprising amount of digging.
We've been working on this with Osprey, automatically mapping calculated tags back to their originating AF analysis, including the element and attribute path. Makes troubleshooting and impact analysis a lot easier.
I visited your booth at AVEVA World 2025 and I second the need for this improvement. Point source "AF" is ambiguous for organizations that have multiple Asset Frameworks.