Troubleshooting PI ProcessBook and PI Vision Data Discrepancies: Why Are My Values Garbled?

OSIsoft PI users sometimes face the perplexing situation where ProcessBook displays values that don't seem to make sense—commonly zeros or ones—while PI Vision shows accurate, expected data. This mismatch can create operational confusion and impact trust in your data displays. In this article, we’ll explore common reasons for such discrepancies, possible causes, and best practices to resolve or prevent this issue.

Common Scenario: ProcessBook Shows 0 or 1, PI Vision Shows Correct Data

Let’s imagine you open a ProcessBook display, and the data for a particular tag only flips between 0 and 1. However, looking at the same point in PI Vision, you see the full range of correct, expected measurements. Why does this happen?

Diagnosis Steps

1. Check Tag References

It’s possible that ProcessBook is incorrectly referencing the wrong PI Tag. This can occur if, for example, a tag in the display was accidentally changed or corrupted (sometimes due to file merges, bulk edits, or script updates). PI Vision, on the other hand, is correctly referencing the intended tag.

• Action: Open the display in ProcessBook Design mode and inspect the tag configuration for all affected symbols. Compare the tag name (case sensitive) to the correct tag being displayed in PI Vision.

2. Inspect Tag Data Types

If the referenced tag in ProcessBook is of a Boolean or integer type used for status (0/1), but the intended tag is analog or digital with a wider value range, this would explain the mismatch.

• Action: In PI System Management Tools (SMT), verify the data type of both tags. PI Vision often references AF attributes, which may have back-end configuration differences compared to ProcessBook’s direct tag references.

3. Display File Corruption/Tag Mapping Issues

Widespread issues across multiple display files are unlikely to be from manual errors. Sometimes display files become corrupted or misaligned through batch editing, copying, or even historical ProcessBook macro execution.

• Action: If multiple displays exhibit the issue, review any recent bulk display updates. Use PI Builder to quickly audit symbols and referenced tags in affected files. Compare lists against the reference (e.g., PI Vision displays or original design specs).

4. Reference Synchronization and Display Links

ProcessBook and PI Vision do not inherently synchronize their references. If you recently performed migrations or bulk edits, certain tools (like PI ProcessBook-to-PI Vision migration tools or scripts) may map tags incorrectly.

• Action: Audit migration logs and script changes if a migration or update has occurred. Confirm that any mapping logic aligns tag or AF attribute references correctly.

Best Practices to Avoid and Fix Discrepancies

• Version Control: Maintain source control on display files. Always keep backups prior to major edits.
• Tag Verification: Regularly cross-check tag references in all visualization layers. Standardize tag naming conventions.
• Bulk Editing Tools: Use PI Builder to audit and correct tag mappings in multiple displays efficiently.
• Data Type Documentation: Document and review PI Tag data types—mismatches are common sources of confusion.

Conclusion

While it can be unsettling to notice diverging values between ProcessBook and PI Vision, a systematic review of tag references, data types, and recent changes can quickly identify the issue. Auditing references and using toolsets like PI Builder or SMT can help align your displays and ensure consistent, trustworthy data visualization across all PI tools.

If you've experienced similar issues or have additional tips, share your experiences below!