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. Support HTTP Token Authentication to a REST Endpoint

    The REST endpoint from which I want to pull data requires token authentication. I would like the UFL Connector to be able to obtain the token given the username and password I enter on the Admin page.

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

    We’ll send you updates on this idea

    4 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  2. Linux Version of PI OPC-UA Connector

    This should be self-explanatory.  I'd also suggest making Linux versions of all software available, but this Connector would be a great start.

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

    We’ll send you updates on this idea

    1 comment  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →

    We are evaluating this proposal. If this request is for a specific distribution of Linux, kindly forward that information to me or please leave a comment with the device type/name or Linux distribution name.

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

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

    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. Get Description from the OPC UA Server into the AF attribute

    Get Description from the OPC UA Server into the AF attribute

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

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →

    Description is currently supported only for PI Tags and AF Elements from version 1.3.×.×. However, description cannot currently be set at an attribute level.

  6. 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?”

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

  7. Make the UFL Connector logic development/testing/debugging process less tedious

    Deploying a UFL Connector solution requires a LOT of edits of the INI file as part of the development/testing/debugging process. After each INI file change and file save, the required procedure is as follows:
    1. Click on the Data Source List link.
    2. Click on ‘See Configuration’.
    3. Click on the ‘Change’ button.
    4. Click on the ‘Browse…’ button.
    5. Double-click on the INI file.
    6. Scroll the page down until the ‘Save’ button is visible (I’m using a 1920 x 1080 monitor).
    7. Press the ‘Save’ button.
    8. Click on the ‘Overview’ link.
    9. Press the ‘Start connector’ button.

    20 votes
    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 →
  8. 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 →
  9. UFL Timezone Conversion

    Supported timestamps are currently limited to Local or UTC timezones.

    Data sources may not be configurable to provide timestamps in supported formats.

    There currently exists no robust or simple way of converting between timezones using the UFL syntax or configuration.  Including custom daylight savings time logic in ini files for this is not a maintainable solution. DST rules change over time and vary from region to region.

    With the current limitations I am currently having to maintain more than 20 ini files with custom DST logic for our global operations.

    Including functionality to accommodate for the timezone formatting limitations of…

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

    We’ll send you updates on this idea

    4 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow the connector to use a proxy for web requests

    Provide a way to configure the connector to use a proxy and authenticate with the proxy if required.

    19 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 →
  11. Write event when data source is offline

    As a PI admin I would like the OPC UA connector to write a value such as 'disconnected' when the data source is offline so that I know when the connector is unable to connect to the data source,

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

    We’ll send you updates on this idea

    1 comment  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  12. OPC UA: Set PI Tag Zero and Span Based on OPC UA Range

    For OPC UA Analog Items, the OPC UA standard mandates an EURange property and an optional InstrumentRange property. These Range properties contain a Low and High field.The PI Connector for OPC UA should have an option to use either of these Ranges to set the Zero and Span of the PI tags it creates and the Maximum and Minimum AF Attribute Traits.

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

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  13. 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.

    18 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. Add the ability to select a subset of PI Points from a PI Data Archive

    The PI System Connector allows to include PI Point replication directly from the PI Data Archive even if they are not reference in the PI AF hierarchy with the "Include all PI points from this PI Data Archive" option.

    I would like to replicate only some PI Points that are not referenced, not all. This would remove the need to maintain both a PI to PI and a PI System Connector.

    I could create a bogus AF Database referencing those points but I would prefer not to.

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

    We’ll send you updates on this idea

    3 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →

    As suggested in the description of this item, PI System Connector uses AF database as the primary source and thus any filtering that is desired at the PI Tag level can be accomplished by referencing only those tags in the source AF database. If users would only like to replicate PI tags without an AF model, then PI-to-PI interface can serve as an alternate option.

  15. PI OPC UA Connector - point attribute based configuration

    We are just starting the first tests with PI OPC UA Interface. We notice that the classic method of tag configuration, known from the interface, is no longer possible. This is probably due to the connector concept.
    Unfortunately, this does not fit with our central approach of tag configuration. We urgently need a way to control the transfer of the data into the archive, as usual from the interfaces, via the point attributes.

    Since there is a tags-only mode - is there any hope that there will be an OPC connector mode so that the connector behaves more like an…

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

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  16. PI Connector for ICCP

    Implementation a connector that supports the ICCP TASE 2 protocol

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

    We’ll send you updates on this idea

    1 comment  ·  New PI Connector request  ·  Flag idea as inappropriate…  ·  Admin →
  17. Enable setting tag attributes in UFL Connector

    UFL Connector should have ways to set tag attributes. There should be way to set the default compression and exception settings and also other tag attributes like point and data security.

    16 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 →
  18. 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.

    15 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. Develop PI Connector/Adaptor for AspenTech IP21 for the PI System and OCS

    We have customers who are using AspenTech IP 21 and would like to have data replicated in both PI DataArchive and OCS in the future. Since the PI Interface is a bit outdated, a new PI Adaptor would make perfect sense (since there is already a PI Connector for WonderWare and Honeywell PHD). The PI Adaptor shall support both PI and OCS.

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

    We’ll send you updates on this idea

    2 comments  ·  New PI Connector request  ·  Flag idea as inappropriate…  ·  Admin →
  20. Reduce Number of Point Sources for PI Connector for PI System Health

    PI Connector for PI System Health creates a LOT of different point sources for the Pi points it creates on the Data Archive. Some customer may prefer to not have so many point sources show up for one interface/connector. Adding a method to reduce/condense point sources pre-point creation would eliminate to need to edit the point sources manually afterwards.

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

    We’ll send you updates on this idea

    2 comments  ·  Other specific PI Connector  ·  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/PREVIEW
COMPLETED