Suggest features, upvote favorites, and use the user story format: > As a [role], I want to [action], so that [benefit]. Help us build what you need - post your idea now!
What you should know submitting product ideas to our product team
Share your product ideas with the community and our product team
For line items in Infield, Operations has requested to be able to see what the most recent previous readings for it were to determine if reading is going up or down at a critical rate. Maybe a button on the line item that will quick trend the line items input data. Or just a list of the last inputs. Either way, we need a quick way to get history on these readings.
This is Dilesha from the Cognite Support team. Thanks for reaching out to us. Could you please give us more context on this request with a screen recording? That would help us to understand your request clearly.No labeling on the 3D visualization, makes it difficult to identify the equipment.Login to Fusion Navigate to "Integrate" and then to "Setup 3D content" Select the 3D file that you need to contextualize Click on the contextualize button on the right-hand side(refer to the screenshot) Then, from the sidebar, search for the relevant asset, then click the add button. Select the relevant node and click the Create annotation button.
Current Observations:When joining multiple Tables (in Cognite Raw) the Transformation (query) is taking a very long time Cognite is advising that Cognite Raw is a “Key-Value” store that is not optimized for running queries with multiple joins And that, currently, it is not possible to index or partition data in Cognite Raw to support efficient querying of data Given these limitations: Cognite Raw is not an ideal solution to store unfiltered data from source systems, in its original state Cognite Raw therefore should not be considered as equivalent to a Data or Delta Lake “Raw Zone” or “Bronze Layer” Other issues:It is not easy to debug or identify error conditions for long running transformation queries e.g., a long running query (with multiple joins, with say million records in few tables) can fail after ~10 hours if there are invalid node references all this after reading millions of records – only to fail with an error message that a node reference is invalid or that there is a duplicate key Joining on a subset of data (using inner queries) – to limit the number of records processed – still results in full table scan i.e., long running transformation Workaround - Recommendations:Execute long running joins (transformation queries) on source side (say, SAP) – Not always possible Consider piecemeal data ingestion and storage, e.g., by Site Code .. to store data in multiple tables (one for each site), instead of storing data for all sites in one table Using an intermediate data storage and processing layer (between Data Source and Cognite Raw) e.g., Snowflake, Databricks or any other platform It is really not ideal for us to consider other data lakes and solutions to mitigate these constraints.
Currently, there's no native way to search for a specific template on InField, making usability difficult cause users needs to scroll down until they find the desired template to edit. They can use Ctrl+F, a browser function to search for an element on the page and they'll be able to find the template, but this is not the best way to search because the function looks for everything with the corresponding text typed.Some Sites has more than 100 Templates, making it difficult to search for an specific template.
As an operator, I want to filter the tasks on a specific checklist, so it would be easier to find specific tasks in large checklists. This is a suggestion from Celanese users: being able to search for specific tasks. This will be useful specially for large checklists, that the operator has to go through the unit taking readings. Not always they do these readings in a specific path, they walk around randomly and fill the tasks as they go. Finding the tasks is somehow difficult in those situations, they have to keep scrolling and looking for the reading they are taking at the moment.
We had an occurrence where deploying a CDF Function to Cognite failed to deploy subsequently to Azure. Our CI/CD Pipeline is not quite set up for re-runnability, so it required changing the code for us to trigger a re-deployment. Considering the function.status method in the cognite SDK, it seems to reason that deployments could be monitored by the Cognite Back End for Success, and then retried up to maybe 3 times if failed. There were no logs provided to indicate why the deployment failed, in fact it looked like a bug in the error reporting as it had a newline character after what indicated a status message, but no status as to what happened.
How do we upload the “Person” data type meta data? Understood that the Person type contains many information, will be great that the extractor allows to configure to extract one of the property (e.g. display name, email, etc) as the meta data. The current extractor only uses the internal name of the column instead of the display name. It will be great that the file extractor allows the user to decide to use internal name or display name for extraction.
When a user makes changes to an Industrial Canvas, it says who and when, but not what was changed.Knowing what was changed would be helpful.
We realized that Cognite Infield for Maintenance Execution requires the ability to write back to close out operations checklist and update SAP, including closing or changing work order status. Please make this a priority.
Request to have before and after message & photos to be put side by side in horizontal. Need to compare before and after corrective maintenance.
On the Template tasks creation, it’s not possible to visualize how the checklist will be from an execution perspective. To have that, the user needs to set the Template as ready and create the checklist, changing the screen and forcing the user to back and forward using the application.With the possibility to preview the checklist, the user will be able to see and adapt the Tasks during the creation itself, checking if the tasks execution flow makes sense and is aligned with the the best approaches.
Request able to paste and display images in InField by the person that create the draft form. Below the images can enter the job descriptions/steps. Users need to view the equipment parts (image) so it is easier to follow the job step instructions & signature (image)for the form revision as audit purpose. Sample:
Request update and delete feature for infield form. Operators may enter the data wrongly and need to edit.
Message entry with enter new line will all appear as 1 line text when display as checklist. Entry of new line is missing.Request the display to be same as draft message entered.
Submitted on behalf of Raj Rathod, a senior principal reliability engineer. (There are also many use cases at the site that relate to safety checklists that would benefit from this product idea):As an InField template creator and user, I would like to be able to pull from a generic template that I can then link to any asset. As an example, I perform a visual inspection of many pieces of equipment across the site. I don’t want to have to create unique templates with the same 19 questions and have to tailor each of the line items to the asset. Instead, it would be convenient to have a generic template of those 19 questions that I can then assign the entire checklist to a specific asset rather than going down to the task level. In addition to this, it would be nice if the template or checklist could read the asset’s QR code and automatically pull up the basic asset information so that I can focus on the 19 questions for inspection purposes. This use case can also be used for safety checklists that have the same questions or fields across the site, regardless of the unit. A unit could pull up the generic template from a Site-wide “asset”, and then specify which unit and area within the unit the checklist can be tagged to.
Currently we can’t aggregate data from views by nested types.For example, in the query below, we cannot aggregate fields by grouping them under the name of B and count the descriptions in view A, as they are nested within view B.type A { refB: B description: string}type B { name: string}Additionally, it would be beneficial if filtering by non-primitive types and nested fields were feasible.For clarity, by primitive types, I am referring to basic fields like strings and numbers.
I’m looking at the list of filtering possibilities on time series, and notice that the unit V for volts is listed as v. For volts, we’ll manage, but this could be more critical for megawatts (MW) versus milliwatts (mW). I think the casing for units should not be altered in the filter list:
As a template creator, I would like the ability to embed an image within a checklist item to help the checklist user with tasks. For example, the Maintenance Manager at Celanese requested this because on their pump bearing sheets, they have images to help technicians identify what they’re seeing in the field prior to performing the rest of the steps on their sheet. I can see many other use cases for this for other template creators - for example, process learning facilitators could use this to help make sure that the process experts or perhaps contractors during a turnaround, are looking at the right piece of equipment when performing a task.The ability to add images as part of the checklist item would help enhance the user’s experience, potentially eliminate human error and avoid safety hazards.
hello everyone:Can the data models be displayed graphically (see image) in industrial tools? I see this way of showing assets as powerful.
Hi Team,We had recently deployed both InField and Maintain for an internal slb team that is showcasing these apps to other customers.The issue that is being faced is that the work orders/activities being generated and planned in Maintain must be executed via tasks under Checklists in InField - this is the complete lifecycle of a work order/activity that is being expected.As mentioned by @Omar Khalil and @STEWART WALLACE in Cognite Hub, we are able to turn a work order in InField space to a Checklist task. But the customer is interested in using Maintain and InField together - an app which creates and plans tasks (i.e. Maintain) to plan and execute them (in InField).We found below issues while troubleshooting:Currently, InField and Maintain use different instance space - For InField, this space is created via the Cognite toolkit whereas for Maintain we use APM_SourceData. Also, since we have two separate configurations for these apps in the APM_Config data model, this is not being achieved. Question is: How do we ensure cohesion between these two apps to achieve the above? Currently it seems the apps are in silos. Steps followed: a. Open Maintain with InField’s configuration and create a new activity. b. It is expected that this work order is now visible in InField We were unable to create an activity from UI in Maintain’s current version - seems a bug in the current build We found that start date is not a mandatory field in Maintain Activity creation - Start date should be mandatory as InField’s work order filters work orders in the Overview section. While troubleshooting we added this one manually in the instance created in Activity view We were finally able to see the work order created in Maintain (with InField’s config selected) in InField when we updated source property of the Activity instance from APP to SAP - Seems InField only shows work orders that are SAP or not APP. Another bug while performing this flow in Maintain was that the test plan was selecting the entire Activity even though it was not selected. Ideally, only the activity selected should be associated to a plan. If nothing is selected, it should not allow you to proceed.@Aditya Kotiyal @kelvin @Kristoffer Knudsen @STEWART WALLACE
As in any industry, we have a lot of time series which correspond to Process Values and Set Points. I set out to do a seemingly simple task. Calculate a new time series that was 1 when the PV was +-10% of the SP and 0 otherwise. The first issue that I faced is that we can’t do logic calculation with Snthetic TS expressions but I won’t go into detail about that since I already made a post about it before. The second issue was unexpected. The Set Point temperature of an oven or other industrial material is seldom modified. For good quality, consistent set points are important. Thus, there are far fewer points in a Set-Point time series than in a Process-Value time series. I was trying to calculate this time series for 11h00 : 11h05. I had a set point set to 180 DEG_C at 09h00. My process values were in the hundreds, about one every 5 seconds (or whenver the temperature changed beyond a 0.1 DEG_C threshold). With data like this, if I try calculating the expression “PV, SP*0.9, SP*1.1” between 10h00 and 11h00, it will result in NAs for the SP columns! This is because the last known value of the SP is at 09h00 and there are no known SP points between 11h00 and 11h:05. My workaround was to retrieve_latest for the PV and use the time stamp to write to a NEW time series with the default time_series.data.retrieve endpoint, all values within 11h00 and 11h:05 and include_outside_points in that write, and then also forward fill it so that I had SP points in between 11h00 and 11h05. In a prior version of my program, I deleted the new time series at the end of the program but CDF started to give me Timeout errors at the delete (Not 429, just time out). I assume I hit some kind of API limit. We deal with hundreds of such pairs of Set Points and Process Values. I feel that there should be a metadata field in a time series that allows it to be filled-down. That is to say, an indicator that if the last point is at 9h00 and I ask for data at 11h00, CDF can safely assume that no new points indicate no change in value, up to the datetime.now().
Oxy’s current workflow involves an automated Power App that based on the answer to a question, will pop the following question. This would be a very valuable feature in InField, avoiding the necessity for the inspector to answer multiple questions and only focus on the relevant ones based on his answers.
Have a smart link between Canvas and Infield, so a Checklist can be started directly from Canvas and added as an element of the Canvas, once the checklist is done, the summary should be available to be downloaded as PDF from Canvas.
Hi Team,User not able to create annotations on 2D or 3d n CDF and InField application to communicate users.Click on Data Explorer tab Click on the Assets tab at the top to select the assets resource type. in the assets tab, search for the asset (By sort field or by SAP equipment number). Switch to list view on the asset search results. on the search results, click on "Select column" button at the top right-hand side of the search results panel. Add 3D Availability column to the view of assets. The asset searched for should be the first one on the search results and should show label "Exact Match". Click on the link for that asset under 3D Availability. Verify the asset in 3D view for point cloud and 360 images. users want to annotate something to inform a colleague.Expected Results: - User desires to make annotations on 2D or 3d to inform. Not possible to find tasks associated to assets in InField in the main CDF solution. Observed Results: - Not possible to create an annotation by an end user in CDF, Infield and communicate to user via CDF to InField, also InField to CDF.
For a better usage of InField, by the operators and persons who need to execute the Checklists, it will be better to set the ‘Assigned To Me’ filter as Default on the Checklist List screen. That will prevent users from executing Checklists that they not supposed to, and also facilitate the visualization of the Checklists that they need to execute.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
