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

    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 →
  2. Annotations support in PItoPI

    Annotations are crucial in some instances. PItoPI should be able to handle annotation duplication.

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

    We’ll send you updates on this idea

    3 comments  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  3. PItoPI should give indication when it is stuck querying a corrupt source archive

    Currently, PItoPI interface can get "stuck" if it is querying a source data archive that is corrupt with no indication that this is what's happening.  It appears to be sending data to the destination server, but no data is received.  It would be helpful if it would write an error message to the interface logs or exit out of the process after a certain amount of time in this state.

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

    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 →
  5. Enhance pitopi.ini sections to include point source to make them unique

    The pitopi.ini file is used by the pitopi interface for collecting data from multiple sources and to save other miscellaneous settings such as 'histonly' flags. The configuration ini file uses sections to separate settings between instances with and the format is [PItoPI-<ID>] and this is not unique enough to distinguish settings between different instances that use the same instance ID but with a different point source. So when there are two instances with the same ID (regardless of the Point Source), any changes made to one instance will affect the other instance too.

    Note: This was previously Enhancement 121629.

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

    We’ll send you updates on this idea

    2 comments  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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…

    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 →
  7. 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 →
  8. PI to PI interface should perform first scan so that future data can recovered

    /fd parameter is only used while performing real-time scan. If scan rate is set to a higher value such as a day, the user would need to wait for the first scan (after a day) to get future data. This should be done at interface startup. For use case see notes for Case # 895278.

    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 →
  9. 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 →
  10. Add functionality to the interface to adjust timestamps by a configurable amount

    This enhancement would add the ability to adjust timestamps to the PI to PI Interface (Beyond the included options for clock drift and subseconds). Potentially, a setting could be supplied to change the timestamps on all data transferred by a specified number of UTC seconds. This setting should be accompanied by a warning message in ICU and the message logs so that the implications of the setting are understood.

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

    We’ll send you updates on this idea

    1 comment  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  11. PItoPI should switch from COLD to WARM failover instead of exiting

    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, older versions supported COLD failover. In the case of upgrading the interfaces, the old configuration with COLD failover would cause them to refuse to start thus causing data loss or data delay.

    The interface could instead log a warning that COLD failover is no longer supported and switch to WARM failover.

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

    We’ll send you updates on this idea

    1 comment  ·  PI to PI Interface  ·  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. Enhance connection logic to source PI server during Interface startup

    When PitoPi Interface starts up, it prints a message saying that it secured a connection with the Target or Host PI server as follows:  PIAPI Successfully connected to <Target_PI_Server>:5450. Then it begins to load target PI points and it starts looking for the source PI point even if it doesn't have a connection to the source PI server. This will result in pipt_findpoint for source tag returned [-5] Tag Not Found

    So this enhancement request is to handle situations when it doesn't have a connection to the source PI server at startup. If there are X number of points on…

    4 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 →
  14. Support of the PI Annotations in the PI-to-PI Interface.

    Having the support of the PI Annotations in the PI-to-PI Interface.

    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 →
  15. PI to PI automatic recovery if time desynchronization between the machines.

    We see a data gap in one PI Data Archive after the machine hosting the PI-to-PI interface was one hour in the future. In this case, the buffer disconnected from the machine when the issue happened, The buffer did not work correctly and there was a data gap in the target server.

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