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
CDF administrators need ability to audit all the modifications done to the projects, based on a selected time interval (for any time in the past). Auditing should be exhaustive enough to capture any and all details relevant to modifications done to the project, updates to user groups etc. The audit log should provide sufficient details on who made the modification, when the change was made, how the change was performed, location details of the user etc. etc. Auditing feature should also include the ability to track what data is being downloaded by end users from CDF, how often, amount and nature of data being downloaded per user, site, location etc. Auditing feature is of high importance to Celanese and as it has came up in discussions multiple times since the beginning of this year, we would like to see this added to the CDF roadmap in the very near future. @Hunter Beck @piya dey @ibrahim.alsyed
We have a task to standardize time series metadata for Celanese, which includes removing some fields. If we remove a field with a transformation, it will be re-added shortly after by extractor update. Currently, we do not find any “natural” way of modifying metadata fields belonging to time series. A possible natural way of doing this would be if the PI extractor could upload TS objects and metadata separately. In this way, metadata could be stored in a RAW table. Based on this table, transformations could be written to update the dataset with the correct metadata fields. Reach out for more information. Please provide input on if and when this could be available. See slack discussion here.
Hi, We see InField 2.0 uses CDF Internal Dataset ID for storing synthetic time-series. This makes it not possible to CI/CD InField configurations. Sending a request to utilize external dataset IDs instead so that the entire config can be easily copied from dev-stage-prod environments. Christian A.
On behalf of InField super users at Celanese:When trending timeseries using InField, all available time series for a specific asset are loaded in at once by default. Depending on how many timeseries are available for the specified asset, this can really bog down InField as it is trying to process that information. If the system doesn’t lock up at that point, the user then has to go and deselect all of the tags that they do not want to see. Can this be updated so that, by default, no tags are loaded in and the user is instead able to select the tags that they want to see?
Hi!The location field list is not sort alphabetically and not able to be filtered. Makes it hard to navigate if several root locations. CC: @roman.chesnokov
Hi, I’d like to be able to use the timeseries/list endpoint for global variables using the Grafana data source (not just assets). Any plans for developing this?
When manually linking Resources to a P&ID, the width of the search window takes up the majority of the screen and the user is unable to visually see the tag they are trying to link. The ability to click and drag the window to reduce the size would minimize the back and forth required when the user inevitably forgets the tag ID they need to search for.
Template creators should have the ability to assign "ok" or "not ok" to each custom state on the template. Also, checklist users should not have to both mark the custom state AND hit "OK" or "Other" and then select "Not OK" from the drop down of options in order to complete a task with custom states. They should only have to mark a custom state and the checklist should automatically register that this is green/OK or red/Not OK, before moving on to the next task.
“Structural entity data. This part of the data typically represents the setup of the control system (from which the OPC-UA data is sourced). You could think of this as the equipment and sensor breakdown structure which helps understand the context of sensors and events. CDF Data Modeling is a good destination for this part of the data.”In one of the Hub Items, I noticed a suggestion to store Entity data in FDM. My question is, how do I use OPC-UA extractor to push data into FDM instead of Asset Hierarchy model which it does today?Is there any documentation I can refer to?Please note, this question is not for TimeSeries or events but only context data into FDM
Provide an option to copy the URL or link to a Canvas such that the link can be included in other objects for referencing / linking to the Canvas
Currently the Streamlit access for the users of the project can only be prohibited if you strip the files.write and files.read capabilites from the specific user groups. This is a good temporary solution, but in case the users want to work with files inside the Streamlit applications, they cannot, since the capabilities restrict them from reading / writing files in CDF. Streamlit’s access rights are very limited at the moment, and the users can see the code of the applications. It would be nice to separate users from developers when it comes to Streamlit in Cognite. The same thing applies to Published / Unpublished Streamlit apps. Right now it is just a label, I am sure there were plans regarding the access rights of Streamlit, so I would like to raise these ideas to the dev team. Thank you for your hard work,Tibor Váncza
I am using OPC-UA Extractor to populate TimeSeries in CDF. Can I attach some extra metadata to all TimeSeries it creates?From documentation I couldn’t figure what configuration should I change to add metadata?
On behalf of Celanese Maintain super users:I would like the ability to see and create layouts for notifications similar to the functionality for activities/work orders in Maintain 2.0. This would allow us to create layouts specific for notifications backlog and improve visibility for the asset leaders/gatekeepers at the site as they look to review and prioritize. @Marius Biermann
We need the ability to write back Basic Finish dates to SAP from Maintain
On behalf of Celanese Maintain super users:I would like the ability to see attachments at the notification and work order level in Maintain. In the current process, it is common for supporting documentation such as red-lines or images to be assigned at the notification and the work order. These attachments would need to be made available in Maintain to support the work package builds using canvas. This would help in preventing the need to jump between two different data sources. @Marius Biermann
As a Charts user, I would like the ability to easily select all of the time series with a check box of some sort and then delete all that I’ve selected, rather than having to delete one at a time. As an example, I duplicated someone’s public chart and wanted to replace the time series that feed into the calculation with different tags. There were a lot of variables, so it took a long time removing each time series that needed to be replaced by having to go one by one.
Use CaseAs a Maintenance Technician or Operator I want to be notified of alerts via the INFIELD user interface which is what I use as my ‘single pane of glass’ for my daily work It is not sufficient to use email or SMS notification.
Writeback of plan updates in Maintain to SAP
If I make a mass change for a long list of tasks in a template, but forget that a handful of those tasks already have the time interval I’m looking for, that handful of tasks should not get a duplicate time interval (see attached picture). The template task should recognize that that time interval already exists for that given task and not add it so as to avoid an unnecessary duplicate time interval.
Users would like the ability to Export to Excel and so want to see an export to excel button from the Activities List/tab in Maintain
Currently, InField 2.0 does not have the date and time stamp as well as the email signature of the person completing a given task show up on the checklist task as it does in InField 1.0. This is an important feature, as operations would be able to trace back when given tasks were completed and by whom, in case they need to go back and ask a question. This is also important for audit purposes.
Allow custom directives to be defined in the FDM language. Currently, you cannot create models with new directives. directive @displayName on FIELD_DEFINITIONtype Wellbore { FacilityName: string @displayName ...} Use case: I want to create a data API with annotation. GraphQL is descriptive, i.e. I can introspect on the model definition. In the example above, I could use the @displayName annotation to know which attribute my client should use when displaying a data item.
As a user of the checklists I need a history log of who did what when.
Use Case : Identify a list of checks to be performed or other instructions to personnel performing a Security Round / Operator Round at a series of WaypointsAdd a DESCRIPTION field within Checklists Not feasible to display a list of checks in the Title of the Task Using the ‘Custom Reading Labels’ does not work well since this produces a set of buttons from which only one can be selected. In this case, the buttons serve no purpose other than to provide the list items to be checked Listing each item as a separate Task would result in an extremely long checklist with too many ‘button presses’ to complete DESCRIPTION field in ‘Add to Task’Custom Reading Labels are not suitable to identify a list of checks at one WaypointNot good to use the ‘name’ field to add a list of items to be checked@Hunter Beck : FYI
In InField v2, the user is not able to edit any of the properties of a time series after creation. In the previous version, you were able to edit the unit and description. It is likely that a user types something wrong when creating a time series. Having the ability to edit (at least some of) the properties in the UI will be very helpful.
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
