Project Vista Kick-Off

1. Project Vista Kick-Off September 12, 2005 CALIFORNIA STATE UNIVERSITY, CHICO

2. WELCOME • Thanks for coming! • What’s this “Project Vista” all about? • Moving Chico to an Enterprise LMS • LMS Strategic Review (www/tlp/LMS2) • Overview of today • Current Status of Chico’s LMS • Future Vision of Chico’s LMS • Project Vista Specifics

3. CURRENT LMS STATUS at CSU Chico WebCT CAMPUS EDITION (version 4.1) • Each course is self-contained • Individual faculty • Supporting Campus Communities • No Reporting in Campus Edition  WALRUS • WebCT Activity Log Reporting & Utilization Statistics

4. FUTURE ENTERPRISE LMS at CSU Chico WebCT Vista (version 4.0) • All faculty (1,000) and students (16,000) using WebCT weekly, if not daily • Reporting Capabilities • Supports Institutional hierarchy • Ease of use – Contemporary Web Interface

5. WALRUS Summary WebCT Statistics

6. 639 Faculty WebCT Growth 13,362 Students (Est.) 1,329 Sections

7. WALRUS Course Section View

8. Campus Edition Homepage & Add Tools

9. Vista Homepage & Add Tools

10. Campus Edition File Manager

11. Vista File Manager

12. Campus Edition Gradebook

13. Vista Gradebook

14. Vista – new roles

15. Vista structure

16. OLD & NEW ARCHITECTURE • Campus Edition – Only One Server! • Campus Edition not designed to be enterprise • Flat-file database, Perl scripts, no fail-over, corruption • Backup millions of small files • Vista • Relational dbase, Java • Oracle backups and recovery • Load balanced • Clustered servers, scalable

17. WebCT Vista Architecture* * Recommended hardware platforms

18. VISION FOR PROJECT VISTA • Provide leading academic technology for the university’s core mission of teaching and learning • Offer faculty and students rich tools for communication, collaboration, assessment and workflow management • Support important teaching and learning tools and best practices, including the use and integration of content repositories, streaming and multimedia technologies, e-portfolios, library systems, as well as plagiarism detection and content development tools • Deliver high levels of availability (24 x 7), reliability, and performance • Meet demands for future growth (scalable, sustainable)

19. WHAT DEFINES SUCCESS? • Stable, Integrated, Enterprise System • Course Content Migration • Least impact on faculty and students • Leverage more of the new system’s features and capabilities • Faculty & Students • Dept. & Colleges • University-wide

20. MILESTONES • Fall 2005 – Installation & Training • Intersession 2006 – Train & Prep for Pilots • Spring 2006 – Run Pilots, Integrate • Summer 2006 – Migrate courses, Test integration • Fall 2006 – ½ courses in Vista • Spring 2007 – all courses in Vista • Summer 2007 –Clean-up & wrap up

21. TIMELINE Spring 2005 • LMS Strategic Review • Purchased Vista License • Purchased computers for training lab Summer 2005 • Purchased Vista Hardware • Attended WebCT Conference in SF

22. TIMELINE Fall 2005 • Consulting Services • Pre-, Install, Post- installation of Dev. and Prod. Systems • Training (Admin. and User Interface) • Develop Migration Processes • Plan Integrations • Develop Training • Pick Pilot Courses/Faculty • Set-up faculty training lab

23. TIMELINE Intersession 2006 • Migrate Pilot Courses • Train Faculty leading Pilots • Fine Tune System for Spring Pilots • Manual Enrollment

24. TIMELINE Spring 2006 • Run Pilot Courses • Do integrations with CMS/Portal/LDAP/etc. • Refine training/migration/implementation • Meet with depts./colleges to prep for migration either Spring or Summer • Begin some training and course migrations for Fall

25. TIMELINE Summer 2006 • Run Summer Sessions with Enterprise Integration • Training • Migration • Support

26. TIMELINE Fall 2006 • Enterprise Integration Running • Half of all WebCT Courses running on Vista Production System • Training • Migration • Support

27. TIMELINE Spring 2007 • All WebCT Courses on Vista Production System Summer 2007 • Complete any left-over migrations • Move towards retiring Campus Edition

28. ROLES FOR ATEC Bill Evans – Project Manager • Lead technical implementation & migration • Work with INF personnel and WebCT • See that Enterprise integrations achieved • Portal, PeopleSoft, SSL/LDAP, Library, • Arrange meetings to discuss technical & support issues (STCP, Computing Services, etc.) • Implement and keep project moving down the timeline/pipeline • Run meetings that keep personnel on track with a feedback loop

29. ROLES FOR ATEC Laura Sederberg – Program Manager • Lead departmental and program side of planning, training migration, & support • Arrange departmental meetings to discuss faculty pedagogical and dept. goals & issues • Train new ITCs and students • Contact other universities to learn from their Vista transition • Create/modify and/or beta test Vista 4.0 training materials for Chico, schedule workshops • Support faculty after training and migration • Create/modify TLP web site for supporting Vista 4.0 • Work with Vicky and other IMC staff for creating communication and marketing materials for campus • Set up and manage Faculty Training Lab

30. ROLES NEEDED FROM INF STAFF Directors will work with their staff on planning and timing support for Vista • Computing operations & networking support • DBA support • PeopleSoft-WebCT-Portal integration • User Support Services to support faculty and students

31. ROLES NEEDED FROM CAMPUS • Enrollment Management • Deans and Dept. Chairs • Accreditation and Program Assessment • AURA Committee • Faculty (pilots, mentors, committees) • Students

32. WHAT’S NEXT?