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. Revise the PI Connector For OPC UA on 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), and it is the only PI Connector whose platform is "Windows" instead of "X64".

    Please add the Generation 2 version of the PI Connector For OPC UA to the list. Please also change the platform of the PI Connector For OPC UA to "X64" unless there is some special reason for having it as "Windows".

    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 →
  2. Elapsed time of last discovery, being a good feature to add into Connector display under Data tab in DCM

    Elapsed time of last discovery is a good piece of information and being a good feature to add into Connector display under Data tab in DCM page.

    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. Add a checkbox disabling Tag and Element creation

    Case1:
    OPC UA Connector configured in a way that if the automation system will offer new tags, they will be created on PI system automatically. However, this makes running out of tags on the PI Server. Is there a possibility to start the OPC UA Connector, although new tags cannot be created.
    Case2:
    In a “validated environment”  in pharmaceutical companies, no one (including Connectors) is supposed to make changes in the system configuration without extended paperwork.

    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 →
  4. 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 →
  5. Connector syncing to existing points in the DA/AF servers.

    Can there be another Excel export/import step when establishing the "Destination" where the "Source" points be matched w/ what points already exist in the DA/AF server?

    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 →
  6. PI Connector automatic configuration file loading

    Have PI Connector for OPC UA to read automaticaly the tag configuration file (.CSV).

    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 →
  7. 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  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  8. Identify the updated or changed nodes on the Type Definitions Export

    Be able to identify the changed (new, updated, removed) nodes that are exported in the Available Type Definitions file through the connector interface.   For systems that are in flux, there's not another way to identify those PI AF elements / attributes that are changed without saving different versions of the Export file and using a file comparison tool to see what has changed.  If the export file contained a date on each item on when it was created/updated (if that's available) that would help identify the new or changed items.

    When there are nodes and attributes that were removed from…

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