Most CMDBs don’t fail because they miss data.
They fail because they trust data they shouldn’t.
That’s a lifecycle problem.
When people start with lifecycle management in ServiceNow, I see the same thing every time:
“Let’s build some Business Rules.”
“Let’s enforce transitions.”
“Let’s automate everything.”
No.
You’re solving the wrong problem.
Why lifecycle actually matters
This is what’s really happening in most environments:
-
A server is gone → still “In Use”
-
An application is “Live” → nobody owns it
-
Infra is removed → still used in impact analysis
And then:
Changes are approved on the wrong state
Incidents go to the wrong teams
The CMDB slowly loses credibility
Not because it’s incomplete.
But because it’s out of time.
Lifecycle is not about movement
It’s about validity.
Is this data still true — right now?
If you can’t answer that, your CMDB is just history with a UI.
The uncomfortable truth
ServiceNow already gives you what you need:
-
Life Cycle Stage
-
Life Cycle Stage Status
-
Life Cycle Mapping
-
CMDB Data Manager
Plus the engine behind it:
-
OOTB rules
-
Scheduled jobs
-
Sync between CI and Asset
You don’t need to “build” lifecycle.
But most teams still do this
They start adding logic:
-
“If X → set Y”
-
“Cascade this across services”
-
“Block this transition”
Feels like control.
It isn’t.
It’s fragmentation.
Now lifecycle lives:
-
partly in fields
-
partly in flows
-
partly in Business Rules nobody remembers
Good luck explaining that during an incident.
How I would start (tomorrow)
Keep it simple:
-
Use OOTB lifecycle fields
-
Configure Life Cycle Mapping
-
Enable CI ↔ Asset sync (if relevant)
-
Add 1 Data Manager rule (stale → retired)
-
Measure where reality and data don’t match
That’s it.
CMDB3D perspective
CSDM gives you structure.
Lifecycle gives you time.
Data Manager gives you control.
Without lifecycle → your CMDB describes the past
With lifecycle → your CMDB supports decisions
Final thought
Stop engineering lifecycle.
Start trusting the platform model.
Because once lifecycle disappears into custom logic…
you don’t lose functionality.
You lose trust.
And without trust, your CMDB is just documentation.