Cognite InField: Measurement Units

Related products: InField

Mismatch of measurement units, InField only does readings in inches, but some items are in feet. The Operator has to calculate on their phone before entering into InField

I recommend a combination of ft and inches

New→Gathering Interest
Gathering Interest→Planned for development

@Anita Hæhre , @Kristoffer Knudsen  Is there an estimated release date for this functionality. Please note that this is a key feature for adoption of InField, in some of our operating units. Thank you!

Hi @rsiddha, thanks! 

Support for multiple measurement readings (e.g. feet & inches) are currently planned for development during Q2. When visiting the AAS unit back in October we experienced that the operators didn’t really have a large issue with the current functionality, but worked around it, which is why we chose not to prioritise it at the time. 

Which units are currently struggling with adoption due to the lack of multiple unit support? thanks! 

Hi @Kristoffer Knudsen 

VAM unit considers this as an adoption blocker. I do know questions arose from at least one other unit as well last year (Utilities I think). Can we add this for Infield 2.0 release?

👍 thanks for clarifying. We have it on the backlog :) 

Hi @Kristoffer Knudsen and @Anita Hæhre what is the updated timeline for this feature?

Hi @Marcela Young - thanks for your feedback. 

In the January release of Cognite Data Fusion, Time Series now support “Units”; https://developer.cognite.com/dev/concepts/resource_types/units/

This allows us to solve the first part of this challenge, which is to have a Unit library available. The next step would be to have a way of doing an automated conversion, e.g. going from feet, inches. We are planning to do this, but not short term due to other priorities. 

How do you see the current need from your side here? I don’t think this is still an adoption blocker as mentioned above? 

Thanks! 

Terms & ConditionsCookie Settings