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. Fix MAXSTOPTIME parameter for batch interfaces

    The MAXSTOPTIME parameter for batch interfaces does not kill the interface process when the limit is exceeded, however the parameter does work for UniInt based interfaces. Please fix the batch interfaces so that the interface process is killed once the MAXSTOPTIME has elapsed.

    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  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  2. Enhance how batch interfaces write to the message logs

    Batch interfaces should write their messages to the message logs using the Source1 and Source2 fields just like UniInt based interfaces. Currently, batch interfaces leave these 2 fields blank. Source1 should contain the process name or similar and Source2 should contain a string in the format of "<PointSource> | <Location1/ID> | <FailoverID>". Having this will greatly help PI administrators filter the logs based on point source, especially when there are 20+ interfaces running on a 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  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  3. Allow diagnostic tags per failover node for batch interfaces

    Batch interfaces should allow for diagnostic tags per failover node, just like UniInt based interfaces. Currently, there is no differentiation between the diagnostic tags for the primary failover node versus the backup failover node. The Location3 field is used to hold the failover ID of UniInt based interfaces so that there is a unique set of tags per failover node, however for some bizarre reason the Location3 field for batch interfaces stores the diagnostic tag index even though the diagnostic tag pointer exists in the ExDesc field. While not all diagnostics tags may be of interest for the backup node,…

    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  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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 →
  5. 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 →
  6. 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 →
  7. Mention the PI ICU in the names of PI Generic Names DLL and PI Spt DLL in Programs And Features

    Both PI Generic Names DLL and PI Spt DLL are part of the PI Interface Configuration Utility, but this is not obvious from their names. This can cause confusion or waste time when an administrator decides to clean up or replace some PI programs but can't figure out exactly which PI programs need those DLLs.

    In Control Panel → Programs And Features, these DLLs appear as:
    • PI Generic Names DLL (PIGenericNames)
    • PI Spt DLL (PISpt)

    I suggest changing these names to something like:
    • PI Interface Configuration Utility Prerequisite: PI Generic Names DLL (PIGenericNames)
    • PI Interface Configuration…

    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

    1 comment  ·  PI ICU  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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 →
  9. Upgrade the most commonly used PI Interfaces to use only the Microsoft Visual C++ 2015-2019 Redistributable

    Please upgrade the most commonly used PI Interfaces so that the only Microsoft Visual C++ Redistributable version that they require is the 2015-2019 version. This will reduce the size of the install kit, make it faster to download, make it faster to install, reduce the wear on the customer's disk, and reduce the clutter in the list of installed programs.

    Here are the versions of the Microsoft Visual C++ Redistributables that some of the most commonly used PI Interfaces currently use:
    OPC DA & OPC HDA: 2008, 2010, 2012, 2017
    PI To PI: 2008, 2012, 2017
    UFL: 2008, 2012, 2013,…

    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 →
  10. 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 →
  11. Interface TCP\IP para Data-Logger Davis (WeatherlinkIP)

    Se recomienda agregar funcionalidad para adquiquirir datos de un DataLogger WeatherlinkIP, ya que actualmente solo se soporta conexiones seriales con este data Logger:

    Davis Vantage Pro / Pro Plus Weather Station (NTI)
    Davis Weather Station (NTI)

    Tener en cuenta que actualmente todas tecnología se basa en conexiones TCP\IP.

    https://www.davisinstruments.com/product/weatherlinkip-for-vantage-stations/

    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 →
  12. Separate commonly used PI Interfaces into read-only and write-only versions

    Currently, it is recommended to use the read-only version of a PI Interface if only reading is required, and to have separate read and write instances of the read-write version of a PI Interface if writing is required. (Reference: page 15 of the PI Interface For OPC HDA user guide, and I assume that the recommendation applies to other PI Interfaces as well)

    This approach is unnecessarily complicated and can still be made more secure. Instead of having read-only and read-write versions of a PI Interface, consider having read-only and write-only versions of a PI Interface. That way, the recommendation…

    4 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. Device Status UniInt health tag should update during runtime without needing a status update

    Currently, the device status is updated on startup, on change, on shutdown, and on each performance summary interval.

    However, for a device status tag created while the interface is running in a good state, the device status tag will remain at 'Pt Created' and not update until the interface status changes or the interface is restarted.

    A newly created device status tag should display the current state of the interface without needing a status change. This is especially helpful in cases where the interface cannot be restarted for the tag to pick up a status update.

    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 →
  14. PI UFL Interface to extract data from csv files from multiple sub-folders within the main folder.

    In case of csv files in subfolders within Main Path for UFl, PI UFL Interface should be able to search the csv files with placeholder and extract data from csv files from multiple sub-folders within the main folder.

    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  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  15. Enhance Visibility of Event Frame Generator/Batch Interface History Recovery Status

    Currently when running any event frame generator interface (EFGen, PIFTBatch, etc.) in history recovery mode, there is no way to monitor progress of the actual history recovery. The only way to determine status is to check message logs periodically looking for the message "Switching to [REALTIME] data processing.". It would be helpful if there was a way to check progress of the history recovery (i.e. percent complete) along with an estimated time until completion. I'm currently in a position in which I'm running a PI-FTBatch interface history recovery, but also have users who need access to FTBatch EVT data generated…

    4 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 →
  16. Support for VT_UI2 Data type

    As a PI System User, I would like to archive values for the VT_UI2 data type using the PI System.

    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 Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  17. PI UFL MULTIPLE Language Support

    PI UFL currently supports only english.
    I would like PI UFL to read multiple language, for my case japanese character.

    PI UFL does not support to extract data from line with japanese character contained. For example, when Message Type-> Message Filter has Japanese character, Data Extraction does not display target line.

    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  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add the ability to create custom Performance tag names for the PI Batch Interfaces

    Add the ability to create custom Performance tag names for the PI Batch Interfaces.

    For systems with numerous batch interfaces the Performance tag naming convention does not intuitively distinguish between interface instances since the Interface ID is the only unique text in the tag name.

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