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. 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 →
  2. 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…

    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 →
  3. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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 →
  9. 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 →
  10. Parameter for restarting the interface if no connection to the OPC server can be established after a defined period of time

    We use the Phoenix Contact Firewall with the OPC Inspector. When the OPC server restarts or breaks the connection for a few seconds, the firewall blocks all ports except port 135. After initial connection through this port, new firewall rules are dynamically established for DCOM connections. If connection break to OPC Server we have to restart interface manually.

    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 →
  11. 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 →
  12. 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 →
  13. PI EFGEN Interface -- Allow the "time true" fuction for EFGen

    in order to eliminate unwanted or noise event which be triggered and recovered in a short period.

    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 →
  14. PI-SNMPTrap interface request support for SNMPv3 trap

    PI-SNMPTrap interface currently only has support for SNMPv1 and SNMPv2C trap. Feature request for PI-SNMPTrap interface to include support for SNMPv3 trap.

    Monitoring of snmp traps originating from CISCO switch devices require support for SNMPv3 trap.

    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 →
  15. 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 →
  16. 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 →
  17. PI BES Interface (i.e. PI EMDVB): aliasing of Unit Names

    Currently the interface creates PI UnitBatches or Event Frames associated to Units (PI Units or AF Elements) determined by some placeholders specified at the "Unit Procedure" level; the default is "[AREA][PROCESSCELL][UNIT]".
    Moreover the interface properly created a PI MDB or AF structure under an alternate module path, specified in "Batch Setup" section (/SMP parameter).

    It would be useful to have a way to specify different Units instead of the one determined by the [UNIT] placeholder (at least).
    As an example, suppose we want to register unit batches for a PI Unit called Reactor1" when the [UNIT] placeholder values "U6-K54100", and…

    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 →
  18. UFL Designer should include a test mode to verify INI behavior with a data file.

    One can do this, to some extent, piecemeal with functionality the UFL Designer already has. However, it's a very manual process and does not actually have a way to show what data would be sent to PI for a particular file. An explicit test mode or test function, where the Designer outputs what the results might be for a supplied data file (Values of each variable, what would have been sent to PI, et.c) would be very helpful in building and verifying INI files.

    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 →
  19. UniInt should include a test mode for all interfaces that collects data but does not send it to PI.

    This functionality would allow users to test the connection to the data source and inspect the data that is retrieved without sending it to PI. That data might be written to a text file, for example.

    This would allow users to verify settings and data integrity without needing to delete archived values, for example. Potentially, this functionality would also have some type of PI point selection so that user would be able to select which tags the interface should use for this test mode, rather than using all tags (The interface would essentially assume that all other tags have scan…

    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 →
  20. Option for PI Interface for UFL to purge read-only files

    Create an option to allow the PI Interface for UFL to delete files with the read-only attribute.

    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 →
  • 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