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

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

  2. PI System Connectivity Map

    Build a visual PI System connectivity map that shows how interfaces and servers (etc) are connected from so many different places.

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

    We’ll send you updates on this idea

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

  3. Alert on buffer queue corruption

    Detect when I have buffer queue corruption and alert on that issue.  Original post in NOC Services - https://feedback.osisoft.com/forums/596665-noc-services/suggestions/18788656-alert-on-buffer-queue-corruption.

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

    We’ll send you updates on this idea

    6 comments  ·  Health  ·  Flag idea as inappropriate…  ·  Admin →
  4. Performance Counter for Critical, Error, and Warning messages.

    In addition to a performance counter for total messages sent into the PI log, it would be very useful to have performance counter to determine which of these messages are Critical, Error, or Warning messages. This way, users can monitor specifically when a certain type of message appears in the log, and even create Notifications around them.

    6 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 →
  5. Filling archive

    As a PI admin I want to get notified if a tag is overfilling my Archive, maybe due to missconfiguration of ex/Comp. Setting.

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

    We’ll send you updates on this idea

    4 comments  ·  Health  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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 →
  7. 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 →
  8. Detect if data is missing

    Have a way to detect if data is missing.

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