Working with Change Enablement

in , a change is defined as a change in the it environment, such as a software update or introducing a new server change enablement is the process of assessing and detecting any impact and potential risk that a proposed change could inflict on your organization the goal of change enablement is to ensure that standardized methods and procedures are used to process change requests successful change enablement minimizes the impact of change related issues and improves daily operations changes are implemented through configuration items changes can be used with incidents, problems, or releases a change request is a formal request for the implementation of a change a change request, specifying the details of a proposed change, must be submitted for every non standard change a change can result from two factors problems that require resolution proactive business decisions that hope to reduce cost, improve service, or improve organization operations changes are carefully controlled only users in authorized roles can work with the full change process most users only interact with changes when they submit change requests see change lifecycle docid\ lqqe50njhxup5ixakalrr for information about the lifecycle of a change request and the different states that a change request moves through see change enablement roles and tasks docid\ ldtgg1y2rrjuyhkdxbtrz for information about s and their roles viewing change requests s, change implementers, and change approvers can view change requests and the tasks that are assigned to them log in to open the change workspace a list of change requests is displayed open a change request record to view its details