Configuration Management Plan

Submitted to: Core Team On 30-04-2009 Submitted by:

For Wipro ES

Template Configuration Management Plan

FILE IDENTIFIER VERSION NO. EFFECTIVE DATE

TP_ES_SACM_CMP 0.4 30-04-2009

Revision History
Version (x.yy) V 0.1 V 0.2 V 0.3 Date of Revision 31/03/200 9 04/04/200 9 15/04/200 9 30/04/200 9 Description of Change Draft Version by Geetha/Garima Reviewed by Satish For implementatio n workshop by Geetha/Garima For implementatio n workshop by Geetha/Garima Reason for Change NA Review comments incorporated Review comments incorporated Review comments incorporated Affected Sections NA Review comments incorporated Review comments incorporated Review comments incorporated Approved By Satish/Satya/ Geetha Satish/Satya/ Geetha Satish/Satya/ Geetha Satish/Satya/ Geetha

V 0.4

Wipro-ES

Internal & Restricted

Page 2

Template Configuration Management Plan

FILE IDENTIFIER VERSION NO. EFFECTIVE DATE

TP_ES_SACM_CMP 0.4 30-04-2009

Table of Contents 1. Scope....................................................................................................................................4 2. Roles & Responsibilities......................................................................................................4 3. Configuration Management Plan for External CIs..............................................................5 3.1 Configuration Identification ..........................................................................................5 3.2 Naming convention .......................................................................................................5 3.3 Attributes of configuration item.....................................................................................5 3.4 Unique Identifier ...........................................................................................................5 3.5 Relationships..................................................................................................................5 3.6 Control Mechanism........................................................................................................6 3.7 Status accounting ..........................................................................................................6 3.8 Verification and Review................................................................................................6 4. Configuration Management Plan for Internal CIs...............................................................6 4.1 Configuration Identification ..........................................................................................6 4.2 Naming convention .......................................................................................................7 4.3 Attributes of configuration item.....................................................................................7 Name and Version of the documentation............................................................................7 4.4 Unique Identifier ...........................................................................................................7 4.5 Relationships..................................................................................................................7 4.6 Control Mechanism........................................................................................................7 4.7 Status accounting ..........................................................................................................7 4.8 Verification and Review................................................................................................8 5. Configuration Management Plan for Organizational CIs....................................................8 5.1 Configuration Identification ..........................................................................................8 5.2 Naming convention .......................................................................................................8 5.3 Attributes of configuration item.....................................................................................8 5.4 Unique Identifier ...........................................................................................................8 5.5 Relationships..................................................................................................................8 5.6 Control Mechanism........................................................................................................8 5.7 Status accounting ..........................................................................................................9 5.8 Verification and Review................................................................................................9

Wipro-ES

Internal & Restricted

Page 3

Template Configuration Management Plan

FILE IDENTIFIER VERSION NO. EFFECTIVE DATE

TP_ES_SACM_CMP 0.4 30-04-2009

1. Scope
Customer contract & related IT infrastructure products comes under the scope of Configuration Management Plan. The Plan also covers related configuration items such as resources & documents. 2.

Roles & Responsibilities

Wipro ES has identified SAP as the SACM database. Following are the roles under SACM process. Roles Configuration Manager(SDM) Responsibilities a. Responsible for development of the process standards, plans & procedures and awareness of the process b. Accountable for overall management of configuration management repository and identification and management of CIs c. Ensures adequate resources are available for Configuration Management Activities d. Accountable for Auditing, Validating & reporting of CM database Configuration Management Group is a team who implements this process & responsible for CM tasks. CM group responsible for defining & establishing the Configuration baseline. CM group responsible for monitoring & control of the CM process (ex. taking corrective actions to address the deviations) status accounting; attribute changes and periodic checking of physical items against the database. Responsible for reviewing & evaluating the proposed changes in the CI Authorizing the Baseline contract Reviewing and approving the CMP Responsible for maintaining, storing, retrieving and distribution of the SACM database

No. 1

SACM Group

Management

SACM Control Group

SACM Manager

Wipro-ES

Internal & Restricted

Page 4

Template Configuration Management Plan

FILE IDENTIFIER VERSION NO. EFFECTIVE DATE

TP_ES_SACM_CMP 0.4 30-04-2009

3. Configuration Management Plan for External CIs

CMP Definition - CMP is an activity initiated to ensure a documented plan for recording data against each CI category. The CMP is prepared to ensure seamless delivery of service to external/internal customer.

CMP for External CIs -

3.1 Configuration Identification Equipments under contractual agreements are considered as Configuration Identification for External CI category. Contracts for these equipments are also identified under external CI Category.

3.2 Naming convention

Equipments are identified according to machine Serial Number, Equipment description and Equipment Location. An example for Equipment description is CISCO IP PHONE 7960G. Under equipment location data SAP team describes about Location, Plant section, Work center, Sort field, Customer name and Customer address. Under the equipment number the OEM equipment serial number is captured for Ex SFXOC02458 Contracts are identified by the unique numbers generated by logging the same in the SAP System.

3.3 Attributes of configuration item

Attributes describe the characteristics of a CI such as CI type, name/description, for contracts - Customer Details, Equipment Details, SLA Parameters etc

3.4 Unique Identifier

OEM Serial number aligned with SAP equipment number should be considered as Unique Identifier for External CIs. Unique Numbers are generated in SAP for Contracts. The contract numbers are sequential in SAP Database.

3.5 Relationships

Wipro-ES

Internal & Restricted

Page 5

Template Configuration Management Plan

FILE IDENTIFIER VERSION NO. EFFECTIVE DATE

TP_ES_SACM_CMP 0.4 30-04-2009

Relationship is maintained at contract level between the contract no. and equipment serial number.

3.6 Control Mechanism

The CIs are controlled through authorization checks in SAP. The SAP system follows the SOX policy which is audited at regular intervals. Through Change Management Approved RFC

3.7 Status accounting Each asset or CI will have one or more discrete states through which it can progress. The significance of each state should be defined in terms of what use can be made of the asset or CI in that state. AMC Equipment under AMC Support WARR Equipment under Warranty Support DEAD Order Loss NOS Not on Support (Temporary Status) Contracts are identified with the warranty start date and end dates to know if the contracts are still live in the system.

3.8 Verification and Review

Verification of equipment happens at the time of acquisition of Asset into support. o For Warranty Support through Installation activity o For AMC Support through Asset Collection Review happens when an incident or service request is reported. This is taken care in the Call Management Process. Contracts database is verified through periodic reports to see how many contracts are live and how many are due for renewal. The trigger for contract renewal is sent 30 days in advance.

4. Configuration Management Plan for Internal CIs

, Processes and Documentations are considered as internal CI. 4.1 Configuration Identification
Wipro-ES Internal & Restricted Page 6

Template Configuration Management Plan

FILE IDENTIFIER VERSION NO. EFFECTIVE DATE

TP_ES_SACM_CMP 0.4 30-04-2009

Processes, Principal Purchase Orders are considered as configuration identification for Internal CIs.

4.2 Naming convention

The Contracts and Principal Purchase Orders are numbered sequentially in the SAP System. Document naming convention to be according to AA.BBB.CCC.

4.3 Attributes of configuration item Name and Version of the documentation. Principal reference details for POs.

4.4 Unique Identifier Process names & document Id are unique identifier for internal CIs. For purchase order unique identifiers are PO No.

4.5 Relationships Relationship s should describe link between Process, Procedure documents & CMS.

4.6 Control Mechanism

Document status control for processes, for e.g Incident management in implementation phase. Document should be checked whether it is in Implementation phase or Initial phase.

4.7 Status accounting

Managing the recording, retrieval and consolidation of the current configuration status and the status of all preceding configurations to confirm information correctness, timeliness, integrity. e.g. Document Release, Implementation Phase, Audit Review etc. Making the status of items under Configuration Management available throughout the lifecycle, e.g. Process reviewed, Documentation Completed.

Wipro-ES

Internal & Restricted

Page 7

Template Configuration Management Plan 4.8 Verification and Review

FILE IDENTIFIER VERSION NO. EFFECTIVE DATE

TP_ES_SACM_CMP 0.4 30-04-2009

Periodic reports are taken from SAP for contract and purchase orders renewals. For Processes the biannually review helps to identify the adherence and streamlining of the processes.

5. Configuration Management Plan for Organizational CIs

The Technical staffs Skill set is considered for organizational CI.

5.1 Configuration Identification Technical staff is identified as o Field Engineer o Resident Engineer o Expert Connect Engineer aligned with skill sets and domain of expertise.

5.2 Naming convention

People are identified in the CMS with the name and unique employee number.

5.3 Attributes of configuration item Attributes for Organizational CIs are experience level & skill sets of technical staff.

5.4 Unique Identifier

Employee Number will be considered as Unique Identifier for technical staffs.

5.5 Relationships

Technical skill sets should be mapped with the domain of expertise.

5.6 Control Mechanism

The CIs are controlled through authorization checks in SAP. The SAP system follows the SOX policy which is audited at regular intervals.
Internal & Restricted Page 8

Wipro-ES

Template Configuration Management Plan

FILE IDENTIFIER VERSION NO. EFFECTIVE DATE

TP_ES_SACM_CMP 0.4 30-04-2009

5.7 Status accounting

The Domain and the Level of Skill is taken under the Status accounting. Ex. Domain SUN, Skill Level L1/L2 etc.

5.8 Verification and Review The verification and review happens with TCAC Technical Competitive Assessment. This happens on a quarterly basis where the skill mappings for technical staffs are reviewed.

Wipro-ES

Internal & Restricted

Page 9