Get Full Government Meeting Transcripts, Videos, & Alerts Forever!
Get email alerts on the Banner Migration topic
No spam. Unsubscribe anytime.
CT State technology committee hears Banner migration update, supplier provisioning delays limited to reporting
Summary
The committee received a progress report on the five‑instance Banner migration: contracts separate fixed baseline work from optional support, repeated 'yellow' statuses reflect Ellucian provisioning delays concentrated in reporting, and discovery work shows about half of non‑standard items can be resolved with existing functionality while the rest will need deeper solutions.
Chair Ted Yang convened the Connecticut State Colleges and Universities technology committee to hear a routine update on the Banner migration and related contracts. Michael, the presenter, said the work flows from a master agreement into five instance‑specific contracts that separate a fixed structural component for Ellucian’s baseline work from an optional support component procured as needed.
"Those contracts have two main components," Michael said. "One component you can think of as a base component...for Ellucian to do Ellucian's work. A second part...is for additional support for the projects to procure as needed." He added that delays caused by Ellucian fall within the fixed‑price portion of the contracts, while delays caused by project teams would be negotiated.
Michael told the committee that some projects have shown repeated "yellow" statuses because Ellucian had difficulty provisioning certain elements internally. He said most provisioning delays so far have affected reporting functionality rather than the core design work and that the contract's fixed‑price protections mean the projects are financially shielded from vendor‑caused provisioning delays.
A committee member asked whether percent complete was being measured by task count. Michael confirmed percent complete is tracked by counts of items and agreed to bring examples of the "harder conversations" — the non‑standard items that are likely to take longer — to the next meeting.
On discovery work, Michael reported that four of the five projects completed inventories of non‑standard objects; the CT State system office kickoff is just starting discovery. He estimated roughly 50% of non‑standard items will be resolved with existing functionality or reporting, while the remaining approximately 50% will require detailed engineering, integrations, or business‑process changes.
Committee members emphasized the project's core purpose — system unification combined with a Banner upgrade — and asked staff to surface oversight deliverables and illustrative examples of any issues that threaten schedule or scope. The group agreed to continue monthly updates and further, targeted reviews offline. No motions or votes were recorded during the briefing.
The committee did not set new deadlines; Michael said the teams expect to have a clearer view of sticky items within about a month as they dig into the more difficult non‑standard objects.
