From the Campus Operations edition of November 1, 2026
University of North Dakota opens its Nebula UND AI pilot in November 2026 with a PCard audit and research-award management agent among first projects
University of North Dakota · Higher education IT, procurement and research administration · North Dakota, United States
- Publisher
- University of North Dakota University Information Technology
- Original publication
- Undated pilot page (page metadata last modified 30 October 2026); pilot stated to launch November 2026
- Source retrieved
- 2026-11-02
What happened
UND's IT organisation says its Nebula UND AI pilot launches in November 2026, by invitation or approved project, to test whether the platform delivers value and can be supported at scale. It evaluates capabilities, security and responsible use, user support, and costs and infrastructure. Listed projects include a planned Procurement PCard audit that would organise transaction data, flag missing statements and discrepancies, and direct staff to items needing review while final decisions stay with human reviewers, and an in-progress agent to help manage about 160 active research awards.
Why it matters
Why now: the pilot's stated launch month began on 1 November. It is a public-university example of piloting AI in finance controls and research administration with explicit scale-up criteria rather than a campus-wide license.
Evidence and measured results
Official pilot page describing evaluation criteria and project goals; no results, metrics or vendor detail.
Limitations and uncertainty
Pilot design only; PCard project is planned, not built; no publication date, vendor, model or results.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-11-02; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Procurement and research administration staff spend time manually reviewing transactions and award data across systems.
- Stakeholders
- CIO
- Procurement & Payment Services director
- Controller
- Research administration lead
- Discovery questions
- How many PCard transactions are reviewed per cycle, and how long does it take?
- Which exceptions matter most to auditors?
- What evidence would justify scaling beyond the pilot?
- Value hypothesis
- AI-assisted exception flagging may reduce repetitive review time; UND has not measured this.
- Potential engagement
- A bounded PCard or expense audit pilot design with baseline and success metrics.
- Unsupported claims
- Audit time savings
- Improved fraud or error detection
- Scale-up decision or budget
Pre-sales engineering
Role takeaway
- Fit
- Campuses piloting department agents on a shared AI platform before broad licensing.
- Architecture and integration
- Central platform hosting project agents; inputs include PeopleSoft reports, spreadsheets and transaction data.
- Prerequisites
- Read access to PeopleSoft and card-transaction data
- Role-based access for procurement reviewers
- Exception logging
- Constraints
- Vendor, models and hosting not disclosed
- Invitation-only pilot scope
- PCard project still planned
- Security
- Security and responsible use is an evaluation criterion; specific controls on financial data are not described.
- Proof of value
- Compare AI-flagged exceptions with a completed manual audit
- Measure reviewer override rate
- Confirm access logs for financial data
Delivery
Role takeaway
- Work
- Design and run a PCard audit agent alongside the current manual audit.
- Dependencies
- Procurement & Payment Services
- UND IT
- Internal audit
- Ownership
- UND Procurement & Payment Services, with UIT as platform owner.
- Skills and adoption
- Procurement staff trained to review and override AI flags.
- Governance checkpoints
- Data-access approval for transaction records
- Parallel run before reliance
- Pilot value and cost review before scaling
- Acceptance criteria
- Proposed: AI flags cover all exceptions found by the manual audit in a parallel cycle
- Proposed: reviewer time per cycle measured against baseline
- Risks
- Missed exceptions
- Over-reliance on flags
- Unclear support costs at scale
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?
A single campus platform hosts several project agents; PeopleSoft reports and spreadsheets are named as current data sources for Atlas.
Governance
Who approves, reviews and stays accountable for outcomes?
Participation is gated by invitation or approved project; security and responsible use is a stated evaluation criterion.
Security and privacy
What data, permissions and controls need testing?
PCard transaction data and research award budgets are in scope, so access controls on financial data matter; no controls are described.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Aims to reduce repetitive manual review for procurement and grant staff and to free staff for higher-value work; no staffing change stated.
Procurement
What should contracts, pricing and exit terms secure?
Pilot is framed to establish costs and infrastructure before broader access; vendor and pricing not disclosed.
Operating model
Which teams own the service once it runs?
Departments own projects (Procurement & Payment Services, Engineering research support) on a central IT platform.
Publication history
- 2026-11-01Campus Operations · Issue 544 resources
Stable resource ID: und-nebula-ai-pilot-pcard-audit-research-admin-202611