All ideas

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.

Way forward now is utilizing PI AF in managing PI tag. Hence by having a feature or tool to auto register or create AF attribute when a PI tag is created will be helpful in promoting and leveraging PI AF as a single source and platform in utilizin...

Currently, in order to set limits (data validation) values for a PI tag, it must be set in a tour run for a specific tag. I think the best solution going forward would be to allow users to set and modify global limits (data validation values) with...

It would sure be nice if OSI had a way to better manage users access, because we know there are a lot of people who have the client tools but move to a different job or end up not needing them, so we want to pull their license/programs away and gi...

As a user, I want to track asset connectivity changes over time, so that I can visualize and analyze interdepedencies of assets over tiem.