Where do Sequences fit in the Core Data Model? CogniteSequence ?

Question

We are migrating to the core data model. Time series we tested. We can ingest CogniteTimeSeries directly from the OPC-UA extractor. Assets are in progress.

Sequences are our open question. We use them heavily for three things:

Multi-dimensional rows tied to a timestamp or time range, where one time series per dimension is the wrong shape.
Static reference data that many Functions read.
Schemas where one data modelling instance per row would explode our instance count — short heating episodes, small production batches, and similar.

What makes them attractive is the combination: readable in the UI, integer indexing, cheap, fast, and metadata slots both per column and per sequence.

Looking at the core data model reference, I see no sequence concept — CogniteTimeSeries, CogniteActivity, CogniteFile and so on are all there, but nothing for tabular data. We have noted CogniteTimeSeries with type: state and CogniteStateSet, which covers state classification, but not the multi-column case.

So:

Is a sequence concept planned for the core data model?
If not, what is the long-term status of the classic Sequences API — supported indefinitely, or on a deprecation path?
Once our assets are CogniteAsset instances, how do we link a sequence to an asset? There is no direct relation slot for it, and classic assetId cannot reference a data modelling node. Is an instanceId-style bridge planned, as was done for time series?
If sequences are not coming to data modelling, what is the recommended pattern for tabular data at this scale — records, plain instances, Raw, or something else?

Thanks,
Sagar

Everton Colling · Accepted Answer

Hi ​@APSHANKAR Sagar!There is no CogniteSequence concept in the core data model and none is planned. The equivalent is Records, which went GA in December 2025. Records are structured data objects stored in streams, outside the graph, and they cover all three of your cases.The link between records and instances in the graph (assets in your case) is a direct relation from the record to the instance (docs). In the coming quarters we are releasing Records views, which bring the view concept to records and let you define reverse direct relations, so an asset or any other instance view can show the records pointing to it.On the classic Sequences API, there are no new features planned. It stays supported, but our investment is going into Records and CDM, so I would recommend building anything new on top of Records.

APSHANKAR Sagar · Answer

Hi ​@APSHANKAR Sagar!There is no CogniteSequence concept in the core data model and none is planned. The equivalent is Records, which went GA in December 2025. Records are structured data objects stored in streams, outside the graph, and they cover all three of your cases.The link between records and instances in the graph (assets in your case) is a direct relation from the record to the instance (docs). In the coming quarters we are releasing Records views, which bring the view concept to records and let you define reverse direct relations, so an asset or any other instance view can show the records pointing to it.On the classic Sequences API, there are no new features planned. It stays supported, but our investment is going into Records and CDM, so I would recommend building anything new on top of Records.Hi ​@Everton Colling,Thank you for your answer.We are already using records and streams (we were on the private alpha as well).It does indeed cover 1 and 3 though I think we will need something forlifecycle management of records, to transfer data from mutable to immutable streams once the data settles. Let me know if Cognite is planning anything specific for this.For 2 (static mappings etc) I guess I can use csv files which also can be displayed.

Sign up

Welcome to Cognite Hub