{"resourceId":"colorado-state-ai-tool-selector-agent-library-staff-20261109","versions":[{"version":"external-75a7da59e3ed5a6d34e54d1bb12ca2f09499028be70e8fde6f9ea46f102597d9","resource":{"id":"colorado-state-ai-tool-selector-agent-library-staff-20261109","title":"Colorado State's IT division launches a staff AI hub: a 16-tool selector, a four-agent library including an ICT-acquisition guide, and $20-a-month Copilot Premium licences","organization":"Colorado State University, Division of Information Technology","sector":"Higher education IT and administrative operations","geography":"United States (Colorado)","publishedAt":"9 November 2026 (CSU SOURCE news)","publicationDate":"2026-11-09","eventDate":null,"sourceName":"CSU SOURCE","sourceLabel":"University news post by the Division of IT communications","sourceUrl":"https://source.colostate.edu/explore-and-use-ai-with-confidence-resources-for-faculty-and-staff/","evidenceClass":"public-sector-association","outcomeClass":"emerging","topics":["governance-procurement","knowledge-work","operating-model"],"finding":"CSU's Division of IT announced faculty and staff AI resources: a governance and guidance website, an AI tool selector that filters 16 tools by role, data type and task (primary tools are Microsoft Copilot and CSU-GPT, powered by Nebula One), an AI agent library launching with four colleague-built agents (program learning outcomes and curriculum maps, image alt text, and navigating the Information and Communication Technologies acquisition process), Microsoft 365 Copilot Premium licences at $20 per month paid annually by department account number, and fortnightly Ask Microsoft sessions from 16 November 2026 to 17 May 2027. The post closes by telling users to review output, protect university information and keep human judgment central.","sledRelevance":"Shows an administrative-operations pattern that matters now: a central IT group steers staff toward approved tools by role and data type, publishes peer-built agents for procurement navigation, and charges departments per licence rather than buying campus-wide.","evidence":"Institutional announcement only: no usage, accuracy, adoption or cost-outcome data, and no description of how agents are reviewed before listing. Evidence is what the university states it has launched.","architectureImplications":"Tool selector and agent directory sit over an existing Microsoft Copilot plus CSU-GPT (Nebula One) estate; agents are customized assistants for single tasks and are submitted by staff for inclusion.","governanceImplications":"Central guidance site and standards, a tool selector keyed to data type, and a submission route for colleague-built agents imply a curation step, though the post does not describe its review criteria.","securityPrivacyImplications":"Selector filters by data type, and the closing guidance tells staff to protect university information; the post gives no detail on data handling, retention or logging for the agents.","caveats":"Single institutional announcement with no results; licence price and department-charge model may not transfer; the listed agents are mostly teaching or accessibility rather than core back-office; the ICT-acquisition agent's accuracy is unreported.","streamIds":["campus-operations"],"roles":{"sales":"Sales framing: CSU shows a buyer pattern of curated choice rather than one tool for all: a selector by role and data type, a peer agent library and chargeback licences. Interpretation: engage with the IT strategist on bounded enablement and governance services, such as agent review criteria and usage measurement. The post reports launch facts only, so it cannot support claims about productivity, adoption or savings.","engineering":"Engineering framing: this is a catalogue and licensing layer over Copilot and CSU-GPT, not a described architecture. Useful validation topics are how agents are reviewed before listing, what data classes each tool may touch, and how usage is logged. The ICT-acquisition agent is the most operations-relevant item; test it against current procurement policy before trusting answers. Single institution, no results published.","delivery":"Delivery framing: the operating change is an enablement program of selector, agent directory and office hours, owned by Division of IT. Delivery would define listing criteria, retire stale agents, and track adoption and error reports. Treat the post as intent and set acceptance criteria locally, because CSU publishes no outcomes. Keep human review of AI output as an explicit user obligation."},"roleDetails":{"sales":{"customerProblem":"Staff pick AI tools ad hoc, creating fragmented purchasing and unclear data-handling rules.","stakeholders":["CIO or IT director","AI strategist or governance lead","Procurement director","Department business managers"],"discoveryQuestions":["Which AI tools do staff use today, and who approved them?","How would a tool-by-data-type selector map to your data classification?","Who reviews staff-built agents before they are shared?"],"valueHypothesis":"A curated selector and agent directory may reduce ad hoc tool adoption; CSU reports no measured effect.","potentialEngagement":"A short assessment of tool inventory, data classes and agent-listing criteria feeding a staff AI guidance hub.","unsupportedClaims":["Productivity or time savings","Reduced shadow AI","Accuracy of the acquisition-navigation agent"]},"engineering":{"fit":"Campuses with a Microsoft Copilot estate plus a second approved assistant wanting central guidance.","architectureIntegration":"Web selector and agent directory in front of Copilot and CSU-GPT; agents are task-specific assistants.","prerequisites":["Tool inventory","Data classification scheme","Identity and licence management"],"constraints":["Review process for agents not described","Department chargeback model","No usage data published"],"security":"Map each listed tool to permitted data classes and confirm logging and retention for staff-built agents.","proofOfValue":["Share of staff using approved tools","Error reports against the acquisition agent","Licence uptake by department"]},"delivery":{"work":"Stand up guidance, selector and agent directory with listing criteria and support sessions.","dependencies":["Approved tool list","Data classification","Agent authors in business units"],"ownership":"Division of IT with a named AI strategist; business owners per agent.","skillsAdoption":"Office hours and live Q&A sessions for staff.","governanceCheckpoints":["Agent listing review","Periodic retirement of stale agents","Data-class mapping check"],"acceptanceCriteria":["Proposed: every listed agent has a named owner and data classes","Proposed: staff-reported error route in place","Proposed: quarterly adoption report"],"risks":["Stale or inaccurate agents","Unclear data handling","Chargeback discouraging use or driving shadow tools"]}},"retrievedAt":"2026-11-09T21:49:24-06:00","enrichedAt":"2026-11-09T21:49:24-06:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"Staff-built agents and live office hours treat employees as contributors and learners; there is no mention of consultation with staff representatives.","procurementImplications":"Departmental chargeback at $20 per user per month, annual billing, creates a per-unit purchasing route; one listed agent guides staff through ICT acquisition.","operatingModelImplications":"An AI strategist role, office hours and a community agent directory form a light operating model for adoption support.","sourceVerification":{"openedUrl":"https://source.colostate.edu/explore-and-use-ai-with-confidence-resources-for-faculty-and-staff/","referenceExcerpt":"However you use AI, review its output, protect university information and keep human judgment at the center.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}