Excerpt |
---|
ChemIT's "Monitoring schedule". By month, reminders regarding ChemIT actions not to forget. |
Table of Contents |
---|
Monthly review and/ or do
...
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. |
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 |
---|---|---|
September 1st (Wed)
| PhysIT Admin: Laptop for Kacey, for annual Admissions work and more | Kacey, MH, OH |