{"resourceId":"utah-chpc-redtail-launch-allocations-newsletter-202611","versions":[{"version":"external-224aa983b64cdbc5414d01036d0ec9819b6d25967f3c59739e70e42cf591706b","resource":{"id":"utah-chpc-redtail-launch-allocations-newsletter-202611","title":"Utah CHPC: Redtail AI Factory formally launched; Winter 2027 allocations open Nov 9 (15k GPU-hours/quarter)","organization":"University of Utah Center for High Performance Computing (CHPC)","sector":"Higher education / state research computing","geography":"United States — Utah (statewide users via University of Utah CHPC)","publishedAt":"November 2026 (CHPC newsletter)","publicationDate":null,"eventDate":"2026-10-06","sourceName":"University of Utah CHPC News","sourceLabel":"University CHPC newsletter","sourceUrl":"https://www.chpc.utah.edu/newsletter_updates/read.php?article=redtail-launch&month=11&year=2026","evidenceClass":"public-sector-association","outcomeClass":"emerging","topics":["infrastructure","governance-procurement","operating-model","accessibility-workforce"],"finding":"CHPC's November 2026 newsletter states Redtail AI Factory formally launched Oct 6, 2026, will move to standard quarterly allocations beginning Jan 1, 2027, opens request window Nov 9–Dec 1, 2026 for Winter 2027, and caps new projects at 15,000 GPU hours and/or 100,000 CPU core hours per quarter, allocated by project rather than research group.","sledRelevance":"Concrete U.S. state/university AI-factory operating model: public–private build (prior archive noted NVIDIA/HPE) now publishing allocation policy, timelines, and project-based governance. Transferable pattern for other states standing up shared GPU factories—limits: Utah-specific portal process; no performance outcomes yet.","evidence":"Launch date Oct 6 at One-U Responsible AI symposium; allocation start Jan 1, 2027; request window Nov 9–Dec 1, 2026; quarterly limit 15,000 GPU hours and/or 100,000 CPU core hours; CPU-only jobs allowed using leftover cores (40 of 104 per node after 64 assigned to GPUs); challenge projects inherit prior six-month allocations.","architectureImplications":"Shared statewide GPU factory needs project-scoped accounting distinct from classic research-group HPC allocations; CPU leftover capacity is an explicit scheduling design choice on GPU nodes.","governanceImplications":"Merit allocation, PI onboarding, and project (not group) resource groups become policy artifacts other SLED sites can copy. Competitive challenge projects coexist with open quarterly calls.","securityPrivacyImplications":"Newsletter does not detail protected-data enclaves; sites copying the model still need separate governed paths for sensitive workloads (Utah's broader AI Factory messaging elsewhere emphasizes sovereign/local control).","caveats":"Operational announcement, not an outcome evaluation. Hardware counts and NVIDIA role are not restated in this newsletter (covered in earlier archived Redtail materials). 'Last Updated' footer noise on page; substance is the allocation calendar.","streamIds":["nvidia","research","campus-operations","state-government"],"roles":{"sales":"Position Utah Redtail as a peer operating reference for state and university shared AI factories—not as an NVIDIA product win story. CHPC has published a real allocation calendar (requests Nov 9–Dec 1, 2026; awards usable Jan 1, 2027) and quarterly GPU-hour caps. Ask prospects how they will allocate scarce GPUs after hardware lands. Avoid inventing performance claims; this source is governance and access process.","engineering":"If advising a similar factory, separate project-based allocation namespaces from classic group allocations, plan CPU-only leftover scheduling on GPU nodes, and automate portal steps for PI → project → compute request. Integrate accounting before general availability.","delivery":"Help clients draft an allocation policy pack: quarterly caps, request windows, challenge-project inheritance, and PI eligibility. Acceptance is a published calendar and portal path tested with a pilot PI—not GPU burn-in alone."},"roleDetails":{"sales":{"customerProblem":"States buying AI factories lack concrete models for fair post-launch GPU allocation.","stakeholders":["State CIO / research officer","University HPC leadership","Faculty PIs","Legislature/oversight"],"discoveryQuestions":["Will allocations be by project or by research group?","What quarterly GPU-hour cap is politically and technically viable?","How will non-flagship campuses get PI eligibility?"],"valueHypothesis":"Publishing caps and calendars early may reduce conflict and idle GPUs after launch.","potentialEngagement":"Allocation-policy design using Utah's calendar as a worked example.","unsupportedClaims":["Measured research outcomes from Redtail","NVIDIA software stack details in this newsletter","Applicability of 15k GPU-hour cap elsewhere without sizing"]},"engineering":{"fit":"Fit for shared university/state GPU factories moving from early access to general allocation.","architectureIntegration":"Project-scoped accounting; GPU and leftover CPU scheduling; portal workflow APIs if available.","prerequisites":["Identity/PI verification","Allocation ledger","Scheduler fairshare tied to awards"],"constraints":["Utah-specific portal UX","No performance data in this source","Challenge projects complicate capacity planning"],"security":"PI and project approval steps are access-control points; audit who can request Redtail-class resources.","proofOfValue":["Pilot PI completes request path before window opens","Scheduler enforces awarded GPU-hour caps"]},"delivery":{"work":"Draft and socialize allocation calendar, caps, and portal SOP before GA.","dependencies":["Governance board approval of caps","Portal change for project-based requests","Comms to statewide PIs"],"ownership":"CHPC-equivalent ops owns allocations; university AI office owns policy narrative.","skillsAdoption":"Train facilitators for PI onboarding outside the flagship campus.","governanceCheckpoints":["Approve quarterly caps","Approve project-vs-group allocation rule"],"acceptanceCriteria":["Proposal: public calendar published ≥30 days before first deadline","Proposal: test request by external-campus PI succeeds"],"risks":["Caps too low spark political pushback","Portal friction blocks non-UofU users","Hardware readiness slips past Jan 1 awards"]}},"retrievedAt":"2026-11-07T04:01:26Z","enrichedAt":"2026-11-07T04:01:26Z","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Statewide researchers, educators, and students are named audiences; access still requires CHPC PI status and portal workflow—capacity building for non-UofU PIs matters for equity.","procurementImplications":"Other jurisdictions can cite Utah's published hour caps and calendar when scoping shared AI-factory chargeback or allocation regimes in contracts.","operatingModelImplications":"Treat formal launch and first open allocation window as distinct milestones; inaugural challenge projects onboard in parallel with Winter 2027 awards.","sourceVerification":{"openedUrl":"https://www.chpc.utah.edu/newsletter_updates/read.php?article=redtail-launch&month=11&year=2026","referenceExcerpt":"We will start accepting Redtail AI Factory allocation requests on Monday, November 9, with a submission deadline of December 1, 2026","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}