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!
Like for extractor pipelines, there should be a documentation field for each function in Fusion. This would make it easier for our customers to use our product and built solutions, and follows a good principle of keeping the documentation of a solution as close as possible to the solution itself.
The asset hierarchy view in CDF needs a couple features to prevent excessive unnecessary scrolling:When I search for an asset then click ‘hierarchy’, the hierarchy should jump to where the actual asset is. Right now, it always starts at the top and I need to scroll down to find it. The hierarchy should stay focused on what was viewed last until a new asset is clicked, as typical use involves studying multiple assets in a particular system, and needing to scroll back down to the appropriate place every time is annoying.
What the users are looking for is for the Maintenance Techs to have the functionality that gives the ability to see SAP information, order parts, charge time to SAP, etc. They would like to get rid of the shop papers and the Maintenance Techs having to record data on paper and then upload or charge time later in the office.
When looking at many time series (8+), the y-axis scales take up a lot of space on your screen horizontally, and adding more time series to the display continues reducing the x-axis space on the chart itself. Having the ability to compress the horizontal space occupied by the y-axis scales would be helpful, especially since there seems to be a lot of white space available to compress into. We have run into this challenge during real-time troubleshooting, and it becomes especially challenging when working off a smaller screen (e.g. using your laptop screen in a conference room). As you can see from the first image below, the white space around the y-axis scales/labels appears significant. The 2nd image below is a more aggressive shot of the same Chart.Additionally, a feature where hovering your mouse above a particular y-axis would reveal the name of the time series that y-axis applies to would also be helpful when the y-axis units are not merged. This is really more useful when looking at many times series all at once. This is probably a complementary idea to another one already on this board about highlighting the time series in the chart when you hover the mouse over the y-axis.Thank you!
On behalf of @Ibrahim Ahmed and Celanese: We would need flexibility to select the date and time stamps we want to select. Some times people want to see the created on date of the WO to see when the work order was created as opposed to the date of an exceedance of a time series tag. @Magdalena Rut @Knut Vidvei
Hi, my name is Geir Engdahl and I’m co-founder and CTO of Cognite. Cognite is currently considering a new mechanism for API versioning for the CDF API. What are your thoughts on this proposed mechanism? I am very eager to hear your input! Why The goal of this mechanism is to: Make it easier to make smaller breaking (ie. non backwards-compatible) changes to the API Allow us to run multiple versions of the API in parallel Avoid unexpected breakages for API clients Make upgrading version as easy as possible for API clients Be backwards compatible so no existing clients break An example of a breaking change could be to introduce a cleaner structure in the JSON request body for a particular query endpoint, e.g by replacing a previous string field with a nested JSON object. How to Our preferred method of accomplishing this is with a new API header, cdf-version, which takes the format YYYYMMDD and fixes an API client to the API as of that date. We consider this version as a major version, meaning breaking changes can occur when you change this. API clients which do not specify this header will default to a fixed date before we introduce this mechanism, ensuring that they do not break.We will publish updates to the API on a regular basis, and breaking changes will only become visible by setting the cdf-version header to a date greater or equal to the date the change was introduced. It will not be possible to request the “latest” version of the API, short of parsing the current date and dynamically updating the header, which would be extremely dangerous, since unexpected breaking changes could be introduced this way.Each version of our SDKs will be pinned to a particular version of the API. Upgrading to a new SDK version will automatically upgrade to a newer API version. The versioning scheme of the SDKs will continue as today.Why not just change the v1 in the API url to v2 and on? We will keep the v1 in the URL and increment that version if we make large structural changes to the API. This will most likely not happen in the near future, as it has proven to be a very heavyweight mechanism. LimitationsOne of the limitations is that the version header is shared between all endpoints of the API. So if you want a new feature under /timeseries which requires a date greater than X, you will also need to make sure that you support breaking changes up to this date under all the other endpoints, for example /events. We think this strikes a good balance between encouraging API clients to upgrade and them having explicit control over upgrades and a chance to test that all changes are working when they do choose to upgrade.
On behalf of Celanese users.As a user, I want to have a feature that provides me with the opportunity to duplicate templates that were created and tested in dev to prod. Creating and testing templates in the Dev environment first will prevent permanent write backs to SAP. Tagging @rsiddha for visibility.
As a Learning Facilitator or template creator, I would like the ability to create a template in a sandbox environment or “project” (example, the celanese-dtr environment), and then be able to push my changes to the production environment (celanese) when I have verified that the naming convention and items follow my organization’s standards. This would allow me to control what my process experts see before the template is ready to be shared, but also prevent mistaken synthetic tags to be created in CDF and junk it up with a tag that was created by accident. Today, if I mistakenly forget to add a character like a number or letter and save the template item, then it is still permanently written into CDF PROD.
A team concept is missing in CDFWe are working with data in our organization aligned with the data mesh principles:- Data as a product- Domain-oriented ownership of data- Self-service data platform- Decentralized data governanceCurrently the setup for access management in CDF does not support this functionality. A team should be able to create, edit and delete datasets, and data associated with their datasets (e.g., assets, events, sequences). With the current solution an admin with group:write and dataset:write access needs to create a dataset and create new groups for service accounts/user accounts and add capabilities to read/write resource types within the dataset. We are thus not able to provide a solution which is self-serviced to teams within our organization where they freely control their data and access to it.
On behalf of Celanese Clear Lake InField super users:When creating a template in InField, I want the ability to link assets across the site regardless of my unit. Some assets are shared between multiple units (i.e Utilities/LDR & Shipping). Other assets may be aligned to one unit but maintained by a different unit. By having the units and their associated assets in silos, this could lead to potentially losing out on valuable data.
I would like to emphasize the need to have touch screen interactions with the 3D Model especially in Remote. We like to use large touch screen interactions to colloborate in large meetings.
On behalf of Celanese Clear Lake InField super user:When creating a template in InField, I would like the ability to copy and paste, or duplicate a line item in my checklist. In most cases, checklists items are repeated throughout with only a few minor changes. It would save so much more time to copy and paste repeated items and make the minor adjustments rather than having to retype each line item individually.
Hi,We are working on building grafana dashboard for all assets connected to specific root asset using cognite grafana plugin. BUT, It seems like Cognite Grafana plugin does not support handling cursor API responses. Due to this limitation, we see following challenges:CDF “Filter assets” api can return max 1000 assets only in a request. This may result into displaying 1000 asset’s data only if we have more than 1000 assets. CDF “Filter time series” api can return max 1000 timeseries only in a request. This may result into displaying partial data only on widgets if total number of timeseries is more than 1000 for all assets coming under selected hierarchy.This is major blocker for us.
Use case: We have variety of workflows which generate multiple values on a single date. To be more specific it is kind of tabular data like Sequences but there is no notion of datapoints/date in Sequences, whereas our output is date effective.We cannot keep on creating Sequences on daily basis as after a certain period of time there will be huge no of Sequences which will be tough to update and query.In Time Series we can store a single value either of type Numeric or String on a given date. We cannot have multiple values on the same date. Alternative can be to store serialized object of Sequences as JSON string in Timeseries datapoint. Questions:What is the data size limit of Timeseries string field?Requested feature: Can we have a variant of Sequences based on similar concept as that of Timeseries where we have datapoints and we can store tabular data as value on given date.
In process operations we have some equipment that runs under a vacuum and there for is running at a negative pressure, currently we are unable to input negative values into infield readings on mobile devices.
Submitted on behalf of Celanese Charts User in a training session:As a Charts User, I would like to be able to change a Node / Operator more easily without having to add node and scroll through all over again.For example, if I accidentally clicked “Absolute value” when I meant to click “Add” directly underneath it on the “Operators” options, I would have to Add another Node, navigate to Function, scroll all the way down to “Operators” again before selecting the correct operator I originally wanted.
Enter your E-mail address. We'll send you an e-mail with instructions to reset your password.