What is PI tag lineage?

PI tag lineage (also called tag genealogy) is the complete map of how data flows from its origin — a sensor, field instrument, or source PI Server — through every Interface node and Data Archive until it reaches the destination PI tag you query. A typical path might be: source sensor → OPC Interface on ServerZ → PI Data Archive on ServerY (as sTagA) → PI-to-PI Interface → PI Data Archive on ServerX (as TagA). Osprey constructs this map automatically, showing every hop and its health status.

Why does my PI tag stop updating and how do I find the cause?

A PI tag goes stale ('stuck') when any hop in its data path fails — the source sensor stops sending, an OPC interface drops its connection, a PI-to-PI interface loses contact, or a Data Archive rejects writes. Without lineage visibility, a PI System Administrator must manually log into each Interface node and Data Archive in sequence to isolate the break, which can take hours across a large system. Osprey's PI Tag Lineage shows the entire hop-by-hop path on one screen, highlighting exactly which hop is failing so you can go straight to the root cause.

What is the difference between PI tag lineage and PI tag genealogy?

PI tag lineage and PI tag genealogy refer to the same concept: mapping the complete data path of a PI tag from source to destination. 'Lineage' is the more common term in data governance contexts, while 'genealogy' is sometimes used by PI System practitioners to describe tracing a tag's ancestors across PI-to-PI replication chains. Osprey supports both use cases — forward tracing (downstream impact) and backward tracing (root source identification).

Can Osprey trace through PI-to-PI interfaces and OPC interfaces?

Yes. Osprey traces the full chain: OPC DA/UA interfaces that pull from PLCs and DCS systems, PI-to-PI interfaces that replicate tags across PI Servers, and calculated tags that derive values from other tags. Osprey maps each hop, identifies the source tag name at each server, and shows the health status of every interface in the path.

How many PI servers and interfaces does Osprey support?

Osprey is built for large PI environments — systems with hundreds of interfaces and millions of data points. The lineage engine is optimized for complex multi-hop architectures spanning multiple Data Archives, Interface nodes, and PI Servers. There is no practical limit on the number of hops or servers that can be mapped.

PI Tag Lineage & Genealogy | AVEVA PI Tag Data Path

Product · PI Tag Lineage

Trace Your PI Tag

Data Path, Instantly

When a PI tag goes stale, stop hopping between Interface nodes and Data Archives. Osprey maps the entire hop-by-hop data path automatically. Pinpoint exactly where the data stopped flowing, in minutes.

PI Tag Lineage: hop-by-hop data path visualization from source sensor through OPC and PI-to-PI interfaces to destination PI tag

The Problem

Your PI tag passes through a complex data pipeline and no one is monitoring the full path

When a tag goes stale, finding the cause means manually checking every system in the chain. No single view exists. It takes hours. And one wrong assumption sends you down the wrong path entirely.

Where does your data actually come from?

DCS Tag

→

Plant Historian

→

Central Historian
⚠ Stale Tag

→

Asset Framework
Hierarchy & Analyses

→

PI Vision

Osprey maps this entire path automatically. The failing hop is highlighted instantly. No manual investigation required.

Hours

Manual investigation across multiple Interface nodes and Data Archives

Minutes

Time to pinpoint the failing hop with Osprey

1 Screen

Every hop, source tag, and interface health in one unified view

Stop Guessing. Start Tracing.

One screen. Every hop. The exact point of failure.

Hop-by-Hop Transparency

See the full data path from source sensor through OPC interfaces, PI Archives, and PI-to-PI interfaces, all in one view.

Instant Failure Pinpointing

Know immediately whether the break is at the source sensor, an OPC interface, or a PI-to-PI replication hop. No more manual node-by-node investigation.

Automatic Discovery

No configuration needed. Osprey reads your PI System's interface and tag setup and builds lineage automatically, giving you full visibility into tag usage and data flow across hundreds of interfaces and millions of tags.

Tribal Knowledge, Documented

Replace the mental maps in senior engineers' heads with a queryable lineage graph anyone on the team can use.

Your PI tag passes through a complex data pipeline and no one is monitoring the full path

See everything downstream that depends on a failing tag. Catch issues before the impact reaches operations.

Product

Solutions

Company

Resources