Did you know that 80% of downtime in data centers is caused by unplanned change? The truth is that flawed business impact analysis and poor collaboration are usually the leading contributors. What makes it worse is that the demand for changes across the IT infrastructure is increasing at an alarming rate along with increasing complexity driven by virtualization of the IT infrastructure. However, the resources required to manage that change is not increasing. In fact, many virtualization projects don't get past an initial stage because they fail to include change management in their deployment strategy and quickly discover that they are overwhelmed by VM Sprawl.
As you can see here, the change request workflow clearly depicts where Service Manager (SM) and Release Control (RC) play a complimentary role in the process. SM automates and standardizes the process in accordance with ITIL best practices, from request through release and review. RC plays a role at a specific point in the process as a decision-support tool for the CAB. RC ensures the CAB has complete and objective information to review all change requests based upon risk and impact, to detect collisions after the change has already been scheduled.
RC was previously known as Change Control Manager (CCM) prior to summer 2007
The Change Management application is a powerful rules-based work flow system for controlling changes throughout their lifecycle: from initial request to approval, to planning and implementation, and to monitoring and evaluation. An intuitive change calendar provides a global view of all changes in the schedule. Change Management provides powerful phase and task change processes. Highly tailorable to the processes unique to your organization, it accommodates both planned and unplanned changes. Change Management’s internal engine documents changes through time, categorizes, and assigns resources in more effective ways. It allows changes to run in serial or parallel paths with multiple dependencies. Change Management provides comprehensive approval capabilities that ensure agreement among stakeholders about what changes are made, and that changes were made correctly. In addition, it automatically updates configuration management data, so changes to the IT infrastructure are accurately reflected in the CMDB.
Key Benefits
• Manages complex change processes across multiple departments
• Improves response time for change requests
• Enables real-time monitoring of change processes
• Ensures processes are repeatable and meet the needs of the business through reusable and dynamic workflows
• Reduces risk of unplanned outages
We spoke about how ServiceCenter has a powerful workflow engine. Here we see the visualization of that workflow.
The entire process, in this case, rlease managemnet, from beginning to end.
This visual representation allows SC users to quickly identify what is the current task in the process
What needs to be done and what has been done.
The automatic generation of individual tasks for multiple CI s is governed by Config Mgt’s ability to group collections of CI records together. Thus, it is possible to create a group (based on a SM query) such as ‘all desktop machines running XP on the third floor of the London office’. Change management can then spawn a separate change task for each separate desktop machine. The baseline version of each desktop machine can be updated according to a user chosen algorithm.
Approvals can be serialized or defined to take place in parallel