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. Add SOAP 1.2 support to the PI Interface for OPC XML-DA

    The current version of the PI Interface for OPC XML-DA seems to only support SOAP 1.1. All recent OPC XML-DA servers are developed following SOAP 1.2 standards, meaning the PI interface will not connect. Please enhance the interface to also support servers using the newer SOAP 1.2 standards.

    This also relates to tech support case 00857284

    26 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  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  2. Add PI Interface for OPC XML-DA documents to the Live Library

    Add PI Interface for OPC XML-DA documents to the Live Library

    1 vote

    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  ·  Help / Documentation / Videos  ·  Flag idea as inappropriate…  ·  Admin →
  3. Fix PI XMLTool (bundled with PI Interface for OPC XML-DA)

    The PI XMLTool that is bundled with the PI Interface for OPC XML-DA does not function with Windows Server 2019 even though the PI Interface for OPC XML-DA itself is documented to function. Can the client tool please be worked on so that it will function with the same operating systems that the interface does. This is a key component to aide in the troubleshooting of the interface as well as determining the correct instrumenttag field by the browsing the XML-DA tags on the server.

    3 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. PI Interface for Foxboro I/A 70 Series should support Windows 10

    On PI Interface for Foxboro I/A 70 series version 2.4.2.12, the supported operational System are Windows 2008 R2, Windows 7, Windows 8 and 8.1, Windows 2012 Server.
    Can we also test the interface against Windows 10, to included it as a supported OS?

    3 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 →
  5. PI Interface for GSE D/3 Compatibility Testing With Latest D/3 DBA Software

    As of writing, the current version of the PI Interface for GSE D/3 (v 4.32.0.50) supports versions of D/3 up to 14.1-2 (consult the latest user guide for more details). It has not yet been tested for compatibility against more recent versions of NovaTech D/3 (versions 15 and 16). However, users and NovaTech have reported successful deployments of this interface against versions 15 and 16, most likely due to a lack of database changes between versions 14.1-2 -> 15, and 15 -> 16. Can the interface officially support compatibility for use with more recent versions of NovaTech D/3 DCS (versions…

    3 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  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  6. Provide ability to disable purge behavior of UFL interface

    The PI Interface for UFL includes a PURGETIME setting to purge successfully processed files (_OK) after some period of time. We have a case where we do not want to purge processed files. We want the data to be in PI but want to preserve the original files in case there are issues. There are cases where the interface can successfully process files and send the data to the PI Data Archive. But the PI Data Archive has an error storing the data and so the data is effectively lost. Keeping the processed files around would give the ability to…

    1 vote

    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  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  7. PI OPCtoCSV tool to continue running and skip branches in error

    The PI Interface for OPC DA is packaged with the PI OPCtoCSV tool which extracts all OPC Items. When the tool is run into error with certain branches, the tool will stop and disconnected from the OPC server/tunneller. For example: “GetItemProperties(“xxx”) error 0x800706be. The remote procedure call failed. pEnumleaves  Next() returned 0x800706ba”
    If we could specify an option for the tool to skip those branches in error and also attempt to reconnect to the OPC server/tunneller, for automation purpose for the tool to continue running instead of exiting.

    1 vote

    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 →
  8. Allow using SQL as a data source for FactoryTalk Batch

    Rockwell FactoryTalk Batch v12.01 allows to output batch data to a SQL database as well as EVT files. Just like with EMDVB, the PI Interface for FTBatch should be able to use both data sources.

    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  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  9. Restructure the Data Collection List

    I have few suggestions for the Data Collection List (https://techsupport.osisoft.com/Products/PI-Interfaces-and-PI-Connectors):

    • In the Platform column, there is currently the out-of-place entry "X64" that is used to signify 64-bit Windows. Please separate the bitness into its own column. Then all of the PI Connectors can finally join most of the PI Interfaces in being labelled as being for Windows.

    • Separate the product code into its own column to reduce the height of the rows and be able to have more rows per page

    • There is a column called "Standard". To unfilter this column, you select "All Types"…

    1 vote

    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  ·  Help / Documentation / Videos  ·  Flag idea as inappropriate…  ·  Admin →
  10. Hitachi ABB Mach Interface

    There are no current direct native interface connectivity to Hitachi ABB Mach systems.

    Current suggestion is to investigate IEC 61850 or Modbus could be investigated as an option.

    1 vote

    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 →
  11. Request for customizing the order of the interface instances in PI ICU interface list.

    The interface instancesnames contain the plantsnames and I want to put the interfaces with the same plant name together in the list.

    2 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 ICU  ·  Flag idea as inappropriate…  ·  Admin →
  12. Allow scan class 0 to be monitored via Performance Counters

    As a PI System Administrator, I would like to monitor the point count and other parameters for scan class 0 via Performance Counters. Currently, this is only exposed via the UniInt Health Tags.

    2 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 →
  13. Capture data from ABB 800xA that doesn't follow ISA88

    ABB 800xA offers a batch capture mode that is more flexible than ISA88 since it doesn't match all unit procedures to units, but rather acquires them at the beginning of the batch. Currently the interface is designed to only retrieve batches that follow the ISA88 model.

    1 vote

    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  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  14. Create a migration path for AMI Interfaces when PI Server is moved to a new machine/hostname

    Currently, AMI Interfaces require a rebuild of the AMI cache files when the PI Server is migrated to a new machine/hostname (Although to clarify if the hostname does not change during the PI Server migration the cache does not need to be rebuilt). This is undesirable for large AMI implementations as rebuilding the cache files can be a time consuming process.

    It is requested that AMI Interfaces should be able to handle PI Server migrations with new hostnames without rebuilding the AMI cache files

    2 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 →
  15. Support Werum PAS|X 3.2 and PAS|X Data Access (PDA)

    Werum has recently released the next version of their PAS|X Database, and it bolsters a new method of Data Access. OSIsoft will need to release an re-tooled version of their PI Interface for Werum PAS|X to support this latest Werum version and the new data access method.

    1 vote

    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  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  16. Provide data validation tools to verify moving history from one PI Server to another using PI to PI Interface

    There is no easy way to verify that historical data moved from one PI Server to another using the PI to PI Interface isn't missing data on the target PI Server.

    1 vote

    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 →
  17. Allowing output point with source tag to keep working even after switching to secondary server

    When primary server is down, secondary server is accessed instead of primary server, which is good. However, in the case of output point with source tag, it stops working, then restarting the interface instance of interest is needed. Of course, if we set up UniInt Failover that backup instance keeps its session with secondary server, this issue can be prevented. But, it will be better if source tag is also switched to secondary server.

    3 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 →
  18. Add a configuration option to UniInt so that the user can adjust the minimum wait time for checking for new events from the Update Manager

    This affects the delay in Event\Trigger tags. KCS: Delay in Event Points.

    The largest and most variable delay seems to come from the time the event is written to the PI Server and the time the interface (UniInt) picks, which is between 0ms-1,000ms from my testing. This seems to be due to a built-in, hard-coded, delay in how often UniInt checks for events from the PI Server update manager. The serviceeventsx function that is part of the main UniInt loop only checks for new events once a second; this means that sometimes there is no delay if the…

    2 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 →
  19. Add a configuration option to the OPC DA Interface so that the user can adjust the maximum advise tag exception delay for Event/Trigger tags

    This affect to delay in Event\Trigger points. KCS: Delay in Event Points.

    When using Event Points, we purposefully do have a delay (if excMax is > 2 s then 2 s else 0.9*excMax) for advise tags (Trigger Point) before they're sent to the PI Server if the event value has not changed since the last scan.

    2 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 →
  20. Improve the recovery process for long EFGEN batches

    Currently if EFGEN is configured to evaluate PI Points at the event end, long batches require recovery start time to be set before the start of the batch. This leads to a long recovery process as many completed batches will be evaluated again.

    2 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  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 10 11
  • 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