Business Intelligence at the University of Minnesota Defining the need and the solution for a comprehensive decision support system for the University of Minnesota Joe Sullivan Senior Manager Office of Information Technology Financial Pilot Kickoff Wednesday, September 7, 2011

Purpose and Objectives Address well documented demand for: –Improved data quality/documentation –Improved data accessibility –Improved analytic capacity –Support for unique needs of individual units

Focus Shared data – a common home for institutional and unit data Shared understanding – consistent data definitions and usage Shared tools – a common suite of reporting tools for central, unit, or blended data Shared development – units can develop reports/analyses together, without waiting for central resources to be identified and assigned

Key Elements People and Processes Data governance – common definitions and consistent practices Analytics Collaborative - forum for collaboration, spreading innovation and insight Training and development – tools, analysis, and process improvement Tools and Technology Enterprise Data Warehouse –EPM (Peoplesoft) –Non-Peoplesoft UM Analytics - Oracle Business Intelligence Enterprise Edition –Dashboards –Analytics –BI Publisher

The Pilot First application of the new toolset – EPM and UM Analytics Focus on identifying, designing and delivering financial content for principal investigators and financial administrators to support their decision making. Opportunity to identify critical issues in data governance, and data architecture

Timeline Sep – Nov 2011Financial Pilot. Sep – Dec 2011 Implementation of production environment. Jan 2012 Rollout and training, establishment of governance and collaboration groups. Post Jan 2012 Expansion of content and distributed development.