Welcome Greetings & Introductions Housekeeping items Purpose Providing user training for the submission of PERCA via the new web based EPPAS system EPPAS User Training

Agenda Timeline for our day together Overview of Training Topics Walk through the system Practice session with Q & A

 Why Does the Board Require Reports? MN Statute 122A.09 subdivision 4(d)  Third Round of Program Review since 2000  How is this report different from those we’ve done before? Rationale & Context

 MACTE representatives have been serving on a redesign task force for the past 3 years +  The goal was to provide a process that:  Provided data to evidence program effectiveness  Was less labor intensive and streamlined  Served multiple needs and required less duplication of effort  Standardized the review process across program types  Was focused on data driven continuous improvement efforts  Provided an accessible archive of programs for shared unit and BOT use The Creation of EPPAS

Program Reporting is now made up of 3 Components Reflected in Draft Program Rule – MN Rule  Program Inputs – Tier 1 (course work, field experiences, residencies, etc.)  Program Specific Candidate Performance Data – Tier 2 Pearson will provide MTLE pass rate data and edTPA data directly to the MN BOT annually  Continuous Improvement Reporting – Tier 3 Narrative PERCA Revisions

 Familiarize users from each unit with the EPPAS tool for program reporting  Understand the differences in reporting across program types  Begin working within the EPPAS applications for your institutions Training Objectives

 Unit staff responsible for entering program data (Entry Role)  Unit leaders (Verify Role) - Priority for immediate BOT staff support will be given to those reporting in the academic year - Who Are EPPAS Users?

 All users must first be granted approval by their unit leader prior to login  Enter through the EPPAS page on the BOT website  Login to Existing Account OR  Create MDE account then Log out and enter EPPAS again, using login and password  Request access for your user role - Entry vs. Verify  Receive confirmation when your access is approved at MDE.  You are now ready to enter & use EPPAS  Each user must have their own working account Do not share user names and passwords Login/User Access

 Verify that all of the approved programs at your campus have been entered and saved correctly  Each program is identified as unique on the first page of an application which is critical to matching program data. Before you begin…

The Home Your Institution Viewing the List of Program applications Sorting the list of programs Left hand navigation options Download Ready Documents Fiscal Attestation Faculty Qualifications Program Development and Capacity Statutory Requirements

 What is the difference between a RIPA application and a PERCA application?  Which should I be using and when?  Why does the process look different this time than it will in the future? RIPA vs. PERCA Applications

SEP vs. Content Applications SEP  Course Sequence - Program Inputs Only  Thresholds will count: Credits (18)  Field Based Exp. Hours will be totaled  Alignment to Standards  Program attachments Content  Course Sequence - Program Inputs  Thresholds will count: Credits (40) Field Based Exp. Hours (100) Student Teaching Weeks (12)  Alignment to Standards  Assessment Information  Candidate Competency Data (auto)  Program Attachments

Unique Identifiers Naming conventions Reporting Year Route Type/Route Code Undergraduate vs. Graduate Programs Cloning option Creating a Program The program identification page

 Course number/name  Naming/numbering conventions  Upload of current syllabi  Error messages vs. Warning messages  What is a waiver? Course/Experience Requirements

 Drop down menu created on course sequence page  “Approved PEPER” learning activity or assessment  If alignment to standards changes, this box will need to be updated to reflect the learning activity or assessment in PERCA applications  Completing learning activities/assessments now vs. in the future Alignment to Standards

 Performance Data will be available on PERCA applications only  Due to changes in Title II reporting to make this streamlining possible, data for MTLE scores may be inaccurate for the first cycle of reporting  All programs will import data, regardless of the N reflected. Low N will be taken into consideration when making approval decisions according to proposed MN Rule Performance Data

 Overlap with Title II Reporting for ease of state/federal alignment  May indicate a key assessment is imbedded in a particular course or experience, as well as in the SEP sequence  Standards that are being addressed will need to be stated Assessment Section

 Guidance will be offered going forward based on Rule revision.  Questions were distributed at spring MACTE meeting.  Answers/goals will roll forward to the next PERCA application so that each year, there is an opportunity to address the goals of the previous reporting cycle. Continuous Improvement Narrative

 Data Entry Role - Validate to make sure application is complete.  Respond to any error or warning messages  Upload Fiscal Attestation  Notify Unit Leader of completion  Unit Leader must verify information is correct, sign attestation and submit the application Submitting for Review

 IMBED Graph Approval Decisions

 MDE Helpdesk  User questions submitted by Compiled and added to FAQ document on the EPPAS website  User Guide/Handbook is forthcoming Support

 BOT staff will be on hand to answer questions as you explore  More information about nonconventional and alternative programs will be provided for those institutions that have them  Watch the EPPAS website for additional resources. Thank you for your time, attention and patience as we begin this work together! Practice Opportunity Q & A