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.

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. Support PI tag renaming

    Tags created by a PI Connector can be renamed, but these renamed points can be "forgotten" if the Connector's point cache is lost. Updating the Tag Mapping configuration file can avoid this cache loss, but I would like to be able to rename Connector tags without updating this configuration file.

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

    We’ll send you updates on this idea

    12 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  2. Monitoring Connector health

    Support for health tags (similar to UniInt health tags), Windows performance counters, or any other way to bring Connector status and health information into PI tags to put them side-by-side with Interface health monitoring.

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

    We’ll send you updates on this idea

    13 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  3. PI Connector for IEC 60870-5-104 bi-directional between SCADA and PI

    RWE Power AG

    “But one really important feature we need, is the ability to write back from PI into the SCADA system
    Until now, we couldn’t find anything about this (important) functionality.
    So our question is if we can use this connector bi-directional?
    And if not, is this already in the roadmap for this connector?”

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

    We’ll send you updates on this idea

    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →

    Can you share with us any info about your use case for sending data back to the SCADA system? For example, what is the purpose of that data? How many tags and how often will you send?

  4. Output tags on connectors

    Sometimes we need to send data back to our sources. Connectors should support output tags

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

    We’ll send you updates on this idea

    RESEARCHING / EVALUATING  ·  6 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow restarting on a data source basis instead of having to restart the connector

    Example 1 - OPC
    If a new connection needs to be made to one OPC Server, restarting the connector forces all data sources (and potentially connections to multiple OPC Servers) to be restarted.

    Example 2 - UFL
    If my web service is down and I do not want to connector to keep trying to access to REST Server, I cannot stop/disable only one data source

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

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  6. Option to remove/edit template prefix

    Allow for connectors to create templates without the fixed prefix. E.g. The option to name an AF template "templatename" and not "UFL.templatename"

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  7. Ability for PI Connectors to create future data point

    Add the ability for PI Connectors to create future data point. This is especially useful for the PI Connector for UFL. The current workaround is to manually create the point as a StoredValues=FutureData.

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  8. 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.

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

    We’ll send you updates on this idea

    3 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  9. Control which PI/AF servers each data source sends data to.

    Right now, for one instance of the connector, all configured data sources will send data to all configured PI Data Archives and PI AF Servers. It is all or nothing. Due to the fact that you cannot have multiple instances of the same connector on any given node at a time, if you want this kind of granular control you would need an entirely new node and another connector. In the past, it was trivial to have multiple interfaces instances on the same node to send different data to different PI Data Archives; connectors should allow this capability.

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  10. 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.

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

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  11. Put a REST endpoint on all connectors

    It would be very useful to see the data flowing through a connector at the edge, or even the data buffered in a connector. Every connector could have a rest endpoint with the same methods as PI Web API. Possible uses:

    -Diagnose connection/configuration issues
    -Attach a dashboard directly to the connector on the node (for example a display on a monitor in a mining truck)
    -Attach third party software for local analysis or alarming of equipment status (for example, alerting the driver of a truck of important events)

    I'm sure there are many others...

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

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  12. 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.

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

    We’ll send you updates on this idea

    2 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  13. Make "Cancel" a button, not a link

    In the configuration page of any data source, there is a "Save" button and a "Cancel" link. This is unnecessarily inconsistent. Please make "Cancel" a button.

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  14. Write an error message to logs when no destination PI Data Archive is specified

    Ran into this problem when configuring a new UFL connector. After install, I went straight to configuring my .ini--forgetting to add the PI Data Archive (in fact, the connector was actually installed on the DA node).

    I had the text files coming in and being processed by the connector without any errors, but saw nothing being created in my data archive. Eventually, I realized I had forgotten to add my destination server. This is an error you would typically never run into with interfaces since they require you to specify a destination when configuring a new instance. There should at…

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  15. Better error handling in DCM UI

    For some cases where disallowed or poor configuration causes unexpected behavior, the UI should give a visual indicator and explanation.  Two examples:
    1. No write access for Relay to AF DB when using the PSC.  Result: replication of AF objects fails with many error messages.  Digging through log, found a message that indicated permissions issue on target AF DB.  In DCM, all was green. Would have been good to have an error or warning symbol on the Relay object with message about missing write permissions on Destination.
    2. Added a second destination AF DB with reference to same Data Archive. …

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

    We’ll send you updates on this idea

    0 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  16. 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 Sign in with OSIsoft
    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.

  17. 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 Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

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

    We’ll send you updates on this idea

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