/
KFS Status Report 11-2013

KFS Status Report 11-2013

Owned by Carmen E Roode
Last updated: Dec 23, 2013


KFS Status Report
As of: November 21, 2013

KFS – Development – In Progress
A new roll-out date has been set for the project – July 2013. The delay was primarily to accommodate new organizational changes that will be made to our chart of accounts and also to allow the campus additional time to prepare for KFS. Testing of KFS has slowed down quite a bit due to other campus priorities and due to the impending changes to the organizational structure. Integration testing cycle 8 is still open for those that can participate in testing. The organizational changes are expected to be applied in December and campus testing will resume in January. Plans and milestones are being updated to reflect the new timeline.
Identified bugs continue to be fixed, and we are also making good progress on various data reconciliations and interfaces. We are working on the preparations for our production environment and we are in the process of planning a phased roll-out of various KFS functions.

  • Integration Testing –
    • Integration testing cycle 8 started on September 10 and has not yet been completed.
    • Some of our central office testing units are making great progress in testing while others have been less engaged.
    • Medical center testing is moving along well. A missing interface was identified and has now been implemented.
    • We continue making adjustments to Purchasing workflows.
  • Chart of Accounts and Data Conversion –
    • We are working on collecting the new organizational changes for campus departments and related account/workflow/contract manager/budget changes related to these organizational changes. We expect to have all these collected by the end of the month
  • KFS Decision Support –
    • The DS team continues to refine and improve the KFS reports. Drill downs were incorporated in several reports.
    • We allocated a business analyst to work with our users on report specifications for PURAP, interfaces, reconciliation, and other module reports. This should help us become more productive with report development.
    • [more details]
  • Feeder, Shadow and Campus System Migrations/Testing –
    • Feeder systems developers have their systems pretty finalized and are working to test their systems with each test cycle.
    • [more details]
  • SciQuest –
    • Made minor adjustment to the SciQuest interface, but coding is basically done.
    • We have entered another black-out period due to the delay and we plan to reengage with Sciquest around April of next year for final testing and roll-out preparations.
  • Portal –
    • KFS is now available in SNAPTest and in the ZotPortal staging instance.
    • ZotPortal with current SNAP content will go live in early December, and KFS content will be in ZotPortal when KFS goes live.
  • KSAMS –
    • KSAMS is getting close to needing to be deployed since it is needed by our new Cognos student data warehouse and other new applications. We plan to roll KSAMS out in February 2014. It requires our KFS chart of accounts and Rice environment, so we will be moving portions of KFS to production for the KSAMS system.


  • KFS Other –
    • Stronger engagement from our central office leaders has started as they work to prepare their units and the campus on training and support of KFS. We look forward to continued interest and embracing of KFS in the coming months.
    • Several team members and SMEs attended Kuali Days 2013 in San Diego this week.
    • Allocated Daniel 50% time to work on Jason's middleware team.
    • Released 2 rSmart developers from the project since development is now largely done.



KFS Issues:

  • Testing of KFS by central offices has slowed down but we hope to see things pick up soon. We need to have all central office staff learning KFS and testing out their work/processes in KFS. They need to be prepared to answer questions from their users once KFS goes live.
  • Organization changes – currently expecting over 500 organizational changes. Because of all the changes, new organization numbers were also assigned. This could require additional changes to systems if they are referring to the older organization numbers.
  • Significant testing of KFS will be required after the Organizational changes and related tables are updated in KFS. KFS is still largely untested due to lack of manpower for testing. We will work to test key functions and would like to solicit testers from the campus to help with more wide-spread testing.