【正文】 erspective. This document outlines the operating guidelines for daily activities and processes used by all Change Management stakeholders. AudienceThis document is intended to be used by ABB IS RUN personnel and Service Suppliers. Specifically Service Suppliers will be responsible to align their internal working practices to this document in regards to handling Changes.2. Change Management process DefinitionA Change is defined as the addition, modification or removal of an authorized, planned or supported service or Configuration Item (CI). Changes may occur due to introduction of a new service, modification to an existing service or termination of an existing service in an IT Infrastructure or for fixing a problem in an existing system.Change Management helps organizations understand and work to minimize risks of changes to the IT environment. It is essentially a process for managing the peopleside of change. ScopeChange Management process can be used to track and manage all IT infrastructure changes. A software application change may include enhancements/modifications to existing applications to address identified problems, address business needs or any other requirement. Similarly a hardware change may include changes to puting devices, network ponents, storage devices and other hardware Configuration Items (CI) to replace malfunctioning hardware, increase hardware capacity or other requirements. In other words, changes to all Configuration Items will be governed by this process.  Process Inputs and OutputsUpdated CMDBPIR ReportsApproved and ImplementedChange DocumentationOther ProcessesPIR ReportsBusiness RequirementsChange PoliciesCI Data from CMDBChange Management process Related ProcessesProcess Input to Change Management Output from Change Management Incident Management167。 Trigger for Change167。 Information on changes to CIs for updates of CMDBKnowledge Management167。 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 bureaucracy without promising on controls for implementation of changes Roles and ResponsibilitiesThis section describes roles and responsibilities within Change Management process. Change Requester (ABB, Service Provider)This role is part of current ADONIS process. The Change Requester is the person who creates the change request and submits it for further processing.Major responsibilities include: Identifying parties to be notified and defining notification criteria Assisting Change Requester with change creation167。 Chairing CAB/ECAB meetings167。 Planning and coordinating technical execution of the Change167。 Performing unit amp。 Documenting Change implementation/development results (Post Rollout Documentation)167。 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。 Setting Post Rollout Documentation requirement, if necessary167。 Implementing authorized Changes to the production environment167。 Updating manuals and operating instructions when applicable167。 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。 minor with Critical/High risk) before change deployment167。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。 Reporting on the Key Performance Indicators (KPIs) to evaluate the effectiveness and efficiency of the process167。 Simple and Standard changes should be easy to implement and should not go through multiple levels of approvals167。Add a new DNS record.Software distribution in one country or region by Wipro without ABB involved in specification.WAN/LAN takeover/cutover.Emergency Known and low risk but may include downtime167。 Standard Change must be approved by CAB as routine in order to be included in the standard changes catalogue RFC Minor ChangeA Minor change usually has the following characteristics:167。 Typically no requirements engineering therefore no functional specification amp。 Mostly requested by Service Suppliers and ABB SMEs 167。 Requires CAB process167。 Follows all required steps within the full Change Management workflow, including all required approvals and a controlled development, testing and deploymentNOTE: IncidentInitiated change is triggered from Incident and subject to categorization of a Minor or Major Change based on structured Change Eva