1. Lessons Learned in Building and Maintaining Longitudinal Education Data Systems Jay Pfeiffer, Florida Department of Education

2. Additional roles include: Department-wide conduit for LMS, LED, Census, BEBR publications Division of Accountability Research & Measurement Assessment & School Performance PK-12 Student & Staff Comm Coll Tech Center Student/Staff Source Information Systems Integrating Systems PK-20 Education Data Warehouse FETPIP Florida’s Primary K-20 Data Resources SUS Data collected from testing vendors, school districts, community colleges Data collected from source systems, agency administrative data bases Aid Finance & Facilities Other

3. Florida’s Comprehensive K-20 Data System nThe “System”  Public pre-kindergarten through graduate school with student level data for public schools, community colleges, career and technical education, adult education, and the state university system  Staff, facilities, finance, and financial aid  Post school employment and non education system program data Dependencies  System of common course numbers and directories  Sunshine State Standards  Statewide articulation agreements and oversight committee  A state culture of data sharing  A means to follow the records of individual students across geographic areas and education sectors.

4. Florida’s Comprehensive K-20 Data System: Getting Data Out

5. Florida’s Comprehensive K-20 Data System: 2006 Initiatives Hurricanes National Data Conferences Strategic Planning State Task Forces Legislative Performance Profiles High School and Community College Feedback Sunshine Connections FACTS.org Research

6. Lessons Learned: What has worked for Florida? 1.Watch for opportunities: Even odd ones. 2.Articulate the goals & purposes of a state-level education information system – both long and short term, revisit as necessary. 3. Articulate benefits and risks for everyone involved. 4. To the extent possible build on existing systems, expertise. 5. Pursue opportunities to provide service and share information – entrepreneurship and “Quid pro quo…” 6. Publicize products, services, capabilities.

7. Lessons Learned: What has worked for Florida? 7. Establish and maintain a culture of data and information integrity. 8. Exceed all requirements dealing with confidentiality and restricted release. 9. Secure ongoing support. 10. Recognize that change is constant, keep ahead of it. Umbrella Lesson Learned: It’s never over…