|
Creating Department Timetables |
  
|
|
Creating Department Timetables |
|
Once the departmental data are split up into different .gpn files each department can process its own data in the same way as if the department were the whole school. The planner can define the periods of his/her “own” classes and can optimise the timetable using all the tools that Untis has to offer.
It is also possible to enter additional master data or lessons that are new or that were previously overlooked. Such data are taken into account when the department data are imported into the school file.
Caution:
Data that have an effect on the complete school, e.g. the length of the school year, should never be modified by the department. Such data are not integrated into the school file.
The Untis title bar displayed in each department file indicates that it is a department file.
All data relating to the department concerned is exported. If cross-departmental resources are used, this data may include classes belonging to another department. In the example you can see that 2a, 2b and 3a have been exported for department A1. Class 2a was exported because it belongs to department A1 - the other two classes either belong to no department or to a different one, but there is one department A1 lesson in which they are involved.
Each exported lesson is assigned to precisely one department, and in the department files you see only the lessons of the relevant department. The figure shows lesson no. 6, which is a cross-departmental lesson involving classes 2a, 2b and 3a.
Any lesson can now be scheduled, deleted modified or added in the departmental files. The changes will be integrated into the overeall file when the department data are imported into the school file.