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. Real Time Snapshot Support

    PI System Connector:  Need real time snapshot data support for the PI System connector.

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

    We’ll send you updates on this idea

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

    Update: PI System Connector 2.3.0.1 is not available at this time due to an issue identified with this version. We are working quickly to provide an updated version that resolves this issue.

    Original Post: I’m really excited to announce that PI System Connector 2.3.0.1 is now available with snapshot support for PI Points that have compression disabled/off (on the source system). I cannot wait to hear your feedback on this latest version. Head over to https://my.osisoft.com/ to learn more about 2.3.0.1.

    We will be keeping this feedback item alive as we continue to work on the next release of PI System Connector. The next release is expected in early 2021, and will expand upon the snapshot support introduced in 2.3.0.1 by adding configuration options and snapshot support for compressed PI Points.

  2. Develop an interactive INI editor for the UFL Connector

    The editor should allow you to see in real time how it interacts with the data. Being able to test the INI file prior to loading some file would make it much more manageable to read a variety of data format and insure that it has the expected behavior before starting the connector and having to use a trial and error approach. A good example of this is what Microsoft does with PowerQuery in PowerBI. This would allow troubleshooting UFL issues much more easily and allow more people to use the connector without having to spend a serious amount of…

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

    We’ll send you updates on this idea

    EVALUATING  ·  4 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  3. Connector-level Failover - OPC UA 2.x

    Support connector-level failover in PI Connector for OPC UA 2.x (relay-enabled version). Similar to UniInt failover (interfaces), failover should be data source specific and always favor the data source in the better state.

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

    We’ll send you updates on this idea

    4 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  4. Retrieve data even it's not changed on OPC server

    Currently Connector configured to rertieve event on change and not based on a scan class like interfaces.The Connector suscribes to the changes, and when a change comes in to the server, the data will be sent to PI connector. We need option to retrieve the data every certain minutes even data is the same and is not changed on OPC server.

    Saken
    TCO

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

    We’ll send you updates on this idea

    7 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
    EVALUATING  ·  Abbas Saboowala responded

    We understand that for slow changing points, values might not change often and thus there is a need to collect values at certain time intervals as opposed to on change. However, scanning at frequent intervals leads to increased load on the server and thus can lead to performance degradation. We are discussing how best to solve this problem with PI Connector for OPC UA.

  5. Connector Failover

    Add failover capability so I can run a pair of connectors that will failover to the backup if the active is unavailable

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

    We’ll send you updates on this idea

    3 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  6. PI OPC UA Connector Array support

    Add reading capability for OPC UA Arrays. Currently items with “ValueRank“ = 1 are ignored.

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

    We’ll send you updates on this idea

    4 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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 →
  8. PI System Connector with mode to synch AF Analysis and Notifications Templates

    As an equipment specialist working centrally, I wish to deploy my AF Element Templates including Analysis and Notifications Templates to my remote sites so I have them managed from a central location. This also insures that remote sites are using the same calculations and KPIs.

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

    We’ll send you updates on this idea

    1 comment  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →

    We are aware of the interest in this functionality, but at this time it is not in our short-term plans to implement.

    We would like to learn more about the different scenarios in which you would be syncing your Analyses and Notifications.
    Please continue to share your use cases here.

  9. OPC UA: allow a host name override

    Allow a hostname override when connecting to the OPC UA endpoint.   We have some use cases where the URL returned by two independent OPC UA servers has the same name.  This prevents the Connector from connecting to the correct endpoint. Allow an IP address to be specified in the config, which would be used to connect instead of the URL hostname.

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

    We’ll send you updates on this idea

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

    32 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 →
  11. Replicate AF Analyses with PI System Connector

    I would like to have the option to replicate AF Analyses using PI System Connector with the option to mark the desired analyses for replication.

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

    We’ll send you updates on this idea

    1 comment  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
    EVALUATING  ·  Abbas Saboowala responded

    There are several edge cases when it comes to replicating analyses. This item needs more deliberation.

  12. Get data by polling

    Support acquiring data by polling the OPC UA server rather than subscription.

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

    We’ll send you updates on this idea

    2 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  13. PI Connector for IEC 60870-5-104 writes 'No Data' or another SYSTEM digital state when connection to the Data Source is lost.

    This connector is specially used to monitor the connection of the machines, but if there is a general network crash, and the connector losses the connection to the Datasource, it will stop sending data instead of sending something to alert of the situation.
    Not being aware of that situation can cause big impact in the companies.
    Receiving a Sytem digital state when the connection to the data source is lost would help to create an alarm and let the people in charge know.

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

    We’ll send you updates on this idea

    0 comments  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  14. 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.

    25 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 →
  15. 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 →
  16. 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 →
  17. 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…

    24 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 →
  18. PI System Connector should be able to delete values on the destination server if they are deleted on the source server

    Sometimes when performing analysis recalculations, values are dropped from when they were initially recalculated. For example, when an analysis runs initially, it may calculate 15 values, which are then written to the source and transferred over to the destination as expected. However, if I perform a recalculation where I choose to permanently delete existing values and recalculate due to some of the analysis inputs having changed, and only 10 values are now written to the source server, these values are written to the destination, but the existing values that are now "incorrect" are still present. I would like for the…

    23 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 →
  19. Do not synchronize description from OPC UA server into PI Tag

    There are situations when customer prefers to use “description” in PI Tag attribute that is independent from item “description” provided by OPC UA Server.  
    Currently, during each synchronization, the OPC UA Connector synchronizes descriptor from OPC UA to PI Tag and overwrites desired “Descriptor” attribute provided by customer. 
    Although the solution would be to have desired description already on the OPC UA Server, in some situations (OPC Server managed by 3rd party) it is not possible. It would be good to have configurable parameter in OPC UA Connector, which disables synchronization of item description from OPC UA Server to PI tag.

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

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

    We have started development to include the ability to specify a query that will define which PI Points are included in the data sent from the source to the destination using PI System Connector. We look forward to sharing more with you about this release in early 2021.

← Previous 1 3 4 5 14 15
  • 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