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!
I’d like the ability to rename files. I do not care if it takes a long time to complete or even if I need to replace the internal CDF ID. I just need some feature or option that will allow me to rename the file. Sometimes, data pipelines require us to put files into cdf before we can craft a useful name, and having to write extra work-arounds seems silly, put that burden on CDF!
We use Synthetic Time Series for as many things as we can to avoid using the trouble of re-indexing and interpolating in pandas.However, CDF Synthetic Time Series can’t do any basic logical operations, comparison operations or lag operations. For instance, if I want a time series that gives me 1 when my TS values is between an LCL and a UCL and 0 otherwise. In pandas, this is simple:1 if pd.between(x, LCL, UCL) else 0but since CDF STS doesn’t support if, and, not, >, < etc, so this doesn’t work.Another use-case was when I needed the moving average for the last hour. I had to make a time series and manage it’s creation, DM entry etc when I would have preferred to use an STS since the only use of that calculation was as an intermediate step. The map command in CDF STS looked promising but it doesn’t work without a string input. I’d like STS to support:if() and() or() not() lag() lead() movingAverage() movingSum() abs()
Currently, the Disciplines are attached to the application and if one specific site needs to add a new discipline or edit an existing one, this will reflect in all the other locations. The ideal is to have disciplines management by location. Similar to what was built for Observations.
We are running into merge conflicts when multiple teams are adding to features that touch the same files. An example, two teams working on different modules might need to both scaffold permissions in the same user groups, but deploy at different times. It would be really helpful if when defining a CDF TK Module, we could have different configurations defined for the same resource, but spread across different modules so that if one team needed to add dataset permissions to a common persona, they could do so within the module and that module would not interfere or conflict with another module adding to the same common persona. Similar to how in CSS if you have a base style, and apply styles overtop, they are added / overwritten.
Hi, Looking at the createGroups api doc I couldn’t find information on what the differeent Acl’s do. What, for instance, does the typesAcl do?Btw, I really appreciate the Feature capabilities list with examples - a lot of this info could be found there (but not typesAcl). It would be really useful to have a list on what each individual Acl does :)
We would be highly interested in the user token refresh settings becoming configurable by customers. Today users manually login (via mobile typing) to the Cognite tools much more frequently than other tools they are using (many are at 30 days refresh). This enhancement would allow each customer to configure these settings based on their security posture. Current token lifetimes are not configurable and limit us to a maximum of 26 hours if a user has not interacted with the tool, regardless of our internal re-fresh rate.We see the ability to extend the times on these settings critical to the long-term user experience of working with Infield and other Cognite tools. @Martin Miller @ryanbooker @Andrew Montgomery
When viewing time series data in Infield, the timestamp is in dd/MM format, but in Japan, the MM/dd format is more common, making it difficult to intuitively grasp the date. Therefore, could it be changed to a format like Mar 1, similar to Charts? This would make it easier for us to understand.
While using Canvas, I want to create work packages with standardized symbols for oil and gas, similar to a library including gate valves, globe valves, control valves, needle valves and more. The PDF editor I currently use allows me to add custom symbols, this could be an option. BlueBeam (REVU20 Extreme) allows me to customize them myself or add them to my toolbox (google a library of symbols to add). Another feature could be to have customizable text boxes that can be added similar to a sticker and edit the contents per the package.
Critical for being able to use Maintain and Infield.
On behalf of Celanese InField super users:I would like the ability to group and categorize my templates based on type. As we continue to digitize our checklists, the list of templates can become very long. This then leads to constant scrolling in InField to find the template that I need. Given that our checklists range from different types such as “Reading Sheets” or “EHSA Checklists”, it would be great if I could group these in a similar functionality that you see in the “Archived templates” tab (see below). This would make template navigation and management much easier.
Workflow Failures Require an Alerting MechanismScenario:Business Users find Incorrect Data Data team rallies to investigate Investigation finds CDF Workflows have been failing subsequently for numerous occurrences, with failing transformations unable to create new assets along with data models being unable to be updated. In order for us to rely on these mechanisms, we must have a mechanism that gives us awareness ahead of the business reporting a data quality problem that is resulting from a processing failure. Without this, trust degrades with each incident. It was determined that we hit the Instance Limit due to Data Model Spaces in this case.It’s not unreasonable for these things to occur, but what is unreasonable is for silent failures to continue and data to skew and business to be the alerting mechanism, here. Within an enterprise that staffs a dedicated data team, the most important thing is maintaining trust in the data regardless of the tooling, and we cannot provide that guarantee with Cognite are our platform today without more proactive alerting mechanisms.
This product idea has a few parts to it that can be separated into different releases. The main focus would be to have a task centric form where we can select the asset and use the same checklist on it. The second focus is to have conditional customer response triggers based on responses provided. The third is to leverage AI to create a summary of the checklist (or parts of the checklist) in a standardized format that meets a customer’s needs. The main value of this is accelerated time to complete tasks and generate reports (less time writing) with tangential value towards analytics generated behind the responses made back into CDF’s contextualization engine. The task should end up residing with the asset selected and be used for the purpose of closing out a required inspection (PDF) back into that system or automatically passed through to it. As an inspector, I would like to be able to complete a generic task similar to this previous request (linked below) but with the addition of custom conditional response requirements that would trigger a required action including taking a photo or describing the damage in greater detail. GPS location functionality (tell the app where you are located) should also be logged to build out 3D views with lon/lat data when it is not yet populated. The checklist would be able to export to a PDF when completed to be logged into my inspection data management system and also store the data in a way that I can run analytics on all inspections completed with that checklist (or multiple checklists with similar formatting). I would also like the checklist to auto-generate AI drafted responses crafted to an initial prompts set up with the set-up of the checklist to accelerate my report writing time so I can spend more time inspecting and less time transferring insights from my paper checklist to the computer. The responses should be tailored to specific checklist items that are linked to that section and any prompt created to support it. The value that this provides includes the time savings from completing the inspection and automated report writing in addition to the analytics and insights gained to recommend focusing more time on certain equipment or inspections that show higher hit-rates. Future functionality could include linking events that are planned from the inspections data management system into the task (Event ID below). Also the ability to create a work notification with this task as a PDF linked to it automatically generated (based on deficiencies found). Another feature would be to have ‘workflows’ where a task flows from one-person to the next with ‘hold-points’ such as a final reviewer on the inspection before it is complete. Example Task: Pressure vessel external visual inspection checklist (Inspection Task 1.1)Event ID: (link this to an event from the inspection data management system or manually enter)Date: Auto populatedName of vessel: (select from asset hierarchy, auto restrict if created with a feature to a specific asset type or unit)Location: (3D configuration - get lon/lat data)Inspection Details: - Is the name tag present: (Y/N) - Is corrosion (pitting) greater than 0.25” present (Y/N) - If a user selects (Y), prompt to take a photo and provide a description [each option should be able to be added independently (photo vs. description or both)] - more tasks as needed.Summary: - Create a paragraph that is consistent between all reports of this type with deficiencies noted Signature: Sign with finger or mouseName: MattAPI Certification Number: User enter
I have created a Rest extractor through cognite UI and have connected it to a source successfully. Now when i am creating a job i have to pass the endpoint containing namespace id and stream id. Problem is that i want to pass a list of stream ids at once and my extractor should loop through it and add to endpoint dynamically and bring in data rather than creating different jobs for different stream ids one by one.
i would like to propose an enhancement for Cognite 3D to improve user experience when navigating large industrial models. The feature would enable automatic asset contextualization based on mouse hover or camera movement, eliminating the need for users to manually search for assets.Proposed Feature Details:Automatic Asset Name Display: Assets that have been mapped to the 3D model should automatically appear when hovered over or brought into view. Real-Time Contextualization: When the user moves the camera, relevant assets should be dynamically identified and displayed. Enhanced Navigation: This feature will improve efficiency by helping users quickly locate assets without searching manually.Use Case & Benefits:Engineers and operators can easily identify assets while navigating 3D environments. Reduces search time for contextualized assets, improving workflow efficiency. Creates a more intuitive and interactive 3D visualization experience.
Hi Team,Below is a requirement to increase user experience and performance while using transformations.Current problem: As a data engineer, I do not have visibility of how many transformations are scheduled to run at a particular time period.As a result, we just rely on manual check or intuition at what time we must schedule our transformations to not hit the concurrency limit or result in increased load on the cdf instance.Proposed idea: A schedule heatmap between time of day against the count would help in this regard. The time should be divided into a group like 10-15 minutes to analyze how many transformations are scheduled within that time period. The count should also consider the repetitions based on the cron expression passed.Note: This can be extended to functions and data workflows as well@Aditya Kotiyal @Jørgen Lund
Cognite charts do not have option to delete multiple tags at once (multi-select and delete).Similarly, we can't add all (or multiple) tags from assets at once, need to manually click on each tag to add it in charts.
The current selection of the target data model when creating in a transformation is sort of a lazy load:Only these three data models are available when dropping down. There are dozens of data models in the project However, as the project grows, the loading of the data models can take too long, since it’s very possible to exist dozens of data models, and it loads the data models one by one. Also if you close the pop up it will start over. I suspect this is because it’s fetching all the information about the data models - all versions and views available - to fill the other options in other fields. And that could be too much to load all at once. The proposal is to fetch all data models at once, but only their names. And then once the data model is selected, fetch the rest of the information from that data model only. This way we can have a more responsive UI when selecting these and reducing the amount of unecessary data we are fetching.
This Cognite Hub Post outlines a workflow where development is done locally with the repository and then synchronized with CDF. Here at Celanese’s CDP (Citizen Developer Program) we have an different process/dynamic. Most of our citizens do not have access to local developer tools like VSCode, etc. Rendering the mentioned approach problematic to be applied in our use cases. A Git-based solution, similar to what Azure ML Studio: Git integration - Azure Machine Learning | Microsoft Learn offer, would ensure a more inclusive version control process. Azure ML Studio allow users to specify their Git repository details—such as the URL, branch, or even a specific commit—to connect their code base directly to the platform. Additionally, the integration could capture Git metadata (like commit hashes and messages) and associate it with each version, providing clear traceability and making it easier to track which code changes correspond to specific deployments.The CDF would benefit from this by adopting a structured Git-based workflow. The repository would be organized with two main branches: one dedicated to versioning, where each commit represents a stable version, and another serving as a work-in-progress branch for ongoing development. Once the work-in-progress branch reaches completion, it would be merged into the main versioning branch, creating a new stable release. A built-in selector could allow users to easily switch between different versions from the main branch or continue working on the latest updates in the work-in-progress branch, ensuring flexibility and control over the development process.With Git integration, multiple developers could collaborate efficiently, even without local development environments. The platform would maintain a consistent history of code changes, enabling better debugging and rollback capabilities while ensuring a seamless and transparent development lifecycle.
In behalf of Celanese Bishop users: We have several checklists that are based on existing PI tags. The operators check the current value using PI or the DCS and write in down on a checklist to certify that they verified it and did not find any problems.This type of checklist would be a lot easier for the user if Infield showed the latest value of the timeseries that is related to the PI Tag. They could verify the value only using Infield, instead of looking in a separate system (PI or DCS).We propose to be able to select the timeseries related to the task, and Infield would show the latest value. Then the operator could proceed with the task status as “Ok” or “Not Ok”, depending on their analyses at the moment.
A user (mark_wrzyszczynski@oxy.com) from Oxy requested for fuzzy search support in InField. Currently, when searching for checklists in InField, it appears that the search functionality only supports matches from the beginning of the string. It was observed that the Templates Search does not seem to support proper fuzzy search functionality.For example, when searching for a template named 'Testwww'. While the search results are displayed when using the keyword 'Test', no results appear when searching with 'www'. The assumption is that the current search implementation may not be handling partial matches or keywords that are not at the start of the template name.The requirement would be to enable partial/fuzzy search in InField for Checklist/Template name searches.
Hi,I am importing work orders from an external CMMS and would like to add a link to a metadata field, so the user could access the CMMS work order directly from that event that represents it. When I add a URL it remains as string, but was wondering if I could make it a clickable link and with a friendly text. Is it possible?
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.
