Asset data, information and the configuration management system
Domain 3: Asset data, information and the configuration management system
This domain tests data quality, the relationship between the asset register, CMDB and CMS, and how discovery and reconciliation keep asset data trustworthy.
Core rules
- The CMS is the set of tools and data used to manage CIs and their relationships. The CMDB is a database within the CMS. The asset register may be separate or part of the CMS.
- Data quality dimensions include accuracy, completeness, consistency, timeliness, validity and uniqueness.
- Sources include procurement, discovery tools, the service desk, finance, suppliers and manual entry. Automate where possible and reconcile regularly.
- Record only data with a purpose; over-collection raises cost and error rates.
- The definitive media library (DML) stores authorized master copies of software and media, supporting deployment and licensing control.
- Relationships matter: a server asset may support several services, so impact analysis needs both asset and CI relationship data.
Worked example
Discovery finds 420 servers while the asset register shows 400. Investigation finds 15 virtual machines created outside change control and 5 decommissioned records left open. The team updates the records, raises a change for the unmanaged VMs and adds a monthly reconciliation control. The reasoning matters: without reconciliation, licensing, support and incident impact analysis are all based on incorrect data.
Traps
- Assuming the asset register and CMDB are the same thing.
- Trusting manual spreadsheets without reconciliation.
- Collecting data without an owner or purpose.
- Ignoring CI relationships when assessing service impact.
Key points
- CMS contains CI data and relationships; the CMDB is part of the CMS.
- Data quality requires accuracy, completeness, consistency, timeliness, validity and uniqueness.
- Automated discovery should be reconciled with the asset register.
- The DML controls authorized software master copies.
- Relationships and dependencies are essential for impact analysis.