University of WisconsineLearning Systems Current State

Common Solutions Group May 7, 2003

Dirk Herr-Hoyman

eLearning System Architect

University of Wisconsin-Madison

May 7, 2003 University of Wisconsin-Madison 2

What is an eLearning System?

• Yet another TLA like CMS and LMS

• Framework, tools, and content

• Similar technology to portals and other integrated apps like SIS, ERP

• An “eWhatever” type of name for online services

May 7, 2003 University of Wisconsin-Madison 3

History at Wisconsin

• Tradition of distance learning from Extension

• Multiple systems on multiple campuses

• Interest in a UW Systemwide Hosting Utility

May 7, 2003 University of Wisconsin-Madison 4

8

Landscape 1998-

May 7, 2003 University of Wisconsin-Madison 5

9

Landscape 2002

May 7, 2003 University of Wisconsin-Madison 6

Key Questions for UW

• Can we afford to support multiple courseware systems?

• Is there one product or set of products that will meet the e-learning needs?

• Where is the marketplace today?• What would we like it to go?• What is the cost of enterprise learning

systems?

May 7, 2003 University of Wisconsin-Madison 7

eLearning System RFP

• UW CIOs charged a Task Force with recommending a single product or set of integrated products

• Year long process, Feb 2002- Feb 2003

May 7, 2003 University of Wisconsin-Madison 8

RFP Architecture Vision

May 7, 2003 University of Wisconsin-Madison 9

RFP Process

• RFI – 31 responses, RFP – 16 responses

• Finalists: Bb, WebCT, Granada Learnwise, Desire2Learn

• Online demos and demo accounts for finalists

May 7, 2003 University of Wisconsin-Madison 10

Technology Profile of Finalists

• Blackboard: Sticking with hybred

• WebCT: Switching to J2EE

• Granada: Switching to J2EE and open source

• Desire2Learn: MS COM (pre-.NET)

May 7, 2003 University of Wisconsin-Madison 11

Selection of Desire2Learn

• Hiding under a rock until our RFP

• Best functional, adequate technical

• User experience design uber alles

• Bb and WebCT were caught off guard

• Spent time after 2001 working on functionality, not technology

May 7, 2003 University of Wisconsin-Madison 12

Desire2Learn Implementation

• Migration of all WebCT and Blackboard courses by June 04

• Single hosting Utility at Madison

• Integration with multiple campus systems

May 7, 2003 University of Wisconsin-Madison 13

Challenges of a young company

Risks• Largest customer• Growing staff quickly• MS technology• Too popular, many

new sales• Shift to partnership

Opportunites• Responsive to our

requirements• Build a good vendor

relationship from beginning

• Remove product branding (WebCT/Bb)