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. Integrate PSH data with enterprise monitoring tools

    I'd like PSH to integrate with Enterprise Monitoring Tools such as Splunk or MS SCOM so that I can see PI System Health data in one console (with my enterprise monitoring solution).

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

  2. PSD to report on SQL Server install

    I would like PSD to report on the SQL Server install. SQL Server is a core component of a PI system as it is required by AF, and used by PI Vision and PI Manual Logger. Similar to the OS information, I want to know where SQL Server is installed in my landscape, and what flavor (Enterprise, Express, etc.) & version.

    In the future I would also like PSH to monitor the SQL Server service and report when it stops/fails/etc.

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

  3. Collect more information about the host operating system environment. For example: is it running Windows Core

    As a system administrator or as an upgrade implementation planner, I need to know the operating system environment that is hosting the software. mPI (Managed PI) collects information about the host OS version, whether physical or virtualized, and whether 32-bit or 64-bit. mPI transferrs this inventory infomation to the OSIsoft NOC where it is visible to NOC Engineers, EPMs, CoEEs, and customers. mPI should also capture whether the host OS is running as Windows Core. This should be feasible since it is available as a registry entry.

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

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

  7. Have PSD detect PI client tools installs

    In our landscape, we usually create an ‘Admin’ server for each major PI system and install all the client tools on it for support staff to use for bulk work because it is normally easier (rather than their desktops) due to the admin servers being faster and closer to the PI/AF servers, and they require their administrative security account, rather than their desktop account. We have had use cases where we need to know what version of a client tool is installed everywhere (in the server landscape) so we know which ones need to be upgraded to a newer version.…

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

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

  11. 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 →
  12. 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 →
  13. 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.

  14. 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 →
  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. 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 →
  18. 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 →
  19. 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 →
  20. 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.

  • 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