Kuali Timeline - January 2005

A Financial System of, by, and for Higher Education

Timeline

· August 2005

· July 2005

· June 2005

· May 2005

· April 2005

· March 2005

Timeline: January 2005

January 27th, 2005

Sally Jackson asks FSO to submit a proposal to join Kuali

January 26th, 2005

Kymber Horn and Mary Vega meet with two BCAC members to develop decision tree. Kuali Decision Tree

January 20th, 2005

Second meeting with Business Computing Advisory Committee. Mary Vega and Liz Taylor presented decision matrix. Sally asked for the negatives of joining Kuali. Group advised FSO to approach workflow from a business application solution, rather than a campus wide solution. Currently workflow does not exist, or is inadequate (FormLink). Intangibles for joining Kuali are many – workflow, possible replacement of FRS, learn from Indiana on project management, receive source code and knowledge transfer for minimal investment. No apparent negatives.

January 19th, 2005

Mark McGurk and Kymber Horn answered questions re: Kuali at Fund Accountants meeting.

January 10th, 2005

Barry Walsh, Bill Overman, Damon Dorsey visit the University and talk about Open/Community Source, Kuali and provide a short demo of their Financial Information System (FIS). 300+ University employees attended. 3D Announcement

January 12th, 2005

Mark McGurk and Kymber Horn met with College Academic Business Officers (CABO) for more Kuali discussions.

January 10th-14th, 2005

Andrew Hollamon, FSO lead developer spends a week in Indiana with developers from the other partner schools – Indiana, Hawaii, Michigan State and the other invitee, Cornell. The purpose of his visit was to team build with the other developers – could they get along? And to test the proposed technology- could they develop with the selected tools? The answer to both was yes. Andrew's Take on the Initial Kuali Developers Week

January 6th and 7th, 2005

Mark McGurk and Kymber Horn travel to Chicago to meet with functional representatives from each University to add and prioritize enhancements to the existing functionality of Indiana University's Financial Information System (FIS). For the past 10 years-Indiana has been collecting a list of enhancements to make to their FIS system. Prior to the functional meeting, Kathleen McNeely, Indiana’s functional rep asked the Indiana functional people to rank each enhancement as high, medium, or low. She gave the same list to Indianas' technical people and they ranked each enhancement as needing low, medium or large resource requirements.

The functional council took this list and added ones that were missing, for example, endowment tables and attributes. Then we added a category called “Essential” which meant that a school would not implement Kuali without it and therefore, it must be included in the appropriate phase. Then we categorized nonessentials as High, Medium and Low. High would most likely be included in phase 1 or 2 and Medium and Low would be phase 3. Kuali Scope document.