Operating your CMDB

A CMDB that nobody maintains becomes a liability, not an asset. This section is about avoiding that outcome. It covers who owns the data, how operational teams stay on top of changes, how your CMDB connects to incident and change workflows, and the patterns that keep an Assets deployment trusted by the people who rely on it every day.

These pages apply regardless of which schema you deployed.

---

What is in this section?

CMDB Ownership Model A CMDB without owners drifts. This page defines the ownership model recommended for JSM LaunchPad deployments: who is responsible for what, how ownership is represented in Assets, and what governance looks like in practice for teams of different sizes.

Operating a CMDB The operational runbook. Covers day-to-day management of your CMDB: keeping records current, handling stale data, managing lifecycle states, and the processes that keep your schema useful beyond the first few weeks after deployment.

Data Sources and Population Where does your data come from? This page covers the main approaches to populating an Assets schema: manual entry, CSV import, API integration, and automation rules. Includes practical guidance on which approach fits which use case.

Reference Types and Relationships How objects relate to each other in Assets, how reference types work, and how to read and extend the relationship model in your deployed schema. Essential context before you start linking records or building AQL queries.

Change Management Linkage How to connect your CMDB to change requests, incidents, and problems in Jira Service Management. Covers the linkage patterns, the configuration steps, and how to use service maps for incident response. Six sub-pages covering each linkage scenario in detail.

---