InField Built-In Naming Convention

Thanks @Marcela Young ! 

Do you know if the “naming convention” referred to for example is identical to the naming convention (tags) in SAP? If that’s the case, one idea could be to incorporate a “drop-down” that the Template builder could choose from instead of having to remember the tag themselves. Or is the “naming convention” a separate document stored somewhere else?

(cc @Nicklas Lind ) 

@Kristoffer Knudsen - that’s an interesting idea - would be cool to directly call a tag from a drop down. But no, the idea I am talking about is Celanese to be able to create a standard synthetic tag naming convention that an admin enters in based on a standardized document, and the template creator doesn’t have to worry about using the convention, only enters the description and the tag gets populated within InField based on the pre-determined synthetic tag format.

@Marcela Young - understood, this is what we discussed in our session last week I believe. 

It makes sense to have functionality to ensure that synthetic tags are created in a standard way, to again make it easier to analyse the data afterwards. Need to do some more exploration to determine how we’ll solve it, but let’s spend some time on it in a deep-dive session early next year. 

Hey @Marcela Young ! small update on this one. 

We are not currently planning to have a “built-in naming convention” component in the InField UI in the near term future. However, in the new version of InField I think the overarching job you are trying to solve should be quite straightforward. 

You could create a simple function that takes the excel master as input and creates new Time Series in Cognite Data Fusion, writing to the same data set that InField is consuming for measurement readings. That means that all the synthetic tags would be in Cognite Data Fusion. 

As you’ve seen in the new version of Templates a builder can simply just search for the synthetic tag and add it to the task item. With this approach I believe it should be quite doable to do this in a safe and reliability way where you don’t need to flip back and forth between InField and the naming convention document.