1 / 17

Implementing KFS Release 2: Strategies and Outcomes from UC Davis and MSU

This document summarizes the implementation of Kuali Financial System (KFS) Release 2 at UC Davis and Michigan State University (MSU). Key topics include mission objectives, approaches to deployment, technical environments, and outcomes. Both institutions focused on reviewing installation documentation, identifying configuration issues, and testing the new functionalities of KFS. The collaborative efforts led to successful installations, smooth functional testing, and the establishment of next steps for ongoing improvements. Insights and lessons learned, including the lack of major obstacles, signal a successful implementation process.

odessa
Télécharger la présentation

Implementing KFS Release 2: Strategies and Outcomes from UC Davis and MSU

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Implementing KFS Release 2(Let’s Get Cookin’!) Susan Moore / Jonathon Keller, UC - Davis Vince Schimizzi / Mike Criswell, MSU

  2. Topics • Mission • Approaches • Technical environment • Distribution: What do you get ? • Goals • How did it go? • Next steps • Final thoughts (open discussion)

  3. Mission (UC – Davis) • Stay ahead of a production implementation in identifying issues. • Review and provide input to installation and configuration documentation. • How to structure deployment of application. • Review new implementation functionality of KFS release 2.

  4. Mission (MSU) • Review, learn, and provide input on installation and configuration documentation. • Begin to identify and review MSU configuration issues and to conduct modeling scenarios. • Review new functionality in KFS release 2.

  5. Approach (MSU) • For bootstrap version (like a go-live installation) much attention was given to data, setup and configuration. • Prior to release, functional/technical staff reviewed process from KFS release 1 and developed plan for KFS release 2. • Upon receiving pre-release software, up and running in 3 business days. • 3 technical staff, 7 functional staff.

  6. Approach (UC-Davis) • Wanted a “fresh” perspective. • 1 technical staff part-time. • 2 functional staff part-time.

  7. Technical Environment

  8. Distribution: What do you get? • Kuali Financial System • Demo Data Set • Bootstrap Data Set • Database Import/Export Tool • Kuali Rice • Kuali Enterprise Workflow • Sample Patch for Extended Attributes

  9. Goals (MSU) • Load MSU sample data. • Implement an extended attribute. • Create a custom business rule. • Replace CAS Authentication with MSU’s home-grown authentication. • Build the application from source. • Test application.

  10. MSU Load Process

  11. Goals (UC - Davis) • Build the application from source. • Test application.

  12. How did it go? (UC - Davis) • Installation • Functional testing

  13. How did it go?(MSU) • Installation went well (some expected challenges) • Functional testing of transaction and maintenance eDocs went smoothly. • Experience from prior load (table load sequence) was helpful in identifying new tables and fields. • Referential integrity constraints helped ensure proper data load. • MSU created Entity Relationship (ER) diagrams on application which was useful in understanding the underlying data.

  14. Next Steps (MSU) • Install actual Kuali release 2 application. • Continue testing application once up and running • Maintenance Edoc • Transaction Edoc • Batch processes • Workflow capabilities • Etc. • Create supplemental implementation documents for MSU.

  15. Next Steps (UCD) • Load institutional data. • Create additional business objects and extended attributes on existing objects. • Replace CAS authentication with UC authentication.

  16. Final Thoughts • Overall smooth process. • The lack of any substantive “show stoppers” is itself a sign of success.

  17. Questions ?

More Related