Abl Scheduler Data Exchange

Initial Set-Up

Abl works with your District IT to identify SIS data required for scheduling. Once District IT has confirmed complete data has been transferred, Abl sets up scheduling environments and works with school scheduling teams to resolve any issues related to data not displaying as expected in Abl.

Fresh Data and Nightly Sync

SIS data is sent nightly to Abl. Information from Abl isnotsent to the SIS during the nightly syncs. The last successful sync date is displayed on the Abl Scheduler homepage.

If any of the data listed above has been deactivated or removed in Abl (for example a current teacher who won't be returning next year that has been deactivated in Abl but remains active in the SIS), it will remain deactivated even after the data sync. 

Freeze Date 

As a district, a Freeze Date will be determined for all schools using the Abl Scheduler. After the freeze date nightly data syncs are discontinued and no further scheduling activity can take place in Abl. After the Freeze Date, Abl will prepare scheduling files to be exported into the SIS. 

Export Process

The export is a 3-5 day process during which the schedule created in Abl is loaded into the SIS. During this process no scheduling activity can take place in the SIS or Abl. Once the export is complete, any additional scheduling work must occur in the SIS. 

Post-Export Scheduling

Once the schedule has been successfully exported from Abl and loaded into the SIS any additional scheduling activity (walk-up registrations, hand scheduling, change requests, etc.) occurs in the SIS. Schedulers continue to have 'View' access to Abl, but no changes made in Abl will be reflected in the SIS.