Academic Scheduling System
Sistem Penjadwalan Terintegrasi Otomatis
An automated academic scheduling system that generates conflict-free schedules while handling complex room, lecturer, time, and building constraints.
Academic Scheduling System / 2025
Automated academic scheduling workspace
SIPENTA is an automated academic scheduling system for generating conflict-free schedules from institutional constraints.
The system was built with a larger team of approximately 17 people and later refined by a four-person core group to complete the most important flows.
Academic scheduling has to satisfy many constraints at once, including lecturer availability, rooms, classes, time slots, and lecturer movement between buildings.
The goal was to reduce manual scheduling work while respecting lecturer availability, room availability, class needs, course rules, time slots, and movement between buildings.
The project must not expose private institutional datasets or sensitive scheduling rules.
I worked as technical lead and full-stack developer, contributing across the scheduling logic, application flow, implementation details, and final refinement with the core team.
SIPENTA turns scheduling constraints into a structured generation workflow, then checks for conflicts so academic schedules can be produced more reliably than manual assembly.
Automated generation for academic schedules.
Conflict prevention across lecturer, room, class, and time constraints.
Building-transition awareness for lecturers moving between teaching locations.
Next.js supported the product interface and application shell, while Python was used where scheduling logic and constraint handling needed a practical implementation path.
The system treats constraints as first-class inputs instead of relying on manual correction after a schedule is already produced.
The main challenge was coordinating many constraints and team contributions without letting the scheduling output become opaque or inconsistent.
The system is completed and planned for intended use in the following semester. The copy avoids claiming active deployment until that use is verified.
SIPENTA taught me how technical leadership depends on clarity: when constraints, ownership, and integration points are clear, a large team can still move toward a coherent product.