System Management

Changes to Tuning Parameters should be reported in the PI Message Log with the identity of the user who made the change.

With ARM64 devices based on the Snapdragon processor becoming more prevalent I would like to be able to install and use PI System Management Tools (PI-SMT) on such a device. Currently installation of PI-SMT fails on these devices, even though a lo...

I can be helpful when tracking down issues or troubleshooting past events what the values of tuning parameters were at a given time. Adding the ability to Audit this table would allow retrospective insight into tuning parameter configurations. A ...

PI system logging is currently fragmented across multiple location. This makes troubleshooting and log correlation difficult. Solution: Make logging consistent across all PI system applications. (ex: all logs stored in windows event log; all logs ...

When changes need to be made to PI Tags, AF Models or calculations, it is important to locate all the places where the changed item is being used to aid in change management.

As a PI Administrator with a test PI Server, I need to be able to easily promote configurations from our test environment to our production environment. Currently this is extremely difficult and a very manual process.

I want the ability to determine what PI System Configuration Changes (AF & PI Data Archive) are legitimate and approved, with the criteria of being able to focus on changes that occurred during a user defined time range. I want to minimize the...

As a PI System administator of a busy PI Data Archive, I find that my message logs are unwieldy. I can miss important messages in the flood of connection messages and other repetitive messages. I would like to be able to search my message logs whi...

Originally posted on PI Square at https://pisquare.osisoft.com/ideas/29295-individual-collective-members-health-data-matches-with-other-nodes We would like a way to know if a node in a collective is not receiving the same data as the other nodes....