Welcome to Student News 1:00 – 2:00 (call in 12:45) Please MUTE your microphones!

1. Welcome to Student News1:00 – 2:00 (call in 12:45)Please MUTE your microphones! Make sure your K20 contact registers your district for the next month’s VTC. We will not be taking roll call, so please email a list of VTC attendees at your site to: stucoord@esd101.net

2. IntroductionStudent News VTC • Welcome to the February 2009 Student VTC. • Our next VTC will be March 26, 2009 • If you have comments or suggestions for upcoming VTC’s, please email them to: stucoord@esd101.net

3. Director’s Discussion Tim Colliver

4. Contact Information • Tim Colliver, Director Northeast Regional Data Center • Student, Fiscal, and Operations • Phone: (509) 789-3584 • E-mail: tcolliver@esd101.net If you ever feel that your needs are not being addressed please contact me.

5. Washington Education Decision Support System (WEDSS) • WSIPC Data Warehouse • Piloted with 4 districts at beginning of school year • Starting with Student Data • Additional Student Data elements will be phased in • Fiscal Data will be added in the future • Statewide implementation starting with NERDC • Ten districts to be selected within NERDC • Clarkston School District: 2/27/09 • Other 9 districts have not been identified No cost to cooperative members

6. District to District Transfer of Student Information • New module released spring 2009 • Allows transfer of student data from one district to another • Skyward to Skyward transfer only • Controls implemented for release of student data • Additional data elements will be added in phases No cost to cooperative members

7. Dropout Early Warning System (DEWS) • WSIPC At-Risk Module • Integrated module within Skyward • Module currently used by several states • Built on real-time requirements from Washington State • Purchasing a system now may put a district in non-compliance with state regulations once finalized • Data Elements: 13 variables to select from • RTI Module (Response to Intervention) will be included No cost to cooperative members

8. Yelm Community Schools Skyward Security Issue • Reported by Nisqually Valley News February 6, 2009 • Skyward User ID’s and Passwords were obtained • Security breach was not with Skyward, rather district business practice • District had Skyward User ID’s and Passwords saved in an unsecure location

9. March Non-Standard Downtimes March 2, 2009: 11:00 p.m. to 11:59 p.m.March 4, 2009: 7:00 p.m. to 11:59 p.m. All users MUST be out of the Skyward system during these downtimes.

10. News What's Happening Shelly

11. NewsUpcoming Release • March Release Weekend This Release is scheduled for: 3:00 AM - 9:00 AM Saturday March 7, 2009 Users must be logged out during this installation – be sure to tell your teachers! Release notes will be posted to the Student Resources Website

12. NewsUpcoming Training Next year scheduling training • For Secondary Schools • Training is consolidated into a single day (instead of Parts 1 and 2 as we have done in the past) • You should have received an e-mail informing you of the date and location for your workshop. Please sign up with Sandy Haasch even if the workshop is being held in your school district. • Dates are posted on the Student Records Calendar. Feel free to contact us if you are unsure of the date you are scheduled to attend. • For those who have chosen not to attend a workshop, the Training Packet is posted on the Student Records Website. • We will be announcing Elementary Scheduling, Year End Prep, and Year End workshops soon.

13. NewsImportant Dates Washington State WESPaC User Group (WASWUG) Conference March 8 – 10, 2009 at the SEATAC Double Tree Hotel Hope to see you there! For those unable to attend, we will share pertinent information with you upon our return

14. .175 Reminders • Trimester collection took place February 17, 2009 • Semester 2 collection will be sometime in April – exact date yet to be determined • At the February OSPI CSRS VTC districts were reminded to fix Processing Errors prior to file errors. Follow the Top Down error correction process recommended by OSPI.

15. Graduation Requirements Maintenance Juli

16. Graduation Requirements Maintenance • The instructions within this presentation are not meant for initial setup and assume that you have a basic understanding of the Graduation Requirements Setup in your District. • We will cover: • Graduation Requirements Reminders • Subject Codes • Curriculum Maintenance • Graduation Requirements Module • Student Graduation Requirements Reporting • Updating for a single student

17. Reminders Juli

18. Reminders If your district has more than one high school entity, it is best to assign one person who will verify that all pieces are in place. If there are any ‘missing links’ the student graduation requirement tab and the graduation requirements reports could be incorrect. It is recommended that all Curriculum Keys be created at the district level (entity 000). If you have only one high school entity and the Curriculum Master has been set up at the entity level, that is ok. If you have multiple high school entities the Curriculum Master must be set up at the district level . When adding new Curriculum Master records it is very easy to inadvertently set them up at the entity level. Again if there is only one high school entity in your district, this will not cause any problems. However if your district has multiple high school entities you need to make sure that new Curriculum Master records are set up at entity 000.

19. Reminders SM/OF/AS/CM

20. Reminders SM/OF/AS/CM When you click edit on the Course Curriculum Master List , the Curriculum Master Maintenance screen is displayed

21. Reminders FAQ What if I have multiple high school entities and forget to change the entity code on the curriculum master to 000? • If a student transfers in-district, and has received credit for a course, and the curriculum master for that course is not tied to entity 000, the course will not be included in the student’s graduation requirements for the new entity.

22. Reminders • Determine if you are set up with a district or an entity plan • Select your entity (not 000) • The ‘Level’ column on the right side of this screen will tell you whether you are set up with a District or an Entity Plan. Below is an example of a district level plan • SM/Office/Curriculum and Assessments/Grad Reqs/Setup/ • Coursework Requirement Setup Area

23. Reminders Below is an example of an entity level plan • SM/Office/Curriculum and Assessments/Grad Reqs/Setup/ • Coursework Requirement Setup Area Note which type of plan you have

24. Subject Codes Crista

25. Subject Codes • For the purposes of this training we will assume that all courses and curriculum keys that count toward graduation requirements, have subject codes. • If each course/curriculum has a subject code, it is much easier to Cross Reference them to Graduation Requirements. Notice the Geometry Class has a Subject Code of Math (MTH) • SM/OF/CS/MA

26. Subject Codes Placeholder Classes • Since placeholders do not meet a graduation requirement they should not have a subject code entered. Notice the Running Start does not have a subject code • SM/OF/CS/MA

27. Subject Codes Run a report to check subject codes • SM/OF/CS/MA/Report/Course Report by Course

28. Subject Codes Sample Report Notice that SST300 for the 2006 school year should have a subject code The other 2 courses are place holders and should not have a subject code

29. Curriculum Maintenance Shelly

30. Curriculum Keys • All courses that meet a graduation requirement must have a corresponding curriculum key. • Courses that do not meet a graduation requirement, such as place holders, late arrival and early dismissal do not need to have a curriculum key Notice the Curriculum key for the English 3 Course Master

31. Curriculum Keys Cleaning up Curriculum Keys • Delete Curriculum Keys from courses that do not count towards graduation requirements. • Add Curriculum Keys to courses that do count towards graduation requirements.

32. Curriculum Keys Student Management/Office/Current Scheduling/Course Master Cleaning up Curriculum Keys

33. Curriculum Keys Student Management/Office/Current Scheduling/Course Master 1 2 3

34. Curriculum KeysReminder A single Curriculum Key can fulfill multiple Coursework Requirement Areas.

35. Curriculum Keys Cleaning up Curriculum Keys • Verify all the Curriculum Keys are: • coded with entity 000 (unless you are setup with an Entity plan) • tied to a course • tied to a graduation requirement (aka Requirement Sub Area Code) • Run 3 versions of the Course Curriculum Master Report

36. Curriculum Keys Student Management/Office/Curriculum and Assessments/Curriculum

37. Curriculum Keys Sample Reports Student Management/Office/Curriculum and Assessments/Curriculum Version 1: These courses are not coded with entity 000

38. Curriculum Keys Sample Reports Student Management/Office/Curriculum and Assessments/Curriculum Version 2: Curriculum keys are not tied to any courses

39. Curriculum Keys Sample Reports Student Management/Office/Curriculum and Assessments/Curriculum Version 3: Curriculum Keys linked to a grad requirement

40. Graduation Requirements Module Shelly

41. Graduation Requirements Module Coursework Requirement Areas and Requirement Sub Area Codes SM/Office/Curriculum and Assessments/Grad Reqs/Setup/Coursework Requirement Setup Area Each Coursework Requirement Area is broken down into Requirement Sub Area Codes Result of Clicking Edit

42. Graduation Requirements Module SM/Office/Curriculum and Assessments/Grad Reqs/Setup/Coursework Requirement Setup Area/Cur Master

43. Graduation Requirements Module Updating the General Electives Requirement Student Mngmnt/Office/Curriculum and Assessments/Grad Reqs./Setup/Coursework Requirement Area Setup

44. Graduation Requirements Module Verifying your setup The best way to verify your Graduation Requirement setup is to use the report in the Curriculum Master: Student Mngmnt/Office/Curriculum and Assessments/Curriculum Master/Report Hint: This is report 3 as referenced earlier.

45. Graduation Requirements Module Splitting a Plan Splitting a plan is necessary if the graduation requirements change from one graduation year to the next. Please request help from ESD101 before proceeding

46. Graduation Requirements Waivers Crista

47. Waiver Classes • When issuing a waiver, a course must be added to the student’s grade history. These course codes must be flagged as a waiver in the Category field in the course file. • When these courses are added to a student’s grade history, the program automatically recognizes the waiver and adjusts the student’s required coursework using the Earned Credit value from the course. • Three processes are commonly done to add a Coursework Requirement Waiver: • Adding a Waiver Course • Linking the Curriculum Master to the Coursework Requirement Area • Adding a Waiver Course to Grade History • These processes are detailed on the following slides

48. Waiver Classes Adding a Waiver Course • Student Mngmnt / Office / Current Scheduling / Course Master

49. Waiver Classes • Linking the Curriculum Master to Grad Req’s • Student Mngmnt / Office / Curriculum & Assessments / Grad. Reqs.

50. Waiver Classes • Adding a Waiver to Course History • Student Mngmnt / Student / Grades tab