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. Support float64 point type in PI Interface for China Network Isolator

    China Network Isolator interface does not support float64 point type, which is required by many customers in China. Right now, they have to change the point type to string first and then to float64 by analytics, this will consume two times of license number.

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

    We’ll send you updates on this idea

    3 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  2. Update the CA ISO interface in preparation for the upcoming API V8 deployment

    CA ISO is planning to upgrade its ADS (automated dispatch system) to version 8. This upgrade introduces breaking changes from the current system, API version 7.

    The CA ISO interface should be updated to account for these changes.

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

    We’ll send you updates on this idea

    2 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    The current information available from CA ISO indicates the go-live of ADS API V8 and the decommissioning of ADS API V6. We have confirmed with CA ISO technical support that ADS API V7 will continue to be supported. The PI Interface for CA ISO ADS Web Service is compatible with ADS API V7, so at this time we do not plan to make any changes to the OSIsoft Interface.

  3. Enhance WMI interface to verify that ACE Class Libraries are running

    PI-ACE Manager looks at the PI-Module Database to see if the individual modules are running. The Class Library sub-processes updates the PI-MDB when it starts & stops. If the process dies, it does not always update the PI-MDB values. So, there is no supported way to verify if the Class Library sub-process is running.

    The PerfMon interface can't monitor the existence of the process. I have found that I can use the OSIWMI interface to find the Class Library process based on the Command Line of the process.

    The WMI interface will only update the PI tag if the process…

    9 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 →
  4. 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.

    5 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 →
  5. Link Referenced Elements from Unitprocedure to Procedure Event

    When Eventframe Batches are created by a Batch Interface, the used Unit in the plant is created as Element in AF and linked to the Unitprocedure EventFrame. Unfortunately it is not linked to the parent Procedure Event, leaving the "referenced Element" list of procedure event empty.
    If a user wants to create a report over all Procedures a certain unit was involved, he has to download all Procedure Events and Unitprocedures via Datalink and do the filtering there.
    With PI Batch it was possible to search for PI Batches using PI UnitBatch criteria like Unitname. We need this feature in…

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

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  6. 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
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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
    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 →
  8. and operator

    Add a function that can be used in the UFL Configuration File to perform bitwise operations. For example, a function similar to the AND operator in Performance Equations and Asset Analytics.

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

    We’ll send you updates on this idea

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

    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. 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
    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 →
  13. Add another Archive Mode option for the PI Interface for UFL

    There should be a way to configure the PI UFL interface to both discard duplicate events (same value at the same timestamp) and record multiple unique values for the same timestamp when these events come from multiple data files.

    For example, if multiple data files contain the following entries:

    (Timestamp)  (Value)
    11:00:00      ABC
    11:00:00      ABC
    11:00:00      XYZ

    The following data should be archived:

    (Timestamp) (Value)
    11:00:00 ABC
    11:00:00 XYZ

    5 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. PI Event Frames Interface Manager

    Hello,
    the PI Event Frames Interface Manager application must be run in the same machine that hosts the PIEFGen interface. This is an issue regarding our security rules because, the PIEFgen interface runs in secured machines and we don't want to allow users to RDP to these machines only for setting batch configuration (triggers, batch nr...) .

    This issue did not exist with PIBatchgen as the setting of batch configuration (triggers, batch nr ...) was available inside PI SMT.

    It would be great to either be able to run PI Event Frames Interface Manager in a different computer or to…

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

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  15. Use /opcstopstat when both interfaces in failover pair are shut down

    We would like to have some sort of digital state such as "Intf Shut" written to all OPC tags when both interfaces in a failover pair are shut down.

    Currently, the /opcstopstat and /stopstat parameters (which write a specified state to all tags when the interface is shut down) are ignored if the interface is in failover. We'd like for some sort of status to be written to tags when no data is being collected by either interface.

    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 →
  16. PI Interface for ABB Web Imaging System via ABB CNI

    CNI interface should support message 25. Currently, we do not support any message beyond 22.

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

    We’ll send you updates on this idea

    2 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  17. PI Interface DNP3 - unsolicited data listen only mode of operation requested

    Is there an option in DNP3 driver (In fact at TCP level) to make it listen on a certain (usually 20000 for DNP3)? In era of IoT devices, most devices are sleeping devices, they wake up usually once a day and push data to DNP3 Master (PI), however DNP3 PI collector doesn't support this model. As an enduser I would like to utilize this mode of operation at our plant. FYI, there are other products e.g. Citect SCADA and ClearSCADA use two separate ports for Inbound and outbound DNP3 traffic to use the both modes simultaneously.

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

    We’ll send you updates on this idea

    1 comment  ·  DNP3  ·  Flag idea as inappropriate…  ·  Admin →
  18. Automatically recreate advise groups when they are discarded by RSLinx OPC Server

    The Rockwell RSLinx OPC Server may discard advise groups when there are too many bad quality tags or incorrect ItemIDs added to the group. The PI Interface for OPC DA should automatically recreate advise groups after it has determined that the group has been discarded from the OPC 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 Interface for OPC DA  ·  Flag idea as inappropriate…  ·  Admin →
  19. RDBMS to Eventframe Batch Interface

    a lot of your existing Batch Interfaces are based on RDBMS (Simatic Batch, DeltaV, ABB). But there will always be some Batchstorage solutions based on a relational database which are not included in your source system list. For now Honeywell Procedure Analyst or ABB Workflowmanager are such systems.
    If we users had a generic RDBMS to Eventframe Batch Interface where we could do the mapping between relationale database rows and your typical Batch Interface placeholders by our own and define triggers for different batch levels just like we can define triggers now for additional batchinformation, we could connect to a…

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

    We’ll send you updates on this idea

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

    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 →
← 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
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA/PREVIEW
COMPLETED