This process controls the integration of new CI-Classes / CI-Relationship-Classes into the Configuration Management System (CMS). Its executed the first time after (or parallel to) the Configuration Management and Planning process and everytime you extend your CMS.
The main result of this process is that your CMS System is able to handle the new CI-Class / CI-Relationship in scope of this execution cycle
- Entities / Keys / Attributes / Domains for the new objects to be managed
- how to initially load the information
- Configuration Control is defined (including integrations)
- Configuration Verification and Audit is defined
- Configuration Status Accounting is defined
and all three processes are implemented for the new class(es). Base for this process definition/implementation are the standard processes (defined in Configuration Management and Accounting).
There is (again) no process flow example in the ITIL Manuals for this CoM subprocess (unlike e.g. for incident management).The following steps are vital:
- Determine the scope and objectives of new CI-Class / CI-Relation Class to be integrated into Configuration Management
- Define CI-Class to be integrated (CIs, Attributes, Keys, Conventions)
- Define CI-Relationship-Class to be integrated
- Adapt standard Configuration Control, Verification and Audit, Status Accouting process to comply with the characteristics of the new CI-Class / CI-Relation-Class
- Adjust CoM-KPIs if needed
- Define and Implement Integration (Change Mgmt / Request Fullfillment)
- Define Initial Load (From where do I get my first set of authorized CIs / relationships for this class(es) )
- Verify and adapt operational procedures of the existing CMS (size of you database, availabilty of the CMS, relevance of the new CIs/CI-Relations for Continuity Management…)
- Create an implementation plan (or extend or at least review an existing implementation plan)
Yet another example from accounting: your CEO decides to expand business, you now not only sell shoes but also handbags, wallets and briefcases. Despite building the supply-chain of this new branch of the company and redecorating your showrooms you also have to make sure that your accouting system is able to integrate this business. That means that you might need to extend you table of accounts, you even need to change certain models (how to evaluate the value of the inventory of handbags in comparison to shoes…. ) etc.
There are different interpretations about the content of this process. My interpretation has the benefit that there is a clear distinction between maintenance of CIs ==> daily, operational CoM processes (Configuration Control, Configuration Verification and Audit, Configuration Status Accouting) and structural changes of the CMS such as definition of new CIs/Relationships to be managed (Configuration Identification). Additionally is to state that by defining a distinct process for the extension of the CMS with new CI-Classes/CI-Relationship-Classes you obtain better quality in your CMS and a more sustainable solution in general.
Tags: Identification, Process