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
I think Charts need a feature for storing notes, thoughts, documentation, or other types of descriptive texts concerning the Chart. This would make it more self contained. For example, it would be useful to have a description of why certain tags have been added, what we aim to accomplish with this chart, which equation is used in the calculations, assumptions in the analysis, how to use the Chart, other related charts, etc. Regards,Anders Brakestad
When I added a trend from other tags, the trend was not saved in Recently selected time series and it’s lost when I reloaded.It would be great if it’s saved so that we can always see the other trend when I select the tag.
On behalf of a DEL (Daily Execution Lead).As a user, I want the custom states on the manual checklist to track towards the completion progress and mark as complete when all of the line items are completed.
Expectation: “I only need a few tags in this Chart, so I’ll just add everything in this one”Reality: The Chart grew to 30 TSs and I probably need to split it up into individual Charts.I would like the possibility of selecting a few TSs from the table, and populate a new Chart with the selected TSs. This should maintain the formatting, calculations, and axis views currently set. As a workaround I suppose I could duplicate the Chart and delete everything I don’t need, but this introduces unnecessary effort in cleaning up the new Chart. Regards,Anders Brakestad
The scroll “zoom” works very well, but on several occasions, I have missed the ability to simply select a window with the mouse, which then is zoomed in to. When looking for a particular time window this method simply just works, without all the scrolling and dragging to manipulate the view to my wish.
On behalf of Celanese Clear Lake R&D InField Super Users:When creating a manual checklist in InField, if you select a manually created state for a checklist item InField does not mark the checklist item as complete. However, if you select the default “Ok” state for the item this then marks the item as complete. Is this as designed? Checklist item marked with manually created stateChecklist item marked with default “Ok” state
Difficult to see between lines of items (sometimes they’re wearing darker safety glasses outside, and it’s hard to see in the sun)Create better visual delineation between line items for the Rounds? Increasing the font size for titles and/or increasing contrast between line items should help with this issue
Entering on behalf of Acid South Unit feedback, as users navigating in the checklists with headers - we love the collapse feature. It would be helpful as we work together on a checklists in the field to show progress of a section on the header/section to know if there is any remaining tasks in that section without having to scroll all the way through. Ask a shift captain, it would be help to collapse headers and see if there is any images, notes, or out of range at a glance per section instead of having to scroll at length to find out where / if there is anything of not to review.
As a production planner, I want a bid matrix that is easy to read, or at least not more complex than necessary. I have understood that the total matrix is supposed to be filtered for columns without any new information, but that is not always the case. I want filtering on the plant matrixes as well.
I just gained access to the DirectQuery early access so was trying to switch over from the PostgreSQL Gateway to the official DirectQuery solution. When experimenting with the types of queries I can include in my SaaS application code, I use Azure Data Studio to query Postgres. Through ADS, I always get an error with DirectQuery:cursor "b07f4a07-c9db-4d5d-9f7c-c9adb01abaf7" does not exist Even for simple queries like this:select "timestamp"from public.datapoint_aggregatesWHERE timeseries_external_id = '419b9b45-8e09-48a9-9912-08da820807fc'AND "timestamp" > '2022-08-23T00:00:00'AND "timestamp" < '2050-08-23T00:00:00'This is likely caused by something the client is doing because using this same login, I am able to run the example PowerBI queries.
I looked around in all the usual places and couldn’t figure out how to rename/re-externalid a transformation with the new UX. I went to the old and did it no problem and then switched back to the new UX.
I have noticed that the SDK now has a “wait” flag when triggering a transformation. This feature is practical when triggering from a integration tool where you wish to trigger something else when the transformation is done. The problem for me is that I only use the API, and the API does not support this feature as of now. Is there a plan to have this feature made available in the API soon as well?
We have a need to list all the features of a specific FeatureType through the geospatial FeatueAPI. There seems to be no list() method or equivalent endpoint to achieve this, excepting using the searchStream method with no filter.Would it be possible to provide such a thing?
It would be really helpful in Cognite Charts to incorporate DataSheet viewing quickly by right clicking a transmitter on the P&ID or from a Tag. In Charts, there is a P&ID view but if you can add DataSheet also, will be really helpful.
I have a use case here where i would like to take a value reading at 9am on a time series and then one at 4pm but then i want to subtract it and have that as a synthetic time series going forward. Can we do this in Charts?@Crystal Connor Richards @Eric Stein-Beldring @Philippe Bettler
When equipment is down, InField still requires the Operator to select N/A, and they could be down for many daysRecommend a way to allow the operator or management to mark the equipment as out of service for a set period of time or better, be aware of equipment being down from CDF a piece of equipment is down and gray it out on the round sheet
Feedback from customer:“Can log in be simplified further after «sign in with Microsoft»?Is there a need to choose CDF cluster when signing in? This is confusing. Can our project be default Project when signing in? This is confusing.Importance: Should have/nice to have.Context: When logging on inField for offshore workers.User story: As an offshore user of inField I would like for the app to “remember” my CDF cluster and project when signing in, so that I don’t have to look up the correct CDF cluster and Project each time I log on.Picture:Example of CDF cluster, similarly for project.
the file name of downloaded files is a bit non-intuitive string containing the External ID++ Could this be changed such that it is easier to figure out what it is. best would possibly be the concatenation of original-filename and file descriptions in the filename when it is downloaded, to the extent that is possible :) then the files downloaded is very intuitive for the downloadee in their downloads directory :)
CDF needs some serious help in searching and querying data. I asked about some simple reporting, like a query telling me how many pumps are in Acid South. To do this within CDF requires a pretty exhaustive knowledge of our metadata fields and what they mean. In this case, understanding that pumps would be found in the SAP data source, and that equipment class was held within the Catalog Profile metadata field, then having to know what numerical code from SAP for Cat Profile actually corresponded to pumps. It’s easier to do in SAP. Even once the list was created in CDF, there is no way to export it. You can look at it within CDF, but that’s it. For something like a bad actor report, Crystal indicated that our current options were to have a Celanese person proficient in python to write one or hire Cognite to write one. All this is to say that from a usability perspective, CDF is, at the current point in time, probably only good for looking up individual pieces of information, one at a time. The effective reporting capability is basically zero. I can’t say I was expecting anything more than that, but I was a little surprised that their answer to everything was to go code whatever you wanted yourself in Python. In my head, I was envisioning something like Pivot Table level usability with the CDF data.
We have a time series that begins on the install date of an asset, which for some assets out in the field have a install date prior to 1970. When we try to insert these time series data points into CDF via the Python SDK, we are getting this error: cognite.client.exceptions.CogniteAPIError: Timestamp is too low, must be at least 31536000000 Is there already a workaround for storing data points with a date prior to 1970? Is this supported by the HTTP API, but not the Python SDK? Thank you,Ben Brandt
I have been playing around with the excellent DirectQuery preview functionality and really enjoyed that I can simply give it a timestamp range and it figures out how many points I need and what the granularity will be with the assumption that I will use the queried data for some visualization. Even if someone has an 8K monitor with no border around their chart, with one pixel per point the most I could possibly need would be 7680 datapoints. Reality is that we need much less since we show a datapoint as more than a pixel width. But I don’t have to care about that complexity. Cognite calculates optimal granularity for me. Can this feature also be available via the API for “Retrieve data points”?https://docs.cognite.com/api/v1/#tag/Time-series/operation/getMultiTimeSeriesDatapointsMaybe we would be able to set granularity to “auto” then the magic happens?
As a production planner, I want a bid matrix that represents our actual water values. Today, we can experience that the given price scenarios do not necessarily trigger any production in every hour. That could be due to high water values or a limited water reservoir. The result is a matrix where the production is only on the last price column. This is not a correct representation of our water values, and something that could trigger an investigation from the market surveillance if used in the market. I think it is not a single solution to this problem. Sometimes, the solution is to have a wider price spread (needs a pop-up alarm or automatic fix), sometimes the right solution could be to get long term water values from our cut-files, or it could be a logic using the water values from hours where production is triggered.
As a Shift Captain when reviewing checklist progress or at end of shift I would like to see any items that have a status of "not ok," a comment, or has an image attached to it, so I can quickly see the most important findings easily and quickly in order to take action. It is difficult to know if I saw all pertinent things when scrolling through a long list of items that are "done" or looking very hard for little image icons or free text comments.
When a child asset (CHILD) is linked with timeseries resources, these timeseries resources are shown in the parent asset (PARENT) of CHILD.I believe this is the design of current CDF and I can easily see both pros/cons of it.Then, I’d like to propose two ideas.When I see timeseries tab of PARENT, I’d like to see with which assets those timeseries are attached with. I attach a sample image of this. I’d like to control if I can see all timeseries or only timeseries attached with PARENT or PARENT with specific CHILDREN.
In CDF the hierarchy on the left hand side and the title blocks at the top of the asset screen are currently the FLOC string. The description would be a better choice since the FLOC string is meaningless strings of letters.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
