Planning for Changes
Before you start processing Changes in your data center, an administrator can perform a
number of operations that will help you manage the Changes more effectively. The administrator can
return to these operations after Changes are underway; at any time, for example, workflows, job
plans, response plans, and blackout periods can be deleted or modified. However, it is strongly
recommended that an administrator perform these steps to initially set up your environment for
efficiently managing Changes.
Managing workflows
A process workflow is a predefined series of steps that result in the completion of a Change, a task, or a series of tasks. The Change Management component uses workflows in three ways: to direct the progression of an entire Change process, start to finish; to manage process requests; and to automate or assist the performance of a task.
Managing job plans
You use job plans to structure the scheduled series of implementation tasks that are performed during a Change implementation phase. Conceptually, a job plan is a process template for the Change process. This template contains several different specifications that help structure and manage a Change. Job plans are focused on tasks, with Change assessors and approvers listed separately.
Managing response plans
Response plans are used to automatically set values on a Change. For example, they can be used to select the correct job plans for your Changes. This capability is useful for defining how different types of Changes will be handled. The use of response plans results in predictable, repeatable behavior in the processing of Change requests, because the response plans ensure that similar Changes always behave the same way.
Managing blackout periods
You can establish time periods during which Change Owners must be cautious in implementing Changes. You use the Blackout Periods application to create, modify, and delete these time periods.
Managing change windows
Change windows specify the time periods during which CIs can be taken out of service for change implementation. Change windows are created in the Change Window Calendars application. You can create a new Change Window Calendar in which to define change windows, and you can modify or delete existing Change Window Calendars. You cannot create Change Window Calendars for assets.
Managing impact analysis settings
Impact analysis is the process of identifying and analyzing which systems, applications, or other configuration items (CIs) will be affected by a proposed Change. For example, if the Change is to add memory to an application server, the applications that use that server will have an outage when the server is offline. You can configure rules and criteria that determine how impact analyses are run.
Managing escalations
Escalations enable you to automatically monitor critical steps in a Change process. With escalations, you can ensure that critical tasks are completed on time, change the status or owner of a record, or cause other automated actions, such as notifications, to occur. If tasks are not completed promptly, they time out, and you can use escalations to assign the tasks to other people to prevent work backlogs.
Managing display of the Specifications table
In the Changes application, the Specifications table displays attributes that are associated with a Change classification or with a Change. Users specify attribute values in the table. By default, this product shows the table only if a classification or a Change has associated attributes. You can configure the application to display the table regardless of whether there are associated attributes.
Enabling or disabling the New Change dialog
When a user selects the New Change action, a dialog can be displayed in which to enter basic information for the new record. After the information is submitted, the record is saved. You can modify a system property that determines whether the New Change dialog is displayed.