PI Connectors

Welcome to the PI Connectors feature suggestion box. We created this forum to hear your ideas, suggestions and feedback.

Please suggest your most important features and design change ideas on this site! Also vote for your favorite features now! We welcome your feedback.

  • NOTE: for documentation feedback and bugs, please report to Documentation@osisoft.com rather than entering them on this site.

How can we improve PI Connectors?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. PI Point name Illegal character handling in PI Connectors

    Currently source points for PI Connectors that contain illegal characters are handled differently depending on the PI Connector. Some will replace the character while others will map an illegal character replacement when creating the PI Point. These illegal characters should be dealt with the same across all PI Connectors. Examples of illegal data source Characters: * ' ? ; { } [ ] | \ ` "

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    We have started implementing a way to handle illegal characters in Wonderware and UFL Connector. If this behavior is desired for a connector besides Wonderware and UFL kindly leave a comment below.

  2. PI System Connector Destination AF Configuration String should not Contain Source PI Server Name if it is Unreachable

    Currently, if the PI Server specified in the source PI AF server is unreadable from the PI System Connector node, the Connector will forward the listed source PI Server name in the configuration string to the destination AF Server. This causes confusion as the Destination AF server will likely not have access to the unreachable source PI Server. Instead, The connector should create a configuration string on the destination AF server stating that the source PI Server Host is unreachable.

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  3. 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
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  4. 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
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  5. Handle deletions across systems

    Ability to have deletions replicated across systems as well (might need to be a config option on how to handle).

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  6. Allow the AF root element name to be configurable

    The root element in AF is determined by the Connector code.  Allow the name of the root element to be specified by the user.

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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.UFL_1.1.0.76_.exe
    PI Connector for UFL 1.1.0.76.exe

    RDBMSPIx64_3.23.3.7_.exe
    PI Interface for RDBMS (x64) 3.23.3.7.exe

    PIDataLink_2017_.exe
    PI DataLink 2017.exe

    PI-DataLink-2017-User-Guide-EN.pdf
    PI DataLink 2017…

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  9. Allow data sources and servers to be renamed

    Currently, if you want to rename a data source, PI Data server, or PI Asset server, you must delete the one with the old name and create a new one with the new name, and redo all of the configuration. This is especially a pain for data sources, since they have a lot of configuration.

    Please allow data sources and servers to be renamed to avoid this trouble.

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  11. Rockwell CLX Connector

    I am interested in a Rockwell CLX Connector.

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  New PI Connector request  ·  Flag idea as inappropriate…  ·  Admin →
  12. Read files from .zip folders

    Would like UFL connector to take a .zip folder and read the files within that folder

    3 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  13. DeltaV Smart Connector Update to OPC UA

    The newest release of DeltaV has the capabilities of enabling an OPC UA server that could be used to transmit realtime date from DeltaV to the PI database. Right now, the interface between the two systems uses OPC DA. With DeltaV's plan to migrate to only using OPC UA, Is there a roadmap to update the smart connector such that it uses OPC UA for realtime data transmission? This could allow the OPC UA connector to be placed on the PI data server directly since it is much easier to setup OPC UA connections across physically separate machines (as opposed…

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  14. Merge Two Tags or Copy Tag Data to a New Point

    Sometimes, when dealing with APS, a new TAG is generated for an existing point. Data stops going to the old point. It would be nice if there was an easy way, within the gui (not manually dumping and importing) that we could take the values from one tag, and place it into the new tag.

    There are other times when we may want to copy all historical values from a tag, and place it into a new tag.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  15. Synchronize behavior between PI Connector for Cygnet and Cygnet enumeration value representation

    The values stored in the “Table Entry” column in Cygnet TRS should match the “State” column in the PI Server Digital states table. This way end users are not confused why the trends in PI do not match the trends in Cygnet.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  CygNet  ·  Flag idea as inappropriate…  ·  Admin →
  16. 2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  17. 2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  18. Support choosing which collective member is the data source

    When configuring the PI System Connector, there is currently no option to constrain the communications for the data source of PI Tag data to a secondary or tertiary PI Collective member.

    The ability to force the PI System Connector to use the secondary or tertiary PDA as the data source will allow customers worried about impacting their primary archive's performance to manually balance the load on their collective and eliminate impacting the performance of their existing solutions.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  19. PI Connector Relay support write modes

    While writing data to PI through the connector relay there seems to be no option to control the write mode . E.g."[-109] Value at This Time Already Exists" is shown in the logs if the archive already contains an event with the same timestamp. The default update option can be "Replace" instead of NoReplace. Other write options can be made configurable.

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  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
NEEDS MORE DISCUSSION
RESEARCHING/EVALUATING
DECLINED
PLANNED
STARTED/IN DEVELOPMENT
IN BETA
COMPLETED