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. Simple, readable, user-friendly names for all downloadable files

    OSIsoft's downloadable files are inconsistently named; use hyphens (-), underscores (_), and concatenations instead of spaces; and sometimes contain unnecessary abbreviations.

    For users who keep their OSIsoft files in the same folder, this means either grouping files into subfolders that have readable names or renaming the individual files if they want to identify their files by readable names.

    Please consider using straightforward, intuitive names for OSIsoft's files.

    Some examples (top is the current name, bottom is the proposed name):

    OSIsoft.UFL1.1.0.76.exe
    PI Connector for UFL 1.1.0.76.exe

    RDBMSPIx643.23.3.7.exe
    PI Interface for RDBMS (x64) 3.23.3.7.exe

    PIDataLink2017.exe
    PI…

    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

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  2. Minify the HTML, CSS, and JavaScript code of the 1st-generation PI Connectors

    The HTML code of the administration pages of these PI Connectors is over 3000 lines long and is very unoptimized. It also seems like most of the CSS and JavaScript code is inline and so is not taking full advantage of HTTP/2's multiplexing.

    Please put the CSS and JavaScript code in separate files where it makes sense and minify all of the administration pages' code to make the pages load faster and to reduce network traffic. To avoid the extra processing time of minifying the code, the generated code should be minified to begin with.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  3. Do not silently overwrite PIPointPrefix.config.json when a PI Connector is upgraded

    Currently, if you install a new version of a PI Connector, the PIPointPrefix.config.json file is silently overwritten and reverted back to the default. For users that do not use the default prefix, this means that data gets recorded in the wrong tags and not the intended tags, which, in turn, can mean that critical notifications are never sent out.

    In general, files that the user is intended to edit should not be silently overwritten, and files that the user is not intended to edit are safe to be silently overwritten.

    Please consider either making it clear which configuration files will…

    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

    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  4. In the DCM, can we display the PI DA and PI AF versions when we click on the node?

    Display the version of the PI DA and PI AF systems when the user clicks on the node, then clicks a "more" hyperlink, when displaying config the DCM.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  5. Add support to the PI Connector Relay to support OMF Delete and Update actions

    The OMF specification outlines that delete and update messages are included within the specification, but those capabilities are not yet included in the PI Connector Relay. It'd be great to be able to delete or update previously created AF Elements or Types--for example, in the case where an edge device is upgraded to include a new sensor feed, which now needs to be appended to the existing AF Element Template created for that edge device.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  6. Better support for IE

    Some field values are missing or inaccurate when viewed through IE as compared to Chrome.  This was seen in the DCM UI and PSC UI for Data Source configuration.  Some IT environments are locked down to the point that IE built into the OS is the only browser option so it needs to show accurate information.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  7. Be able to browse for PI Asset Database and Root PI Asset Path

    On the Server List page, under "PI Asset servers", after the "Hostname or IP address" of a new PI Asset server has been specified, the user should be able to browse for the PI Asset Database and then the Root PI Asset Path. That is, the user should not have be forced to type these in, which can be error-prone.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  8. Keep a consistent order of PI Data servers on the administration pages

    On the Overview page, the PI Data server list grows downwards from the top. On the Server List page, the PI Data server list grows upwards from the bottom.

    Please use a consistent order for the PI Data server list so then one list does not appear out of order compared to the other list.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  9. Warning when stopping a connector about potential consequences

    Some connectors perform some kind of rediscovery of the data source upon start - Such as meta data or current values, etc. When stopping a connector from the UI, a warning should pop-up indicating potential consequences of doing so and what to expect, such as "Restarting the connector will potentially require a long time in order to perform data source discovery."

    This will prevent users from unnecessarily restarting connectors as a basic troubleshooting mechanism.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  10. Use units in the attribute templates of the element templates that PI Connectors create

    Currently, all of the attribute templates of the element templates that PI Connectors create have their unit stated in their description but do not have a Default UOM assigned to them. Please assign Default UOMs to the attribute templates to save the user from doing this manually.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  11. "Connected" to invalid PI Data servers

    If I add an invalid PI Data server in the Server List page, the PI Connector will say that it is connected to this data source. The status only becomes "Error" when the PI Connector tries to save data to this server. Please change this so that invalid servers produce an error immediately.

    Imagine this scenario. You configure all of the PI servers for the PI Connector. It says that everything is OK. You move on to configuring, say, the INI file for the PI Connector for UFL. When communication fails, you will likely try to troubleshoot the INI file…

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  12. Put a PI Collective note directly on the Server List page

    The PI Connector user guides mention "For a PI Data Archive collective, add each member of the collective to the PI Data servers list, not the collective itself." It would be useful to have this note directly on the Server List page.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  13. Drop support for TLS 1.0 & TLS 1.1 for the 1st-generation PI Connectors

    For the administration pages of the 1st-generation PI Connectors, please drop support for TLS 1.0 & TLS 1.1. These have been known to be insecure protocols for a while now, are not supported by modern browsers, and have been superseded by TLS 1.2 & TLS 1.3.

    "Compatibility with older browsers" is not a good reason to keep them around, since even Internet Explorer supports TLS 1.2 & TLS 1.3. Anyone using an older browser should upgrade for their own good. Since PI Connectors are a newer technology, I'm surprised that OSIsoft even bothered adding support for TLS 1.0 & TLS…

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  14. Add support for TLS 1.3 to the 1st-generation PI Connectors

    The highest version of TLS that the 1st-generation PI Connectors currently support is 1.2. Please add support for TLS 1.3 to make the administration pages of the 1st-generation PI Connectors load faster and more securely.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  15. Add support for TLS 1.3 to the PI Data Collection Manager (PI DCM)

    The highest version of TLS that the PI Data Collection Manager currently supports is 1.2. Please add support for TLS 1.3 to make the PI Data Collection Manager load faster and more securely.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  16. Add support for HTTP/2 to the PI Data Collection Manager (PI DCM)

    Currently, the PI Data Collection Manager's web GUI supports only HTTP/1.1. Please add support for HTTP/2 so that it will load faster.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  17. Connectors should support a Send Rate parameter

    Connectors need adapt to many different types of networks, in both configuration and quality (latency, etc.) of the data transfer. One of the features that interfaces had, but connectors still lack, is the ability to batch the values sent to PI and spread out when they are sent. These are the Send Rate settings for the buffer subsystem, they are requested for connectors as well.

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  18. 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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  19. Make the PI Data Collection Manager default to a more user friendly configuration

    When the PI Data Collection Manager is installed, intuitive defaults are chosen, and intuitive redirects are not set up. The PI Data Collection Manager installation should:

    -By default, check for port 443 and 80 availability on the machine. If they are available, set the collection manager up on port 443, and set up a site on port 80 to do a HTTP -> HTTPS redirect.
    -Set up a redirect, redirecting the root / site to /UI.

    These two changes would greatly improve remote management, and management of the server itself. Rather than doing the intuitive thing and visiting the root…

    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  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  20. Cognex Vision System Connector

    I am interested in a Cognex Vision System Connector.

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