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. 64-bit version of CatGH5 interface

    There needs to be a 64-bit version of the CatGH5 interface that is capable of parallel processing in order to efficiently process an quantity of data/files (that the 32-bit version is not up to the task of handling well).

    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 →
  2. Ability to wait successful connection to PI Data Archive and download PI point information during startup

    (Posted on behalf of our customer)

    It can reduce the chance of startup failure because of the connection to PI Data Archive time-out. It's also helpful if interface can reduce time to get PI point information from PI Data Archive.

    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 →
  3. 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 →
  4. Davis to Pi Interface - Additional sensor functionality

    Add functionality for the Davis to Pi Interface to read additional sensor data points. The Davis to Pi Interface does not support the use of additional sensors, such as a second or third temperature sensor. The Davis console supports additional sensors, but the Pi Interface cannot read them.

    1 vote
    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. Remotely view logs

    I understand that you can remotely view logs using pigetmsg. However this solution does not work for me as the interface is on a controlled network that only allows outbound traffic. I would like a way for the interface node to be able to push out interface logs somewhere such as to my DA, that way I could use SMT to view my interface logs.

    2 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 →
  6. PItoPI: Disabling Time adjustment

    the ability to disable the timezone adjustment.

    currently we are calculating daily kpis on our global pi server. with PItoPI we are sharing it to the site pi-servers.
    so the daily kpi for e.g. 1st januar 2019 00:00AM sould alwas have that timestamp. Because if the forward it to e.g. britain, it has the timestamp 31st decemper 2019 11:00PM (adjusted -1h to austrian time)

    plz make it possible to disable it via Location2.

    1 vote
    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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. Expand failover functionality in Schneider-Electric Foxboro fxbais interface

    Failover mechanism in fxbais (Schneider-Electric PI interface for Windows) doesn't lead to a failover when the primary interface node loses connection to the network (f.i. when its NIC fails). It just starts buffering and sends its data after the connection is back again.
    It keeps on updating its watchdog CALC block on IA, so no take over is initiated.
    Some applications require "near real time" data, so if it comes in a day later, it's not very useful.
    In such a case, the secondary interface node could perfectly take over the data collection.

    1 vote
    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. Support data collection across data diodes or similar technology

    Regulatory and/or security requirement to separate data collection from data storage using a one-way data flow. Could apply to Interfaces or Connectors, for example PI Interface for Emerson Ovation.
    PI Interface/Connector -> one-way data flow -> PI Server/EDS/OCS

    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 →
  15. 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,…

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

    5 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. Managing loss of connectivity - local data

    For a PI tag with a specific scan class, if no new value is collected by the PI Interface after a period of time (for example 2x the scan class) , the interface will add automaticaly the value "No Data". It will avoid the usage of a dedicated analyze for this, in the PI Server. And like that, the PI user will be aware of the issue, by using any PI Visualization tool.

    1 vote
    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 →
  18. 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 →
  19. OPC DA, A&E historical recovery

    We have seen that the primary OPC interface will be connected but we don't see data coming across since the OPC server itself seems to have a problem. Since the connection is still active we won't failover to the secondary. We have to leave Notifications to look for IORATES to drop so we know we have to go and manually fail over to the secondary but this isn't good enough as we now have a data gap for the duration it takes for us to log in and failover.
     
    What if the secondary interface actually buffered a configurable amount…

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  20. Support dynamic OPC addresses

    My OPC server's items have the OPC server node name included in the itemID, for example: serverA.AB_1234.PV. I have redundant OPC servers and redundant interfaces (in failover) and would like the tags to refer to the correct OPC address including when the OPC servers fail over. Currently the workaround is to create two sets of tags, each pointing to one OPC server's itemIDs in their instrument tags and then merge the data with AF or a PE.

    5 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 →
← Previous 1 3 4 5 8 9
  • 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