Skip to content

Before required classroom use

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 →

All 13 admission checks are planned, not run. A working notebook or award alone does not establish classroom readiness. Open a check to see the evidence and stop condition.

1. Operations · scope

Status: Planned — not run

Confirm eligible PI, actual courses/leads, Greg’s four-hour/week total envelope, separate TA/lead hours, distinct backup and full-term coverage. No cash budget; fund any necessary expenses only from a confirmed eligible grant.

Owner / timing: Greg + course leads / Before request

Evidence: Named owners, realistic hours log, separate support commitments and confirmed grant/allowable-cost evidence if paid resources are needed.

Stop if: Counting four hours per role, assuming grant award, missing backup, or unfunded necessary spending.

2. Teaching · benchmark

Status: Planned — not run

Complete campus AWS CPU component tests and free-resource GPU benchmarks; retain failures, correctness, measured memory/runtime, checkpoint/export results and workload scope. Reproduce representative GPU work on awarded ACCESS hardware before class.

Owner / timing: Greg (operator) + course leads / Before student canary / request sizing

Evidence: Versioned workload/environment manifest, dataset checksums, dated result rows, actual GPU/account limits and target-resource comparison. No measurements recorded yet.

Stop if: Unmeasured GPU amounts, treating free quota as guaranteed classroom capacity, or assuming benchmark timings transfer unchanged to ACCESS.

3. Access · provider

Status: Planned — not run

Confirm ACCESS CPU/GPU allocation, separate resource exchanges, actual quotas/storage, course dates and project structure; campus AWS stays test-only. If CloudBank is selected, confirm service type, CPU/GPU availability and accounting.

Owner / timing: Allocation lead + selected ACCESS provider / Before request / gate to class

Evidence: Provider response and approved award/resource configuration, recorded privately.

Stop if: Assuming unspecified limits, general broker terms or automatic renewal.

4. Access · accounts

Status: Planned — not run

Every approved student/staff test account authenticates; student A cannot read/write student B files or instructor grading areas; removal/revocation works.

Owner / timing: Operator + course leads / Canary; repeat before week 1

Evidence: Access matrix and dated test results; no passwords or roster identifiers in public reports.

Stop if: Access leakage, shared credentials or unverified removal.

5. Teaching · software

Status: Planned — not run

Both complete representative assignments run on the approved CPU image from fresh workspaces; no paid account or GPU is required. Pin the approved environment and input checksums.

Owner / timing: Each course lead / Canary

Evidence: Clean-run outputs, environment manifest, resource measurements and a known-good baseline.

Stop if: Missing packages, memory failure, unapproved app or required GPU dependency.

6. Access · capacity

Status: Planned — not run

With provider permission, rehearse 80 simultaneous students plus agreed staff use in three representative sessions. Proposed p95 login-to-workspace ≤5 minutes; no unresolved assignment-blocking launch failure.

Owner / timing: Operator + provider / 2–4 weeks before term

Evidence: Dated latency distribution, workspace success count, quota/usage forecast and provider-agreed concurrency.

Stop if: No permission/capacity evidence; peak spec exceeds awarded limits.

7. Teaching · save

Status: Planned — not run

Edit, save, stop/restart and recover a notebook/data package; verify filesystem location and retention. Export and re-import it into the CPU fallback.

Owner / timing: Course leads + TAs / Canary; repeat after image update

Evidence: Saved-file checksums, restart/export receipt and fresh-environment reopen.

Stop if: Student work depends on an unsaved session or cannot be exported.

8. Teaching · grades

Status: Planned — not run

Distribute a versioned assignment, collect it, reconcile all test submissions, preserve student authorship and instructor judgment, and import/export a test grade receipt through the approved LMS workflow. If Classroom 50 is selected, verify Team/Enterprise organization eligibility, permissions, billing controls and an independent export; Codespaces and Actions quotas remain separate.

Owner / timing: Course leads / Before graded use

Evidence: Submission manifest and grade reconciliation results in the approved institutional destination. Classroom 50 canary and quota/fallback records if selected; no additional Codespaces allocation assumed.

Stop if: A leaderboard/auto-score substitutes for the authoritative grade, or a missing receipt goes undetected.

9. Operations · data

Status: Planned — not run

Approve provider and backup data destinations, lawful/appropriate datasets, access roles and retention. Keep grades/rosters in the approved LMS/institutional systems; publish only aggregate results.

Owner / timing: IT/privacy reviewer + Libraries / Before student data

Evidence: Approved data map, rights notes, retention schedule and service/accessibility review.

Stop if: Assuming research storage or this public site is approved for private student records.

10. Teaching · accessibility

Status: Planned — not run

Rehearse keyboard and screen-reader access, readable instructions and equivalent small-data CPU/offline activity; resolve barriers in essential workflows.

Owner / timing: Greg (design coordination) + course leads / Before course admission

Evidence: User/task review and course-lead sign-off, with accommodations and fallback instructions.

Stop if: An essential assessed activity is inaccessible without an equivalent route.

11. Recovery · recovery

Status: Planned — not run

Make independent copies in approved destinations and restore onto a different host/environment. Proposed RPO ≤24 hours and RTO ≤one business day; measure both.

Owner / timing: Primary + backup operators / Before course admission

Evidence: Restore logs, independent file checksums, recovery timing and backup-operator runbook rehearsal.

Stop if: No independent copy or unmeasured recovery; relying only on snapshots or cold archival retrieval.

12. Operations · support

Status: Planned — not run

Publish actual staffed help windows and escalation route; rehearse an outage with CPU/small-data fallback. Proposed first response within one staffed business day; do not promise 24/7 support. Keep actual Greg hours within four/week across all duties; reduce scope when demand exceeds coverage.

Owner / timing: Owner + TAs + operators / Before week 1; weekly

Evidence: Coverage schedule, ticket routing, outage exercise and fallback delivery proof.

Stop if: Unfunded coverage, unreachable operator or missed class deadline without substitution.

13. Recovery · exit

Status: Planned — not run

Schedule alerts 60/30/14/7 days before expiry; decide continuation at least 30 days before. Rehearse learner/grade export, retention and deletion; verify closure on the approved dates.

Owner / timing: Service owner + course leads + Libraries / Before start; execute near term end

Evidence: End-of-term runbook, sample exports, provider confirmation of exit window and deletion/renewal decision.

Stop if: Relying on grace periods, unconfirmed education extension or archival deposits of private coursework.

Download readiness CSV · Return to stages

This page records the plan. Selecting or opening a check does not approve it or update readiness.