INTEGRATING SWIS DATA WITH YOUR DISTRICT DATABASE

It can be done!

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?

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

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

ONE PLACE VS. TWOHow does our school avoid the issue of double entry?

Integration Option: Distributor

SISDistrict

Data Report

Data Warehous

e

PBIS Applicatio

ns Database

SWIS

CICO-SWIS ISIS-SWIS

PBIS Assessment

ECS Distributor

Viable option for schools:1. Entering data into SWIS2. Can upload data into another data

source

Districts Using Distributor:Willamette ESDCascade Technology AllianceKalamazoo Regional Education Service Agency

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.

This seems like a technical issue…

…if only it were that simple

Challenges

Behavior categoriesSet, operationally defined vs. Custom for reporting requirements

Required fields10 required fields vs variable number for referral entry

Missing fields

Data integrityThis is a technical solution – there will be errors to resolve

REQUIREMENTS FOR SUCCESSWhat can you do to prepare for data integration?

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

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

Requirement for Success: Pool your resources

One school solution Multi-school solution

Regional District

School District

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 BehaviorSWIS       Student System      

Behavior Abbreviation Code Minor Behavior Abbreviation Code DescriptionAbusive language/ inappropriate language/ Profanity Inapp lan 2 0Physical Aggression PAgg 3 0Defiance/ Disrespect/ Insubordination/ non-compliance Disrespt 4 0Lying/ cheating Lying 5 0Harassment/ bullying Harass 6 0Disruption Disruption 7 0Tardy Tardy 8 0Property Damage/ Vandalism Prop dam 10 0Forgery/ Theft Theft 11 0Dress Code Violation Dress 12 0Use/ Possession of Tobacco Tobacco 13 0Use/ Possession of Alcohol Alcohol 14 0Use/ Possession of Combustible Items Combust 15 0Bomb Threat/ False Alarm Bomb 17 0Arson Arson 18 0Use/ Possession of Weapons Weapons 19 0Other Behavior Other behav 20 0Use/ Possession of Drugs Drugs 22 0Minor - Inappropriate Verbal Language M-Inapp lan 23 1Minor - Physical Contact M-Contact 24 1Minor - Defiance/ Disrespect/ non-compliance M-Disrespt 25 1Minor - Disruption M-Disruption 26 1Minor - Property Misuse M-Prpty Misuse 27 1Minor - Other M-Other 28 1Minor - Dress code violation M-Dress 29 1Minor - Technology violation M-Tech 30 1Minor - Tardy M-Tardy 31 1Technology Violation Tech 32 0Inappropriate display of affection Inapp affection 33 0Inappropriate location/ Out of bounds area Out bounds 34 0Minor - Unknown M-Unknown 35 1Gang Affiliation Display Gang Display 36 0Skipping Skip 37 0Truancy Truan 38 0Fighting Fight 39 0

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

Real World Example• WESD

Questions + Comments

Contact information:

Megan Cave + Robin Spoerl

1-855-455-8194

support@pbisapps.org