Configuration management has long been the cornerstone of ITIL. In version 2 it was the touted as the lynchpin of service support and in version 3 was conflated with service assets to the point where it seems to have lost a clear and distinct meaning.
Every customer I work with seems to view configuration management uniquely. One has an organizational unit called the Configuration Management Office. Their mission is to manage the endpoint asset to the field offices. Another thinks of configuration management as monitoring the configuration baseline and ensuring that they discover and address any drift.
Neither of them have a "ITIL" configuration management database (CMDB) and that is the point. Configuration management is a process that is adopted and adapted by organizations based on their need and their pain . The CMDB as defined by ITIL is not a big factor.
So if someone comes by and offers to do a maturity assessment and lowers your maturity because you don't have a CMDB, smile and thank them and find a better ITSM expert.
R.
Every customer I work with seems to view configuration management uniquely. One has an organizational unit called the Configuration Management Office. Their mission is to manage the endpoint asset to the field offices. Another thinks of configuration management as monitoring the configuration baseline and ensuring that they discover and address any drift.
Neither of them have a "ITIL" configuration management database (CMDB) and that is the point. Configuration management is a process that is adopted and adapted by organizations based on their need and their pain . The CMDB as defined by ITIL is not a big factor.
So if someone comes by and offers to do a maturity assessment and lowers your maturity because you don't have a CMDB, smile and thank them and find a better ITSM expert.
R.