Choosing Open Source and Partnering as an IT

Choosing Open Source and Partnering as an IT Strategy Brad Wheeler Associate Vice President & Dean Office of the VP & CIO Indiana University bwheeler@iu. edu

IU & Community Source Projects Twin Peaks Navigator 2004

We had a problem… (Jan 2002) Continue to develop ASP • Isolated Development & Sys Admin Team • No leverage w/other capabilities Bu ild Oncourse was succeeding… but ? ONLY major enterprise System in ASP. All others were in J 2 EE/AIX/Linux Redevelop in J 2 EE ourselves $$$ Bu y License a commercial CMS/LMS $$$ Build… 1998 2002 Decision would set costs/options for many years

CMS Requirements are Growing Textbook Integration w/ Publishers Special Character Sets Math/Languages/Sciences Research/Committee Support Streaming Multi-media Sophisticated Assessment Distributed Ed Oncourse Ongoing Maintenance Integration/Leverage w/Enterprise Services Self-paced Tutorials Workflow Library Integration E-Portfolio Direct Manipulation User Interfaces IMS/SCORM Greater Personalization How will IU meet these growing requirements for Oncourse in a period of flat resources?

Web Services Unbundle Silos Library Registrar CMS Schools Unbundled Services Portal üAuthentication üPersonalization üData integration üDelegation

Post-PC Future of Mobile Computing Portal Services connect to the Portal and the Portal connects to the evolving plethora of wireless, mobile computing devices headed to campus. Connecting each service is infeasible.

IU CMS Strategy Review – May 2002 Continue to invest in Oncourse as an IU ild Enterprise application rather than licensing a commercial CMS package. Bu 2. Direct Oncourse development efforts toward s rd Open Knowledge Initiative architecture da compliance. n ta S 3. Pursue aggressive integration efforts among e at IU’s comparative strengths in Oncourse, the gr One. Start Portal, and Digital Libraries. te n I 4. Develop Oncourse as IU’s lead initiative for mobile device connectivity via the One. Start Portal. 1. “CMS Strategy for Indiana University”

“w/Like-minded Partners” Joint development Agreement w/u. Mich IU Development Principles Join Open Source Portfolio Initiative Navigo w/ Stanford, u. Mich Sakai OSPI Grants Kuali Project Financial System Build Decision 2002 Twin Peaks Grant Sakai Conceived 2003 2004

Sakai, OSPI, Kuali Lessons Ø Collaboration is a capability ü Organizational readiness, learning ü Value for the future Ø Choose your partners well ü Like-minded institutions, timelines Ø Sakai structure is promising ü Small core development team ü Large partners organization

Community Source Projects “Community source describes a model for the purposeful coordinating of work in a community. It is based on many of the principles of open source development efforts, but community source efforts rely more explicitly on defined roles, responsibilities, and funded commitments by community members than some open source development models. ” …. from www. sakaiproject. org

Sourcing Options… + “Borrow” Build 1970 -80 s Build or Buy 1990 • ? ? ? Risks Build, Buy, or “Borrow” 2000 2010 • Control of destiny • Leverage of $$ • Learning • Ecology of innovation Benefits

Controlling Our Destiny…“Borrow” Functionality of Systems ü Integration ü Standards ü Innovation Cost of Systems ü Operations ü Maintenance ü Timing ü Evolution üBest Path for sustainable Economics and Innovation

www. sakaiproject. org Nat Hill Room at the Marriott Hotel, 3 rd Floor

Choosing Open Source and Partnering as an IT Strategy Brad Wheeler Associate Vice President & Dean Office of the VP & CIO Indiana University bwheeler@iu. edu