Demystifying PI Vision's Zoom Level Saving Behavior

In the world of industrial operations and process monitoring, tools like OSIsoft PI Vision are invaluable. They present data in visual formats that can be easily interpreted by engineers and operators. However, even these advanced tools have their quirks and limitations, as epitomized by user discussions around the saving of zoom levels.

The Zoom Level Conundrum

Users have noted inconsistent behavior when it comes to saving zoom levels in PI Vision displays, particularly in the 2019 and 2020 versions. This problem has prompted debates and confusion within the PI community, leading to multiple theories and user experiences.

What Users Are Experiencing

• Inconsistent Saving Behavior: Some users claim that they have successfully saved zoom levels in PI Vision 2019 as long as the display wasn't set to "Fit All". However, others dispute this claim, stating that zoom levels always revert to the original view upon saving.

• Attempted Solutions and Testing: Users have tried various methods to solve this, including extensive testing across different versions. One user's tests indicated that non-FitAll setups weren't persistent, adding to the confusion.

• Feedback and Historical Context: There has been a feedback request dating back to 2015, suggesting that the feature to save zoom levels has been on the wish list for quite some time, yet it seems to not have been fully integrated or consistently functional.

• Potential Memory Lapses: Some users speculate that they might be misremembering functionalities from older tools like ProcessBook, which might have behaved differently.

Exploring the Underlying Issues

The core of this issue seems to be a gap between user expectations and the software's behavior. Here are some possible areas where this discrepancy might be explored:

• Software Design and Updates: As PI Vision evolved, certain functionalities might have shifted, leading to confusion among users who previously used older versions or different tools like ProcessBook.

• Documentation and Communication: Clear and concise documentation often helps manage user expectations better. A gap in this area can lead to misunderstandings and assumptions about how certain features are supposed to work.

• User Experience and Feedback Integration: Ensuring user feedback is adequately reviewed and acted upon can help bridge these gaps in functionality or usability that end-users face.

Moving Forward

As users, the best course of action may involve collaborating directly with OSIsoft support teams, seeking clarifications, and staying updated with release notes and patch updates. Engaging in community forums also offers a platform to voice concerns and share solutions, further assisting in refining our collective knowledge and expectations regarding PI Vision's capabilities.

Ultimately, whatever the cause behind these discrepancies, they highlight the importance of robust development, testing, and user feedback mechanisms in complex software solutions like PI Vision.