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. PI AMI Itron Interface support for TLS1.3

    PI AMI Itron Interface currently supports TLS1.1. Microsoft ended support for TLS1.1 in March 2020. To keep the PI AMI Itron Interface usable with latest browsers, please update to support TLS1.3.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  2. Automatic restart of the OPC interface whenever OPC server is restarted

    whenever the OPC server undergoes any restarts or configuration changes, the OPC interface will delete all old connections, groups, etc. and it will establish a new connection to the OPC server, loading all ItemID's etc (as if it is an automatic restart of the interface).

    The reason for this enhancement request:
    if OPC server is restarted or undergone configuration changes, all the handles and subscriptions for advise tags are not valid anymore. The interface would get the advise values in an inconsistent manor (values betwen the OPC server and the interface would show a mismatch)

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    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 →
  3. OPC AE: add history recovery feature

    There is a stronger market demand to have more alarm data in PI so that the alarms can be analysed together with the process data. Existing (as of Oct 2019) PI OPC AE Interface does not support history recovery. Without the history recovery feature (automatic or manual), the interface is less reliable in terms of data loss possibility, especially in highly regulated industries such as Pharmaceuticals. On the control system side, OPC Historical Alarm and Events data access (OPC H A&E) is already available, for example for Siemens PCS7 with their product OpenPCS7. Requesting OSIsoft to look into adding this…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  5. 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

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  6. PI Interface for IEEE C37.118 support for Analog data Signed and Unsigned 16-bit Integers

    The IEEE specification of the IEEE C37.118 protocol does not specify if analog data should be singed or unsigned for 16-bit integers. The currently the PI Interface for IEEE C37.118 represents these values as exclusively unsigned. Both types should be configurable in the interface

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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

    We're glad you're here

    Please sign in to leave feedback

    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. Upgrade the PI Interface Configuration Utility to a responsive web-based user interface

    OSIsoft's migration from PI Interfaces to PI Connectors is very slow. Even after the migration is complete, many PI Interfaces will not be upgraded to PI Connectors, so users will continue to use the PI Interfaces and the PI ICU to configure them.

    Please consider upgrading the PI ICU to a responsive web-based user interface, much like the PI Connector administration pages. The PI ICU is currently very cramped, very grey, not resizable, and a bit hard to navigate.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI ICU  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    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. Uni-Int to write to scan-class health tags on startup

    We've noticed this particularly with the RDBMS-PI interface when configured for failover: Health tags that are only written to when the interface becomes primary or has completed its first scan (eg Point Count, Scan Class I/O Rate etc.) say 'Intf Shut' when the instance is actually in 'Backup' mode. Even when changing to Primary status, many of these tags don't get a value till after the first scan, which could be quite a long wait.

    I would like UnitInt interfaces, on startup, to post an 'Initialising' or 'Awaiting 1st Scan' or some such digital state to all health tags that…

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  11. 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

    We're glad you're here

    Please sign in to leave feedback

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  PI to PI Interface  ·  Flag idea as inappropriate…  ·  Admin →
  13. Update GE iFix interface compatibility information

    As an interfaces user, I would like to know which versions of iFIX and Windows Server OS are compatible with the PI Interface for GE iFix so that I can determine whether this interface is suitable for my use case.

    The last update for this interface was in 2014, so there has been no testing on compatibility since iFIX 5.5, but I am looking to use versions 5.8, 5.9, and 6.0 and Windows Server 2016.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  14. Update EFGen Interface Health Tags To Allow For Better Status Monitoring

    The current EFGen interface "Status" health tag displays a value of "Good" if it is connected to the data source but does not factor in if it is writing Event Frame data to PI. There is not currently a straightforward way to drive a PI Notification to alert that there may be an interface issue in the scenario that the interface is connected to the data source but can not write event frames. Either the criteria for what results in a status of "Good" needs to be revisited to include both connectivity to the source data as well as actively…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  15. Support for the VT_UI4 data type

    As a PI System User I would like to archive and analyse VT_UI4 data using the PI System.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

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

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  17. 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

    We're glad you're here

    Please sign in to leave feedback

    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. CA ISO Interface - Allow conversion of timestamp values (i.e. InstructionStart) from UTC to local time

    Currently, the interface does not have any means to convert timestamp values (i.e. not the actual timestamps corresponding to values), such as InstructionStart, to account for timezone differences.  Therefore, the timestamps have to be manually adjusted to account for timezone differences once it reaches the archives. 

    Having to manually adjust the timestamp causes issues further down the line, such as with PItoPI, and creates unnecessary overhead in AF to do said conversion.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  19. Assure changes made to any configuration of an interface are audit trailed

    We noticed that changes to the configuration of newer interfaces / connectors like
    - PI EMDVBCS interface 4.0
    - PI inbatch interface
    - PI Connector Wonderware Historian
    are no longer recorded in the PI Audit trail. (see also TechSupport Case # 937205)
    This is a compliance issue for the regulated industries.

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  20. DeltaV Smart Connector Enhancement

    I think it would be a good idea to allow exception settings to be created. The DeltaV history collection settings only allow for compression. Since many/most users use 1/2 compression for their exception value then perhaps we could have a check box on install of the smart connector to turn a general exception rule on. The point of the smart connector is so that a user shouldn't have to modify tags after they are created from DeltaV.

    The other enhancement that would be great is if we didn't have hard-coded security groups (DeltaV and Deltavadmin user) but could put in…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    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
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED