Allocation engine

Describe the campus once. Run the term as often as you like.

Enrolment shifts, a professor leaves, a laboratory closes for works. Re-running the allocation should be an afternoon, not another semester of coordination.

Inputs

Four things Kampus needs to know.

Rooms

Every classroom, laboratory and lecture hall, with capacity, building, block and the resources fixed to it. A room with anatomy equipment is not interchangeable with a room that has thirty chairs.

Cohorts

Each group with its real size, course and semester. Kampus works with cohorts rather than individual students, because that is how an institution actually times a term.

Subjects

Subjects with their workload, the cohorts taking them and the professors teaching them — including who can teach what, and when they are available.

Rules

The exceptions everyone in the faculty knows but nobody has written down. Kampus makes you write each one once, and then honours it on every run.

Kampus asset management: rooms, cohorts and subjects with capacity and status
A single inventory with capacity and status: 58 of 67 rooms active, 103 of 132 cohorts running.

Rules

The exceptions are the hard part.

Any scheduler can fill a grid. What breaks a timetable is the rule nobody encoded — the professor who always teaches Philosophy II in room 401, the anatomy class that has to be in the anatomy lab, at night, always.

  • Written in plain language, once, and reused every term
  • Applied per subject, per professor, per room or per shift
  • Switched on and off without deleting them
  • Visible in the conflict report when they cannot be satisfied
The rules column of the Kampus allocation wizard

Output

Conflicts, versions and a semester you can publish.

The engine does not pretend a perfect answer exists. It optimises what it can and hands back exactly what it could not resolve.

Conflicts, itemised

Each clash listed with the subject, professor, room and time — so a coordinator fixes three problems instead of re-reading three hundred rows.

Version history

Autosaves with author and timestamp. Sixteen saves into an afternoon, you can still see what the timetable looked like at 9:34.

Three views

Overview for the status of the run, weekly agenda for how a cohort actually experiences the term, and list for review and export.

The Kampus allocation overview, with pending conflicts and version history
78% resolved, three conflicts pending, sixteen autosaves — the state of a run at a glance.
The Kampus weekly agenda view for a cohort
Weekly agenda, by cohort, professor, room or subject.
The Kampus list view of every allocated class
List view — every allocated class, ready to review and publish.