1. Navigate to https://isdservicedesk.corp.mcb-group.bnk/
or via https://myapps.microsoft.com
2. Click on new request
3. Navigate to “Activity and Change Control Form v1” under the category Changes
4.Please fill the mandatory fields , such as :
· Requester |
· Change Type (Choose between Standard , Normal ,Emergency or Expedited) |
· Ticket type (Problem log (PL) System Service Request (SSR) or Operational request (OR) |
· Ticket number (Helpdesk ticketing system) |
· Pre-approved task (Applicable only for Business as usual : Standard tickets) |
· ACC Description : Describe of the activity (avoid using technical terms, acronyms, and ticket numbers in the) |
· Reason for ACC : Business reason of the request |
· Category |
· Scheduled Start date and End date |
· Impact and Risk (If impact yes, please fill the Outage start time and end time) |
· Change Environment (Production, UAT or Development) |
· Password required (Please choose Yes if privilege access is required to execute the change control) |
· Group and technician (Please assign to the team that should execute the task) |
· Confirmation of Business communication and Confirmation Test was executed |
Where the requester must choose between the options "Yes" or "No":
Mandatory field | Option Selected | What is expected from the requester ? |
Confirmation of business communication | Yes | Attach the business communication evidence to the Service Desk ticket |
Confirmation that test was executed | Yes | Attach the test evidence to the Service Desk ticket (e.g., Sign-off of the test performed in the UAT environment) |
Confirmation of business communication | No | Provide a detailed explanation of why business communication is not necessary
|
Confirmation that test was executed | No | Provide a detailed reason why testing was not performed prior to the changes
|
5. Please attach the mandatory documentation , such as :
5.1 Action log or implementation plan (Describe the environment that will be accessed, and which steps will be executed based on a detailed plan) |
5.2 Sign off or Proof of testing. |
5.3 Impact Document if available |
5.4 Business owner approval or proof of communication with the business (Applicable for items will business impact) |
5.5 Related Helpdesk ticket |
Note : Above requirements doesn't apply for Emergency requests that require immediate action to fix or prevent a major user, customer or operational impact
6. Add request and wait for the chain of approvals based on the requested ticket.