Dashboard
Total Faculty
Total Courses
Total Rooms
Total Sessions
Total Workspaces
Faculty Management
| Name | Email (Identity) | On Campus | Address | Actions |
|---|
Students
Courses Management
Institutional Concept
Courses encode canonical teaching demand. L-T-P workload values and room-type preferences are converted into session requirements during scheduling preparation.
Field semantics: L-T-P represents lecture/tutorial/practical weekly hours; Credits is derived from workload; optional room preferences shape placement feasibility.
CSV columns: code, name, department, lecture_hours, tutorial_hours, practical_hours, course_category, optional expected_enrollment, required_consecutive_slots, preferred_room_type, description.
Uniqueness: code is unique. Missing or duplicate codes are rejected or skipped.
Downstream effect: course definitions drive session creation, faculty-course eligibility, and course-room eligibility.
| Code | Name | Department | L-T-P | Credits | Actions |
|---|
Batches Management
Institutional Concept
Batches represent formal learner cohorts (program + year + size). They provide the demand side of timetable allocation and cohort-level workload balancing.
Downstream effect: planner filtering, course assignment scope, and session audience targeting depend on batch definitions.
Relationship to Student Groups: student groups can represent full batches or derived sub-cohorts used by session-centric modeling.
| Name | Program | Year | Total Students | Actions |
|---|---|---|---|---|
| No batches yet | ||||
Rooms Management
| Number | Capacity | Location | Primary School | Type | Projector | Actions |
|---|
Session Planner
Workflow Semantics
Planner compiles institutional intent into session mappings by linking course demand, eligible cohorts, and faculty assignment decisions.
Each step narrows the feasible scheduling domain: cohort selection defines demand scope, and faculty mapping defines candidate instructors.
Program and year identify the institutional cohort receiving the planned sessions.
School Schedule Template
Institutional Concept
Define your school's weekly rhythm: working days, start/end windows, and lunch breaks.
Build a reusable school schedule template first, then apply or adjust day-level blocks.
Technical Details
CSV columns: day, slot_index, start_time, end_time, is_lunch.
Each (day, slot_index) should be unique within a template.
| Day | Slot | Start | End | Lunch |
|---|
Session-Centric Modeling
Institutional Concept
Sessions are the primary scheduling units. A session represents one recurring instructional activity with course identity, delivery type, student audience, and eligible instructors.
Downstream effect: generator feasibility, workload distribution, and room-time placement all operate on these session definitions.
Student Groups Semantics
Student groups encode who attends a session. Use batch for formal cohorts, cohort for grouped populations, and derived for split or synthetic subsets.
Groups CSV columns: code, label, group_type, program, year, size.
Uniqueness: code is unique. Existing group codes are skipped in bulk upload.
| Code | Label | Type | Program | Year | Size | Actions |
|---|
Session field semantics: Type is L/T/P modality, Duration is hours per occurrence, Occ/Wk is weekly repetition, and Consecutive slots is a hard continuity requirement.
Sessions CSV columns: name, course_code, session_type, duration_hours, occurrences_per_week, required_consecutive_slots, preferred_room_type, group_codes, eligible_faculty_emails.
Multi-value columns use | separators for group_codes and eligible_faculty_emails.
Uniqueness assumption: no strict unique key is enforced for session rows; avoid duplicate logical definitions in the same planning cycle.
Downstream effect: this dataset becomes the direct input domain for scheduling allocation.
| Name | Course | Type | Duration | Occ/Wk | Consecutive | Preferred Room | Groups | Eligible Faculty | Actions |
|---|
Eligibility Modeling
Institutional Concept
Eligibility matrices encode institutional permission boundaries. They prevent invalid assignments before optimization scoring is attempted.
Faculty-course matrix semantics: each allowed pair means a faculty member is permitted to teach that course.
Faculty-course CSV columns: faculty_email, course_code. Faculty identity is resolved by canonical faculty email.
Course-room matrix semantics: each allowed pair means a course may be timetabled in that room.
Course-room CSV columns: course_code, room_number. Uniqueness assumption: each pair should appear at most once.
Downstream effect: both matrices prune infeasible faculty and room candidates during generation.
Workspaces
Each workspace is an isolated scheduling universe.
Departments Management
| Name | Actions |
|---|
Manage Locations
Spatial Adjacency Modeling
Manage Locations is the canonical campus geography editor. Coordinates are optional during transition, but they enable map rendering and automatic walking-time estimates.
| Short Name | Full Name | Latitude | Longitude | Actions |
|---|
Secondary Location Adjacency Matrix
The values below represent approximate walking time in minutes between locations.
Settings
System Administration
This page is for administrator controls only. It manages login defaults, module visibility, and password resets.
Default faculty password policy: pass1234. Bootstrap administrator password policy: admin1234.
Future recovery contact is stored here for upcoming forgot-password workflow support.
Authentication
Loading authentication settings...
User Visibility
Choose which modules are visible to faculty users.
Room Capacity Policy (%)
Controls elective room sizing only. Default 100 means rooms must fit full expected enrollment.
Password Management
Reset any faculty password to pass1234.
Future Email Recovery
Loading recovery contact...