• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
TBR Common Data Repository ITS13
 

TBR Common Data Repository ITS13

on

  • 299 views

During the June 2010 quarterly meeting of the Tennessee Board of Regents, board members approved an implementation plan recommended by the National Center for Higher Education Management Systems ...

During the June 2010 quarterly meeting of the Tennessee Board of Regents, board members approved an implementation plan recommended by the National Center for Higher Education Management Systems (NCHEMS) that called for the creation of a data warehouse to be used to enhance decision-making at both the system and campus levels. The strategy now referred to as the “Common Data Repository” (CDR) is to create a single authoritative data warehouse where data from institutions will automatically be fed into the CDR from their Banner administrative systems be they hosted or located at the campus. The presentation provided an overview of the project as to its strategic purpose, how the technology will work, and the role that the functional users will play (including governance).

Statistics

Views

Total Views
299
Views on SlideShare
299
Embed Views
0

Actions

Likes
0
Downloads
0
Comments
0

0 Embeds 0

No embeds

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • Must satisfy requirements in Phase 1 Project Concept Select core project team, integrated schedules, costs baselineFreeze project requirements
  • Must satisfy requirements in Phase 1 Project Concept Select core project team, integrated schedules, costs baselineFreeze project requirements

TBR Common Data Repository ITS13 TBR Common Data Repository ITS13 Presentation Transcript

  • Common Data Repository (Data Warehouse) Tennessee IT Symposium 2013 April 22nd 10:25a Thomas Danford Greg Turmel Pamela Clippard
  • TBR Common Data Repository (CDR) Agenda • CDR History & General Overview (Thomas Danford) • Technologies Employed & Mechanics of the CDR (Greg Turmel) • Functional Overview & Governance (Pamela Clippard) Our Phased Approach  Phase1 - Project Concept  Phase 2- Project Design  Phase 3 - Project Development  Phase 4 - Quality Assurance  Phase 5 - Beta  Phase 6 - Release  Phase 7 - General Availability 2
  • CDR History & General Overview • Complete College Tennessee Act of 2010 (CCTA) TCA 49-8-101(c) • The National Center for Higher Education Management Systems (NCHEMS) Report 3
  • NCHEMS Recommendations to TBR (Accepted at June 20th 2010 Board Meeting) 4
  • Basic Objectives • Leverage Existing Investments/Projects Wherever Possible – Open BI Project – ODS/EDW – Argos • Implement as Quickly as Possible 5
  • 6
  • 7
  • CDR UM WSCC VSCC TTU TSU STCC RSCC PSCC NeSCC NaSCC MSCC MTSU JSCC ETSU DSCC CoSCC ClSCC ChSCC APSU Board Office BI Development What’s Common in the CDR? SingleDatabase(Oracle) Multiple Entities (MEP) 8
  • 9
  • 10
  • 11
  • 12
  • TBR Common Data Repository 13 Phase 1 - Project Concept Phase 1 - Project Concept Where are we? Shortfalls – time to move on – technology is now available to do better  Not timely  Not consistent  Very costly Where do we need to be as a system? What is available from our technology infrastructure What we currently have – what do we need to add Other – and Future system Initiatives  Platforms  Vendors – Software – Hardware
  • TBR Common Data Repository Phase 2 - Project Design Each design point takes advantage of known technology strengths - minimizing modifications to underlying infrastructure 14 [---------------- Identify Core Team Members from the Central Office and Campuses --------- ------- ] TBR Common Data Repository Ellucian Operational Data Store & Enterprise Data Warehouse TBR EDW TBR ODS Each TBR Campus’ Data Loaded into a Pre-Stage Database Using Oracle Golden Gate RSCC WSCC TSU Etc. Each Banner Data Module Transformed Using Ellucian software (Oracle Materialized Views) Accounts Receivable Student Financial Aid Etc. Phase 1 – Project Design
  • TBR Common Data Repository 16 Phase 3 – Project Development Phase 3 - Project Development Information Technology  Integration of the hardware and the software to implement CDR system as designed. Strategy Development (TBR IT, AA and OESI))  Works in all areas of the organization to ensure the project focuses on the user and that the CDR is provides value added to the executive decision makers. Project Manager  Ensures that local and remote technical & development staff understand the their interdependencies, facilitates communication among the departments, and resolves issues surrounding slipping deadlines. Quality Assurance  Responsible for defining, designing, developing, and implementing a test plan. Begins initial documentation. Help Desk  Responsible for designing, defining, developing a detailed plan that articulates how the project will be supported after release.
  • TBR Common Data Repository Phase 3 - Project Development IT integrates project hardware and software; users and work with IT to QA the project building out sample test procedures; testing and user documentation begins 17 [---------------- Identify Core Team Members from the Central Office and Campuses --------- ------- ] TBR Common Data Repository Ellucian Operational Data Store & Enterprise Data Warehouse TBR EDW TBR ODS Each TBR Campus’ Data Loaded into a Pre-Stage Database Using Oracle Golden Gate (February 2012) RSCC WSCC TSU Etc. Each Banner Data Module Transformed Using Oracle Materialized Views (March 2013) Accounts Receivable Student Financial Aid Etc. Phase 3 – Project Development
  • TBR UOM TTU TSU MTSU ETSU APSU 18 TBR Common Data Repository WSCC VSCC SwSCC RSCC PSCC NeSCC NaSCC MSCC JSCC DSCC CoSCC ClSCC ChSCC UOM TTU TSU MTSU ETSU APSU WSCC VSCC SWCC RSCC PSCC NeSCC NaSCC MSCC JSCC DSCC CoSCC ClSCC ChSCC Banner Pre-Stage Extract using Oracle Golden Gate into a single Banner database which has no SSB, no INB, and no other access other than the Ellucian ODS/EDW application for mapping the required Banner tables into the materialized views (and/or any additional Banner tables necessary to complete custom applications. Ellucian ODS/EDW Ellucian ODS/EDW Mappings VPDI is OPEIDVPDI is OPEID The Banner Pre- Stage and the ODS/EDW use FICE code to populate the VPDI code for each record from the campus. The VPDI (FICE) code is used to partition each schools’ data into individual Oracle partitions. TBR UOM TTU TSU MTSU ETSU APSU WSCC VSCC SWCC RSCC PSCC NeSCC NaSCC MSCC JSCC DSCC CoSCC ClSCC ChSCC TBR UOM TTU TSU MTSU ETSU APSU WSCC VSCC SWCC RSCC PSCC NeSCC NaSCC MSCC JSCC DSCC CoSCC ClSCC ChSCC TBR UOM TTU TSU MTSU ETSU APSU WSCC VSCC SWCC RSCC PSCC NeSCC NaSCC MSCC JSCC DSCC CoSCC ClSCC ChSCC Phase 3 – Project Development - Integration of Hardware and Software
  • TBR Common Data Repository TBR UOM TTU TSU MTSU ETSU APSU WSCC VSCC SWCC RSCC PSCC NeSCC NaSCC MSCC JSCC DSCC CoSCC ClSCC ChSCC Ellucian ODS/EDW Mappings EDW Dimension Dimension Dimension Dimension Fact Table TBR Operational Data Store and Enterprise Data warehouse CDR ODS/EDW Phase 3 – Project Development 19
  • TBR Common Data Repository Phase 4 - Quality Assurance 20 Quality Assurance of the Project – IT  Largely IT oriented to encompass physical operating specifications are met. This will include data synchronization, user response times, source system impact at data replication, and that appropriate disaster recovery plans are in place.  Documentation of the technical system is created, and test plans are share with functional users. Quality Assurance of the Project - Functional  PM/IT work with governance teams to identify functional offices who will test the project at their location, recruit help desk for each test site, prepare sign-off procedures and secure release dates for data modules.  PM develops initial release plan using technical and functional QA feedback. Phase 4 – Quality Assurance Sample Test Design and User Documentation
  • RSCC Accounts Receivable Alumni Finance Financial Aid Human Resources Student Baseline Common Data Definitions Tennessee Mods WSCC Accounts Receivable Alumni Finance Financial Aid Human Resources Student Baseline Common Data Definitions Tennessee Mods VSCC Accounts Receivable Alumni Finance Financial Aid Human Resources Student Baseline Common Data Definitions Tennessee Mods Sub-System Load One School at a Time ODS Load Schools as One Integrated Data Store EDW Load Schools as One Integrated Data Warehouse Data Extract Validation Transform and Load Validation Integrated Reports and KPI Validation . . . etc. CDR Validation * *includes security and data discovery validations 21 Phase 4 – Quality Assurance Sample Test Design and User Documentation 21
  • Common Data Repository Campus Load Schedule – Central Office and Campus IT/OIR Load Order Wave #1 Wave #2 Wave #3 Wave #4 Wave #5 February OIR Infrastructure Validation M ay June July August Septem ber Testing Campus & System security, network, capacity and benchmark testing. Initial data loads. TBR DSCC ChSCC STCC TTU CoSCC MSCC NeSCC NSCC ETSU WSCC JSCC PSCC TSU MTSU RSCC ClSCC VSCC APSU UoM Testing Campus & System security, network, capacity and benchmark testing. Initial data loads. Data Verification and Quality Assurance Schedules June July August Septem ber October Testing Campus & System security, network, capacity and benchmark testing. Initial data loads. IT/Functional Offices - Quality Assurance for data validation, common data definitions, etc, TBR DSCC ChSCC STCC TTU CoSCC MSCC NeSCC NSCC ETSU WSCC JSCC PSCC TSU MTSU RSCC ClSCC VSCC APSU UoM IT/Functional Offices - Quality Assurance for data validation, common data definitions, etc, 22 Phase 4 – Quality Assurance Sample Test Design and User Documentation
  • TBR Common Data Repository Phase 5 - Beta Testing 23 Beta Testing  Takes place after the Quality Assurance group agrees that the project, user documentation, help desk procedures, and are functional and meet the design specifications. Beta Sites  The project is sent to a select group of users who have agreed to test the project to confirm that its features work in a campus environment.  The quality Assurance group takes the lead in monitoring the user test process.  IT continues to fix bugs.  If the project will be available to campuses, the CDU is focused on actualizing the Project launch plan Phase 5 – Beta Testing
  • Test Schools Selected • Hosted • Non-Hosted • Community College • University Banner Data Modules • Alumni • Student • Financial Aid • Finance • Receivables • HR & Payroll TBR Common Data Repository Phase 5 – Beta Testing Four Reporting Profiles for Security: 1. Institution 2. Executive Key Performance Metrics 3. Management Aggregated Data 4. Staff Detailed Reporting Common Data Repository – ODS/EDW Shared Library of Dashboards and Reports TBR Central Office Business Intelligence Degree Completion Campus Executive Dashboards 8% 17% 42% 13% 11% 5% 6% Degrees Awarded by College Campus Operational Reporting New Graduates R. Jones, MBA D. Smith, AA, AS A. Neville, MA P. West, BSBA Campus Banner Transaction Campus Banner Transaction 24
  • TBR Common Data Repository Phase 6 – Release 25 IT as Key Member  Provides technical information and support CDR Communications  Interacts with campuses and Central Office TBR IT, AA & OESI  Leads analysis and user focus Project Manager  Communicates & supports the interdependencies Quality Assurance  Responsible for designing test plans Helpdesk  Creates plan for support after release Documentation  Installation, support, interfacing contacts and controls Training  Provides training courses for internal & external staff Phase 6 – Release
  • TBR Common Data Repository Phase 7 – General Availability 26 Helpdesk  Ongoing support to answer questions End-user training  Ongoing training for technical and functional users Scheduled Upgrades/Installs  Software and hardware upgrades and patching Daily IT Application Support  Maintains and repairs software and hardware Ongoing System and Campus Integration  Continued focus groups for future development Phase 7 – General Availability
  • Four Reporting Profiles for Security: 1. Institution 2. Executive Key Performance Metrics 3. Management Aggregated Data 4. Staff Detailed Reporting Common Data Repository – ODS/EDW Shared Library of Dashboards and Reports TBR Central Office Business IntelligenceDegree Completion Campus Executive Dashboards 8% 17% 42% 13% 11% 5% 6% Degrees Awarded by College Campus Operational Reporting New Graduates R. Jones, MBA D. Smith, AA, AS A. Neville, MA P. West, BSBA Campus Banner Transaction Campus Banner Transaction Campus Banner Transaction Campus Banner Transaction TBR Common Data Repository 27 Phase 7 – General Availability
  • 28 TBR Common Data Repository Executive Leadership Dashboards and Scorecards with performance metrics toward established goals and objectives Management Reporting Trend, summaries, operations analytics. front line for implementation of business rules, verification of business processes, complex interdependencies and application integration Staff Reporting Detailed and ad-hoc reports, front line of data quality assurance, verify reporting result set CDR Supports Reporting and Business Intelligence at All Levels of System and Campus Management
  • Why Measure Our Progress in a New Way? Bill Gates Says There Is Something Perverse In College Ratings There is a perverse metric rating system for U.S. colleges, says Bill Gates, the world’s most generous and influential philanthropist. The problem is that it gives credit to schools that attract the best students rather than schools that take poorly prepared students and help them get ready for the next stage. View full story at http://www.forbes.com/sites/luisakroll/2013/01/31/bill-gates-says-there-is- something-perverse-in-college-ratings/ 29 Supporting Student Success “You can’t manage what you can’t measure.” 2025 65,000 42,000 What is our mission? What is our focus? Move from reporting how well we have done? Reporting how well are we doing? TO Leading IndicatorsLagging Indicators Why Change?
  • Common Data Repository Questions and Discussion Thomas Danford, Thomas.Danford@tbr.edu Greg Turmel, Greg.Turmel@tbr.edu Pamela Clippard, Pamela.Clippard@tbr.edu