Product Ideas

As we are aggregating more and more activities since our go-live, we noticed a need to export more than 5000 activities from Maintain to Excel or Csv.   

There is a need to generate a check list for all functional location in the object list of a work order in SAP independent of operation. Currently it is possible to generate check list based on operations/tags. I.e if I choose one operation and click “Create and assign” I will generate a check list for all f.locs assigned to the operation.Sometimes it is a need to just get a check list for the whole work order where each f.loc in the object list is listed once. Using the current method this is not possible to get. The exisitng functionality of operation/f.loc checklists works great! This is just needed in addition to what we already have.

Many batch process customers use a long standing approach to batch management where a batch is designated the “best batch”, the benchmark all others are compared to, often called the “Golden” batch. CDF can provide batch and or other time period comparisons by using Atlas AI. This can provide key differences between batches for sure. The visualization is where there is a functionality gap. They want to see batch parameters overlaid on “Golden” parameters. I do not know how to accomplish this except with an AI driven dashboard. Attached is a basic example of output that would be useful. This was generated by co-pilot based on Atlas AI output.  

We would like to ask if the -> open button under files (see below screenshot) can be coded in such way that it can be opened in a new tab in the browser. 

As per the 3D Config feature, it should be good to have a Canvas Config option to configure the colouring for a quick highlight of the contextualization results in a Canvas for P&ID or any “plan” documents like isometrics loaded in a Canvas.In the configuration option we should be able to select attributes/data linked to the OCR captures, then in Canvas we should have a button to select and highlight all the OCR captures contextualized to PI-Tags, 3D tags, WOrkorders, SECE equipments…This option is of importance, it will avoid to check one by one each equipment in a P&ID, it will accelerate the completion of the contextualizations workflows, but not only… it’s also of importance for operations when preparing an intervention.

For classic data model, the UI can roll up timeseries from all children, which is a very useful function allowing you to reduce the amount of traversing to find all relevant timeseries. This functionality seems to be missing for data modelling. Is this functionality missing, or is it a particular requirement to the data model that we have not met in our model?It would be good to either document ​​​​​​better how to make this happen with data modelling, or reintroduce it if it is missing.  

ProblemIn checklist items today, users can only see the time series description, not the actual tag name. Because assets often have multiple associated tags, it can be difficult to determine which time series a checklist item is referencing. This is especially challenging when users click through to view trends and must manually identify the correct tag.Proposed EnhancementDisplay the time series tag name directly on the checklist item (alongside or in addition to the description).Value / BenefitsImproved operator usability: Newer or less experienced operators are not yet familiar with tag naming conventions, making it harder for them to confidently navigate from checklist items to the correct trend. Faster troubleshooting: Power users and IT frequently need to diagnose checklist or tag write‑back issues. Seeing the tag name directly eliminates the need to switch back and forth between checklists and templates to identify the correct time series. Reduced ambiguity: When multiple tags e

Currently Cognite Canvas allows users to perform below steps (example)1. Add Engineering document file2. Add Asset contextualized with the Engineering document file3. Add Events (Work Order, Notifications, Operations etc) contextualized with the asset where each event is a separate container/tile on the Canvas. Is it possible to add a tabular view for all the linked Events with an Asset instead of a single tile per event view.Also if the tabular view could have features to sort and filter based on the available event properties.  

Its a need to have the schedules tab available for all users using InField. As a technician it is beneficial to see all upcoming check lists in a schedule view just as the lead technician is able to today. This gives a much better overview of all lists coming up in the next week.The only downside is that the technicians don’t need to set a check list to “Ready” status. Its proposed to give technicians a display version of schedules, without the possibility of setting lists to “Ready”.  

In the overview tab its currently not possible to see who the checklists are assigned to. Its only possible to see if the checklist is assigned to a person.  In the schedules section, there is a good solution for this, where you can see the initials of the person who is assigned the check list, and when holding the mouse over the name, one can see the entire name.  Adding the same functionality to overview tab would be very beneficial

On the hand held device, add an option in the search section of the app to “scan” a functional location using the camera. Once the functional location is scanned in the field, the user automatically is brought into the detail section of the functional location.Using gloves for manually typing in f.loc in the field is cumbersome and adding an automatic scan function will save time for the end users.

In the overview tab in InField, be able to filter on all colums. As of now, only very few of the columns can be filtered on. An example is provided below:   Today one can for example not filter on ones own discipline(Work Center) or Work plan (Revision) which is crucial for finding your own relevant work orders. Filters are both relevant for work order and check list tabs.

Today the CogniteUnit is not shown under the Properties in Search. It is also not used in the timeseries Preview tab. It would be helpful to be able to search and filter on CogniteUnit, and do unit conversion in the timeseries Preview

there is no option to edit a chart directly from canvas. you have to open the time series in charts. Save as a new name and then reopen canvas and manually add the new chart. It should be possible to edit the chart directly from canvas, save and then update the canvas.

When using classic data model, there is a separate button in the right column allowing you to add events in the Charts For Data Modelling you have to do “+ Add data” → “Add time series” → select either Asset or the Activity category → select the Activity you want to include.For a new user, the “Add time series” might throw you off a little (reoccurring feedback from SMEs trying Data Modelling in Charts).It would be good to have names that allow a new user to find things more easily 

Can a simple label be added to Infield so that a user knows which environment they are in? We have 3 different environments and the only way to know which we are in for certain is to log out and log back in. We have had users create templates in our UAT environment before they realized it. Then they had to recreate them manually again in production.A simple label at the top would suffice. This would save us countless times of logging in and out and also make sure users know when they are not in the correct environment. ​@Andrew Montgomery 

The File category view is very useful, allowing you to quickly filter on the right files. But some file categories are more important than others, especially the P&IDs. It would be good to be able to configure the order of the file categories in that list, allowing us to eg “pin” the P&ID category on the top 

there's an unnecessary amount of filtering options under search. I guess its okay to show the options available, but for several tags there are multiple filters without any hits - why are these shown? The number of filters is already many, some of them with descriptions not too accurate (but I guess they are for some people...)  This is mainly for trying to remove some noise from the filtering functions.   An explanatory information document for the filter options would also be nice. many people who will be trying to filter will really struggle to know what to filter on.Can hide properties from filter if none of the values are populated.

When selecting an instance in Search, the Overview tab is very useful (seeing more than one data category without having to switch view). The challenge today is that the tiles have pre-defined columns, and they do not allow for filtering. It is of course possible to go into the “full screen mode” for each category, like Activities, but then you loose the possibility of seeing data from more categories in context.It would be very useful to be able to configure the properties we see in each tile and to filter on properties, like we can do in the “full screen mode”. 

With the data modelling framework, most models will end up with a significant number of Views. Today we are not able to control the order the Views are presented in a good way. By reverse engineering it seems like the order of the Views is based on The order of the (first mentioned) CDM extension in the model definition. Alle non-CDM Views are listed at the end, irrespectively whether it is listed before CDM or not  What is considered a CDM extension by the UI is not based on the implements, but whether it reference at least one property from one of the CDM containers Inside each Category (eg, a specific CDM extension, or the non-CDM Views), the order in the model definition dictates the orderIf I choose alphabetic sorting it seems to only affect the non-CDM-Views, and not the order inside each CDM category. It do however put all the CDM categories first or last It is very inconvenient to use the order of appearance in the model definition as the way of sorting (we have to sort both th

When selecting an instance in Search, the Overview tab is very useful (seeing more than one data category without having to switch view). However, the tiles are static and cannot be resized. Resizing would allow the user to see more of the data in one category while still see the other data categories (eg I want to see more of the properties from the Asset while still seeing the list of workorders.For the same reason we would like to be able to change the order of the tiles, eg moving the workorder tile up next to the properties tile, to better focus on the things we want to see.The same behavior is also relevant when searching for data via Charts and Canvas

When selecting the property that will be used for the x-axis in the graph, the list is not searchable. For more complex Views the list of properties can be long (100+), which makes a non-searchable non-sorted list relatively hard to work with 

The closest to that solution as for now would be adding a timeseries on the canvas, then you have an option to Open in charts and then choose a new one or existing one. This is too cumbersome.See picture below of suggested solution directly in canvas: 

Recently a change was implemented to make the connection lines between documents on a Canvas to be orthagonal and to combine and flow between documents.There are some Canvases where I would like to be able to see a direct straight line connection between my references to quickly locate interconnectivity.My product idea:  add a toggle to allow me to choose between orthagonal connectors or straight line direct connector.

Currently, the PI-AF Extractor works as a forward synchronization tool that reads the PI-AF structure and sends it to Cognite Data Fusion (CDF).The extractor correctly handles: Insertions: New elements created in PI-AF are detected and created in CDF. Modifications: Updates to elements or attributes (such as renaming elements or moving branches) are synchronized and reflected in CDF. However, when elements or branches are deleted in PI-AF, the corresponding objects remain in CDF, and there is no indicator that the element no longer exists in the source system. This behavior is currently intentional to prevent accidental or irreversible data loss in CDF.While this approach protects data in CDF, it creates challenges for downstream processes. Without any indication that an object was deleted in the source system, it becomes difficult to automate workflows that depend on identifying obsolete or removed elements.Requested capabilityA mechanism to identify when an element has been deleted