Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
Thanks @Marcela Young, understood!
Thanks @crgomez13, this is very aligned with the flexibility we want to enable with scheduling of templates!
Hi @crgomez13 - sorry for the late reply on this one. Does the checklist only contain the one measurement reading you are taking multiple times a day/shift? or is the same reading part of different checklists you do throughout a day/shift? Trying to understand if an operator only goes out to take that one specific reading or if it also contains other tasks that vary throughout the day/shift. (cc @Nicklas Lind) Br,Kristoffer
Hi @crgomez13 - this makes sense! Will bring it back to the team to discuss how we can solve the need. (cc @Nicklas Lind)Br,Kristoffer
Thanks @rsiddha!We are well aware of this limitation and you are correct in the reason for why it is not possible today. We are looking into how we can enable a seamless experience if internet connection is lost. Br,Kristoffer
Hi @crgomez13, thanks for your feedback! Making it easier to create more table/matrix based forms of rounds in InField is something we want to enable, will bring your insights back to the team (cc @Nicklas Lind) - thanks!
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 @rsiddha! After a checklist that has been created using “Templates” is “archived” we will “delete” the checklist after a 4 week period. Currently this 4 week period is not configurable, but it makes sense to make this configurable in the future. One important note on this. When a checklist is “deleted” in InField it does not mean that it is permanently deleted, we simply want to make the list of checklist less crowded for the user and only display what is still “active”. You can at all times go to the “Weekly summary” page and find all “deleted” checklists, just choose the week and discipline you are interested in. Br,Kristoffer
👍 thanks for clarifying. We have it on the backlog :)
Hi @Culbreth Dylan Celanese !Happy to share that in the latest release of InField support for inputing negative values is available. When using your Tablet or Phone out in the field you should see the standard apple/android keyboard pop-up when entering a “measurement reading”. Navigate to where you typically find the “-” symbol and start typing, Hope this solves your needs at VAM. Br,Kristoffer
Hi @rsiddha - thanks for your feedback. This makes a lot of sense, will bring it back to the team. Thanks!
Hi @Crystal Connor Richards ! Cognite InField would work fine on a screen of that size. However, InField determines if the device is a Desktop or Handheld device based on the device width in pixels. If InField determines that it is a Desktop device, touch features won’t work, so you would have to demo it using a mouse and keyboard. Do we know what the resolution of the device is? That would have an impact on the device width in pixels and therefore if InField would categorise it as a desktop or handheld device 😀
@rsiddha - this is on our list and the ambition is to have a solution for it within that timeline. Thanks!
Thanks @rsiddha - will bring this feedback into our “internet connection” discovery work.
Hi @rsiddha - thanks for reaching out. For Cognite InField this is currently not possible. I’m certain that it exists scenarios where it would make sense for InField to trigger an email, but unsure if this is one of those scenarios. But happy to discuss this more. For CDF in general we have multiple places where sending emails are triggered as part of a workflow, e.g. on extractors and AIR. However, I do not believe the scenario you are describing here is currently possible out-of-the-box.
Hi @crgomez13 - thanks for forwarding this feedback. The need to ensure standardisation, e.g on units, makes a lot of sense.
Hi @crgomez13 - thanks for the feedback. We’ve seen the similar need for these “if statements” before, and are thinking around a concept for it. Do you know which Unit that at Clear Lake that has brought this up? Thanks! (cc @Nicklas Lind)
Hi @crgomez13 - thanks for the feedback. Today, this logic is controlled by how the asset hierarchy is modelled in Cognite Data Fusion, e.g. every asset below the root node “AAS” can be “linked”. I agree that it makes sense to de-couple this logic, such that you are able to maintain an asset that is not aligned with the unit. We’ll see what we can do here.
Hi @crgomez13 - thanks for the feedback. We agree, this is something we’ve observed both at Celanese and other customers. We are planning to incorporate functionality for this in a future release (cc @Nicklas Lind).
Hi @crgomez13 - thanks for the feedback. This is something we’ve seen the need for across users, especially when working with (as you point out) large templates. Will bring it back to the team.
Yes, that could make sense 👍 Currently the logic is built around the concept that each real-life facility/platform is modelled as the root asset, and then we search all assets beneath that root. This logic made sense in O&G, as each platform is “decoupled” from the rest (easy to say platform A = root A), but probably something we need to re-evaluate now that we see several units (roots) within one facility that have dependencies on each other.
Hi @ibrahim.alsyed! I believe the plan that was sent over by Marius prior to Christmas still stand, that we want to have write-back of Notifications to SAP triggered from InField during H1. In accordance to that plan a Celanese specific execution plan will be ready during February.
Hi @asgottlieb - following up on this one. After this input we have released a way of navigating the asset hierarchy through the “search field”, the reason for not implementing a full hierarchy was to not ruin the mobile experience. Have you tested the “search” experience and does it meet some of your needs for a hierarchy?
Hi @DGrooms - as @davidhwu mentioned above, we are happy to say that this functionality was released today (see the release notes here; https://docs.cognite.com/infield/changelog/). You now have the possibility to either mark the remaining tasks in the whole Checklist or a Section with the same state (ok, not ok, Not applicable, etc.). Remember that to put either one item or multiple items as “Not applicable” you need to have this state applied in the setting page for the particular Template (see the image below). If you don’t have access to editing Templates, reach out to one of your admins. We hope this makes things easier for you and please reach out with any comments/feedback!
Hi @ibrahim.alsyed ! First part of this feature was part of the previous release, please see an update here: When it comes to scheduling when a Checklist or Sections should be “N/A” based on e.g. planned outages, this is something will look into at a later stage.
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.