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

2. About the CSU Overview 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. IAM Primordial Soup History ITAC Workshop on Middleware (April 2002)
CIO Steering Group, Governance
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 (September 2006)
Subcommittee of ITAC

4. Evolution Without Revolution
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. Federation Goals The New Recipe 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. Why CSUconnect CSUconnect Federation Flexibility
CSU-Specific requirements
Internal services and resources
Central administration
Consistency
Knowledge and resource sharing
Coordination and adoption

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

8. Signs of Intelligent Life
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. Chancellor’s Office Responsibilities
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. Campus Responsibilities
CSUconnect Federation
Campus Responsibilities
On-Going leadership: Appointed project leads – one neck to wring
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. Roll-out CSUconnect Federation 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. Roll-out, Continued CSUconnect Federation
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. Challenges CSUconnect Federation 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. Lessons Learned CSUconnect Federation Don’t wait
Systemic Benefits – It’s important for the stakeholders to understand why you’re doing it
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. Q & A Questions For further information:
Mark Crase Carol Kiliany Michael Trullinger

16. Any questions?