Join the conversations to shape a safer, more efficient, and sustainable industrial future!
Recently active
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”.
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
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
Currently, the Japanese translation for the operator used to perform exponentiation in Charts is shown as 「電源」, but this makes it difficult to understand at a glance what the function actually does.Would it be possible to correct this to a more appropriate translation? It’s a minor detail, but since this is a function that is used fairly often, I would really appreciate it if you could consider reviewing the translation.
In Charts, it’s possible to freely configure the units for each time series.However, I’m having trouble when trying to merge a manually set unit with the default unit.For example, in the screenshot, the upper time series is a calculated value added using “Create calculation.” I manually set its unit to “°C,” and attempted to merge it with the lower time series using “Merge unit.”But Charts recognizes them as different units, so the merge doesn’t work properly. To work around this, I have to manually reassign the unit “°C” to the lower time series—even though it already has the correct unit. This is quite time-consuming.If I'm doing something wrong, I would really appreciate it if you could point it out.If this behavior is actually by design, I hope it can be improved in the future.
Current BehaviorIn the transition from InField 1.0 to InField 2.0, PDF rendering on mobile devices shifted from utilizing the device's native viewer to rendering in-app using the Unified File Viewer. Native viewers are written in native code (C/C++) and render directly to the GPU meaning that they can stream pages and down-sample large images on the fly without memory constraints. But this change, while necessary to support advanced interactive features, subjects the viewer to strict memory limits enforced by mobile browsers (e.g., iOS Safari, for example, caps total canvas pixels at ~16.7 million.). Consequently, when a user attempts to open a highly complex or large document that exceeds this safe mobile rendering threshold, the browser fails without providing any notification or context to the user.Proposed SolutionImplement a clear warning prompt within the Unified File Viewer when a document’s size exceeds the safe mobile rendering limit. A notification such as, "Document size too
Alternate Tank Numbers – It looks like the alternate Tank numbers are not included. I tried to search for Tank 35-2 and it wasn’t able to locate it. Would be possible to add a field for the alternate name for tanks?P&ID Connections – I like how Cognite draws connection lines between references currently, however I think this could be improved by adding a conditional for matching line number so that each exact pipe connection only is shown.Text ID – on some of the P&IDs, it looks like the text identifier struggles to ID rotated text, is there any way to improve this? Ex. Can the AI run another similar search with each P&ID rotated 90 degrees?
In the checklist section of InField it is a need to be able to sort on functional location attributes. If we first are able to choose which attribute to sort on, and afterwards if it is in rising or falling order it would be really helpful! A specific use case for this is to sort on location/area. Then the user are able to see all f.loc that is in the area that he currently is working in.
There is a need to create a check list based on a list of functional location copied from an external source (Such as an excel sheet) or manually typing in. The functionality makes it easy for technicians wanting to create checklists based on a list of functional location from mail or other list to make tag data/work orders and 3D model available in the field. Using templates for this is not a viable option since these are one-off needs (Check list is only needed once). This functionality has been available in earlier versions of our InField which can be used for reference.
Sylvamo users are looking to avoid scrolling with the trackpad, essentially. When navigating the Chart, the idea is: Buttons that allow users to scroll through the time series (see screenshot below). These buttons could dynamically scroll either large chunks of time or relatively small ones, depending on how quickly the user was clicking them. End users are using Dell, Lenovo etc. laptops
When exploring data in CDF search industrial tools, I want to be able to open & expand the 3D model/ asset results in a new tab, without (pop out in new tab button) without leaving my search page ,currently I have to expand the result to full screen & leave my search page ( not easy to compare between different assets & have to duplicate tab & consume time for search results to load then expand only one asset per tab)not sure if I am missing an already existing feature,But a pop up button for asset overview, would be very useful for me & my clients
Sometimes is difficult to navigate in Search. Lets improve filters in Search by adding "Contains", "Is empty" (and probably numerical options like greater, less etc) options. This is industry standard. But CDF doesn’t have it
In Celanese, we are reviewing moving multiple data model views to streams due to the growing instance volumes. Several of the views have direct relations to each other and to other data models. Within one record, we need the capability to define a direct relation to a data model instance and to a record in another stream.
The user from MPC have requested the ability to customize the Tooltip on the Annotation display on the Canvas. When hovering over an annotation in Canvas, the tool tip is listing the Source IDs of the referenced files. The Source ID is less meaningful to users than the drawing number or the title of the drawing. They’d like the option to control what appears in the tool tip.CC @eric.dixon@cognite.com
the 3D Model pushed into a power BI dashboard with the annotation as well, to be utilized in external dashboards.
In Workspace Data Management / Data explorer you can preview a timeseries and download datapoints as csv (image attatched). In workspace Industrial Tools / Search, you don’t have this option to download as csv when previewing a timeseries.CDF users who use Industrial Tools / Search, have to find the ts externalId, copy it, switch workspace, paste and search for the ts externalId, preview and then download. This is very confusing and non-intuitive, especially for new or casual CDF users.
SummaryIntroduce a first-class NumericSeries object in Cognite CDF to natively represent depth-indexed data (measured depth, true vertical depth) and elapsed-time-indexed measurements (wireline elapsed time, drilling offsets in hours). Depth is a fundamental axis in upstream oil & gas, on par with time measurements. A NumericSeries would unlock more natural storage, querying, visualization, and analytics for a large portion of subsurface and drilling data.Why numeric indexes matter in Upstream Oil & GasNumeric indexes are the most widely used independent variables across the upstream domain: Drilling: MWD/LWD logs, drilling parameters vs. depth, trajectories, broomsticks, hole conditions Geology: lithology descriptions, stratigraphic tops, formations, facies vs. depth Petrophysics: wireline logs, core measurements, interpreted curves Reservoir & Completions: perforations, zones, intervals, properties vs. depth Elapsed time s/min/hr in addition to depth: wireline, we
Dear Cognite Community,One of the repetitive tasks I have noticed in InFieldIs that some checklist items are the same for multiple templates,Or that some templates need same task added in an update ( like additional requirement update).Currently we can duplicate tasks within a single template & duplicate a whole template,But, if we want to drag & drop / copy tasks/ grouped tasks between templates, there is no option to do that,& they have to remake the same task in every template they need .I hope that this idea is put into consideration in future release of infield - as that simple addition will greatly help end users.