From the Campus Operations edition of October 29, 2026
University at Buffalo's pilot of an AI procurement assistant inside its eProcurement system ends this month, with user ratings deciding its future
University at Buffalo (SUNY) · Higher education procurement · New York, United States
- Publisher
- University at Buffalo Administrative Services Gateway
- Original publication
- Undated web page; pilot stated to run until the end of October 2026
- Source retrieved
- 2026-10-30
What happened
UB is piloting JAI, an AI assistant built into its JAGGAER-based ShopBlue procurement system, until the end of October 2026. It answers from UB-approved policies and training, explains approval workflows, and can show a user's recent purchase orders and receivers. Users rate every response, and UB says the evaluation will decide broader availability. The page states JAI complements rather than replaces existing support channels.
Why it matters
Embedded vendor AI in procurement suites is arriving on many campuses; UB's pilot ends now, so its go or no-go decision is a near-term signal. Results are not yet public, limiting what can be concluded.
Evidence and measured results
Official procurement page describing scope and evaluation process; no results yet.
Limitations and uncertainty
No results, criteria or costs published; page undated; vendor co-developed the pilot.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-10-29; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Campuses must decide whether embedded procurement AI is worth continuing after a short pilot.
- Stakeholders
- Procurement director
- Controller
- Procurement systems manager
- Chief information officer
- Discovery questions
- What criteria decide continuation?
- Does the assistant reduce help requests?
- Is there an added license cost?
- Value hypothesis
- Interpretation: a clear evaluation could support a renewal decision; no value is shown yet.
- Potential engagement
- A bounded evaluation framework for an embedded procurement assistant pilot.
- Unsupported claims
- Time savings
- Fewer procurement help tickets
- Accuracy of answers
Pre-sales engineering
Role takeaway
- Fit
- Fits campuses on procurement suites that offer embedded AI assistants.
- Architecture and integration
- Assistant within the eProcurement suite grounded in institutional content with read access to purchase records.
- Prerequisites
- Curated policy content
- Role-based access in the suite
- Rating data export
- Constraints
- Controls undocumented
- Vendor-hosted feature
- Security
- Assistant must respect suite permissions when showing purchase orders and receivers.
- Proof of value
- Test that users see only their own records
- Review a sample of rated answers against policy
Delivery
Role takeaway
- Work
- Run a time-boxed evaluation of an embedded procurement assistant.
- Dependencies
- Vendor cooperation
- Procurement content owners
- User pilot group
- Ownership
- Procurement systems and operations team.
- Skills and adoption
- Users trained to rate answers and suggest questions.
- Governance checkpoints
- Evaluation criteria set before pilot
- Expert review of rated answers
- Go or no-go decision documented
- Acceptance criteria
- Proposed: at least 90% of sampled answers match policy
- Proposed: measurable drop in procurement help requests
- Risks
- Ratings mistaken for accuracy
- Stale policy content
- Unclear cost after pilot
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?
Assistant embedded in the procurement suite with read access to a user's purchase orders and receivers.
Governance
Who approves, reviews and stays accountable for outcomes?
Time-boxed pilot with per-response ratings feeding a decision on availability.
Security and privacy
What data, permissions and controls need testing?
Read access to purchasing records means answers must respect each user's permissions; the page does not detail controls.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Positioned as complementing procurement staff support, not replacing it.
Procurement
What should contracts, pricing and exit terms secure?
Vendor feature in an existing contract; cost of continued use not stated.
Operating model
Which teams own the service once it runs?
Procurement systems staff own the evaluation and its decision.
Publication history
- 2026-10-29Campus Operations · Issue 525 resources
Stable resource ID: ub-jaggaer-jai-procurement-assistant-pilot-evaluation-202610