Impact 2024: The Industrial Data and AI Conference for and by Users | Nominate Speakers Now for a Ch...
Understood. I’ve bookmarked this feature request and will respond here once we have plans set for the new feature. Thank you for the awesome feedback!
I’m curious now. I see you’re with Radix. Are you building your own application to plot the machine state, or are you depending on Charts for this?
If you download the data it will not be aggregated, you will get the raw data points.The charts application is tuned for plotting the output of a sensor reading and so when you zoom out, it will always switch to aggregations.When we introduce support for machine states, we will introduce a parameter in the API to designate it as such and when this parameter is true, we will not perform aggregations on the data (no point doing min, max, average etc on state representations).
Hi Dalvania!I’m the time series API product manager.Is the binary series a representation of a machine state (i.e. on/ off) or something else? We are planning to have support for machine state type time series in 2024, where aggregations such as this will not happen. The work isn’t schedule yet but I expect it will be in the second half of 2024.Kind Regards, Glen
Hi Satish,I’m the product manager for our Time Series API. Can I ask from which source is this time series data coming from please? Where possible we try to minimise the use of RAW for onboarding of data points (particularly high volumes of data points). Understanding the source of this data can help us streamline the onboarding process and enable you to directly write this data to the API, where feasible.
Hello All,I am pleased to confirm that this feature is now available in Beta, please refer to our updated introduction page on the developer portal, and our API documentation for further details. The feature will be formally announced in our release communications on the 5th March. We hope to bring this feature to full General Availability level of maturity in our subsequent release, depending on good and timely customer feedback.In order to ingest Time Series data points with status codes, you will need to update your OPC-UA or PI extractor to the latest beta version. The API updates should not affect any existing applications or integrations and it is possible to have a mix of old data points (where bad and uncertain quality data is missing) and new data points with status codes. The API will continue to behave the same by default.An update to Cognite Charts to support status codes in how Charts are plotted is in the works, and a separate update will come from the Charts team near
Thanks for the tag @Everton Colling, and I’m pleased to be able to say that having native support for machine states in our Time Series service is in our 2024 roadmap, and we expect to be able to commence work on this feature in the second half of 2024.For what it’s worth, in my experience the number of states a machine can be in is rarely more than say 10, so creating a type in your data model where you can store the mappings between the numeric representation and the state name, could be a solution in the meantime.
Hi @Anders Brakestad,I’m the product manager for our Time Series services, and I’m keen to learn any observations, good or otherwise that you find from your evaluation. Would you be available to have a short call with me when you’ve concluded your research?Kind Regards, Glen
You are correct Andre, when Time Series data points are stored in CDF via our OPC-UA or PI extractors, they flow directly from the source system into the Time Series API.Same is true for OPC-UA event types, which are typically written directly to the Events API by the OPC-UA extractor.
That sounds good. I look forward to meet you and the team.
Hello! Thanks for coming to us with this feature request. I’m the product manager for our Time Series and OT backend services, and I’ll be handling this request.The sequences service was originally built to service subsurface logs and we’re somewhat limited in the features we’re able to add to this without it becoming a significant investment. Instead, we’re in the planning and designing phase of a new analytics service, which will integrate with our Data Modelling backend. This service is being designed to store and process huge datasets (billions of rows), and will be flexible enough for us to define schemas and index structures for many different types of logs, alarms and events.If this sounds like it might fit your purpose, I’d be glad to have a conversation with you to learn more about your use case.Kind Regards, Glen
@Glen Sykes will this also be built into the extractors like PI and OPCUA to enable catching the machine status, error messages etc? The extractors support string types today. When we declare support for machine states, we will have ‘end to end’ support, which means we will develop the feature on the extractors at roughly the same time as the storage API. The current design hypothesis is that the states will be stored as an integer, and an enum mapped to that. Basically a ‘productised’ version of the recommendation that @Johannes Hovda makes earlier, where we will offer some common enum mappings out of the box, and allow for new mappings to be created.
Hi there, I see there has been an update on this. Can we say string, numeric, enums will be supported for time series data from Jan 2024? Hi, Time Series has supported the string type for a long time. There hasn’t been any change there. Enum support should be coming during 2024, but it is more likely to be the second half of 2024.
My pleasure Andre! Please let us know how you get on with the feature! :)
Hi Andre, I think the error is because you need the privileges to create (write) a subscription, not for the subscription to write to the Time Series itself.Kind Regards, Glen
Hi Marcela,Our approach to solving this requirement is by introducing support for Time Series Status Codes, which after implementation will mean there will be no more empty time series, (unless that is the case in the source system). Please could you take a moment to review the proposed API changes I shared with and the team some days ago and let me know if you’d like to have a follow up discussion if this doesn’t solve your requirement.Kind Regards, Glen
Following up on this request. Representation of Machine States in Time Series is now in our program backlog for 2024. By our current estimation we will have capacity to deliver this in Q3/Q4 timeframe. Timescales are subject to adjustment of course.
Hi Oussama, Would an approach where we implement a subscriptions API, similar to that of Time Series satisfy this requirement?Kind Regards, Glen
Hi Marcela,I will send you a direct message as I would like to share our draft API specification with you for feedback.Kind Regards, Glen
Hi Oussama, Thank you so much for using our API, and for your great feedback. I’ve shared your comments with the team and we’ll come back with a reply soon.I can say that we took a decision during the development phase to not implement a real-time push as that would require a sizeable effort, though we would consider adding that later depending on customer feedback (such as yours!) so this is really good information.We might look at how we can implement non-blocking / async methods and see if that’s low hanging fruit that we can include in the production release.Kind Regards, Glen
Thanks Oussama, one of our developers will be along soon to help out!
Hi Oussama, I’ll discuss with the development team and see what we might recommend.I like the sound of your versioning approach!Glen
Hi,We currently do not natively support enums in Time Series (for example for representation of machine states), however this is in our roadmap for 2024 (though possibly second half of the year due to other priority items in the queue)Kind Regards, Glen
p.s. if you could let me know the language you’re programming in against the API too, I’ll check if there’s any functionality in our SDKs that might also be helpful here.
Hi again Oussama,Unfortunately, due to that field already having a defined behaviour (it is updated on metadata changes), to fulfil your specific request would be a breaking change that we cannot fulfil as other customers may be using this field for other purposes.But, I am keen to understand the use case behind the request, and I will work with the team to explore what solution possibilities we have to fulfil your requirement.If you can provide as much detail as possible about the use case, this will be very helpful.Kind Regards, Glen
Already have an account? Login
Enter your username or e-mail address. We'll send you an e-mail with instructions to reset your password.
Sorry, we're still checking this file's contents to make sure it's safe to download. Please try again in a few minutes.
Sorry, our virus scanner detected that this file isn't safe to download.