Needs and gaps assessment¶
Supplemental reference · Browse supplements · Current report
Draft framework — no college-wide findings established. The resource inventory and historical provider changes identify questions to examine; they do not establish the size or distribution of college needs.
Prepare and optionally submit a need · Download blank needs register
Questions to investigate¶
| Area | What we need to learn | Useful evidence |
|---|---|---|
| Compute and cloud | Which activities need local devices, interactive sessions, batch jobs, GPUs or hosted models? | Small measured workloads, access delays and required concurrency |
| Software and models | Which licenses, APIs, environments and accessible interfaces are required? | Current agreements, use cases, compatibility and renewal terms |
| Data | Which datasets, rights, metadata, storage and preservation services are missing? | Data inventories, permissions, stewardship and export/restore needs |
| RSEs and support | Which skills and support windows are required, and what capacity is actually available? | Task estimates, existing commitments and service-owner confirmation |
| Research and instruction | How do research schedules, class deadlines and student access differ? | Course/project scenarios and faculty/student perspectives |
| Collaboration | What can be shared or improved before adding infrastructure? | Underused resources, compatible workflows and willing partners |
Assess a reported gap¶
Distinguish not available, not accessible, not known about, not supported, not suitable and not affordable. They require different responses.
For each need, capture who is affected, the activity being blocked, current workaround, timing and evidence. Compare it with a verified resource route. A technical shortage should be distinguished from permissions, onboarding, skills or support barriers.
Summarize responsibly¶
Report which parts of the college and which roles contributed, the number of usable inputs and important missing perspectives. Keep measured demand, self-reported needs, estimates and unanswered questions separate. Do not scale a few examples into college-wide GPU, spending or staffing totals.
Ready for a preliminary draft when…¶
The group has a versioned needs register, a documented account of participation, significant gaps linked to evidence, and a clear list of remaining unknowns. Refine these with faculty, students and resource owners early in Spring 2027.
Review submitted briefs¶
Barney Maccabe and Greg Chism can use the private pilot queue to review explicitly submitted public/synthetic briefs, add a status and notes, and export or delete requests. Contact addresses are self-reported. Submission does not imply approval, capacity or an allocation; internal and restricted information needs an agreed university channel.