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. PI Event Frames Generator - Fix 'merge consecutive' in PIBAGEN mode.

    To enable us to move from PIBAGEN to EF Gen interface, we need 'merge consecutive' to work when running  in PIBAGEN mode. Currently none of this functionality is working, and the following known issues is already found.

    119695 - Merge consecutive at unit procedure level does not merge all consecutive unit procedures.
    124407 - Unit Procedures may be improperly merged in PIBaGenCompatibility mode.
    119363 - Consecutive subbatches can get merged incorrectly

    Please make an updated version of the 'PI Event Frames Generator' where this important functionality is working.

    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 →
  2. Enhance element creation to use user defined element templates

    The interface can automatically create an element at each level of event frames, but the elements do not derive from a template and there is no way to specify any attributes on the element. The enhancement request is to create elements that are based off of different templates for different Event Frame levels it would allow categories, default attributes, etc. to be assigned to the elements associated with the Event Frames.

    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 →
  3. PI EMDVB Interface - Rename Parsed Files

    PI EMDVB Interface - Rename Parsed Files.  Files that get renamed to .999 is no longer available with PI EMDVB.  This file renaming feature was very useful from a system maintenance perspective.  We would easily remove .999 from the active EVT folder and move to an offline directory.  Currently with PI EMDVB, there is no obvious visual indication that the EVT file was parsed completely.

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

    5 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. Batch Framework Interfaces - Allow creation of only the Event Frame levels that exist on data source

    The BES/MES sometimes contains recipes with no Procedure, or even Unit Procedure. The Batch Framework Interfaces should allow the creation of only the Event Frame levels that exist on the data source. This would need to be enabled with an interface configuration parameter so the default behavior is not changed on upgrades to existing systems. This enhancement would not be possible when writing to the PI Batch Database.

    2 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 →
  6. Batch interface to support slightly different parsing logic

    Some of the fields incoming from the DCS are user entered and prone to errors. Please allow for the option to include slightly different logics to be able to filter out those user errors (such as empty spaces at the end of the string, etc).

    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 →
  7. 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 →
  8. Make UserID and ReviewerID available from BatchQuestion table for PI Interface for Wonderware InBatch

    Currently UserID (DoneByUserID) and ReviewerID (CheckByUserID) cannot be read from the BatchQuestion table when using PI Interface for Wonderware InBatch. These fields are important to know who answered the question and who confirmed/checked the question.

    1 vote
    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 →
  9. Delete mode in Wonderware InBatch interface

    When run in delete mode for WWInBatch interface, it uses the data source as the system of record--any open batch in SQL will be deleted. However, as abandoned or done  batches are open in WonderWare but closed in PI, the interface may delete batches in PI that are still open in the source. It would be helpful if the interface gave the option of using PI as the system of record regarding batch end times.

    5 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 →
  10. Batch Framework Interfaces - Support filtering by whitelisting

    As a Batch Framework Interface user, I would like to filter my batch data by whitelisting. Currently the only option is blacklisting. This is inconvenient, for example, if data is only desired from a few units. Each time a new unit is added to the data source, the interface configuration must be updated.

    0 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 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/PREVIEW
COMPLETED