Computing resources¶
Resources we can build on¶
Start with college and campus compute, software, data services and technical expertise. The resource inventory brings access, costs, contacts and limitations together. Match a service to the activity and confirm capacity with its owner.
The growing gap¶
Demand spans compute, software, data and the people who make them usable. Meanwhile, some free services have closed, shortened access or tightened limits. Useful options remain, but a previous semester’s setup is no longer a sufficient continuity plan. The report distinguishes documented changes from unknowns; it does not measure a college-wide shortfall.
The opportunity¶
Clarify access, onboarding and support before duplicating services.
Capture the activity, barriers and support needs. Technical quantities can remain unknown.
Compare reusable environments, shared expertise, partnerships and allocation-backed services.
For the instructional pilot, a measured ACCESS CPU + GPU allocation is the proposed route; eligible NAIRR Classroom pilots may complement it. Awards, operations and classroom access still need confirmation. The group can compare this with other shared-service approaches.
Next: scope an ORAI AI pilot¶
Greg Chism plans to draft a focused proposal for ORAI AI Innovation Pilots, to showcase ORAI tools alongside his infrastructure components in an AI-native classroom. A separate proposal will be drafted next. Available time: four hours/week total, shared across these duties and EduCloud. The next draft will define one proof of concept, ready data, responsibilities and handoff.
The program describes eight weeks of execution after assessment. Fit, acceptance and staff support are unconfirmed; this is not ongoing classroom support. The earlier two-course workload exceeds available time and needs rescoping.
Working-group context¶
End of Fall 2026: preliminary inventory, needs assessment, approaches and recommendations. Early Spring 2027: refinement and intra-college circulation. Working materials →