Download
peims reporting 2005 2006 n.
Skip this Video
Loading SlideShow in 5 Seconds..
PEIMS REPORTING 2005-2006 PowerPoint Presentation
Download Presentation
PEIMS REPORTING 2005-2006

PEIMS REPORTING 2005-2006

124 Vues Download Presentation
Télécharger la présentation

PEIMS REPORTING 2005-2006

- - - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript

  1. PEIMS REPORTING2005-2006 425 DISCIPLINE RECORDS

  2. 425 DISCIPLINE RECORDS • Coding should be decided by professional staff and NOT by data entry personnel. • Data should be entered daily. • Data should be verified at least once each six weeks. • Data is reported for PEIMS Summer Submission. D I S C I P L I N E Discipline Training 2005-2006

  3. 425 DISCIPLINE RECORDS • DATA INTEGRITY • Under TEC 37.008(m-1), failure to report all disciplinary removals and truancy actions as required by state and federal law may result in a review by the commissioner of education and notice to the local school board of any problems noted in the district’s data, or a violation of a law or other rule. This review may also result in a notification to the county attorney, district attorney, criminal district attorney, as appropriate, and the attorney general. This provision can apply to missing, inaccurate, and/or falsified information/data. • Discipline data is used to determine unsafe schools. Discipline Training 2005-2006

  4. Topics to be covered • Basic Rules for entering Discipline. • Guidelines for In school (ISS) and Out of School (OSS) Suspensions. • Things to keep in mind • How to enter multiple students involved in a single discipline incident. • New Offense Codes. • Accessing Cognos Reports. • Samples of different Discipline situations. Discipline Training 2005-2006

  5. 425 DISCIPLINE RECORDS BASIC RULES • Every disciplinary action that results in the removal of a student from any part of their regular academic program will be categorized in one of the following general categories: ISS, OSS, Expulsion, JJAEP, or DAEP. • For an ISS removal any setting other than the classroom will constitute a removal. Discipline Training 2005-2006

  6. In School Suspension Guidelines • What IS ISS (In School Suspension)? • If the student is sent to the principal’s office and told to remain there for the rest of the period or the rest of the day, that will constitute a partial day ISS removal. The intent is to “place” the student anywhere but in the classroom. The principal’s office became ISS. • If the student is sent to the principal’s office and placed in a “time out” situation, that will constitute a partial day ISS removal. • ISS can be any place where the student is not in the regular classroom. Discipline Training 2005-2006

  7. In School Suspension Guidelines • What is NOT ISS (In School Suspension)? • The teacher can have a “time out” situation in the classroom. This does not constitute a removal because the student is still in class. • There is no removal if a student is sent to the principal’s office but the principal takes no action and sends the student back to the classroom. • There is no removal if the student is assigned to lunch or after school detention. Discipline Training 2005-2006

  8. Out of School Suspension Guidelines • What constitutes a partial day OSS (Out of School Suspension) removal? • If the student is suspended at any period during the school day that day will be reported as a partial day removal. • If the student is suspended at any period during the school day and for two additional days, the partial day will be rounded up and reported as 3 days of removal. • If the student is kept in the Principal’s office for the remainder of the day, pending two days suspension, then this will be reported as one partial day of ISS and 2 full days of suspension. Discipline Training 2005-2006

  9. THINGS TO KEEP IN MIND! • Always enter discipline data from a form, not by hearsay, the story may change. • Never decide the coding on a discipline incident, if something doesn’t look right, then ask. • Keep discipline data current, don’t let it stack up, if you have questions on the coding decisions, then address them right away while it’s fresh in someone's mind. • All discipline incidents requiring a hearing at pupil personnel must be entered on the region system prior to scheduling. Any incidents requiring a placement will be entered by pupil personnel. Do not duplicate. • Discipline incidents which lead to out of school suspension, must NOT exceed 3 days. • Make sure all information is included in the discipline incident record, include comments whenever possible. • The most severe offense should be listed as the primary offense, when entering the discipline record on Region 20. • An offense or action code enclosed by parenthesis should not be used. • If a student is arrested, all actions taken must be after the student is released. • An offense of “fighting” should include two students, otherwise coding should re-evaluated and possibly changed to “conflict with another student” or “instigation”, whichever may apply. • Elementary offense and action codes may differ from Secondary Codes. Discipline Training 2005-2006

  10. Discipline Inquiry Screen Actions where a student is removed from their regular schedule are reported for PEIMS. NOT Reported to PEIMS Reported to PEIMS Discipline Training 2005-2006

  11. Discipline Maintenance Screen Discipline Training 2005-2006

  12. Discipline Record Multiple Actions For a single discipline incident, there can be several actions Multiple actions for one incident number Most severe offense is entered as Primary Discipline Training 2005-2006

  13. NEW SECONDARY Codes enclosed by parenthesis () should not be used Discipline Training 2005-2006

  14. NEW ELEMENTARY Codes enclosed by parenthesis () should not be used Discipline Training 2005-2006

  15. Northside Code PEIMS Code Discipline Training 2005-2006

  16. Discipline Record on Region 20 • Campus ID of Enrollment • Student ID • Incident Date • Incident Number • Primary Offense Code • Campus of Responsibility • Action Code • Action Date • Consequence Start/End Dates • Consequence Length • Difference Reason • Campus of Assignment 2 1 3 4 5 6 8 9 10 11 12 7 Discipline Training 2005-2006

  17. Multiple Students Involved in a Single Incident • At Region 20 Main Menu – • Select Student Discipline Maintenance Multiple Students • Add Discipline Data for first student – Save • Click on right arrow key to add additional students Discipline Training 2005-2006

  18. Sample Multiple Students Discipline Record • Offense and Action Information will be transferred to next student • Enter the next student ID and save if actions are same or make changes to actions, but primary offense should not change. • *Use the same procedures to add any additional students* 2 1 Discipline Training 2005-2006

  19. Sample Student requires Mandatory Placement Until student is placed by Pupil Personnel the warning will appear on the discipline record. Discipline Training 2005-2006

  20. Online Assistance Online Help Discipline Training 2005-2006

  21. Accessing Cognos Reports • At Region 20 Main Menu Screen • Select Reporting Products • Select NISD Cognos System • Cognos Sign-on screen 1 2 3 Discipline Training 2005-2006

  22. Accessing Cognos Reports 4 Click on link to Cognos Reports 5 Select Discipline Reports Folder Select Discipline Reports Folder 6 Discipline Training 2005-2006

  23. Accessing Cognos Reports The following reports will reflect PEIMS Reportable Incident Information Select your campus 7 Discipline Training 2005-2006

  24. PEIMS Discipline Reports Discipline Training 2005-2006

  25. PEIMS Discipline Reports Discipline Training 2005-2006

  26. PEIMS Discipline Reports Discipline Training 2005-2006

  27. Data Quality Reports for Discipline SAMPLE • Students appearing on this report have reported an offense of “Fighting”, but a second student is not tied to this incident number with the same offense code. • Fights require two students involvement, if a second student is not involved, then another offense code should be used. Discipline Training 2005-2006

  28. Data Quality Reports for Discipline SAMPLE • Students appearing on this report are reflecting the same incident number, but a different offense code. • Sometimes this will occur when one of the students involved has a hearing at central office and after investigations are completed one or more students may be changed to a more severe offense code, when originally they were all involved in a single incident. To correct this error call Rita Garcia at 397-8714 for assistance. Discipline Training 2005-2006

  29. Data Quality Reports for Discipline SAMPLE • Students who appear on this report have a greater than 3 days suspension in the official or actual days field. • The maximum number of days should NEVER be more than 3, and this includes partial days of suspension. • Enter the start date for suspension and the lng (length) then save, the system will calculate the ending date. Discipline Training 2005-2006

  30. Data Quality Reports for Discipline SAMPLE • Students who appear on this report have an offense code that requires a placement to an AEP Campus. • Check to make sure that a hearing has been scheduled. • All actions requiring placements are entered by Pupil Personnel Discipline Training 2005-2006

  31. Sample Discipline Situation #1 During Prep days, prior to the beginning of school Angel Elizondo was in line to register when Dolly Perez pushed Angel and caused her to fall. Angel and Dolly began to fight when Ms. Freckles stopped them and took them down to the principal’s office. They continued to fight in the office so Mr. Martinez called parents and scheduled a hearing at Central office. At the hearing, placement to an AEP for both students was decided. Region 20 would reflect the following discipline record for both. Although incident occurred prior to 1st day of school, the Start date can be no earlier than the 1st day of school. Discipline Training 2005-2006

  32. During the summer Precious Elizondo was at a Pizza Place. Precious saw her principal and his family at the Pizza Place and remembered that the previous school year the principal had suspended her from school. She started to harass one of the family members. The student was brought in for a hearing at Central office for Retaliation against an employee. At the hearing there was not enough evidence and a decision was made to send the student back to campus once school started. X This incident happened during the summer and no disciplinary action was taken. Because no disciplinary action was taken and incident happened during the summer no discipline record was created. Sample Discipline Situation #2 Discipline Training 2005-2006

  33. Common error with the same referral numbers Angel Elizondo and Dolly Perez were both entered into Region 20 with the same incident Number but with different primary offense code. In order to have the same incident Number the primary offense must be the same. Discipline Training 2005-2006

  34. Correcting the referral / incident number error • To change incident number you need to: • Go to inquiry select the red button make a copy of the screen along with any comments. • Delete the incident by going back to inquiry, select the green button and select the delete bar. • Go back to inquiry maintenance single student and re-enter all information from the print copy and save. Discipline Training 2005-2006

  35. Pupil Personnel Department 5900 EversSan Antonio, Texas 78238 William Woodland, Director of Pupil Personnel 397-8695 phone Tony Lozano Administrator Student System Specialists Rita Garcia 397-8714 Lorraine Elizondo 397-8698 706-8717 fax Discipline Training 2005-2006

  36. To summarize • Basic Rules for entering Discipline. • Guidelines for In school (ISS) and Out of School (OSS) Suspensions. • Things to keep in mind • How to enter multiple students involved in a single discipline incident. • New Offense Codes. • Accessing Cognos Reports. • Samples of different Discipline situations. Discipline Training 2005-2006

  37. Notes page Discipline Training 2005-2006