1. Open Source Solutions for Education all materials ©2004 the rsmart group Open Source Applications for Higher Education

2. Open Source Solutions for Education all materials ©2004 the rsmart group Kuali & rSmart Corporate Objective HE Community Source “Commercial” Partner rSmart committed to change applications software business model proprietary software (controlled by vendors) 1968 - 2005 2005 - open software (owned by HE Community)

3. Open Source Solutions for Education all materials ©2004 the rsmart group Kuali & rSmart rSmart Committed to Community Source Last 4 years ( as well as last 35 years) Long term obligation is to insure HE confidence in Community Source solutions - Kuali - Sakai - OSPI - Other related “modules” (all in concert with Community) “Commercial partner” needs to be 100% committed to open source solutions.

4. Open Source Solutions for Education all materials ©2004 the rsmart group Kuali & rSmart “Commercial” partner is required to: Participate in creation of Community and its structure (common interests) Become totally knowledgeable of solutions and the process of their implementation “Develop” qualified personnel for implementations Participate in development (representing the interests of existing and future Community) Provide - information center implementation process (include Community Partners) training subscription service for on-going support of systems’ sustainability

5. Open Source Solutions for Education all materials ©2004 the rsmart group Kuali & rSmart Financial Systems We know financial systems - 3 Kuali partners are using FRS - 6 colleges present are FRS users “We” identified IU FIS as a system which can become the “standard” We are well aware that the advantages to HE are compelling!

6. Open Source Solutions for Education all materials ©2004 the rsmart group Kuali & rSmart Advantages Cost savings - considerable Community development, enhancements, governance, ownership, potential for standard Designed for HE, by HE Free from being “locked in” Community leadership will lead solution future Technology – interoperable, open standards, open architecture, web-oriented, community endorsed Sustainability “guarantees” are in place

7. Open Source Solutions for Education all materials ©2004 the rsmart group Kuali & rSmart Is Kuali suited for your campus? - Today’s session - Kualikualifier might be of further help

8. Open Source Solutions for Education all materials ©2004 the rsmart group Kualikualifier Financial System Fit Analysis 1. Interview functional stakeholders – at your site 2. Interview technical stakeholders - at your site

9. Open Source Solutions for Education all materials ©2004 the rsmart group Kualikualifier Interview functional stakeholders to indentify: - where functionality of Kuali meets local needs - fit/gap analysis to determine how best utilize system flexibility - changes to chart, if needed - features of legacy code might become attributes - attributes which might be maintained for control and reporting - Kuali Workflow can be of added value to total institution environment - which modules would be required and when - special reporting needs - implementation process - sequence of training - possible changes in business processes - issues and opportunities for improvements - roadmap with a time line for implementation and integration - participation in Installation Partnership weighed

10. Open Source Solutions for Education all materials ©2004 the rsmart group Kualikualifier Interview technical stakeholders to determine: - Kuali architecture - open source operating environment - links to existing systems - migration to open source (open standards) - training needs and timetable - participation in Installation Partnership

11. Open Source Solutions for Education all materials ©2004 the rsmart group Kualikualifier Process for Kualikualifier visit: 1. Set up agenda for visit prior to visit 2. Visit and conduct interviews (2 – 4 days with 2 people) 3. Record interview sessions 4. Report observations a week later 5. Be available for discussion about report

12. Open Source Solutions for Education all materials ©2004 the rsmart group Kualikualifier On-going principle in community source business model… Community drives their own future Minimal “sales” and marketing expense required –Therefore, HE must take initiative! –Individual institutions need to step forward. –Participants should become involved in Community. –Determine how to get involved and get involved. –In Kuali, door is open for early implementation partners.

13. Open Source Solutions for Education all materials ©2004 the rsmart group Potential implementation support Implementation activities Can be started 8 to 9 months prior to go-live, but no later than 6 months prior to go-live.

14. Open Source Solutions for Education all materials ©2004 the rsmart group Potential implementation support Table set up (18 – 22 days) - Define Chart of Accounts Structure - Define chart - Define organization code - Account responsibility table - Sub account table - Object code table - Sub object code table - Fund group - Sub fund group - Grants and contracts attributes - Vendor information - Workflow definition and setup

15. Open Source Solutions for Education all materials ©2004 the rsmart group Potential implementation support Training (10 – 20 days) Develop and deliver train the trainer modules and materials for each of the key financial business areas –Financial docs –Grants and contracts –Labor distribution –Asset management –Accounts receivable –Accounts payable –Purchasing –Workflow Develop conversion programs (10 – 20 days) Develop specifications for attributes and balances for bringing them forward Vendor information Capital assets

16. Open Source Solutions for Education all materials ©2004 the rsmart group Potential implementation support Build pilot (20 days) –Verify environment –Install software –Configure environment –Build test data –Run tests Project management (30 days) –Project plan –Monthly project reviews –Monthly project status reports Customization and technical support (10 – 20 days) –Limited customization –Technical overview of the system Contingency (60 – 100 days) –Backfill –Transition support at cutover –Additional customization