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. 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 →
  2. DNP3: store data as "bad"

    Add functionality to treat the data as "bad" and send a digital state instead, when status flags are sent with the event and status bits are set to TRUE. Right now, the data is sent to PI and marked as "questionable".

    Note: This was previously Enhancement 125605.

    4 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 →
  3. 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 →
  4. EMERSON PK based DCS - EMDVB Interface support

    Emerson has a new PK Controller based DCS available (in lieu of full blown DeltaV). This new device is contained with OPC-UA and Batch Exec/Historian. We want support for the existing EMDVB interface to supply S88 based batches into PI Event Frames and/or PI Batch. Additionally, we will want to run the PI OPC-UA interface to get the live module data into PI tags. Do you have support for this today?

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

    3 votes
    Sign in Sign in with OSIsoft
    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 →
  6. Bring in UOM from EMDVBCS source files.

    EMBVBCS currently does not bring in UOM from source files to 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  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  7. Monthly scans

    Allow for monthly scan intervals for scan classes. i.e. "scan monthly on the first hour of the first day of every month".

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

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  8. 64-bit version of CatGH5 interface

    There needs to be a 64-bit version of the CatGH5 interface that is capable of parallel processing in order to efficiently process an quantity of data/files (that the 32-bit version is not up to the task of handling well).

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

    We’ll send you updates on this idea

    1 comment  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  9. Ability to wait successful connection to PI Data Archive and download PI point information during startup

    (Posted on behalf of our customer)

    It can reduce the chance of startup failure because of the connection to PI Data Archive time-out. It's also helpful if interface can reduce time to get PI point information from PI Data Archive.

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

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

    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 →
  12. Support data collection across data diodes or similar technology

    Regulatory and/or security requirement to separate data collection from data storage using a one-way data flow. Could apply to Interfaces or Connectors, for example PI Interface for Emerson Ovation.
    PI Interface/Connector -> one-way data flow -> PI Server/EDS/OCS

    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 →
  13. OPC DA, A&E historical recovery

    We have seen that the primary OPC interface will be connected but we don't see data coming across since the OPC server itself seems to have a problem. Since the connection is still active we won't failover to the secondary. We have to leave Notifications to look for IORATES to drop so we know we have to go and manually fail over to the secondary but this isn't good enough as we now have a data gap for the duration it takes for us to log in and failover.
     
    What if the secondary interface actually buffered a configurable amount…

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

    We’ll send you updates on this idea

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

    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 →
  15. PI Interface for GE HABConnect FLDTIME Support for COUNT Objects

    Currently only POINT/ANALOG fields support COUNT. This request would be to enhance the interface to additionally support the COUNT field.

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

    We’ll send you updates on this idea

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

    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 →
  17. PI UFL Interface can read input files from non-UNC paths such as Azure File share

    I would like the PI UFL Interface to be able to directly read from input files that are in non-UNC paths such as Azure File share, so I do not need to periodically copy the input files into another path.

    3 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 →
  18. UNIINT Interfaces and Connectors should be able to retry an output event if output write fails

    When an interface fails writing to a DCS system, the interface writes a failure status to the output tag and goes on.  User has requested an option to have an output tag retry after write failure. It would be good to have this functionality in all uniint interfaces as they are recompiled, starting with the OPC DA interface, also to have this added to PI Connectors. Retries could stop after x retries of 1 minute retries, or when a new output value comes in. Or some other policy could be worked out.

    3 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 →
  19. 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 →
  20. PI Interface for CAISO Exclude Certain Batch Types

    We would like the PI CAISO interface to parse through the .XML files and exclude XMLs that contain certain specified <Batch Types>. Only certain batch types contain valid data for consumption.

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

    We’ll send you updates on this idea

    1 comment  ·  Other Interfaces  ·  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