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

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

    9 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 →
  3. Allow the UFL Connector to performa a scan Immediately after startup

    On startup, the Connector currently waits for the configured scan frequency time to pass before doing its first scan. There are cases where a low scan frequency (e.g. once per day) is required. This results in an unnecessary delay before the Connector starts collecting data. Please all ow the option to perform a scan immediately after the Connector finishes its internal startup routine.

    14 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 →
  4. 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…

    13 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 →
  5. Make the UFL Connector logic development/testing/debugging process less tedious

    Deploying a UFL Connector solution requires a LOT of edits of the INI file as part of the development/testing/debugging process. After each INI file change and file save, the required procedure is as follows:
    1. Click on the Data Source List link.
    2. Click on ‘See Configuration’.
    3. Click on the ‘Change’ button.
    4. Click on the ‘Browse…’ button.
    5. Double-click on the INI file.
    6. Scroll the page down until the ‘Save’ button is visible (I’m using a 1920 x 1080 monitor).
    7. Press the ‘Save’ button.
    8. Click on the ‘Overview’ link.
    9. Press the ‘Start connector’ button.

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

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

    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 →
  8. Add scan time offset option to UFL Connector

    Use case: The UFL Connector needs to read a huge data set from a REST Server which is updated once a day. The only way to control when the data fetch occurs is by starting the connector at the desired time. The Connector however currently waits for the configured scan frequency time to pass before doing its first scan after starting. Furthermore, the Connector/hosting server may be restarted throughout the day for various reasons (e.g. application of Windows patches) throwing the timing off and further adding another 24 hour delay.

    Scanning, processing and sending to PI the same data more…

    9 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 →
  9. PI Connector for MQTT

    Create a PI Connector that supports the MQTT messaging protocol

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

    We’ll send you updates on this idea

    25 comments  ·  New PI Connector request  ·  Flag idea as inappropriate…  ·  Admin →
  10. PI Connector for OPC UA Relay Support

    As a PI Admin relays allow for improved security of process-network-to-DMZ communication.  This will greatly aide in the PI Connector for OPC UA's deployment in production systems.

    38 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 →
  11. 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…

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

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  12. UFL Connector HTTP compression

    Large data sets need to be pulled from a REST server on the internet which supports HTTP compression. Since this feature is not supported by the UFL Connector, the data will need to be retrieved in an uncompressed format. For the current project, this means several Gigabytes daily.

    3 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 →
  13. Add ‘No Replace’ mode to UFL Connector

    Currently the only PI Data Archive ‘Store Mode’ options are ‘Insert’ and ‘Update’. I’m currently working on a project where a large quantity of data needs to be downloaded daily from the internet using the REST client node. To reduce chances of data loss (e.g. due to download failure), the Connector will be configured to retrieve the same data set several times throughout the day. The best option at the moment is the “Update” mode. This however will place unnecessary load on the PI Data Server as large quantity of archive records are re-written with the same data throughout the…

    3 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 →
  14. Allow PItoPI APS connector to sync "Point Type" changes

    Currently (as of PI to PI Interface AutoPointSync Connector Version 1.5.0.7), it's not possible to sync changes to "Point type". (See pg 5 of user manual).

    Please make this possible in a future release.

    2 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 →
  15. Selectively send source data to PI based on network connectivity

    Example:
    - If on network A (which could be satellite or 3G) send Tags 1-10 and buffer Tags 11-50.
    - If on network B (Wifi, wired), flush buffer and send all Tags 1-50.

    Requested by OSIsoft Transportation Team, but very beneficial for all remote mobile asset tracking.

    2 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 →
  16. Selectively send source data to PI based on triggering conditions

    Example 1: If Circuit Breaker trips, begin sending high frequency load, voltage data, etc. Under normal operations do not send this data.
    (condition must allow for definition of a moving window, i.e. Trip occurs, data just before the trip must be sent as well as data after the trip)
    Example 2: Continually collect 10 engine variables. If an engine DTC (Diagnostic Trouble Code) triggers, collect additional set of 5 variables for the time the DTC code is active.

    Requested by OSIsoft Transportation Team, but very beneficial for all remote mobile asset tracking.

    2 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 →
  17. 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 →
  18. 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 →
  19. 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 →
  20. PI Connector Relay support write modes

    While writing data to PI through the connector relay there seems to be no option to control the write mode . E.g."[-109] Value at This Time Already Exists" is shown in the logs if the archive already contains an event with the same timestamp. The default update option can be "Replace" instead of NoReplace. Other write options can be made configurable.

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

    We’ll send you updates on this idea

    1 comment  ·  General  ·  Flag idea as inappropriate…  ·  Admin →
← Previous 1 3 4 5 8 9
  • 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