|
Example |
  
|
|
Example |
|
Errors and input weaknesses are described in greater detail below. The following example provides a brief introduction to the percentage planning function.
| 1. | Open the file demo2.gpn . |
| 2. | Delete all timetables via the menu item "Scheduling | Delete the Timetable". |
| 3. | An information window appears. Click on <OK>. |
| 4. | Carry out a timetable optimisation run (via "Scheduling | Optimisation") and enter the value 30 in the field "% of periods to be scheduled". |
| 5. | Display the timetable for class 1a ("Timetable | Classes"). |
The timetable for class 1a should correspond approximately to the timetable shown in the figure below. There may be slight variations in display depending on the software version you are using.
As mentioned before, the percentage applies to the entire school and not to individual classes. The example shows that more than 50% of the periods for class 1a have been scheduled. The software would have scheduled proportionately fewer periods for other classes. The high percentage of scheduled periods indicates that the lessons of class 1a are more "difficult" to schedule than the lessons of other classes.
Click on the subject "Design".
The period details window shows that the subject Design is difficult to schedule because three teachers are involved in the lesson (Andersen, Gauss and Curie) and two rooms are required (the Chemistry lab and the Physics lab). Furthermore, another class (1b) takes part in the lesson. If Untis attempted to schedule this lesson towards the end of the optimisation run, the software would find it much more difficult to find a slot on the timetable that would suit all teachers, rooms and classes involved in the lesson.
When the percentage planning function is unable to schedule periods, you can assume that inaccuracies and errors during data input are to blame.