PI Interfaces

Welcome to the PI Interfaces feedback page!

We created this forum to hear your ideas, feature suggestions and feedback on PI Interfaces. 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.
  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Allow Buffer to communicate with other buffer

    Currently the PI Buffer Subsystem only has the capability to speak directly with the Data Archive. This setup can have a negative impact on your Cyber Security setup as you are not able to leverage the DMZ between the IT/OT networks as it is designed.

    This request is to allow the PI Buffer Subsystem to communicate with another buffer subsystem to act as a relay to the data archive and would allow all cyber security requirements to be met.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback. While we are declining this functionality request for direct implementation in PI Buffer Subsystem, we encourage you to check out PI Adapters. PI Adapters were designed with use cases similar to the one described here and we hope that they will meet your needs.

  2. UniInt should include a test mode for all interfaces that collects data but does not send it to PI.

    This functionality would allow users to test the connection to the data source and inspect the data that is retrieved without sending it to PI. That data might be written to a text file, for example.

    This would allow users to verify settings and data integrity without needing to delete archived values, for example. Potentially, this functionality would also have some type of PI point selection so that user would be able to select which tags the interface should use for this test mode, rather than using all tags (The interface would essentially assume that all other tags have scan…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    We have reviewed this idea, and it’s not something we plan to implement. Even though we are declining this idea for now, it is still open to comments. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!

  • 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
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED