Uni-Campus

How Uni-Campus helped a multi-campus university unify student services without replacing legacy core systems.

case image

AT A GLANCE

The client is a UK-based private university group operating three campuses and serving more than 25,500 students and 1,535 faculty members. After campus expansion, academic, administrative, and student-service systems became fragmented across localized SIS environments, LMS, ERP, and identity infrastructure.

The university needed higher education system integration that could connect campus-level systems of record while preserving operational continuity. Leadership needed consistent academic, scheduling, billing, and student-service data without launching a high-risk core-system replacement.

Computools delivered Uni-Campus, a phased integration solution connecting three legacy SIS environments, LMS, ERP, IAM, a unified data hub, analytics, and a central student portal. After rollout, academic reporting preparation decreased from 8–10 business days to 3–4 business days, routine requests requiring manual intervention fell from 65% to 25% of ticket volume, and cross-campus data synchronization improved from 24–48 hours to under five minutes.

THE CLIENT

The client is a UK-based private multi-campus university group with three campuses, more than 25,500 students, and over 1,535 faculty members. The institution manages academic records, course registration, tuition billing, student requests, identity access, and cross-campus scheduling across a complex application landscape.

Each campus operated its own localized Student Information System. This created a need for student information system integration across academic records, grading formats, course structures, student profiles, and reporting workflows.

The university’s digital environment also included LMS, ERP, and IAM infrastructure that supported learning delivery, financial administration, identity management, and access control. These systems were operationally important, but disconnected data flows created manual work for IT, academic administration, student services, and leadership teams.

BUSINESS CHALLENGE

The main challenge was fragmentation across academic and administrative systems. The university had functioning core platforms, but each campus managed data through different structures, workflows, and synchronization cycles.

  • SIS fragmentation. Three localized SIS environments made cross-campus academic reporting, accreditation preparation, and student-record consolidation manual and error-prone.
  • Disconnected student services. Students used several portals for timetables, tuition billing, academic requests, and service interactions, increasing helpdesk workload.
  • Scheduling conflicts. Faculty working across multiple locations faced timetable overlaps and inefficient classroom allocation because resource planning was not centrally coordinated.
  • Delayed reporting. Academic and operational reports depended on batch exports, manual reconciliation, and inconsistent campus-level data models.
  • Legacy cost pressure. IT budget was increasingly consumed by maintenance work, limiting capacity for university digital transformation initiatives.
  • Access-control complexity. Faculty, students, administrative teams, and leadership required role-specific access to connected data without weakening governance.

The project required higher education software development experience across academic workflows, student services, legacy integrations, identity management, and phased rollout. It also required legacy system modernization for universities because the institution needed a new digital layer while keeping existing systems of record in place.

SOLUTION SUMMARY

Computools designed Uni-Campus as a phased integration layer for multi-campus university integration. The solution connected three SIS environments, LMS, ERP, IAM, analytics, and a central student portal through an API-driven architecture.

The core architecture supported API integration for higher education by exposing controlled data flows between campus systems, administrative platforms, and student-facing services. Existing SIS, LMS, ERP, and IAM platforms remained the systems of record.

A unified data hub normalized academic records, student profiles, course data, billing references, access roles, scheduling information, and service-request data. This created one operational foundation for reporting, portal workflows, and cross-campus visibility.

Computools delivered student portal development that gave students one access point for timetables, academic requests, billing visibility, and service interactions. The portal reduced navigation across separate systems and lowered repetitive helpdesk demand.

The integration scope included LMS ERP SIS integration with Canvas via LTI 1.3, SAP ERP, Microsoft Entra ID, and three legacy SIS environments. Role-based access controls and centralized governance supported the university’s UK GDPR and data-protection framework.

IMPACT

The phased rollout improved reporting speed, data availability, student-service efficiency, scheduling accuracy, and portal experience across the university group:

  • academic reporting preparation decreased from 8–10 business days to 3–4 business days;
  • routine requests requiring manual intervention decreased from 65% to 25% of total ticket volume;
  • cross-campus data synchronization improved from 24–48 hours to under five minutes;
  • cross-campus scheduling conflicts decreased from about 40 incidents per semester to fewer than five;
  • student portal satisfaction increased from 3.2/5.0 to 4.1/5.0.

The education data integration platform gave academic, administrative, and IT teams one governed view of student, course, schedule, billing, and access data. This reduced manual reconciliation, improved reporting reliability, and made student-service workflows easier to manage across campuses.

The unified data foundation also prepared the university for future AI development use cases, including student-service automation, academic analytics, and early-risk indicators.

WHY COMPUTOOLS

The client selected Computools because the project required legacy integration, academic data modeling, student-service UX, IAM alignment, API architecture, and phased rollout across three campuses.

Computools connected fragmented SIS, LMS, ERP, IAM, and student-service data into a practical operating model for reporting, portal workflows, access control, and cross-campus visibility.

Delivery priorities were tied to measurable KPIs: reporting preparation time, manual-intervention requests, data synchronization speed, scheduling conflicts, and student portal satisfaction.

The team covered business analysis, CX and UX design, architecture, integrations, QA automation, security alignment, rollout validation, and post-launch support.

Launch your software solution within 1-3 months instead of years. Unlock tomorrow. Build a future-ready business through innovation.

STORY IN DEPTH

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.

DESIGN

The design focused on student-service clarity, role-based access, cross-campus visibility, academic workflows, and administrative efficiency.

USER PERSONA → SITE MAP → WIREFRAMES → USER INTERFACE

USER PERSONA

Defining student-service needs, academic administration workflows, IT operations, faculty scheduling, and leadership reporting.

SITE MAP

Structuring the platform around student services, academic records, campus operations, data synchronization, and role-based reporting.

WIREFRAMES

Designing low-fidelity layouts for student dashboards, service-request flows, academic records, scheduling conflict views, data-sync monitoring, and leadership reporting.

USER INTERFACE

The interface gave students one access point for core academic services while giving staff controlled views of requests, records, schedules, and cross-campus data.

DIGITAL PLATFORM & TECHNOLOGY

Computools delivered web development for Uni-Campus, combining a central student portal, role-based staff workflows, integration monitoring, reporting dashboards, and secure access.

PROJECT MANAGEMENT METHODOLOGY

Computools used a phased delivery model with two-week iterations, stakeholder demos, and KPI-based acceptance criteria. Each sprint connected a platform capability to a measurable operational outcome: reporting preparation time, manual-intervention requests, synchronization speed, scheduling accuracy, or portal satisfaction.

The team started with current-state architecture assessment, integration mapping, and data-model consolidation. Portal workflows, reporting dashboards, synchronization logic, and IAM integration were introduced after data ownership and validation rules were agreed.

The rollout followed the academic calendar. Campus teams, IT stakeholders, student services, finance, and academic administration reviewed each release before broader deployment.

PROJECT MANAGEMENT METHODOLOGY

PROJECT TIMELINE

image

WHAT OUR CLIENT SAID

Uni-Campus gave us one consistent view of academic and student-service data without forcing us to replace the systems our campuses still depend on. Reporting became faster, students had a clearer digital entry point, and our IT team gained a safer path for modernization.

CONTACT US TO GET A COST-EFFECTIVE
PROJECT ESTIMATE

Thank you for your message!

Your request will be carefully researched by our experts. We will get in touch with you within one business day.

WHAT HAPPENS NEXT?

01.
We deeply analyse your request.
02.
We create project roadmap, accelerating your time-to-value.
03.
We co-scope features, minimizing project risk upfront.
04.
We submit a comprehensive project proposal with estimates, timelines, CVs, etc.
Trusted by: