We know, that within these three areas clearly defined controles are applied and enforced. So to speak, strict Configuration Management is applied – only difference – the Configuration Items (CI) are not IT Objects but screws, engines, pharmaceuticals, money. (more…)
Here you see an example process flow diagram for Configuration Control .
The Configuration Control process guarantees that the content of your Configuration Management System (CMS) / Configuration Management Database (CMDB) remains accurate.
It is always triggered by another process. Usually by the change management process or the request fulfillment process. As in accounting, you don’t enter accounting records just for fun, you always have a business case such as something has been sold, another thing has been bought, year end closing… (more…)
No. I don’t think so.
But the CMS should be the one and only place where the important parts of all this metadata information is consolidated, connected (through relations) and provided to all other ITSM Processes. In addition, I am convinced that the CMS is also the most appropriate place to apply configuration control. (more…)