PI Interfaces

Welcome to the PI Interfaces feature suggestion box. We created this forum to hear your ideas, suggestions and feedback.

Please suggest your most important features and design change ideas on this site! Also vote for your favorite features now! We welcome your feedback.

  • NOTE: for documentation feedback and bugs, please report to Documentation@osisoft.com rather than entering them on this site.

How can we improve PI Interfaces?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Emerson Ovation Interface: Enable the extraction of the full 32-bit overpacked digital tag as opposed to the now max of 16-bit

    Customer would like to extract the full 32-bit overpacked digital tag into an int32 pi point.

    0 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  2. Replace pipc.log and PI Message logs with the Event Viewer

    PI Connectors already use the Event Viewer to log messages. It is time for PI Interfaces to do the same.

    0 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  3. DNP3: Add slave functionality

    DNP3 - add slave functionality. Currently, interface can only act as master station.

    0 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  4. Accept the dd-mmm-yyyy format in the absolute time syntax for history recovery start and end times

    The PI Interface for RDBMS currently accepts the format dd-mmm-yy but not the format dd-mmm-yyyy for history recovery start and end times.

    The former format lacks the century, so the year is ambiguous. The latter format solves this problem and so should also be accepted as a valid time format.

    0 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
  5. Unregister interfaces in bulk on ICU

    In scenarios where we have to move interface instances to a new machine, we will have to perform some cleanup after of un-registering the interfaces in ICU. This includes removing the bat files and services. It would be nice to perform this task in bulk.

    0 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  PI ICU  ·  Flag idea as inappropriate…  ·  Admin →
  6. Support redundancy with OPC event tags

    Currently, with OPC event tags, if the connection between the interface and PI Data Archive is broken and signups lost, the event tags will stop polling the OPC server for data. I would like to see a level of redundancy added whereby if the OPC-PI Server connection is broken, the event tags will default over to a predefined scan class, or alternatively be advise tags.

    0 votes
    Sign in
    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 →
  7. Batch Framework Interfaces - [TIME] placeholder should consider whether TS=LCL is configured

    Batch Framework Interfaces - [TIME] and [TIMESTAMP] placeholders should consider whether TS=LCL is configured (meaning the interface is processing incoming events as Local Time). Currently, values of these placeholders always show up as GMT timestamps.

    0 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  8. New start-up parameter /SYNC_TIME defining a floating-window during which the interface will keep a RDB table in sync with PI data archive

    The new RDBMSPI param:  /SYNC_TIME=rel_start_time,rel_end_time  
    for instance /SYNC_TIME=*-6h,*+1h

    When set, the interface:

    - after each execution of a query, which shall have the same "floating" window in its WHERE clause; for instance:

    SELECT time, value, status FROM table1 WHERE time BETWEEN GETDATE()-6  AND GETDATE()+1;

    reads events for this tag from the PI data archive (for the interval defined by /SYNC_TIME) and compares timestamps from both sets. The "master" is the set from the rel. database; that is, if in the set taken from PI, there are timestamps, which were not returned from RDB, they are deleted (in PI data…

    0 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI Interface for RDBMS  ·  Flag idea as inappropriate…  ·  Admin →
  9. Reference a local .csv file with mappings (TagName-InstrumentTag) to shorten start-up times.

    The .csv file with TagName-InstrumentTag mappings will allow start the interface without specifying the PointSource, which will potentially shorten the start-up times against systems with larg point count. Once the interface is running it will update this file with corresponding points, which have been created/updated/deleted while the interface has been running.

    Note: This was previously Enhancement 125215.

    0 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  10. Support for mathematical operations to be performed on timestamps that are stored as SECONDS_GMT

    Time manipulations (adding and subracting) can only be performed on standard datetime formats and not on SECONDS_GMT 

    Note: This was previously Enhancement 118924.

    0 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  11. Create a new function signaling the Beginning of the Stream

    Create a new function signaling the Beginning of the Stream. For example, BOS() returns 1 if this is the first line of a stream; otherwise it returns 0.

    0 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
  12. Support Modbus device failover

    Enhance the interface to support redundant Modbus devices with different network cards/IP addresses. The controllers would publish a status update on the active device, and the interface should request data from it accordingly.

    0 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Modbus Interfaces  ·  Flag idea as inappropriate…  ·  Admin →
1 2 3 4 5 6 8 Next →
  • 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