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

  3. 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 →
  4. 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 →
  5. 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 →
  6. 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 →
  7. 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 →
  8. 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,

    21 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 →
  9. Give the ability upload different Tag Naming files in DCM / OPC UA Connector

    When uploading a "Tag Naming" file in DCM, this file completly replace the existing Tag naming. It mean that a Tag naming file must be done for all datasources within one connector.
    It would be a lot more easy when dealing with a large number of tags to be able to import a list of new or modified tags. DCM will then compare the imported file with the existing list and make the required modification or creation.
    An option to delete some datas using a filter will then be usefull.

    20 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 →
  10. Prevent OPC UA Connector 2.x from doing Data Discovery in Tags-Only mode

    Use case: If we are frequently adding OPC UA tags and OPC UA server has a large variable count, then each discovery will increase the amount of time for it to complete. This increases the amount of time needed to discover the data source + configure new tags, and can also exhaust machine resources during the discovery.

    In version 1.3 of the connector, tags-only mode did not do a discovery.

    19 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 →
  11. Transformations and scaling

    Add the ability to configure PI points so that the PI Connector for OPC UA performs transformations and scaling on the values before being archived.

    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 →
  12. 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…

    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. Allow options to alter the way the connector handles different qualities (bad, questionable)

    At this time, the connector does not expose any way to alter the way data of different qualities (bad, good, questionable) is handled. The PI OPC Interface allows several different options with regards to “quality” such as "send only GOOD quality data", "Store Value Flagged Questionable", etc. Some customers will want to keep the quality (eg. Pharma, FDA), while others don't want to (eg. Oil industry). When storing quality is not important, storing BAD and ? is simply a hassle. I would like to have the same functionality as the PI OPCDA interface.

    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 →
  14. Connector should rescan UA server, on a configureable basis, for new objects already defined in CSV file

    It would be helpful if the UA Connector could rescan the UA server for new objects that have already been selected in the AvailableTypeDefinitions file and add them to the server on a configurable frequency.  We primarily use the UA Connector for our wireless implementation and constantly adding one of two types of field devices that are defined.  This would decrease the amount of time in having to stop/start the connector or using the workaround of remaking and changing the CSV file every time a device is added in the field.

    14 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 →
  15. OPC UA Connector Trend Advise Option

    OPC UA Connector Trend Advise Option, such as in the UniInt interfaces

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

    We’ll send you updates on this idea

    3 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  16. Switch for using Name of AF Attributes from Browsable Name or Display Name

    Add a Switch to the OPC UA Connector that we can choose if we want the AF Attributes to be created using "Browsable Name" or "Display Name". Using the Display Name would make it much easier for us to locate the Attribute and refer to its OPC Tag as we can see the same "Display Name" in both PI System Explorer and OPC Tools.

    11 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 →
  17. Need to start/stop individual data sources

    When going in the PI Connector Admin page in the data sources page, we cannot start/stop individual data sources listed when there is more than one. To stop one you need to stop all the data sources listed.

    11 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 →
  18. Warm and cold PI Connector for OPC UA failover

    Currently only hot failover is featured for the PI Connector for OPC UA but this creates a lot of strain on the data sources. We need to be able to select warm/cold failover mechanism.

    8 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 →
  19. OPC UA 2.x - Health information and connector statistics

    In the PI Connector for OPC UA 1.3.x, some very useful statistics are available - Events in DA queue, Data rate, Variables Numbe - but 2.0.x these items are not available anymore. Those items should be available for data selection to be monitored and stored in PI.The same should be true for the PI Connector Relay Statistics

    6 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 →
  20. Make data source redundancy config more flexible

    Some SCADA vendors are still only natively implementing OPC Classic so if one wants to use OPC UA, then a wrapper is needed. If that SCADA is configured in a redundant pair, it is not always true that the wrapper is aware of that or not aware of his corresponding wrapper running on the redundant server.

    In such a case the Redundancy Support tag is 0-None and the Service Level tag (if present) has unknown behaviour.

    Right now the only way to manage that is by configuring two data sources and archive all tags twice (once each data source) and…

    5 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 →
← 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