【正文】 ChangeA Minor change usually has the following characteristics:167。 Uses a fixed execution plan or is fully automated167。 Known and low risk but may include downtime167。VM Disc extension to 1 TB due to no free space on SQL instance.Router exchange due to failure.Router reboot.Change of configuration.Table 3 Change Types examples Standard ChangeA preapproved change which has the following characteristics:167。WAN/LAN takeover/cutover.EmergencySkybox amendment.MajorNew GPO deployed globally.Printing outage in whole country.Worldwide deployment of a software that significantly affects user.Desktops and is integrating with other systems.Add a new DNS record.Software distribution in one country or region by Wipro without ABB involved in specification.Delete a Shared mailbox.There are no standard changes implemented in Service Catalogue as of yet. These could be: Software packaging Addition of Network Printer in the officeThere are no standard changes implemented in Service Catalogue as of yet.There are no standard changes implemented in Service Catalogue as of yet.MinorOU creation on every Country subOU.Software distribution in one country or region by Wipro with ABB involved in its specification.Add new VM capacity (RAM, Drive, storage). Simple and Standard changes should be easy to implement and should not go through multiple levels of approvals167。 All changes are not equal and need to be treated differently167。 Reporting on the Key Performance Indicators (KPIs) to evaluate the effectiveness and efficiency of the process167。 Approving Changes during CAB\ECAB meetingProcess RoleOrganizational RoleServiceNow FieldTechnical Service Owner (ABB)Tower Control LeadChange Task Assignment Group/ Change Task Assignee Change Process Manager (ABB)This role is not part of current ADONIS process. Change Process Manager holds operational responsibility for managing the whole process.Major responsibilities include:167。A ManagersApprover Group member Technical Service Owner (ABB)This role is not part of current ADONIS process. Technical Service Owner holds the responsibility for managing the Tower Control.Major responsibilities include:167。 Acts as a Single Point of Contact for munication to and from Business stakeholdersProcess RoleOrganizational RoleServiceNow FieldSDamp。 minor with Critical/High risk) before change deployment167。A function shall be involved in the approval process before the change is deployed into production. This approach ensures consistent decision making processes and allows for a proactive munication towards the ABB IS RUN customers.Major responsibilities include:167。 Evaluating and approving changes during PreApproval, Functional Approval and for SOX related changesProcess RoleOrganizational RoleServiceNow FieldCI OwnerSystem/Application OwnerService Owner based on Business Service SDamp。 Verifying the Configuration Information is updated as appropriateProcess RoleOrganizational RoleServiceNow FieldBTL Deployment Manager (Service Provider)Service ProviderChange Task Assignment Group/ Change Task Assignee CI OwnerThis role is part of current ADONIS process. Service Owner is responsible for individual Business Service.Major responsibilities include:167。 Updating manuals and operating instructions when applicable167。 Attempting to resolve any issues arising during the deployment167。 Implementing authorized Changes to the production environment167。 Defining implementation approach for deployment activities167。 Setting Post Rollout Documentation requirement, if necessary167。 Reviewing change before change deployment from technical point of view167。 Verifying the update of the CMDB to reflect the implemented ChangeProcess RoleOrganizational RoleServiceNow FieldBTL Change Manager (Service Provider)Service ProviderChange Assignment Group/Change Assignee OTL Change SME (ABB)This role is part of current ADONIS process. OTL Change SME is the one responsible to technically review and assess the change before it goes to production environment.Major responsibilities include:167。 Coordinating the implementation/development of the Change167。 Documenting Change implementation/development results (Post Rollout Documentation)167。 Conducting Post Implementation Review to verify implementation when required167。 Performing unit amp。 Attempting to resolve any issues with the implementation/development167。 Planning and coordinating technical execution of the Change167。 Managing escalations relating to a Change 167。 Chairing CAB/ECAB meetings167。 Confirming Change Planning done by BTL Change Manager167。 Assisting Change Requester with change creation167。 Monitoring the lifecycle of an assigned Change167。 Identifying parties to be notified and defining notification criteria Obtaining additional information, as needed, for submitted Change Requests Updates to Service CatalogueTable 1Related Processes Process ObjectivesThe goal of Change Management process is to maintain the integrity of the controlled IS environment. Change Management is the “gateway” through which every change must pass on its way to the controlled environment. Change Management process primarily aims at ensuring the implementation of changes with minimum risk to the business. The objectives of Change Management process are: ? Ensure efficient and prompt handling of changes? Provide accurate and regular information about all planned changes? Ensure consistent procedures for change implementation to minimize the risk of failure? Minimize Incidents resulting from the introduction of Changes? Ensure risk and impact analysis to assess risk of changes and minimize risk of implementation? Monitor and track the lifecycle of all changes? Ensure proper categorization of changes and that proper procedures are followed for each type of change? Reduce