Institutional ERP & LMS Platform
Unified campus platform for learning, transport, alumni, gate operations, and placements.
[Screenshot] — Institutional ERP admin / student dashboard
Overview
A production education ERP/LMS suite for colleges and institutions. The platform consolidates academic learning workflows with operational modules — Transport, Alumni, Gate Pass, and Placement — under shared authentication, role management, student profiles, and admin reporting.
Business problem
Educational institutions were running fragmented tools for academics, campus transport, alumni engagement, gate entry, and placements. Staff lacked a single source of truth for student data, approvals, and operational status.
Requirements
- • Shared student/staff master data across academic and operational modules.
- • Role-based access for admin, faculty, students, transport staff, and placement officers.
- • LMS capabilities for courses, materials, assessments, and progress tracking.
- • Operational modules for transport allocation, alumni records, gate passes, and placement drives.
- • Dashboards and reports for institutional decision-making.
- • Secure, maintainable PHP/CodeIgniter architecture with MySQL.
Architecture
- • Modular MVC (CodeIgniter) with shared auth, RBAC, and student master.
- • Domain modules: LMS, Transport, Alumni, Gate, Placement.
- • REST/API endpoints for dashboards and cross-module integrations.
- • MySQL relational schema with module-specific tables and shared references.
- • Admin console for configuration, users, and operational reporting.
Tech stack
Responsibilities
- • Implemented and maintained ERP/LMS modules for educational institutions.
- • Designed relational schemas linking students, staff, courses, and operational entities.
- • Built role-aware workflows for admins, faculty, students, and operational teams.
- • Delivered Transport, Alumni, Gate, and Placement module features end-to-end.
- • Improved reporting, dashboards, and cross-module data consistency.
- • Collaborated with institutional stakeholders on requirements and UAT feedback.
Challenges & solutions
Module silos created duplicate student data and inconsistent statuses.
Centralized student/staff master records and enforced shared identifiers across LMS and ERP modules.
Different user roles needed tightly scoped access to sensitive campus data.
Implemented RBAC with module-level permissions for academic vs operational functions.
Modules
0+
LMS · Transport · Alumni · Gate · Placement
Domain
Edu
College / institutional ERP
Stack
CI
PHP · MySQL · React/Next
Lessons learned
- • Shared master data is the foundation of multi-module campus systems.
- • Operational modules succeed when workflows match how staff actually work on campus.
Business impact
- • Reduced tool fragmentation for academic and campus operations.
- • Improved visibility for administrators across learning and operational processes.
- • Enabled institutions to manage students, transport, alumni, gate, and placements in one platform.
Future improvements
- • Deeper analytics across modules.
- • Stronger notification and approval automation.
- • Mobile-first student self-service improvements.