1. The FLORIDA VISTA IMPLEMENTATION PROJECT: Implications for CAMPUS I.T. professionals Learning Support Systems Office of Academic Technology

2. Background http://lss.at.ufl.edu Course Management System Advisory Group 8/2002 – 6/2003

3. Background http://lss.at.ufl.edu Course Management System Advisory Group 8/2002 – 6/2003 Recommends WebCT Vista 2.1+

4. Background http://lss.at.ufl.edu Learning Support Systems is given go-ahead to implement, 8/2003 Course Management System Advisory Group 8/2002 – 6/2003 Recommends WebCT Vista 2.1+

5. Hardware Infrastructure: Current 1 Sun Solaris Enterprise 4500 4@400MHz UltraSPARC processors 2 GB RAM 44 GB HD http://lss.at.ufl.edu

6. Hardware Infrastructure: Current http://lss.at.ufl.edu CanScaleOnlyvertically 1 Sun Solaris Enterprise 4500 4@400MHz UltraSPARC processors 2 GB RAM 44 GB HD

7. Software Infrastructure: Current http://lss.at.ufl.edu Software = Perl, C, JavaScript, and Java applets

8. Software Infrastructure: Current http://lss.at.ufl.edu Software = Perl, C, JavaScript, and Java applets Flat file “database:” Creating minor instabilities at current scale

9. Software Infrastructure: Current http://lss.at.ufl.edu Limited analytical data available Software = Perl, C, JavaScript, and Java applets Flat file “database:” Creating minor instabilities at current scale

10. Hardware Infrastructure: Vista http://lss.at.ufl.edu Clustered Architecture

11. Hardware Infrastructure: Vista http://lss.at.ufl.edu Clustered Architecture Initial: 2 app 1 DB Tivoli App = IBM x345 DB = IBM x445

12. Hardware Infrastructure: Vista http://lss.at.ufl.edu Clustered Architecture Initial: 2 app 1 DB Tivoli Summer ’04: 4 app 2 DB SAN Tivoli App = IBM x345 DB = IBM x445

13. Hardware Infrastructure: Vista http://lss.at.ufl.edu Clustered Architecture Initial: 2 app 1 DB Tivoli Summer ’04: 4 app 2 DB SAN Tivoli RedHat Linux AS 2.1 App = IBM x345 DB = IBM x445

14. Software Infrastructure: Vista Enterprise Oracle DB http://lss.at.ufl.edu

15. Software Infrastructure: Vista Enterprise Oracle DB Includes DataGuard http://lss.at.ufl.edu

16. Enterprise Oracle DB Includes DataGuard May migrate DB in 3-4 years Software Infrastructure: Vista http://lss.at.ufl.edu

17. Enterprise Oracle DB Includes DataGuard May migrate DB in 3-4 years Vista entirely J2EE (BEA WebLogic) Software Infrastructure: Vista http://lss.at.ufl.edu

18. Enterprise Oracle DB Includes DataGuard May migrate DB in 3-4 years Vista entirely J2EE (BEA WebLogic) Vastly expanded analytical data Software Infrastructure: Vista http://lss.at.ufl.edu

19. Support Fall 1998 <.2 WebCT admin, trainer, user support ca. 100 courses, 5,000 user seats http://lss.at.ufl.edu

20. Support Fall 2000 <.2 WebCT admin, trainer, user support ca. 100 courses, 5,000 user seats http://lss.at.ufl.edu

21. Support Spring 2000 <.5 WebCT support Ca. 500 courses, 15,000 user accounts http://lss.at.ufl.edu

22. Support Spring 2003 Creation of Learning Support Systems @ 2 FTE http://lss.at.ufl.edu

23. Support Spring 2003 LSS = 2 FTE Begin integration with UF Computing HelpDesk ca. 900 courses, 30,000 user seats http://lss.at.ufl.edu

24. Support Spring 2004 LSS = 3 FTE http://lss.at.ufl.edu

25. Support Spring 2004 LSS = 3 FTE Tight integration with UF Computing HelpDesk http://lss.at.ufl.edu

26. Support Spring 2004 LSS = 3 FTE Tight integration with UF Computing HelpDesk ca. 1,700 courses, 74,000+ user seats http://lss.at.ufl.edu

27. Support Summer 2004 +1 FTE, migration coordinator 6-8 PT OPS “Rapid Migration Team” http://lss.at.ufl.edu

28. Teaching & Learning Infrastructure http://lss.at.ufl.edu WebCT Campus Edition Two separate instances GL – main campus NGL – distance education

29. Teaching & Learning Infrastructure http://lss.at.ufl.edu WebCT Campus Edition Two separate instances GL – main campus NGL – distance education Template (look and feel) capability is limited

30. Teaching & Learning Infrastructure http://lss.at.ufl.edu Course is primary learning context

31. Teaching & Learning Infrastructure http://lss.at.ufl.edu Course is primary learning context Admin, designer, TA, and student accounts: Each ID = one role

32. Teaching & Learning Infrastructure http://lss.at.ufl.edu Admin, designer, TA, and student accounts: Each ID = one role Course is primary learning context Shared designer access = “shared”

33. Teaching & Learning Infrastructure http://lss.at.ufl.edu Course is primary learning context Separate ID required for student view by instructor Admin, designer, TA, and student accounts: Each ID = one role Shared designer access = “shared”

34. Teaching & Learning Infrastructure WebCT Vista One instance http://lss.at.ufl.edu

35. Teaching & Learning Infrastructure WebCT Vista One instance Many potential institutions (hosting?) http://lss.at.ufl.edu

36. Teaching & Learning Infrastructure WebCT Vista One instance Many potential institutions (hosting?) Learning context hierarchy: http://lss.at.ufl.edu

37. Teaching & Learning Infrastructure WebCT Vista One instance Many potential institutions (hosting?) Learning context hierarchy: Institution > Group > Course > Section http://lss.at.ufl.edu

38. Teaching & Learning Infrastructure http://lss.at.ufl.edu WebCT Vista Institution level allows for University “branding”

39. Teaching & Learning Infrastructure http://lss.at.ufl.edu WebCT Vista Group level allows for College “branding”

40. Teaching & Learning Infrastructure http://lss.at.ufl.edu WebCT Vista Course is still the primary development context

41. Teaching & Learning Infrastructure http://lss.at.ufl.edu WebCT Vista Section is the primary instructional context: Push-down content capability

42. Teaching & Learning Infrastructure User Roles http://lss.at.ufl.edu Institution Level Group Level Course Level Section Level

43. Teaching & Learning Infrastructure User Roles http://lss.at.ufl.edu Institution Level Group Level Course Level Section Level Role Permissions ??

44. Teaching & Learning Infrastructure User Roles Each ID can be assigned multiple roles http://lss.at.ufl.edu

45. Teaching & Learning Infrastructure User Roles Each ID can be assigned multiple roles Each designer is now independent http://lss.at.ufl.edu

46. Teaching & Learning Infrastructure User Roles Each ID can be assigned multiple roles Each designer is now independent Designers can also function as students to test all features (no separate ID) http://lss.at.ufl.edu

47. Learning Context Hierarchy Instance Vista http://lss.at.ufl.edu

48. Instance Vista University of Florida http://lss.at.ufl.edu Institution

49. Learning Context Hierarchy Instance Vista University of Florida USNDH Institution http://lss.at.ufl.edu

50. Learning Context Hierarchy Instance Vista University of Florida USNDH CALSCLAS HSC CoE CoB CALS CLAS HSC CoE CoBGroup Institution http://lss.at.ufl.edu

51. Learning Context Hierarchy Instance Vista University of Florida USNDH CALS CLAS HSC CoE CoB MAC1147 STA2023 CHM1025 Courses Group Institution http://lss.at.ufl.edu

52. Learning Context Hierarchy Instance Vista University of Florida USNDH CALS CLAS HSC CoE CoB MAC1147 STA2023 CHM1025 0001 0002 0003 0004 0005 Sections Courses Group Institution http://lss.at.ufl.edu

53. Learning Context Hierarchy MAC1147 0001 0002 0003 0004 00005 Push-down content changes http://lss.at.ufl.edu

54. Timeline * Dec. 2003 - Feb. 2004 * AcquisitionInstallation Infrastructure testing Operational planning Administrative training Pilot planning http://lss.at.ufl.edu

55. Timeline * March - May 2004 * Training development Migration planning Migration of pilot courses Training of pilot faculty “soft” roll-out of training “train-the-trainer” http://lss.at.ufl.edu

56. Timeline * May 2004 * Pilot go-live Support provider OJT http://lss.at.ufl.edu

57. * July 2004 * Migration training Migration implementation Vista training roll-out Timeline http://lss.at.ufl.edu

58. Timeline * August 2004 * Hardware upgrade (?) http://lss.at.ufl.edu

59. Timeline * Fall 2004 * Campus-wide go-live Vista becomes primary CMS WebCT CE supported through Summer 2005 http://lss.at.ufl.edu

60. Points for you to Consider How extensive is use of the CMS in your college and/or department? How extensive *could* use of the CMS be? http://lss.at.ufl.edu

61. Points for you to Consider Do you provide tech support for faculty or student users? Do you want to provide Vista support for your users? http://lss.at.ufl.edu

62. Points for you to Consider Do you want to consider administrative and/or HelpDesk possibilities under the new distributed hierarchy? http://lss.at.ufl.edu

63. Contact Learning Support Systems learning-support@ufl.eduhttp://lss.at.ufl.edu352.392.2007 http://lss.at.ufl.edu