This presentation from the US West Coast 2010 MoodleMoot discusses how the California State University is building coordinated LMS Services to reduce overall system costs and support unique campus needs. In particular, we discuss how the Moodle Learning Management System is being leveraged to reduce cost and increase resources provided for implementation, development, and user support. This presentation discusses the CSU Learning Management Systems and Services Initiative. The project started in 2007 with an RFP to select LMS applications, and has recently begun to provide systemwide LMS services that are offered through local campuses, the CSU Chancellor’s Office, and external providers. Currently there are 4 campuses with Moodle production systems, with 2 additional campuses in the process of converting to Moodle. This presentation will discuss the strategic plan for these services and progress to-date, including development of an ASP Moodle “safety net," a standardized SIS integration into Peoplesoft, a shared knowledge base, and a multi-campus Moodle Consortium. Participants will be asked to discuss their own experiences deploying LMS services, how these models apply to their campus, and identify additional ways that Moodle development and deployment costs can be reduced through consortial arrangements. Presenters: Kathy Fernandes, CSU Office of the Chancellor Andrew Roderick, San Francisco State University John Whitmer, CSU Office of the Chancellor

1. Building CSU System-Wide LMS Services using Moodle San Francisco State University Andrew Roderick, Technology Development and Support Manager CSU Chancellor’s Office Kathy Fernandes, Director of System-Wide LMS Initiatives John Whitmer, Associate Director of System-Wide LMS Initiatives

2. PAST Historical background of Moodle collaboration within the CSU system

3. CSU Demographicshttp://calstate.edu 23 campuses Approx. 433,000 FTE students 44,000 faculty and staff We are the largest, the most diverse, & one of the most affordable university systems in the country We play a vital role in the growth & development of California's communities and economy

7. Humboldt State - 2007

8. CSU Monterey Bay - 2009

10. 2,400 courses

11. Branded as iLearn

12. Moodle1.9.9 in Fall

13. Customized gradebook, course archive, file system, custom integrations

15. Cooperative

16. CollaborativeCSU Moodle Coalition was the context for cooperation. CSU LMSS is the step toward collaboration.

17. Present Overview of CSU System-wide Learning Mgmt Systems & Services

18. CSU Campus LMS Usage (2010)

19. Overview of System-wide Processes Perform LMS RFI and RFP (2008-2009) Define LMSS Strategy (2009-2010) Implement Governance (2010-2011) Create Collaborative Projects that Benefit Multiple Campuses (2010-)

20. System-wide LMSS Strategy LMS Futures Group (Provosts, CIOs, Faculty) prepared 4 documents (http://dat.cdl.edu): LMS Critical Elements External Scan of Market & Higher Ed Systems CSU System-wide Recommendations LMS Governance Recommendations Organize stakeholders to implement recommendations, starting with Moodle

21. System-wide LMS Governance

22. Identified Project Areas for 2010 Governance implementation and revision Common licensing (lms, integrations, etc.) Common Moodle codebase (mixed hosting) Integrations – library, MERLOT, web conferencing, lecture capture Migration, training Future: shared help desk / support And other activities that governance identifies …

23. CSU Moodle Collaborations

24. Stages of Adoption/Interest Mature New Production Pilot LMS Assessment Moodle-curious

26. Informational/Community and Production/Deliverables based

27. Open Participation + Working Groups

28. Steered by Governance (S&PG)

29. Broad Stakeholders (IT, AT, ID, Developers, etc.)

32. Vendor Hosted + Self-Hosted

33. Needs Based on Stage of Adoption

34. Differences in Stakeholder Perspectives

35. Differences in Campus Environments/Size

37. Common Code Base End goal is stable, effective build running in a campus environment – this means interdisciplinary participation. CSU Distribution centrally tested and managed Locally tested and customized for environments Scaled for performance across campus size Agreed upon components, add-ons More to come…

38. CSU-wide Initiatives Purpose-built for the CSU Local Infrastructure Integrations Accessible Technology Initiative CSU Library Initiatives (Xerxes, etc.) Merlot Fresca Digital Marketplace/Affordable Learning Solutions

39. Models, Ideas

40. Key Questions to Address Common codebase process – change management framework, QA, requirements definition … in decentralized, opt-in environment Readiness and participation “requirements” – in-kind or $$$? Recognize diverse existing investments/resources Defining economic value and metrics – increase efficiency/VOI, not cash savings Communication plan – addressing diverse stakeholders w/o attending every meeting

41. Contact Information SF State Andrew Roderick (roderick@sfsu.edu)Technology Development Manager Chancellor’s Office Kathy Fernandes (kfernandes@csuchico.edu)Director of System-Wide LMS Initiatives John Whitmer (jwhitmer@csuchico.edu)Associate Director of System-Wide LMS Initiatives