Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
Requesting an option in scheduling field for planned outages where all rounds and readings would default to N/A during a given time frame with a singular comment box for justification. For ISO 9001 compliance, this would allow for the given time frame to have a singular comment for all readings which would greatly decrease the need for daily comments on all readings as N/A with a “planned outage” comment for compliance. This option would also need to allow for individual readings to be overridden and readings to be collected if a partial outage is observed. Benefit to users would be ease of ISO 9001 compliance and removal of redundant documentation to support compliance purposes.
As an end user, it would be beneficial to be able to visualize uploaded word documents with isolation plans on a 3D model. Isolation plans identify what valves need to be closed and locked and are not represented with distances on the word document for spacing constraints. The drawings show valves close to a pump, for example, when they may be in a pipe rack some distance away. Being able to visualize these on the 3D model will assist with training, prevent crossing lines when tracing them in the pipe rack and prevent potential process safety incidents.
As a data validation end user, I need the ability to extract the data out of CDF and compare it to the source data platform. Currently in CDF, there is no option to “select all” and all all events have to be manually extracted for download out of CDF. Additionally, when the metadata is downloaded, it comes through as a .json file which is not easily comparable to other system extracts. I need the file to be extracted from CDF in a user friendly format like csv to be compared to source data for easy data integrity validation.
Requesting additional enhancement to come with the subheader creation in infield where the checklist will be able to open with all tasks collapsed and to be toggled collapsed/un-collapsed by subheader. This enhancement would allow for checklists to be more easily viewed and shared among operators.
Need functionality to auto deploy checklist templates based on calendar.Currently checklists are available in templates or the link has to be copy/pasted and sent to people each week. As a manager, when staff comes on shift, there are different checklist tasks that need to be completed based on the day/week/month that it is. For example, there are shiftly readings that need to be taken (day/night) that need to be assigned to the team so they are all available when the team comes in. There are other checklist/tasks that need to be completed quarterly or the first weekend of the month.As a manager, I need the functionality to set up reoccurrence of the checklists to be opened for the user when they come on the shift so they have a list of all actions that need to be completed during that shift. With rotating shifts, we do not have the bandwidth to send reminders that a new checklist needs to be completed. In our current world, papers are printed and batched so each shift has a duty roste
As an end user, it is beneficial to be able to clear up the “noise” in CDF when searching for data. It would be beneficial to have filtering capable of selecting more than one item of a sub-type for better visibility.
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 curren
Already have an account? Login
Enter your username or 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.