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

    Add a function that can be used in the UFL Configuration File to perform bitwise operations. For example, a function similar to the AND operator in Performance Equations and Asset Analytics.

    9 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  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your input. We are continuing to support PI Interface for UFL with stability and security releases. However, for feature enhancements, we are starting to develop PI Adapter for Structured Data Files and encourage you to go to the PI Adapters forum to share your use cases.

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

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

  4. DNP3 Interface specify Class for scans

    Create some way to configure PI Points belonging to a DNP3 interface instance such that the interface only requests data for a single class (Class 1/Class 2/Class 3) and not all three? Essentially, an event scan that will request one specified Class 1, 2, or 3 data from the RTU.

    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  ·  DNP3  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your input. We are continuing to support PI Interface for DNP3 with stability and security releases.

    That being said, PI Adapter for DNP3 is now available and we will continue to focus on the PI Adapter for enhancements to DNP3 connectivity. Please check out the release notes and user guide for a comprehensive list of capabilities.

  5. Please allow to use a hex value as a delimiter, which will allow to specify a Carriage Return (0x0D) as a delimiter

    While PI Connector for UFL supports FOREACH (CsvGetItem(__Message, char(13))) to allow using a Carriage Return as a delimiter, it does not support Serial input.
    This leaves PI Interface for UFL the only option to work with Serial input. Please allow to use a hex value as a delimiter, which will allow to specify a Carriage Return (0x0D) as a delimiter.

    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

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

    Thank you for your input. We are continuing to support PI Interface for UFL with stability and security releases. However, for feature enhancements, we are starting to develop PI Adapter for Structured Data Files and encourage you to go to the PI Adapters forum to share your use cases.

  6. choose PI API Version during installation

    At the moment PI API 1.x without Windows Integrated Security is installed as standard. For customers who want to use PI API 2.x with Windows Integrated Security an additional installation is needed. please include both APIs in install-pack and ask during installation what Version should be installed.

    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

    2 comments  ·  Installation  ·  Flag idea as inappropriate…  ·  Admin →

    We pride ourselves on making security a high priority, and PI API for Windows integrated security (WIS) is a prime example of that in product form.  However, the first rule of cyber security is to do no harm. We do not package PI API for WIS with interfaces because it requires security configuration changes that cannot be handled by the interface installer. As opposed to failing the installation, we have decided to continue to package PI API 1 with PI Interfaces and make PI API for WIS available as a standalone download. This will allow you to carry out the manual steps needed to leverage Windows Integrated Security for PI Interfaces.

  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. Allow Buffer to communicate with other buffer

    Currently the PI Buffer Subsystem only has the capability to speak directly with the Data Archive. This setup can have a negative impact on your Cyber Security setup as you are not able to leverage the DMZ between the IT/OT networks as it is designed.

    This request is to allow the PI Buffer Subsystem to communicate with another buffer subsystem to act as a relay to the data archive and would allow all cyber security requirements to be met.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback. While we are declining this functionality request for direct implementation in PI Buffer Subsystem, we encourage you to check out PI Adapters. PI Adapters were designed with use cases similar to the one described here and we hope that they will meet your needs.

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

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

  11. AMI Interface: allow meter data to be writable to PI Point attributes

    Synced to PI Square at https://pisquare.osisoft.com/ideas/29455

    Currently, meter data can only be written to static attributes. Historizing the meter data may be useful if there are expected changes that should be monitored.

    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  ·  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!

  12. Support Automatic Failover for PI UFL

    Currently UFL only supports two independent instances for redundancy purposes.

    8 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  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your input. We are continuing to support PI Interface for UFL with stability and security releases. However, for feature enhancements, we are starting to develop PI Adapter for Structured Data Files and in the process of evaluating failover needs. We encourage you to go to the PI Adapters forum to share your use cases.

  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

    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.

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

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

  16. Modify the Modbus Interface to accept 32-bit Unsigned Ints from the PLC

    provide a data type to accept a 4 byte unsigned integer from the PLC.  At this point, it would be stored in a 64-bit float in PI DA.

    21 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  ·  Modbus Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your feedback. We do not plan to add native support for 32-bit Unsigned Integers to PI Interface for Modbus Ethernet PLC. Please check out the workaround provided in the comments below.

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

  18. Support multiple Modbus devices on the same machine

    Add support for multiple Modbus devices (using the same IP address but different port numbers) on the same machine. For example, the interface could allow the user to configure something like this:

    /dn= xxx.xx.xxx.xx:43120,/cn=1,/polldelay=0,/to=2,/rci=30,/writedelay=0,/debug=0,/disabled=0
    /dn= xxx.xx.xxx.xx:43122,/cn=1,/polldelay=0,/to=2,/rci=30,/writedelay=0,/debug=0,/disabled=0
    /dn= xxx.xx.xxx.xx:43124,/cn=1,/polldelay=0,/to=2,/rci=30,/writedelay=0,/debug=0,/disabled=0
     
    Note: This was previously Enhancement 121980.

    9 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

    2 comments  ·  Modbus Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    While we are declining to add this functionality to the PI Interface for Modbus Ethernet PLC, the PI Adapter for Modbus TCP does support the configuration of Modbus devices with the same IP address and a unique port number. We encourage you to go to the PI Adapters forum to share your use cases.

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

  20. Create a clearer, shorter INI file syntax

    Most of the problems appear in the FIELD, MSG, and message sections of the INI file. Note the difference in clarity, readability, and length between the current and proposed syntaxes below.

    Current syntax:

    [FIELD]
    FIELD(1).NAME="Tag"
    FIELD(1).TYPE="String"
    FIELD(2).NAME="Date"
    FIELD(2).TYPE="DateTime"
    FIELD(2).FORMAT="yyyy-MM-dd"

    [MSG]
    MSG(1).NAME="MessageSection1"
    MSG(2).NAME="MessageSection2"

    [MessageSection1]
    MessageSection1.FILTER = (MessageSection1 message filter)
    (MessageSection1 code)

    [MessageSection2]
    MessageSection2.FILTER = (MessageSection2 message filter)
    (MessageSection2 code)

    Proposed syntax:

    [Variables]
    Tag String
    Date DateTime("yyyy-MM-dd")

    [Messages]

    <(MessageSection1 message filter)>
    (MessageSection1 code)

    <(MessageSection2 message filter)>
    (MessageSection2 code)

    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  ·  UFL Interfaces  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for your input. We are continuing to support PI Interface for UFL with stability and security releases. However, for feature enhancements, we are starting to develop PI Adapter for Structured Data Files. We encourage you to go to the PI Adapters forum to share your use cases.

← Previous 1 3
  • 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