Scribd Logo
Upload

Welcome to Scribd!

  • 20 views

    Change Management

    Uploaded by

    Shilpa Hak
    policy

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd

    Change Management

    Uploaded by

    Shilpa Hak
    20 views3 pages
    policy

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    DOCX, PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    policy

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    20 views3 pages

    Change Management

    Uploaded by

    Shilpa Hak
    policy

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as DOCX, PDF, TXT or read online from Scribd
    Download as docx, pdf, or txt
    of 3

    Change Management Policy

    Version: 1.0 February 20, 2012


    REVISION HISTORY: PARTICULARS CREATED VERSION 1.0 REVISION DATE NO. 1 20/2/2012 EDITED BY/ REMARKS

    1.0

    Objective
    To define the policy for managing all infrastructure and production changes to the FGS computing environment. This includes changes to FGS IT managed, servers, systems, networks, databases, and telecommunications.

    2.0

    Policy
    An IT Change Request Form must be completed for all requested changes to the production

    environment of the FGS data center. This covers both dynamic updates and updates that require any of the aforementioned components to be down. Following CIs are primarily under Change control in FGS environment:1. Network Devices (Changes to L3 Switches). 2. Servers Devices 3. Documents Requests for change are to be reviewed and status (approved, pending, denied). If an approver is out of the office, it is their responsibility to delegate the status activity to someone else and inform all the stakeholders of this so as not to negatively impact the change request process. Document change control shall happen over email. Changes shall be categorized as Standard, Minor, Major and Emergency changes and shall be dealt with according to procedures mentioned in the change management Process document. The CMDB records shall be updated following the successful deployment of changes. The Change Manager chairs the Change Advisory Board (CAB), and the CAB is the ultimate decision making authority within the CHM process. Minor and Standard changes do not require CAB involvement.

    Following are the criteria to define a change as a Major change: . Removal of an existing service (Refer service Catalogue for existing Services. Transfer of a service from FGS IT to Customer or a different party. Business risk is high and may impact cash flow. Change and back-out plan are very complex. Change will require extensive planning, building and testing. Change needs significant communication with affected customers in advance and may be required to be discussed at multiple CAB meetings. Customers are affected during and after the change. After the change is executed, there are some functionality changes for the customer Requires a Change request to be submitted by IT Support

    You might also like