Data Integration Layer – ODS: ODS is a non-queryable centralized staging areas for storing extracted, cleansed, and transformed data, and for gathering centralized metadata for implementing an Enterprise Data Mart Architecture (EDMA), eliminating the need for another non-queryable staging area called data warehouse. Needed is a dimensionally modeled data warehouse for enterprise DSS, prepared to provide the best in query response performance and to support the most advanced OLAP functionalities.
Enterprise Data Warehouse Fundamentals 101 KIDS Phase II Project Mojo Nwokoma Director , Enterprise Data Systems Architecture Office of Assessment & Information Services Oregon Department of Education 503-378-3600 x2242 [email_address]
Data Warehouse (DW) is a collection of integrated, subject oriented, time-variant, and non-volatile data from various sources into a single and consistent warehouse that supports reporting, analysis, and decision making within the enterprise.
Integrates operational data through consistent naming conventions, measurements, physical attributes, and semantics.
Business Intelligence (BI) solutions use a blending of technologies, including relational and multi-dimansional databases, client/server architecture, and graphical user interface, to integrate disparate data sources into a single coherent framework for real-time reporting, drill-through analysis and decision support.
KIDS Phase I Project Report: The Business Case for Change
NCLB & Federal Accountability:
The reporting and performance requirements of NCLB demands a fundamental change in the statewide data collection and reporting.
The need to report individual student achievement and aggregation of data by subgroups.
Statewide Accountability & Efficiency:
Major gaps and inefficiencies exist in information collection, reporting and analysis at both district and state levels that need to be addressed.
Funding formula compliance and equity, and ability to evaluate relative effectiveness/ineffectiveness of education programs.
Student & Community Service:
Growing stakeholder demand for a significant improvement in student records availability, accessibility, portability, and accuracy.
Cost Efficiency Gains:
Evidence of economies of scale resulting in cost reductions in the management of administrative systems at the larger school districts and ESD structure.
Source: KIDS Phase 1 Final report: ODE & IBM Confidential (10/20/05)
KIDS Phase II Project Planning: 5 key questions for a successful project planning & implementation What? When? Who? Why? How? SUCCESS
- Business Case
The Essential Building Blocks for a Successful Enterprise Information Management Project
Enterprise Data Warehouse Architecture District Data Warehouse
Data Mart SIS Data Mart FINANCE Data Mart Transportation Data Mart Instruction HR SIS Curriculum & Instruction Finance Nutrition Extraction Phase Transformation Phase Load Phase Data Management H/W Server Platform Applications
KIDS Phase II Project District/ESD Server Deployment & Data Warehouse Integration Architecture Transaction System Transaction System Transaction System Transaction System Transaction System ODE (State) DW Physical & Virtual ODS = Operational Data Store DW = Data Warehouse ODS ODS ODS ODS ODS Hillsboro District DW Beaverton District DW Portland District DW Eugene District DW ESDs DW LEGENDS: KIDS Work = ODE Districts Record Exchange
Project Planning Methodology – “The How?” For the Project Team Step 1: Define the Work Breakdown Structure The first is to create a comprehensive Work Breakdown Structure (WBS). The WBS lists all the phases, activities and tasks required to undertake the project. Identify and describe each phase, activity and task required to complete the project successfully. Depict the order in which the tasks must be undertaken and identify any key internal and external project dependencies. Also list the critical project milestones, such as the completion of key project deliverables Step 2: Identify the Required Resources Having listed all of the tasks required to undertake the project, you now need to identify the generic resources required to complete each task. Examples of types of resource include: full-time and part-time staff, contractors, equipment and materials. For each resource type, identify the quantity required, the delivery dates and the project tasks in the WBS that the resource will be used to help complete. Step 3: Construct a Project Schedule To construct your schedule, you need to: List the phases, activities and tasks Sequence the phases, activities and tasks Add key internal and external dependencies Allocate relevant completion timeframes Add additional contingency to mitigate risk Assign resources required to complete tasks List critical delivery milestones Specify any assumptions and constraints
Lack of granular, integrated, accurate, standardized, and timely data regarding student performance and achievement both for individual students and specific student subgroups.
Lack of data and information integration between instructional management sources and assessment sources aligned to the state’s specific educational standards. Other factors affected include attendance record, discipline, teacher qualification, classroom size, and instructional hours.
Lack of close collaboration between the districts and ODE in tracking students as they move through the educational system, both vertically and horizontally, in order to improve performance by identifying actionable indicators.
Lack of specific multi-year student performance information to support longitudinal analysis, accessible at the State, District, and school levels with appropriate controls to assure confidentiality.
Need for data and tool standardization between all reporting districts to ensure accurate, consistent, and useful analytical input for decision making purposes.
No single version of the truth exists for business rules and data definitions among various data sources.
Lack of easily validated financial information that accurately reports budgeted vs actual expenditures by program that allows correlation of these expenditures to student performances.
Lack of appropriately controlled online access to information for all stakeholders regarding student progress and school quality.
Reports and associated BI tools are not standardized.
Recommended Model for Enterprise Data Warehouse System KIDS Phase 11 Project E-Portal Data Warehouse Operational Data Store ODS Transactional Database Educational Stakeholder Communication Benchmarking/Decision Support District & State Reporting Day to Day Operations PK-12 Data Model for Information Management (ODE & IBM Confidential) 10/20/05
Data Integration Layer & Operational Data Store (ODS):
ODS is a non queryable centralized staging areas for storing extracted, cleansing, and transformed data, and for gathering centralized metadata for implementing an Enterprise Data Mart Architecture (EDMA), eliminating the need for another non queryable staging area called data warehouse.
Needed is a dimensionally modeled Data Warehouse for enterprise DSS, prepared to provide the best in
query response performance and to support the most advanced OLAP functionalities.
Integrating systems that support instructional management that empowers teachers to combine
student performance and instructional data to make informed classroom decisions.
Districts will be better able to meet NCLB and state standards for having “highly qualified” teachers
in the classroom.
2. Integrated & Interoperable Operational Data Store (ODS)
Provide ability to evaluate student performance within selected programs across various schools
and districts in the State, and highlight ways to achieve AYP consistently over time.
Allows for quick turnaround in transferring students records when they move between districts.
Ease reporting burden on districts, and eliminate redundant and possibly inaccurate reporting of data, and a better foundation for integrated data analysis.
3. Data Warehouse & Decision Support System /Tools
A repository for State and district reporting and analysis even at student-level data.
Allows for more meaningful system-level questions and answers by legislators or policy makers.
Greater system accessibility to all users with relevant security access privileges will mean greater
acceptance and use, and ultimately better decision.
4. System Wide Communication Portal
Provide a focused location for access to information, analytical/reporting tools, and the necessary
training and support. Also, maximization of effective system-wide use of state’s data warehouse.
Rapid and wide dissemination of integrated and proven instructional and administrative practices.
KIDS Phase II Project High-level Project Work Plan, Time-line, & Resource requirements Project Phase: Time-line Resource Requirements
Requirements Validation January 10, 2006 Mojo & Gary Scheduled trips to all
Districts & ESDs
3. “ Test Site ” DW/ODS Modeling, June 30, 2006 Database Administrator integration, ETL, Data Quality, Data Modeler/Analysts Meta Data Repository, and Data Quality Analysts Vendor “Bake-off” contracting Business User (Client) Meta Data Administrator ETL & BI developers Data Warehouse Project Manager
Inauguration of Governance & January 30, 2006 Doug Kosty & Mojo Nwokoma
Project Team committee
4. OLAP & Portal Development, October 30, 2006 End-user Business Analyst including Training, and Web Developer vendor “Bake-off” Contracting Portal Dashboard developer Business User (Client) BI OLAP Report Developer “ Train-the-trainer” Data Security Officer