Implementation Phase
Overview
Once a request for change has been defined and approved, it moves into the implementation stage.
Implementation refers to the process of actually performing the task(s) that are involved in the change request. Implementation can may take one or more of the following forms:
- Referring to a existing HelpMaster job(s) to track and manage the implementation
- Logging new job(s) to track and manage the implementation
- Use the Request for Change record to record the implementation
- Do not link or log any jobs, and just record the details of what was done in the "Implementation text box" directly on the change request form
Use
To being the implementation stage, click on the "Start" button on the change record next to the Implementation stage label. This will enable the implementation tab and time-stamp the Change Record with the current date and time, and enter an event in the History tab.
Implementation details for the change can be found on the "Implementation" tab.
Depending on the complexity and scope of the change, the implementation stage can either be very simple, or as complex as you need it to be.
Simple Implementation - No additional job(s) to be logged
A simple change implementation refers to when there are no additional jobs that have been logged, or need to be logged to record and track the change implementation. In this case, you can simply specify details about the implementation in the implementation text box (or not), and this becomes the "Implementation notes" for the change. Using this simple model, all of the implementation details are stored with the change request, and appear on the Implementation tab in the text-box provided.
Job-based implementation
For more complex change implementations, new jobs can be logged that will record and track the change implementation. If existing jobs have already been logged for this purpose, these can also be linked to the change record by dragging them into the jobs listview control.
When a job-based implementation is used, the idea is that existing jobs, or new jobs will contain all of the definition, the workflow and process of a regular job that will be used for the implementation work. These jobs may be based on Job Templates as per usual.
When a change request is created via a Change Request Template, any Job Templates that are linked to the Change Template will be transferred into the change and appear as "jobs to do" on the Implementation tab. Use the toolbar button to convert the job template into a real job.
When implementation jobs are logged from, or linked to a change request, these will need to be completed (closed) before the change can be closed.
Note: The implementation phase of a change is performed in HelpMaster in a functionally similar way to the review phase.
See Also
Feedback
Was this page helpful?
Glad to hear it! Please tell us how we can improve.
Sorry to hear that. Please tell us how we can improve.