-
Notifications
You must be signed in to change notification settings - Fork 393
MeetingConstraints
This page documents the constraint modelling planned for the Automatic Schedule Builder project. This is not yet final, and will probably be updated as part 1 of the project progresses.
The constraints define where and how sessions (primarily WGs and BoFs) in meetings should be planned. Different constraints may different priorities, as a conflict-free schedule may not always be possible.
The following constraints are planned to be part of the business logic of the scheduler, although they will use information from the database, e.g. to determine which sessions are a BoF.
| Constraint | Comment |
|---|---|
| A single room during a single time slot can only have a single session | Absolute requirement |
| BoFs cannot conflict with any other BoFs | |
| BoFs cannot conflict with any other WGs in their area | |
| BoFs cannot conflict with PRGs | |
| BoFs cannot conflict with any area-wide meetings (of any area) | |
| Area meetings cannot conflict with anything else in their area | The area meetings are: dispatch, gendispatch, intarea, opsarea/opsawg, rtgarea, rtgwg, saag, secdispatch, tsvarea, irtfopen |
| Area meetings cannot conflict with other area meetings | |
| WGs overseen by the same Area Director should not conflict | Some ADs also oversee WGs outside of their main area] |
TODO: verify whether area meetings are recognisable as such in the database.
The following constraints are to be entered by users when requesting their session:
| Constraint | Comment |
|---|---|
| Conflict with other WG, BOF or whole area | Chair conflict highest priority, technology overlap second, key person third |
| Timeslot preference | WGs may declare mornings/afternoons of each day as "not possible" or "preferred" |
| Timing between multiple sessions of same WG | WGs may declare they want their sessions on consecutive days, or with at least one day in between |
| Adjacent session with other WG | WGs may declare they want their session to be scheduled immediately before/after another WG, same room, no break |
| Joint meetings | Multiple WGs hosting one session together - details TBD |
TODO: decide on a plan for joint meetings# Attachments