What it is (plain English)
The CMDB (Configuration Management Database) is ServiceNow's inventory of everything your business runs on — servers, laptops, applications, network gear, cloud resources — and, crucially, how those things connect to each other. Each entry is a configuration item (CI).
It's the "map of your world" that other modules consult: when something breaks, what services does it affect? When you change a server, what depends on it?
Problems it solves
- "We don't actually know what we have" — no reliable inventory of systems and their owners.
- Support teams can't tell how big an outage is because nothing records what depends on what.
- Change approvals are guesswork without knowing what a change might break.
What must exist first
Platform Core Setup — users, groups, and core company data must exist before CIs can have owners and support groups.
What the customer needs to provide
- Whatever inventory you have today, in any state: spreadsheets, an old asset database, an existing monitoring tool. Honest and incomplete beats polished and stale.
- A named owner for the CMDB — someone accountable for keeping the map accurate.
- Decisions on scope: which kinds of things matter enough to track first (start small: the systems behind your most critical business services).
- Access for automated discovery of your network/cloud, if you choose to use it (credentials, firewall arrangements — your infrastructure team will be involved).
Where it can go next
A healthy CMDB unlocks almost everything: Incident Management impact analysis, Change Management risk assessment, asset management, and automated discovery/service mapping (covered under the ITOM family when ingested).