Presentation will start at 2:00 If you are using your phone for audio, please put it on mute. Submit questions through the chat feature For assistance go to: and click on Support Oregon Dept. of Education, April

Oregon Department of Education April 5, 2011 Oregon Dept. of Education, April

 Secondary data-entry personnel  Postsecondary Perkins contacts  CTE Regional Coordinators  Perkins direct-recipient grant managers Oregon Dept. of Education, April 20113

 Understand changes in technical skill attainment data reporting requirements for Perkins IV.  Understand timelines for new data reporting.  Understand what qualifies as a valid and reliable technical skill assessment.  Understand which programs should be reporting technical skill assessment data. Oregon Dept. of Education, April 20114

 Tom Thompson – ODE ◦ ◦ (503)  Questions will be answered at the end of this presentation or posted on the ODE website. Oregon Dept. of Education, April 20115

 Key features of Perkins IV: ◦ CTE Programs of Study ◦ Accountability based on data ◦ Assessment of Technical Skill Attainment  CTE Programs of Study beyond scope of today’s discussion  Accountability based on data ◦ Perkins IV Performance Measurement: ormancemeasurement.pdf ◦ Data for program management and improvement: Oregon Dept. of Education, April 20116

 Today’s focus is on how to collect and report the data for Perkins Performance Measure related to Technical Skill Attainment  Actually, two measures for Technical Skill Attainment for secondary and postsecondary: ◦ 2S1(a) and 1P1(a). The long-time approach using grades in CTE courses (which will continue), and ◦ 2S1(b) and 1P1(b). The use of valid and reliable assessment aligned with standards ◦ We are required to report to USDOE using results from 2S1(b) and 1P1(b) this year. Oregon Dept. of Education, April 20117

2S1(b) Technical Skill Attainment (Using assessments) Numerator: Number of CTE concentrators who completed their CTE program and took and passed valid and reliable technical skill measurements that are aligned with industry-recognized standards, if available and appropriate, and completed high school during the reporting year. Denominator: Number of CTE concentrators who took technical skill assessments and completed high school during the reporting year. 1P1(b) Technical Skill Attainment (Using assessments) Numerator: Number of CTE concentrators who completed their CTE program and took and passed valid and reliable technical skill assessments that are aligned with industry-recognized standards, if available and appropriate, during the reporting year or the following year. Denominator: Number of CTE concentrators who [completed their CTE program and] 1 took technical skill assessments during the reporting year or the following year. Oregon Dept. of Education, April 20118

 Assessments selected locally from an approved list ◦ List available through Oregon Skill Sets online database ◦  Locally developed assessments allowable ◦ Require approval from ODE in advance ◦ Also included in the Oregon Skill Sets online database Oregon Dept. of Education, April 20119

Click on Quick View Oregon Dept. of Education, April

1. Select Career Area 2. Select Cluster 3. Expand Assessments Oregon Dept. of Education, April

Part of the Expanded Assessments List for Manufacturing Oregon Dept. of Education, April

 Administered to program completers  Secondary completers ◦ ODE online program listing ◦ ◦ Students completing the program must be assessed ◦ Updates available online April 28, 2011  Postsecondary completers ◦ Complete a degree or certificate  AAS Degree  Independent certificate of 45 credits or more ◦ Oregon Dept. of Education, April

Oregon Dept. of Education, April

Oregon Dept. of Education, April

 Reporting on Secondary Technical Skill Assessment will be done through the CTE Student Data collection ◦ CTE data collections open April 28 to June 30, 2011 ◦ Student information systems should have been updated using file format data from: ◦  Specific data ◦ Assessment date ◦ Program code ◦ Assessment Type Code  entcodes.pdf entcodes.pdf ◦ Met or Did not meet (actual score not reported) Oregon Dept. of Education, April

Date Program Strand Code Assessment Type Met = M; Did Not Meet = D Oregon Dept. of Education, April

Program Strand Code Oregon Dept. of Education, April

 Divided into general types ◦ Performance Assessments (1A, 1B, 1C) ◦ Tests (2A, 2B, 2C) ◦ Portfolios (3A, 3B, 3C)  Divided into source and use ◦ Industry recognized license (1A, 2A, 3A) ◦ Externally developed and no license (1B, 2B, 3B) ◦ Locally developed (1C, 2C, 3C)  Full list available at: Oregon Dept. of Education, April

Most Common Secondary Performance Assessment Oregon Dept. of Education, April

Most Common Secondary Test Oregon Dept. of Education, April

Most Common Secondary Portfolio Assessment Oregon Dept. of Education, April

 Reported through OCCURS System  Fields and coding similar to secondary  Full list of codes available at: Oregon Dept. of Education, April

Oregon Dept. of Education, April

 Up to two assessments per student per year can be collected  Collection and reporting of grades will continue  Reporting by ODE to USDOE start  Approved programs must report by  Not all programs will have technical skill assessment data in Oregon Dept. of Education, April

Oregon Dept. of Education, April Student Assessment Student Information System State Data System Chosen locally Local system for reporting Third-party data usually available Proficiency score Sample reporting forms available Statewide system (OCCURS or OAIS) Able to collect data Secondary vendors notified Backup secondary online system Colleges have made modifications

 Optional secondary reporting document ◦ arytsadatareport.doc arytsadatareport.doc  Optional postsecondary reporting document ◦ ssesssubmissiontemplateccc.xls ssesssubmissiontemplateccc.xls Oregon Dept. of Education, April

 Make sure there is a local method to move data to the statewide system.  Identify programs that should or could be reporting data for  Make sure data is being reported during the appropriate timeline. ◦ Secondary – April 28 to June 30, 2011 ◦ Postsecondary – deadline August 5, 2011 Oregon Dept. of Education, April

 Understand changes in technical skill attainment data reporting requirements for Perkins IV.  Understand timelines for new data reporting.  Understand what qualifies as a valid and reliable technical skill assessment.  Understand which programs should be reporting technical skill assessment data. Oregon Dept. of Education, April

 This Webinar and Power Point will be posted on the ODE website at:  All questions and responses will be posted on the ODE website.  For any additional questions contact Tom Thompson at Oregon Dept. of Education, April

 CTE Regional Coordinators or Perkins Grant Managers  ODE resources on technical skill assessment ◦  ODE resources on CTE data quality ◦  ODE staff ◦ Technical Skill Assessment – Tom Thompson ◦ Perkins Data Reporting – Brent Jacobsen Oregon Dept. of Education, April

Q: Are the CTECS assessments and the NOCTI Oregon Agriculture assessment considered to be locally developed? A: Yes. They should be categorized as local assessments without an attached license. That would be code 2C for secondary and TESTLOC*** for postsecondary. Oregon Dept. of Education, April

Q: When reporting high school data, I think the program code for agriculture is 600 and the code for business is 250. Is that correct? A: Yes. The correct code for each program can be found on the website at: prprgs.aspx The code is a 3-digit number listed with the Program of Study title. Oregon Dept. of Education, April

Q: Should I input “met” and “dnm” in the student information system to indicate that the student met or did not meet the proficiency level of the assessment? A: Possibly. Different student information systems may use different terms. In the end, the community college data system (OCCURS) and K- 12 data system will only accept specific characters. These data systems accept M for met and D for did not meet. It is the responsibility of the student information system vendor or developer to make sure the appropriate type of data can be submitted. Oregon Dept. of Education, April