Record room capacities and teaching loads
Planning run for winter semester 26/27, 148 slots, 43 rooms, 12 lab constraints
Education
The seminars next door cannot find a room.Open agent
Enlarge demo
Developed in Germany · Hosted in the EU or on-premises
Delivered together with
Rooms, teaching loads and expected attendance sit in separate lists that are filled in at different times. Planning is based on last year's figures, and corrections follow after the second week of lectures. Every change means one query to the lecturer and another to the room booking office.
148
courses
The faculty is planning 148 courses for the winter semester.
43
rooms
43 rooms with between 12 and 300 seats are available.
9
clashes
Nine slots clash over room or lecturer and are untangled by hand.
5,300
empty seats a week
Large lecture halls run half empty while seminars wait for a room.
Once occupancy is calculated against all 43 rooms rather than last year's list, utilisation rises by 20%.
The 20% improvement in utilisation is this agent's headline figure. The room booking office keeps no record of empty seats; the 5,300 a week are extrapolated from 148 slots and 43 rooms.
The agent calculates occupancy proposals; academic administration approves the timetable.
Planning run for winter semester 26/27, 148 slots, 43 rooms, 12 lab constraints
2 scenarios calculated, scenario 2 cuts clashes from 9 to 2
plan_ws2627_v2.xlsx, 148 slots, 2 open clashes
It calculates scenarios and shows their utilisation. The room booking office makes the booking in the room directory.
If a seminar needs movable tables, it treats that as a constraint once it is recorded. The lecturer sets the requirement.
A lecture hall closed because of water damage stays bookable in its calculation for as long as the closure only sits in the facilities team's inbox. It recalculates only once the closure is entered in room management.
Connected systems
Campus management system
room management
course catalogue
Operations
Deployment model
Data processing
Responsible teams
How quickly is the Timetable Planning Agent ready to use?
Where is the data processed?
Where does the figure “20% better utilisation” come from?
All agents
25%
less planning effort
HR department, programme coordination
40%
less administrative effort
Examinations office, faculty
50%
faster processing
Student registry, admissions
60%
less time spent searching
Research data management, institutes, library
up to 60%
fewer first-level enquiries
Student registry, student advisory service
55%
faster processing
Examinations office, International Office