Implementation
After the required approvals are received, the change request moves to the Implementation stage, where the change is implemented through tasks in projects caused by the change.
In this stage, the change manager will lay out the higher-level objectives and break them down into projects caused by change, milestones, and tasks, depending on the work involved.
The required teams are assembled and added to specific tasks and projects, keeping in mind the downtime and other constraints.
The following tabs will be displayed in this stage:
- Details: Displays additional fields configured for the change implementation process. Depending on your change role and permissions, you can spot-edit the fields.
- Tasks: You can add and manage tasks in this stage.
- Associations: Associate requests and projects used to manage the change deployment.
- Click Attach beside Requests Caused by Change/Projects Caused by Change.
- Choose the customer from the filter in the header.
- Select the request/projects and click Associate.
For a customer, you can associate requests and projects created in the customer and the MSP Customer. For the MSP Customer, you can associate requests and projects in the MSP Customer and all customer.
- Approvals: Track the approval levels associated with the Implementation stage.
If no approval is added for the Implementation stage, the Approvals tab will not be visible for this stage after the change moves to the next stage.
- Status Comments: View the status transitions of the change in this stage, along with the comments added during the transitions.