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. 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

    39 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 →
  2. 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.

    25 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 →
  3. Support Assigning Point Sources for Connectors

    Connectors currently assign point sources; this is not user configurable.  In addition, all connector of like kind get the same point source.  This makes it difficult to determine which tags "belong" to which connector node.  Users would like to be able to monitor\count\filter searches based on connector node.

    24 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 →
  4. 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.

    22 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 →
  5. 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.

    21 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"

    20 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. Have option to enable exception on Connectors.

    There are use cases where data is sent over networks with latency (satellite link, for example) so being able to filter out noise at the connector is important.  This is also important when a connector sends data to a local PI Server in the field (low latency), but then PItoPI is used to send snapshot updates to a central PI Server over a high latency link.

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

    We’ll send you updates on this idea

    4 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.

    11 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. PI Connectors buffering (Tau) - provide configuration options

    As a PI Administrator, I would like to be able to DISABLE or configure Tau buffering SO THAT after a network outage the flood of data doesnt overload my network switch and PI DA. My current use case doesn't require the data that may be lost during a network outage.

    I would like to be able to throttle the number of events that are sent ot the PI DA via Tau buffering so that the PI DA can ingest the data without building event queues.

    Specific connector: PI Connector for EtherNet IP which is used for high speed data collection.

    10 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. 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.

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

    We’ll send you updates on this idea

    4 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  11. Exclude Bad values from data collection in PI Connectors

    PI connectors such as OPC UA, Wonderware and Cygnet send BAD values from the data source. We would like the option to filter these values out at the connector level such that they do not make the PI Data Archive.

    8 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 →
  12. Increase the default log size

    The current default log size in the event viewer is 1MB. Although it can easily be increased, a larger default (100MB+) would allow to catch errors the first time they occur and allow for further troubleshooting then having to change it and have to replicate the error one more time.

    8 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 →
  13. 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...

    8 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 →
  14. PI Connector for MQTT - support more generic JSON formats

    While the existing support for Sparkplug MQTT format is helpful, this connector would be more useful if it also supported a more generic JSON format.

    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 →
  15. 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.

    6 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. 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 →
  17. 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 →
  18. Support for Chromium-based version of Microsoft Edge

    Currently OSI has not tested web-based PI tools with Chromium-based version of Microsoft Edge.
    It will be helpful to know if there are plans for it to become officially supported by a certain time, since eventually Chromium-based Edge will get pushed to all of end users

    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 →
  19. 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 →
  20. 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
    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
TELL US MORE
EVALUATING
PLANNED
IN DEVELOPMENT
COMPLETED
DECLINED