Which AF Analysis Writes to a PI Tag? How to Find It
If a PI tag contains calculated data, start by identifying the writing source and any AF attribute associated with the output. Then locate the AF Analysis that uses that attribute as an output and inspect the analysis configuration. Do not assume every calculated tag comes from AF Analysis: Performance Equations, interfaces, and external applications can also write data.
This is a common troubleshooting problem: the output value looks wrong, but the engineer knows only the PI tag name, not the calculation that produces it.
Work backward from the output PI Point
First, confirm the PI Point name, Data Archive, and update history. Inspect available point and interface information to determine whether the tag is written by an analysis or another source.
If it is an AF Analysis output, identify the AF attribute whose PI Point data reference maps to that tag. Then inspect analyses in the relevant AF database and element or template to find which ones declare that attribute as an output.
The element path and analysis name matter. A template-based analysis can have many instantiated analyses across assets, even when they share the same definition.
Don't confuse readers with writers
An analysis can read a PI Point without writing to it. Likewise, an output attribute can be referenced by other calculations downstream. Build the investigation around two relationships: reads from and writes to.
If multiple analyses or other sources write to the same output tag, investigate carefully. Conflicting writers can produce confusing histories and make root-cause analysis much harder.
Check the whole path
Once you find the writer, inspect its schedule, recent errors, input attributes, configuration, and changes near the start of the problem. If the value is wrong rather than stale, verify the source inputs before modifying the formula.
Osprey's discovered tag and analysis relationships can shorten the hunt by showing where calculations sit relative to their inputs and outputs. Source-system checks remain necessary to confirm runtime behavior.
Frequently asked questions
Does every PI tag with a calculation come from AF Analysis?
No. PI Performance Equations, interfaces, external applications, and other writing mechanisms may also be involved.
Can two AF Analyses write to the same PI tag?
Conflicting output configurations can occur. Review all potential writers and the time history before drawing conclusions.
Why can I find the AF attribute but not the Analysis?
The attribute may be an input, the analysis may be instantiated from a template, or the writing source may not be AF Analysis at all.