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
We can chose color, weight, type and linear/step. but often there are alot of trends we want in the backgrond, so can we add a alpha (0.0 to 1.0) / transperancy of the trends aswell? to be able to have information in the background without clouding over the most essential trends. Should be a quickfix :)
Remote is not showing P&IDs, we only see a black screen when we attempt to open it. It is visible in CDF. @simenri @MaureenB
Currently, using the "download metadata with datapoints" button on a time-series in the “explore data” tab of Fusion UI, gives a JSON file which does not include datapoints which have timestamps in the future. As such, when used on time-series which contain future predictions, the download button does not give you all the data-points. Can the functionality of the download button be amended to include future data points?
I would really appreciate if you can provide capability to drop a pin (or a little walk man) into the 3D model, and the app can then zoom and navigate into that area. A lot of 3D visualization software has the capability to do that instead of us trying to wheel mouse. More example in this link:see time stamp 00:25 to 00:30
Once CDF Geospatial is in general availability we can start to process 50 million daily “emission points” for 250 000 ships world wide. We developed this solution in collaboration with Microsoft and NoA Ignite. By means of Spire AIS-data (being curated by Global Fishing Watch) and IHS vessel particulars data (dimensions, type of propulsion system, fuel type etc.), we can feed data into an emission model. Through partnership with Mercuria, Allianz and more, we can provide a lot of interesting GHG emission data without being “connected” to the ship and fuel-meters. But, it will be even better if we could get in touch with some of the major maritime players, like Wartsila and their Voyage service. If they could share fuel data anonymously, we could feed our emission models with live training data and become even more accurate.Link to Microsoft article:https://www.microsoft.com/en-us/ai/ai-for-earth-ocean-data-platformWe also presented the solution at Microsoft Build in May 2021.
As a developer, I want to only interface with externalIds in cdf, so that the state between resources can be maintained consistently and, and for easy state-management accross projects.With the internalId of resources exposed, a vulnerability in the state of CDF occurs when parts of the tenant are e.g. recovery. Additionally, the management of internalIds complicate the development and maintenance of the "fusion" part of CDF: linking Events to Assets, TimeSeries to Assets etc.We understand most of this feature to be covered by Flexible Data Models, and temporarily with a managed consistency tool in Cognites recovery portefolio.This feature has the highest priority for the modelling of Statnett data.
As discussed in both the name and the description needs to be filled when changing a name of a dataset. If not the error from the API is displayed, which might not be easy for end-users to undertand. Suggestion: Do a check in the frontend on the input that both Name and Description is filled.
As a developer/architect, I want to version my datasources in CDF, so that we can manage compatability between datasources (fusion layer) and compatability internally in the datasource. This request pertains to two related challenges in CDF:a) A versioned datamodel allows a concept of a rollback of the datamodel (by enabling a concept of breaking changes inside/between datasources). It also allows for an unambiguous recovery of a tenant/project where dependencies in datasources/resources are explicitly declared.b) A versioned datamodel will detect breaking changes in the datasource, and allow the maintainer to reason about blocking a version (in case of an error), incrementing a breaking major version, etc. This feature request has medium priority in from the Statnett data modelling team.
Currently the setup for inserting and reviewing OIDC credentials is confusing in Fusion. At the first setup a suggestion for Scopes, Token Uri and CDF Project name is suggested. When the Client ID and Client Secret is filled in and the credentials are saved, all fields are cleared on the next visit on this config site. Furthermore, it is confusing that the Manifest CLI file does not include this config. Also, the example file here is not in sync with the documentation and does not seem to work without reformatting. Suggestion: All fields are filled except Client Secret which has **** indicating that it is set.
As an end user, it is beneficial to be able to clear up the “noise” in CDF when searching for data. It would be beneficial to have filtering capable of selecting more than one item of a sub-type for better visibility.
The idea here iswhen we have a checklist item with a tag and a value to input, and we have a live timeseries for that tag, why not prefill that value in the checklist item, showing the at any one time existing value. Then when you check off the item, you fix the value. Also show the delay as we do on the trends widget.This would involve selecting the timeseries you want displayed when setting up the template/checklist. Thoughts?
As a developer, I want to search for resources, so that the SME can access relevant equipments.The current search functionality in CDF is at a bare minimum, and getting the SME to the correct equipment is cumbersome and requires significant complexity in the client. This feature has medium priority at the App development team at Statnett.
When we access InFiield, all the asset configurations are available to every account who can access the project. It would be better if there is some controlling option available.
In many cases the description field will contain text that exceeds the maximum length of assets/events etc. Any increase will be helpful, now we have to truncate the field.
When completing an operator round in Cognite Infield, the status of the round should be able to preselect ok/not ok based on the values provided. Currently, the operations team needs to input the value from the reading and then manually select if that round reading is ok or not ok. The acceptable ranges are provided and listed in infield, but the current set up of the system is causing operations teams to interact with each individual reading twice: once to input the entry and a second time to classify the entry. This double entry is a barrier to adoption as it is requiring additional steps from the operations team. Additionally, due to the location of the radio button being at the top left of the title and not close to the text field for data entry creates an additional likelihood that the field will be missed. Furthermore, the lack of the ok/not ok will cause the reports to have to be manually verified by those who are utilizing them, to quickly validate operation status. This current solution does not provide much improvement over the current paper analysis of digital rounds.
This is a request for Cognite to make all of their applications Proxy Aware, allowing enterprise organizations to specify a proxy that will be used for all traffic.
In infield, there should be a button where we could request missing Cognite resources, such as connected timeseries, Document/document-type (Files) and assets close by in the hirearchy. Such as this tag is missing its P&ID or instrument loop diagram. Such that the contextualization algorithms can prioritize better. As well as beeing able to manually set a resource relevant for the asset we are on.
CDF Templates currently does not support geospatial, however this would be a very natural integration as Geospatial is reaching general availability.In the case of the Ocean Data Platform - we would like to be able track data from moving equipment, for example a floating sensor called an Argo Float that floats around in the ocean collecting temperature and other interesting measurements. The measurement series could be expressed as a time series, which then could be tied to geospatial locations.
Have arrow buttons where we can jump backwards and forwards in time. so say 2day span is selected. but have a button where this jumps back 2days or forward.
Dataset Awareness · Issue #173 · cognitedata/cognite-replicator (github.com) We have discovered that when using Cognite Replicator, our source Project has dataset id's set, but in the target Project all dataset id's are null. Please add support for replicating datasets and setting dataset id's on all entities to the replicator. The workaround we will be operating on in the meantime is to run a script afterward to copy the Datasets and set the dataset id's. Add Support For Mapping of Annotations · Issue #174 · cognitedata/cognite-replicator (github.com) Annotations are stored in Cognite as events of type cognite_annotation. There are sometimes id values in metadata fields CDF_ANNOTATION_resource_id and CDF_ANNOTATION_file_id that we have seen. We depend on these id's being correct to show the list of files applicable to an asset or other entities. When these events are being replicated to the target project, the id's are not being updated with the target id. Please add support for contextualization annotations in the replicator. Thanks!
It would be nice to insert additional default color pallet, based on the colors the company uses, as the first couple of default colors. and not just the default #RGB colors. just a place to push inn a list of HEX colors, and this then becomes the default color sequence for the user or the projects charts instance. But the color pallet should be changeable pr project basis, and that you could also have a custom color pallet aswell, based on user prefrernce. Additionally if we could also get a alpha / transparency factor aswell, that would be very nice :)
Cognite Functions are looking like a great solution to filling some of the gaps to what the CDF API is able to provide, allowing us to effectively extend the API with custom aggregations not possible with the limitations of Synthetic Time Series as well as alleviate the need for application vendors to run more complex business logic in their own backend service layer.Currently the native language during the Cognite Functions preview is Python. As Cognite Functions moves towards being production-ready I propose the next language/ecosystem that official support be added for is .NET 6. Our company has quite a lot of IP written in a .NET backend and it would be nice to be able to leverage Cognite Functions to port this over and quickly swap out our queries to our Azure SQL instance over to where data will be persisted in CDF.
Hi,When reviewing hours and days of high-sampling data the peaks are lost. But the high and low values are registered. It would be beneficial to “go to” the specific value shown, or at least have a time-reference for the peak - so I can zoom in and find the value in the graph.
The first line of the readme in cognitedata/cognite-sdk-dotnet: .NET SDK for Cognite Data Fusion (CDF) (github.com) is:Under development, not recommended for production use cases We are currently using this library in production, but we are having to add our own support for some features that are natively built into the Python SDK:Mocking/Testability Concurrency and connection pooling More mature data classes/SDK “glue”Please devote time and effort towards making this library production ready and officially supported. Thank you!
I would like the ability to ‘zoom’ to an area within remote from a hotlink within an external web application. e.g. link directly to the area in Remote from Maximo pertaining to a specific asset. I would also like the ability to embed a tool like Remote within a web application. Perhaps ‘Remote Web’ would be a good product...
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
