Where Is My Data Coming From? Understanding Tag Mapping in the PI System

A value in a PI Vision display can pass through several objects before it reaches the user. When a number is wrong, teams need to trace that path quickly.

Source mapping and lineage make the data path visible.

Start with the consumer

Identify the display, report, or calculation that shows the unexpected value.

Determine whether it references:

• A PI Point directly

• An AF attribute

• A calculated AF attribute

• An analysis output

Trace AF attributes to the source

For an AF attribute, review the data reference and source configuration.

Confirm the PI Data Archive server and PI Point. Also confirm substitution parameters when the mapping comes from a template.

Trace calculations

If the value is calculated, identify each important input and the final output.

A correct output configuration can still produce a wrong value when one upstream input is incorrect.

Identify downstream use before change

Before renaming or removing a tag, determine which AF attributes, analyses, and PI Vision displays use it.

This supports impact analysis and safer decommissioning.

Use source mapping during migration

Control-system and PI server migrations can change tag names, servers, and mappings.

Create a dependency inventory before the migration. Validate important data paths after cutover.

Review old and development sources

Large environments can retain references to development, test, or legacy servers after projects finish.

Search for these references and confirm whether they are intentional.

The practical objective

Every important value should have an answer to two questions:

• Where did this data come from?

• What depends on it?

When PI teams can answer both quickly, troubleshooting and change management become much more controlled.