Business Intelligence at Penn State. June 2011

Transcription

1 Business Intelligence at Penn State June 2011

2 Agenda Introduction and Status Update. Who is Using itwo and how they are using it. Conclusion

3 Introduction and Status Update

4 Business Intelligence Early History Initiative Approved by Executive Sponsors Early 2005 Over 80 Interviews with representatives from both academic and administrative units. Proposed Business Intelligence Strategy for Penn State finalized and published. Obtained Executive Approval to move forward with proposed strategy. Issued RFP for an Information Access and Analysis Solution Commenced Contract with Oracle for Oracle Business Intelligence Enterprise Edition Tool Suite June 2005 through May 2006 November 2007 November 2007 July 2008 June 2009

5 Oracle Business Intelligence Web based, no client software is needed. Provides users with ad hoc query and analysis capability. Users do not need to understand physical data, joins are predefined, and each attribute has a definition. Availability of dashboards, which provide users with an interactive collection of analytic content with a variety of visualizations. Analysis objects can be shared with other users.

6 What has happened since Deployed Oracle Business Intelligence under the name of Institutional Insight System (itwo). Piloted Access and Security Representative Dashboards. Worked with Registrars Office and a Committee of Student Information users to create the Registrars Student Enrollment Answers Model and a set of representative Dashboards. Subject area is currently available to Registrars, Financial Officers as well as to Departments Heads, Academic Management, Chancellors, and Deans. Worked with Controllers Office and a Committee of Financial Information users to create the Financial Information Pilot. Currently available in production to the pilot user group. Deployed Basic and Advanced training classes.

7 What are the steps for an itwo project Work with data stewards, process owners and information users to create data model representative of Subject Area Business processes. Identify required new Data Warehouse table structures or changes to existing structures. Create new Data Warehouse processes and/or modify existing processes. Create Metadata model. Test and validate model. Ensure integration/integrity of source data records.

8 Who is Using itwo and how they are using it.

9 itwo Queries per Month 3,000 2,250 1,500 Avg Daily Query Count

10 itwo Monthly Unique Users Max # Daily Users Avg # Daily Users

11 Penny Carlson Director, Academic Services and Records Office of the Vice President for Commonwealth Campuses Introduction Current usage example. Future usage.

12

13

14

15 Mary Lou D'Allegro Senior Director Office of Planning, Research and Assessment Penn State Berks Introduction Current usage example. Future usage.

16

17

18

19 Carol S. Findley, Information Technology Director Office of Registrars From Enrollment Reporting System (ERS) and EIS to itwo Comparison between ERS and itwo Patti Cochrane, Financial Officer Office of the Vice President for Commonwealth Campuses Using Dashboards to track Enrollments Using Dashboards to answer questions.

20

21

22

23

24 Mark Weaver, Assistant Director University Budget Office How the Budget Offices plans to use itwo for Official Reporting. Ross Brode, Assistant Registrar Security and Network Support Office of Registrars Using the Access and Security Representative Dashboard.

25

26

27 Conclusion

28 What is new with itwo Available via the web. Availability of pre-defined online, interactive reports. Accessible to non-technical users. Significantly easier to use than the Data Warehouse or the Enterprise Information System. For functional groups like Deans, Chancellors, Registrars, and others access is granted automatically ensuring that everybody that is supposed to have access has access. Strong emphasis on data consistency on the creation of the back-end systems. Extensive documentation available. Focus on the University needs, not the needs of a specific office or unit.

29 What is coming next from the BI team Work with Pilot group to define and create a set of representative dashboards for Financial Information. Make Subject Area and Dashboards available to a larger group of users by Q Deploy Financial Information training classes. Work in conjunction with the Registrars Office to retire the ERS system and the Registrars EIS Enrollment cubes. Completion planned for Q Model and deploy next iteration of student life-cycle information with the initial focus on admissions information. Pilot planned for Q Continue to migrate current EIS Models. Next focus area will potentially be Human Resources. Pilot tentatively planned for Q Upgrade to new version of Oracle product suite to make expanded functionality available to end-users. Tentatively planned for Q

30 What is coming next from other teams With the support of the BI team, the Budget Office is currently in the process of migrating the Official Student Enrollment information to itwo. They will, subsequently, initiate report and dashboard development. The Outreach Marketing department is currently in the process of developing a Subject Area model that is customized to their specific needs.

31 Risks and Challenges Current culture of distributed data ownership can create barriers to the creation of an integrated and view of Penn State s data. The same culture can impose limitations on the solution by asking for non-integrated, customized solutions for each stewardship area. Availability and retention of skilled Business Intelligence development and consulting staff. Even though they work well for operational purposes, Penn State s information systems can be challenging to use when it comes to data analysis and reporting purposes.

32 Where to find more Information itwo Information Site Business Intelligence Strategy Site itwo