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
Hello,IntroductionI have been working with Cognite Vision app, and I’d like to share my experience and suggest improvements that could be helpful. ProblemWith the assistance of the vision.extract (TextDetection) feature, I have developed a script to aid in the detection of asset tags. This script offers the following features: it matches the detected text with existing assets based on contextualization rules, and predicts the asset based on the extracted text. This functionality becomes particularly helpful when the extracted text is not 100% accurate due to pixelation or if a letter or number is not clearly visible in the image. The script suggests a number of assets based on the extracted text, providing confidence scores to assist the user in selecting the correct asset. FlowThe script will execute on all images, generating a set of images.AssetLink annotations per image if any suggestions are found. Subsequently, the user will access the Vision UI to review and approve the correct annotation from the provided suggestions. SuggestionsAnnotation Filter: Enhance the filter functionality by incorporating additional fields, such as creating_app, creating_app_version, or creating_user. This enhancement aims to facilitate image list filtering, enabling users to display only those images with annotations having the status suggested and created by the asset tag prediction script. Breadcrumbs: Currently, the breadcrumbs are dysfunctional when an image is opened. It is essential to ensure that users can easily navigate back to the images list with the preselected filters intact Navigation: Occasionally, to accurately select the predicted asset, it becomes necessary to open the 360 view and examine adjacent assets for clear identification. Including a button that opens the 360 view with the camera focused on the selected image could enhance user navigation. Alternatively, providing the option to search for the image by its ID within the 360 view would also be beneficial. Reviewing Annotations: In cases where there are multiple predictions, and a user approves one, it would be beneficial to display a popup message asking, 'Do you want to reject the other annotations that appeared in the same location?' This feature is particularly helpful when, for instance, there are 7 suggested annotations with the exact bounding box location. By approving one, the user can efficiently manage the process by simultaneously rejecting the remaining 6 suggestions. Thank you for considering these suggestions. Your attention to these enhancements will contribute to a more streamlined and efficient workflow. I look forward to any further discussions or implementations that may arise.
We want to use the Cognite File Extractor to load files from Sharepoint to Cognite.In working with support it appears that currently the File Extractor only supports reading from non-Teams Sharepoint sites.
Hi, I am not sure if this is already on your roadmap, however I wanted to share an idea that could potentially improve the current data management processes in CDF. Our team utilizes for some data integrations a single extractor to fetch data that multiple datasets uses. This is done to minimize the load on our source enterprise databases, and reduce the maintenance of having a single larger extraction rather than many smaller extractions. This approach, presents a challenge in monitoring and lineage visibility, as each extraction can only be linked to only one dataset.The core of the proposal is to consider a "many-to-many" relationship between Extraction Pipelines and Datasets. This would allow us to maintain our integrations easier while significantly improving lineage visibility for all related datasets. Implementing such a feature could provide a clearer overview of data dependencies, that I believe other firms than AkerBP would also find useful.
As a user of InField I need a process of handling out of tolerance observations. I want to be informed that the there is an out of tolerance observation, and I want to be able to alert others.
Originally this was filled out as a bug, but the support team recommended to fill out as a product idea. After I change the name of a synthetic tag in InField 2.0, I still only see the external ID in the first edit view. I have to click on the pencil icon to edit the tag, and then I will be able to see what the new name I changed it to, is.The name that shows up in the first edit task view should show as the updated tag, rather than the external ID. Otherwise, what is the point of having the ability to change the name? If a user needs to search for a tag in CDF or in InField, do they need to know the updated name or external ID?First image: external ID shows, despite the changed nameSecond image: updated name
Infield Users (especially approvers and team leaders) want to see date/time stamp information for completed checklists with Infield 2.0. With Infield 1.0 the released checklists have date attached in the file name, which was helpful. Can we add this detail for Infield 2.0 too?
On behalf of Celanese InField 2.0 super users:Can the threshold for triggering offline mode be adjusted? Based on this Cognite Hub posting, it is understood that offline mode is only triggered when there is a complete loss of connection. Currently, users are experiencing issues with offline mode triggering during instances of slow/poor connectivity. We are noticing with the Zebra devices specifically, that they tend to hold on to a connection signal for as long as they can regardless of the strength of the signal. This is causing instances where the connection becomes so poor that the users are unable to capture their data and, in some cases, lose their data during a signal transition phase by which the devices switch to a stronger signal connection. The devices are never truly in a “no connectivity” state and therefore Infield never initiates offline mode.This is currently a high priority issue and is causing two units at the site to consider forcing the devices into airplane mode and working in InField offline mode by default. The users would then only rely on the wifi connection in the control rooms to upload their data once their round is complete. @Kristoffer Knudsen
The date is not displayed in the checklist overview. It would be an advantage if the user could configure the information that is displayed themselves.
It would be conveniant to have a way to request Python pakcages to be installed in the Jupyter environment in CDF.Plotly, for instance, is not part of the default installed packages. I could still use it by using micropip:Screenshot from Jupyter Notebook in CDF.But it seems inconveniant to do this everytime, especially for popular packages like Plotly.
Good morningClient is asking to perform a feature request so the extractor configuration files are currently stores as encrypted files on the source systems where the extractor are run (on prem).This is because:Yaml files are stored locally as clear text Even using ENV-VARS to ‘hide’ the actual values in the YAML files, if someone has access to the system, it can take a look at this ENV variables anyway. THe KeyVault functionality has also a failure as the KeyVault config as well shall be exposed, having a vuelnerability anyway to access ALL keyvault stored params.If this is planned to be, client wants to know an estimated date of the release of this new functionality, and if this is not considered to be imlemented, please to provide a justification. Client is Sierracol (Colombia) and project is CDF deployment. Thank you, Sebastian Wolter
Using the Infield with the small screen of mobile devices can be a challenge with current layout of the Infield screen. The text are small and navigating left + right and up + down can be difficult with narrow width of the Checklists and Assets Explorer Section. To begin with, Infield tries to put 3 section of information (All Checklists, Checklists, Assets Explorer) into the screen of mobile device the same way for potrait and landscape mode. While in Landcape mode, the adaptation seems ok but in Potrait mode, with example a 6 inch display, the assets explore section is only partially displayed on the screen. It is not possible to navigate left or right to see the rest of the Assets explore section because the sections are fixed. This arrangement also made the fonts smaller as the sections are squeezed and scrolling up and down difficult. There are 2 methods to improve the UI for Potrait mode for the field people, 1) To arrange the sections in a vertical manner instead of horizontal. Disadvantage of this is there will be a lot of scrolling up and down to get from 1 section to another. 2) To separate each section to a tab (refer to-be worksheet). This enlarges the font size, increases the width of each section and improves the scrolling and ease of data entry for the field workers.Infield should be intelligent enough to identify between potrait mode and landscape mode and change the UI according to the display mode as field users can use mobile devices and also tablets in either modes.
Ability to sort checklists and tasks based on certain criteria configurable by the enduser.
There must be an easier and direct way to change the location than via the account settings. Needed for users who work for several units or provide shared services. The possibility of assigning several locations at the same time would also be very useful.
Infield 2.0: Adjusting the width of columns/areas for templates & checklists. Right now available in the “overview” and the "observation” only.
On behalf of Celanese super users: Would like customization options after pulling in a Chart or document kind of like how you can in PI
On behalf of Celanese super users:Would like for there to be options pulling up when right clicking on a blank canvas, just like how options pull up if you right click on a chart.
On behalf of Celanese super users: Would like to have ability to use common shortcut keys. Canvas doesn’t seem to recognize “CTRL Z” / “CTRLC” / “CTRLV”
PI drops some datapoints due to poor quality. Ideally this would be written to CDF with some sort of indication on the quality of the data.
As I user, I would like to have an adjustable document title for the PDF export instead of the Plan title.
Specific colors instead of multiple shades of grey for hierarchy levels for easier readability in long reports in PDF reports. Current status (shades of grey) vs idea (color coding)
As a user, I want the possibility to create public dashboards in Grafana that displays data from the Cognite datasources/CDF plugin. This will enable me to share my dashboards publicly, to be used for marketing purpose, sales etc.
For the reccurency tasks of the Checklists that have a longe planned time, it’s important to have a option to define a days until due. Users intent to create checklists only one time and it needs to have all defined before that. The Days Until Due field will help them to define, for a Monthly task for example, the number of days to an operator execute a task without making any harm to the operation. Also, it’s an important field to use as a reference in a data perspective to understand if the operators are executing their duties in the correct time.
Hi,I'm reaching out to suggest an enhancement to the CDF's dataset overview functionality that could significantly improve user experience and efficiency.Currently, while reviewing a dataset in the CDF platform, users can see the data owner but not the integration owner or the specific developer/team responsible for the dataset's integration. This gap in the documentation requires users to spend considerable time identifying the individual or team who developed the pipeline and is accountable for its integration.To address this challenge and enhance our workflow, I propose adding an "Integration Owner" field to the summary box within the dataset's overview tab. This addition would provide a clear, immediate reference to the responsible party, streamlining communication and troubleshooting processes.
As a user of Canvas I want more types of equipment symbols, etc.
On behalf of Celanese super users:Would like ability to adjust size horizontally and vertically rather than just on corners of a document.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
