Cognite InField: Timeseries Trending

Related products: InField

On behalf of InField super users at Celanese:

When trending timeseries using InField, all available time series for a specific asset are loaded in at once by default. Depending on how many timeseries are available for the specified asset, this can really bog down InField as it is trying to process that information. If the system doesn’t lock up at that point, the user then has to go and deselect all of the tags that they do not want to see. Can this be updated so that, by default, no tags are loaded in and the user is instead able to select the tags that they want to see?

@Kristoffer Knudsen 

Hi @crgomez13 - have you tried to use the “trends” configuration in fusion.cognite.com for InField? See the end of the page on the “trends” section here: https://docs.cognite.com/cdf/configure/infield/infield_config_timeseries

Hi @crgomez13 have you had a chance to explore @Kristoffer Knudsen’s suggestion? If you have any further questions with it, please ask. We’re here to help:)

@Kristoffer Knudsen wanted to follow up on this item. The configuration did seem to work for most units but I am curious if there is a better way to approach this similar to the original ask above? The reason I ask is for assets that may have a large amount of “.mde” tags contextualized as well. It would be a cleaner experience to allow the users to select the tags they would like to see. I found a temporary fix by applying the “.mde$” configuration in both the “default visible trends”  and “Regex pattern to filter out unwanted matches of default visible trends” dialogue boxes. This allowed me to view the trend page without any default timeseries being displayed. However, an unexpected side effect of this was when viewing the asset overview page, the “View trends” button was greyed out. Because of this I was required to revert back to the original configuration.

Hi @crgomez13 - thanks for coming back to us on this one! 

Yes, I agree - there are improvements to be made around customisation here. In this development cycle we are working on a new configuration for InField 2.0, but the feature/customisation part of this will come in a later cycle. I’ll ensure that we bring your feedback into this work. 

Br,

Kristoffer  

Terms & ConditionsCookie Settings