...
1 – Order Submitted - Daily
Requests New requests should be responded to acted on as quickly as possible.
2 – Order Under Review - Weekly
Please try to move orders through this queue as quickly as you canpossible. Check weekly for stalled orders.
3 – Order Quote Issued - Monthly
This queue should be checked at the beginning of each month. Those orders older than 90 days should be cancelled, and the materials (if in G81) should be returned to the owning repositories.
4 – Order Payment Received - Daily
No order should stay in this queue for very longCheck daily for paid orders that are being stored in G-81, and bring any paid orders to the appropriate production area. Ignore all HOU and THE orders, but investigate any other order that remains in this queue for more than two days. First check to make sure that we delivered the order to production areas, and then check with production staff to make sure that the order gets checked in and moved to “5 – Order In Production.”
...
This queue should be checked once per month, before the last day of billing, to make sure that all owning repository codes are correct, that all batch names are properly entered, and for anything that looks off. Doing so before the month-end billing is done will help to avoid difficulties with the billing.
...
Orders are automatically routed to this queue if there is a payment imbalance. It may contain orders that are waiting for refunds to be processed, orders for a project with a special payment arrangement (Ames Foundation), or orders where payments have been entered incorrectly. This last category of order These orders should receive immediate attention, but an immediate solution is not always possible.
Project (Activity) Requests -
...
Monthly
Sorting by different columns can reveal discrepancies in billing codes, batch (Bundle) names, and owning repository (Location), among other things. And sorting by date might uncover old orders that may be duplicates, or might require some investigation.
...
Check this queue once per week to make sure that it accurately reflects the material that we have in-house, waiting to be picked up. We are the ones who route to this queue, and with non-Aeon-using repositories we should route out of it, but Aeon-using repositories will route out of it themselves.