Implementing a Change

During the implementation phase, implementation task owners receive task assignments when the tasks are ready to be performed. Task assignments are sent in the correct order; an assignment is sent only when any preceding task or tasks are completed. The implementation phase is completed when the owner of the last task in the Change indicates that his or her task has been completed.

About this task

The start of the implementation phase depends on whether the Change has a scheduled start date. If it does not have a scheduled start date, the workflow sets the Change status to INPRG after the authorization phase completes, and starts sending the implementation task assignments. If there is a scheduled start date, and it is in the future, the workflow waits. When the scheduled start date arrives, an escalation sets the status to INPRG, and the implementation begins.

These process steps ensure that implementation tasks are not performed until the Change is scheduled for implementation.

  • Automatically updating CIs, assets, and locations
    A Change results in modifications to configuration items (CIs), assets, locations, or some combination of these. You can specify the updates that will result from a Change at any time before the change is completed. You can update configuration item (CI) attributes, asset attributes, and location attributes.
Parent topic: Managing changes

Feedback