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

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

    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 →
  3. 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 →
  4. 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 →
  5. 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.

    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. 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 →
  7. 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 →
  8. 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 →
  9. UFL Designer should include a test mode to verify INI behavior with a data file.

    One can do this, to some extent, piecemeal with functionality the UFL Designer already has. However, it's a very manual process and does not actually have a way to show what data would be sent to PI for a particular file. An explicit test mode or test function, where the Designer outputs what the results might be for a supplied data file (Values of each variable, what would have been sent to PI, et.c) would be very helpful in building and verifying INI files.

    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 →
  10. 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 →
  11. Option for PI Interface for UFL to purge read-only files

    Create an option to allow the PI Interface for UFL to delete files with the read-only attribute.

    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 →
  12. 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 →
  13. BACNet: Add support for Conversion Factor PI Point attribute to PI Interface for BACNet

    Add support for Conversion Factor PI Point attribute to PI Interface for BACNet.

    Note: This was previously Enhancement 118928.

    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 →
  14. 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 →
  15. Streamlined management of PI Interface for SNMP .pwd file

    When using the interface to gather data for hundreds of SNMP devices, managing the .pwd file becomes very burdensome due to an inability to format the file. Comments are helpful in sorting devices, but they are removed upon encryption. It would be nice to see a tool that helps with the management of passwords.

    2 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 →
  16. Preferring a primary interface failover member

    hen the primary Interface becomes available and healthy again, it becomes "back up". I need the primary Interface to become the "primary" whenever it is healthy.

    https://pisquare.osisoft.com/thread/42591-revert-back-to-primary-data-collector

    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 →
  17. Buffering Manager - add metrics for each buffered interface

    When validating/troubleshooting data flow issues, it would be helpful to see metrics on which interfaces are actively sending data to the buffering subsystem via Buffering Manager. If an interface is in a bad state or stopped, it would be obvious which interface is having issues since the count would be zero. Currently the counts in the buffer queue are for all interfaces, so this only gives the user an idea on whether the buffer subsystem is forwarding data to the data archive, without knowing which interfaces this data is coming from.

    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. PI Buffer Subsystem doesn't use the user who is logged in

    PI Buffer Subsystem must have a option to set up the user account is logged instead of using Windows Domain or Local account that is running the windows service. This is a huge security issue when using Buffer on client computer to send manual data because you will need to create a Mapping or Trust and give permission in so many pi points when the user logged on computer should have access to write in few pi points.

    Please prioritize this one!

    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 →
  19. EFGEN - Allow Active Point Trigger Based on Specific Value/Logic/Calculation

    Using EFGen, currently an EF can only be triggered based on the zeroth state of the Active Point. This makes is impossible to trigger different events based on specific values of a single PI Tag.

    I am trying to implement a batch structure using Event Frames with production run as the parent and different phases of the run as children. I have a single PI Tag that lists the current phase of the run in real time. It would be nice to be able to trigger the phase child events based on the specific string values of this tag.

    PI…

    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. Improved handling of PI Write failures

    Provide a configuration option in UniInt interfaces, to enable shutdown of the interface if it consistently receives error messages when attempting to write to PI. Recently had an interface successfully connect to PI but not achieve write access to its tags; would've been nice to have this interface gracefully shut down or restart, and allow its UFO failover partner to serve the data flow

    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 →
  • 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/PREVIEW
COMPLETED