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.

How can we improve PI Connectors?

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  • Hot ideas
  • Top ideas
  • New ideas
  • My feedback
  1. Allow specifying UOM for new AF attributes created by UFL or OMF

    I'd like the ability to specify UOM for new attributes that I create. Adding categories as well would be even better!

    2 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 →
  2. Validate credentials before running connector

    Need a way to easily confirm that the credentials are correct before I try and run the connector.  Would like to see any errors surfaced via the web page so I can troubleshoot.

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

    We’ll send you updates on this idea

    0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  3. Relay -> Relay communication

    To accomplish a dataflow in a cross domain architecture including a DMZ, and the abbility to avoid the use of a Credential Manager it would be usefull to setup connection between two PI Connector Relays (DZM domain and PIDA domain) based on AMQPS.

    1 vote
    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 →
  4. 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.

    1 vote
    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 →
  5. PI Connector for Siemens SIMATIC PCS7 Alarm and Conditions backfilling support

    In case of an interruption, the PI Connector has the current capability of backfilling any tag data from the source OpenPCS 7 system.

    Condition data leading to PI Event Frame creation from the connector should also support similar backfilling capability to avoid data loss.

    1 vote
    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 →
  6. Native support for PI Data Archive collective

    "For Interfaces if we add a new member to the PI Collective, all other interfaces will automatically detect it, and start sending data.
    With PI Connector Relay 1.x, someone will have to remember to manually configure.

    1 vote
    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 →
  7. PI Connector for OPC UA Failed to populate Discovered Endpoints list

    When pressing the Discover Available Endpoints button under the following condition , it failed to populate the Discovered Endpoints list because of 501 Error:
    a. NAT configured between PI Connector for OPC UA and OPC UA Server networks b. OPC UA Server's Endpoint URL was specified with the IP address from OPC UA Server network.

    Request
    This error occurs when NAT is involved in the network configuration. PI Connector for OPC UA should take into consideration this scenario and work as UaExpert, which can handle it without any problem.

    1 vote
    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. Connector for Oasis Site

    Customer would like to be able to pull data from Oasis site (http://oasis.caiso.com). This would allow the customer to have the most current price information coming from CAISO

    1 vote
    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 →
  9. Wonderware Connector - History Recovery

    Wonderware Connector has limited historical data recovery capabilities. It can cover a few days back in time but has not been designed to perform both realtime values and configurable history recovery period as both processes are synchronous.
    An old date is configurable but it would delay real time values capture which is counterproductive with the nature of the connector.
    It is not a reproach; that's just what it is.
    That's we figured out when implementig and assessing connector with an excellent support from OSISOFT engineers.

    Our connector implementation project came with the need of nearly a year of historical data…

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Wonderware Historian  ·  Flag idea as inappropriate…  ·  Admin →
  10. UFL / Generic file & web based interfaces interoperable with EDS & OCS

    Connectivity to “universal devices”; used for general purpose connectivity to many industrial devices and systems; capabilities include accessing REST Web services and parsing generic MQTT based messages.

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

    1 vote
    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 →
  11. 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).

    1 vote
    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 →
  12. PI Connector for Siemens SIMATIC PCS7 relay support

    Allows customers to leverage the PI Connector relay for improved security, ease of deployment and maintenance when PI Connector for Siemens SIMATIC PCS7 is implemented in a process network with DMZ communication to the corporate network.

    1 vote
    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 →
  13. 1 vote
    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. PI Connector Relay - Add ability to retrieve cached OMF meta data like Types and Containers

    As an OMF application developer it will be very useful to have the ability to retrieve and have a look at the already created and cached OMF meta data like Types and Containers.

    1 vote
    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 →
  15. Support string data types for PI Connector for EtherNet/IP

    String data, such as serial numbers, are supported by the EtherNet/IP protocol and are often collected to help understand what was being made by a piece of equipment at any given time.

    1 vote
    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 →
  16. IEC61850 encryption

    Implement TLS encryption between the IEC61850 Connector and the target IED(s) as per TS 62351.

    1 vote
    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 →
  17. Cygnet - Check for prerequisites during the installation process instead of in the logs on startup

    Currently, if some Cygnet prerequisites are missing, the following error is logged:
    Although the errors are clear, this verification step should also occur during the initial installation process.

    Please review the "Installation requirements for PI Connector for CygNet" in the User Guide.
    And subsections "Install the ODBC drivers" and "Verify connectivity with ARS".

    1 vote
    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 support to the PI Connector Relay to support OMF Delete and Update actions

    The OMF specification outlines that delete and update messages are included within the specification, but those capabilities are not yet included in the PI Connector Relay. It'd be great to be able to delete or update previously created AF Elements or Types--for example, in the case where an edge device is upgraded to include a new sensor feed, which now needs to be appended to the existing AF Element Template created for that edge device.

    1 vote
    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 →
  19. Provide documentation and examples of how to interact with the PI Data Collection Manager API.

    - Enable Programmatic configuration for OMF applications to automate onboarding process
    - Swagger specification

    1 vote
    Sign in Sign in with OSIsoft
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Help / Documentation / Videos  ·  Flag idea as inappropriate…  ·  Admin →
  20. PI Connector for FANUC Focus should give a warning to users when they change the machine IP address for an existing data source.

    In the PI Connector for FANUC Focus, each data source has the IP address of the related machine specified. The "Device ID" is also part of the configuraiton. If a Device ID is not specified, the IP address is used as part of the Device ID and ends up becoming part of the AF hierarchy as well as the PI point names.

    If a user goes to change the IP address for an existing data source, and the default Device ID is being used, they will inadvertently create a second set of PI points (Duplicates, orphaning the original PI points…

    1 vote
    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 →

    Any configuration changes made to the device id or IP address after initial configuration, will be met by a warning message which the user will have to accept before proceeding with the changes.

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