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
Digital Transformation Team of Cairn suggested following capabilities into Cognite charts.Extend the concept of folder to store charts created by different teams. e.g.: Teams can chose where to store their chart. Add capability to Industrial Canvas to import a folder containing charts.
Hi, I’m wondering if i could make AI search answer more correctly.My understanding of AI search is first LLM changes questions in a search bar into graphQL and then returns the corresponding data as an answer.We need to tune questions so that we can draw the answer we are looking for and is there any example of use of RAG to tune questions more friendly to your own knowledge graph?I don't know technical detail but in my image, designing to sandwich LLM between RAG and graphQL might help improve accuracy.
Global companies might face the challenge of having global data used by different countries, regions and languages, in ERP and other source systems. Such data exist in form of shared ‘catalogs’, ‘master data’ or ‘configurations’. This data is often setup and maintained in source systems, with different languages to support users in multiple regions. This data then became attributes or metadata in Cognite objects.Example given - Current situation:This 'catalog' data (metadata) is extracted from source system in one single language - English - only, since CDF can't store it in multiple languages.Then these metadata - field names and field values - are displayed in CDF with the only one language available - English -.*Notice Metadata fields names and metadata field values don't change, despite user changing CDF language settings. Proposed solution (request):Have a way to store metadata fields names and metadata field values, coming in different languages from source systems, with language indicators such as EN (English), SP (Spanish) or DE (Deutsch) in CDF. Then display the metadata field names and metadata field values in CDF UI, based on the user language settings.
Create a new Tab on CDF home page (in the same line as Home, Data Explorer, Canvas, Charts) called Process Explorer (or any other suitable name). This should give the users the ability to build process graphics for manufacturing plants. Standard palette for common unit operations (Columns, vessels, valves, controllers, pumps, heat exchangers etc.) Ability to embed timeseries associated with Unit Ops in the graphics. Contextualization of Files, Assets, 3D, 360 etc., with Unit Ops on the graphics. Ability to spinoff ad-hoc charts by selecting timeseries tags from the built graphics. Ability to save and share these charts. Ability to add ad-hoc calculations on the graphics. Ability to navigate from one graphic to another. Dynamic color coding of Unit Ops based on conditions. (Example: - Pump ON = Green, Pump Off = Grey) Ability to group graphics (based on which processing plant it belongs to.) Ability to share graphics. Ability to lock graphics for editing per credentials.
Hi. In our data models, we typically have a few attributes that contain only a sinlge float. Say, the “installedCapacity” of a power plant. It would be useful to have this float be a “float with unit” type - preferably connected to the unit catalog for simple conversion.I assume that right now we’ll have to define the “float with unit” as our own custom type, but would be a good idea to have this value type come as a standard type?
Checking the online documentation for PI and PI-AF extractors, you will only find a single version of PI-AF-SDK which is supported by them: PI AF Client 2018 SP3 Patch 3. But it wont say which versions of PI Data Archive and PI-AF the extractors are compatible with. It would be great if the docs could mention the range of versions of those two components that are supported.
On behalf of Celanese InField super users:When executing a checklist in offline mode on a mobile device; it has been discovered that there is a risk of losing data due to accidentally refreshing the screen. Due to the design of the UI of InField 2.0, it is common to frequently scroll through a checklist when completing. Most users do this rather quickly without giving it much thought. However, when scrolling back to the top of a checklist, a user could be at risk of accidentally refreshing the screen whenever they reach the boundary limit (very top item) of a checklist. This is due to how the touch interface works on the mobile devices. To refresh the browser, the user needs to only press and drag their finger down on the screen window to initiate a refresh. This is a common movement when scrolling through checklists and could be inadvertently initiated. Would it be possible to include visual indicators or engineers controls that could limit the possibility of this issue occurring? Perhaps something that lets the user know they have made it to the top of the checklist and prevent them from further scrolling and initiating a reset? We will also explore if this is something that could be controlled within the device settings themselves.
There are cases on the checklist tasks execution that technicians and operators need to select more than one option from the Check Items buttons created. For example, we could have multitple reasons for a task be ‘Not Ok’. But currently, the users can only select one button from the Check Items created. Check the example below: All the options are ‘Not Ok’ and in this example, it could be one or the 4 options. We may consider use a ‘Message’ field, but it’s not the ideal because users can insert anything on the Reply field.
Hello, That would be nice to be able to use the asset external IDs (instead of the assetId field) in transformations, to link events (or timeseries, sequences) to existing assets.
Enhance the SAP extractor to incorporate a configuration option enabling the division of large date range inputs into smaller segments. This functionality aims to prevent SAP requests from failing due to size constraints.
I see cognite SAP extractor doesn’t accept multiple keys for sap_key parameter.I have a requirement to ingest many tables , where i need to give multiple keys in the SAP_key parameter.Would be great if this feature will be added in the next version of SAP extractor.
Currently, the Power BI data connector contains a function to return timeseries aggregations and this function takes a source, start and end dates, and a granularity. It then returns 13 columns of data. My report only uses 3 of those columns: timestamp, timeseriesId, and Average. With 3.4 million rows, this is a huge amount of wasted bandwidth and storage. It also adversely affects the report performance to a small degree.One possible solution to this would be to add a parameter to TimeseriesAggregate() to indicate which columns of data should be returned. Not transmitting the data would save network bandwidth, reduce the size of the report, reduce the time required to load data, and improve the end-user experience.
Do you have in the product roadmap to integrate one canvas to another. Such that you can have several canvas at various granular levels ( System view, asset view, platform) and all of them could be connected so that its easy and intuitive for a usecase.
Cognite Data Explorer includes a feature to search in an object such as a P&ID. This feature would be very useful in Canvas. The search in Data Explorer also allows cycling through all search results.
In Infield Trends section, only timeseries linked directly with the selected Asset is shown by default. This is not the same behavior as Fusion, which show the timeseries of child assets.Although we have the ability to see other trends, there might be some cases that other trends can be shown more easily, for example adding “Other time series related with this tag” under “Other time series on this tag”.
On behalf of Celanese InField super users:I would like to see some functionality in InField that limits who can view and approve checklists based on discipline. An example of this is when a checklist has been opened from a maintenance work order. The process team captains should not be able to see these checklists in their “Checklists for approval” tab or even have the ability to approve any checklists that are owned by maintenance. Can the approval rights be restricted based on maintenance?
Currently, date is not available as input from the users to the tasks in infield checklist. This is important to users as the users would like to record the date in few of the tasks in the checklists as shown belowCatalyst replacement date? Hydrotest completion date for the equipment?
End users expressed the need to be able to share and see the calculations that are behind a chart, when the chart is embedded in a canvas and the canvas is shared with others. At present only the trend lines from charts seems to be embedded into Canvas.
On behalf of Celanese CDF super user:When setting up data set graphs in Canvas, graphs are not pulled in a standardized way (some show vertical, other horizontal) as well as not showing the same standardized data series in the picture (see picture attached)
On behalf of Celanese InField super users:I would like the ability to archive and delete unwanted checklists in InField 2.0. Currently, InField 2.0 only supports the ability to delete templates but not checklists. The only option we are given is to mark checklists as “done”. However, if this is added, it must be limited by access permissions as we do not need all users to have the ability to delete checklists.
When data is downloaded in CSV format, the time stamp format is not as detailed and we would like the timestamp format to match the output format when it is retrieved from API, which is like 2024-04-14 10:08:19.115000-05:00
Users may need to make adjustments in a certain numbers of Templates and it will be good to have an option to select multiple templates on a list and change the status to Ready. This will improve the user experience, by reducing the clicks to execute an action and saving time to operate multiple templates.
CDF - Filter option is not working as expected under common filters at Data Explorer screen. Login to CDF Click on Data Explorer tab in CDF menu bar. Click on Files tab in right side of the panel. Set Data set as 'src:006:documentum:b60:ds under Common filters in left side of the screen. Select the check box ‘Before’ under common filters in left side of the penal. Click on the Calendar icon and set data as (e.g.) '10-01-2023' Expected results: Document ‘Amarjeet_Test_DT.docx’ should not display in results window because its created after the set date.Actual results: Document Amarjeet_Test_DT.docx is displaying in CDFNote Issue exists for all Date filters like Created time, updated time with Before, After, During in CDF, user want to know what date is used for filtering the documents in CDF with these filters.
Feature Request: Implement a dynamic visualization module in the Cognite Monitoring for extractors to enrich data insights. Users should have the ability to visualize the extractors status by plant in a traffic signal format (red/green/blue). The feature must support real-time updates, allowing users to monitor live data and historical trends seamlessly. Include interactive elements like drill-down options, tooltips, and data filtering for a user-friendly experience.
Can we have a text-editing mode in Cognite Hub where we can type Markdown? We developers love markdown.
Already have an account? Login
No account yet? Create an account
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
