From the Campus Operations edition of September 23, 2026
SIU System AI task force sets operations goal including Ellucian Smart Plan on Banner
Southern Illinois University System (reported by The Alestle) · Public higher education system · United States — Illinois
- Publisher
- The Alestle (SIUE student newspaper)
- Original publication
- September 23, 2026
- Source retrieved
- 2026-09-24
What happened
SIU’s AI task force defined four goals; goal three targets operational systems (grades, faculty reporting, scheduling) with legal/ethical/usefulness filters for staff tools across three campuses. SIUE Registrar describes Ellucian Smart Plan using Banner, scheduling, and Degree Works to rebuild semester plans and estimate added years/tuition when students reshuffle courses. Paid Copilot access is under consideration for some classes.
Why it matters
Concrete multi-campus campus-operations AI governance and SIS-adjacent planning tooling roadmap—still early, with student concerns recorded.
Evidence and measured results
On-record quotes from Mario Hayek, Tobias Merriman, Registrar Patrick Sears, and students; task force described as planning/research handoff rather than completed deployment metrics.
Limitations and uncertainty
Student newspaper interview; Smart Plan benefits described hypothetically (“in theory”); no measured ops KPIs yet; teaching/research goals dominate article length.
Put this evidence to work
Lighthouse Advisory interpretation, grounded in this source. Enriched 2026-09-23; this does not change the original publication date. Each role follows the same checklist so takeaways compare across sources.
Sales
Role takeaway
- Customer problem
- Multi-campus universities lack shared rules for staff AI in grades, scheduling, accounting, and student planning, risking policy breaches and uneven tool spend.
- Stakeholders
- System CIO / IT
- Registrars
- Academic affairs / provost offices
- Business school and faculty senate leads
- Student affairs
- Discovery questions
- Which operational systems (SIS, Degree Works, finance) may AI touch today?
- Who approves new admin AI tools across campuses?
- What student-data classifications block consumer AI?
- How will usefulness be measured before paid Copilot or Ellucian Smart Plan expansion?
- Value hypothesis
- A systemwide ops AI framework plus controlled SIS-linked planning pilots can reduce accidental unlawful use and clarify when paid tools are justified—without promising shorter time-to-degree.
- Potential engagement
- 8–12 week multi-campus AI operations policy and inventory sprint culminating in one registrar-approved Smart Plan or Copilot pilot design.
- Unsupported claims
- Guaranteed tuition savings from Smart Plan rerouting
- Systemwide adoption completed by the task force alone
- Ellucian Smart Plan accuracy claims not measured in this article
Pre-sales engineering
Role takeaway
- Fit
- Best for multi-campus systems already on Banner/Degree Works that need policy-gated AI for staff workflows and degree planning.
- Architecture and integration
- Ellucian Smart Plan would consume Banner scheduling and Degree Works progression data; paid Copilot needs tenant controls for classroom and staff use.
- Prerequisites
- AI use inventory across campuses
- IT security and ethics review path
- Data classification for student records
- Registrar ownership of degree-plan logic
- Constraints
- Illinois/state policy compliance
- Faculty control of classroom AI settings
- Usefulness gate before spend
- Three-campus consistency
- Security
- Student and staff PII must not go to unapproved consumer AI; any Banner-linked planner needs institutional identity and least-privilege integrations.
- Proof of value
- Pilot Smart Plan on a defined program cohort with registrar sign-off
- Track accidental-policy incidents before/after guidance
- Measure staff tool usefulness surveys, not only license counts
Delivery
Role takeaway
- Work
- Stand up inventory, draft ops AI acceptable-use guidance, and run one SIS-adjacent planning pilot with change management for staff.
- Dependencies
- Banner/Degree Works access
- Ellucian or Copilot licensing path
- Legal/compliance review
- Campus communications
- Ownership
- Joint system AI task force with registrar and central IT as operational owners for planning tools.
- Skills and adoption
- Train department staff and accountants on approved tools; faculty retain classroom AI decisions.
- Governance checkpoints
- Ethics/security gate before new tool
- Registrar acceptance of Smart Plan reroute logic
- Student consultation on AI encouragement concerns
- Acceptance criteria
- Published system ops AI guidance covering banned vs allowed tools
- Documented inventory of admin AI uses
- Pilot report with usefulness and data-handling evidence
- Risks
- Student pushback on AI encouragement
- Smart Plan path advice creating tuition/time surprises
- Uneven campus enforcement
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?
Ops AI must integrate with Banner/Degree Works under registrar control; consumer vs paid Copilot paths need IT security gates for student data.
Governance
Who approves, reviews and stays accountable for outcomes?
Systemwide ethics, syllabi, and ask-IT guardrails precede tool expansion; faculty retain classroom AI decisions while staff use is separately structured.
Security and privacy
What data, permissions and controls need testing?
Leaders explicitly warn against sharing personal information with unapproved AI and require tools to pass SIU and state policy.
Accessibility and workforce
Who is affected, and what skills or accommodations follow?
Accountants and department staff are named as users who may benefit or accidentally break policy—workforce guidance is central.
Procurement
What should contracts, pricing and exit terms secure?
Usefulness gate sits beside legal/ethical checks before spending on paid Copilot or planning products.
Operating model
Which teams own the service once it runs?
Operations is an explicit third pillar of system AI strategy, not only teaching integrity.
Publication history
- 2026-09-23Campus Operations · Issue 164 resources
Stable resource ID: siu-system-ai-ops-taskforce-20260923