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

Background Course Management System Advisory Group 8/2002 – 6/2003

Background Course Management System Advisory Group 8/2002 – 6/2003 Recommends WebCT Vista 2.1+

Background 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+

Hardware Infrastructure: Current 1 Sun Solaris Enterprise 4500 UltraSPARC processors 2 GB RAM 44 GB HD

Hardware Infrastructure: Current CanScaleOnlyvertically 1 Sun Solaris Enterprise 4500 UltraSPARC processors 2 GB RAM 44 GB HD

Software Infrastructure: Current Software = Perl, C, JavaScript, and Java applets

Software Infrastructure: Current Software = Perl, C, JavaScript, and Java applets Flat file “database:” Creating minor instabilities at current scale

Software Infrastructure: Current Limited analytical data available Software = Perl, C, JavaScript, and Java applets Flat file “database:” Creating minor instabilities at current scale

Hardware Infrastructure: Vista Clustered Architecture

Hardware Infrastructure: Vista Clustered Architecture Initial: 2 app 1 DB Tivoli App = IBM x345 DB = IBM x445

Hardware Infrastructure: Vista Clustered Architecture Initial: 2 app 1 DB Tivoli Summer ’04: 4 app 2 DB SAN Tivoli App = IBM x345 DB = IBM x445

Hardware Infrastructure: Vista 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

Software Infrastructure: Vista Enterprise Oracle DB

Software Infrastructure: Vista Enterprise Oracle DB Includes DataGuard

Enterprise Oracle DB Includes DataGuard May migrate DB in 3-4 years Software Infrastructure: Vista

Enterprise Oracle DB Includes DataGuard May migrate DB in 3-4 years Vista entirely J2EE (BEA WebLogic) Software Infrastructure: Vista

Enterprise Oracle DB Includes DataGuard May migrate DB in 3-4 years Vista entirely J2EE (BEA WebLogic) Vastly expanded analytical data Software Infrastructure: Vista

Support Fall 1998 <.2 WebCT admin, trainer, user support ca. 100 courses, 5,000 user seats

Support Fall 2000 <.2 WebCT admin, trainer, user support ca. 100 courses, 5,000 user seats

Support Spring 2000 <.5 WebCT support Ca. 500 courses, 15,000 user accounts

Support Spring 2003 Creation of Learning Support 2 FTE

Support Spring 2003 LSS = 2 FTE Begin integration with UF Computing HelpDesk ca. 900 courses, 30,000 user seats

Support Spring 2004 LSS = 3 FTE

Support Spring 2004 LSS = 3 FTE Tight integration with UF Computing HelpDesk

Support Spring 2004 LSS = 3 FTE Tight integration with UF Computing HelpDesk ca. 1,700 courses, 74,000+ user seats

Support Summer FTE, migration coordinator 6-8 PT OPS “Rapid Migration Team”

Teaching & Learning Infrastructure WebCT Campus Edition Two separate instances GL – main campus NGL – distance education

Teaching & Learning Infrastructure WebCT Campus Edition Two separate instances GL – main campus NGL – distance education Template (look and feel) capability is limited

Teaching & Learning Infrastructure Course is primary learning context

Teaching & Learning Infrastructure Course is primary learning context Admin, designer, TA, and student accounts: Each ID = one role

Teaching & Learning Infrastructure Admin, designer, TA, and student accounts: Each ID = one role Course is primary learning context Shared designer access = “shared”

Teaching & Learning Infrastructure 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”

Teaching & Learning Infrastructure WebCT Vista One instance

Teaching & Learning Infrastructure WebCT Vista One instance Many potential institutions (hosting?)

Teaching & Learning Infrastructure WebCT Vista One instance Many potential institutions (hosting?) Learning context hierarchy:

Teaching & Learning Infrastructure WebCT Vista One instance Many potential institutions (hosting?) Learning context hierarchy: Institution > Group > Course > Section

Teaching & Learning Infrastructure WebCT Vista Institution level allows for University “branding”

Teaching & Learning Infrastructure WebCT Vista Group level allows for College “branding”

Teaching & Learning Infrastructure WebCT Vista Course is still the primary development context

Teaching & Learning Infrastructure WebCT Vista Section is the primary instructional context: Push-down content capability

Teaching & Learning Infrastructure User Roles Institution Level Group Level Course Level Section Level

Teaching & Learning Infrastructure User Roles Institution Level Group Level Course Level Section Level Role Permissions ??

Teaching & Learning Infrastructure User Roles Each ID can be assigned multiple roles

Teaching & Learning Infrastructure User Roles Each ID can be assigned multiple roles Each designer is now independent

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)

Learning Context Hierarchy Instance Vista

Instance Vista University of Florida Institution

Learning Context Hierarchy Instance Vista University of Florida USNDH Institution

Learning Context Hierarchy Instance Vista University of Florida USNDH CALSCLAS HSC CoE CoB CALS CLAS HSC CoE CoBGroup Institution

Learning Context Hierarchy Instance Vista University of Florida USNDH CALS CLAS HSC CoE CoB MAC1147 STA2023 CHM1025 Courses Group Institution

Learning Context Hierarchy Instance Vista University of Florida USNDH CALS CLAS HSC CoE CoB MAC1147 STA2023 CHM Sections Courses Group Institution

Learning Context Hierarchy MAC Push-down content changes

Timeline * Dec Feb * AcquisitionInstallation Infrastructure testing Operational planning Administrative training Pilot planning

Timeline * March - May 2004 * Training development Migration planning Migration of pilot courses Training of pilot faculty “soft” roll-out of training “train-the-trainer”

Timeline * May 2004 * Pilot go-live Support provider OJT

* July 2004 * Migration training Migration implementation Vista training roll-out Timeline

Timeline * August 2004 * Hardware upgrade (?)

Timeline * Fall 2004 * Campus-wide go-live Vista becomes primary CMS WebCT CE supported through Summer

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?

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?

Points for you to Consider Do you want to consider administrative and/or HelpDesk possibilities under the new distributed hierarchy?

Contact Learning Support Systems