Meeting Notes April 26, 2006

The meeting opened the meeting with an update from Michael Crow.

  • The decision has been made to change from Oracle Student Systems (OSS) to Oracle/PeopleSoft Campus Solutions.
  • Plans and timeline will be reconfigured.
  • Re-launch planned for July 2006 at the “process phase.”
  • Hardware changeover to be completed by midsummer.
  • Consultant (who also has worked with KU) will come in for 3-4 weeks.
  • Meetings to talk about processes will resume in early September.
    • Focus on what’s done, what’s needed.
    • Develop flow charts.
  • Set-up to be completed by end of 2006.
  • Six to eight months anticipated to confirm process.
  • Next six to eight months will be used to expand training.
  • “Go-live” date MAY be 2008.
  • Advantages of CS. . .
    • Can see how CS works, where we couldn’t in OSS – what we have, what we want/need to have; screens, reports.
    • Will use “issues” format for continuing discussion.
    • Partnering with KU for some things (KU has been on-line with CS for 2-3 years)
    • Terminology is familiar – classes & courses will continue; credit hours will be “units”.
    • Can call on the experiences of 600 other schools who use CS, including those in Big 10 and California State system (Cal State-Northridge has used CS with DARS).
    • CS seems more intuitive than OSS.
  • “Oracle is becoming more customer-friendly.”
  • Still lots of questions. . .
    • SEVIS (international admissions)
    • Building codes (minor adjustments)
    • Course prefixes (?)
    • Semester codes will change some
    • Course set-up will be complicated
    • Servers
  • Rawson has identified $250,000 for changeover expenses.
  • Colleges and departments need to upgrade equipment to specs on LASER website.
  • Departments will have greater role in “special permission” transactions.
  • We’ll start at v.8.9 or v.9

Ray Hightower distributed spreadsheet of data collected on ranking of SIS codes. Kevin Donnelly distributed survey information collected from College of Agriculture departments. Next step is to identify DATA ELEMENTS that are needed, not just screens.

Assignment:

Review spreadsheet, update. Summarize previous questions.