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

    14 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 →
  2. DeltaV Smart Connector Update to OPC UA

    The newest release of DeltaV has the capabilities of enabling an OPC UA server that could be used to transmit realtime date from DeltaV to the PI database. Right now, the interface between the two systems uses OPC DA. With DeltaV's plan to migrate to only using OPC UA, Is there a roadmap to update the smart connector such that it uses OPC UA for realtime data transmission? This could allow the OPC UA connector to be placed on the PI data server directly since it is much easier to setup OPC UA connections across physically separate machines (as opposed…

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

    We’ll send you updates on this idea

    3 comments  ·  Flag idea as inappropriate…  ·  Admin →
  3. Enable or Disable single DataSource

    When a datasource is actually offline and we don't want the UFL connector to keep trying uploading or connecting to it and pollute the message log .

    The best option would be having the stop/start enable/disable and restart options for each datasource.

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

    We’ll send you updates on this idea

    1 comment  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →
  4. Create child Event Frames

    UFL connector can create child element using StoreElement function.
    it should be useful to extend functionality to event frames on function StoreEventFrame

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

    12 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. New function for Ethernet/IP (“scanner”)

    Add the function to able to act as (“scanner”).
    At this moment the connect can only act as an adapter, that means that It can't collect data from other device that also are connector is an adapter.
    https://www.odva.org/Technology-Standards/EtherNet-IP/Overview

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

    We’ll send you updates on this idea

    0 comments  ·  Ethernet/IP  ·  Flag idea as inappropriate…  ·  Admin →
  7. 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.

    11 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 →
  8. Merge Two Tags or Copy Tag Data to a New Point

    Sometimes, when dealing with APS, a new TAG is generated for an existing point. Data stops going to the old point. It would be nice if there was an easy way, within the gui (not manually dumping and importing) that we could take the values from one tag, and place it into the new tag.

    There are other times when we may want to copy all historical values from a tag, and place it into a new tag.

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

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

    11 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 →
  10. Windows Authentication to the Rest Endpoint should be supported with PI UFL Connector. Currently only Basic is supported

    I tried connecting to a REST endpoint using PI UFL Connector. However, it seems the Connector only supports Basic Authentication. The REST point only supports Windows Integrated Security. We can use Web Browser to read data from the REST endpoint. We get the following error in the connector log: HTTP status code: Unauthorized

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

    We’ll send you updates on this idea

    2 comments  ·  UFL  ·  Flag idea as inappropriate…  ·  Admin →

    Thank you for reaching out. We can extend the connector to support the NTLM authentication, which falls under Windows Authentication. Would it meet your needs?

  11. Create/Write to Child Attributes

    I would like to be able to write to Child attributes with the UFL connector using the StoreInElement function. Currently, it seems that the Connector cannot write to or create an attribute with a path like:

    ..\Element|ParentAttribute|ChildAttribute

    It ends up creating another Attribute at the level of the ParentAttribute with %18i inserted in the name where the second pipe would go. (i.e. the attribute is named ParentAttribute%18iChildAttribute)

    11 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 →
  12. PI Connectors buffering (Tau) - provide configuration options

    As a PI Administrator, I would like to be able to DISABLE or configure Tau buffering SO THAT after a network outage the flood of data doesnt overload my network switch and PI DA. My current use case doesn't require the data that may be lost during a network outage.

    I would like to be able to throttle the number of events that are sent ot the PI DA via Tau buffering so that the PI DA can ingest the data without building event queues.

    Specific connector: PI Connector for EtherNet IP which is used for high speed data collection.

    10 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 →
  13. Have option to enable exception on Connectors.

    There are use cases where data is sent over networks with latency (satellite link, for example) so being able to filter out noise at the connector is important.  This is also important when a connector sends data to a local PI Server in the field (low latency), but then PItoPI is used to send snapshot updates to a central PI Server over a high latency link.

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

    We’ll send you updates on this idea

    4 comments  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
  14. Rollback Option for System Connector

    We had an issue with the System Connector and had to reinstall every part of it, but then all tags in the destination system have been created again. The old tags have not been updated anymore. We think about an option to reverse every change the connector did on the destination system (delete AF Elements, Attributes, Event Frames, PI Tags) that have been created by the connector.

    We thought of a workflow like this:

    Delete the routing of the "not-correct-working" Connector via DCM
    Delete the Connector via DCM UI (and de-registering it from DCM and Relay in that step)
    Deleting…

    10 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 →
  15. Have PI System Connector support null system digital states

    Would like to have the connector support Null System digital states. Null system digital states can work locally on a PI Server. Would like the connector to support all the options found locally so that we could accurately sync systems.

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

    We’ll send you updates on this idea

    STARTED / IN DEVELOPMENT  ·  3 comments  ·  PI System Connector  ·  Flag idea as inappropriate…  ·  Admin →
  16. PI Connector for Modbus TCP

    Develop a PI Connector for Modbus TCP. 

    Connectivity to Modbus slave devices; used for general purpose connectivity to many legacy industrial devices.

    Interoperable with Edge Data Store (EDS) and OSIsoft Cloud Services (OCS).

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

    We’ll send you updates on this idea

    0 comments  ·  New PI Connector request  ·  Flag idea as inappropriate…  ·  Admin →
  17. Synchronize behavior between PI Connector for Cygnet and Cygnet enumeration value representation

    The values stored in the “Table Entry” column in Cygnet TRS should match the “State” column in the PI Server Digital states table. This way end users are not confused why the trends in PI do not match the trends in Cygnet.

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

    We’ll send you updates on this idea

    0 comments  ·  CygNet  ·  Flag idea as inappropriate…  ·  Admin →
  18. Add failover capability for the BACnet Connector.

    Failover similar to the UFO available for UNIint interfaces.  Warm failover would be sufficient, although I'm sure there are some who would like cold and hot as well.

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

    We’ll send you updates on this idea

    1 comment  ·  BACnet  ·  Flag idea as inappropriate…  ·  Admin →
  19. Support user-defined data types in the PI Connector for EtherNet/IP

    As an advanced user, I would like to be able to specify a user-defined data type for the array sent to the PI Connector for EtherNet/IP.  For example, if I have a 32-bit array composed of one INT and two SINTs, I would like to be able to configure the connector to parse this array correctly. Currently the data type specification of the array is limited to one data type (DINT, INT, FLOAT, or SINT).

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

    We’ll send you updates on this idea

    0 comments  ·  Ethernet/IP  ·  Flag idea as inappropriate…  ·  Admin →
  20. 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.

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