/
KFS Status Report 03-01-2013

KFS Status Report 03-01-2013

Owned by Carmen E Roode
Last updated: Jul 08, 2013Version comment


KFS Status Report
As of: March 1, 2013

KFS – Development – In Progress
The KFS project team, subject matter experts, system migration teams, campus testers, trainers, KFS report design and development teams, and numerous other individuals supporting the KFS project are in full swing as we approach our target rollout four months from now. We are deep in the testing and bug fixing phase of the project with continual problems being identified and fixed as planned. We are enhancing our staffing and campus support to prepare for the most intense part of the project in the coming months. Our target roll-out is July 1, 2013 and we are working to refine our cutover planning and are making preparations for assisting the campus with this change.

  • Integration Testing –
    • We have begun our integration testing which is working to simulate KFS in a production environment. This includes full end to end testing of the system including all interface points, file transfers to and from KFS both within the campus and outside the campus, check write process, bank transfers, processing documents, and more.
    • Full Integration tests are scheduled to run each month between January and June with the expectation that each test will become more complete and run cleaner with each passing cycle.
  • KFS Modifications –
    • Work continues to finish up on modifications that were identified last year.
    • Several new modifications are being identified during the current testing phase as we learn what needs to be adjusted in the systems. The most critical modifications will be addressed immediately and the rest will be pushed off until after we roll out KFS.
  • TEM (Travel and Entertainment Management) –
    • TEM has been installed and is now incorporated in with the rest of the KFS modules.
    • System configuration has been completed and we are now able to start fit gaps and functional testing of TEM.
    • We are currently planning to roll out the TEM module by July 2013 along with the rest of KFS.
  • Chart of Accounts –
    • KFS Accounts have been converted and are now locked. If changes to accounts are needed or new accounts need to be created, this is being done through the KFS front end.
    • Plant object codes for the med center and campus have also been defined.
    • Campus units are starting to adjust their organization units as they work to define KFS workflow processing for their units.
  • Functional Testing and Training –
    • Beta testers from several campus units have been testing specific KFS documents since January. Along with learning to use the system, they are helping to identify problems in the system. They have been entering hundreds of documents each week through training sessions, labs and testing at their desk.
    • Beta testing is now on hold until identified bug fixes are completed.
    • Additional testing and training was started by central offices.
  • KFS Decision Support –
    • The decision support team continues to make progress on report specifications and building of data models despite being a bit behind schedule.
    • Report development will now begin in March.
    • The team is supplemented by the campus Decision Support Work Group which is helping to define and will build additional campus reports.
    • [more details]
  • Feeder and Campus System Migrations/Testing –
    • Feeder and campus system migrations continue in their development and now developers in the first phase of the migration are participating in the KFS integration test cycles. Developers along with the KFS technical team continue to resolve any issues uncovered in the testing.
    • Ledger results will be shared with system owners as data becomes cleaner in the in the ledger.
    • [more details]
  • Cut-Over Planning –
    • Cutover planning has started with separate plans being detailed for each functional module and technical activities. Proper planning is needed to identify when processes will be last managed within the current systems, and how the switch over to the new system will occur.
    • Many of these activities occur in the months preceding and the months following the actual implementation date.
  • SAMS and KIM –
    • Planning is occurring on how SAMS and KIM (Kuali Identity Management) will manage user access for KFS, KC, and other campus applications that currently use SAMS.
    • KIM will be the future access management system for our campus, and SAMS will continue to manage access primarily for PPS and other HR applications.


Issues

  • Large volume of work to do before June 30.
  • Behind schedule in Decision Support group. Will work to ensure the most critical reports are created first. Reports will continue to be developed past the implementation date (i.e. quarterly reports, year end reports)
  • Campus readiness – there is a lot to do to ensure central and campus units are prepared for KFS. This will be a significant change for the campus which can be difficult to grasp until you see your data in the system and have to manage it.
  • Testing – A lot more testing is needed to ensure the system works properly upon roll-out. Need to ramp up system testing in the next month so that fixes can be made before our final code freeze next month.
  • TEM work is behind schedule. Still have not tested the system.