360 likes | 483 Views
Kuali Days Successful Financial System Implementation Indianapolis April 11, 12 2006. Community Source. Kuali (integrated with Sakai) KFS next modules: KWF KSSS KRA KHR Modules integrated with today’s ERP systems All Kuali systems fully integrated.
E N D
Kuali Days Successful Financial System Implementation Indianapolis April 11, 12 2006
Community Source • Kuali (integrated with Sakai) • KFS next modules: • KWF KSSS • KRA KHR • Modules integrated with today’s ERP systems • All Kuali systems fully integrated
Kuali Development Community NACUBO
Kuali Development Community Indiana University
Kuali Development Community Michigan State University
Kuali Development Community University of Hawaii
Kuali Development Community University of Arizona
Kuali Development Community Cornell University
Kuali Development Community San Joaquin Delta Community College
Kuali Development Community rSmart
Kuali Development Community The Andrew W. Mellon Foundation
Why Kuali ? • Cost savings – today and future • Community driven - development, enhancements, governance, ownership, potential for standard • Solution sharing • Designed for higher HE by HE • Free from being locked in • Architecture update supporting web services
Kuali Development Community • Suggested processes • Transfer IU FIS with enhancements • Documentation • Training materials
Implementation Community • Implement modules • Build links to existing ERP systems • Enhancements • Participate in Kuali future • Set standards for implementations
Total Community Development partners + Implementation partners = Kuali Community Board Committees
Kuali Business Model • Develop for and by higher education • Community supports community • Community grows community • Members in control of destiny • Members can predict and plan budgets • Sustainability insured
Business Model Changes Behavior • Community makes all decisions • Members take control of future • No sales/marketing; therefore, colleges need to be proactive • A chance to step out and create your own gains • Chance to join communities suitable to your requirements • Your input makes a difference only if you are in
How Would You Participate? • Take initiative • Look into Community Source • Talk with Community Members • Take steps toward decision • Implement modules that fit schedule
the rSmart Group The rSmart group is an open source application software company (e.g. Red Hat) serving its subscribers in the higher education market We package, certify, deploy and support a suite of enterprise financial and collaborative learning applications for colleges and universities We, along with integrators, help support subscribers
Corporate Objective HE Community Source “Commercial” Partner rSmart committed tochange applications software business model proprietary software (controlled by vendors) 1968 2005 open software (owned by HE Community) Kuali & rSmart
What Role Does rSmart Play? • Add to sustainability • Answer the phone • Create stacks insuring reliability • Offer subscription • Offer KualiKualifier • Initial readiness • Offer more extensive fit/gap analysis • Support implementation, where desired
Planning Operations & Support Implementation Strategic Planning High Availability Configuration Admin Support RemoteSystem Management System Integration End User Support Installation & System Configuration Custom Application Development Training Needs Assessment Migration rSmart Services Full-Service Partner
Why rSmart ? • Vendor Independence • More Value for IT $$$ • Rapidly Address User Needs • Ease of integration/interoperability • Broader platform support • Improved Security • Single Source Accountability • Platform Certification • Over 30 years of Higher Ed experience • Focus is Higher Ed, not distracted by other markets
How May We Assist You? www.rSmart.com
Look at whether or not to Proceed • Get a quick assessment as to where you fit • Where do you start? • When do you start? • What to implement? • Who to involve on campus?
KualiKualifier Client Service Kuali Kualifier Plan Design Implement Support Project Management
KualiKualifier Review Institutional Strategies Identify Issues Document High Level Requirements Meet with User Community Stakeholders Review User Communities Develop Recommend-ations Present Recommend-ations Start Plan 1.9 Identify Deficiencies Document Integration Points Review Application & Technology Strategy • Inputs • Institutional snapshot and future vision • User Community snapshot and future vision • Technology snapshot and future vision • Stakeholder high level requirements • Integration points • Outputs • Recommendations • Gap Analysis • Issues • Action Plan • Show-stoppers
Project Plan Assistance Client Service Kuali Kualifier Plan Design Implement Support Project Management
Resource Planning Time Commitment Resource Availability Backfill Plan Organizations Steering committee Project director Functional committee Focus groups Typical Implementation Questions • Budget Planning • New staff and Backfill cost • Travel • Communication • Ongoing support cost • Training
Project Plan When to Go-Live Project Timeline Pre-planning period Implementation timeline Setting Important milestones Prevent scope creep Communication Plan Audience, frequency and medium Managing expectations Marketing plan Buy-in from stakeholders Typical Implementation Questions
Design and Implementation Assistance Client Service Kuali Kualifier Plan Design Implement Support Project Management
Design and Implementation Assistance Design Code Tables Define Attributes Design Workflow Design Chart Structure Analyze Reporting Needs Installation Configuration Setup Plan Support 2.3 2.6 • Inputs • Technical Requirements • Hardware requirement • Database requirement • Functional Requirements • Organizational Structure • Chart of Accounts • Required Attributes • Business Process • Reporting Needs Outputs • Hardware configuration • Software installation • Chart of Accounts • Attributes • eDoc Business Rules • Test Plans
Support Client Service Kuali Kualifier Plan Design Implement Support Project Management
Support Application Support Expert Support RSN Knowledge-base, Downloads, etc. Survey User Community Webinars What do you need? Implement Ongoing 2.3 2.6 • Inputs • Training Activities • Testing and Production Activities • Marketing and Roll-Out Activities Outputs • Schedule for review and planning • Plan for future enhancements • Plan for additional training • Plan for production communications • Plan for support