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

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We are declining this item as we don’t feel it’s the right fit with our overall product strategy for the EMDVB interface. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

  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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We are declining this item as we don’t feel it’s the right fit with our overall Batch Framework product strategy. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We have reviewed this idea, and it’s not something we plan to implement. Even though we are declining this idea for now, it is still open to comments. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!

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

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We are declining this item as we don’t feel it’s the right fit with our overall Batch Framework product strategy. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

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

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We are declining this item as we don’t feel it’s the right fit with our overall Batch Framework product strategy. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

  6. Suppress creation of an AF Element hierarchy

    As a PI Admin, I may have already created a AF Element Hierarchy corresponding to my BES or MES source data. Therefore I have no need for the interface to create a new AF Elements and I would like to suppress this completely.

    4 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We are declining this item as we don’t feel it’s the right fit with our overall Batch Framework product strategy. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We have reviewed this idea, and it’s not something we plan to implement. Even though we are declining this idea for now, it is still open to comments. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!

  8. EFGEN - Allow Active Point Trigger Based on Specific Value/Logic/Calculation

    Using EFGen, currently an EF can only be triggered based on the zeroth state of the Active Point. This makes is impossible to trigger different events based on specific values of a single PI Tag.

    I am trying to implement a batch structure using Event Frames with production run as the parent and different phases of the run as children. I have a single PI Tag that lists the current phase of the run in real time. It would be nice to be able to trigger the phase child events based on the specific string values of this tag.

    PI…

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We are declining this item as we don’t feel it’s the right fit with our overall product strategy for EFGen. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We are declining this item as we don’t feel it’s the right fit with our overall Batch Framework product strategy. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

  10. 3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We have reviewed this idea, and it’s not something we plan to implement. Even though we are declining this idea for now, it is still open to comments. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We are declining this item as we don’t feel it’s the right fit with our overall Batch Framework product strategy. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We are declining this item as we don’t feel it’s the right fit with our overall Batch Framework product strategy. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

  13. Allow PI Interface for EMDVB to have the ability to define the source system Time/TimeZone offset.

    PI EMDVB interface stops because of time difference between SQL and PI servers:

    "Error, SQL Server is ahead of PI Server more than 30 seconds, please adjust clocks. "

    That means we should adjust the (SQL server) DCS clock. However 30 seconds seems a short time to me.

    I would like the PI Interface for EMDVB to have the ability to define the source system Time/TimeZone offset.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We are declining this item as we don’t feel it’s the right fit with our overall product strategy for the EMDVB Interface. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We are declining this item as we don’t feel it’s the right fit with our overall Batch Framework product strategy. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We have reviewed this idea, and it’s not something we plan to implement. Even though we are declining this idea for now, it is still open to comments. We do want to hear your opinion. Thank you for the feedback, and please, keep sharing!

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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Batch Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    We are declining this item as we don’t feel it’s the right fit with our overall Batch Framework product strategy. Thank you for your feedback, and please continue sharing your thoughts on how we can better serve you.

  • 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
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED