Guide
The ultimate guide to managing your PI System Download now
How to Easily Identify Which PI Tags and AF Attributes Are Mapped to PI Vision Displays
How to Easily Identify Which PI Tags and AF Attributes Are Mapped to PI Vision Displays
PI Vision displays can reference PI Points directly or use AF attributes. Over time, it becomes difficult to know which data sources support each display.
This information is important for troubleshooting, cleanup, migration, and governance.
Why manual review does not scale
An administrator can open one display and inspect its data sources. That method becomes slow when an environment contains hundreds or thousands of displays.
A central dependency inventory provides a more practical view.
Capture the important fields
For each discovered display reference, record information such as:
Display name
PI Vision server or environment
Symbol or object when available
Data reference type
PI Point name and server
AF database, element, and attribute path
This creates a dataset that can be searched and filtered.
Use the inventory for troubleshooting
If a display stops updating, identify its underlying tags and attributes first.
Then check freshness, quality, AF mapping, and calculation status for those sources.
Use the inventory before migration
Before moving PI Vision, AF, or Data Archive infrastructure, identify displays that reference the systems that will change.
Create a validation list and confirm each important display after the migration.
Use the inventory for cleanup
A stale or old PI Point should not be deleted until the team knows whether PI Vision still uses it.
Usage information also helps identify displays that depend on retired equipment or development servers.
Include indirect dependencies
A PI Vision display can use an AF attribute that receives a calculated result. The direct display reference is only part of the chain.
For high-impact changes, trace the attribute and analysis back to the original sources.
Keep the data current
Display usage changes frequently. Refresh the inventory before major projects and on a recurring schedule if the environment changes often.
The practical goal is simple: PI teams should be able to identify which displays use a data object without manually opening every display.