Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
Hey @Benjamin A Onweni ! just a small update on this one. The new version of InField will come with a completely new log-in flow, where the log-in/log-out issues you’ve experienced in the path shouldn’t be an issue.
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.
Gathering Interest→Planned for development
Hi @Crystal Connor Richards - just to give an update on this one. In InField v2 this will be resolved.
Hi @Benjamin A Onweni ! Just to update you on this one, in the new version of InField (v2) changes will be reflected the first time you open the Checklist again (don’t need to wait a week). Br,Kristoffer
New→Gathering Interest
Hi @crgomez13 - thanks for the feedback! I agree, green doesn’t make sense if that status is “N/A”. But maybe something like grey would make more sense than yellow? Nevertheless, I’ll bring this back to the team. Br,Kristoffer
Hi @crgomez13 ! Just to update on this feature request. This functionality will be available to you out-of-the-box with InField v2 once you are migrated over. When building Template items/task you can utilise a component called “custom labels”, where you essentially have the possible to define any type of custom buttons you might need (e.g. yes, no). Br, Kristoffer
Hey @Crystal Connor Richards - just an update on this one. All of these points (1, 2, 3) is solved out-of-the-box with InField v2. Br,Kristoffer
Planned for development→Implemented
Hi @ibrahim.alsyed ! For transparency I’ll just copy-paste what we discussed on email here as well. Interested in hearing the thoughts from the rest of the community on this topic :) The current Templates functionality in InField is largely built towards process operators in the context of doing operator/routine rounds type of work. As part of InField 2.0 we are, as you know, re-designing Templates to enable more flexibility in the tasks you can create and how you schedule them. When creating tasks, one key new component is the ability to create "custom labels". In short, this means that you are not restricted to the simple "ok, not ok", but can define a task as for example "yes, no, etc.". However, you can also create tasks that might be more relevant for e.g. an inspection checklist like "compliant, non-compliant, not available, not applicable". In short, I believe we are already developing functionality that makes it easier to create other types of Templates/Checklists than those
Yes, talked with @rmaidla and as I understand they are also after that. I think right now, the view above should at least make it easier to keep the limits/setpoint up to date although it’s not automatically updated.Having it automatically updated based on some calculations makes sense to do as well, but I think before we can enable something like that we have to enable a way to keep track of the historic limits, as pointed out by @Brendan Buckbee in the attached hub post. I would assume that when you are analysing the data, and the limit keeps changing, it is important to always know what the limit was in the timeframe where you are analysing the data?
Hi @rmaidla!Thnx for the input. We are re-design the way of exploring data in InField, and one key concept of that is the ability to always explore data in the context of what you are working with. This means that you will have the possibility to investigate a datapoint (such as the calculated one you mention above) while setting the setpoint in the Template/Checklist without being taken away from the context. So hopefully as a more “one-stop-shop”. I’ve attached an example below of how this could look like when working with a Checklist, with a numerical reading task, on Desktop. If you are building out a Template and setting “min/max” values you will also be able to have that similar exploration context in the same views as the Template. How does this resonate with the need you describe above? Br,Kristoffer
Hi @Brendan Buckbee! Thnx for the feedback. On 1) that makes a lot of sense. Will bring it back to the team to see how we can work with “historic limits”. On 2) I think it would be valuable to sit down and show you how we are developing the new version of these “custom labels”, and how we envision to trend/work with the data after it’s captured in the field. I’ll send you a meeting proposal. I’d love to hear from the rest of the community on these topics as well!Br,Kristoffer
Thanks @Niklas Laufer ! From the video I can’t see that you are doing anything wrong. There might be a bug here, could you please log a ticket at support@cognite.com with the video attached? Br,Kristoffer
Hi @Niklas Laufer , thanks for reaching out! From your screenshot it doesn’t look like you are doing anything wrong, but could you potentially attach a screen-recording of exactly what happens after you click “confirm”? Br,Kristoffer
That is correct @rsiddha, this is the reason for this pop-up warning. Does that make sense @Marcela Young ? What is the main reason for why the AAS Learning Facilitator don’t want to see it?
Hi @ibrahim.alsyed, thanks for your feedback! Question on the different checklists for each status: are these actually completely different checklist? Or would you have one Template/Checklist with Equipment A, B, C, and if Equipment A is “out of service” the tasks relevant for that equipment would simply change to “N/A” or something?
Already have an account? Login
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.