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. Incoming TimeStamps Utc

    Please rename "Incoming TimeStamps" to "Incoming Timestamps".
    Please change "Utc" to "UTC".

    These small spelling issues come across as sloppy.

    3 votes
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  2. PI Connector for FANUC Focus should give a warning to users when they change the machine IP address for an existing data source.

    In the PI Connector for FANUC Focus, each data source has the IP address of the related machine specified. The "Device ID" is also part of the configuraiton. If a Device ID is not specified, the IP address is used as part of the Device ID and ends up becoming part of the AF hierarchy as well as the PI point names.

    If a user goes to change the IP address for an existing data source, and the default Device ID is being used, they will inadvertently create a second set of PI points (Duplicates, orphaning the original PI points…

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
    PLANNED  ·  Abbas Saboowala responded

    Any configuration changes made to the device id or IP address after initial configuration, will be met by a warning message which the user will have to accept before proceeding with the changes.

  3. Use a consistent language-region separator for Locale

    Currently, the language-region separator in the Locale choices can be any of "-" (hyphen-minus), "–" (en dash), or ":" (colon). For consistency, please use only 1 separator.

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  • 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
COMPLETED