Skip to Main Content
Data services feedback portal

Welcome to our feedback site!


We created this site to hear your enhancement ideas, suggestions and feedback about CONNECT products and services. All of the feedback you share here is monitored and reviewed by the CONNECT 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 CONNECT data services. For links to our other feedback portals, please see RESOURCES below.

Status No status
Categories Asset Rules
Created by Guest
Created on Aug 18, 2022

Improve Asset Rule Flexibility - Accommodate Stream with Segments with two purposes / overlapping token strings

The ability to derive multiple tokens from the same overlapping strings. Requirement: From the example stream name “PIDAHou_Flow.PV”, we need to be able to derive the following asset ID and metadata information. Asset ID: ”PIDAHou” Asset property “Measurement”: “Flow.PV” Value of Asset metadata “Location” : “Houston” (mapped val from Hou) Value of Asset Metadata “Product” : “PI Data Archive” Solution Option 1: Support: Overlapping tokenization (Note that Token1, Token3 and Token4 has overlapping string parts of the stream name). Token1: string before the first “_”, and use this token to express Asset ID : {Token1} Token2: string after the first “_”, and use this token for Measurement property Token3: Three letter string prior to the first “_” with the mappings {“HOU”:”HOUSTON”, “DAL”:”Dallas”}. use this token to assign to the metadata Location Token4: Two letter string starting at 3rd position with the mappings {“DA” : ”Data Archive”, “AF” : “Asset Framework”}. Use this token to assign the metadata Product Use the values of these tokens to extract required info as follows Asset ID={Token1} Measurement = {Token2} Location={Token3} Product={Token2} Solution Option2: Use both raw unmapped token as well as mapped value of a token Token1: First Two letter as literals Token2: Two letter string starting at 3rd position with the mappings {“DA” : ”Data Archive”, “AF” : “Asset Framework”} Token3: Three letter string prior to the first “_” with the mappings {“HOU”:”HOUSTON”, “DAL”:”Dallas”}. Token4: string after the first “_”, and use this token for Measurement property Use the values of these tokens to extract required info as follows Asset ID={Token1}{Raw unmapped value of Token2}{Raw unmapped value of Token3} Measurement = {Token4} Location={Token3} Product={Token2}
  • Attach files