{"resourceId":"purdue-teamdynamix-ai-itsm-2026","versions":[{"version":"external-3916a7de86290b11bae9d3b0de5b2b65a06a2beea9d42edf0809b9ec1cea62ea","resource":{"id":"purdue-teamdynamix-ai-itsm-2026","title":"Purdue IT scales service delivery with TeamDynamix AI triage, VSAs, and procurement automation","organization":"Purdue University (TeamDynamix customer story)","sector":"Higher education IT service management / multi-campus operations","geography":"United States (Purdue campuses and Purdue Global)","publishedAt":"Undated TeamDynamix customer story (retrieved 2026-09-24)","publicationDate":null,"eventDate":null,"sourceName":"TeamDynamix","sourceLabel":"Vendor customer story on Purdue AI ITSM and automation outcomes","sourceUrl":"https://www.teamdynamix.com/resources/customer-stories/purdue-university-scales-it-service-delivery-with-ai-and-automation/","evidenceClass":"vendor-claim","outcomeClass":"effective","topics":["knowledge-work","infrastructure","operating-model","accessibility-workforce","data-security"],"finding":"TeamDynamix’s Purdue University customer story—quoting IT Process Manager Lead Kevin Morgan—claims campus IT absorbed large volume growth without proportional staffing by combining no-code workflows and AI. A three-person computer-procurement team reportedly handled a tenfold ticket increase and more than a twofold spending increase with no added headcount and no increase in resolution times via guided intake and business-center approvals. Security patch deferrals that once required manual MECM group changes are described as fully automated end-to-end. TeamDynamix AI Assist is credited with 25% faster ticket routing/categorization and day-one response suggestions for new technicians; Virtual Support Agents handle common requests (software install guidance, password resets, device eligibility) with campus-scoped knowledge bases. Closed tickets can draft knowledge articles. Prior platform: BMC Footprints.","sledRelevance":"Large public research IT operations evidence for AI-assisted ITSM, procurement intake, and patch-exception automation—core campus-operations workloads. Why now: never archived; pairs with Emerson’s mid-market build story as the enterprise platform contrast on 2026-09-24.","evidence":"Opened vendor HTTPS case page with named Purdue process lead and quantified outcome claims. Marketing evidence; independent replication not provided.","architectureImplications":"Unify ITSM/ITAM/PPM with integration to MECM and business-approval systems; prefer campus-scoped VSAs over one monolithic bot; treat AI triage as dependent on clean categorization taxonomy and KB hygiene.","governanceImplications":"Fail-forward launches need stakeholder communication loops; document who may grant patch deferrals and how AI suggestions are overridden.","securityPrivacyImplications":"Automated MECM group changes and password/device workflows expand blast radius—require eligibility checks, audit logs, and policy caps on deferrals as described.","caveats":"Vendor-claim evidence class; undated page; 25% and 10× figures not independently audited; process redesign and AI are entangled.","streamIds":["campus-operations"],"roles":{"sales":"Multi-campus CIO and service-management buyers facing roughly twenty-percent annual ticket growth want volume absorption without headcount—not another novelty chatbot. Purdue’s TeamDynamix vendor story centers guided computer-procurement intake, zero-touch patch-deferral automation against MECM, AI Assist triage, and campus-scoped Virtual Support Agents, with claimed twenty-five percent faster routing and tenfold procurement volume on a three-person team. Bound the value hypothesis to ITSM modernization and deflection; do not guarantee copied percentages without a measured baseline on the prospect’s queues.","engineering":"Architecture fit is an enterprise service-management platform with AI categorization, response suggestions, VSAs, and orchestration into MECM and business-center approvals—often replacing or coexisting with legacy ITSM such as Footprints. Prerequisites are a clean service catalog, campus-partitioned knowledge, identity for authenticated VSA actions, and deferral policy encoded as automation rules. Constraints include vendor-reported metrics and undated case material. Proof of value requires before/after triage timing, procurement tickets per FTE, and deferral automation error rates versus the manual baseline.","delivery":"Delivery covers ESM cutover, guided procurement forms, MECM exemption automation with expiry, campus-specific VSAs, and technician AI coaching that treats suggestions as drafts. Ownership belongs to the Service Management Office with CISO concurrence on automated security exceptions. Acceptance should show documented triage-latency change on a pilot queue, successful zero-touch deferrals, and sampled VSA accuracy without cross-campus wrong answers. Risks include incorrect automated security exemptions, poisoned knowledge bases, and metric theater when baselines were never captured."},"roleDetails":{"sales":{"customerProblem":"Ticket volume and complexity grow faster than IT headcount across multi-campus service desks.","stakeholders":["CIO","ITSM process owners","Service desk managers","Endpoint/security operations","Procurement/business centers"],"discoveryQuestions":["What is annual ticket growth and backlog age?","Which request types still require senior touch?","How are patch deferrals governed today?","Is knowledge content campus-scoped or conflicting?"],"valueHypothesis":"AI triage plus workflow automation can raise throughput per technician when catalog/KB quality is sufficient—Purdue’s percentages are vendor-reported, not guaranteed.","potentialEngagement":"Six-week ITSM AI readiness assessment: baseline triage time, top deferrable request types, MECM integration feasibility, and VSA pilot scope for one campus.","unsupportedClaims":["Guaranteed 25% faster triage","Guaranteed 10x procurement capacity","Labor cost reduction promises"]},"engineering":{"fit":"Enterprise service management with AI categorization, response suggestions, VSAs, and orchestration to MECM/approvals.","architectureIntegration":"Replace or coexist with legacy ITSM (Footprints cited); integrate asset DB, business-center approvals, and campus-specific VSA knowledge partitions.","prerequisites":["Service catalog and form taxonomy","KB cleanup","MECM/API access for deferrals","Identity for authenticated VSA actions"],"constraints":["Vendor-reported metrics only","Undated case page","AI quality bounded by training data/KB conflicts"],"security":"Automating MECM exemption groups and password/device flows requires eligibility checks, expiry, and audit trails; least privilege for VSA-triggered changes.","proofOfValue":["A/B or before-after triage time on matched ticket types","Procurement tickets per FTE and resolution time","Deferral automation error rate vs manual baseline"]},"delivery":{"work":"Implement ESM workflows, AI Assist for agents, campus VSAs, procurement guided intake, and MECM deferral automation.","dependencies":["MECM owners","Business center approvers","KB authors per campus","Identity/IAM"],"ownership":"IT Service Management Office with CISO concurrence on automated security exceptions.","skillsAdoption":"Train technicians to treat AI suggestions as drafts; teach catalog owners to maintain campus-scoped KB.","governanceCheckpoints":["Deferral policy limits encoded before go-live","VSA escalation rules","Post-launch KB conflict review"],"acceptanceCriteria":["Documented % change in triage time on pilot queue","Zero-touch deferral path with expiry","Campus VSA accuracy sample above agreed threshold"],"risks":["Incorrect automated security exemptions","Cross-campus wrong answers","Metric theater without baselines"]}},"retrievedAt":"2026-09-24T21:57:05-05:00","enrichedAt":"2026-09-24T21:57:05-05:00","enrichmentBasis":"retrieved source","accessibilityWorkforceImplications":"AI response suggestions aim to make new technicians productive on day one; VSAs may improve after-hours access but must not strand users with campus-wrong answers.","procurementImplications":"ESM platform consolidation (ITSM/ITAM/PPM/AI) can reduce tool sprawl; still require integration and change-management cost beyond license line items.","operatingModelImplications":"Shifts service desk toward automation-first for volume and human-for-complexity; requires fail-forward culture and continuous KB governance.","sourceVerification":{"openedUrl":"https://www.teamdynamix.com/resources/customer-stories/purdue-university-scales-it-service-delivery-with-ai-and-automation/","referenceExcerpt":"AI-assisted triage has contributed to 25% faster ticket routing and categorization.","promptVersion":"sled-research-v4.0","model":null,"basis":"agent-reported inspection"}}}]}