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!
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
To ensure data quality we want to run a filtering algorithm on certain timeseries that are prone to faulty spikes. Typically we want to replace a datapoint that is more than rollig.avg +/-3rolling std.dev with interpolated values. as part of this, it would also be useful to track the changes on the actual datapoints. Is there a functionality in CDF for this? Ideally, there could be some metadata attached to the datapoint, describing e.g. the original value, when it was changes, etc.
We currently have the ability to turn off annotations & connecting lines in canvas. I do not always want these annotations because they can make the canvas become too “busy” on a canvas that I’m using on projects where I just want to share the canvas, collaborate, or present. Sometimes people I share the canvas with may not know how to turn these off. I would like for Canvas to cache or “remember” my choices so the annotations/connecting lines do not have to be turned off each time someone opens the canvas. Default should be to have these turned “on”. I would just like them to stay “off” once I select that choice. Attaching visual examples. I would be happy to answer any clarification questions. Thank you!
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.
Ability to import a checklist template from a word or excel file (some sort of required format/template) instead of in UI only. Or pull from CDF or source.
When creating a “Point of Interest” in Scene, after it’s created, you need to click on an area that doesn’t overlap with the point cloud (the dark blue area in the screenshot) to display its details.This means you have to zoom in quite a lot to avoid overlapping with the point cloud, which makes it difficult to check the “Point of Interest” while viewing the entire point cloud.Therefore, it would be helpful if “Point of Interest” could be made easier to click and select, or if Scene could include a mode that allows selecting only “Point of Interest.” This would make the feature much more practical.
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, well testing, drilling offsets Statistically, the largest share of subsurface data in upstream O&G is indexed by depth rather than time. Treating depth as a first-class concept would better reflect how domain experts think, work, and analyze data. Traditionally storage and infrastructure around depth and time logs in upstream software follows exactly the same pattern (everything except the index type).OptionsIn 2026 CDF currently has 3 potential options to store depth data - Sequences, Records, Files. Theoretically, CDF also allows to use TimeSeries, since index is integer. Integer index is interpreted as milli-seconds since 1970, however can hold any value, for example, millimeters, which is OK for depth and length measurements. One of viable options for future CDF is to fork TimeSeries into NumericSeries (or DepthSeries, or LengthSeries), since it seems to satisfy most of requirements for this kind of objectFeature comparison Requirement for numeric Sequences Records Files NumericSeries* Static schema (ex, trajectory) Yes Yes Yes Yes Flexible schema (most depth) Static only Static only Any Any Datasets 1000+ columns 200 max 1000 max Any Any Datasets 100k+ rows Too heavy All data <50M Any Any RAW and Transformations Yes No No Any Filtering by index Only int index Yes No Any Filtering by column values Yes Yes No Yes Aggregations No Yes No Yes Chunking/pagination Yes Yes No Yes Unit conversions No No, planned No Yes Python SDK Yes, now No, planned Yes Yes Extractor support Yes Yes, partial Yes Yes Value type - float Yes Yes Yes Yes Value type - float[], images No Via JSON Yes No Value type - text Yes Yes Yes Yes Value type - timestamp Yes Yes Yes Yes Available in CDF UI Yes, native Custom app Yes Custom app Value to CDF and Users Aligns CDF’s data model with upstream O&G data models (OSDU, WITSML, PPDM) Improves performance and usability for subsurface and drilling workflows Enables rich domain-specific applications and analytics Lowers total cost of ownership by simplifying data pipelines Strengthens CDF as a system of record for subsurface and drilling data
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.
Hello,As seen in several topics :Cognite Hub - Alert/Notification when MQTT Hosted Extractor is down Cognite Hub - MQTT Hosted Extractor ErrorCould it be possible to configure kind of alert or notification with rules on topic filter status ?A timeline of last 72h is already computed. It could be very usefull to receive something (mail, notification) on custom trigger to avoid silent data loss. Regards,Pierre Rambourg
With the use of Cognite Core Datamodel, we can create different types of Assets. Right now I have a case where I have EquipmentTag and Functional Locations.An EquipmentTag always has a FLOC a parent. So the Hierarchy is always:FLOC1-- FLOC1.1----EquipmentTagFLOC2--EquipmentTagIn this case, If I open the EquipmentTag, te UI is trying to get all the hirarchy as EquipmentTag, so the UI knows that exists a path, but can’t create the tree-view cause no data is returned. If I open the same EquipmentTag just as an Asset, the tree-view works fine, but then I lose all the specific data from my EquipmentTag.Openning as EquipmentTag
I’m creating this feature request on behalf of @Smitakshi Sen In CDF Data Explorer, it should be possible to download a filtered list of events into Excel or CSV format with all the selected metadata columns.For example, when filtering events by type “Failure”, CDF returns the list of filtered Failure events, however, that list cannot be exported for audit and reconciliation.
In Infield 1.0 the user was able to print the summary report of the checklists. The user would like to have the export as a pdf to upload to other software and email the reports if needed.
User story:As a developerI want to produce documented and transparent codeso that my end users and colleagues can understand what is going on. Current stateFor deployed Cognite Function we see three tabs: Calls, Schedules, and Details. Documentation is limited to the description field. Desired stateI would like to see four tabs: Calls, Schedules, Details, and Documentation/ReadmeI would like to be able to write a README markdown file that I package together with the handler, requirements and all the rest. This should be picked up and rendered in a dedicated tab for the function. I think this would really increase transparency in the deployed functions. All employees have access to CDF, but not all have access to source code repositories where documentation usually lives. The deployed Function is a black box at the moment.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.