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
When a new user logs into InField 2.0 for the first time, their default location is set to the very first location for the organization in the dropdown. This should instead be set to the proper site location that the user’s access permissions have them in. For example, someone from the Shelby site should see “SH” or something instead of “AT”.
On behalf of Celanese InField super users: When releasing a checklist in InField 2.0, it is not immediately clear what date the checklist had been opened. In InField 1.0, the release date was made part of the checklist title and made it easier to distinguish between other similar checklists that had been released. Can this feature be brought back into 2.0? Or at least make the release date easier to distinguish? @Kristoffer Knudsen
As business product owner I would like to have a possibility for deep links (hyperlink that brings me directly (without any user interaction) to a floc in the 3D model) into remoteso that I am able to generate and store deep links in my other systems e.g. Riskpoint where the users are able to immediately switch over to remote. so that I am able to give users a one click experience to enter the application and remove any hurdles
Are you considering providing your Industrial Canvas for teams to collaborate directly via Microsoft Teams? Apps in Microsoft Teams
Hi, When the data is in CDF RAW then we can use is_new function with lastUpdatedTime in transformation and this works fine but how can we use that function for data coming from FDM model. Let’s say, from CDF RAW we are populating the data in FDM domain model and we are considering only incremental data with is_new function in transformations.This is the domain model (space: dm):type Entity @view(space: "dm", version: "1"){name:String} This is transformation query to populate above Entity type:select distinct concat('wellbore:',WellUWI) as externalId, WellName as name, FROM `db1`.`wellbores`where is_new( "db1:wellbores", lastUpdatedTime )This is good and we can see only incremental data from CDF RAW in the domain model. Now this is the solution model (sol_model):type WELLBORE{name:String }This is transformation query to populate above WELLBORE type ( I can directly map the name of WELLBORE of solution model to ENTITY of domain model but for this example I am ignoring it to understand is_new() function):select entity_table.externalId as externalId, entity_table.name as name FROM cdf_nodes('dm','Entity','1') as entity_tablewhere is_new( "dm:entity", entity_table.lastUpdatedTime )Here, I can’t use lastUpdatedTime because even though it is internal attribute of Entity type, it is not possible to get it in the result of cdf_nodes . The cdf_nodes doesn’t give us internal attributes. How can we make sure, the solution model transformations only consider the incremental data coming from domain model? Am I missing anything here?
There is lacking a possibility to filter better in charts. With millions of timeseries it is needed for us to filter based on datasets, assets, and so on.Is this something that is on the roadmap or could be looked into?
In use cases where CDF is being rolled out with multiple data sources for a number of operating locations, there is a need for better extractor health and diagnostics monitoring for e.g. like a heat map. Having the functionality where admin/support personnel for different sites can quickly identify the root cause of data issues in CDF would be of benefit. Users should have a GUI display in CDF, where they are able to quickly identify a data issue, drill down and generate the list of extractor error messages and alerts, in a chronological order based on user selected/configurable choices of operating sites, set of data sources/extractors etc. etc.
Hi. We would like our SMEs/Data stewards/Data owners to be able to update fields on CDF Resources directly in the Fusion UI. Say, assets and time series missing description, or with missing/erroneous metadata etc.
Dear Team,I am reaching out to provide feedback and suggest enhancements for the new Cognite subscription API, particularly concerning its use in continuous data streaming applications.Challenge with Time Series Subscriptions API:We are currently utilizing your Time series subscription API in a project that requires continuous data streaming. However, the API’s synchronous nature has presented us with significant challenges. The main issue is the inherent latency in data processing, which is exacerbated by the need to implement a sleep mechanism with a fixed delay. Determining the optimal sleep duration is challenging; too short a delay leads to frequent polling, while a longer delay results in data lag.Benefits of Asynchronous Streaming:Implementing asynchronous functionality in the API would greatly alleviate these issues. Asynchronous methods would enable more efficient and responsive data handling, reducing latency and providing a smoother data stream. This is particularly crucial in applications where timely data processing and analysis are vital.Suggestions for Improvement:We suggest the addition of asynchronous streaming capabilities to the API, such as non-blocking data fetches or real-time push mechanisms. This improvement would align with industry standards and significantly enhance the API's utility for various applications, especially those requiring real-time data processing.Best regards,Oussama
Content:In sequences, we see that sometimes some data point in the sequence is updated but the updated time in the metadata stays the same. It means that if we query based on the latest updated time we might miss some new data points in the sequence. Could the updated time relate to when new data points are added in the sequence?
On behalf of the learning facilitator for the VAM unit:Can the capability to roll-back a previously approved checklists be added as a feature for admins in InField? The reasoning behind this is recently a checklist was accidently approved by one of my team captains before being completed and there was no way to go back and complete the remaining checklist items without opening a new checklist for that shift.
The icons on the checklists don't necessarily match the shift that the checklist is meant for. For example, there are checklists that release at 2am but are meant to be available for when the day shift comes on. The checklists that release at 2pm are meant for night shift. In this case, the sun icon does not make sense for the 2pm checklist, and the would instead make more sense for the 2am checklist. Same thing with the moon icon for 2am - it would make more sense for 2pm release since it is meant for the night shift. The template creator could designate the proper icon to describe the shift to complete the checklist.
With a limit on the number of access groups within an environment and the implementation behind-the-scenes of soft versus hard deletes, it would be beneficial to have an SDK method for updating the permissions or scope of an access group that already exists. Presently, we have to pull down the old-group, duplicate its permissions and scopes for the modified-group, upload the modified-group, delete the old-group, and rename the modified-group to the name of the old-group. With a global project with over 30+ sites, it’s easy to see how we can hit that access group limit within in an environment.
We would like to have a filter option for “Retrieve rows from a table” that makes it possible to fetch certain rows instead of every row in the RAW table. The filter should be able to use any column which contains a certain value and return every row containing this value.
Content:As a user of data explorer I often find myself exploring multiple types of content at the same time and it would be helpful to be able to open the Asset tab in a tab in the browser. Would speed up my exploration process instead of opening another tab with Data Explorer and navigating to Asset from there.
Content:Are there any best practices on how to use CDF available somewhere? Transformation are for example quite complex and it would be support useful to have more guidance in how to create them properly to get the best possible result
I am working on the config.yaml configuration of Documentum Extractor. But I am facing an issue while configuring the dataset-ext-id parameter in config.yaml as this parameter is not supported in the Documentum Extractor yaml. Can we get support for dataset-ext-id parameter as well?Caused by: com.fasterxml.jackson.databind.exc.UnrecognizedPropertyException: Unrecognized field "dataset-ext-id" (class com.cognite.connector.dctm.config.CdfConfig), not marked as ignorable (10 known properties: "idp-authentication", "external-id-prefix", "host", "project", "source", "api-key-env", "data-set-id", "api-key", "security-categories", "extraction-pipeline"])
Today the annotations used on PDFs in CDF only point to one resource. I.e. in a P&ID when clicking on a document annotation it assumes there is a unique object that represents that annotation. However, in reality there is a one to many relationship. Examples from ExxonMobil:P&IDs have the following structure, all are considered the latest revision which share the same short name used when being references in other documents, hence should be offered to the user as options for which document to jump to. E.g. FM-1234 in a P&ID should be linked to all the below: FM-1234 Revision X FM-1234 Revision X Markup 1 FM-1234 Revision X Markup 2 FM-1234 Revision X Markup N Isometric diagrams represent actual piping drawn at scale. Due to this, they can span several documents while still referenced in the P&ID with a common name. E.g. HT-1234 should link to all the below. HT-1234 section 1 HT-1234 section 2 HT-1234 section 3 Time series tags in a diagram are referenced with the core tag name, e.g. PI-1234, but in the control system it is expanded up to have aggregated information or properties. These are often added as a post fix to the name used in the diagram. E.g. PI-1234 should link to all the below. PI-1234.HH PI-1234.LL PI-1234.Offset
In InField 1.0, synthetic tags would automatically have all letters lowercased.In InField 2.0, the lowercase and uppercase lettering seems to matter. Users would prefer it all be lowercased for them to avoid discrepancies in naming convention usage.
In InField 1.0, synthetic tags would automatically add underscores when users would put a space. This functionality is no longer present for InField 2.0 but the end users are used to it at this point, and it looks odd to them when there are spaces when searching for tag names.
On behalf of Celanese Clear Lake InField super users:As a user, I have no way of knowing which synthetic tags are existing outside of my checklist/template items without having to search through CDF. This is a problem if we decide to rework our checklist/template items and create new tag names without realizing that there may be an existing tag name for that line item/asset with linked historical data.I would like to see some functionality that lets me see/search existing synthetic tags for my unit within my template. This could be a simple dropdown when adding an item to a checklist/template. This will allow users to maintain continuity and retain historical data linked to specific tags where a new tag does not need to be created.
On behalf of a DEL (Daily Execution Lead) at CelaneseAs a DEL, I want changes made to the template to reflect immediately to the checklist, this functionality will help my team adapt quickly to our agile environmentWhen creating an interval based checklist template in InField, if you wish to make any changes to that template after it has already been opened/released, the following warning message is given: " Existing checklists will not be updated if changes are made to the template. These changes will be included in the checklist created in the first calendar week following the template update"The user is unable to use their updated templates until the next calendar week."
The ability to filter by labels in the Explore screen would be helpful, We filter data using labels for the purpose of contextualization, so it makes sense to have labels available as a common filter to filter Assets, Files, etc. in Explore.
DP3D is one of the main asset virtualization application. Many of our customers in Middle East are using it. It is important to be able to connect to it.
On behalf of Celanese InField super users:As an InField user, I would like the ability to customize the layout of the asset overview page. Specifically, for some units/sites there may not be a 3D model available. It would be great to have the ability to disable that module and utilize the extra real-estate to surface more important data.@Kristoffer Knudsen
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
