Ideas

Currently, if a user tries to add a new event in the Archive Editor by specifying the timestamp first and then the value, an error message will appear. The entry order should not matter, as long as all of the required information is present when t...

As a general suggestion, please look through all the tuning parameter descriptions and fix any mistakes or inconsistencies between descriptions. This includes the ones that the user cannot see by default. All: Almost every tuning parameter descri...

The menu bar in PI System Management Tools has almost nothing in it. It would be cleaner if it were eliminated. File: Add Server can be moved to a button in the title bar of the Servers pane. Save Session Log can be moved to a floppy disk icon in...

As a PI System Administrator I would like to configure my own custom watchdog tag in PSH to help monitor data flow from my interfaces

I would like to be able to monitor the health of my DNP3 interfaces using PSH.

In the preview I saw at PI World, each event view had a list of the 3 most recent events.  That list will either be empty or have 3 items with the same name/description and a different date.  The important piece of information is the dat...

Each equipment/asset owner needs to only see the PI components (interfaces, etc) that pertain to data collection from their equipment. Making all interfaces we have on site visible to all users will make it difficult for asset owners to find what ...

It would be helpful to filter versions using conditional operators such as searching for all OPC interfaces < 2.6.

Applying name filters to either the component name or the display name would be helpful based upon the type of user using the product. When a Display Name has been provided, you can no longer filter on the original component name.

When applying labels, automatically deselect everything in the components list after pressing the Apply button to prevent accidentally applying labels to components that were still selected.