From the Campus Operations edition of September 24, 2026
Purdue IT scales service delivery with TeamDynamix AI triage, VSAs, and procurement automation
Purdue University (TeamDynamix customer story) · Higher education IT service management / multi-campus operations · United States (Purdue campuses and Purdue Global)
- Publisher
- TeamDynamix
- Original publication
- Undated TeamDynamix customer story (retrieved 2026-09-24)
- Source retrieved
- 2026-09-25
What happened
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.
Why it matters
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 and measured results
Opened vendor HTTPS case page with named Purdue process lead and quantified outcome claims. Marketing evidence; independent replication not provided.
Limitations and uncertainty
Vendor-claim evidence class; undated page; 25% and 10× figures not independently audited; process redesign and AI are entangled.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-24; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- 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
- Discovery questions
- 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?
- Value hypothesis
- AI triage plus workflow automation can raise throughput per technician when catalog/KB quality is sufficient—Purdue’s percentages are vendor-reported, not guaranteed.
- Potential engagement
- Six-week ITSM AI readiness assessment: baseline triage time, top deferrable request types, MECM integration feasibility, and VSA pilot scope for one campus.
- Unsupported claims
- Guaranteed 25% faster triage
- Guaranteed 10x procurement capacity
- Labor cost reduction promises
Pre-sales engineering
Role takeaway
- Fit
- Enterprise service management with AI categorization, response suggestions, VSAs, and orchestration to MECM/approvals.
- Architecture and integration
- 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.
- Proof of value
- 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
Role takeaway
- 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.
- Skills and adoption
- Train technicians to treat AI suggestions as drafts; teach catalog owners to maintain campus-scoped KB.
- Governance checkpoints
- Deferral policy limits encoded before go-live
- VSA escalation rules
- Post-launch KB conflict review
- Acceptance criteria
- 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
Implementation considerations
Lighthouse Advisory interpretation across the operating dimensions a public-sector buyer must settle before this evidence becomes a design. Each note answers the question under its heading for this specific source.
Architecture and integration
What must connect, and where does the AI sit in the workflow?
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.
Governance
Who approves, reviews and stays accountable for outcomes?
Fail-forward launches need stakeholder communication loops; document who may grant patch deferrals and how AI suggestions are overridden.
Security and privacy
What data, permissions and controls need testing?
Automated MECM group changes and password/device workflows expand blast radius—require eligibility checks, audit logs, and policy caps on deferrals as described.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
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.
Procurement
What should contracts, pricing and exit terms secure?
ESM platform consolidation (ITSM/ITAM/PPM/AI) can reduce tool sprawl; still require integration and change-management cost beyond license line items.
Operating model
Which teams own the service once it runs?
Shifts service desk toward automation-first for volume and human-for-complexity; requires fail-forward culture and continuous KB governance.
Publication history
- 2026-09-24Campus Operations · Issue 173 resources
Stable resource ID: purdue-teamdynamix-ai-itsm-2026