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. implement the option to choose between append or replace in the configuration

    It would be nice to be able to choose between append or replace when configuring a new source in a PI system connector, to be able to choose how to copy the data in real time. Since right now by default it is like replace. In the RDBMS interfaces of the source we have several data with the same timestamp, and when copying that data the connector to the destination system only copies the last value, that is, it replaces it. We would like it to be possible to choose between append or replace data copy and that the data…

    16 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    5 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  2. 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.

    103 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    8 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  3. Remove or disable the PI Connector UFL function which puts "Excluded" into attributes

    If the user has two different UFL flows working on same elements and attributes, one flow puts "Excluded" into the attributes created within the second one and vice versa.

    Giving the possibility to the user to disable this function would be a smart solution.

    (To give an example: if one UFL flow creates elements and its attributes and another flow creates only EventFrams referenced to those created elements, there are 2 ways:
    1) having EventFrames referenced to elements (using "StoreElement" funcion tin the INI file) and all attributes created with the first flow in "Excluded"
    2) having EventFrames not referenced…

    18 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  4. Allow specification of PI Point Attributes set by the PI Asset Connector for Emerson DeltaV 3.X

    The PI Asset Connector for Emerson DeltaV 3.X sets PI Point Attributes either based on the values in the enterprise historian configuration file (EntHist.xml) or based on default values.

    It would be useful to have the option to adapt the PI Point Attributes set by the DeltaV Asset Connector before a PI Point is created. These are: PtClassName, PointSource, PtOwner, PtGroup, DataOwner, DataGroup, PtAccess, DataAccess, DisplayDigits, ExcDev, Location1, Location2, Location3, Location5, Shutdown.

    So far, it is only possible to adapt them after the PI Point creation (for example by using PI Builder or SMT > Point Builder).

    12 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  5. Allow the PI Connector for UFL to call a REST endpoint using the POST method

    I have come across customer requirements asking for the possibility of calling a REST endpoint using POST, from a PI UFL connector running as a "REST Client".

    So far, the workaround has been to develop an intermediary custom script which would call the REST endpoint using the POST method, store the results in flat files, and then have the connector pick them up from there.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  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.

    29 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  8. PI Connector for Wonderware Historian should be configurable to use 'FULL' mode query

    The connectors should have a standard behavior. We believe the Wonderware connector should be collecting data in the same way as the Cygnet connector by getting all the data stored in the source historian irrespective of the value change. Currently, PI Connector WWH uses 'DELTA' mode query where only the changes are retrieved. In some situations, the source value doesn't change much, but we still want to collect the data reliably on PI. To accomplish this, we would like to have the ability to configure the connector to use 'FULL' mode query. Without this Full query option, we have to…

    5 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  9. 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

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Other specific PI Connector  ·  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.

    21 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  11. OPC UA Historical data recovery

    The PI OPC UA connector can manage historical data recovery when connection is lost between the OPC UA server and the connector, but if the connection problem is between the OPC UA server and the data source on field, when connection is recovered and pending data is available in the OPC UA server there's no way to recover it using the connector.

    3 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  12. Windows Authentication on the Wonderware SQL databases

    Currently, if SQL server authentication is disabled on the SQL server hosting the Wonderware Historian, the connector cannot authenticate and read from it because the connector is designed to authenticate explicitly using SQL credentials. To be able to authenticate using Windows authentication is essential for some customer to be able to implement the PI Connector for Wonderware Historian, as some organizations disable SQL server authentication for security purposes.

    6 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    IN DEVELOPMENT  ·  0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  13. Support for Alarms and Conditions

    We need to be able to handle Alarms and Conditions into the PI system. We are moving away from OPC classic into OPC UA.

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  14. Revise the PI Connector For OPC UA on the Data Collection List page

    Currently, only the Generation 1 version of the PI Connector For OPC UA appears in the Data Collection List (https://techsupport.osisoft.com/Products/PI-Interfaces-and-PI-Connectors), and it is the only PI Connector whose platform is "Windows" instead of "X64".

    Please add the Generation 2 version of the PI Connector For OPC UA to the list. Please also change the platform of the PI Connector For OPC UA to "X64" unless there is some special reason for having it as "Windows".

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  15. Read the historical data of a variable from OPCUA server when PI connector (version 1.3) is running


    • In my OPC UA server, each node is historized for 7days of time in order to avoid the data loss in case of internet issue/communication issue in field devices.

    • When the PI connector is stopped and restarted for some time interval, data missed during that period has been recovered successfully.

    • While PI connector is running, I want to read and store this historical data of each node in PI server. It would be great if any options available in PI connector (version 1.3) to view and store this historical data?. Thank you

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  16. Import function for data selection in PI Data Data Collection Manager

    During setup of a new data source we always face a long list of several thousand tags where we only need a couple of hundred. We have also a list with tagnames available as .xlsx or similar. The idea is to have an import function for that list to automatically select / create the selection rules for that given set of tags.

    2 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    7 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  OPC UA  ·  Flag idea as inappropriate…  ·  Admin →
  18. PI Connector for IEC 60870-5-104: to filter IOAs

    Considering the following scenario encountered by the customer:

    In IEC-104 data source, there might be 500 signals of single point (type=1, MSPNA1) and 1000 measurements of normalized value (type=9, MMENA1); however the customer would not like to transfer all those signals and measurements into PI system with PI Connector for IEC 60870-5-104.

    How to configure the connector to filter them (such as filter them by IOA of signals and measurements)? Just like what can be done with filter file in PI OPC UA Connector?

    9 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  19. Allow rename of tags for IEC-60870-104 connector

    The connector should allow sending the data to a custom tag name. The combination of ASDU and IOA are not useful to end users without the signal list.

    There should also be an option to automatically combine the quality flags with the value e.g. if the quality is not valid, then write the quality code to the value

    1 vote

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

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

    26 votes

    We're glad you're here

    Please sign in to leave feedback

    Signed in as (Sign out)

    We’ll send you updates on this idea

    3 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
← 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