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. PI Interface for GE HABConnect FLDTIME Support for COUNT Objects

    Currently only POINT/ANALOG fields support COUNT. This request would be to enhance the interface to additionally support the COUNT field.

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

    We’ll send you updates on this idea

    1 comment  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  2. PI UFL Interface can read input files from non-UNC paths such as Azure File share

    I would like the PI UFL Interface to be able to directly read from input files that are in non-UNC paths such as Azure File share, so I do not need to periodically copy the input files into another path.

    3 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 →
  3. UNIINT Interfaces and Connectors should be able to retry an output event if output write fails

    When an interface fails writing to a DCS system, the interface writes a failure status to the output tag and goes on.  User has requested an option to have an output tag retry after write failure. It would be good to have this functionality in all uniint interfaces as they are recompiled, starting with the OPC DA interface, also to have this added to PI Connectors. Retries could stop after x retries of 1 minute retries, or when a new output value comes in. Or some other policy could be worked out.

    3 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 →
  4. 3 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 Interface for CAISO Exclude Certain Batch Types

    We would like the PI CAISO interface to parse through the .XML files and exclude XMLs that contain certain specified <Batch Types>. Only certain batch types contain valid data for consumption.

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

    We’ll send you updates on this idea

    1 comment  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  6. PI BES Interface (i.e. PI EMDVB): aliasing of Unit Names

    Currently the interface creates PI UnitBatches or Event Frames associated to Units (PI Units or AF Elements) determined by some placeholders specified at the "Unit Procedure" level; the default is "[AREA]\[PROCESSCELL]\[UNIT]".
    Moreover the interface properly created a PI MDB or AF structure under an alternate module path, specified in "Batch Setup" section (/SMP parameter).

    It would be useful to have a way to specify different Units instead of the one determined by the [UNIT] placeholder (at least).
    As an example, suppose we want to register unit batches for a PI Unit called Reactor1" when the [UNIT] placeholder values "U6-K54100", and…

    3 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 →
  7. PI EMDVB Interface - Rename Parsed Files

    PI EMDVB Interface - Rename Parsed Files.  Files that get renamed to .999 is no longer available with PI EMDVB.  This file renaming feature was very useful from a system maintenance perspective.  We would easily remove .999 from the active EVT folder and move to an offline directory.  Currently with PI EMDVB, there is no obvious visual indication that the EVT file was parsed completely.

    3 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 →
  8. 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
    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 →
  9. PI ICU should not allow PItoPI COLD failover configuration

    As of version 3.8.1 COLD failover is no longer supported by the PI to PI Interface (https://techsupport.osisoft.com/Troubleshooting/Enhancements/19255OSI8). However, the PI Interface configuration utility still allows COLD failover to be selected. This leads to an invalid configuration and the interface refuses to start.

    PI ICU should not allow the selection of COLD failover as it does not allow HOT failover, both of which are not supported by the interface.

    3 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 →
  10. DNP3: handle invalid timestamps from the RTU

    If the RTU provides a timestamp of 0 when using RTU provided timestamps, which does not conform to the DNP3 spec, allow the option to timestamp the event with PI time or drop the event altogether.

    Note: This was previously Enhancement 123208.

    3 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 →
  11. 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 →
  12. 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 →
  13. 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 →
  14. 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 →
  15. 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 →
  16. For PItoPI interface having a source PI-HA collective, allow failover on source automatically.

    This enhancement would allow the PItoPI interface to treat a source PI collective as a collective, rather than requiring PItoPI failover to be specified for collective members.

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