TABLE OF CONTENTS

• Overview of the Tes <-> Sentral Synchronisation Process
  • Tes –> Sentral
  • Sentral –> Tes

Overview of the Tes <-> Sentral Synchronisation Process

Tes –> Sentral

• Cyclical timetable structure (includes Bell times)
• Class data
• Class lists
•  Yard duties 
•  Study classes 
•  On-call periods 
•  Student timetables (cyclical and with daily variations) 
•  Teacher timetables - including casual teachers (cyclical and with daily variations) 
•  Date to cycle mapping (Mon 27th March is a Mon week ‘A’ for example) 
•  Daily variation events such as excursions, incursions, absences, covers, room swaps. 

Sentral –> Tes

•  Student data including Statewide/Admin ID’s 
•  Teacher data including Statewide/Admin ID’s 
•  Room data 

From a timetable perspective, Tes should be considered the ‘source of truth’ when it comes to all of the aspects listed in the Tes -> Sentral section above.  A new enrolment can be entered into Tes first to ensure that the student has a timetable to begin with, before the data comes across into Sentral from the admin system.  Tes and Sentral will then ‘match’ on the admin ID of the student upon the next sync, to ensure that the student’s timetable will begin appearing on Sentral and that the students name will appear on class rolls.

Alternatively, new student data (for your Year 7 cohort for example) can be downloaded into Tes via the synchronisation process, eliminating the need to import (as a file) or type the data into Tes.

Synchronisation should be done from Timetable Daily on a daily basis (if using), and when timetable changes have been made in Tes.  Ensuring the ‘Sync on Save’ checkbox is check in the Sync configuration window in Tes and Timetable Daily will ensure that Sentral is always displaying the most up-to-date information.