REPORTING AT THE UNIVERSITY OF CHICAGO AUGUST 20, 2010

Current Reporting Environment 2  Central systems provide reporting using various methods and tools Legacy Financial : E-Ledgers, DW with BO Legacy Student :Daily data files, Crystal, BO pilot against copy of production, DW with BO in progress Legacy HR: E-Ledgers, IFocus, DW with BO SunGard Alumni:Extensive BO against production copy Research Administration: DW with BO in progress Concur Expense Mgt:Cognos Etc..  Many other central systems with standard reports, tool, Access dbs, etc.  Numerous shadow systems in departments and schools  Feeds, and more feeds

Impacts of Reporting Environment 3  A lot of reporting delivered, supporting many hundreds of users  Multiple entry points, processes, and versions of truth  Challenging to integrate data from multiple sources - users are on their own  Duplication of effort across IT Services, business offices, schools, and departments  Difficult to respond sophisticated user requests, on the rise with a new senior leadership group that demands data to support decisions and continued growth  Complex data governance issues

Goal: Integrated Reporting Strategy  Common way to implement reporting solutions from a variety of information systems to a variety of audiences  Implement through consistent development and delivery tools, and access policies and procedures  Support data custodians and user audiences – those who manage and use data to support various purposes and perspectives 4

Who is BIS? 5 Business Information Services (BIS) is part of central IT Services, with responsibility to move toward an integrated reporting strategy Lead Architect PM s 3 Senior BI Analysts 3 BI Analysts 3 Senior DW/ETL Developers 1 DW/ETL Developer 1 ETL/BI Developer 1 BI Administrator DW/BI strategy, planning, architecture, design, build, implementation, training, support

What does BIS do? 6  Design, build, and maintain DW and ETL architectures (Oracle, ESP, 24x7)  Design, build and administer BI architectures (5 BO deployments)  Model University data for reporting (‘stars’ or hybrid for financial, payroll, HR; student and research in progress)  Design, build, and maintain extract/transform/load ETL processes (OWB)  Design, build, and support custom BI applications (BO XIR2 and XIR3, WebI, DeskI and InfoView)  Add context to the data (documentation in application and external)  Design, build, and administer row, column, and user group security (Oracle VPD, BO folders, custom web apps)  Develop and maintain feeds to other enterprise systems  Train users (casual through ad-hoc, data training)  Technical and user production support  Facilitate data stewardship coordination, policy, and process

Current Steps  Consolidate BO architecture Upgrade to XIR3 Move away from DeskI Consolidate all DW-based BO implementation on single clustered environment  Deliver new subject areas Student Research Administration  Implement best practice DW and BI development across projects High availability, high performance ETL processes Universe and BO design and naming standards, report look and feel 7

Current Steps  Build dimensional data models Facilitate enterprise data warehouse  Template current ‘tiered’ training program for new subject areas Support casual through advanced users  Evaluate reporting needs early in process for new administrative systems 8

Challenges  Multiple parallel paths needed to move toward integrated strategy (architecture, new subject areas, data integration, stewardship)  Investment and time for build and deploying DW/BI applications  ‘Conforming’ like data difficult in decentralized business process environment 9

Overcoming Challenges  Work closely with application and data stewards to understand and resolve complex data issues  Engage key users and deliver targeted chunks of reporting to support critical analytic needs  Investigate more agile development methods  Leverage appropriate BI functionality support different users types 10

Questions 11 Contact Name Phone Suneetha