A CMDB you can keep current: starting small with configuration data

A configuration management database records configuration items, such as servers, applications, licences and network devices, and the relationships between them. Its promise is simple: before a change, see what it might break; during an incident, see what else is affected. The common failure is just as simple: a CMDB that nobody keeps current is worse than none, because people trust wrong data.

Where should a mid-market team start?

Start with services, not devices. List the five to ten business services that hurt most when they fail, such as email, the finance system, the customer app and the VPN. For each, record the main components it depends on and who owns them. That small map answers most "what will this change affect" questions and is small enough to maintain.

How much can discovery do for you?

Discovery tools scan your estate and create or update configuration items automatically, which is the only realistic way to keep large inventories current. Vendors in this comparison document different depths:

• ServiceNow ITSM describes Discovery across on-premises and cloud, Service Mapping of relationships between components and business services, certified Service Graph Connectors and continuous data-accuracy checks.
• Freshservice describes agentless discovery that builds a CMDB from devices, software, storage, cloud resources and their interdependencies.
• Halo (formerly HaloITSM) includes assets and CMDB in its single licence; ServiceDesk Plus includes CMDB in Enterprise and sells it as a $1,195 annual add-on on Professional; Jira Service Management includes asset and configuration management from Standard.
• ServiceNow puts asset management and CMDB in its ITSM Foundation package.
• Zendesk lists IT asset management from Suite Growth but no CMDB, and monday service's product and pricing pages do not document a CMDB or an asset management module.

How do you keep the data honest?

Three rules help a team without a dedicated configuration manager:

• Link records to work. Every change and major incident should reference the configuration items involved. Records that are never referenced are candidates for removal.
• Review by owner. Once a quarter, each service owner checks their map. Ten minutes per service is enough.
• Prefer fewer, accurate records. A CMDB with 200 correct items beats one with 20,000 stale ones.

Is IT asset management the same thing?

Not quite. Asset management tracks hardware and software through their life, with cost, licences and ownership. Configuration management tracks how components support services. Many platforms combine them, and asset data is a good seed for a CMDB, but an asset list alone does not show dependencies.

What if your platform has no CMDB?

Keep a simple service map in a shared document or spreadsheet linked from change and incident templates, and review it quarterly. If configuration data becomes central to how you work, make a CMDB a must-have in your next platform decision.