VN:F [1.8.8_1072]
VN:F [1.8.8_1072]
Configuration Management Process Overview
19. August 2010Basic Implementation Considerations Configuration Management System
1. Juli 2010When implementing a configuration management system you usually start with the following steps:
- What is expected? submitted requirements catalogue has to be available
- Establish roles and responsibles
- Define measurement system (KPIs to control Critical Success Factors)
- Strong and stable CMS Architecture and Design (including Metamodel)
- Create standard configuration management processes (samples see here: www.dis.ch/blog/index)
- Determine CI-/ CI-Relation scope needed to meet customer requirements
- Define degree of control (accuracy) of Configuration data required Diesen Beitrag weiterlesen »
Why should I raise an incident when finding a discrepancy in my CMS
29. Juni 2010You don’t have to, but there are some reasons you should consider it:
Reason Nr. 1: because the ITIL Manuals state: What is an Incident? ”An unplanned interruption to an IT Service or reduction in the Quality of an IT Service. Failure of a Configuration Item that has not yet affected Service is also an Incident. ” Diesen Beitrag weiterlesen »
What are the five Configuration Management Processes?
20. Juni 2010- Configuration Management + Planning
- Configuration Identification
- Configuration Control
- Configuration Verification + Audit
- Configuration Status Accounting Diesen Beitrag weiterlesen »
What is a CI?
20. Juni 2010You can imagine a CI (Configuration Item ) as any IT Object (e.g. desktop, server, printer, piece of code, script, operating system, database system, service, business application) which is managed by the Configuration Management processes. Each CI also has relations to other CIs, the consideration of relations is vital.
See more here: What is the difference between an asset and a CI? and Is a person a CI?
Where does Change/Release-Management depend on accurate Configuration Information?
3. Juni 2010Where in the process of Change/Release/Deployment Management is an interface to Configuration Management and what exactly is the content of information required?
a) first of all in the Request for Change, who is required to initiate and document any change. There it has to be specified which components / relations are to be changed. It is beneficiary to select the affected components from a predefined fixed CI-list rather than enter the components name as free text.
Do I have to apply strict Configuration Control?
2. Mai 2010It depends !
It depends on what you intend to do with the CI/CI-Relation data. Diesen Beitrag weiterlesen »
What does the Configuration Verification & Audit process look like?
1. Mai 2010This 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. Diesen Beitrag weiterlesen »
What does the Configuration Status Accounting process look like?
1. Mai 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 Diesen Beitrag weiterlesen »
Configuration Status Accounting, an example process diagram
1. Mai 2010The diagram below shows the Configuration Status Accouting process flow.