Guide
The ultimate guide to managing your PI System Download now
Give PI admins, engineers, and citizen developers practical standards for building and maintaining a reliable PI System.
THE CHALLENGE
PI environments often grow across sites, teams, and use cases without a shared set of standards.
Poorly designed analyses, displays, AF models, and tag configurations can create unnecessary load and make systems harder to maintain.
Without clear guardrails, teams solve problems differently and technical debt grows with every new project.
1
1. Understand your environment
Review your PI architecture, team structure, and current challenges.
2
2. Teach practical patterns
Show common PI anti-patterns and better ways to build.
3
3. Define guardrails
Align on standards for development, governance, and change.
4
4. Create an action plan
Identify immediate improvements and longer-term priorities.
THE SOLUTION
Give your teams a practical playbook for building better in PI
The PI System Best Practices Workshop aligns administrators, engineers, and citizen developers on proven practices for performance, governance, and change control.
Teams learn what creates risk, what good practices look like, and how to apply consistent standards across PI System development.
The workshop is tailored to your PI environment, team structure, and priorities.
PERFORMANCE BEST PRACTICES
Build without creating unnecessary system load
Understand common patterns that affect PI Data Archive, Asset Framework, analyses, and PI Vision performance.
What this includes:
Analysis design and performance
PI Vision performance
Tag and data access patterns
Common system anti-patterns
AF & MODELING STANDARDS
Build Asset Framework models that remain maintainable
Establish consistent approaches for templates, attributes, calculations, naming, and asset structure.
What this includes:
AF modeling practices
Template standards
Naming conventions
Consistent asset structure
GOVERNANCE & OWNERSHIP
Create clear rules for how PI is managed
Define lightweight standards for ownership, development, review, and maintenance across teams.
What this includes:
Roles and ownership
Development standards
Review checkpoints
Documentation expectations
CHANGE & RELEASE PRACTICES
Reduce risk when PI configurations change
Teach teams how to test, review, communicate, and release changes without introducing unnecessary operational risk.
What this includes:
Change review
Testing practices
Release discipline
Change communication
COMMON USE CASES
When a PI Best Practices Workshop helps
Growing citizen development
Give engineers guardrails before local development creates system-wide problems.
PI performance issues
Reduce patterns that create unnecessary analysis and display load.
Inconsistent AF development
Align teams on common modeling and naming standards.
Multi-site standardization
Create a shared PI operating model across sites and teams.
New PI teams
Give engineers a practical foundation for building and maintaining PI.
Migration & modernization
Improve standards before carrying technical debt into a new environment.
Frequently Asked Questions
Get answers to common questions about the workshop
GET STARTED