CSDM Lifecycle
Walk a CI through Design → Build → Operate → Retire. Set required fields, pick a substatus, and see what the platform enforces.
CI Record
nameAPP-PAYROLL-01
classcmdb_ci_app_server
operational_statusNon-Operational
owned_byRequired from Design
managed_byRequired from Build
assigned_toRequired for Operate
environmentRequired for Operate
CSDM Lifecycle Stages
life_cycle_stage / life_cycle_stage_statusDesign
● planned
○ approved
CURRENT
Build
○ in_development
○ qa_testing
Operate
○ deployed
○ operational
○ monitoring
Retire
○ decommissioning
○ decommissioned
○ archived
Attempt Transition
Design
Build
Operate
Retire
Current Stage Details
CMDB Health: Not scored — CI is pre-production
Visibility: Visible only in planning views and CSDM design reports
Required: owned_by
Transition History
No transitions yet. Pick a stage and status to begin.
Reference
life_cycle_stage
The CSDM lifecycle stage. Progresses linearly: Design → Build → Operate → Retire. Build can return to Design.
life_cycle_stage_status
Substatus within the stage. Each stage has its own set of valid statuses. Invalid combinations are rejected.
CMDB Health
Health scoring varies by stage. Design CIs are not scored. Operate CIs are fully scored. Retired CIs only get compliance checks.