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
Ability to print out checklists out of Infield 2.0.
When Exploring data the logical first input is the Data set. As of todays solution, the filters applied afterwards, are not confined by the Data Set selected initially, e.g. “Assets”.Suggest to include/modify solution in order to have the filtering functions applied afterwards taking the Data Set selected into account.
It is important that the operators are able to write back to SAP from the field during operator rounds or checklists.
Hi Team,On behalf of CNTXT, I am creating this FR; they reported that when using the metadata filter in CDF Explorer Files section, selecting two filtering conditions results in a list containing items that meet either condition, similar to OR logic.However, the requirement here is to filter the list to only contain items that satisfy both conditions simultaneously, similar to requiring all conditions to be met using AND logic. Currently this functionality is working based on the “OR” operation.
If I try to filter time-series with metadata (left panel in data explorer), there seems to be an “OR” logic. Wich means that if I filter on two metadata key-value pairs, I get results for all time-series that contain one (or both) of the metadata field. This makes it really hard to use metadata fields to narrow down my search in Data Explorer, because more chosen metadata fields means more time-series are shown.I would want to be able to filter with an “AND” logic, so I could narrow my search down more and more, when I select key-value pairs. For example:I select:timeSeriesCategory = “ProductionPlan” priceArea = “NO1”I want to see all results for production-plans for power plants in NO1, not all time-series that are in NO1 and all time series that are production plans.I don’t think this is possible yet.I do see why it can also be practical to be able to filter with “OR” logic, in cases where I select multiple values for a single key. For example:I select:priceArea = “NO1” priceArea = “NO2”Now I want to see all time series in either NO1 or NO2.With other words: when selecting multiple values for the same keys I want an “OR” logic, and when selecting mulitple keys, I want an “AND” logic.
As a functional planner I would like to copy a project with a set of activities as they will repeat for the next project such that I dont have to create the activities again and save timeToday the workaround is the functional planner exports and imports the activities again.
As a user, the current options for the column width adjustment are limited and this option would improve the functionality of the tool.
Direct tool\data bridge to bring CDF data into ARCGIS without data conversion.This could be API plugging into ESRI ArcGIS or bridge via for example FME (future manipulation engine) export from CDF via FME to SDE SQL geodatabase.Mainly we would like to be able to display CDF generated survey products outlines and attributes in GIS to help with sales. We could use this data in ArcGIS desktop but also integrate with data on our web maps and applications.
Can Cognite develop C# and C++ supported SDKs which includes functionality to handle OIDC authentication?Currently if end users of Seismic CDF want to use the SDK we are dependent on their software supporting Python. A lot of software dealing with seismic data is written in C# or C++ and having SDK supporting these languages would greatly increase the assimilability of the Seismic SDKs out of the box.Other programming languages that could be of interest is Java.
- Today to much information is cumbersome to visualize, when the information is easily available.- Annotated P&ID is a perfect example.- Assets are recognized on a document, but actually the assets are only the placeholder for the valuable information, like live data, metadata, events and all the other stuff we have in CDF. - Users are interested in being able to visualize this information on a technical workface instead of in a 3d model.- ITs a visualization based on context with regards to flow, P&Id, Electrics etc which can be automatically populated based on the underlaying contextualized information in CDF
On behalf of Celanese super users:We should have the ability to have multiple users edit inside a shared canvas. This would allow us to utilize canvas as a live workspace and is critical for any live troubleshooting or RCA working sessions. This should function similarly to a live document in SharePoint.
In InField 1.0, we could at least see the date when a given template was last edited and by whom it was edited by. (see attached picture). In InField 2.0, we lose this ability - it would be helpful to understand what the last change was and who made the change in order to follow up with that person and ask follow up questions.
On behalf of Celanese InField super users:I would like the ability to visualize/trend the previous value that was captured in a checklist within the task without having to use Charts/trend overview page. This will allow me to have visibility on downward trending items while executing a checklist and provide insight to items that may require escalation.
I was fixing a task in InField 2.0 by deleting the synthetic tag assigned. But then I wanted to see what the original tag chosen was. Unfortunately when I clicked “Cancel” at the bottom of the editing window of that task, and then I re-entered the task - the task had auto-saved and I couldn’t go back to what it had originally been. The auto-save is great - but what if I want to see prior edits for a given task?
One of our users from HESS reached out to Support with the below request. Currently the user can create an entity matching pipeline, but there's not way to schedule it to run and have to trigger it manually.This used to be possible, but seems to have been removed.Please bring this feature back as it's a core capability and differentiator that Cognite offers that they need to utilize to effectively contextualize their data.
Is there a way to delete the files from CDF if it has been deleted in the source using FileShare Extractor? # (Optional) Behavior when deleting files. # "soft" means that a metadata field will be added to the file if it is deleted in the source. # "hard" means that the file will be deleted from CDF. #delete-behavior: # mode: soft # key: "deleted" # OR #delete-behavior: # mode: hardThis concern was raised on behalf of neha.a.saini@accenture.com at CNTXT.
Hi! Our organization has strong desire for OpenID/OAuth2 authentication against the DB extractor. We are currently using SQL authentication, which is outdated.
Request: Enhance our SAP extractor by incorporating compatibility with SAP transaction codes. This integration is crucial for seamless communication between systems, allowing to execute specific SAP transactions directly through the extractor interface. . This feature will streamline processes, providing efficiency and convenience for obtaining data from SAP system.
Idea to develop an API-based extractor designed to facilitate seamless integration between external system APIs and Cognite. This extractor serves as a crucial link between diverse APIs and the Cognite platform, ensuring efficient data transfer and integration capabilities.Current approach is we go to the source system and custom configure the API’s of source system and Cognite API’s to integrated data. API Compatibility: - The extractor must support a wide range of APIs to accommodate various data sources and types, including RESTful, GraphQL, and other standard API protocols. - It should be adaptable to changes in API versions and structures, allowing for easy updates and maintenance.Extractor should have capability to send data to Cognite Raw/FDM/any specific target area within Cognite. Data Extraction and Transformation - The extractor should enable configurable data extraction parameters such as date ranges, filters, and pagination options to retrieve relevant information from source APIs. - Capability to call a transformation /function and pass inputs Scalability and Performance: - The solution must be scalable to handle large datasets and high-frequency data updates, ensuring optimal performance even under heavy loads.Support for Queuing mechanisms where the data can be queued and processed to CDF in the order - Support for asynchronous processing and parallel execution to enhance speed and efficiency in extracting and transferring data. Security and Authentication: - Robust authentication mechanisms, including API key management, OAuth support, and secure token handling, to ensure data security during extraction and transmission. - Compliance with industry-standard security protocols, such as TLS/SSL, to safeguard data integrity and confidentiality. Configurability and Customization: - Intuitive configuration options for users to set up and customize extraction parameters based on specific API and Cognite requirements. Monitoring and Reporting: - Integration with monitoring tools to track extraction performance, detect anomalies, and generate reports on data transfer activities. - Real-time alerts for system administrators to address issues promptly and ensure continuous data flow. By addressing these requirements, the API-based extractor will serve as a robust and versatile solution, facilitating smooth integration between APIs and the Cognite platform while meeting the diverse needs of users and maintaining high standards of security and performance."
In InField 1.0 process experts have the ability to open checklists from templates. In InField 2.0, process experts cannot even access the templates. The process experts should be able to access the templates in case their templates do not have time intervals and are on an "as needed" basis for opening checklists. Learning facilitators or team captains will need to open on-demand checklists on their desktop as a workaround.
On behalf of Celanese InField super users:Currently, InField only supports an itemized list view when creating templates. However, for Maintenance applications, I would like to see some flexibility in template formatting to allow support for tables (multiple columns and rows) similar to original Excel forms today. Given that maintenance checklists cover multiple inspection criteria per equipment, a list is not the ideal interface as the users would be required to scroll through a long list of items.
On behalf of Celanese InField super users:When building templates in InField 2.0, it has been discovered that there is currently a limit of 500 tasks that can be added to a template. Can this be increased? There are a few checklists in the unit where this limit is easily reached. The only workaround today is to separate the checklists into parts, which is not ideal.
On behalf of Celanese InField super users: I would like to see improved functionality for adding line items to an existing group or merging groups. Currently, I am unable to drag and drop a new item into an existing group. Instead I am required to select the item I want to add and an item within an existing group and merge the groups as a “new” group. However, when this is done, the new group is moved to the bottom of the checklist. It would be a smoother user experience to be able to add an item to a group directly and without the position of the group being moved.@Kristoffer Knudsen
I would like to please match the cognite tabs here to the right SAP fields. Can we include more tabs such as components, objects, cost, operations? We have the data coming but it needs to be organized in the black rectange. so in SAP, we have the following headers so Objects is where - we should have object list as below (not components which we are showing?) Next question: How do we tie a checklist to the work order? should that be on operations tab or should that be on Objects? Food for thoughthow do i automatically assign a checklist to the work order? can contextualization do that?
As Daily Execution Leader, when something is marked Not OK and in red, I would like my process experts (those doing shiftly rounds) to be required to enter in a comment to make sure the issue is communicated and visible to all. Make it so that it cannot be skipped without putting a comment.Feedback from the Daily Execution Leader @ VAM (Vinyl Acetate) Unit at Clear Lake going through onboarding now
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
