...
Customers (Requestors) submitting this form may be Unit Admins or Hiring Managers
The Request ticket is assigned automatically via the workflow to the NIT Support Group for the Requestor’s Asset (which is an attribute on the Asset’s Location)
All MiWorkspace Onboardings will have at least these 3 tasks and 1 Choice Step:
Prep for Day-1 task assigned to ITS-NIT (matches Request’s Responsible Group)
Day-1 Delivery task assigned to ITS-NIT (matches Request’s Responsible Group)
Provision Crashplan task assigned to ITS-SCComputeandCollabSupport
Source Hardware choice step assigned ITS-NIT (matches Request’s Responsible Group)
Unit - select this option if the unit or NIT already has the equipment and does not need Depot
Depot or New - select this option if any hardware is needed from Depot
May include items to be ordered, items from stock, or a mix of both
...
Depot requires the following information from NIT to proceed with their piece:
List of items to be ordered & quantities needed
List of items to pull from stock at Depot & quantities needed
Specs of the computer to be ordered or pulled from stock
Hardware purchase Unit Approver & Shortcode (if known)
Build group for the computer (Otto or Izzy group)
When How to trigger Depot once you’ve gathered the above information:
[Update] the NIT Verify Hardware task
Set the Percent Complete to 100% (this marks the task complete upon save)
Comment all of the info you’ve gathered
[Save] the task update (comment will be automatically posted to the Request feed too)
| Note |
|---|
If Depot does not receive sufficient information when their task generates, the Inventory, Build, and Logistics teams will be reaching out to clarify all of this information, creating unnecessary delays |
Changes from Previous WF & Other Notes
...