PI Asset Framework Best Practices: Designing Reliable Asset Models in the PI System

PI Asset Framework (AF) is the contextual layer that transforms raw historian data into meaningful operational information. When implemented well, AF enables engineers to organize equipment data, standardize analytics, and build scalable dashboards.

But many PI environments struggle with AF design.

Over time, asset models become inconsistent. Templates drift from reality. Attributes point to incorrect tags. Calculations multiply without documentation.

The result is familiar to many PI teams:

• Engineers struggle to understand asset structures
• Analytics break when equipment changes
• Dashboards rely on outdated signals
• Troubleshooting takes longer than it should

These issues are rarely caused by the technology itself. They are usually the result of poor Asset Framework design and governance practices.

This guide outlines PI Asset Framework best practices used by experienced PI teams to build scalable, reliable asset models.

We'll cover:

• AF template design
• Asset hierarchy design
• Attribute and tag mapping strategies
• Calculation and analytics structure
• Governance practices that keep AF reliable over time

Quick Self-Check: Is Your AF Model Healthy?

Before diving into best practices, consider a few questions.

• Can engineers easily understand your AF hierarchy?
• Do templates consistently represent equipment types?
• Do attributes reference valid tags across all assets?
• Are AF analyses easy to maintain and troubleshoot?
• Can new engineers understand the model without extensive guidance?

If these questions are difficult to answer, your AF environment may need structural improvements.

Many organizations only discover AF design problems when analytics begin failing or dashboards become difficult to maintain.

Why Asset Framework Design Matters

The PI System collects massive volumes of time-series data.

Without structure, these tags are difficult to interpret or use.

Asset Framework organizes that data into meaningful equipment models.

A well-designed AF structure enables teams to:

• Standardize equipment analytics
• Scale models across hundreds or thousands of assets
• Simplify dashboard creation
• Reduce duplication of calculations
• Accelerate troubleshooting and investigations

In other words, Asset Framework turns historian data into operational intelligence.

But achieving these benefits requires thoughtful design.

How Asset Framework Fits Into the PI Architecture

Understanding the role of AF in the PI ecosystem helps guide best practices.

Asset Framework sits between the raw data archive and the applications that use the data.

If the AF layer is poorly designed, everything downstream becomes harder to maintain.

1. Design Reusable Templates

Templates are the foundation of scalable AF models.

Each template represents a type of equipment, such as:

• Pumps
• Compressors
• Heat Exchangers
• Reactors
• Pipelines

Templates define the structure of attributes, calculations, and metadata for each equipment type.

Best Practices for Template Design

Standardize attributes

Ensure each equipment template uses consistent attribute names such as:

• Temperature
• Flow Rate
• Pressure
• Status

This allows analytics and dashboards to be reused across assets.

Avoid template proliferation

Creating too many templates makes models difficult to maintain.

Whenever possible, reuse existing templates instead of creating new variations.

Document template intent

Each template should clearly describe what type of asset it represents and how it should be used.

2. Design Clear Asset Hierarchies

The AF hierarchy organizes assets into logical structures.

A common pattern mirrors the physical plant layout:

Best Practices for Hierarchy Design

Mirror physical reality

Where possible, align the hierarchy with the real plant structure.

This makes navigation intuitive for engineers.

Avoid overly deep hierarchies

Complex nested structures can make navigation difficult and increase maintenance overhead.

Keep hierarchy roles consistent

For example, avoid mixing equipment types and process groupings at the same level.

Separate equipment and functional views when necessary

Some organizations maintain multiple hierarchies for different perspectives:

• Equipment hierarchy
• Unit monitoring hierarchy
• Reliability hierarchy

3. Map Attributes to Tags Carefully

Attributes link AF models to underlying PI tags.

Incorrect mappings are one of the most common AF reliability issues.

Best Practices for Attribute Mapping

Validate tag references

Ensure attributes reference active tags and correct data sources.

Use data reference types consistently

Standardize the use of PI Point, Table Lookup, or other data references.

Audit attribute health regularly

Attributes referencing stale or missing tags can silently break analytics.

For tag health monitoring strategies, see: PI Tag Governance: Best Practices for Naming, Managing, and Cleaning Up PI Tags

4. Design Scalable AF Analyses

AF analyses allow teams to generate derived signals, KPIs, and alerts.

But poorly designed analyses can create maintenance challenges.

Best Practices for AF Calculations

Use templates for analyses

Attach calculations to templates so they automatically apply across assets.

Avoid event-triggers on high-frequency tags if possible

These may bog down system performance.

Document business logic

Each analysis should include clear descriptions of its purpose and assumptions.

Monitor performance

Large numbers of complex analyses can increase system load.

Regularly review analysis health and performance.

5. Manage Asset Framework Governance

Even well-designed AF models can degrade over time without governance.

Equipment changes, new analytics, and organizational shifts can introduce inconsistencies.

Governance Practices for AF

Track configuration changes

Understand when templates, attributes, or analyses are modified.

Audit dependencies

Know which dashboards, calculations, and reports depend on each asset.

Review template consistency

Ensure new assets follow established modeling patterns.

Detect broken references

Identify attributes connected to stale or missing tags.

These governance practices help maintain reliability as systems evolve.

For broader data governance frameworks, see: PI System Data Governance: Best Practices for Reliable Operational Data

Common AF Design Problems

Many PI environments encounter similar modeling challenges.

Examples include:

• Templates that no longer match equipment configuration
• Attributes referencing deprecated tags
• Inconsistent attribute naming across assets
• Calculations duplicated across multiple elements
• Dashboards relying on outdated AF structures

Over time, these issues reduce confidence in analytics and increase maintenance effort.

Scaling Asset Framework in Large PI Environments

Large industrial deployments often contain:

• Hundreds of thousands of tags
• Thousands of assets and elements
• Hundreds of AF analyses
• Multiple teams contributing to asset models

In these environments, maintaining AF reliability manually becomes difficult.

Teams often rely on automation to monitor:

• Attribute health
• Template consistency
• Analysis performance
• Tag dependencies

Automating AF Governance with Osprey

Tools such as Osprey help PI teams maintain reliable asset models as systems scale.

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

Osprey provides visibility into the PI ecosystem, helping teams:

• Identify attributes referencing stale or missing tags
• Track dependencies between tags, assets, and dashboards
• Detect broken or failing AF analyses
• Monitor template and hierarchy consistency
• Audit configuration changes across AF

By automating these checks, engineering teams can maintain reliable AF models without relying on manual audits.

PI Asset Framework Best Practices (Summary)

Strong AF environments typically follow several key practices.

• Design reusable templates for equipment types
• Build intuitive asset hierarchies aligned with plant structure
• Carefully map attributes to correct PI tags
• Standardize AF analyses through templates
• Implement governance to track configuration changes

Together, these practices help ensure the AF layer remains reliable and scalable.

Building Reliable Operational Data Models

Asset Framework plays a central role in transforming historian data into usable operational insight.

When AF models are well-designed, engineers can quickly understand equipment performance, build reliable dashboards, and scale analytics across operations.

But achieving these benefits requires thoughtful template design, clear hierarchies, and ongoing governance.

By following these best practices and monitoring AF health continuously, organizations can maintain reliable asset models as their PI environments grow and evolve.