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 dynamic parameters in URL

    Often third party web API needs input parameters so static URL is not enough.
    Sometimes parameters are simple, e.g. current data, or can be derived from PI tags; these could be set with placeholder in configuration.

    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

    0 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  2. Try catch management

    Actually, if an error occurs during data processing, datasource stops immediately execution and skips the remaining rows.
    Try catch or similar could increase stability of data acquisition.

    8 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 →
  3. Configure target PI/AF/DB at datasource level

    Actually the UFL Connector sends data to all of the listed PI Data Archives and AF Servers in the server list configured in administration page, so it's not possible to send different data to different PI DA or AF databases with a single UFL Connector.
    It would be better to bring these configuration at datasource level.

    8 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. Re-Order Data Source List

    It would be helpful to be able to re-order (e.g. sort) data sources being used by the PI Connector for UFL.

    As the number of data sources grow it can be difficult to find a particular data source, especially if those data sources have similar names (changing one or two characters)

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

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

    135 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

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

    17 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 →
  8. Allow users to rename PI Connector for UFL point source

    PI Connector for UFL allows for configuring point prefix, but does not allow for modifying point source. Some users prefer browsing tags by point source, and may want separate point sources for different UFL connectors.

    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  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  9. Update PI Interface for Citect Supported Operating System to Windows Server 2019

    The latest supported operating system for PI Interface for Citect is Windows Server 2016, with a requirement to upgrade our machines to Windows Server 2019, this interface is the only thing holding us back, the ICU is supported although the interface is unsupported.

    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  ·  Other specific PI Connector  ·  Flag idea as inappropriate…  ·  Admin →
  10. Allow PI Connector for Cygnet to support a mix of VHS and CVS when Automatic UDC Recognition is enabled

    With Automatic UDC recognition enabled, PI Connector for Cygnet defaults to placing all UDC's in the CVS column by default, or in the VHS column if "Prefer VHS for Automatic UDC recognition" is checked.

    This behavior should be a preference, not an all-or-nothing selection - users would like Automatic UDC recognition to default to CVS or VHS, but also have the option to specify UDCs that do not follow the default behavior.

    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  ·  CygNet  ·  Flag idea as inappropriate…  ·  Admin →
  11. The MQTT Connector should be able to connect to MQTT Brokers that requires Client SSL Certificate.

    Currently the MQTT Connector only supports username/password authentication. This is great for local brokers/servers, but very unpractical when connecting to cloud brokers like AWS IoT Core. Adding support for Client SSL authentication will make it significantly more useful in a cloud based infrastructure.

    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 →
  12. 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 →
  13. 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).

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

    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

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

    30 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 →
  18. 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 →
  19. 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.

    28 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 →
  20. 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 →
← 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