Background
The university’s expansion created three campus-level operating environments. Each campus had its own SIS configuration, local academic processes, reporting routines, and student-service workflows.
The institution had already invested in LMS, ERP, and IAM systems, but these platforms operated around separate data structures. Student information, course records, billing data, access roles, and service requests moved through disconnected workflows.
Students experienced the fragmentation directly. They had to move between several portals to check timetables, billing information, academic requests, and campus services. Helpdesk teams absorbed the result through repetitive low-tier tickets.
Leadership also lacked a consistent cross-campus view. Academic reporting, accreditation preparation, resource planning, and scheduling analysis depended on manual reconciliation across systems that were never designed to operate as one environment.
Approach to solution
Computools started with current-state architecture assessment across SIS, LMS, ERP, IAM, student services, reporting, and scheduling workflows.
The team mapped data ownership across campuses and defined which systems had to remain authoritative for student records, learning activity, billing, access control, and academic operations.
The main architectural decision was to keep existing systems of record in place. Uni-Campus introduced an integration and data layer above them, reducing delivery risk and avoiding disruption during active academic periods.
Computools then designed a unified data model for student profiles, academic records, grading formats, course structures, billing references, schedules, access roles, and service requests.
The rollout was aligned with the academic calendar. Integration releases were phased so that enrollment, course registration, examination periods, and student-service peaks were protected from operational disruption.
Computools role
Computools acted as the product and technology partner responsible for:
- assessing the current-state architecture across three campuses;
- mapping SIS, LMS, ERP, IAM, reporting, and student-service data flows;
- defining the integration architecture and unified data model;
- designing the central student portal and role-based workflows;
- developing API services and data synchronization logic;
- integrating Canvas LMS, SAP ERP, Microsoft Entra ID, and three legacy SIS environments;
- implementing RBAC, auditability, and data-governance controls;
- building reporting and analytics views for academic and operational teams;
- supporting QA automation, phased rollout, stabilization, and post-launch support.
The team worked with stakeholders from IT, academic administration, student services, finance, compliance, scheduling, and university leadership.
Key decisions and outcomes
The first key decision was to preserve existing systems of record. This allowed the university to modernize student-facing and reporting workflows without interrupting academic operations.
The second decision was to normalize data before expanding portal functionality. Consistent student, course, billing, identity, and scheduling data made the portal reliable across campuses.
The third decision was to phase delivery around the academic calendar. This reduced rollout risk during enrollment, course registration, and reporting periods.
The completed platform moved the university from fragmented campus-level workflows to a connected digital ecosystem with unified data access, centralized portal services, and stronger operational visibility.