enterprise data system to support

20
Enterprise Data System to support Decision Making and Reporting Update to KSDE Leadership August 10, 2006 Kansas State Department of Education

Upload: aamir97

Post on 21-Jun-2015

315 views

Category:

Technology


0 download

TRANSCRIPT

Page 1: Enterprise Data System to support

Enterprise Data Systemto support Decision Making and Reporting

Update to

KSDE Leadership

August 10, 2006

Kansas State Department of Education

Page 2: Enterprise Data System to support

The Vision

School Secretary

Secretary of Education

District Level

State Level

Page 3: Enterprise Data System to support

The SHORT List: Data Accessibility Data Quality Effective Data Use

The NOT-SO-SHORT List: Ensure data provided are accurate, timely, and reliable Build a culture of data awareness and data quality Establish a secure environment for this critical information Establish convenient, reliable, repeatable processes for data collection and data

access Provide educators and policymakers with the data they need to improve student

achievement and effectively allocate resources (D3M) Provide appropriate data access to researchers to improve our understanding of

effective management and instructional policies Enable more efficient compliance reporting, releasing staff to focus on educating

students Improve the public’s access to school academic & financial data Provide alternatives for tracking and measuring student progress

The Vision - Project Objectives

Page 4: Enterprise Data System to support

Teacher Assignment & Licensure

Budget & Finance

Migrant

Career & Tech Ed

Special Ed

Student Data Repository

Assessments

Cor

eS

tud

en

tD

ata

Cleanse

Integrate

Transform

Load

Extraction

&

Analysis

Data Mart

Research

……

LEA

District

&

Schools

Enterprise Data Warehouse

Integrated

Time Variant

Cleansed

Student Identifier

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Data Mart

Fed Rpts

Data Mart

LEA Analysis

Data Mart

State Rpts

Staff & Stakeholder Training & Capacity Building

Return Data to the LEAs

Common Authentication – Security Architecture Security & Confidentiality Policies – Security Certificates

Definitions MetaDataBusiness Rules, Tech Info, Data Quality

OrganizationsData Mart

AYP

The Vision – Enterprise System Design

Page 5: Enterprise Data System to support

The Reality – Project Considerations

Must comply with 1998 Senate Bill 5 Legislative Funding 3 year plan – iterative process Priorities based on business objectives and technical

realities Must ensure KSDE’s capacity to maintain Not just a technology change – also a culture

change

Page 6: Enterprise Data System to support

Secure funding Establish internal capacity

Hiring Training Creating a culture!

Establish initial business priorities for guidance for project execution iterations Iteration 1 – Student Data (KIDS), Org Data (Directory), Assessment/Accountability Data (CETE) Iteration 2 – Staff (Teacher Education & Licensure, Para Databases) Iteration 3 – Programs (Migrant, Special Ed, Tech Ed), Other (ACT, ?), Finance

Complete initial project documents Planned Project document (CITO) High Level Project Plan (CITO) Other important project documents (Project Statement, Roles & Responsibilities, Communication

Matrix) Award contract for consulting expertise

Develop RFP Gain approval of RFP (CITO) Let and award RFP

Complete project management tasks Develop detailed project plan for first iteration Gain approval of detailed project plan (CITO)

The Reality – Project Planning and Initiation (1/2006 – 9/2006)

You Are Here

Page 7: Enterprise Data System to support

KSDE Staff: KSDE staff will lead most tasks, accessing contractor’s

expertise as needed, and developing in-house expertise to maintain the system

Plan capitalizes on KSDEs “business” knowledge

Contract Staff (via RFP) Contract with experts experienced in data warehousing

and business intelligence systems Contractors will provide advise and expertise as

needed. In many cases they lead the first iteration and KSDE leads subsequent iterations.

Contractors will lead quality verification efforts

The Reality – Getting the work done

Page 8: Enterprise Data System to support

Establish Enterprise Data System 9/2006 – 6/2007

Priority 1 Data System Load 6/2007 – 3/2008

Priorities 2 & 3 Data System Load 3/2008 – 5/2009

The Reality – Project Execution Includes 3 Iterations

Page 9: Enterprise Data System to support

(9/2006 – 6/2007) Enterprise Data Model

Conceptual Model of data subjects Technical Infrastructure

Hardware & System Software Enterprise Metadata

Design, develop, and implement framework Enterprise Data Warehouse

Design, develop, and implement framework Plan for Data Marts / Business Intelligence

Establish needs for iteration 1 data delivery Select tools based on these needs Build capacity with these tools

The Reality – Iteration 1: Establish Enterprise Data System

Page 10: Enterprise Data System to support

Teacher Assignment & Licensure

Budget & Finance

Migrant

Career & Tech Ed

Special Ed

Student Data Repository

Assessments

Cor

eS

tud

en

tD

ata

……

LEA

District

&

Schools

Enterprise Data Warehouse

Student Identifier

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Staff Training & Capacity Building

Common Authentication – Security Architecture Security & Confidentiality Policies – Security Certificates

Definitions MetaData

Establish Enterprise Data System

Organizations

Page 11: Enterprise Data System to support

Priority 1 Data System Load (6/2007 – 3/2008) (Student, Organization, Assessment & Accountability) Model relationships of Priority 1 data Load initial data to Enterprise Data Warehouse &

Metadata Repository (Priority 1 data) – current & historical Extract, Transform, Load Populate technical metadata Validate data quality

Establish repeatable process for ongoing loads Establish Data Mart(s)

Load data Train stakeholders

The Reality – Iteration 2: Load System with Priority 1 Data

Page 12: Enterprise Data System to support

Teacher Assignment & Licensure

Budget & Finance

Migrant

Career & Tech Ed

Special Ed

Student Data Repository

Assessments

Cor

eS

tud

en

tD

ata

……

LEA

District

&

Schools

Enterprise Data Warehouse

Student Identifier

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Staff Training & Capacity Building

Common Authentication – Security Architecture Security & Confidentiality Policies – Security Certificates

Definitions

Load Priority 1 Data

Organizations

Cleanse

Integrate

Transform

Load

Extraction

&

Analysis

Data Mart

Research

Enterprise Data Warehouse

Integrated

Time Variant

Cleansed

MetaDataBusiness Rules, Tech Info, Data Quality

Data Mart AYP

Page 13: Enterprise Data System to support

(3/2008 – 5/2009)

Priority 2 Data System Load – Staff Expand Model to include Priority 2 data relationships Load Initial data Enterprise DW & Metadata Repository (Priority 2 data) – current &

historical Extract, Transform, Load Populate technical metadata Validate data quality

Establish repeatable process for ongoing loads Establish Data Mart(s)

Load data Train stakeholders

Priority 3 Data System Load – Program & Finance Expand Model to include Priority 3 data relationships Load Initial data Enterprise DW & Metadata Repository (Priority 3 data) – current &

historical Extract, Transform, Load Populate technical metadata Validate data quality

Establish repeatable process for ongoing loads Establish Data Mart(s)

Load data Train stakeholders

The Reality – Iteration 3: Continue Data Loads

Page 14: Enterprise Data System to support

Teacher Assignment & Licensure

Budget & Finance

Migrant

Career & Tech Ed

Special Ed

Student Data Repository

Assessments

Cor

eS

tud

en

tD

ata

……

LEA

District

&

Schools

Enterprise Data Warehouse

Student Identifier

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Submission Verification

Staff Training & Capacity Building

Common Authentication – Security Architecture Security & Confidentiality Policies – Security Certificates

Definitions

Load Priority 2 & 3 Data

Organizations

Cleanse

Integrate

Transform

Load

Extraction

&

Analysis

Data Mart

Research

Enterprise Data Warehouse

Integrated

Time Variant

Cleansed

MetaDataBusiness Rules, Tech Info, Data Quality

Data Mart

State Rpts

Data Mart

Fed Rpts

Data Mart

LEA Analysis

Data Mart AYP

Return Data to the LEAs

Page 15: Enterprise Data System to support

(5/2009 – 6/2000)

Obtain signoff of the project Prepare (PIER) Post Implementation

Evaluation Report for CITO Document Lessons Learned & Celebrate!

The Reality – Project Closeout

Page 16: Enterprise Data System to support

*changing data rules*new data elements*new federal and state needs*new questions to be answered!

The Reality – The project’s over but there will be more work

Page 17: Enterprise Data System to support

Leadership’s Role – Participate in Data Governance

Issu

es a

nd R

espo

nsib

ility

Page 18: Enterprise Data System to support

To the field To the agency Others?

Leadership’s Role – Advocate the Vision

Page 19: Enterprise Data System to support

The Challenges

Business Intelligence Identifying alternatives Understanding and using data Building capacity at KSDE and in schools Developing and implementing a quality

research agenda

Page 20: Enterprise Data System to support

Future Challenges SIF

Collecting data Transcript transmission (school-school; school-higher ed)

Establish standards for data definitions & code sets for data sharing (PK – 20) Schools Universities Other agencies

Evaluating Programs Tie teachers to results Tie teacher ed programs to results Requires standard state course codes Use of State ID in multiple systems (KBOR, Licensure, ??)

Complying with FERPA, but meeting federal requirements for data sharing and effectively using the data