The CMDB is one of those foundational concepts that we all know we need. We reference it in change reviews, we use it during incident triage, and it plays a central role in every ITSM framework from ITIL to ISO 20000.
It’s Not Just About Configurations
“Configuration” implies settings, versions, maybe even scripts. All valid attributes maintained within a CMDB. But when we talk about the CMDB in practice, that’s rarely what we use it for.
What the CMDB actually provides is operational visibility:
- It shows how our infrastructure and services are interconnected.
- It informs impact assessments and change planning.
- It’s the single place where IT operations can understand what exists, where it is, and how it relates to everything else.
Calling it a “Configuration Management Database” is like calling a city map a “Street Name List.” Technically accurate—but it completely misses the point.
So, What Should We Call It?
Here’s my pitch: Operational Component Database (OCD) or Operational Component Inventory (OCI)
I personally enjoy the acronym OCD! However, both of these names speak to the real role the CMDB plays in modern IT organizations:
- It supports operations, not just documentation.
- It tracks components, not just configuration items.
- It focuses on relationships and visibility, which are key to enabling agile, resilient service management practices.
An Operational Component Database (OCD) would be understood as a living system of operational knowledge. Away from the perceived dusty record of device settings that is never reliable.
Why the Name Matters
I’ve seen too many organizations struggle with CMDB adoption because the name itself sets the conflicting expectations. Leaders hear “configuration” and think it’s purely technical. Engineers hear “database” and expect a spreadsheet with version numbers.
What they should see is a strategic inventory of Service components. Something that empowers IT to respond faster, plan smarter, and recover more effectively.
A rebrand can help reframe that conversation. Finally elevating the CMDB to the role it was always meant to play.
Let’s Talk About It
So here’s my question to you, fellow ITSM’ers:
Is it time to rebrand the CMDB?
Would a name like Operational Component Database (OCD) help shift mindsets in your organization?
Leave a comment below—I’d love to hear your thoughts.
If you’re into ITSM ideas like this, subscribe for more of my random thoughts. Who knows, you might get some practical takeaways from the world of service management.
Leave a Reply