Skip to main content
Cognite’s core data model—CogniteCore—offers standardized building blocks for industrial data, forming the basis for more specialized models. It’s available from the cdf_cdm system space. The core data model uses two methods to define properties: core features and core concepts:
  • The core features are sets of properties that are available for many concepts.
  • The core concepts have properties that are specific to a single concept.
Each core feature and core concept comes with a matching container and view. The exceptions are stateless concepts, which only have a view and no container. The containers have efficient indexes and constraints and can be used at scale out-of-the-box. The views combine the properties of the core features and the core concepts. The core data model can be extended, currently via GraphQL. For example, Cognite’s industrial data models extend the core data model to meet common, industry-specific needs.

Access control

In addition to the dataModelInstancesAcl capabilities to read/write the instances, users of the core data model need the following capabilities:
  • dataModelsAcl.READ to cdf_cdm to read the core data model schema.
  • dataModelsAcl.READ to cdf_extraction_extensions to read properties set by Cognite extractors.
  • dataModelInstancesAcl.READ to cdf_cdm_units to use units.
For more information, see Control access to a graph.

Core features

This section collects commonly used properties, with common definitions. If a core concept uses a different definition, or narrows the scope of, an otherwise common property, it will be called out in the section that defines the core concept.

CogniteDescribable

The CogniteDescribable core feature has properties to create names and descriptions for concepts.

CogniteSourceable

The CogniteSourceable core feature has properties to represent how the source information in concepts is stored.

CogniteSourceSystem

The CogniteSourceSystem core feature has properties to represent the source system where the information is stored. The following core features are also available for this core feature: CogniteDescribable

CogniteSchedulable

The CogniteSchedulable core feature has properties to represent start and end times for a concept, for example an activity.

CogniteVisualizable

The CogniteVisualizable core feature has properties to enable a standard display of objects and to represent a reference to a 3D resource.

Core concepts

CogniteUnit

The CogniteUnit concept has properties to represent a single unit of measurement, for example Ampere. The following core features are also available for this concept: CogniteDescribable

CogniteAsset

The CogniteAsset concept has properties to represent systems that support industrial functions or processes. Assets are often called “functional locations”. You can structure assets hierarchically according to your organization’s criteria. For example, an asset can represent a water pump that’s part of a larger pump station asset at a clarification plant asset.
For hierarchies, root, path, and pathLastUpdatedTime are system-maintained hierarchy properties. children is a virtual reverse relation, so its behavior differs from these fields. Depending on your SDK-generated model classes, children might not be available as a standard typed property.
Any path values longer than 100 are truncated to the first 100 items. Assets with more than 100 ancestors in the hierarchy will not get a complete path.
The following core features are also available for this concept: CogniteDescribable, CogniteSourceable, CogniteVisualizable

CogniteAssetClass

The CogniteAssetClass concept has properties to represent the class of an asset, for example Pump or Heat exchanger. The following core features are also available for this concept: CogniteDescribable

CogniteAssetType

The CogniteAssetType concept has properties to represent the type of an asset, for example Centrifugal pump or Air cooled heat exchanger. The following core features are also available for this concept: CogniteDescribable

CogniteEquipment

The CogniteEquipment concept has properties to represent physical supplies or devices. Example: a pump or a valve. The following core features are also available for this concept: CogniteDescribable, CogniteSourceable

CogniteEquipmentType

The CogniteEquipmentType concept has properties to represent types of equipment, for example centrifugal pumps. The following core features are also available for this concept: CogniteDescribable

CogniteFile

The CogniteFile concept has properties to represent files. The following core features are also available for this concept: CogniteDescribable, CogniteSourceable

CogniteFileCategory

The CogniteFileCategory concept has properties to represent the categories of files as determined by contextualization or categorization. The following common properties are also available for this concept: CogniteDescribable

CogniteActivity

The CogniteActivity concept has properties to represent activities. Activities typically happen over a period and have a start and end time. The following core features are also available for this concept: CogniteDescribable, CogniteSourceable, CogniteSchedulable

CogniteTimeSeries

The CogniteTimeSeries concept has properties to represent a series of data points in time order, for example the temperature readings from a water pump. The following core features are also available for this concept: CogniteDescribable, CogniteSourceable

CogniteStateSet

The CogniteStateSet concept has properties to represent a set of valid states for state time series. Each state consists of a numeric value (integer) and a string value pair, for example [(0, "OFF"), (1, "ON")]. State constraints:
  • Both numeric and string values must be unique within a state set.
  • Numeric values must be between -2,147,483,648 and 2,147,483,647.
  • String values can be up to 255 UTF-8 characters.
The following core features are also available for this concept: CogniteDescribable

CogniteAnnotation

The CogniteAnnotation concept has properties to represent annotations from contextualization results or links. The following core features are also available for this concept: CogniteDescribable, CogniteSourceable

CogniteDiagramAnnotation

The CogniteDiagramAnnotation concept has properties to represent an annotation for a diagram. The following core features are also available for this concept: CogniteDescribable, CogniteSourceable, CogniteAnnotation

3D concepts

Cognite3DTransformation

Defines a comprehensive 3D transformation, which positions an object in 3D space using translation, rotation (Euler angles), and scale.

CogniteCubeMap

Defines the cube map projections surrounding a 3D entity, such as Cognite360Image.

Base 3D concepts

Cognite3DModel

Groups 3D data into a single model entity. The following core feature is also available for this concept: CogniteDescribable.

Cognite3DRevision

Represents revision data for 3D models. Typically accessed through CognitePointCloudRevision, Cognite360ImageCollection, or CogniteCADRevision.

Cognite3DObject

Represents the virtual position of a physical object, connecting an asset to one or more 3D resources. The following core feature is also available for this concept: CogniteDescribable.

Cognite3DGroup

Groups related 3D entities together.

CAD

CogniteCADModel (view)

This view filters Cognite3DModel where type equals CAD. It’s used for navigating across CogniteCADModel instances. This view inherits properties from the Cognite3DModel concept. The following core feature is also available: CogniteDescribable.

CogniteCADRevision

Represents revision data for CAD models. This concept extends Cognite3DRevision.

CogniteCADNode

Represents contextualized nodes from a CAD model. The following core feature is also available for this concept: CogniteDescribable.

360° images

Cognite360ImageModel (view)

This view filters Cognite3DModel where type equals Image360. It’s used for navigating across Cognite360ImageModel instances. This view inherits properties from the Cognite3DModel concept. The following core feature is also available: CogniteDescribable.

Cognite360ImageCollection (view)

This view represents a logical collection of Cognite360Image instances. It filters Cognite3DRevision where type equals Image360. This view inherits properties from the Cognite3DRevision concept. The following core feature is also available: CogniteDescribable.

Cognite360Image

Represents a 360° image capture. This concept includes properties from the following 3D concepts: Cognite3DTransformation, CogniteCubeMap.

Cognite360ImageStation (view)

This view groups images across collections to create a visual scan history. It filters Cognite3DGroup where groupType equals Station360. This view inherits properties from the Cognite3DGroup concept. The following core feature is also available: CogniteDescribable.

Cognite360ImageAnnotation

This concept defines edges connecting Cognite360Image to Cognite3DObject. The status is always approved. This concept extends CogniteAnnotation. The following core features are also available: CogniteDescribable, CogniteSourceable.

Point cloud

CognitePointCloudModel (view)

This view filters Cognite3DModel where type equals PointCloud. It’s used for navigating across CognitePointCloudModel instances. This view inherits properties from the Cognite3DModel concept. The following core feature is also available: CogniteDescribable.

CognitePointCloudRevision

Represents revision data for point cloud models. This concept extends Cognite3DRevision.

CognitePointCloudVolume

Defines a volume within a point cloud. The following core feature is also available for this concept: CogniteDescribable.
Last modified on July 3, 2026