MiWorkspace: Onboarding - Create a Request from a Catalog Order

Overview

This step-by-step procedure is designed for ITS Neighborhood IT and describes how to create a Request in ServiceLink from a Catalog order for MiWorkspace onboarding.

To align with the Service Level Expectation (SLE), a MiWorkspace onboarding request must be completed within 72 hours from when the request was submitted. If you are waiting for a uniqname to be created, waiting on hardware to be provisioned, or the start date is out in the future, put the task in Pending status to stop the clock and allow extra time for these tasks to be completed.

https://umichprod.service-now.com > Service Catalog > Catalog

Step-by-Step Procedure

  1. Click MiWorkspace Onboarding.

    service catalog

  2. Enter, select, or lookup lookup icon values in the applicable fields.

    Notes:

    • Expand More information as needed for applicable fields.
    • Selecting Yes in the Does Employee Need Hardware? and/or Is Employee Using a Shared Machine? fields will enable additional fields.

     

  3. If applicable, check the Hiring Manager or Unit Contact notification boxes.
  4. If applicable, enter Onboarding Notes.
  5. Click Submit.
  6. Click the Request Number.
  7. Click the RITM#.
  8. Once the Request Item opens, scroll to the bottom and click on the Task link under the Catalog Tasks section.

Note: If you need to leave the task at any point, click Update to save progress.

  1. Enter or lookup lookup icon the applicable Neighborhood IT group in the Assignment group.
  2. Enter your name in the Assigned to field.
  3. Enter, select, or lookup lookup icon values for applicable fields in the Variables section.

    Notes:

    • Expand More information as needed for applicable fields.
    • Selecting Yes in the Does Employee Need Hardware? and/or Is Employee Using a Shared Machine? field(s) will enable additional fields.

     

  4. Enter applicable Work notes or Additional comments (Customer visible).
  5. Click Close Task.

MiWorkspace Onboarding Task Workflow

Note: If no hardware is needed, all applicable tasks are kicked off in parallel.

oboarding task workflow: The next set of tasks will all be kicked off in parallel if the answer to the questions are Yes:
•	Set Executive Support Flag in ServiceLink (assigned to Access and Accounts)
•	Provision Crashplan (assigned to Access and Accounts)
•	Prep or Request Loaner
•	Set up Universal Home Directory
•	Order Hardware
Note: Not all tasks will have to be closed in order for new tasks to be kicked off.
Once the  Order Hardware task has been closed the next tasks to be kicked off are:
•	Prestage/Build Workstation
•	Identify Hardware/Tag for Inventory
Both Prestage/Build Workstation and Identify Hardware/Tag for Inventory have to be closed to have the next task kicked off:
•	Hand Install Apps, Provision Access, and Unit Specific Activities
After Identify Hardware / Tag for Inventory, Coordinate Software License, and Hand Install Apps, Provisions Access, and Unit Specific Activities tasks are closed these remaining tasks will be kicked off:
•	Restore User Data from User State Migration
•	Deliver to Customer / Day 1 Orientation
Note:  If Depot is providing hardware there is an additional step to delivery device to NIT before Hand Install Apps, Provision Access, and Unit Specific Act ivies. 
Note:  When No hardware is needed all tasks are kicked off in parallel.

Last Updated: 
Tuesday, May 2, 2017