Kansas State Department of Education Enterprise Data Strategy

1
Kansas State Department of EducationEnterprise
Data Strategy

• StateWide IEP task force
• April 25, 2006

2
The legacy.

• Independent silos each collecting and
  reporting data independently
• No link or consistency in reports
• No agreement on authoritative source
• Inconsistent technologies
• Work often redundant
• Security needs not necessarily understood or
  followed

3
The legacy
. . .
4
What issues did this cause?

• Security Confidentiality standards and
  policies were non-existent, unknown, or not
  followed
• Support Maintenance multiple technologies led
  to difficulty in providing effective support and
  inability to integrate
• Reporting Burden asked for the same data
  multiple times
• Inconsistent Data questionable data quality -
  multiple versions of the truth
• Redundant Data many sources or owners of data
  elements
• Data Availability required to access multiple
  sources to gather needed information
• Aggregate Data vs. Atomic Data detailed and
  aggregated data didnt agree or werent available

5
How are we addressing these issues?

• KSDE Enterprise Data Strategy
• Technology standards (.Net / Sql Server / web
  services / SIFXML? )
• System and data security
• Common authentication system
• SSL certificates and secure architecture
• Security policies
• Identification of authoritative data sources
• Horizontal Integration
• Metadata
• Enterprise data warehouse / data marts

6
Terminology

• Operational System optimized with fast response
  for transactions
• Operational Data Store optimized for reporting
• Enterprise Data Warehouse optimized for data
  storage
• Data Mart optimized for data analysis and
  business intelligence
• Business Intelligence use of data
• Metadata information about data
• Transformation processes to apply business
  rules to data
• Cleansing process of formatting and
  standardizing data
• Horizontal Integration data automatically flows
  across the organization
• Vertical Integration data automatically flows
  vertically from the source to KSDE

7
The Goal - KSDE Enterprise Design
Staff Stakeholder Training Capacity Building
Enterprise Architecture
Business Intelligence
Student Identifier
Student Data Repository
Submission Verification
Data Mart Research
Core Student Data
Cleanse Integrate Transform Load
LEA District Schools
Submission Verification
Enterprise Data Warehouse Integrated Time
Variant Cleansed
Submission Verification
Extraction Analysis
Submission Verification

Submission Verification

Submission Verification

Submission Verification
MetaData Business Rules, Tech Info, Data Quality
Definitions
S e c u r i t y
Common Authentication Security Architecture
Security Confidentiality Policies
Security Certificates
8
Where are we today?
Student Identifier
Student Data Repository
Submission Verification
LEA District Schools
Submission Verification
Submission Verification
Submission Verification
Submission Verification

Submission Verification

Submission Verification
9
How do we get to our objective?

• Challenges
• Capacity
• Culture
• Technical infrastructure
• Security infrastructure
• Iterative process

10
Whats the schedule for the Enterprise Data
System?

• 1/23/2006 Project Planning Start
• 6/14/2006 Project Execution Start
• Establish Enterprise Data System
• 6/15/2006 6/15/2007
• Priority 1 Data System Load
• 6/18/2007 3/14/2008
• Priorities 2 3 Data System Load
• 3/17/2008 5/15/2009
• 6/30/2009 Project Closeout Complete

11
Establish Enterprise Data System
Enterprise Architecture
Student Identifier
Student Data Repository
Submission Verification
Core Student Data
LEA District Schools
Submission Verification
Submission Verification
Submission Verification
Submission Verification

Submission Verification

Submission Verification
Definitions
S e c u r i t y
Common Authentication Security Architecture
Security Confidentiality Policies
Security Certificates
12
Load Priority 1 Data
Enterprise Architecture
Student Identifier
Student Data Repository
Submission Verification
Core Student Data
LEA District Schools
Submission Verification
Enterprise Data Warehouse
Enterprise Data Warehouse Integrated Time
Variant Cleansed
Submission Verification
Submission Verification
Submission Verification

Submission Verification

Submission Verification
MetaData Business Rules, Tech Info, Data Quality
Definitions
S e c u r i t y
Common Authentication Security Architecture
Security Confidentiality Policies
Security Certificates
13
Load Priority 2 3 Data
Enterprise Architecture
Student Identifier
Student Data Repository
Submission Verification
Data Mart Research
Core Student Data
Cleanse Integrate Transform Load
LEA District Schools
Submission Verification
Enterprise Data Warehouse
Enterprise Data Warehouse Integrated Time
Variant Cleansed
Submission Verification
Extraction Analysis
Submission Verification

Submission Verification

Submission Verification

Submission Verification
MetaData Business Rules, Tech Info, Data Quality
Definitions
S e c u r i t y
Common Authentication Security Architecture
Security Confidentiality Policies
Security Certificates
14
KIDS vs. Enterprise Data Warehouse

• What is KIDS?
• Kansas Individual Data on Students
• Operational system
• Unique State IDs
• KSDE authoritative source of core student data
• What is the Enterprise Data Warehouse?
• Data across the enterprise (student, staff,
  financial, organizational, )
• Time variant
• Integrated
• How are they related?

15
KSDE Enterprise Design
Staff Stakeholder Training Capacity Building
Enterprise Architecture
Student Identifier
Submission Verification
Data Mart Research
Core Student Data
Cleanse Integrate Transform Load
LEA District Schools
Submission Verification
Submission Verification
Extraction Analysis
Submission Verification

Submission Verification

Submission Verification

Submission Verification
MetaData Business Rules, Tech Info, Data Quality
Definitions
S e c u r i t y
Common Authentication Security Architecture
Security Confidentiality Policies
Security Certificates
16
Where does a Statewide IEP system fit?

• Operational system accessed by LEAs via browser
• Horizontally integrated
• Includes core student data
• Includes organizational data
• Vertically integrated
• Data required for federal reporting (via Special
  Ed State Management Information System)
• Enterprise Data Warehouse Business Intelligence
  tools

17
Where does a State Wide IEP system fit?
18
What are the benefits?

• Decreased redundant reporting
• Horizontal integration
• with KIDS for core student data
• with KSDE organization data
• Vertical Integration
• Special Education State Management Information
  System
• Enterprise Data System (metadata, business
  intelligence)
• Access and environment security
• Data confidentiality and policies
• Built on standards / open technologies (web
  based, supported by KSDE)
• As a student moves around the state, data can
  follow (based upon appropriate security)

19
Next steps