This process makes sure that the content of your Configuration Management System (CMS) / Configuration Management Database (CMDB) is verified and audited to guarantee the required level of data content accuracy. That goal is reached by executing a set of different procedures searching for discrepancies and raising incidents when difference can not be explained (e.g. some discrepancies can be explained by open changes, that means the TO BE State is already defined, but the change has not been deployed yet, so that the AS IS (discovered state) is not YET correct. (more…)
Archive for the ‘Process’ Category
What does the Configuration Verification & Audit process look like?
Saturday, May 1st, 2010What does the Configuration Status Accounting process look like?
Saturday, May 1st, 2010This process manages all reporting aspects from your Configuration Management System (CMS) / Configuration Management Database (CMDB). Remember, all other IT Service Management Processes are keen on such reports (if the quality of the content meets expectations ==> is properly controlled by configuration control).
The result out of the Configuration Status Accounting process are reports, such as (more…)
Configuration Status Accounting, an example process diagram
Saturday, May 1st, 2010The diagram below shows the Configuration Status Accouting process flow.
Configuration Verification & Audit, an example process diagram
Saturday, May 1st, 2010Below you see picture with an example of a process flow diagram for Configuration Verification & Audit. (more…)
Configuration Control, an example process diagram
Wednesday, April 28th, 2010Here you see an example process flow diagram for Configuration Control .
Best Practices for Configuration Management and Planning
Friday, April 23rd, 2010The Configuration Management and Planning process is absolutely essential when starting with Configuration Management. It ensures that the whole foundation of your Configuration Management is well tought out and your Configuration Management System is sustainably built. It is usually executed only once in full detail and then only updated when extending your CMS (e.g. with new CIs / new CI-Classes (Types) / new CI-Relations ).
Experience has shown that the importance of this process cannot be stressed enough. If this process is not given its full due attention, the risk of following an aimless CoM course – with consequential financial impact – is extremely high. (more…)
What does the Configuration Management and Planning Process look like ?
Friday, April 23rd, 2010This process provides the base of your configuration management. It is usually executed first. The main results are
a) a configuration management plan where all relevant information (e.g. process description, CMS Architecture, mandatory attributes, naming conventions…) is described
b) an implementation plan for CIs/CI-Relationships their processes and the CMS within the scope (more…)