1 / 13

EFS Reporting Strategy Financial Data Warehouse Initiative GMUN – May 2010

EFS Reporting Strategy Financial Data Warehouse Initiative GMUN – May 2010. 1. Agenda. Overall reporting strategy Charge related to EFS data warehouse Methodology Guiding principles Recommendations Next steps. Financial Reporting Environment . 2. Target Audience. Today. In Process.

hector
Download Presentation

EFS Reporting Strategy Financial Data Warehouse Initiative GMUN – May 2010

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. EFS Reporting StrategyFinancial Data Warehouse InitiativeGMUN – May 2010

  2. 1 Agenda • Overall reporting strategy • Charge related to EFS data warehouse • Methodology • Guiding principles • Recommendations • Next steps

  3. Financial Reporting Environment 2 Target Audience Today In Process Needs • Strategic • Central/Dept • Access to certain tables in data warehouse with a Functional ID used to create own views in their tool/system • Access to all tables in rpt instance to pull into tool of choice to use data • Business Intelligence Tool Investigation • Principle/process/policy guidelines governing access • Define role Few Users • Tier 3 • Strategic • Central/ • College/Dept • All tables/Raw data • Broader focus • Across systems • Tier 2 • Dept /Unit focus • Dept Head • Financial managers • N-vision • Query Manager • Query Manager Training • Business Intelligence Tool Investigation • Intelligible query tool • Clear communication & training • Improved access to data • Pre-populated views/filters • More ability • Custom queries • Custom reports • Ad Hoc • Tier 1 • Accounting Staff • Faculty • Many Users • Point & Click • Defined & Delivered Data & Reports • 21 standard reports • 8 non spon UMR • 13 spons UMR&PS • PS delivered/custom • Inquiries, Queries, • Reports • Enhancements • Additional Reports • Training • Replacement for UM Reports on web (UMR) • BI Publisher Tool Investigation

  4. 3 ChargeFinancial Data Warehouse Initiative • Financial users require both broad and specific data & reports from the EFS modules which we support as Business Process Owners (BPOs) • We were charged with the task of identifying a long term strategy related to financial data and reporting, which includes discussion about data warehouses and tools

  5. 4 MethodologyFinancial Data Warehouse Initiative • Broad target audience • Deans, faculty, central BPOs, dept. heads, data analysts, module support/helpline, FSUN, GMUNAC/CAAC, key reporting user group • Over 100 total participants • Group discussion sessions & written input • Business process focused questionnaire • Requirement review & summarization • Six prioritized summary requirements • Transactional detail data • Flexibility of reporting parameters & summarization/roll-up • Reporting across Peoplesoft and non-Peoplesoft systems • Functional usability • Simplified data structure • Data maintenance & documentation practices

  6. 5 Guiding Principles Financial Data Warehouse Initiative • Provide operating units with an infrastructure that facilitates the gathering, analyzing, and reporting of data for operational and strategic decision making purposes. • User satisfaction is a priority as requirements are gathered, decisions are made, and solutions are implemented. • OIT and the University’s financial management are partners in the provision of technological solutions to identified business requirements. • Solutions should facilitate an enterprise wide reporting strategy.

  7. 6 Guiding Principles Financial Data Warehouse Initiative • Solutions should leverage previous University investments in hardware, software, and expertise. • Solutions purchased from, and maintained by, vendors should be favored over solutions developed and maintained by University staff. • A full lifecycle funding plan should be developed and approved prior to the implementation of a solution. • Priority given to requirements associated with Tier 2 target audience. • Short term solutions may be necessary as a bridge to different longer term solutions.

  8. 7 Recommendations • Short term • Improve query and report performance in EFS Reporting Instance • Improve access to the data by providing query capability via the Web Query tool used with the existing data warehouse • Provide Meta Data to assist users in reporting efforts

  9. 8 Recommendations • Long term – Data Source • Implement the PeopleSoft Financials EPM data warehouse • Leverage previous University investment in software and hardware • Vendor supported and enhanced solution • Implementation effort reduced due to delivered architecture and data base structure • Could also be implemented in the future for the HR/Payroll and Campus

  10. 9 Recommendations • Long term – Reporting Tool • Evaluate and document the capability of the Oracle BI tool to meet the functional requirements • Custom reporting tools – UM reports, Web Query Tool – replaced with BI tool

  11. 10 High Level Timeline Today FY12 FY13 FY14 FY15 POTENTIAL TIMEFRAME

  12. 11 Next StepsFinancial Data Warehouse Initiative Obtain Approval of Long Term Recommendations Implement Short Term Recommendations Develop Long Term Implementation Plan Partner with units

  13. 12 Julie Tonneson tonne001@umn.edu Sue Paulson spaul@umn.edu

More Related