Skip to content

Time & funding

Supplemental reference · Browse supplements · Current report

Supporting compute pilot. These DS/MLIS proposals retain their own $0 cash and Greg’s four-hour weekly envelope. They are not college-wide capacity findings or the working group’s selected solution. Return to working-group deliverables →

Greg: 4 hours/week total. Cash budget: $0. Those hours cover all duties, including EduCloud. The earlier two-course workload does not fit this capacity. Its estimates remain visible below for rescoping, not as committed time.

Across the modeled 23 weeks, available time is at most 92 hours, compared with 230 hours in the earlier workload illustration: a 138-hour gap before other duties. Reduce scope or confirm distinct support; no ORAI staffing or grant is assumed.

Function Potential hours over 23 weeks
Allocation and coordination 22.0
Benchmark and component work 34.0
Service operations 78
Instructional design and accessibility 14.5
Data, rights and recovery review 25
EduCloud grant preparation 23
Planning and incident buffer 33.5
  • Two course support TAs: 102 potential hours over the modeled period; separate from Greg.
  • Two course leads: 70 potential hours over the modeled period; separate from Greg.

Course leads need no salary. No college sponsor or finance role is included. Regular teaching/grading is outside these added pilot hours. No appointment, funding or backup commitment is established by this plan.

Grant dependencies

Any paid need must be covered by confirmed eligible grant funding under the EduCloud plan. Separate development, training, evaluation and recurring operations; avoid double counting hours or assuming that an application is an award. An allocation supplies resources, not automatically staffing or durable managed hosting.

Detailed hours CSV · Grant work packages · Scope support demand

If the hours do not fit: reduce the pilot scope or secure actual additional support before class. The independent backup remains unfilled.