Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
When completing an operator round in Cognite Infield, the status of the round should be able to preselect ok/not ok based on the values provided. Currently, the operations team needs to input the value from the reading and then manually select if that round reading is ok or not ok. The acceptable ranges are provided and listed in infield, but the current set up of the system is causing operations teams to interact with each individual reading twice: once to input the entry and a second time to classify the entry. This double entry is a barrier to adoption as it is requiring additional steps from the operations team. Additionally, due to the location of the radio button being at the top left of the title and not close to the text field for data entry creates an additional likelihood that the field will be missed. Furthermore, the lack of the ok/not ok will cause the reports to have to be manually verified by those who are utilizing them, to quickly validate operation status. This current solution does not provide much improvement over the current paper analysis of digital rounds.
Cognite InField: Data Analysis
InField
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Hi Kylie,
thanks for your input! Let me see if I understand you correctly. You have two points: one regarding the relative placement of the interaction elements, and one regarding setting a status automatically.
Regarding the placements of the value field and the radio button, I agree with you that their order should be swapped around. I’m making a task on that in our task management system.
As for the automatic setting of status depending on whether an entered value falls within or outside a predefined range, that makes sense, too. However, we have already done some insight work on this and there is a divide between users as to whether this is beneficial or a nuisance. I’ll make a note of your wish though, and we’ll have a look and see if there is something to be done.
We really appreciate your input, but as we have to prioritize a number of needs against each other, I’m unfortunately not able to communicate a release date for these improvements right now.
Thanks again, and don’t hesitate to let me know if you have any further suggestions for improvements!
This is very valuable insights – thank you so much for sharing!
I pretty much concur with Jonas above. To give a little context regarding the setting of the task state to ok/not ok depending on the input: This is something we’ve discussed throughout the design and implementation of the measurement reading feature. The challenge – based on our existing users’ needs – has been that for some tasks it would be detrimental to rely solely on the value of the input to determine whether a task status is “ok” or not. Therefore, we decided to include that one additional manual check to make sure that the status is set as intended by the user.
However, seeing this implementation if not ideal in your case, I think we might be able to escalate this within the team to find a solution.
Hello again,@Kylie R !
After discussing your post with the InField team and other stakeholders, we landed on changing the default behavior of the measurement readings input field to what you’re suggesting in your post.
Pending final testing, with the next release of InField, which you will be getting automatically, the value of the input of the measurement reading determines the task status. If the value is within range, the task is automatically set to “OK”. If the value is outside of range, the task is automatically set to “Not OK”. If no range is set in the template, the task is set to “OK” when any value is inputted. You can always “manually overwrite” this, of course, simply by tapping the radio button and selecting a different status.
Hopefully that takes care of the second part of the request as well, since you won’t have to manually select “OK” or “Not OK” on tasks with a measurement reading anymore – I can ping you again once the change is out, and you can let me know if this solves the issue.
Hopefully that helps!
Have a great day
Nicklas
Thanks for the update@Nicklas Lind
I know@Kylie R and the Celanese Acid South Unit will be very happy for the functionality to ensure adoption!
Will it end up in the April release, or the following?
Release should be around April 6, is that correct? Or will this end up in the release following on 4/20?
Pending a bit more internal testing today, the update will be sent to our QA testers later this week. If approved, the change will be part of a release on Wednesday next week
Thank you all for all of your help! This enhancement will greatly decrease user interaction to complete a task, enhance user experience and increase adoption!