District Setup - Incident Management
The following data elements are required for district setup. The first two pages of navigation are removed for brevity:
Start Page > District Setup.
- On the Start Page, click the School link at the top of the page. The school list appears.
- Choose District Office from the pop-up menu. The district start page appears.
- Click District. The District Setup page appears.
Note: For more information on code values see the Appendix.
Data Element | Additional Information | [Table]FieldName | Used in these Reports |
---|---|---|---|
District Information | |||
Name of District | Enter the district name. | [Prefs]Value [Prefs]Name=districtname | Required Setup |
District Number | Enter the district number. | [Prefs]Value [Prefs]Name=districtnumber | Required Setup |
Load Codes and Subcodes | Click the link to access the Arizona Incident Management configuration file, which is used to automatically set up incident codes and subcodes. Note: This link is only available if the Arizona Incident Management configuration file has not been loaded. | N/A | Required Setup |
Load is complete | This message appears if the Arizona Incident Management configuration file has already been loaded. This field is view-only. | N/A | Required Setup |
District Information > Load Codes/Subcodes > Codes and Subcodes Load Information | |||
Load Codes/Subcodes | Select the checkbox to automatically set up codes and subcodes for incident management. See the Appendix for code values. Verify that you want to load codes before clicking Submit, because the process cannot be reversed. The codes are loaded on the hour or when PowerSchool is launched. However, only the PowerSchool task master application is updated. If more than one PowerSchool application exists in a server array, see article 56478 on PowerSource. The PowerSchool log window displays either a Complete or Failure message when the codes are loaded. | N/A | |
Incident Management > Incident Types | |||
Name | Enter the three incident types available for Arizona:
| [Incident_LU_Code]Incident_Category [Incident_LU_Code]Code_Type=incidenttype | Required Setup |
Incident Management > Code & Subcode Setup Note: An automated process for setting up incident management codes is available by accessing the Load Codes and Subcodes link on the District Information page. In all instances, the State Detail Report Code must not be edited. Additional descriptions may be edited based on local requirements. See the Appendixfor code values. For more information about creating incidents, see Discipline Incident Setup. | |||
Action Codes | The following action codes must be set up:
See the Appendix for valid values. | [Incident_LU_Code]Code_Type=actioncode [Incident_LU_Code]Incident_Category [Incident_LU_Code]State_Aggregate_RPT_Code | Required Setup |
Action Subcodes | Multiple action subcodes must be set up. See the Appendix for valid values. | [Incident_LU_Sub_Code]Sub_Catetory [Incident_LU_Sub_Code]State_Detail_Report_Code [Incident_LU_Sub_Code]Is_State_Reportable_Flg = 1 (True) | Required Setup |
Attribute Codes | The following attribute code must be set up:
See the Appendix for valid values. | [Incident_LU_Code]Code_Type=attributecode [Incident_LU_Code]Incident_Category = State Reportable [Incident_LU_Code]State_Aggregate_RPT_Code = 100 | Required Setup |
Behavior Codes | Multiple behavior codes must be set up. These codes are used to assign a violation to a discipline incident. See the Appendix for valid values. | [Incident_LU_Code]Code_Type=behaviorcode [Incident_LU_Code]Incident_Category [Incident_LU_Code]State_Aggregate_RPT_Code | Required Setup |
Behavior Subcodes | Multiple behavior subcodes must be set up. See the Appendix for valid values. | [Incident_LU_Sub_Code]Sub_Catetory [Incident_LU_Sub_Code]State_Detail_Report_Code [Incident_LU_Sub_Code]Is_State_Reportable_Flg = 1 (True) | Required Setup |
Participant Attribute Codes | The following participant attribute codes must be set up:
See the Appendix for valid values. | [Incident_LU_Code]Code_Type=participantattributecode [Incident_LU_Code]Incident_Category [Incident_LU_Code]State_Aggregate_RPT_Code | Required Setup |
Participant Attribute Subcodes | Multiple participant attribute subcodes must be set up. See the Appendix for valid values. Note: Special Education (SPED) Codes are required only if SPED Need data is not tracked in PowerSchool via the SAIS Needs student pages. See Knowledgebase article 58749 on PowerSource for details on setting up SPED Codes if not tracking SPED data in PowerSchool. | [Incident_LU_Sub_Code]Sub_Catetory [Incident_LU_Sub_Code]State_Detail_Report_Code | Required Setup |
Location Codes | The following location codes must be set up:
See the Appendix for valid values. | [Incident_LU_Code]Code_Type=locationcode [Incident_LU_Code]Incident_Category [Incident_LU_Code]State_Aggregate_RPT_Code | Required Setup |
Location Subcodes | Multiple location subcodes must be set up. See the Appendix for valid values. | [Incident_LU_Sub_Code]Sub_Catetory [Incident_LU_Sub_Code]State_Detail_Report_Code | Required Setup |
Object Codes | There are no required object codes for Arizona state reporting. | N/A | Not Required |
Participant Role Codes | The following participant role codes are set up by default and should not be edited:
| N/A | Required Setup |
Time Codes | The following time codes must be set up:
See the Appendix for valid values. | [Incident_LU_Code]Code_Type=timecode [Incident_LU_Code]Incident_Category [Incident_LU_Code]State_Aggregate_RPT_Code | Required Setup |
Time Subcodes | Multiple time subcodes must be set up. See the Appendix for valid values. | [Incident_LU_Sub_Code]Sub_Catetory [Incident_LU_Sub_Code]State_Detail_Report_Code | Required Setup |
Duration Codes | The following duration code must be set up: Number of Days Removed / Reassigned. See the Appendix for valid values. | [Incident_LU_Code]Code_Type=durationcode [Incident_LU_Code]Incident_Category [Incident_LU_Code]State_Aggregate_RPT_Code | Required Setup |
Action Change Codes | There are no Arizona specific action change codes See the Appendix for valid values. | N/A | Not Required |
Action Attributes | The following Action Attribute codes must be set up:
See the Appendix for valid values. | [Incident_LU_Code]Code_Type=actionattributecode [Incident_LU_Code]Incident_Category [Incident_LU_Code]State_Aggregate_RPT_Code | Not Required |
Action Attribute Subcodes | Multiple Action Attribute subcodes must be set up. See the Appendix for valid values. | [Incident_LU_Sub_Code]Sub_Catetory [Incident_LU_Sub_Code]State_Detail_Report_Code | Required Setup |
Scheduling/Reporting Ethnicity Codes > Edit/New Ethnicity Code | |||
Code | Enter the ethnicity code. See the Appendix for ethnicity code values. | [Gen]Value [Gen]Cat=ethnicity | Required Setup |
Description | Enter the ethnicity description. | [Gen]Name [Gen]Cat=ethnicity | Required Setup |
Schools/School Info > Edit School | |||
School Name | Enter the school name. | [Schools] Name | Required Setup |
School Number | Enter the school number. | [Schools]School_Number | Required Setup |
Grades | Enter the school grades (lowest - highest). Note: Grade levels must be in the range -10 to 20. | [Schools]Low_Grade [Schools]High_Grade | Required Setup |
Reporting Method | Choose one of the following reporting methods for the AZ Safe and Drug Free report from the pop-up menu:
Note: A mandatory incident is any incident involving bodily injury and/or a mandatory violation and/or a mandatory action. Mandatory violations include all violations involving items in the Dangerous Items, Firearms, and Other Weapons categories. Mandatory actions include all actions in the "Removal" category, such as expulsion or suspension. See the Appendix for valid values in these categories. | [S_AZ_SCH_X]Safe_Rpt_Mode | Required Setup |
Years & Terms | |||
Years & Terms | Define term names and abbreviations with term beginning and ending dates. | [Terms]FirstDay [Terms]LastDay | Required Setup |