PI Interfaces

Welcome to the PI Interfaces feature suggestion box. We created this forum to hear your ideas, suggestions and feedback.

Please suggest your most important features and design change ideas on this site! Also vote for your favorite features now! We welcome your feedback.

  • NOTE: for documentation feedback and bugs, please report to Documentation@osisoft.com rather than entering them on this site.

How can we improve PI Interfaces?

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

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Double check window required when deleting an instance in PI Event Frames Interface Manager

    As a PI System Admin, I would like to see a confirmation window (acceptation pop-up message), when deleting Interface instances in PI Event Frames Interface Manager. This would minimize the deletion of the instances by error.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  2. 1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  3. PI to PI interface should perform first scan so that future data can recovered

    /fd parameter is only used while performing real-time scan. If scan rate is set to a higher value such as a day, the user would need to wait for the first scan (after a day) to get future data. This should be done at interface startup. For use case see notes for Case # 895278.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  4. PI Interface for OPC DA retry writing data when it receives a CONNECT_E_ADVISELIMIT error.

    I would like the ability for the PI Interface for OPC DA to retry writing data when it receives a CONNECT_E_ADVISELIMIT error. Certain OPC servers return a CONNECT_E_ADVISELIMIT error when write requests are received in quick succession, and having a setting to retry writing the data would be better than the current method of performing a restart of the service. The issue is exacerbated when the network is unstable.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  5. Embed more videos inside of help topics

    Add the YouTube help videos that exist on the OSIsoft Learning channel to the "Help" section of ICU. For example, the UFL designer YouTube videos would appear alongside the corresponding documentation that should be accessible from ICU > Help > Interface Manual...

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Help / Documentation / Videos  ·  Flag idea as inappropriate…  ·  Admin →
  6. Quindar interface should allow tracing of values from the data source for a specified PI point.

    The PI Interface for Quindar SCADA should have an option to log all values and timestamps from the data source (Prior to any processing by UniInt) for a specified PI point.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  7. History recovery from multiple tags with one output tag

    I have a scan-based output point writing multiple PI values to the relational database as described here:
    https://livelibrary.osisoft.com/LiveLibrary/content/en/int-rdbms-v4/GUID-1A194D2B-388B-4FD7-8B82-D85EDDBBC572

    I would like to perform history recovery for such an output point, but this is currently not possible because the output point is scan-based:
    https://techsupport.osisoft.com/Troubleshooting/KB/KB01139/

    Since event-driven tags can have only one source tags, I cannot recover historical data from multiple PI tags with only one output tag.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
  8. SNMP Interface outputs a .txt file that includes the SNMP devices that are timed out

    For the SNMP Interface, the suggestion would be to have the interface output a .txt file that includes the SNMP devices that have lost connection with the interface. This could be useful when there is a high volume of SNMP devices that connect to the interface.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  9. Consistent Naming Convention for the UniInt Health Points Across Versions for the SNMP Interface

    The health point names for the Read_Only 1.6.8.1 SNMP Interface have a different naming convention than the health points for Read-Write SNMP Interface 1.5.1.306. In order to keep monitoring consistent across version upgrades, the suggestion is to keep naming convention of the health points the same across versions.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow PI Interface for EMDVB to have the ability to define the source system Time/TimeZone offset.

    PI EMDVB interface stops because of time difference between SQL and PI servers:

    "Error, SQL Server is ahead of PI Server more than 30 seconds, please adjust clocks. "

    That means we should adjust the (SQL server) DCS clock. However 30 seconds seems a short time to me.

    I would like the PI Interface for EMDVB to have the ability to define the source system Time/TimeZone offset.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  11. Read-only versions of the PI Interface for RDBMS

    Several PI Interfaces that previously only had read-write versions (e.g. OPC DA, SNMP) now have read-only versions to help protect the data source from unintended or malicious edits.

    We need the same for the PI Interface for RDBMS. Since the PI Interface for RDBMS already comes in 2 versions (32-bit and 64-bit), we will now have 4 versions. The documentation must be clarified so that the user knows exactly which install kit to download.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
  12. Improve error messages in PI ICU

    Currently if you attempt to create a service for a UniInt interface without a service ID you get an error message "Unknown Error" (see attached screenshot)

    Generally review and improve error messages to be meaningful but also allow the creation of services without service IDs if the user wishes.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI ICU  ·  Flag idea as inappropriate…  ·  Admin →
  13. Make UserID and ReviewerID available from BatchQuestion table for PI Interface for Wonderware InBatch

    Currently UserID (DoneBy_User_ID) and ReviewerID (CheckBy_User_ID) cannot be read from the BatchQuestion table when using PI Interface for Wonderware InBatch. These fields are important to know who answered the question and who confirmed/checked the question.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  14. Allow Tag Template Triggers to trigger on blank placeholders

    Currently, Batch Interface Framework interfaces implement tag template triggers that can trigger whenever a placeholder has any value. These interfaces should also support triggering when a placeholder does not have a value. For example, our SISBatch data source has separate columns for Operation and Phase information. We would like to record the value of the [DESCRIPT] column in a tag only for non-phase batch events (i.e. trigger the tag template only when the [PHASE] placeholder is blank).

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  15. More external resources for high latency networks with PItoPI, specifically with satellite networks

    I have been working with a customer who works with oil rigs and satellite networks and they requested that more external resources be available for how to efficiently operate PItoPI in a high latency environment. Currently there is only one internal document that may be out of date.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Help / Documentation / Videos  ·  Flag idea as inappropriate…  ·  Admin →
  16. Suppress the message "exception attributes corrected through the SDK read"

    In the PI Interface of UFL we would like the option to suppress the message: "exception attributes corrected through the SDK read" for values of excmax larger then 9hrs.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  17. Name support in BACnet Network Discovery Tool

    Can you remove the restriction to use only an IP address in the BACnet Network Discovery Tool?  The interface will correctly load and poll tags to a network device referenced by name instead of IP, however the Discovery Tool has the limitation of being IP only.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  18. Upgrade the PI Interface Configuration Utility to a responsive web-based user interface

    OSIsoft's migration from PI Interfaces to PI Connectors is very slow. Even after the migration is complete, many PI Interfaces will not be upgraded to PI Connectors, so users will continue to use the PI Interfaces and the PI ICU to configure them.

    Please consider upgrading the PI ICU to a responsive web-based user interface, much like the PI Connector administration pages. The PI ICU is currently very cramped, very grey, not resizable, and a bit hard to navigate.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI ICU  ·  Flag idea as inappropriate…  ·  Admin →
  19. debug an arbitrary number of tags belonging to a PI OPC interface instance

    It is currently possible to debug one tag, or all tags. Logging timestamp and data for all tags is expensive and make logs harder to read, so one one would like to select an arbitrary number of tags.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  20. Accept weeks and years in the relative time syntax for history recovery start and end times

    For whatever reason, times such as *-1w or *-1y are not accepted, but times such as *-1mo and *-1d are OK.

    Please make the PI Interface for RDBMS accept the same relative times that other PI programs accept.

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for RDBMS  ·  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