PI Tag Governance: Best Practices for Naming, Managing, and Cleaning Up PI Tags

The PI System is designed to collect and store vast amounts of time-series data from industrial operations. Over time, however, even well-maintained PI environments accumulate a common problem:

tag sprawl.

New sensors are added. Projects create temporary tags. Interfaces generate thousands of signals. Control system upgrades introduce new naming structures.

Without clear governance, PI environments often end up with:

• duplicate tags representing the same signal
• inconsistent naming conventions
• undocumented tags no one understands
• unused or abandoned tags consuming resources

The result is familiar to many PI teams:

• engineers struggle to interpret signals
• dashboards reference incorrect or outdated tags
• analytics break when tags are renamed or removed
• troubleshooting becomes slower and more error-prone

Tag governance ensures that signals in the PI System remain consistent, understandable, and reliable as the environment grows.

This guide covers best practices used by experienced PI administrators to manage tags at scale.

Quick Self-Check: Does Your PI System Have Tag Governance Issues?

Consider the following questions.

• Can engineers easily understand what a tag represents just from its name?
• Do you know how many tags are unused or abandoned?
• Do naming conventions remain consistent across systems and sites?
• Can you trace which dashboards or analytics depend on a tag?
• Do you know which tags were created during past projects or migrations?

If these questions are difficult to answer, your PI environment may have tag governance gaps.

Many organizations only discover these issues when analytics fail or engineers struggle to interpret signals.

Why PI Tag Governance Matters

Tags are the foundation of the PI System. Every asset model, dashboard, calculation, and analytics pipeline ultimately depends on them.

Poorly governed tags create several operational challenges:

• engineers waste time identifying the correct signal
• duplicate tags introduce conflicting values
• unused tags increase license and infrastructure costs
• analytics reference signals that are no longer reliable

Strong governance practices help ensure that tags remain consistent, trustworthy, and easy to use across the organization.

How Tags Fit Into the PI Architecture

Understanding where tags sit in the PI ecosystem helps explain why governance is critical.

Tags serve as the bridge between physical equipment and the analytics systems that rely on the data.

If tag structure becomes inconsistent or unreliable, every downstream system becomes harder to maintain.

1. Establish Clear Tag Naming Conventions

Tag naming conventions are the most visible aspect of tag governance.

A well-structured naming convention allows engineers to understand signals quickly and avoid duplication.

Best Practices for Naming PI Tags

Use consistent naming patterns

Tag names should follow a predictable format. A structure could be:

Example:

Include meaningful identifiers

Tag names should communicate what the signal represents, not just where it originates.

Avoid overly cryptic abbreviations

While shorter names can be convenient, excessive abbreviations often make tags difficult to interpret.

For comprehensive AF design guidance, see: PI Asset Framework Best Practices: Designing Reliable Asset Models in the PI System

2. Control Tag Creation

One of the main causes of tag sprawl is uncontrolled tag creation.

Projects often introduce large numbers of new tags without considering long-term governance.

Governance Practices for Tag Creation

Define ownership

Establish clear ownership for tag creation and approval.

Review new tag requests

Ensure new tags follow naming conventions and serve a defined purpose.

Avoid duplicate signals

Before creating new tags, verify whether a similar signal already exists.

Document tag purpose

Each tag should have a description explaining what the signal represents.

These practices prevent uncontrolled growth of poorly documented tags.

3. Identify and Remove Unused Tags

Unused tags accumulate quickly in large PI environments.

They may originate from:

• decommissioned equipment
• temporary project deployments
• retired dashboards
• legacy integrations

Over time, these tags consume system resources and increase licensing costs.

How PI Teams Detect Unused Tags

Teams typically look for tags that:

• have not updated in long periods
• are not referenced in Asset Framework
• are not used in dashboards or calculations

Identifying these tags allows organizations to safely retire them.

For detailed stale tag detection methods, see: How to Detect Stale or Flatlined PI Tags in the PI System

4. Detect Duplicate or Conflicting Tags

Duplicate tags often occur during migrations, system integrations, or parallel data sources.

Examples include:

• two tags representing the same sensor
• duplicate signals created during control system upgrades
• derived tags duplicating existing calculations

Duplicate tags create confusion and reduce confidence in the data.

Governance practices should ensure that each operational signal has a clear, authoritative source.

5. Track Tag Dependencies

In modern PI environments, tags rarely exist in isolation.

A single tag may feed:

• AF attributes
• analytics calculations
• operator dashboards
• reporting tools
• machine learning models

Governance requires visibility into these dependencies.

Before renaming or retiring a tag, teams must understand which systems rely on it.

Without this visibility, changes can introduce unexpected failures.

6. Maintain Tag Documentation

Documentation plays an important role in tag governance.

Each tag should include metadata such as:

• signal description
• measurement units
• source system or equipment
• expected update frequency

Clear documentation helps engineers understand the signal and ensures knowledge can be transferred across teams.

Common PI Tag Governance Problems

Many organizations encounter similar tag governance challenges.

Examples include:

• inconsistent naming conventions across sites
• tags created during projects but never removed
• duplicate signals representing the same measurement
• undocumented tags whose meaning is unclear
• dashboards referencing outdated signals

Over time, these issues reduce confidence in historian data and slow down operational analysis.

Managing Tag Governance in Large PI Environments

Large PI deployments often contain:

• hundreds of thousands or millions of tags
• hundreds of PI Interfaces, PI Connectors, and source systems
• thousands of analytics and dashboards

Maintaining tag governance manually in environments of this size becomes extremely difficult.

Organizations increasingly rely on automation to monitor:

• unused or stale tags
• naming convention violations
• duplicate signals
• tag dependencies across analytics and dashboards

Automating Tag Governance with Osprey

Tools such as Osprey help PI teams manage tags more effectively.

Osprey provides visibility into the PI ecosystem and helps identify governance issues across the system.

Learn more about Osprey: Osprey - PI System Data Observability Platform

Capabilities include:

• identifying unused or stale tags
• detecting duplicate or conflicting signals
• mapping where tags are used across dashboards and analytics
• monitoring tag reliability and update behavior
• auditing configuration changes across the PI environment

By automating these checks, engineering teams can maintain clean, well-structured tag environments without relying on manual audits.

PI Tag Governance Best Practices (Summary)

Strong tag governance programs typically follow several key practices.

• establish consistent naming conventions
• control tag creation and approval processes
• identify and retire unused tags
• detect duplicate or conflicting signals
• track dependencies across analytics and dashboards
• maintain clear documentation for each tag

These practices help ensure that the PI System remains organized, scalable, and reliable.

Building Reliable Operational Data Foundations

Tags are the foundation of every PI deployment. When tag structures become inconsistent or poorly documented, analytics and dashboards become difficult to maintain.

Strong tag governance ensures that signals remain understandable, reliable, and easy to use across the organization.

By combining disciplined governance practices with automated monitoring tools, organizations can maintain clean and reliable PI environments as their systems continue to grow.