Join the conversations to shape a safer, more efficient, and sustainable industrial future!
Recently active
As our main data model grows we are seeing a need for better management and navigation in the Fusion UIWe are doing what we can to “trick” the UI into behaving how we want. But we still run into limitations. Grouping the views by the Core Data Model (CDM), doesn’t really serve the purpose we need when the semantics of our views rarely match with the CDM setup. So grouping them by business meaning and relevance is something we see a great value in and would help our end users navigate the UI more easily.We have an “aggregate” model designed for the Fusion UI that contains all our views in one giant model allowing our users to see the full context of what we have in CDF. This model is invaluable to us. This model is also expected to grow with time. Because of this we also see the need to have some kind search/filtering for the views within a location filter as the number of views will force endless scrolling. Markus PettersenAker BP - Data Platform Architect
Ability to sort by multiple attributes simultaneously to improve usability. For example, sorting by area and f.loc. at the same time.Norwekgian: Kunne sortere på flere attributter samtidig for å skape brukervennlighet. F.eks. sortere på område og f.loc. samtidig.
Links from InField should open directly within the InField app instead of an external web browser.Norwegian: Når man åpner linker fra InField så vil man InField skal åpnes og ikke nettleser
We would like some way to give a CDF project an alias and also to set the order in which they are shown. The technical name of the CDF projects is not always what we would like to communicate with our end users, rather than telling them to use “abp” I could tell them to go to “Production”. Just more friendly to the less technical users we have more and more of.And our projects have a natural order that is not reflected by an alphabetical sorting.Here is an example from a Flows app showing what I mean:
When selecting the “File category view” for a CogniteFile extended View, the table width for the header is disconnected from the columns containing the values. Note that the Name width match the width of the “Manufacturing...” column (which is the category and not the name of the file), but is disconnected from the actual name column
If I choose a different language than English under “Admin account->Language”, the Atlas conversation window is still in English
Issue Summary – Cognite connection reliability (Power BI / CDF)We’ve had reports of a recurring problem when using Cognite connections in Power BI (Desktop and Service) where the authentication session does not persist.Problem DescriptionThe Cognite connection repeatedly logs out users unexpectedly. Users must re-authenticate frequently, often daily, using Aker BP credentials. This behavior occurs in both Power BI Desktop and Power BI Service. The issue is specific to Cognite connectors and does not occur with other integrations (e.g., Microsoft Fabric connections), which maintain stable sessions.ImpactDisrupts workflow and user experience due to repeated sign-ins. Reduces productivity, especially for users working with frequent or scheduled reports. Creates inconsistency compared to other data platform integrations.Expected BehaviorAuthentication sessions should persist for a reasonable duration, similar to other enterprise connectors. Ideally support long-lived sessions or token refr
Unfortunately, I cannot insert the approved table as a true table in Canvas using the currently available tools. The Canvas integration only supports data elements and chart/box structures, not tables, spreadsheets, or formatted notes.Any previous box-based table attempts should be removed manually. The table provided in the previous response is the complete and corrected source and can be copied directly into Excel or a Canvas table/note without losing the column layout.
Using Search, when selecting an instance and then choosing the Properties tab, all the populated properties are listed with the key and value in two columns. The key column is apparently a fixed width column (40ish char wide), not possible to manually resize, and it doesn’t resize when the browser window is resized. This becomes a problem when the property key is long, something that may happen when the property is a JSONObject such that the key becomes “nested” Below is an example of how it looks It seems like the UI is able to wrap the line if the key either has a space or a hyphen, but not else (have not tried all characters...) We can of course mitigate this by creating more compact keys, but it would be really helpful if we could resize the column such that our key naming convention do not have to take a 40 character UI limitation into account.
Hello community! The Aura design system team has launched a shared community repo where builders can contribute and pull industrial components, patterns, and app templates instead of building from scratch every time.❓WhyBuilder feedback and app audits turned up the same problems: components either don't exist yet or exist somewhere nobody can find, so people rebuild the same things repeatedly. Aura is also an intentionally a high bar for contribution as changes can have wide-reaching impact. Community gives builders a lower-stakes place to share and refine work without waiting on Aura. It also protects the platform experience - the more apps share real, proven patterns, the less an end-user has to relearn when moving between them.🛠 How it worksCentralized repo with a registry-based install approach means one single source of truth where you can pull a component or app template with one command, customize it for your use case, and run updates on your own terms Usage tracking signals to
ProblemField users commonly create Observations while working at the asset, but the mobile experience does not currently support the same file attachment capabilities already available in the desktop version of InField. As a result, users are unable to attach important supporting documentation, particularly PDFs, at the time the Observation is created.Many Observations require supporting documents such as P&IDs, equipment drawings, procedures, vendor documentation, inspection reports, and other asset-related files. While users may have these documents available on their mobile devices, they must often return to a desktop computer to complete the attachment process.PDFs are the most commonly requested file type, especially for P&IDs and other engineering documentation associated with the asset. Today, users often need to stop their field activities, walk back to an office or control room, locate a computer, open the Observation, and attach the document. Depending on the location
What we need, and why it is per-asset.We ingest from OPC-UA. One extraction pipeline serves a production line carrying several machines. The PLCs publish on change, so a tag going quiet is completely normal — and from the data alone it is indistinguishable from the source having stopped.Our calculations forward-fill. So before forward-filling a value we have to know up to what point it is safe to do so: the last moment we know that machine was actually reporting. That is a property of the machine, not of any individual time series — every tag on a machine shares the same liveness — so what we need is one current value per asset, kept up to date continuously and read on every calculation.How we did it with classic resources. We wrote a Last Synchronized key into the classic asset's metadata bag. One small write per asset per cycle, and it cost nothing against data-modelling limits.Why this is awkward in the core data model. CogniteAsset has no free-form property — none of its 23 propert
Search Experience ImprovementsWe would like to see the "Show More" expansion button removed from the Search experience.Today, as additional datasets are added, the interface progressively hides content behind the "Show More" control. This creates friction for users who must repeatedly click to access information that is already available. More importantly, users who are unaware that new datasets have been added may never discover them because they remain hidden by default.Instead, we recommend allowing the full list of datasets to be displayed in a scrollable view. If the number of datasets exceeds the available page space, users can simply scroll through the list rather than repeatedly expanding sections. This would improve discoverability, reduce clicks, and create a more intuitive search experience.Collapsed Expanded@Andrew Montgomery
Currently when filtering with certain column on Cognite Industrial Tool Search we have options to filter byIs Equal to Is not Equal to Starts With Doesn’t start with Is set Is not setCan we please add another option “Contains”?This would significantly improve the ability to filter data and files on text-based fields such as Title and Description, enabling more flexible and effective search capabilities.
Hi team !Is it possible to configure a backup (failover) server for the PI Extractor, so data collection continues if the primary server goes down?Thanks!
As part of the September/Q3 product release, we enabled Smarter Search Results across all clusters except westeurope-1. For westeurope-1, we’re currently working on stability improvements. To avoid introducing additional changes while that work is ongoing, we’ll enable Smarter Search Results there once those improvements are complete. Smarter Search Results is improving how data is analyzed to provide more relevant and precise search results. See more information about this improvement in the linked documentation.
The idea is to get a Search and Filtering options in the “Data Managament > 3D” tosearch something in the structure of the 3D model filter the nodes to display or not in the 3D model, this Filtering option should be possible with a “contain” option with multiple filters option. This should save the active filters to display the “cleaned” 3D CAD model in the Industrial tool domain. By this filetring we keep the original structure of the 3D CAD model and we can clean it for its display in the CDF
The proposal is to get in the Search overview, the location of the contextualized tag in the 3D CAD structure. Such feature will help the user from where the 3D CAD contextualization is coming from in teh 3D CAD structure.Rigth now we do not have this feature, and this should allow us to potentially correct, add, remove some pieces of the 3D CAD structure contextualizationSee the attached illustration...
Hi, Unfortunately, we experienced unforeseen challenges with the Preview Panel Redesign in the Search application after the Q3 release September 8. Due to these challenges, we opted for rolling back the update, so that we can assess the issues and handle them appropriately. We deeply apologies for the issues experienced with the release, and we will ensure better testing before a new release. Current estimate on timeline for re-releasing the updates with bug fixes and other improvements, is the Q4/December release. Please let us know if you would be interested in a limited Private Preview spot on the updates, which will open up for a period of time before the December release. Apologies again, and thank you to all reporting challenges with the release, Sofie, Product Manager
Hi everyone,We're excited to share one of the standout features from our Q3 release: real-time, multi-user collaboration in Industrial Canvas — now in Private Preview.The problem we're solvingUntil now, Industrial Canvas has been a single-user experience. That meant teams working on the same problem couldn't work in the same space at the same time — creating silos and slowing down team-based decision-making.What's newIndustrial Canvas is becoming a truly collaborative workspace, where multiple users can work together simultaneously — exploring data insights side-by-side and driving faster, unified decisions together. Where this creates value — real use cases (not limited to):Root Cause Analysis — multiple engineers investigate different parts of a failure simultaneously and consolidate findings instantly. Field-to-Office Bridge — field operators and back-office engineers mark up the same P&ID together, in real time. Meeting Facilitation — run operational reviews or shift handovers
RequestTo improve business continuity and operational stability, we would like to request your consideration for developing official applications within InField that provide the following capabilities:An application that can export individual inspection forms in both CSV and PDF formats. An application that enables approval of individual inspection forms and allows users to view and track their approval status.BackgroundCurrently, we operate a workflow in which inspection results are entered through InField, exported using a Streamlit application, and then submitted for supervisor approval through another Streamlit application.Under normal circumstances, this workflow functions without major issues. However, due to a Streamlit application issue that occurred yesterday, the workflow became temporarily unavailable. To the best of our knowledge, this is the second occurrence of a similar issue this year.In addition, since Streamlit is currently provided as a preview feature, we have conce
SummaryEnable aggregation operations (such as step_interpolation) on requests containing both numeric and string time series in the same SDK call.Currently, aggregation works correctly for numeric time series, but the request fails when a string/alphanumeric time series is included alongside numeric series. This limitation prevents users from retrieving synchronized operational datasets that combine process measurements and categorical/status information in a single query.Problem DescriptionWhen using the Cognite SDK method retrieve_dataframe() with aggregation enabled, requests containing mixed data types fail if at least one time series is of type string.Example:Numeric-only aggregation → works correctly Numeric + string aggregation → failsThe expected behavior for string time series using step_interpolation is to replicate the last known value across the aggregation interval, similar to how industrial historians such as PI System behave.Example Use CaseOperational dashboards and an
As part of the September/Q3 product release, we enabled Smarter Search Results across all clusters except westeurope-1. For westeurope-1, we’re currently working on stability improvements. To avoid introducing additional changes while that work is ongoing, we’ll enable Smarter Search Results there once those improvements are complete.Smarter Search Results is improving how data is analyzed to provide more relevant and precise search results. See more information about this improvement in the linked documentation.
When dropping a file from your desktop/drives into Canvas, the file size increases. As one example, it went up 30 times; from 84kb --> 2520kb (without the canvas coverpage). The file size change makes it difficult to download the canvas, as it gets stuck. The end users cannot download the canvas they create and therefore are prone to stop using the platform.