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.

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. Add a Trace Route feature to PI Ping interface

    Add ping -i feature to the interface and allow for either the output of the ping time or destination in the PI tag.

    Case: This will allow for IT to monitor the network path taken in communication from one site to another. If the route has changed in the communication of devices, we will be able to track it in PI and know exactly when the route changed.

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

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  2. Allow PItoPI APS connector to sync "Point Type" changes

    Currently (as of PI to PI Interface AutoPointSync Connector Version 1.5.0.7), it's not possible to sync changes to "Point type". (See pg 5 of user manual).

    Please make this possible in a future release.

    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 →
  3. Determine the packet loss of the ping (Ping Interface tag) out to another tag

    Scenario: I have a tag that pings site A. I have the response times, which quantifies the response times of the network, but this line is also a bit slow and we suspect packet loss, but I want that in a tag.

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

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  4. Add -f (Ping Switch) to OSIsoft Ping Interface

    Enhancement for Ping Interface to add -f switch 'Set Don't Fragment flag in packet. When sending large packets we do not want to Fragment.

    Case: When monitoring a site ping worked for small packets, however with large packets sent, the site showed packet loss which in turn was an actual hub issue missed when using Ping Interface.

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

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  5. PI UFL: Support String Interpolation for Print() Function

    Allow Print() function to evaluate runtime variables before outputting text to the log.

    For example: I have created a Counter variable that increments for each event that is successfully sent to PI. I would like to output the final tally to the logs but printing the raw number [Print(Counter)] is not valuable without context. Instead, I would like to combine literal string text with the dynamic value of this Counter variable:

    Print("Events sent to PI: {Counter}")

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

    We’ll send you updates on this idea

    0 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  6. OPC DA interface to read data for advise and polled tags at startup

    If digital tags are part of advise groups and the flag to write "Intf Shut" is enabled in the OPC DA interface, then digital tags can read "Intf Shut" for hours/days/weeks, if the value does not change after an interface restart (for example, 2 pumps on the same duty, and they are only swapped every 2-3weeks). The unused pump reads "intf Shut" until it is started.

    It would be better for the OPC interface to get new values for ALL tags after a restart, regardless of whether the value has stayed the same before and after the restart, and timestamp…

    2 votes
    Sign in Sign in with OSIsoft
    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 →
  7. DeltaV Smart Connector configurability

    Smart Connector foo DeltaV should let user configure some default attributes for tags created:
    - User should be able to define what the default point security should be
    - User should be able to decide if tags should be created as Poll or Advise

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

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  8. Add subscribeCOV support to BACnet Interface

    My device only supports SubscribeCOV, but the PI Interface for BACnet only supports SubscribeCOVProperty. I would like the PI Interface for BACnet to support SubscribeCOV like the PI Connector for BACnet already does.

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

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  9. PI Buffer subsystem - management tool + robustness improvement

    1. Having the capability of acknowledging the message in the PI Buffer GUI and removing the "red flag" when messages acknoledged.
    2. Having the Buffer updated automatically when a tag is renamed, without having to restart the buffer.

    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 →
  10. Parameter for restarting the interface if no connection to the OPC server can be established after a defined period of time

    We use the Phoenix Contact Firewall with the OPC Inspector. When the OPC server restarts or breaks the connection for a few seconds, the firewall blocks all ports except port 135. After initial connection through this port, new firewall rules are dynamically established for DCOM connections. If connection break to OPC Server we have to restart interface manually.

    2 votes
    Sign in Sign in with OSIsoft
    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 →
  11. Provide support for Modbus function code 20

    Provide support for Modbus function code 20

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

    We’ll send you updates on this idea

    0 comments  ·  Modbus Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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.

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

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  13. Batch interface to support slightly different parsing logic

    Some of the fields incoming from the DCS are user entered and prone to errors. Please allow for the option to include slightly different logics to be able to filter out those user errors (such as empty spaces at the end of the string, etc).

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

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  14. POINDexter app be modified such that addresses beyond 64000 can be used

    POINDexter application be modified such that addresses beyond 64000 are able to be ‘tested’ / polled, rather than having to configure a tag to read those registers

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

    We’ll send you updates on this idea

    3 comments  ·  Modbus Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  15. Support string tags in PI Interface for CSI UCOS

    The newest version of UCOS now supports string tags.  Currently the CSIUCOS interface (1.0.0.22 as of writing) does not support these types of tags.

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

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  16. PI-SNMPTrap interface request support for SNMPv3 trap

    PI-SNMPTrap interface currently only has support for SNMPv1 and SNMPv2C trap. Feature request for PI-SNMPTrap interface to include support for SNMPv3 trap.

    Monitoring of snmp traps originating from CISCO switch devices require support for SNMPv3 trap.

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

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  17. PI Interface for GE HABConnect support of SCTIME request

    Currently, the PI Interface for GE HABConnect supports FLDTIME requests, which provides the timestamp of the field device.  In the absence of this, the default is the timestamp of the Sampler when HAB API makes an unsolicited update to the interface. 

    If SCTIME was a request that was supported, the timestamp that the sampler received data from the field device could be returned instead.  This would be helpful for two reasons. 

    1.  As an alternative to FLDTIME: SCTIME would standardize the timestamps coming in when field devices are not on synced time clocks

    2.  As an alternative to the update…

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

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  18. Source and destination tag mapping list

    Customer would like the ability to have PItoPI create a list of tags that includes the FULL name of the source tags, as well as the destination tags they are mapped to.  This will greatly assist in managing tags that are being sent to a remote customer.

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

    We’ll send you updates on this idea

    0 comments  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  19. 2 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  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.

    2 votes
    Sign in Sign in with OSIsoft
    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