First identify the people who will actually do the work. Then contact [email protected]. SIRAS can help your team identify the correct setup path and the articles each person should use.
What do you need to do?
| I don't know anything about this yetStart here. Identify the doers, contact SIRAS, then assign the setup tasks. | We use AeriesUse the Aeries onboarding and testing workflow in Article 355. |
| We use another SISUse the file-based integration path for PowerSchool, Q, SchoolWise, School Pathways, Synergy, or another SIS program. | Our integration already existsSee what a live integration can update, understand a “System” change, or troubleshoot a problem. |
I Don't Know Anything About This Yet
That is a normal place to start. A district does not need one person who understands every part of SIS integration. The first job is to identify who can do each part.
1. Identify the doers
| Who you may need | What that person helps do |
|---|---|
| District integration coordinator | Keeps the setup moving, knows who the local contacts are, and coordinates questions or approvals with SIRAS. This may be the SEDS Coordinator, SPED administrator, SIS administrator, or another local project owner. |
| SIS / Aeries administrator | Works inside the district SIS. For Aeries, this person can create the SIRAS API Certificate/key and configure the Aeries Special Ed Data Import. For other SIS products, this person helps produce or consume the required integration files. |
| SIRAS / SPED / SEDS administrator | Knows the district's Special Education records and can review whether the information arriving in SIRAS or returning to the SIS looks correct. This person is also a good candidate for ongoing integration monitoring. |
| IT / network / SFTP support | Helps when secure file transfer, firewall, network access, or an SFTP client requires technical support. Some districts will not need a separate person for this role. |
| SIRAS Support | Helps the district choose the right integration path, configures the SIRAS side when needed, assists with Training review, and helps the district investigate integration problems. |
The goal is not to create a large project team. The goal is to know who can perform each task when it is needed.
2. Contact SIRAS
Email [email protected] and tell us:
- your district/LEA;
- which SIS you use or are moving to;
- whether this is a new SIRAS implementation or a change to an existing integration; and
- who the local doers are, if you already know them.
When a credential needs to be delivered to SIRAS, use the secure method identified in the applicable setup article.
3. Give each doer the article for their task
| Aeries setupAeries–SIRAS Integration: Start Here Starts with the district's first tasks: create the API Certificate/key, verify SFTP, and securely deliver the credential. |
Other SIS productsFile-Based SIS Integration: Implementation Guide Use for PowerSchool, SchoolWise, School Pathways, Synergy, and other file-based SIS integrations. |
| SFTP / secure file transferSIRAS SFTP: Secure File Exchange & Connection Settings Use when a doer needs to test SFTP access, understand connection settings, or securely exchange integration files. |
Established integration problemSIS Integration Troubleshooting & Ongoing Monitoring Use after an integration has been established and a scheduled job, file, or expected update is not working as expected. |
You know which SIS path applies, the people doing the work know their part, and SIRAS knows who to coordinate with. The technical setup can then be completed one task at a time.
We Use Aeries
Workflow
The person who creates the Aeries API Certificate/key should ideally also verify SFTP access, or work directly with the person responsible for SFTP. That way the district confirms the secure connection works before the same SFTP credentials are entered into Aeries.
If Aeries is already live in Production and you want to know which fields may be updated in SIRAS, use Aeries to SIRAS API Reference: Fields, Defaults & Optional Mapping. It is not the best starting point for a new implementation.
We Use Another SIS
For PowerSchool, Q, SchoolWise, School Pathways, Synergy, or another non-Aeries SIS, start with File-Based SIS Integration: Implementation Guide.
Product-specific extraction and import capabilities vary. Use SIRAS file specifications for the data being exchanged and contact [email protected] when you need help determining the correct vendor-specific path.
| Task | Reference |
|---|---|
| Send demographic data from the SIS to SIRAS | Data Import: Demographic File Specification |
| Send contact data from the SIS to SIRAS | Data Import: Contact File Specification |
| Send Special Education / Section 504 data from SIRAS to the SIS | Data Export: Special Education and Section 504 Data from SIRAS to SIS |
| Securely exchange files | SIRAS SFTP: Secure File Exchange & Connection Settings |
Keep Both Data Directions in Mind
A complete integration may involve one or both directions. The district can implement them in stages.
The SIS keeps SIRAS current with approved demographic, enrollment, school, and—when configured—contact information.
Where the SIS supports it, SIRAS can provide current Special Education and, when applicable, Section 504 information back to the SIS. Service information is also available for local use.
Do not assume that successfully setting up one direction automatically configures the other. Use the applicable implementation article to verify what your district has chosen to exchange.
Review Results in Training Before Production
During implementation, compare representative district data with the expected result before relying on the integration in Production. Start with standard behavior. Address source-data or mapping exceptions only when testing shows that an exception actually exists.
The SIRAS/SPED/SEDS doer should participate in this review because a technically successful connection is not enough—the resulting student information also needs to make sense for the district.
Our Integration Already Exists
Once an integration is established, the district should know who reviews its scheduled-task logs, completion emails, or other recurring results.
- Aeries is already live and you want to know what it may update in SIRAS: use Aeries to SIRAS API Reference: Fields, Defaults & Optional Mapping.
- Student History shows “System” as the updater: use Student History Help to understand automated background updates and where to investigate next.
- An expected update stopped working or the result does not make sense: use SIS Integration Troubleshooting & Ongoing Monitoring.
Assign an ongoing owner for integration monitoring and review the applicable logs or completion reports on a regular schedule.
