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.
  1. The old PI roadmap allowed us to perform some software release planning. Can you bring something like that in?

    The old Roadmap had planning lists, such that we had some clue to product updates and we could plan our internal software release schedules. The new roadmap is a great glossy for general long term strategies, but doesn't help us know what software may be released in the next quarter or year. Can you bring something like that back. Maybe a new name, since "Road map" has changed, but maybe "product planning guide"? Or, please pick a new name. Thanks.

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

    We’ll send you updates on this idea

    10 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  2. Security tool that allows management of PI Data Archive, Vision, and AF security settings

    PI System Administrators would benefit from a client or PI SMT extension that supports auditing and modifying user access. This includes mapping Active Directory roles to PI Identities, managing PI Database and Point access, managing AF Database and element access, managing PI Vision access, and managing permissions for folders and displays within PI Vision.

    This would be useful for administrators who manage large teams, complex PI Systems, and/or environments where appropriate data access is critical to security policy compliance.

    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 →
  3. Configuration as Code PI System wide

    "As a business owner, I want to set up change control procedures where any change to the PI System, be it the data archive, asset framework, PI Interfaces, PI Connectors, or any other component is done through a change in source controlled configuration files so I can track change requests, assign them to reviewers, and automatically apply them to production after the changes are applied to a test environment and satisfy automated tests. The configuration should be flexible enough to work with other deployment scripts so new servers can be automatically provisioned and configured if the configuration requires it."

    Essentially…

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

    We’ll send you updates on this idea

    0 comments  ·  Testing  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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.

    7 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 →
  5. Integrate SSO for PI ML

    For better user manageability Single Sign On should be integrated into PI Manual Logger PC Client.

    1 vote
    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 →
  6. 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).

    8 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 →
  7. 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.

    11 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 →
  8. Add a column in PI System Directory showing the latest released version of PI Products

    It would be helpful to see if our PI system version is up to date and if not, what the latest released version is. This helps us with the upgrade planning.

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

    We’ll send you updates on this idea

    1 comment  ·  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.

  9. 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.

    4 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 →
  10. Possible integration of PI System Health with internal ticketing systems

    Make it possible for PI System Health to integrate/communicate with out internal IT ticketing system. This way, any health-related issue identified by PSH can be a trigger in our ticketing system.

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

    We’ll send you updates on this idea

    1 comment  ·  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 here.

  11. 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.

    1 vote
    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 →
  12. 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

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  13. 3 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.

  14. 3 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 →
  15. 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.

  16. Monitor the health of analytics/notifications

    As a user of asset-analytics and notifications, I need an  easy way to know that PI Analysis and PI Notifications services are in good health and that event frames/notifications are being generated/sent as expected

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

    We’ll send you updates on this idea

    5 comments  ·  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 here.

  17. I'd like NOC to monitor PI Vsion

    I'd like to have the NOC Service monitor the health of my PI Vision system.

    17 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 →

    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.

  18. 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.

    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 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.

  19. I'd like NOC to monitor Web API Services

    I'd like to have the NOC Service monitor the health of my Web API Services.

    17 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 →

    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.

  20. Add Support for DNP3 Interface

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

    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 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.

← 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/PREVIEW
COMPLETED