1. EFS Reporting Strategy Financial Data Warehouse Initiative GMUN – May 2010

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

3. Strategic Central/Dept All tables/Raw data Broader focus Across systems Tier 2 Dept /Unit focus Dept Head Financial managers Tier 1 Accounting Staff Faculty Business Intelligence Tool Investigation Few Users Tier 3 Strategic Central/ College/Dept TodayNeeds 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 Pre-populated views/filters More ability Custom queries Custom reports Ad Hoc Many Users Point & Click Defined & Delivered Data & Reports N-vision Query Manager 21 standard reports 8 non spon UMR 13 spons UMR&PS PS delivered/custom Inquiries, Queries, Reports Principle/process/ policy guidelines governing access Define role Query Manager Training Business Intelligence Tool Investigation Intelligible query tool Clear communication & training Improved access to data Replacement for UM Reports on web (UMR) In Process Enhancements Additional Reports Training Target Audience Financial Reporting Environment BI Publisher Tool Investigation 2

4. Charge Financial 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 3

5. Methodology Financial 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 4

6. 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. 5

7. 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. 6

8. 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 7

9. 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 8

10. 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 9

11. High Level Timeline TodayFY12FY13FY14FY15 POTENTIAL TIMEFRAME 10

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

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