Overview
RMDM (Reliability Maintenance Data Model) provides a standardized data model for maintenance and reliability use cases in Cognite Data Fusion (CDF). It extends Cognite's common data models with maintenance, equipment, and failure-analysis concepts aligned with ISO 14224 and NORSOK Z-008 standards. By deploying RMDM, Value Delivery teams can establish a consistent foundation for troubleshooting, root cause analysis (RCA), and condition-based maintenance initiatives without designing a maintenance data model from scratch.
Who is this for & when to use
Target personas: Delivery Engineer, Data Modeller, CDF Administrator on a reliability and maintenance project.
Use this pack when:
- Setting up a new CDF project for reliability or maintenance use cases and you need a standardized data model without building it from scratch.
- Your project requires Root Cause Analysis (RCA), condition-based maintenance (CBM), or failure analysis workflows.
- You need to integrate maintenance data from CMMS platforms, historians, DCS systems, and engineering databases into a unified, queryable structure.
- Extending an existing CDF project with a standardized maintenance, equipment, and failure-analysis data model aligned with ISO 14224 and NORSOK Z-008.
When NOT to use this pack:
- If your project is manufacturing-focused — use the ISA Manufacturing Data Model deployment pack instead.
- If your project is oil & gas operations with AVEVA, SAP, and PI source systems — use the CFIHOS Oil & Gas Data Model deployment pack instead.
Why you need it
Maintenance and reliability data is often distributed across multiple systems such as CMMS platforms, historians, DCS systems, and engineering databases. Without a standardized data model, teams spend significant effort defining data structures, aligning terminology, and creating relationships between maintenance records, equipment, and failure information.
RMDM reduces this effort by providing a predefined industry-aligned model that:
- Covers the full ISO 14224 failure analysis taxonomy — FailureMode, FailureCause, FailureMechanism, and FailureNotification are pre-wired as first-class views, linked to equipment and maintenance orders without custom schema work.
- Extends CDM and IDM directly — every view implements a standard Cognite interface (CogniteAsset, CogniteEquipment, CogniteMaintenanceOrder, CogniteNotification, etc.), ensuring compatibility with CDF Search, Canvas, and AI tooling out of the box.
- Prevents structural divergence across projects — all reliability and maintenance projects start from the same validated baseline, making cross-project comparison and reuse straightforward.
- Deploys in minutes, not weeks — no schema design iterations, no container/view alignment work, and no CDM/IDM extension wiring to figure out.
- Designed to extend — the module is intentionally a starting point: add properties to existing containers, create new views, or wire up transformations and a workflow as your project evolves.
What's included
| Component | Description | Optional? |
|---|---|---|
rmdm | Enterprise module — owns containers, views, space, and the composed RMDM data model. Deployed to the rmdm space. Treated as the durable contract. | No |
| Equipment views | Asset, Equipment, EquipmentClass, EquipmentType, and EquipmentFunction — extending CDM types (CogniteAsset, CogniteEquipment, CogniteEquipmentType, CogniteDescribable). Asset is the central navigation hub. | No |
| Maintenance views | MaintenanceOrder and Notification extending IDM types (CogniteMaintenanceOrder, CogniteNotification). Linked to equipment and failure analysis views. | No |
| Failure analysis views | FailureMode, FailureCause, FailureMechanism, and FailureNotification — ISO 14224 failure taxonomy as first-class views. FailureNotification extends Notification with failure mode, cause, and mechanism links. | No |
| Supporting views | TimeSeriesExtension (extends CogniteTimeSeries) and FileExtension (extends CogniteFile) — time series and document metadata linked to equipment and maintenance entities. | No |
Prerequisites
Verify all of the following before starting deployment:
- Cognite Toolkit version 0.8 or later is installed. Follow the setup instructions.
- A
cdf.tomlfile exists in your project root. If missing, runcdf initand select Create toml file (required). - Authentication is configured and verified — run
cdf auth initandcdf auth verifyusing a local.envfile. See the Toolkit authentication docs. - Your CDF project has Data Modeling enabled.
- The CDF group used by Toolkit has the following capabilities:
spaces:write,datamodels:write,datasets:write,rawdb:write.
Deployment & installation
Choose your setup path
1. Existing Toolkit project
Use this path if you already have a local Toolkit project and only want to add the RMDM data model.
a. Point cdf.toml at the Cognite Library
Long-time Toolkit users may still have [library.cognite] pointing at toolkit-data. Update it to the official library release:
[library.cognite]
url = "https://github.com/cognitedata/library/releases/download/latest/packages.zip"b. Enable deployment packs in cdf.toml
In the same cdf.toml, ensure the alpha flag is set:
[alpha_flags]
deployment-pack = truec. Add the RMDM module
From your project directory:
cdf modules add -d rmdmd. Build and deploy
Run in order:
cdf build
cdf deploy --dry-run
cdf deployAfter deployment, the RMDM data model, containers, and views are available in your CDF environment.
Verify folder structure
Your project should include:
modules/
└── data_models/
└── rmdm/2. Starting from scratch
Use this path for a new Toolkit project with only the RMDM data model (and the data models pack scaffolding Toolkit creates).
a. Initialize the project
In an empty directory:
cdf modules init .b. Select RMDM in the interactive UI
In the terminal:
- Choose Data models (data models that extend the core data model).
- Use Space to select RMDM.
- Press Enter to confirm.
Toolkit downloads the library, creates the module under modules/data_models/rmdm/, and updates config.dev.yaml / config.prod.yaml.
c. Build and deploy
cdf build
cdf deploy --dry-run
cdf deployAfter either path, the RMDM space, data model, containers, and views are deployed to your CDF environment.
Verification
After deployment, perform the following checks:
- Verify that the deployment completed successfully. The
cdf deploycommand should finish without errors and report successful deployment of spaces, containers, views, and data models. - In Cognite Data Fusion, navigate to:
Data Modeling → Spaces
Verify that thermdmspace exists. - Navigate to:
Data Modeling → Data Models
Verify that the RMDM data model is available. - Open the RMDM data model and verify that entities such as
Equipment,FailureMode,FailureCause, andMaintenanceOrderare present. - Navigate to:
Data Modeling → Containers
Verify that the expected RMDM containers have been deployed. - Navigate to:
Data Modeling → Views
Verify that the expected RMDM views have been deployed.
The deployment is successful when the RMDM space, data model, containers, and views are visible in CDF and can be opened without errors.
Configuration reference
Parameters are set in config.dev.yaml at the project root. Default values work for an initial test deployment.
| Parameter | Description | Default | Required? |
|---|---|---|---|
project | CDF project external ID to deploy to. | — | Yes |
space | CDF space for the RMDM data model — containers and views. | rmdm | No |
dm_version | Version identifier for the RMDM data model. | 1_0_0 | No |
dataset_external_id | CDF dataset used for resources and lineage tracking. | ds_rmdm | No |
Architecture
RMDM is deployed as a single Cognite Toolkit module containing a dedicated space, data model, 13 containers, and 13 views. The module is schema-only — it defines the data structure and CDM/IDM extensions, and does not bundle transformations or a workflow. Data instances are populated separately using transformations or the CDF API once source systems are connected.
CDM extensions (cdf_cdm)
| View | Extends | Purpose |
|---|---|---|
Asset | CogniteAsset | Central asset and functional location node — the navigation hub linking equipment, maintenance orders, notifications, and time series. |
Equipment | CogniteEquipment | Physical equipment with class, type, function code, and service start date. Carries reverse relations to maintenance orders, time series, and files. |
EquipmentType | CogniteEquipmentType | Standard equipment type definition linked from Equipment. |
EquipmentClass | CogniteDescribable | ISO 14224 equipment class classification with code and description. |
EquipmentFunction | CogniteDescribable | Functional category of equipment with code and description. |
FailureMode | CogniteDescribable | ISO 14224 failure mode — the observable way in which equipment fails. Linked to failure notifications. |
FailureCause | CogniteDescribable | Root cause classification for failure analysis. Linked from FailureNotification. |
FailureMechanism | CogniteDescribable | Physical or chemical process that caused the failure. Linked from FailureNotification. |
TimeSeriesExtension | CogniteTimeSeries | Time series data linked to equipment — sensor readings, process values, and historian data. |
FileExtension | CogniteFile | Documents and file metadata linked to equipment and maintenance entities. |
IDM extensions (cdf_idm)
| View | Extends | Purpose |
|---|---|---|
MaintenanceOrder | CogniteMaintenanceOrder | Maintenance work orders with scheduling, priority, and direct relation to Equipment. |
Notification | CogniteNotification | Maintenance notifications linked to Asset. |
Domain-specific views
| View | Purpose |
|---|---|
FailureNotification | Failure-specific notification extending Notification with direct relations to FailureMode, FailureCause, and FailureMechanism — the primary view for RCA and failure analysis workflows. |
Key design decisions
Schema-only module. RMDM deploys the data structure and CDM/IDM extensions only — no transformations or workflow are bundled. This keeps the module lightweight and applicable across any source system combination. Transformations and a workflow can be added per project once the source schema is known.
Single asset hierarchy via Asset. Only Asset implements CogniteAsset. All other entities (Equipment, MaintenanceOrder, FailureNotification) link to assets via direct relations, preserving a clean single-hierarchy navigation pattern in CDF applications.
ISO 14224 failure taxonomy as first-class views. FailureMode, FailureCause, and FailureMechanism are independent views with their own containers — not properties on Notification. This allows reuse across multiple notifications, and enables RCA aggregations across the failure taxonomy without duplicating data.
Troubleshooting
| Symptom | Likely cause | Resolution |
|---|---|---|
cdf auth verify fails with 401 Unauthorized | Missing or incorrect credentials in .env file. | Run cdf auth init, re-enter credentials, then re-run cdf auth verify. |
Module not found during cdf modules add | [library.cognite] not configured in cdf.toml, or [library.toolkit-data] still present alongside it. | Replace [library.toolkit-data] with [library.cognite] in cdf.toml. The two sections cannot coexist. |
cdf deploy fails with "Insufficient permissions" | Toolkit service account is missing required CDF capabilities. | Add spaces:write, datamodels:write, datasets:write, and rawdb:write to the CDF group used by Toolkit. |
cdf build fails with validation errors | Project configuration issue or incompatible Toolkit version. | Review the build output and resolve reported errors. Ensure Toolkit version is 0.8 or later. |
| Views show no instances after deployment | No data has been ingested into the RMDM space yet. | RMDM deploys the schema only — populate instances using transformations or the CDF API once source data is available. |
Support & ownership
| Field | Details |
|---|---|
| Team | Cognite Delivery Team |
| Support channel | #topic-deployment-packs on Slack |
| Documentation | docs.cognite.com |
| Version | 1.0.0 |
| Last updated | 2026 |
Check the
documentation
Ask the
Community
Take a look
at
Academy
Cognite
Status
Page
Contact
Cognite Support
