1. Dana C. Voss Manager, Decision Support Services, UIS University Information Technology Services INDIANA UNIVERSITY May 2003 Copyright Dana C. Voss, 2003. This work is the intellectual property of the author. Permission is granted for this material to be shared for non-commercial, educational purposes, provided that this copyright statement appears on the reproduced materials and notice is given that the copying is by permission of the author. To disseminate otherwise or to republish requires written permission from the author.

2. Technical Implementation of Indiana University’s enterprise web reporting environment & demo History Accomplishments Challenges Business Perspective How we did it Lessons Learned

3. Technical Implementation of Indiana University’s enterprise web reporting environment & demo History Accomplishments Challenges Business Perspective How we did it Lessons Learned

4. Public University 8 Campuses 10,565 Appointed Staff members 4,745 Faculty members 97,000 enrolled students in Fall 2001-2002

5. PeopleSoft Student & HR Financial Information Systems Library Electronic Records Management TimeKeeping Maintenance Management System

6. What do All These Applications Have in Common????

7. 20 years of mainframe reporting: Information Center in Focus 1995-2000: Financial Data in Sybase 2000: moved to Oracle Today: Student Admissions (PeopleSoft) Human Resources (PeopleSoft) Library, Financial Data, etc. Upcoming (2003-2004): PeopleSoft Student Financials, Student Records, Financial Aid, Academic Advising 500GB 1000+ data structures 3-5 TB

8. 1,100 Users (Consumers ) 100 programmers (Providers) What was wrong: too confusing Requires Focus programming skills to write reports Users want one place to go to get data & reports Users don’t want to choose their own tools Departments don’t typically have resources to build their own reporting applications

9. Data Warehouse Infrastructure Reporting Environment

10. 20 years of mainframe reporting: Information Center in Focus 1995-2000: Financial Data in Sybase 2000: moved to Oracle & AIX 2002: purchased ETL tool (Informatica) Today: Student Admissions (PeopleSoft) Human Resources (PeopleSoft) Library, Financial Data, etc. Upcoming (2003-2004): PeopleSoft Student Financials, Student Records, Financial Aid, Academic Advising 500GB 1000+ data structures 3-5 TB

11. Simple application interfaces One place to go to get data & reports Don’t want to choose their own tools Departments don’t typically have resources to build their own reporting applications

12. Ad-hoc Inquiries Dept-al Reporting (Crystal, MS/Access) Complex, Operational Reporting (SQR) Analysis Analyze business within and across departments Analysts, Dept. Heads, Decision Makers Ad-hoc Query Specific or one-time queries/reports Anyone Designed by Brian D. Voss Managed Reporting (IUIE) Reports to support daily business/operational needs Functional Support Staff

13. Indiana University Information Environment https://onestart.iu.edu/iuie Web based reporting application Provides point and click interface for functional users Delivery of Enterprise-Wide Operational Data and Reports User interface for the Data Warehouse In production since November 2000 Work on enhancements continues today Developed in Uniface & Perl CGI initially Conversion to J2EE completed in April, 2003

14. 3500 Users – requests for new accounts come in daily 1300+ Report Objects (RO) as of May 2003 750+ requests for ROs per day 325+ users log in a day Supports: Object & Row-level security (at the database level) Scheduling

16. We believe IUIE satisfies 70-80% of the end–user needs for reporting However, the reporting tool, SQR requires programming skills, significant learning curve Handful of programmers write reports and publish them in IUIE Analysis needs are not met Ad-hoc reporting needs are not met Power Users use Crystal Reports, Access, Excel, and other tools

17. Business Intelligenc e Tool Ad-hoc Inquiries Dept-al Reporting (Crystal, MS/Access) Complex, Operational Reporting (SQR) Analysis Analyze business within and across departments Analysts, Dept. Heads, Decision Makers Ad-hoc Query Specific or one-time queries/reports Anyone Designed by Brian D. Voss Managed Reporting (IUIE) Reports to support daily business/operational needs Functional Support Staff

18. Easier to learn than SQR – doesn’t necessarily require programming skills Easier to build reports Can augment or replace SQR for building enterprise wide reports Analysis made easy Dashboards for the decision makers Centrally supported Ad-hoc reporting tool

19. Technical Implementation of Indiana University’s enterprise web reporting environment & demo History Accomplishments Challenges Business Perspective How we did it Lessons Learned

20. Business/Functional users are oftentimes too busy working on the ERP implementation to turn their attention to reporting specifications Day 1 – Users want access to the Data and they want the data and reports to be PERFECT! In some cases many new requirements or requests for changes to the reporting environment come in AFTER the implementation

21. Implementation date: 1995 FMS developers worked and continue to work very closely with core users Financial Data Retrieval System (FDRS) https://fdrs.fms.indiana.edu/fdrs/ converted to IUIE 445 ROs, approx. 2500 Users

22. Implementation date: Nov. 2000 (Phase 1) Oct. 2001 Row-Level security (Phase 2) Jan. 2000 – inventory of existing Focus reports Several meetings with functional users Data structure creation - Central IT team at UITS 95% of reports created by UITS 1 week before go-live date – training in IUIE content Significant paradigm switch for the end users IE Admissions User Groups formed in early 2003 456 ROs, approx. 1000 users

23. Implementation date: December 2002 Sept. 2001 – inventory of existing Focus reports Several meetings with functional users from main offices Data structure creation - Central IT team at UITS 95% of reports created by Functional Users Limited training in IUIE content (Payroll) End users more mature (overlap with Financial Data) Today: Payroll – less involved in the implementation phase, actively writing reports today Academic – very involved in the implementation HR & Benefits – less involved, but doing ok 617 ROs, approx. 600 users (only Central Offices)

24. Implementation date: January 2005 Committees: IUIE Implementation Team SIS Steering Committee SIS Executive Committee Using PeopleSoft RDS running on Informatica Inventory finalized LegacyReports New DW tbl’s New Incrementals Frozen FilesTotal SF455225105244484 SR + AA4661042663195388 FA461175105190380 Total138250446736291252

25. Technical Data Warehouse ETL Tool is key Data model – depends on data warehouse size, reporting requirements, hardware resources Reporting Solution Build vs. Buy – depends on the problem addressed, the level of skill within institution, and the availability of packaged solutions Business End User involvement is key Identify and understand the data elements that are needed for reporting Identify Report Writers Provide adequate training to the Report Writers Metadata is important! Training in the data content is essential

26. INDIANA UNIVERSITY Dana C. Voss dvoss@indiana.edu