Guide

The ultimate guide to managing your PI System Download now

Enhancing PI System Data Lineage with Tycho Data Osprey

Enhancing PI System Data Lineage with Tycho Data Osprey

PI System dependencies are often spread across PI Points, AF attributes, analyses, and PI Vision displays. Osprey discovers and presents these relationships so teams can trace data and assess change impact.



Trace data sources

A lineage view can show which PI Point supplies an AF attribute and which server contains the source.

This helps teams verify that an asset model uses the intended signal.



Trace calculations

For AF analyses, lineage can show important input and output relationships.

This helps engineers answer:

  • What feeds this analysis?

  • Which analysis produced this output?

  • Which other calculations depend on it?



Trace PI Vision use

Display dependencies help PI administrators identify where a tag or AF attribute appears in PI Vision.

This is useful before tag retirement, server migration, and AF redesign.



Support impact analysis

Before a change, teams can review known downstream dependencies.

For example, a tag change can affect an AF attribute, several analyses, and one or more displays. Seeing the chain before the change reduces the chance of an unexpected break.



Support troubleshooting

When a user reports an incorrect display value, lineage narrows the investigation path.

The team can trace from display to AF, analysis, and source instead of opening each system independently.



Combine lineage with health and change data

Lineage becomes more useful when it is connected to data-quality status and configuration history.

A team can identify the failed object, see what it affects, and review changes that occurred before the failure.



Know the limits

Automated lineage can only discover relationships that are visible to the scanner or integration.

External reports, scripts, and custom applications may require additional inventory or integration.



The practical objective

Osprey lineage is intended to make PI dependencies easier to understand and maintain.

The value is not the graph itself. The value is faster investigation, safer change, and better knowledge of how operational data moves through the PI environment.