Difference between revisions of "Orders"

From UMIACS
Jump to navigation Jump to search
(Created page with "=Submitting/Creating Order within Jira= ==Important Considerations== * Verbosity is always preferred to lack of critical details. * ORDERS ticket descriptions should cont...")
 
 
(9 intermediate revisions by 5 users not shown)
Line 1: Line 1:
=Submitting/Creating Order within [[Jira]]=
+
The following pages outline the procedures and best practices for creating and requesting orders.
==Important Considerations==
+
 
 +
=Personal Orders=
 +
Please visit [https://umd.service-now.com/itsupport?id=service&service=250341bf3708c20041271f9543990e5a&t=so this page] to order personal equipment or get quotes for Apple or Dell equipment.
 +
 
 +
=UMIACS Orders=
 +
==Requesting Orders Tickets==
 +
===Important Considerations===
 +
* Verbosity is always preferred to lack of critical details.
 +
* Ticket descriptions should contain a list of specific items being ordered (provide direct links) unless you're attaching an official quote. No wishlists or links to carts.
 +
* If it requires priority shipping, please include that in the <b>subject</b> of the email.
 +
 
 +
===Send email to staff===
 +
'''Before proceeding''': If the account you plan on charging is owned by the Computer Science Department, please [https://helpdesk.cs.umd.edu/faq/iribe/equipment-peripherals consult their FAQ] for ordering the equipment you want.
 +
 
 +
Otherwise, if the account you plan on charging is owned by UMIACS: send mail to orders@umiacs.umd.edu.
 +
* Please CC the PI for the KFS account you want to charge.
 +
* <b>In the body of your email:</b>
 +
** Specify the KFS account to charge.
 +
** Specify the items using links or attached quotes and specify the amount of each item.
 +
*** If ordering from numerous vendors:
 +
**** Separate each one in the body of the email.
 +
**** Specify if you want priority shipping per vendor.
 +
 
 +
===When Staff Receives the Ticket===
 +
* As long as the PI is CC'd and all needed information is present, we will go ahead and process the order.
 +
* You will receive an email to pick up the order when it arrives.
 +
 
 +
==Submitting/Creating Order within [[Jira]]==
 +
===Important Considerations===
 
* Verbosity is always preferred to lack of critical details.  
 
* Verbosity is always preferred to lack of critical details.  
 
* ORDERS ticket descriptions should contain a list of specific items being ordered unless you're attaching an official quote. No wishlists or links to carts.
 
* ORDERS ticket descriptions should contain a list of specific items being ordered unless you're attaching an official quote. No wishlists or links to carts.
 
* Always attach supporting documents (like a PDF print-out of a dell e-quote, a vendor-furnished quote, or a screen-shot of a requestor-furnished wishlist or cart.)
 
* Always attach supporting documents (like a PDF print-out of a dell e-quote, a vendor-furnished quote, or a screen-shot of a requestor-furnished wishlist or cart.)
  
==Step-by-step==
+
===Step-by-step===
 
*Create an Issue via the [[Jira]] web interface.
 
*Create an Issue via the [[Jira]] web interface.
**Change the drop-down Project menu to Orders.
+
**Go to https://intranet.umiacs.umd.edu/jira/servicedesk/customer/portals.
**Change the drop-down Issue Type menu to Order.
+
**Select the Order option.
  
You will be presented with the default ordering screen. Here is a very fictitious example:
+
You will be presented with the default ordering screen. Here is a very fictitious example:<br/>
[[Image:ORDERS-main-small.png]]<br><br>
+
Please note that Summary, Reporter, Account and PI are mandatory fields.<br/>
Please note that Summary, Reporter, Account and PI are mandatory fields:
+
[[File:ORDERS_main_new.png]]
  
 
*<b>Requester</b>  
 
*<b>Requester</b>  
Line 25: Line 53:
 
** A PI (Principal Adviser) who has approved the purchase on the FRS.  
 
** A PI (Principal Adviser) who has approved the purchase on the FRS.  
 
** In some cases, multiple PIs can charge to a single FRS.
 
** In some cases, multiple PIs can charge to a single FRS.
* <b>Participants</b>
 
** In most cases, you want to include all interested parties so that they receive updates, tracking, etc.
 
** Jira will not allow you to add a participant without a Jira account. If you need to do this, complete the ticket, wait for the email pertaining to the ticket to arrive in your inbox, and reply to it with any additional participants CC'd.
 
* <b>Labels</b> 
 
** If this is an order that physically needs to go to CBCB, change the label to 'bsb' so that it's easily noticeable for the daily tech.
 
  
 
* <b>Description</b>
 
* <b>Description</b>

Latest revision as of 19:01, 6 January 2021

The following pages outline the procedures and best practices for creating and requesting orders.

Personal Orders

Please visit this page to order personal equipment or get quotes for Apple or Dell equipment.

UMIACS Orders

Requesting Orders Tickets

Important Considerations

  • Verbosity is always preferred to lack of critical details.
  • Ticket descriptions should contain a list of specific items being ordered (provide direct links) unless you're attaching an official quote. No wishlists or links to carts.
  • If it requires priority shipping, please include that in the subject of the email.

Send email to staff

Before proceeding: If the account you plan on charging is owned by the Computer Science Department, please consult their FAQ for ordering the equipment you want.

Otherwise, if the account you plan on charging is owned by UMIACS: send mail to orders@umiacs.umd.edu.

  • Please CC the PI for the KFS account you want to charge.
  • In the body of your email:
    • Specify the KFS account to charge.
    • Specify the items using links or attached quotes and specify the amount of each item.
      • If ordering from numerous vendors:
        • Separate each one in the body of the email.
        • Specify if you want priority shipping per vendor.

When Staff Receives the Ticket

  • As long as the PI is CC'd and all needed information is present, we will go ahead and process the order.
  • You will receive an email to pick up the order when it arrives.

Submitting/Creating Order within Jira

Important Considerations

  • Verbosity is always preferred to lack of critical details.
  • ORDERS ticket descriptions should contain a list of specific items being ordered unless you're attaching an official quote. No wishlists or links to carts.
  • Always attach supporting documents (like a PDF print-out of a dell e-quote, a vendor-furnished quote, or a screen-shot of a requestor-furnished wishlist or cart.)

Step-by-step

You will be presented with the default ordering screen. Here is a very fictitious example:
Please note that Summary, Reporter, Account and PI are mandatory fields.
ORDERS main new.png

  • Requester
    • If the order is being requested by CBCB, MC2, or QuICS, prepend the summary with [CBCB], [MC2], or [QuICS] respectively.
  • Summary
    • This should be of the format "Vendor | Brief Description".
    • If the order must be placed today, this will instead be "PRIORITY TODAY | Vendor | Brief Description".
  • Account
    • This should be the account (FRS) to be charged. Please be as specific as possible (e.g., don't say "DRIF", say "UMIACS DRIF", or "CHIB DRIF", etc.)
    • In the event that a single order has multiple accounts, list them all and specify which items are being charged to what accounts (or what percent of an item is being charged to an account) in the description.
  • PI
    • A PI (Principal Adviser) who has approved the purchase on the FRS.
    • In some cases, multiple PIs can charge to a single FRS.
  • Description
    • Provide a description of what you want to buy or provide it in a comment before you submit your order.
    • When possible, provide a link to the item to be purchased.
    • When purchasing through Amazon or a site that provides fulfillment for third party vendors, please state the specific vendor that is providing the item and at what price. This work to prevent errors caused by ordering from a different vendor when the site auto-updates
    • It's good to be polite with your description. ex - "Hi, please purchase $requestedItems. Here are the links/relevant information: $relevantInformation. Thanks!"