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 the same RTU Address to be used across different IP nodes

    The current implementation of the PI Interface for DNP3 does not allow the same RTU address to be used across different IP nodes. The PI Point Location3 attribute is used to specify the RTU address only. If a customer has multiple RTUs with the same address but on different IP nodes, they either have to reconfigure all of the RTUs to have different addresses, or create a new DNP3 interface instance for every IP node.

    Case example:

    Customer has 800 SEL-735 meters, each with a different IP address, and each with a DNP Address (RTU address) of 1. He has…

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

    We’ll send you updates on this idea

    1 comment  ·  DNP3  ·  Flag idea as inappropriate…  ·  Admin →
  2. Batch Framework Interfaces - Support of two byte languages

    Batch Framework Interfaces currently do not support two byte languages. Please add support of two byte languages to batch interfaces.

    9 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 →
  3. PI BACnet interface: add support for BACnet Setpoint object

    Add support for BACnet Setpoint objects in the PI BACnet interface.

    9 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 →

    Does this request refer to the Setpoint property of the Loop object type, the Setpoint_Reference property of that type, or something different? The interface currently cannot read Setpoint_Reference, but it can read Setpoint using a float32 PI point.

  4. Conversion Factor with PItoPI interface

    I would like to use a Conversion Factor for some PI Points that retrieve data via PI to PI. For example, on the source server the data is in volts. I would like to convert this data to kilo volts on the destination server.

    9 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 →
  5. Enhancement for Advise tags to poll  OPC server when Excmax expires

    Currently, when an advise tag does not get a value in an ExcMax period,  the interface will send the same value to PI over again without going to the OPC server (assuming that the OPC interface has not disconnected from the OPC server during that interval). This can cause the OPC interface to continuously send the wrong value to PI over and over again. ( last known good value) with current timestamp

    This enhancement would allow the interface to behave in the following way:
    When advise tags are configured and ExcMax expires, the interface would poll the OPC server for…

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

    We’ll send you updates on this idea

    2 comments  ·  PI Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support multiple Modbus devices on the same machine

    Add support for multiple Modbus devices (using the same IP address but different port numbers) on the same machine. For example, the interface could allow the user to configure something like this:

    /dn= xxx.xx.xxx.xx:43120,/cn=1,/polldelay=0,/to=2,/rci=30,/writedelay=0,/debug=0,/disabled=0
    /dn= xxx.xx.xxx.xx:43122,/cn=1,/polldelay=0,/to=2,/rci=30,/writedelay=0,/debug=0,/disabled=0
    /dn= xxx.xx.xxx.xx:43124,/cn=1,/polldelay=0,/to=2,/rci=30,/writedelay=0,/debug=0,/disabled=0
     
    Note: This was previously Enhancement 121980.

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

    We’ll send you updates on this idea

    2 comments  ·  Modbus Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  7. and operator

    Add a function that can be used in the UFL Configuration File to perform bitwise operations. For example, a function similar to the AND operator in Performance Equations and Asset Analytics.

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

    We’ll send you updates on this idea

    1 comment  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  8. Customize UniInt Failover Sync File Permissions

    Prior to UniInt v4.6.0.60, UFO sync files created during interface startup would inherit file permissions from their parent folder (assuming child inheritance had been enabled on the folder).

    With UniInt v4.6.0.60, this behavior changed and now sync files created by the interface do not respect inheritance.  Instead, they are created with a standard ACL containing only the local "Administrators" and "Users" security groups.

    For users with complex file permission schemas, this change introduces additional, unnecessary configuration efforts that scale as interface numbers grow beyond the site-level. 

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

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  9. PI OPCtoCSV Tool: Filter by OPC ItemID

    The PI Interface for OPC DA is packaged with the PI OPCtoCSV tool which extracts all OPC Items. It is possible to filter the items by subbranch like the PI APS Connector for OPC DA interface, but unlike the APS Connector, it is not possible to filter by OPC ItemID using the PI OPCtoCSV tool.
    We have an OPC server with around 20k items that we read into PI, however, using the OPCtoCSV tool it takes 12 hours to extract about 2k of these PI tags and 200k other OPC items that we are not interested (mostly just metadata). Filtering…

    8 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 →
  10. EFGEN - Allow for null/blank values to be Zeroth State for active point

    When my EFGen Active Point tags have a null value, the interface should be able to designate this as a Zeroth State.

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

    We’ll send you updates on this idea

    NEEDS MORE DISCUSSION  ·  0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  11. Allow the UFL interface to delete PI tag data or provide some other supported automated method of deleting PI data from a collective.

    There is no way to easily delete data in a time range if you want the changes to occur on both the primary and secondary data archive. It seems the UFL interface would be good to use to do this. You could provide it a tag name and time range and then buffer the delete to both collectives, so the data does not exist on either.

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

    We’ll send you updates on this idea

    3 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  12. For PItoPI interface having a source PI-HA server, allow failover on source without using PI interface status utility.

    For PItoPI interface having a source PI-HA server, allow failover on source without using PI interface status utility. This should allow failover based on connectivity and/or a watchdog (like failover if a specific tag stay stale for a configurable duration).

    8 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. Link Referenced Elements from Unitprocedure to Procedure Event

    When Eventframe Batches are created by a Batch Interface, the used Unit in the plant is created as Element in AF and linked to the Unitprocedure EventFrame. Unfortunately it is not linked to the parent Procedure Event, leaving the "referenced Element" list of procedure event empty.
    If a user wants to create a report over all Procedures a certain unit was involved, he has to download all Procedure Events and Unitprocedures via Datalink and do the filtering there.
    With PI Batch it was possible to search for PI Batches using PI UnitBatch criteria like Unitname. We need this feature in…

    7 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. PI OPCtoCSV Tool: Subbranch filter depth

    The PI Interface for OPC DA is packaged with the PI OPCtoCSV tool which extracts all OPC Items. It is possible to filter the items by subbranch however it recurses all sub-subbranches.
    We have an OPC server with around 20k items that we read into PI, however, using the OPCtoCSV tool it takes 12 hours to extract about 2k of these PI tags and 200k other OPC items that we are not interested (mostly just metadata). If we could specify a subbranch and also specify how many levels below this branch to recurse or how many levels above a leaf,…

    7 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 →
  15. OPC interface retries sending InstrumentTag/ItemID to OPC Server

    The idea is to have PI Interface for OPC DA/HDA to be able to send again Instrument Tag/Item ID after a configurable time when OPC Server is not able to resolve it (AddItem failed). This would be a workaround for an OPC server issue and would help customers avoid the need to restart interface or modify affected tags in order to have tag incorporated into interface's list.

    7 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 →
  16. 7 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 →
  17. Enhance element creation to use user defined element templates

    The interface can automatically create an element at each level of event frames, but the elements do not derive from a template and there is no way to specify any attributes on the element. The enhancement request is to create elements that are based off of different templates for different Event Frame levels it would allow categories, default attributes, etc. to be assigned to the elements associated with the Event Frames.

    7 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 →
  18. change the default behavior of the OPC DA interface to use /DC

    per the OPC DA 2.x spec, the OPC server will call us back for all points that have a changes; even those points where we are polling.

    We have a switch to disable the callbacks for points that are not set to advise: /DC

    Can we make that the default?!

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

    6 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 →
  20. Support Analysis Backfill of Source Tag

    Many of our source tags sending data to a central Data Archive are populated with data from analyses on the source AF Server. This creates two problems when we perform a backfill that recalculates data over a specified timespan for the source tag:


    1. History recovery has to be manually triggered for the target PI tag over the timespan the analysis was backfilled over. The best way we've found to do this is to have multiple interface instances running at once that we can switch tags between (which feels redundant and is prone to error).


    2. Even if we remember to manually…

    6 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 →
  • 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