Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

Tip

Depot Buys:

  • Computers from M-Markesite Marketsite provided by UofM U-M Strategic Suppliers under contract or Tech Shop

  • Computer-related hardware, such as

    • Docking Stations

    • Monitors

    • Keyboards & Mice

    • Computer adapters

Warning

Depot Does Not Buy:

  • Software licenses

  • Printer ink or toner

  • Large format plotters or poster printers

  • Furniture or general office supplies

  • Anything from vendors besides Tech Shop or M-Marketsite (such as Amazon or BestBuy)

...

  1. Depot will build one-or-more carts via Tech Shop or M-Marketsite, or request custom quotes from vendors to comprehensively include all requested in-scope items

  2. Depot will Update the Request and send cart/a message with the cart file attached to get approval

  3. Depot will attach a copy of the cart as a PDF or PNG screenshot at this stage or the previous step

  4. Place the Order

  5. Track the Order and provide UpdatesOnce approved, Depot will place the order with all required vendors and ensure the Request reflects this

  6. Depot will track the order and provide updates in the ticket at important milestones or upon request

  7. As hardware arrives, the Depot Inventory team will create ad hoc Tasks for Depot Build and Logistics teams as needed

  8. Once all ordered items have arrived, the Depot Inventory team will Mark Complete the Purchase Task and assign the next and final task in the workflow ⬇️

Depot Verify Task

  • This is the last programmed task in the workflow

  • Any ad hoc tasks will exist until they are Marked Complete 100%

...

Previous Workflow

New & Improved Workflow

NIT was required to provide Build Info for the computer(s) when applicable, but there was no standard location for it in the Request Form to park this information in a consistent and highly visible manner

New Build Info fields have been added to the Technician Visible Only section of the Request Form, so that NIT has a place (with Help Text examples) to put this critical info, and the customer will not be confused by seeing the fields

Depot Inventory staff were hesitant to close the MWS IT Hardware Purchase Task assigned to ITS-DepotInventory when all items had been received because there were no further Depot tasks in the workflow and the team would lose visibility.

New Depot Verify Task allows any Inventory team member to confidently close the Purchase Task with comment, since the New Task will act as a failsafe or sanity check for the Purchaser to retain visibility on the Request through to completion.

Some Unit Approvers and Financial Liaisons would reach out to NIT or Depot to gather qualitative information on the purchases Depot made against shortcodes for their group. This was because the information was not available on the ITS Client Portal.

The Request Info fields on the form have all been marked Visible on the ITS Client Portal - NIT or Depot can add Unit Approvers and Financial Liaisons as Contacts for the Request ad hoc to give them access to view the specific Request in the ITS Client Portal.

Depot Inventory staff would Edit the Request and put the vendor PO Number information in a variety of places, such as the Title or the What to Order section of the Request

New PO Number(s) field added to the Request Form. Field data is Visible in the ITS Client Portal but only TDNext Technicians may Edit the field.