1. INTEGRATING SWIS DATA WITH YOUR DISTRICT DATABASE It can be done!

2. How many of you… Use SWIS in your district? Use a student information system for state reporting? Double-enter discipline data? Have access to a data warehouse?

3. Overview of SWIS Web-based application Supporting school teams to Improve discipline practices Build individualized plans Report on outcomes Tiered approach Tier I – ODR Tier II – CICO Tier III – Individualized Plans Emphasis on efficiency and precision in decision making

4. State and District-Level Reporting Requirements Mandatory Data Entry Multiple Facets to School-Day Access to Student Information Progress Monitoring School-Level Reporting Data for Decision Making Focus on Student Success Comparing SWIS with Student Information Systems Accountability

5. ONE PLACE VS. TWO How does our school avoid the issue of double entry?

6. Integration Option: Distributor SIS District Data Report Data Warehouse PBIS Applications Database SWIS CICO-SWIS ISIS-SWIS PBIS Assessment Viable option for schools: 1.Entering data into SWIS 2.Can upload data into another data source Districts Using Distributor: Willamette ESD Cascade Technology Alliance Kalamazoo Regional Education Service Agency

7. What’s coming up? SWIS 5 student/staff roster import New API [Application Programming Interface] The API exposes an interface making it possible to read, create and update information in the SWIS database, such as referrals, students, and educators. The API internally handles communication with the underlying SWIS database, ensures basic data validation, and automatically transforms lookup values between your system and SWIS based upon mappings you specify.

8. This seems like a technical issue… …if only it were that simple

9. Challenges Behavior categories Set, operationally defined vs. Custom for reporting requirements Required fields 10 required fields vs variable number for referral entry Missing fields Data integrity This is a technical solution – there will be errors to resolve

10. REQUIREMENTS FOR SUCCESS What can you do to prepare for data integration?

11. Requirement for Success: Allocated Time Technical: Developer/Database Administrator Non-Technical: SWIS Facilitator Mapping document User training On-going data reviews Troubleshooting Initial Setup + Testing Scheduled downloads On-going maintenance Troubleshooting

12. Time Initial development—6 months New implementation—1 week SQL Platform Extract & Staging process in place Metric development & transform & load process will vary Time delays Permission forms Scheduling data extract (when and where) Outside vendors Other staff commitments

13. Requirement for Success: Pool your resources One school solutionMulti-school solution Regional District School District

14. Requirement for Success: Consensus Where to enter data: SWIS or SIS How to enter data: Required fields What will data look like in each system: Mapping labels Problem Behavior SWIS Student System BehaviorAbbreviationCodeMinorBehaviorAbbreviationCodeDescription Abusive language/ inappropriate language/ ProfanityInapp lan20 Physical AggressionPAgg30 Defiance/ Disrespect/ Insubordination/ non-complianceDisrespt40 Lying/ cheatingLying50 Harassment/ bullyingHarass60 Disruption 70 Tardy 80 Property Damage/ VandalismProp dam100 Forgery/ TheftTheft110 Dress Code ViolationDress120 Use/ Possession of TobaccoTobacco130 Use/ Possession of AlcoholAlcohol140 Use/ Possession of Combustible ItemsCombust150 Bomb Threat/ False AlarmBomb170 Arson 180 Use/ Possession of WeaponsWeapons190 Other BehaviorOther behav200 Use/ Possession of DrugsDrugs220 Minor - Inappropriate Verbal LanguageM-Inapp lan231 Minor - Physical ContactM-Contact241 Minor - Defiance/ Disrespect/ non-complianceM-Disrespt251 Minor - DisruptionM-Disruption261 Minor - Property MisuseM-Prpty Misuse271 Minor - OtherM-Other281 Minor - Dress code violationM-Dress291 Minor - Technology violationM-Tech301 Minor - TardyM-Tardy311 Technology ViolationTech320 Inappropriate display of affectionInapp affection330 Inappropriate location/ Out of bounds areaOut bounds340 Minor - UnknownM-Unknown351 Gang Affiliation DisplayGang Display360 SkippingSkip370 TruancyTruan380 FightingFight390

15. Requirement for Success: Commitment to data integrity Avoiding duplicates On-going training for new team members Understanding of how the data entered in one place impacts the data in another place. Consistency in data entry/reporting Review of data integrity reports

16. Real World Example WESD

17. Questions + Comments Contact information: Megan Cave + Robin Spoerl 1-855-455-8194 support@pbisapps.org