Beyond Stale and Bad Points: A Modern Look at PI System Data Quality

PI System Management Tools provide useful ways to identify stale and bad PI Points. These checks remain an important part of PI administration.

Modern PI environments also require context about where those points are used and what a change can affect.

Stale and bad detection is the first layer

A stale or bad-point list helps administrators identify signals that need review.

The list does not always explain:

• Which assets use the signal

• Which AF attributes reference it

• Which analyses depend on it

• Which PI Vision displays show it

• Whether the point is important or unused

Add dependency information

A stale point that feeds a critical display deserves different attention from a stale point on retired equipment.

Usage and lineage help teams prioritize the finding.

Add source context

When a point is stale, trace the interface, source system, and AF mapping.

This helps the team repair the correct layer instead of changing the historian first.

Add change history

If the condition began after a tag, interface, or AF change, that history can shorten the investigation.

Use existing PI tools and additional observability together

Built-in PI administration tools remain valuable for detailed configuration and system management.

Additional observability can provide enterprise inventory, recurring scans, dependency maps, and cross-system prioritization.

The tools solve different parts of the operating problem.

The practical objective

Modern PI data quality is not only the detection of bad or stale values.

It also requires an understanding of source, use, dependency, and change so teams can decide what to fix and what can be retired safely.