TBR ODS EDW Planning 2007

1,460 views

Published on

Presentation used to gain consensus on the adpotion of a data warehousing solution for the TBR.

Published in: Technology, Business
  • Be the first to comment

TBR ODS EDW Planning 2007

  1. 1. Tennessee Board of Regents ODS/EDW Planning Presented by Thomas Danford Fall 2007
  2. 2. Information Requirements of the TBR Institutional Research Administrative and Academic Departments A single, trusted source of i l d f institutional data Easy-to-understand data layout coupled with industry-based, Accurate data based on easy-to-use reporting tools that consistently applied institutional allow end-users to satisfy their business rules b i l own requests CIO/IT audience Executive Level Robust Information Access architecture based on The same information “visible” to commercially supported tools all layers of the institution An abstracted data model built Less time arguing over data; more with and for higher education time using information to make better and timely decisions Supports choice of reporting tools to meet varied needs and budgets 2
  3. 3. Reporting out of Banner can be Complex EXAMPLE: The simple report below for 5 pieces of information requires accessing data fields from 4 Banner tables: ID Name Address Phone Age _______________________________________________________________ 123-43-4564 Buler, Brian 1464 West Street West Chester PA (453)657-5768 43 324-64-3445 Carol, Bob 84 South Street Philadelphia PA (728)495-4535 34 848-39-4848 Crain, Joan 23 Brandywine Kenneth PA 23 834-56-3443 Kaachen, Perry 3444 Broadview Allentown PA (435)309-5445 54 ….. …. … .. . 3
  4. 4. Banner Normalizes Data (3rd Normal Form) so that it exists only in one location The tables for the example report: SPRIDEN SPBPERS SPRADDR SPRTELE 4
  5. 5. SQL is the programming language used to manage data in Banner The SQL code for the example report: SELECT SPRIDEN_ID,SPRIDEN_NAME,SPRADDR_STREET_LINE1,SPRADDR_CITY, SPRADDR_STAT_CODE,SPRADDR_ZIPC_CODE, SPRTELE_PHONE_AREA_CODE||’-’||SPRTELE_PHONE_NUMBER, FUNC(AGE(SPBPERS_BIRTH_DATE)) FROM SRPIDEN,A.SPRADDR,B.SPRTELE,SPBPERS WHERE SPRIDEN_CHANGE_IND IS NULL AND SPRIDEN_PIDM = SPBPERS_PIDM (+) AND SPBPERS_PIDM = SPRADDR_PIDM (+) AND SYSDATE BETWEEN A.SPRADDR_FROM_DATE (+) AND A.SPRADDR_END_DATE (+) AND A.SPRADDR_ADDR_CODE (+) = FUNC(ADDRHICR(SPRIDEN_PIDM,”OF”) AND A.SPRADDR_ASTA_CODE (+) = “A” AND A.SPRADDR_PIDM = B.SPRTELE_PIDM (+) AND A.SPRADDR_ADDR_CODE = B.SPRTELE_ADDR_CODE (+) AND B.SPRTELE_SEQ_NO (+) = (SELECT MAX( C.SPRTELE_SEQ_NO) FROM C.SPRTELE WHERE C.SPRTELE_PIDM = B.SPRTELE_PIDM AND C.SPRTELE_ADDR_CODE = C SPRTELE ADDR CODE B.SPRTELE_ADDR_CODE)…. …ORDER BY SPRIDEN_NAME; 5
  6. 6. Approach Under Plus - IT Department Made Reports Based on Specifications Provided by Functional Users … Frustrating developing specifications Inefficient iterative process Very time consuming Multiple functional users competing for limited IT resources Functional dependency on IT developed 6
  7. 7. Information Access Maturity Model SunGard Plus Reporting Created by Self- Self-Service Analytical Institutional IT Staff Reporting R ti Reporting R ti Performance P f Ad- Ad-Hoc Historical Trends Management Time Forecasting Process Improvement Data Mining Dashboard/Scorecard Analytical Applications Custom Reports Baseline Reports Level 1 Level 2 Level 3 Level 4 Level 5 Not Available 7
  8. 8. ODS/EDW & Banner Approach Instead of continually spending IT staff time and budget on developing and programming reports for functional users, we will develop the infrastructure that simplifies how information is accessed. accessed The infrastructure must support the enterprise and provide both a common framework and methodology for solving Information access problems. Simplifying the access gives both IT and functional users the information they need, when they need it, with less of an effort. 8
  9. 9. Information Access Maturity Model SunGard SunGard SunGard Operational Enterprise Banner Data St D t Store Data D t Warehouse Institutional Performance Analytical Management •Process Improvement Reporting •Dashboard/Scorecard Time •Historical Trends •Analytical Applications •Forecasting Self- Self-Service •Data Miningg Reporting SunGard S G d •Ad-Hoc Ad- Performance Custom Management Reports Solutions Baseline Reports Level 1 Level 2 Level 3 Level 4 Level 5 Institution Adoption 9
  10. 10. Information Access Maturity Model SunGard SunGard SunGard SunGard Banner Operational Enterprise Performance Data St D t Store Data D t Management M t Other Warehouse Solutions Systems KPIs Banner ETL ODS ETL EDW Alerts SELF- SELF-SRVC BANNER CUSTOM REPORTS OLAP Oracle Discoverer Scorecards QUERIES REPORTS Cognos Impromptu g p p CUBES Dashboards &REPORTS Others (any ODBC) Cognos Powerplay Others Level 1 Level 2 Level 3 Level 4 Level 5 10
  11. 11. 11
  12. 12. Data Modeling Strategy Model specifically designed for end-user reporting Applicable TBR (enterprise) wide Simplified & standardized data structures User-friendly table and field names Designed from a reporting perspective g p gp p Indexed and optimized for reporting Flexible enough for individual campus requirements Consistency between Banner product releases 12
  13. 13. Key Roles in ODS/EDW (Senior) Data Architect(s) – An IT management role that is responsible for the data modeling, ETL processing, and administration of the ODS/EDW. Experience and Responsibilities: p Designs data dictionaries & data warehouses Enterprise application and analytics integration Metadata registry Oracle RDBMS and Structured Query Language (SQL) XML, including schema definitions and transformations ODBC/JDBC linkages & reporting tools Business & Systems Analyst(s) – An internal consultancy role that identifies options for improving business systems and bridges the information needs of the business with the use of the ODS/EDW. Experience and Responsibilities: Gathers and defines business requirements Analyzes, maps, and documents processes (current state/future state) Identifies, collects, and analyzes data requirements (forecasting, trend analysis, etc.) Contribute to the design of the ODS/EDW from a business needs point of view Creates required reports, KPI’s, alerts, scorecards, dashboards, etc. C t i d t KPI’ l t d d hb d t ODBC/JDBC reporting tools 13
  14. 14. Data Model Approach & Responsibilities Model specifically designed for On Line Analytical Processing (OLAP) reporting Enterprise Wide Star Schemas Designed from a departmental perspective Multidimensional business analysis Complex calculations Trend analysis Sophisticated data modeling Documenting the ODS/EDW (ERDs Data Dictionaries (ERDs, Dictionaries, Flow Charts, Metadata, etc.) 14
  15. 15. Example: The Enrollment Star 15
  16. 16. ETL Processing Responsibilities Commercial ETL tool Oracle Warehouse Builder (OWB) Improved customization Improved extensibility User defined time slices Incremental Refresh Only move what has changed Feeds from Campuses to TBR ODS/EDW ODS/EDW Campuses Custom Warehouses (MTSU & UoM) 16
  17. 17. ETL – Oracle Warehouse Builder 17
  18. 18. Administration Responsibilities Administration tool for execution and monitoring of ETL processes Web-based Job S Submission/Scheduling and Logging /S Snap-Shots Transformation Setup and Maintenance Data cleansing Security – (FGA) Meta Data Repository 18
  19. 19. Data Warehouse Implementation Roadmap Federal, State, THEC Business Discovery Project Requirements Requirements & Analysis Scoping Gathering Business Analysis Project & Infrastructure Planning DB Architecture Extraction Transform Load Data Structure and Implementation Management & Testing DB Design Reporting & R ti Analytics Architecture Reporting and Analytics Development Reporting & Analytics Design Deployment & Implementation Testing (KPIs, Dashboards, Support Alerts, Etc.) 19
  20. 20. Discussion … Q&A Di i Special thanks to SunGard HE who provided content for this presentation. … 20

×