This article owns implementation, testing, Production activation, automation, the two data directions, and ongoing monitoring. Detailed file structures live in Articles 50, 9, and 69.
1. Confirm SFTP Access
Before working on automated SIS jobs, confirm that the district can connect manually to its SIRAS SFTP location. Use SIRAS SFTP: Secure File Exchange & Connection Settings for host, port, username, password, manual connection testing, folders, and firewall troubleshooting.
A district or SIS technical contact can connect manually to the district SFTP location.
2. Identify the Population and Designation
Do not treat “students in SIRAS” as one undifferentiated integration population.
| Population | Integration purpose |
|---|---|
| Special Education | SIS → SIRAS demographics/contacts can keep SPED Current data aligned. SIRAS → SIS studentData.csv can help maintain/reconcile current SPED participation, and serviceData.csv is available for local use. |
| Section 504 | Optional 504 demographic/contact files can keep SIRAS 504 data current. SIRAS → SIS 504StudentData.csv or a manual handoff communicates current 504 participation/exits to the SIS. |
| SST | SST has its own intervention/meeting workflow. Do not assume a SPED or 504 integration file represents the SST workflow unless a documented local process explicitly does so. |
3. Send the First File(s)
A manually generated file is appropriate for initial testing. The goal is to get representative data into the district SFTP location so SIRAS can inspect real source values.
| Inbound file | Suggested filename | Use |
|---|---|---|
| Special Education demographics | {7-digit district CDS code}_demographics.csv | Primary file-based inbound population. |
| Special Education contacts | {7-digit district CDS code}_contacts.csv | Optional parallel contact exchange. |
| Section 504 demographics | {7-digit district CDS code}_504demographics.csv | Optional when SIS 504 demographics should update SIRAS. |
| Section 504 contacts | {7-digit district CDS code}_504contacts.csv | Optional when the district also wants 504 contacts in SIRAS. |
Accepted working formats include CSV, XLS, or XLSX with descriptive headers. Use Data Import: Demographic File Specification and Data Import: Contact Data from SIS to SIRAS for detailed inbound structures.
4. Review Real Results in Training
- SIRAS reviews headers, identifiers, source values, schools/programs, dates, and other incoming data.
- SIRAS configures the initial interpretation and processes the file in Training.
- Local staff review representative students and the processing logs/results.
- The district and SIRAS identify only the source-data or mapping changes actually needed.
- Retest until the Training results reflect the intended behavior.
Most districts do not need extensive custom mapping. Add an exception only after Training shows a real local difference.
5. Enable the Approved Processing in Production
After the district confirms the Training results, SIRAS can enable the approved file processing in Production. Review the first Production runs closely so source-file, matching, or mapping problems are found before they become routine.
6. Work Toward Reliable Automated Delivery
Manual delivery is fine during implementation and can remain temporarily when district/vendor automation is not ready. The longer-term goal is the most reliable recurring exchange the district can support.
On the SIS → SIRAS side, schedule current demographic/contact files so SIRAS can process the newest data. On the SIRAS → SIS side, schedule retrieval after the current nightly SIRAS export files have been created.
7. Complete the Section 504 SIRAS → SIS Handoff
The SIS is responsible for the district's Section 504 CALPADS reporting, including the applicable Program 101 workflow. A new 504 determination or 504 exit in SIRAS cannot remain isolated in SIRAS.
Preferred path where supported:
504StudentData.csv → SIS import → SIS Program 101 / local CALPADS responsibility
If the SIS cannot import 504StudentData.csv, document a manual handoff so staff know who communicates a new 504 entry or exit to the SIS and how completion is verified.
Use Data Export: Special Education and Section 504 Data from SIRAS to SIS for the 504 field specification.
8. Complete the Special Education SIRAS → SIS Side Where Supported
| File | Role |
|---|---|
studentData.csv | Main Special Education SIS-facing file. It can maintain/reconcile SPED participation/status. When used to identify the current active SPED population, Inactive Reason is blank. |
serviceData.csv | Service data available for local use. It is not the same thing as Service Logs and is not necessarily the primary SIS integration target. |
How the receiving SIS applies these files is a local implementation decision. Use Article 69 for all outbound file layouts and fields.
Understand “Pending” in Integration Population Rules
When Article 69 says Pending records are not included in studentData.csv, it means the student's Special Education Current Active Status = Pending.
It does not mean:
- IEP Manager Pending Changes;
- Pending As Of MEET; or
- an archived transaction whose Report Status is Pending.
Similarly, 504StudentData.csv represents Active 504 plan records, not a 504 record that is still Pending for referral/review.
See Pending in SIRAS.
9. Monitor the Exchange After Go-Live
- Confirm the expected file/job ran.
- Review SIRAS processing logs and receiving-SIS completion evidence.
- Compare expected and actual record counts.
- Review unmatched/rejected records.
- Verify representative student values in the receiving system.
- Retest after credential, schedule, school, mapping, or vendor changes.
Verify that the receiving system actually processed it.
Use SIS Integration Troubleshooting & Ongoing Monitoring for established-integration problems.
