RSIG Software release to ACC: Create Service Manager Ticket
- Dave Alburger
This document presents the step-by-step guide to the process of releasing RSIG to the ACC environment. Keep in mind that there is a separate RSIG UAT environment, which is managed by the RSIG development team. The ACC environment is managed by the server group. Pushing a new version of RSIG to ACC requires creating a ticket in Service Manager (SMGS)
Instructions
Log into Service Manager (SMGS)
http://smgs.tc.gc.ca/sm/index.do
Under Change Management, select changes\Open New Change
Select “Software” in the Category list
The change request screen shows with the change ID and Phase “Change Logging”. Add the required information:
You can refer the SMGS ticket from the previous release for the information. In Initiator section, put the account of the who will coordinate the release. Description will be the summary from the Release Notes document. Fill the “Change Detail” tab information.
Under tab “Impact/Justification”, fill the information
Under Tab “Blackout Plan”, fill the information by copying from previous ticket.
After all required information has been entered, click “Save”, then “Close”. Reopen the ticket. The “Plan” Tab will show, and Phase changed to “Change Review”
Under “Plan” tab, put the tasks for the release. Can refer previous ACC change request and modify.
Click “Save”. All RSIG team members should receive the email of the change request “phase Change Review” email. Forward the email to related team members for reviewing.
Update the Change request based on the feedback if applicable.
Close the ticket, reopen it. The phase will be changed to “Change Assessment & Planning”, and first task was created.
Change management will review and create tasks according to the plan. RSIG team will work on the tasks assigned. Change Coordinator need assign the task to responsible individuals in the team and monitor the progress.