The task
University processes cross several departments: an enrollment affects classes, a student record relates to tuition and different staff members need different views of the same information.
My role
The project work covers process modeling, configuration of existing ERP modules, linked scenarios and reproducible startup instructions. The institution and all demonstration participants are anonymized.
How it works
The prototype connects admission and enrollment with scheduling, attendance and grades. Financial scenarios connect an invoice, partial payment and remaining balance. Student requests and staff workflows extend the same administration environment.
Technical decisions
Frappe and ERPNext provide the core modules instead of rebuilding an ERP from scratch. Education, learning and support workflows are configured around related documents and role-specific access.
Reliability and boundaries
Separate role scenarios help verify what each participant can see and change. Data persistence and restart checks are part of the local setup. HEMIS, external payments and Telegram delivery are separate integration stages.
What was delivered
A functional prototype and a documented role-based walkthrough are prepared for reviewing linked university processes. The next stage is an institution-specific pilot with agreed integrations and acceptance scenarios.