Which tags are being used by a PI Analysis
As a PI Administrator, I want to know which tags are being used at which PI Analysis so I can know exactly if there is already another Analysis writing to a tag and avoid duplicated or wrong data.
We add the AF path (to the output-attribute of the analytics) into the calculated tags extended description.
This is a manual process but saves a lot of time tracing tags back to the source. This can be done easily if AF creates the tags, however this set-up is always a manual process.
It would be great if analytics did this automatically, as an option. The extended descriptor or source tag attribute is not used by analytics, so in most cases should be available to use.
I understand why it's useful to know which PI Point are analysis outputs. However, the suggestion to add a PI Point attribute may not be the best way to accomplish this. Thank you for your comments and votes. We'll continue to evaluate what we can do to help our users.
there are times I cannot easily find what analysis is writing to an attribute if the tag has more than one location in AF. this information would be extremely helpful!
As we increase our use of PI Analytics, we are having difficulty keeping track of tags being written to by Analysis. For any tag, it's difficult to determine when the Analysis lives in AF, or if the tag is being written to by Analysis at all!
It would be nice if there as an additional trait in a PI Tag that specifies if it's being written to in analysis and the analysis path. Currently there isn't a great way to find tags that are being written to via analysis unless you've done a good job classifying it with a unique point source and adding some notes in the extended descriptor.
I would like to see AF Analysis populate this new field or fields with information pertaining to if it's data is coming from analysis and the AF path for the analysis so we can easily find these in our AF system.
Hahnming Lee commented
Where? Are you just looking for something that alerts you when two analyses are writing to the same place, regardless of where it is in the database (or even server)? Is this a common scenario for the customer, or do they do this unintentionally during configuration? If it's unintentional, what is the common path to getting into that scenario?
You can get a higher level look at your analysis via PI Builder and pulling in attributes and analysis. This will give you all the PI points data reference string configurations associated with attributes. While this won't exactly map it together, you can look for duplicate config string (or tag references) across attributes.