ChemIT's "Monitoring schedule". By month, reminders regarding ChemIT actions not to forget.
Monthly review and/ or do
| Task | Notes |
|---|---|
Review reminders for the specific month.
| See below section, "Annual actions or reminders, by month". |
| Invoicing to department groups, including faculty. | ChemIT's billing to faculty |
| Remedy ticket counts | Remedy snapshot of current tickets |
| Review ticket-related reminders | See below section, "Ticket-related reminders with future dates/ triggers". |
Look over every ticket a month old and older and ensure there is a pertinent "next step" written in the Work Detail tab.
| See section "Review & Additional follow up" at Remedy. Review at the Thursday Group meeting, first one of the month. (Started 4/9/15.) |
ChemIT newsletter OR: Specify months, if not monthly | ChemIT newsletter |
| Stockroom: Verify backups are happening | \\files.cornell.edu\as\chm\DEPT\Dept\Stockroom\QBBackup Files generated by QuickBooks, on exit. Check for recent date-stamps. |
Annual actions or reminders, by month
| Month | Task | Notes |
|---|---|---|
| August | Fall semester starts | |
| August | Renew Dreamspark, when due every 3 years | Expires on 8/31/2016 (as of 12/2014) |
| September | Update Dreamspark CCB user list, to expire 10/15 (8:00AM) of each year (our choice). | Include Faculty, Students (grads only), and Staff (PDA's, but not most CCB staff) |
| September | Review which email lists we are on. Clarify any designated responsibilities to each other, if any. What are expectations regarding whose reading what? | Our lists are parked in a MS Excel file, "ChemIT staff and email lists", located on ChemIT's file server: R:\Chem IT\IT Support http://www.it.cornell.edu/services/elist/howto/user/whichlists.cfm |
May/ June? | License renewal counts and reminders.
Specify licenses and expiration dates. Ex: ChemDraw expires each July. | Process idea: Use web form; compile info centrally.
|
| November | ACL exceptions review ID Finder (if not this month, when?) | ACL: Martin (Hoffmann, Sol), done 6/14 and 11/14. |
| Jan | Staff performance review process begins | |
| Mid-Feb | Faculty hires. Determine if any, and investigate so as to prepare for their arrival, as appropriate. | |
Spring. Specify months (per cluster, if more than one month total) | Cluster and other HPC computers: Planning, learn of anticipated changes. | |
| March | Clusters and other HPC computers: Verify accounts on cluster and other HPC computers. | Ensure folks need access accounts on each system. |
| Late March or early April | Summer student employee recruitment | Student hiring |
| May, into the summer | Inventory check-up (do every other year? Last started Summer 2014, and took ~9 mos!)
Hardware lifecycle reviews: (how orchestrate, if not done ad hoc?)
|
Ticket-related reminders with future dates/ triggers
| Month | Service or ticket information | Who |
|---|---|---|
| May, middle | PhysIT Instruction: Testing center refresh. Was: Incident Number INC000001186777 "We aim to do this refresh after this semester, during the early summer. Thus, we can touch base mid-May to coordinate starting into this project." | OH |
September 1st (Wed)
| PhysIT Admin: Laptop for Kacey, for annual Admissions work and more. Was: Incident Number INC000001280665 "We'll plan on looking at getting a replacement laptop starting in September." | Kacey, MH, OH |