The Kuali “Community Software” Initiative

1. The Kuali “Community Software”Initiative Council of Deans and Vice Chancellors February 10, 2009

2. Today’s Agenda Community Software What is it? Why is it of interest on a global scale? How can it help UC Davis meet its goals? How does it relate to the campus IT Roadmap?

3. “Community Source” A hybrid combining advantages of Purchasing from a commercial source Building an application yourself The historical “open source” approach Community Software means building with others based on mutual priorities and investments Leverages accumulated wisdom about structure and governance

4. Community Software at UC Davis Sakai Kuali

5. “Sakai” A Collaborative Learning Environment Chosen after “build/buy” review Conclusion that this was “build AND buy” Serves as the engine for SmartSite Focus is on learning and collaboration “Partners” include Indiana U, U Michigan, Cambridge, Tulane, UCB, UCSB, Yale, Stanford, Harvard, MIT; 65+

6. Kuali Advantages • Community source project • J2EE architecture and middleware products • Tight integration and similar look and feel • Based on proven technologies and proven baseline systems • Opportunity for collaboration with UC’s and other Higher Education institutions • Institutions can choose to implement only those functional elements that meet their needs and extend certain functionality • No vendor or licensing fees

7. Kuali Communities

9. Kuali Applications Core Applications • Kuali Financial System (KFS) • Kuali Stores • Kuali Coeus (KC) • Kuali Student (KS) • Kuali Rice Potential Future Applications • Kuali Payroll/HR • Kuali Business Continuity (UC Ready)

10. Kuali Investing Partners KFS Investing Institutions UCD, UCI, UCSB, UCOP USC, Colorado State, Cornell, Indiana, Michigan State, Arizona, Hawaii (10+) KC Investing Institutions UCD, UCB, MIT, Arizona, Cornell, Indiana, Iowa State, Colorado State (7+) RICE Investing Institutions UCSD, U Washington, Iowa State, Indiana, Cornell Kuali Student Investing Partners UCB, USC, MIT, U Washington, Maryland, Carnegie Mellon (4+)

11. Kuali – Planned Deployments at UCD • Kuali Financial System (KFS) • Phased implementation beginning July 2010 • Future replacement for DaFIS Transaction Processing and General Ledger • Very little change to DaFIS Decision Support • Kuali Coeus (KC) • Fills gap for electronic research administration • Pilot implementation January 2010 • Kuali Rice • New Middleware services • Production implementation March 2009 • Collaboration(Campus, UC, Higher Ed Community)

12. Highlights of Kuali Coeus (KC) • Functionality is based on MIT’s Coeus System • Budget Development Tool for PIs • Electronic document routing • Research Compliance Management for IACUC & Bio-Safety • Integration with Kuali Financial System (KFS)

13. Benefits of Release 1 Pilot at UC Davis • Proposal Development Tools • Minimize the administrative effort it takes the PIs to develop and route proposals • Allows the PIs to leverage previous templates and/or proposals to develop new ones. • Integration with the Campus administrative and middleware systems will provide up-to-date and accurate information and eliminate unnecessary data entry • Budget Development & Management Tool • The PIs can develop multiple budget scenarios per each proposal • Upon awarding the grant, the budget is integrated and synchronized with KFS

14. Benefits of Release 1 to UC Davis • Electronic Routing of Proposals • PIs can route proposals electronically within the department and route it to Office of Research • System will be integrated with the Campus identity management system to minimize user maintenance and improve the data accuracy • Contact information will be populated from the Campus directory to minimize data entry • Grants.gov integration for federal grants • System to system integration will eliminate dual entry for PIs for federal grants (Adobe & Pure Edge)

17. Kuali Rice and “Middleware” Authentication (who you are) Authorization (what you get to do/see) Identity Management Campus Portal Workflow A “Service Bus” IT Administrative Services and Middleware Components

18. The UC Davis IdM Initiative • An essential project shared by the Davis and the Sacramento campus- • Enables a common mechanism to authoritatively identify faculty, staff, students, patients, affiliates and visitors • Kuali RICE provides a standard way for the IdM suite of applications to connect with enterprise aps –

19. UC-wide participation Results from Systemwide Middleware Survey • UC Campuses planning to use Rice • UCB; UCD; UCI; UCM; UCSD

20. Connie Melendy Bella Corbin Diane Davies-Connelly Lora Jo Bossio Jill Blackwelder-Parker & Leslie Hays Mike Allred Dave Shelby Karen Hull & Mike Allred

21. Relevance to Academic Units • Academic Units often need to- • access data from many different sources • Make use of middleware tools (workflow, IdM, portal) • Initiate transactions in enterprise applications (i.e., Banner)

22. Upcoming Forums/Information Sharing • PPT will be available online and updated • Additional Forums • Coordinating Council (Conveners) • AdMAN • Senior Advisors • Technology Infrastructure Forum • Dean’s Technical Council • Contacts: • Mike Allred: jmallred@ucdavis.edu • Dave Shelby: drshelby@ucdavis.edu • Lora Jo Bossio: ljbossio@ucdavis.edu • Kathy Olsen: kcolsen@ucdavis.edu