CSU Systemwide Learning Management Systems and Services


Published on

Presentation to the CSU Community of Academic Technology Staff annual conference in April 2010. Topics discussed include the history of the LMS in the CSU, the current services coordinated through the Chancellor's Office, and upcoming services.


Kathy Fernandes, CSU Office of the Chancellor
John Whitmer, CSU Office of the Chancellor

Published in: Education, Business, Technology
  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide
  • Could remove sub-bullets under each recommendation for clarity and succinct presentation
  • Could remove sub-bullets under each recommendation for clarity and succinct presentation
  • Leave out? Or replace with overview what campuses have decided?
  • John
  • JohnSlide needs resizing –Is content relevant for this presentation?
  • John
  • John
  • CSU Systemwide Learning Management Systems and Services

    1. 1. CSU SystemwideLearning Management Systems and ServicesKathy Fernandes, CSU Chancellor's OfficeJohn Whitmer, CSU Chancellor's Office <br />CATS 2010 <br />April 13, 2010<br />
    2. 2. Agenda<br />Welcome and Introductions<br />CSU LMS Landscape<br />LMS Futures Group: Systemwide LMS Recommendations & Governance<br />Moodle Coordination and Strategies<br />Blackboard Coordination and Strategies<br />CATS Participation and Contribution Opportunities<br />Q & A (time permitting)<br />2<br />
    3. 3. Welcome and Introductions<br />Presenters:<br />Kathy Fernandes<br />Director of Systemwide LMS Initiatives, CSU Chancellor's Office <br />John Whitmer<br />Manager of Systemwide LMS Initiatives, CSU Chancellor's Office <br />3<br />
    4. 4. CSU Campus LMS Usage<br />4<br />
    5. 5. Current Context of CSU System-wide LMS’<br />77 FTE staff work on LM systems & services <br />Average 3.3 FTE per campus<br />Low of .5 FTE and high of 10 FTE<br />Includes DBA, Systems, Application Admin, Support Tier 1, 2 & 3, training and instructional design<br />We have 23 different LMS integrations with Peoplesoft <br />We have 23 different authentications to the LMS<br />We spend $2.0M/yr on Blackboard licensing & hosting $12M spent since 2005 (inc. WebCT)<br />Another $450k/yr on server hardware and software<br />5<br />
    6. 6. Current Context of CSU System-wide LMS’<br />We pay for ALL faculty and student enrollments on Bb campus regardless of how many use the LMS<br />Price increase avg. 5% per year (1 exception)<br />Some campuses cannot afford increased cost (and growth) to their LMS<br />The CSU has made multiple requests to Blackboard for a more affordable centralized solution<br />Written proposal is from Bb is coming…<br />6<br />
    7. 7. Continued CSU LMS Context<br />No campus has fully maximized their LMS (100% faculty and student use), and LMS usage continues to grow<br />We have no standard way of reporting systemwide LMS growth<br />Some campuses have automatic LMS course shells created for every single course<br />Some campuses use a template for course shells branded and “resource ready” for course content<br />Some campuses have an LMS database that is larger than their CMS database<br />7<br />
    8. 8. Opportunity? Lots of LMS Migrations<br />Migrating campuses experience pain and costs:<br />7% increase to keep a license one more year if not committing to the 2 years left in the contract<br />$11,000 per campus for a non-production license for grade challenges and late content migrations<br />Getting ALL the course content out of Blackboard is requiring lots of development time to move the content from the old LMS to the new<br />New training materials, new issues to solve, new skill sets for faculty, staff and students to learn<br />8<br />
    9. 9. CSU LMS Systemwide Recommendations<br />9<br />
    10. 10. Systemwide LMS Recommendations Overview<br />The LMS Futures Workgroup was charged by the EVC of Academic Affairs and the EVC of Business and Finance in December, 2008 to develop recommendations for effective and efficient LMS services environments that<br />Support teaching and learning activities that contribute to improved student success;<br />Improve the management of academic programs on campuses and across campuses; and<br />Can be integrated with appropriate services selected by campuses and the CSU system. <br />The LMS Futures Workgroup will present its draft to the Academic Technology Steering Committee (ATSC) for review, revision, and recommendations.<br />10<br />
    11. 11. Systemwide LMS Recommendations Overview<br />http://dat.cdl.edu/lms/lms-futures-group<br />Two Background Documents<br />LMS Critical Elements<br />LMS External Scan<br />LMS Futures Workgroup Recommendation Report (12/10/09)<br />DRAFT LMS Futures Workgroup Governance Model Recommendations Report (3/17/10)<br />11<br />
    12. 12. LMS System-wide Recommendationsfrom Recommendations for Future LMS Directions for CSU, p. 3-4<br />Recommendation 1 - Provide an “opt-in” services approach with a collection of resources and best practices<br />Integration of key services <br />SIS integration<br />Shibboleth integration <br />3rd party application integrations for TurnItIn, Respondus, etc.<br />Standard Reporting<br />12<br />
    13. 13. LMS System-wide Recommendationsfrom Recommendations for Future LMS Directions for CSU, p. 3-4<br />Recommendation 2 - Provide a centrally hosted “safety-net” LMS for campuses that are at risk<br />We recommend a limited production available by July 2010<br />Moodle first, followed by Blackboard<br />Implement an agile governance and management process for continuously improving the learning management services for campuses and overseeing the CSU LMS roadmap<br />Expand the Total Cost of Ownership analysis to the full range of learning management services, enabling campuses and the CSU system to make informed decisions about costs and effectiveness<br />Adopt a phased approach over the next 3-5 years that enables the CSU to make continuous improvements and adjustments in this dynamic business and technology environment (see Figure 1).<br />13<br />
    14. 14. LMS Governance<br />Shared/Representative governance of LMS Systems and Services<br />UCLA CCLE as model<br />Governance groups: Executive Sponsors, Standards and Practice Group, Common Interest Groups, LMS Subgroups<br />Includes CIO, Academic Technologists, Academic/Student Senate. <br />Organized to distinguish “strategic policy” from “technical operations”<br />14<br />
    15. 15. LMS Governance Diagram<br />15<br />
    16. 16. Blackboard Coordination and Strategies<br />New “Strategic Account” Reps <br />Biweekly meetings<br />CSU-Bb Webinar on Roadmap<br />Blackboard centrally hosted?<br />Upcoming coordination<br />CSU Sandbox for Bboard v9.1 (5 Campuses)<br />Campus Collaboration on hosting old courses?<br />16<br />
    17. 17. Blackboard Contract Renewals<br />9 campuses on 3-year agreement<br />5 to join the 2nd year of the 3-year agreement<br />5 campuses needing short-term extensions will work with Blackboard individually<br />Consider production versus non-production needs<br />Archives of courses for grade challenges, course content<br />7% increase for a full year of production license<br />17<br />
    18. 18. Moodle Coordination and Strategies<br />Moodle usage increasing within the CSU<br />4 production deployments, 3 migrations in progress, multiple evaluations<br />CSU Moodle Consortium Meetings<br />9 Campuses participating<br />Areas: Hosting, Training/Help Desk, Migration, Integrations, additional development<br />Coordinated training resources<br />Lynda.com multimedia tutorials<br />http://seir.calstate.edu/protected/moodle/<br />Editable object-based tutorial<br />http://quickguides.calstate.edu<br />18<br />
    19. 19. Moodle + LM services in the CSU<br />19<br />
    20. 20. Moodle Coordination: Moodlerooms<br />Hosted Moodle flavors<br />Standard (Power) <br />Enhanced (Joule)<br />Integrations (Conduit-Peoplesoft, Shibboleth)<br />Automated course creation, backup, restore<br />Course content migration support<br />Advanced reporting, automatic notifications, interface<br />Optional ePortfolio, Equella Content Management System<br />Complete description at DAT LMS Site<br />http://dat.cdl.edu/swat/moodlerooms<br />Biweekly meeting with CSU and Moodlerooms<br />Free CSU pilot server available to any campus<br />20<br />
    21. 21. Moodlerooms Joule vs Power Builds<br />21<br />
    22. 22. MR “Power” Standard Moodle<br />22<br />
    23. 23. MR “Joule” Enhanced Moodle<br />23<br />
    24. 24. Systemwide LMS Safety Net – July 1, 2010(Moodle LMS)<br />Safety Net ServicesHosting Moodlerooms, Technical Account Manager, Pilot/Testing Servers, Production Server<br />Service Integration Shibboleth Integration process, Peoplesoft integration process, TurnItin, Respondus, MERLOT search integration, Common reporting queries <br />Training / Support Implementation consulting, Course content migration process support, Lynda.com Moodle tutorials, QuickGuides Maintenance<br />Current Pilot – central coordination can save approx. $50K annually through coordinated hosting and integrations. <br />24<br />
    25. 25. CSU LMS Next Steps<br />ATSC discussion/review Governance and Budget Request 4/21<br />Begin Governance Implementation<br />Moodlerooms Safety Net (CSUN and Sonoma)<br />CSU Moodle Cloud on Amazon (pending)<br />CSU MB host Humboldt<br />Moodle Consortium (Coordinated Reporting, Migration Tools, and more)<br />25<br />
    26. 26. CATS Participation and Contribution <br />Participate in Moodle Consortium (2nd/4th Tuesdays from 9:00-10:00)<br />Pilot Joule Moodle platform<br />Pilot Blackboard v9.1<br />Stay tuned to http://dat.cdl.edu for communications from LMS governance committees<br />26<br />
    27. 27. Questions, Comments, Suggestions?<br />Feedback/Evaluation: please complete 5-question survey at: http://www.surveymonkey.com/s/M7XVH5L<br />Documents, references and archive on DAT LMS Website at: http://dat.cdl.edu/ (login)<br />Contact information:<br />Kathy Fernandes – kfernandes@csuchico.edu<br />John Whitmer – jwhitmer@csuchico.edu<br />27<br />