1 / 14

Enterprise Financial System (EFS)

Enterprise Financial System (EFS). Project Update Grants Management User Network October 13, 2006 www.finsys.umn.edu. EFS Project Update. Objectives: Status Proposed policy changes Next steps for project Q & A. The Latest. Analyze Phase completed

brooke
Download Presentation

Enterprise Financial System (EFS)

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. Enterprise Financial System (EFS) Project Update Grants Management User Network October 13, 2006 www.finsys.umn.edu

  2. EFS Project Update • Objectives: • Status • Proposed policy changes • Next steps for project • Q & A

  3. The Latest • Analyze Phase completed • Involved 100+ subject matter experts, teams & business process owners • Completed 50 conference room pilots • Reviewed 170 business processes • Determined the “fits” between requirements and PeopleSoft • Determined the “gaps” • Determined “to-be” business processes for each module

  4. Fits & Gaps Summary • Remember guiding principle is to install PeopleSoft as “vanilla” as possible • For all modules: • Total requirements = 3,472 • Total “fits” = 2,843 • Total “gaps” = 629 • Requirements met = 82 percent

  5. Phasing the Gaps • BPO’s, EFS Teams & Management joint effort • Currently underway • Critical for July 1, 2008 • Can wait until after go live • Commitment for a Phase 2

  6. Grants, Projects & Contracts • Primarily used by SPA & SFR, departments will use the data entered into GPC • Integration of sponsored data into one system

  7. Policy & Procedure Recommendations • Examples: • Facilities & Administrative processing • At what level we budget • Commitment Control • Cost Share tracking

  8. Accounts Receivable & Billing • Integrated services model • Larger impact on non-sponsored • Current structure for sponsored • Formalization of SFR procedures into policies

  9. Policy & Procedure Recommendations • Examples: • University wide policies for credit & collections • Central “lock box” • Depositing of Program Income • Automate Print & Mail Bills

  10. Accounts Payable & Expenses Budgets Accounts Receivable & Billing Treasury & Endowments Asset Management Integrated Financial System General Ledger/Chart of Accounts Purchasing & eProcurement Grants, Projects & Contracts

  11. Next Steps • Functional design • Technical design • Build • Test & User Acceptance Test • On track for July 2008 “go-live”

  12. Resources • Web site: www.finsys.umn.edu • Email: finsys@umn.edu • Team leads • Subject matter experts • Meetings like this!

  13. What are Your Questions?

  14. Have a great fall! Thanks everyone!

More Related