The SIS keeps SIRAS current with student demographics and, when desired, contacts. SIRAS provides current Special Education and, when applicable, Section 504 information back to the SIS. Districts can move toward that goal in stages.
| Choose the Integration PathAeries has its own setup path; other SIS products commonly use file-based/SFTP exchange. | Think About Both DirectionsKeep SIRAS current from the SIS and keep the SIS informed from SIRAS. |
| Review in TrainingTest representative data before relying on Production. | Work Toward AutomationManual steps are acceptable while the district works toward a reliable recurring exchange. |
Choose the Integration Path
| Situation | Start here |
|---|---|
| Aeries | Aeries–SIRAS Integration: Configure and Test Both Data Directions |
| PowerSchool, SchoolWise, School Pathways, Synergy, or another non-Aeries SIS | File-Based SIS Integration: Implementation Guide. Product-specific extraction/import details vary; contact [email protected] when vendor-specific assistance is needed. |
| SFTP connection help | SIRAS SFTP: Secure File Exchange & Connection Settings |
| Established integration troubleshooting | SIS Integration Troubleshooting & Ongoing Monitoring |
Think About Both Directions
For file-based integrations, current Special Education demographics are the primary inbound goal. Contacts are an available parallel option. Districts using the SIRAS 504 module may also exchange separate 504 demographic and contact files where useful.
Where the SIS supports imports, use SIRAS export files to keep the SIS aware of current Special Education and Section 504 participation. Service information is also available for local use.
Use Data Import: Demographic File Specification and Data Import: Contact File Specification for the inbound file structures. Use Data Export: Special Education and Section 504 Data from SIRAS to SIS for the complete SIRAS → SIS export-file reference.
Review Actual Results in Training Before Production
The goal of Training review is to compare representative district data with the expected SIRAS result. Start with standard behavior and address source-data or mapping exceptions only when they actually appear.
Work Toward the Most Reliable Exchange the District Can Support
Manual files and manual handoffs are useful during implementation and may remain necessary when an SIS does not support a particular automated exchange. They are not a failure. The longer-term target is to automate the recurring exchanges the district and SIS can support and assign staff to review the resulting logs or completion reports.
