1 / 16

California State University CSUconnect Federation

Learn about the evolution, goals, challenges, and roll-out of the CSUconnect Federation for secure, scalable access to system-wide resources, utilizing existing infrastructure and campus initiatives. Discover lessons learned and key responsibilities for the Chancellor’s Office and campuses.

kmelissa
Download Presentation

California State University CSUconnect Federation

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. California State University CSUconnect Federation Presentation for InCommon August 19, 2009

  2. Overview About the CSU • Campuses • Nation’s largest 4-year public university system • 23 campuses and 7 off-campus centers • 437,000 students (Fall 2008) • 47,000 faculty and staff • More than 1,800 bachelor’s and master’s degree programs in 357 subject areas • Chancellor’s Office • Administrative Headquarters • 700 Staff

  3. History IAM Primordial Soup • ITAC Workshop on Middleware (April 2002) • ITAC Middleware Steering Committee (May 2002) • Directories Working Group (Spring 2002) • Adoption of eduPerson Object Classification • Creation of calstatePerson Object Classification • SIMI Proposal Approved by TSC (May 2003) • Initial SIMI Workshop (July 2004) • Technical Architecture Group formed (September 2006) • Technical Representation from all 23 Campuses • IAM CIO Steering Committee formed (September2006) • Subcommittee of ITAC

  4. The New Recipe Evolution Without Revolution • Deliver on key drivers • Access to system-wide resources • Provide foundation for realizing local benefits • Provide cost effective, scalable approach • Affordable system-wide software licensing • Avoid forklift upgrades and take advantage of existing campus resources

  5. The New Recipe Federation Goals • Security and scalability • Limit centralized maintenance overhead • Rely on local identity data authorities • Enable access to services • Electronic library resources • Collaboration between higher-education institutions and partners • Collaboration between campuses • System-wide applications

  6. CSUconnect Federation Why CSUconnect • Flexibility • CSU-Specific requirements • Internal services and resources • Central administration • Consistency • Knowledge and resource sharing • Coordination and adoption

  7. CSUconnect Federation Why InCommon • Low cost, low maintenance • Use of existing non-CSU infrastructure • Existing relationships • User driven community

  8. CSUconnect Federation Signs of Intelligent Life • Proof of concept with Moss Landing Marine Labs (January 2007) • CSUconnect Federation Standards document completed and approved by ITAC (April 2007) • Technical system-wide design completed (August 2007) • Phased roll-out plan constructed (March 2008)

  9. CSUconnect Federation Chancellor’s Office Responsibilities • On-going coordination and leadership of IAM program system-wide • Administrative management and oversight • Shared system-wide infrastructure • Discovery Service (WAYF) • Provide training • Provide bulk of funding

  10. CSUconnect Federation Campus Responsibilities • Identification and commitment of local staffing resources • Administrative paperwork • InCommon • CSUconnect • Completion of campus infrastructure • Enterprise Directory • Shibboleth Identity Provider (IdP) • calstateEduPerson • On-going coordination and leadership of IAM initiatives at campus level

  11. CSUconnect Federation Roll-out • Project Plan • Three implementation phases (~ 33% campus each) • Includes common administrative and technical processes • Campus training (began October 2008) • Costs covered by the Chancellor’s Office • Hardware distribution ($180,000 upfront) • InCommon setup fees ($16,000 upfront) • InCommon annual registration fees ($24,000) • Campuses cover proceeding years • First campus became member of CSUconnect Federation, February 2009. • Most campuses should be complete September 2009

  12. CSUconnect Federation Roll-out, Continued • Initially targeting four major system-wide applications • SharePoint (System-wide Intranet) • Consolidated PeopleSoft Finance • Central Finance Data Warehouse • Wireless • Some campus specific targets • CSU Learning Management Systems • Google Mail • Microsoft Dreamspark • External Library providers

  13. CSUconnect Federation Challenges • Budget • Competition for campus staff resources with other projects • Varying levels of technical expertise between campuses • Multiple group involvement on larger campuses • Coordinating the participation of campuses • Ongoing communication and project management with campuses to ensure work is completed

  14. CSUconnect Federation Lessons Learned • Don’t wait • If you think it’s important, start now! • Define the systemic benefits early on • CIO’s must lead, but must not focus on the technology • This is about doing our business in a different way

  15. Questions Q & A For further information: Mark Crase Carol Kiliany Michael Trullinger mcrase@calstate.educkiliany@calstate.edumtrullinger@calstate.edu

  16. www.calstate.edu

More Related