university of san diego
play

University of San Diego California Higher Education User Group - PowerPoint PPT Presentation

University of San Diego California Higher Education User Group Presentation Nov-2014 ITS Meeting Agenda Business Intelligence and Operational Analytics Project Team Operational Analytics Architectural Overview Operational


  1. University of San Diego • California Higher Education • User Group Presentation • Nov-2014 ITS

  2. Meeting Agenda • Business Intelligence and Operational Analytics Project Team • Operational Analytics Architectural Overview • Operational Analytics Discussion • Security / Data Custodians • Project Lifecycle • Part II – Technical Presentation • Q&A

  3. BI & Operational Analytics Project Team: • Avi Badwal – Senior Director ERP Technologies • Satish Attili – Business Intelligence and Analytics Team Lead Users • Kris Haskell – Senior Business Intelligence Analyst • ERPT Business Matter Experts: Managers and Technical Resources Functional • Designated USD Functional and/or Academic Area Business Matter Experts • The individual(s) that will engage the operational analytics Technical to make actionable decisions and observations within their areas of responsibility

  4. Operational Analytic Architecture Overview Cognos Tools and Technologies Presentation Layer Third Party Metadata ODS + Report Views EDW + Star Schemas Layer Data Integration + Oracle Banner SIS Data Third Party Oracle ODS >EDW + Layer Transactional + Transactional + Data Data Source Data Extraction Data Transformation Presentation

  5. Operational Analytic Architecture Overview (continued): The EDW project implementation team (functional areas and ITS/EDW team) defined snapshot star ‘Events’ – events define and capture data at predetermined points in time during an academic period and academic year (e.g. 10 Weeks Before Class, Census, Last Day of Class, Final Period). Ellucian architected EDW using ‘star schemas’, which surround a ‘fact table’ containing interesting, often numeric data (e.g. # enrolled students) specific to one analytic area with associated referential ‘dimension tables’ that provide context to the facts (e.g. By College, Department, Program, Course) The Star schemas design, in conjunction with the ‘time dimension’, provide the opportunity to look across ‘like events’ (i.e. same relative point in time each academic period and year) to analyze trends.

  6. Architecture Overview: EDW Student Stars • EDW Academic Program Course Dimensions : Time; Academic Program; Concentration; Course: Demographic; Enrollment Status; Instructor; Major; Minor; registration Facts : Student ID; Course Reference Number; Curriculum Priority Number; Age; Age Range; Major (Group, Order, Count, Description; Minor (Group Order, Count, Description); Concentration (Group, Order, Count, Descriptions, Major Group, Order, Count, Description) • EDW Course Registration Dimensions : Time; Academic Study; Course: Demographic; Enrollment Status; Instructor; Registration, Student Facts : Student ID; Course Reference Number; Age; Age Range; Credits Generated; Credits Attempted; Credits Earned; GPA Credits; Quality Points; Credits Passed • EDW Enrollment Dimensions : Time; Academic Study; Demographic; Enrollment Status; Student Facts : Student ID; Age; Age Range; Total Credits Generated; Total Billing; Total Contact Hours; FTE Numerator; FTE Denominator; Tuition Charges; Financial Aid Amount; Total CEU, Total CEU Billing; Academic Period (Credits Attempted; Credits Earned, GPA credits; Quality Credits; Credits Passed); Student Level (Credits Attempted; Credits Earned, GPA credits; Quality Credits; Credits Passed); Institution Level (Credits Attempted; Credits Earned, GPA credits; Quality Credits; Credits Passed • EDW Graduation Completion Dimensions : Time; Academic Study; Demographic; Graduation; Student Facts : Student ID; Outcome Number, Age; Age Range; Active Academic Periods; Credits Attempted; Credits Earned; GPA Credits; Quality Points; Credits Passed)

  7. Operational Analytics Security and Data Custodians: Student Financial • Cognos Groups and Roles are being defined to restrict access to folders, Services EDW Cognos ‘packages’, and underlying reports and dashboard components. Financial Aid • Report Studio analytic applications are developed specifically for each college or school (or operational area) and contain embedded ‘parameter filters’ that restrict the queries to analysis appropriate to that Banner location. • In a number of cases, Report Studio analytics applications will be developed specifically for the recipient of the analysis – this could be for Registrar a department chair that will only have access to his/her dashboard specifically developed for that department. • Cognos also supports ‘session parameters’ where Cognos user definable session attributes determine, preset, and restrict drop-down access to Admissions applicable parameters. • Data Custodian ‘authorization’ is still required before an Operational Analytic project can be launched – the data custodian responsible for an ODS package will be responsible for the corresponding EDW package. • Operational Analysis is NOT ‘Official IRP Data’ and should not be released to external sources. EDW is sourced directly from ODS and is not cleansed data.

  8. Operational Analytics Project Lifecycle: • Kick-off meeting to review presentation and EDW demo • Requirement Gathering to identify and discuss: - Key Performance Indicators (KPI) - Analytic Requirements/Business Use-Cases - Determine Best-Candidate EDW Baseline Star(s) - Identify Project Team Members • Development Phases : Report Studio analytics; Workspaces and Dashboards – additional meetings / conversations to refine scope and resolve outstanding questions/issues • Review and Hand-Off Analytics to recipient for user testing: support user testing, modifications and/or enhancements of deliverables • Incremental Development: iterate between development, hand-off, and refinement phases until requirements have been met • Embrace ‘Agile BI’ approach and ‘initial’ Data Governance, standardizing/defining titles, sub-titles, KPIs, labels, etc.

  9. Functional Demo Below appears on the ‘landing’ page of the College of Arts and Sciences EDW Academic Program Course Subject Analysis and states the objectives of our initial proof-of-concepts:

  10. University of San Diego Part II – Technical Review – EDW and IBM Cognos Analytics: Report Studio>Workspace>Dashboard

  11. IBM Cognos Report Studio Analytics • Initially began development of Report Studio analytics with all charts and graphs envisioned/mined (50+?) from a single EDW (relational) Star - Best Practice now: Design Report Studio reports with limited/scoped KPI or KPI category to reduce impact on any changes to underlying analytics on workspace updates (Admission Applications Completed, Gender, Ethnicity = 18 charts); scalability; and maintain focus • ‘Prompt Page’ with ‘named parameters’ provide ‘Listen for Widget Events’ (Workspace) capabilities for a flexible and navigable analytic user experience - Design consideration: can develop a consolidated prompt page in one area of analysis containing ‘named’ prompts referenced by charts in other Report Studio analytics – this can provide ‘drill - thru’ capabilities (e.g. drill into ‘Age Range’; ‘GPA range’) • Charts Titles, Sub-Titles and Footers: use reference data item values, calculated columns or parameter values to provide an opportunity for reusing underlying analytics in a different area (i.e. department)

  12. IBM Cognos Report Studio Analytics • Initially developed analytics exploring relative size or proportion using Pie Charts - Best Practice now:100% Stacked Column charts • A standard practice for us is to provide KPIs by both academic year and academic period within academic year (2 sets of same analysis) – as is the case in all aggregation strategies, counts differ because unique student PIDM’s appear once per year, but more than once a year in each academic period the student is enrolled • Assign meaningful names to each chart/graph for easy identification when constructing the Workspace (e.g. CmplAppEthnAcadYrCht)

  13. IBM Cognos Workspace • Ask IBM: Workspace is a report consumption environment that provides an integrated Business Intelligence experience for business users • Global Area now available for sharing prompt page parameters across one or more Workspace pages (i.e. sub-tabs). Can toggle between expand (i.e. new prompt selections) and collapse (display full page) • IBM Cognos Content and Toolbox pane (expand/collapse) for selection of components available for inclusion on the Workspace (e.g. Report Studio, Analysis Studio) – drag and drop on Workspace page • ‘New Tab’ is a new feature introduced in Cognos 10.2.1 used to create additional ‘pages’ to better organize/segment analysis – can be reordered – components share ‘named parameters’ in Global Area • ‘Share Workspace’ allows you to set features and copy the URL link to provide to other users (we’ll use this in another kind of ‘page’ when building our demo dashboard)

Recommend


More recommend