1 / 69

FMLoB and BFELoB Update June 1, 2009

FMLoB and BFELoB Update June 1, 2009. Financial Management Line of Business (FMLoB) Overview of FMLoB Overall Goals Stages of FMLoB Other FMLoB Activities Specific Goals for 2009. Budget Formulation and Execution Line of Business (BFELoB) Overview of BFELoB Goals

darena
Download Presentation

FMLoB and BFELoB Update June 1, 2009

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. FMLoB and BFELoB Update June 1, 2009

  2. Financial Management Line of Business (FMLoB) • Overview of FMLoB • Overall Goals • Stages of FMLoB • Other FMLoB Activities • Specific Goals for 2009

  3. Budget Formulation and ExecutionLine of Business (BFELoB) • Overview of BFELoB • Goals • Activities and Accomplishments

  4. Overview of FMLoB • In 2001 President Bush created the President’s Management Agenda (PMA) to address the need for citizen-centered, results-oriented, and market-based Federal government initiatives. • Pursuant to the PMA, the Office of Management and Budget (OMB) created the Lines of Business (LOB) initiatives which address redundant IT investments and business processes across the Federal Government. • The Financial Management Line of Business (FMLoB) was created as part of these initiatives.  

  5. Overview of FMLoB (cont’d) • The Financial Systems Integration Office (FSIO) within the General Services Administration (GSA) is the program manager for FMLoB. • The FSIO was formerly known as the Joint Financial Management Improvement Program (JFMIP) staff office.

  6. Overview of FMLoB (cont’d) • The FSIO has three major areas of responsibilities: • Core financial systems requirements development, testing and product certification. • Supporting the Federal financial community on priority projects. • Conducting outreach through an annual financial management conference and other related activities. • To learn more about FMLoB visit www.fsio.gov.

  7. Overall Goals The goals of FMLoB are that Federal agencies are implementing financial systems that: • Provide timely and accurate data available for decision making; • Facilitate stronger internal controls that ensure integrity in accounting and other stewardship activities;

  8. Overall Goals (cont’d) • Reduce costs by providing a competitive alternative for agencies to acquire, develop, implement, and operate financial management systems through shared service solutions; • Standardize systems, business processes and data elements; and • Provide for seamless data exchange between and among Federal agencies by implementing a common language and structure for financial information and system interfaces.

  9. Stages of FMLoB

  10. Stage 1 - Transparency • In determining the best options available when modernizing financial systems, the Federal financial community must have sufficient information and clear direction on how to evaluate the performance and cost of shared service alternatives; i.e., Shared Service Providers (SSP’s) as well as clarity on what steps Federal agencies are expected to undertake in order to migrate to an SSP.  • Two specific projects are underway to achieve additional transparency: • Establishment of Common Performance Measures • Development of Migration Planning Guidance

  11. Stage 1 – Transparency (cont’d) Establishment of Common Performance Measures • This project will result in standard quality and cost measures for agencies to benchmark and compare the performance of financial system alternatives.

  12. Stage 1 – Transparency (cont’d) Phase I - IT Infrastructure Hosting & Administration and Application Management Services • Monthly data collection and reporting began in April 2007. • Metrics are collected in a web based environment at the Federal Interagency Databases Online (www.FIDO.gov) as part of the Chief Financial Officers’ Metric Tracking System (MTS). • SSPs and CFO Act Agencies report data.Non-CFO Act agencies are not required to report but are encouraged to participate.

  13. Stage 1 – Transparency (cont’d) Phase II – Business Processes • In August 2008, a panel consisting of Agency CFOs and Deputy CFOs met with members of the FMLoB Performance Measures work stream to discuss long-term objectives and strategies for development of agency-wide, financial management measures. • Since the August meeting, and based on the feedback received from this panel, the Performance Measures work stream has focused on developing a core repository of all financial management-related measures, including those currently collected and those that should be considered, and industry benchmarks.

  14. Stage 1 – Transparency (cont’d)

  15. Stage 1 – Transparency (cont’d)

  16. Stage 1 – Transparency (cont’d)

  17. Stage 1 – Transparency (cont’d) Development of Migration Planning Guidance • This project will result in comprehensive guidance that helps Federal agencies describe, prepare for, and manage an agency’s migration to an SSP. • This guidance will also include a definition of the full range of services to be provided by all SSPs and a description of the “rules of engagement,” including templates for service level agreements outlining provider and client responsibilities.

  18. Stage 1 – Transparency (cont’d) Acquisition Advisory Team • Developing tools that will assist agencies in developing solicitations to upgrade or implement financial systems. • These tools are intended to assist agencies by streamlining the process of developing requests for proposals for financial management system shared services including services for hosting, application management, system integration, and transaction processing.

  19. Stage 1 – Standardization • In order to mitigate the cost and risk of migrations to an SSP and to improve the quality and usability of financial data government-wide, the Federal government must ensure greater standardization of business processes, interfaces, and data. • Two specific projects are underway to provide standardization: • Development of Standard Business Processes • Creation of Common Government-wide Accounting Classification Structure (CGAC)

  20. Stage 1 – Standardization (cont’d) • Once established, the standards from these two projects will be incorporated into the existing FSIO core financial systems requirements and be tested during the FSIO software qualification and certification process. • Once the software products are certified as meeting FSIO core financial systems requirements, Federal agencies will only be permitted to purchase, and SSPs required to implement, the certified products as configured with the standards.

  21. Stage 1 – Standardization (cont’d) Development of Standard Business Processes • The Federal Financial Management Standard Business Processes establish the framework for consolidating and optimizing financial accounting practices in the Federal Government to improve cost, quality, and performance government-wide.

  22. Stage 1 – Standardization (cont’d)

  23. Stage 1 – Standardization (cont’d) Funds management • Includes processes related to the establishment of budgetary authority, funds distribution and funds control.

  24. Stage 1 – Standardization (cont’d) Payables management • Includes processes from requisition to payment for commercial contracts and small acquisitions disbursed by Treasury. • The payables document was developed by conducting weekly focus group and periodic working group meetings with agency representatives, Federal SSPs and commercial software vendors.

  25. Stage 1 – Standardization (cont’d) Receivables management • Includes steps from establishing accounts receivable due from the public, billing, collection and application of receipts, dunning, allowance for loss and write-off, credit memo and returns, waiver of interest, administrative costs and penalties, and installment plans. • The receivables document was developed by conducting weekly focus group and periodic working group meetings with agency representatives, Federal SSPs and commercial software vendors.

  26. Stage 1 – Standardization (cont’d) Reimbursables management • Outlines business processes for administering and managing interagency buy/sell transactions. The document spans the full lifecycle of an Interagency Agreement (IA) from establishing an agreement between a Buyer (requesting agency) and Seller (providing agency) to close out of the IA. • The reimbursables document was developed by conducting weekly focus group and periodic working group meetings with agency representatives, Federal SSPs and commercial software vendors.

  27. Stage 1 – Standardization (cont’d) Changes to Expect as a Result of Reimbursables Management Document • Incorporates an intragovernmental solution system which will house information related to IAs including orders, bills, payments and collections, earned unbilled information and order close out. • Standard of monthly billing. • Recording of earned unbilled amounts.

  28. Stage 1 – Standardization (cont’d) Changes to Expect as a Result of Reimbursables Management Document (cont’d) • Approval/rejection of bills within 7 calendar days or else funds transfer automatically. • Standard of monthly reconciliation with trading partner where work in progress/earned unbilled reporting is completed so both partners record proper accruals.

  29. Stage 1 – Standardization (cont’d) Reports management • FSIO established core reporting and content based reporting groups. • The groups were tasked with reviewing current reporting requirements, identifying reporting deficiencies, recommending changes to existing reporting requirements, defining new reports and identifying changes to existing reports.

  30. Stage 1 – Standardization (cont’d) The Core Reporting Team • Stratified reports into several reporting categories: Financial Statements, General Ledger, Payment Management, Reimbursable Management, Receivable Management, System Management and Treasury Reporting; • Reviewed existing reporting requirements;

  31. Stage 1 – Standardization (cont’d) The Core Reporting Team (cont’d) • Solicited Transformation Team members to identify individuals who could serve on the content based reporting groups; and • Prepared documentation on new, as well as existing reports, for review by the content based reporting groups.

  32. Stage 1 – Standardization (cont’d) Segment Architecture Launch Team (SALT) • This team has been organized to map and standardize data elements used in interfaces. • Agencies, including ARC, have made presentations on their existing interfaces in their core financial system detailing whether they were interfaces in or out and batch or real time.

  33. Stage 1 – Standardization (cont’d) Creation of Common Government-wide Accounting Classification Structure (CGAC) • This project will result in a uniform accounting classification structure, layout and definitions. • Establishes a standard way to classify the financial effects of government business activities. It includes data elements needed for internal and external reporting and provides flexibility for agency mission-specific needs.

  34. Stage 1 – Standardization (cont’d) CGAC (cont’d) • The standard definition process will also require modifications to central agency (i.e., FMS) reporting systems. • Implementation guidance will be developed to help each agency analyze the gap between existing systems and the FMLoB standards so that agency-specific implementation plans can be developed.

  35. Stage 1 – Standardization (cont’d) CGAC (cont’d) • Each agency will be required to meet with OMB to discuss current status of CGAC within the agency. • In March 2009 ARC provided our strategy as well as a CGAC gap analysis to Treasury for their meeting with OMB. • ARC's strategy for becoming CGAC complaint is to incorporate CGAC as part of our upgrade to Oracle version R12 which should occur after the completion of the current commercial hosting migration project.

  36. Stage 1 – Standardization (cont’d) CGAC User Group • Formed in January 2009 to share knowledge and leverage best practices of agencies as they implement CGAC. • Group includes representatives from most of the CFO Act agencies. • After grouping them by software vendor, various agencies have made presentations on their status and plans for implementing CGAC.

  37. Stage 1 – Standardization (cont’d) CGAC Comparison • CGAC has 74 elements • 20 elements are user entered • 54 elements are derived or based on system configuration • Some of the user entered elements are optional • Ultimately Oracle configuration may make these mandatory • A comparison of elements currently entered by users in Oracle to user entered elements in CGAC follows.

  38. Current Oracle User Entered CGAC User Entered Mandatory Internal Fund Code Budget Fiscal Year USSGL Account Internal Organization Code Object Class Code Program Code Credit Cohort Year Government-wide Project Code Mandatory • Fund • Budget Fiscal Year • USSGL Account • Cost Center • BOC • Reporting Category • Cat B Apportionment • Cohort • Project Code • Future Use 1 • Future Use 2 • Optional • Cost Center Code • Strategic Goal Code • Project Code • USSGL Account Extension Code • Object Class Extension Code • Revenue Source Code • Activity Code • Critical Agency Mission-Specific Fields 1 - 5

  39. Stage 2 – Competitive Environment & Seamless Data Integration • In order to enable improved performance of financial systems, the FMLoB envisions more competitive alternatives for financial systems and an environment where financial data can be more easily compared and aggregated across agencies.

  40. Stage 3 – Results • When the FMLoB goals are fully realized, agencies’ data will be more timely and accurate for decision-making and there will be improved government-wide stewardship and accounting.

  41. Stage 3 – Results (cont’d) • More timely and accurate data will result from the standardization and seamless data integration efforts, including the implementation of centralized interfaces between core financial systems and other systems. • These efforts will focus on promoting strong internal controls and ensuring the integrity of accounting data.

  42. Other FMLoB Activities SSP Forums • Brings together FSIO, OMB and senior officials from the Federal SSPs to promote information sharing, improve communication and encourage collaboration between the key FMLoB stakeholders and designated SSPs in order to foster improvements in Federal financial management.

  43. Other FMLoB Activities (cont’d) Transformation Team • Includes representatives from most of the 24 CFO Act Agencies who are subject matter experts serving on behalf of their respective agencies. • Members review FMLoB draft deliverables and monitor ongoing progress.

  44. Other FMLoB Activities (cont’d) Transformation Team (cont’d) • As an Agency’s financial expert, their guidance and recommendations, as well as communicating agency concerns, are equally essential in driving the success of the FMLoB and standard business processes development.

  45. Other FMLoB Activities (cont’d) Transformation Team (cont’d) • Team members carry the dual responsibility of ensuring the successful transformation of the FMLoB as well as making certain their own Agency will be prepared to implement the process.

  46. Specific Goals for 2009 • Finalize the business process standards for Reports Management and Reimbursables Management. • Complete update of the Core Financial System Requirements.

  47. Specific Goals for 2009 (cont’d) • Develop and begin implementing a change management strategy for agencies implementing the FMLoB standards. • Develop testing materials that incorporate updated requirements.

  48. Overview of BFELoB • The initiative began in spring 2005 as a workgroup of the Budget Officers Advisory Council (BOAC) charged with exploring the potential for improving Federal budgeting. • The Budget Formulation and Execution Line of Business (BFELoB) was officially announced as a formal line of business in February 2006 as part of the President's FY 2007 Budget.

  49. Overview of BFELoB (cont’d) • The focus is to build a "budget of the future" by promoting information sharing across government agency budget offices and building a "community of practice". • With this collaboration, the budget community can start to identify best practices for all aspects of budget formulation and execution. The BFELoB strives to find solutions that link budget formulation, execution, planning, performance, and financial information.

  50. Overview of BFELoB (cont’d) • The BFELoB taskforce, made up of agency representatives, was formed. • This taskforce meets regularly to identify opportunities for common budgeting solutions as well as automated tools to enhance the agency budget process.

More Related