Best Practices
Sample description for Best Practices
Understanding AF GUID Dependencies in OSIsoft PI System Client Applications
When recreating AF data via XML import, new GUIDs are assigned to elements. While OSIsoft PI client tools typically reference elements by path, issues can arise where GUIDs are leveraged (notably in Notifications). Best practice is to store both GUID and path, ensuring reliability across migrations.
Roshan Soni
How to Retrieve the Instrument Tag of a PI Point Using AF SDK: Understanding Lazy Loading
Learn why PI Point attributes like Instrument Tag may appear missing in AF SDK, and how to explicitly load them using lazy loading and bulk loading techniques for optimal performance.
Roshan Soni
Using Serialized .NET Objects for AFPlugin Configuration: A Time-Saving Technique
A modern, developer-friendly approach to managing AFPlugin configuration—store serialized CLR objects and forget about manual string parsing.
Roshan Soni
Secure Storage of Connection Strings and Passwords in PI AF: Challenges and Solutions
This post explores secure methods for storing connection strings and passwords in PI AF, including encryption strategies, AF security, and secret management best practices in distributed systems.
Roshan Soni
Performance Equation Pitfalls: Logic, Tag Update Synchronization, and Data Freshness in PI System
Troubleshooting why a Performance Equation (PE) in PI System returns unexpected results. Understand the role of Boolean logic, tag update rates, and triggering methods, and learn practical solutions for robust tag comparison in PE analysis.
Roshan Soni
Best Practices for Migrating Your PI System from 32-bit to 64-bit
Upgrading your PI System from 32-bit to 64-bit enhances scalability and performance. A clean install of the 64-bit PI Server, followed by data transfer from the old server, is recommended. However, verify interface and component compatibility, as some—like Managed PI and RtWebParts—may require a 32-bit environment.
Roshan Soni
Can You Create a PI Collective with Different PI System or Windows Versions?
It's not recommended to create a PI Collective with differing PI System versions; exact version matching is enforced for new members. Minor version mismatches are allowed temporarily during upgrades, but not for long-term operation. Windows OS version is generally not a compatibility concern for PI Collectives.
Roshan Soni
Best Practices for Naming Your PI System Collectives
Naming your PI collectives wisely can enhance system management and scalability. Explore best practices to create effective, future-proof naming conventions.
Roshan Soni
About Best Practices
Explore our collection of expert articles about Best Practices. Our content is written by experienced PI System professionals and covers everything from basic concepts to advanced implementation techniques.
Whether you're new to PI System or an experienced engineer, you'll find valuable insights, tutorials, and best practices to help you get the most out of your industrial data infrastructure.