Manageability

Welcome to the PI System Manageability feedback page!

We created this forum to hear your ideas, feature suggestions, and feedback on how we could make the PI System more manageable. Manageability covers different aspects, including but not limited to, monitoring, deployment, upgrade, and managing different configurations. Please suggest your most important features and design change ideas on this site, and vote for your favorite ideas.

Please note that your ideas and comments posted here are visible to all other users.

  • For bugs, please open a case with OSIsoft Tech Support through myOSIsoft Customer Portal  (https://my.osisoft.com) instead of sharing them on this site.
  • For documentation feedback and bugs, please report to documentation@osisoft.com instead of sharing them on this site.

How can we improve the manageability of OSIsoft suite of products?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Allow PI Buffer Subsystem (pibufss) to be managed by Powershell tools for the PI System

    Powershell is a convenient way to administer a PI Server. One limitation, however, is that there is no built-in functionality for administering pibufss with powershell. Please add PI Buffer Subsystem (pibufss) management to Powershell tools for the PI System.

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  2. Make message logs easier to export in bulk

    Tech support often asks customers for message logs in bulk. The PISDKUtility and SMT are not good for this because they run out of memory if you try to load too many messages. The only way to export the logs is to use the command line pigetmsg utility and pipe the output to a text file, but PI users who haven't used it before often run into syntax errors when using it. It usually requires a step-by-step explanation, which also requires a caveat that pigetmsg.exe is in a different folder if the machine is a PI Server (%piserver%adm vs. %pihome64%adm).

    4 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  3. Securing the PI System

    As an ICS systems engineer, I need to understand and easily configure Authentication and Authorization settings to secure the PI System from the point of data collection to data access and remote display viewing.

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  4. Guidance on best practices

    As an ICS systems engineer, I need to provide broad, real-time access to operations data using the PI System while assuring that sensitive systems are defended appropriately via standard security zones and authorization mechanisms. So I need guidance on best practices in deployment and security as well as tools to verify them.

    8 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Security  ·  Flag idea as inappropriate…  ·  Admin →
  5. Monitor data throughput for PI OPC DA interface

    Just knowing if the interface service is running is not enough. Knowledge of data throughput, events/sec, of PI OPC DA interface is needed to know if the OPC DA server is up and running and there are no connection issues.

    3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Health  ·  Flag idea as inappropriate…  ·  Admin →
  6. Limit log file transfer to only essential context

    For remote assets, transferring the entire log files could be taxing on the network. Limit the transfer to aspects of the log that are essential for troubleshooting.

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Health  ·  Flag idea as inappropriate…  ·  Admin →
  7. Auto register AF attribute when creating PI tag

    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 utilizing PI data.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  8. Auto register AF attribute when creating PI tag

    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 utilizing PI data.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  9. add PI License serial number

    add the PI license Serial number to the report

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Directory  ·  Flag idea as inappropriate…  ·  Admin →

    OSIsoft is committed to providing customers with a more manageable system. We are working hard to solve the problems of deployment, security, and standardized health messaging within our products.

    PI System Health and PI System Directory were early steps in the manageability story, and we learned a lot thanks to significant customer testing and feedback. We also discovered that there is much more to making a truly manageable system through these engagements.  In order to pursue these larger needs surrounding manageability, we will not be releasing PI System Health, and we are putting PI System Directory on maintenance so that our engineering resources can be allocated toward these bigger efforts. As such, there are no additional enhancements for PI System Directory planned at this time.

    As a result, the status of this suggestion will be changed back to “No status” for the time being. Future status updates will be communicated here.

  10. Support duplicate performance monitoring PI points with mPI

    Managed PI should check to see if performance tags already exist and either allow duplicates or provide a way to change the performance points it wants to create.

    6 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  11. Automatically deselect components list items after applying labels

    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.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Directory  ·  Flag idea as inappropriate…  ·  Admin →

    OSIsoft is committed to providing customers with a more manageable system. We are working hard to solve the problems of deployment, security, and standardized health messaging within our products.

    PI System Health and PI System Directory were early steps in the manageability story, and we learned a lot thanks to significant customer testing and feedback. We also discovered that there is much more to making a truly manageable system through these engagements.  In order to pursue these larger needs surrounding manageability, we will not be releasing PI System Health, and we are putting PI System Directory on maintenance so that our engineering resources can be allocated toward these bigger efforts. As such, there are no additional enhancements for PI System Directory planned at this time.

    As a result, the status of this suggestion will be changed back to “No status” for the time being. Future status updates will be communicated here.

  12. Apply filter to component name or display name in PI System Directory

    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.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Directory  ·  Flag idea as inappropriate…  ·  Admin →

    OSIsoft is committed to providing customers with a more manageable system. We are working hard to solve the problems of deployment, security, and standardized health messaging within our products.

    PI System Health and PI System Directory were early steps in the manageability story, and we learned a lot thanks to significant customer testing and feedback. We also discovered that there is much more to making a truly manageable system through these engagements.  In order to pursue these larger needs surrounding manageability, we will not be releasing PI System Health, and we are putting PI System Directory on maintenance so that our engineering resources can be allocated toward these bigger efforts. As such, there are no additional enhancements for PI System Directory planned at this time.

    As a result, the status of this suggestion will be changed back to “No status” for the time being. Future status updates will be communicated here.

  13. Provide conditional operators when filtering versions in PI System Directory

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

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Directory  ·  Flag idea as inappropriate…  ·  Admin →

    OSIsoft is committed to providing customers with a more manageable system. We are working hard to solve the problems of deployment, security, and standardized health messaging within our products.

    PI System Health and PI System Directory were early steps in the manageability story, and we learned a lot thanks to significant customer testing and feedback. We also discovered that there is much more to making a truly manageable system through these engagements.  In order to pursue these larger needs surrounding manageability, we will not be releasing PI System Health, and we are putting PI System Directory on maintenance so that our engineering resources can be allocated toward these bigger efforts. As such, there are no additional enhancements for PI System Directory planned at this time.

    As a result, the status of this suggestion will be changed back to “No status” for the time being. Future status updates will be communicated here.

  14. Expose PI components on the UI based on end user's role

    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 is relevant to them.

    2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Health  ·  Flag idea as inappropriate…  ·  Admin →

    OSIsoft is committed to providing customers with a more manageable system. We are working hard to solve the problems of deployment, security, and standardized health messaging within our products.

    PI System Health and PI System Directory were early steps in the manageability story, and we learned a lot thanks to significant customer testing and feedback. We also discovered that there is much more to making a truly manageable system through these engagements.  In order to pursue these larger needs surrounding manageability, we will not be releasing PI System Health, and we are putting PI System Directory on maintenance so that our engineering resources can be allocated toward these bigger efforts. As such, there are no additional enhancements for PI System Directory planned at this time.

    As a result, the status of this suggestion will be changed back to “No status” for the time being. Future status updates will be communicated with here.

  15. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  16. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  17. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Health  ·  Flag idea as inappropriate…  ·  Admin →

    OSIsoft is committed to providing customers with a more manageable system. We are working hard to solve the problems of deployment, security, and standardized health messaging within our products.

    PI System Health and PI System Directory were early steps in the manageability story, and we learned a lot thanks to significant customer testing and feedback. We also discovered that there is much more to making a truly manageable system through these engagements.  In order to pursue these larger needs surrounding manageability, we will not be releasing PI System Health, and we are putting PI System Directory on maintenance so that our engineering resources can be allocated toward these bigger efforts. As such, there are no additional enhancements for PI System Directory planned at this time.

    As a result, the status of this suggestion will be changed back to “No status” for the time being. Future status updates will be communicated with here.

  18. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Directory  ·  Flag idea as inappropriate…  ·  Admin →

    OSIsoft is committed to providing customers with a more manageable system. We are working hard to solve the problems of deployment, security, and standardized health messaging within our products.

    PI System Health and PI System Directory were early steps in the manageability story, and we learned a lot thanks to significant customer testing and feedback. We also discovered that there is much more to making a truly manageable system through these engagements.  In order to pursue these larger needs surrounding manageability, we will not be releasing PI System Health, and we are putting PI System Directory on maintenance so that our engineering resources can be allocated toward these bigger efforts. As such, there are no additional enhancements for PI System Directory planned at this time.

    As a result, the status of this suggestion will be changed back to “No status” for the time being. Future status updates will be communicated here.

  19. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  20. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3
  • Don't see your idea?

Feedback and Knowledge Base

Posted ideas will have one of the following statuses.
Full definition of these statuses can be found on the Home Page.
No status
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED