Skip to Main Content
AVEVA™ PI System™ Feedback Portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about AVEVA products and services. All of the feedback you share here is monitored and reviewed by the AVEVA product managers.

To start, take a look at the ideas in the list below and VOTE for your favorite ideas submitted by other users. POST your own idea if it hasn’t been suggested yet. Include COMMENTS and share relevant business case details that will help our product team get more information on the suggestion. Please note that your ideas and comments are visible to all other users.


This page is for feedback specifically for AVEVA PI System. For links to our other feedback portals, please see the tab RESOURCES below.

Status No status
Product PI Connectors
Created by Guest
Created on Aug 20, 2022

Allow filtering of source points

In the HabConnect Connector the only filtering of source composite ID's for inclusion into PI is through use of wildcards. As a user I want to filter not at the query level to sampler, rather filter out tags in the result set (preferably using regex) that are to be included to PI. The current mechanism can be tremendously wasteful in configuration time, tending towards error, and impact system resources. For example, using a record type, say DEVICE, you want only specific substations, you have to create multiple queries for each specific substation. If you need to monitor a dozen substations, you create a dozen substations. If you monitor them all, you have a simple query but create tens of thousands of tags that are unneeded, require system resources. This doesn't sound like a burden, but config files can become unruly, exceeding 2k lines, and multiple dozens of queries. The old interface only pulled what tags were created, so filtering could be done on tag creation. As the connector now wants to participate in the tag creation process, it needs to consider these use cases. The only alternative is to turn synchronization off, and at that point this makes the connector a like for like replacement of the interface.
  • Attach files
  • Guest
    Reply
    |
    Dec 18, 2024

    I would prefer to have another column indicator along with “regex” mentioned in the feature request.

    eg.,

    Key=*,PISTORE=true

    above step should extract all the points when PISTORE column is set to true.

    key=*KING*,PISTORE=1

    Above step should extract all points which contains “KING” and PISTORE=true.