PI Connectors

Welcome to the PI Connectors feedback page!  

We created this forum to hear your ideas, feature suggestions and feedback on PI Connectors. 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. 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

    2 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  3. Connector-level Failover - OPC UA 2.x

    Support connector-level failover in PI Connector for OPC UA 2.x (relay-enabled version). Similar to UniInt failover (interfaces), failover should be data source specific and always favor the data source in the better state.

    159 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

    14 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  4. OPC UA Historical data recovery

    The PI OPC UA connector can manage historical data recovery when connection is lost between the OPC UA server and the connector, but if the connection problem is between the OPC UA server and the data source on field, when connection is recovered and pending data is available in the OPC UA server there's no way to recover it using the connector.

    6 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  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  5. Give the ability upload different Tag Naming files in DCM / OPC UA Connector

    When uploading a "Tag Naming" file in DCM, this file completly replace the existing Tag naming. It mean that a Tag naming file must be done for all datasources within one connector.
    It would be a lot more easy when dealing with a large number of tags to be able to import a list of new or modified tags. DCM will then compare the imported file with the existing list and make the required modification or creation.
    An option to delete some datas using a filter will then be usefull.

    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

    2 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  6. Do not synchronize description from OPC UA server into PI Tag

    There are situations when customer prefers to use “description” in PI Tag attribute that is independent from item “description” provided by OPC UA Server.  
    Currently, during each synchronization, the OPC UA Connector synchronizes descriptor from OPC UA to PI Tag and overwrites desired “Descriptor” attribute provided by customer. 
    Although the solution would be to have desired description already on the OPC UA Server, in some situations (OPC Server managed by 3rd party) it is not possible. It would be good to have configurable parameter in OPC UA Connector, which disables synchronization of item description from OPC UA Server to PI tag.

    32 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

    3 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  7. Prevent OPC UA Connector 2.x from doing Data Discovery in Tags-Only mode

    Use case: If we are frequently adding OPC UA tags and OPC UA server has a large variable count, then each discovery will increase the amount of time for it to complete. This increases the amount of time needed to discover the data source + configure new tags, and can also exhaust machine resources during the discovery.

    In version 1.3 of the connector, tags-only mode did not do a discovery.

    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

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  8. View more detailed buffer queue statistics for PI Connector for OPC UA

    I would like to get a more detailed view of the buffer queue for the PI Connector for OPC UA. In particular, I would like to be able to see the number of PI Events in the queue (not just the number of Tau Messages) and the amount of space filled in the buffer queue file.

    10 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

    4 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  9. Support for Alarms and Conditions

    We need to be able to handle Alarms and Conditions into the PI system. We are moving away from OPC classic into OPC UA.

    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  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  10. Add PI Connector For OPC UA (Generation 2) to the Data Collection List page

    Currently, only the Generation 1 version of the PI Connector For OPC UA appears in the Data Collection List (https://techsupport.osisoft.com/Products/PI-Interfaces-and-PI-Connectors). Please add the Generation 2 version of the PI Connector For OPC UA to the list.

    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  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  11. Read the historical data of a variable from OPCUA server when PI connector (version 1.3) is running

    • In my OPC UA server, each node is historized for 7days of time in order to avoid the data loss in case of internet issue/communication issue in field devices.
    • When the PI connector is stopped and restarted for some time interval, data missed during that period has been recovered successfully.
    • While PI connector is running, I want to read and store this historical data of each node in PI server. It would be great if any options available in PI connector (version 1.3) to view and store this historical data?. Thank you
    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  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  12. Make data source redundancy config more flexible

    Some SCADA vendors are still only natively implementing OPC Classic so if one wants to use OPC UA, then a wrapper is needed. If that SCADA is configured in a redundant pair, it is not always true that the wrapper is aware of that or not aware of his corresponding wrapper running on the redundant server.

    In such a case the Redundancy Support tag is 0-None and the Service Level tag (if present) has unknown behaviour.

    Right now the only way to manage that is by configuring two data sources and archive all tags twice (once each data source) and…

    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  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  13. Import function for data selection in PI Data Data Collection Manager

    During setup of a new data source we always face a long list of several thousand tags where we only need a couple of hundred. We have also a list with tagnames available as .xlsx or similar. The idea is to have an import function for that list to automatically select / create the selection rules for that given set of tags.

    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  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  14. OPC UA 2.x - Health information and connector statistics

    In the PI Connector for OPC UA 1.3.x, some very useful statistics are available - Events in DA queue, Data rate, Variables Numbe - but 2.0.x these items are not available anymore. Those items should be available for data selection to be monitored and stored in PI.The same should be true for the PI Connector Relay Statistics

    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  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  15. Connector should create point in PI server irrespective of the source tag value field, whether blank or null

    Connector should create point in PI server irrespective of it's value status in OPC UA server side, whether the source tag value field is blank or null, in either case, PI tag should be created for PI Connector for OPC UA 2.0.

    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

    1 comment  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  16. Enhance data collection manager compatibility

    At the moment also the newest version of the DCM has many issues with different browsers. Buttons will not work, lists doesn't scale right and sliders hinding. Especialy the performance leak. We have 8 datasources with 500k values and 800 tags selected. If I want to select new values it takes up to 1 minute until it is processed. I suggest to devide the selection process to source base not on connector base.

    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  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  17. Remove AF Requirement for PI Connector for OPC UA

    Remove the AF requirement for PI Connector for OPC UA.

    Users who may only be looking to send data from PI Connector for
    OPC UA to Data Archive are currently forced to configure connections/security for AF as well during initial setup.

    6 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  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  18. Need to start/stop individual data sources

    When going in the PI Connector Admin page in the data sources page, we cannot start/stop individual data sources listed when there is more than one. To stop one you need to stop all the data sources listed.

    17 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  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  19. An import-export feature for PI Connector for OPC UA similar to the one used to configure OPC DA points

    Having to select the OPC UA server points to import from a list with thousands of points where a naming rule is not followed is a never-ending task using the OPC UA Connector web interface. My suggestion is to create an interface similar to the one on the OPC DA interface where it is possible to export the complete server’s point list to a csv file, remove the undesired ones, and import back the csv file.

    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  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  20. Switch for using Name of AF Attributes from Browsable Name or Display Name

    Add a Switch to the OPC UA Connector that we can choose if we want the AF Attributes to be created using "Browsable Name" or "Display Name". Using the Display Name would make it much easier for us to locate the Attribute and refer to its OPC Tag as we can see the same "Display Name" in both PI System Explorer and OPC Tools.

    12 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  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
← 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