Connected software for higher education
Bring admissions, academics, finance and administration together, with software built around the way your institution already works.
In use at Management Development Institute, Gurgaon since 1999–2000. See the evidence.
Institutions and evidence
Institutions we work with include
- Indian Institute of Management Calcutta
- Indian Institute of Management Visakhapatnam
- Indian Institute of Management Jammu
- Indian Institute of Management Shillong
- Indian Institute of Management Nagpur
- Indian Institute of Management Tiruchirappalli
- Indian Institute of Management Sirmaur
- Management Development Institute, Gurgaon
- International Management Institute, New Delhi
- International Management Institute, Bhubaneswar
- Babasaheb Bhimrao Ambedkar University, Lucknow
- Lal Bahadur Shastri Institute of Management, Delhi
- PML SD Business School, Chandigarh
- Jaipuria Institute of Management
Choose the area you are responsible for
Each area can be taken on its own or with the others. Which modules are included in a deployment is set out in the proposal for that institution.
Admissions
Run an admission cycle from the first application to the last waitlist offer, on a form your own office designs.
Who it serves: Admissions chairs and committees, The admissions office, Programme coordinators, Applicants.
Key capabilities
- Form builder
- Applicant portal
- Online fee payment
- Scoring and selection stages
- Interviews
- Merit lists and seats
Academics and student administration
One student record from registration to transcript, covering courses, attendance, assessment, grading and attainment reporting.
Who it serves: Registrars, Deans of Academics, Controllers of Examinations, Programme offices.
Key capabilities
- Student records
- Courses and sections
- Timetable and calendar
- Attendance
- Electives
- Assessment and marks
Fees and finance
Fee collection that posts to a double-entry ledger, so the fee register and the accounts are the same numbers.
Who it serves: Finance officers and bursars, Accounts sections, Fee counters, Students and parents.
Key capabilities
- Fee structures
- Fee collection
- Late fees and reminders
- Fee reports
- General ledger
- Posting control
HR and payroll
Employee records, leave and payroll for teaching and non-teaching staff, working from the same attendance data.
Who it serves: HR and establishment sections, Accounts sections, Heads of department, Faculty and staff.
Key capabilities
- Employee records
- Leave
- Staff attendance
- Payroll
Institutional operations
The services around the classroom: stores, hostel and mess, transport, complaints and correspondence.
Who it serves: Administrative officers, Stores and purchase sections, Hostel wardens, Estate and maintenance teams.
Key capabilities
- Stores and inventory
- Hostel and mess
- Transport
- Complaints
- Grievance redressal
- Dispatch
Placement and corporate relations
Placement administration and executive education, including the corporate clients who nominate and pay for participants.
Who it serves: Placement offices, Corporate relations teams, Deans and chairs of executive education, Programme offices.
Key capabilities
- Placement portal
- Summer internships
- Programme catalogue
- Registration and payment
- Sponsor nominations
- Delivery
Start from what you answer for
The same software looks different depending on which office you run. Each page gathers the solutions, evidence and questions relevant to that role.
One system at MDI Gurgaon since 1999–2000
Admissions, timetable and attendance, marks and relative grading, elective selection, stores, HR and leave, complaints and placement — twelve functions in all, used by faculty, students and the programme office, with records of approximately 10,000 students.
As stated in MDI's letter of 26 February 2016.
We are satisfied with the operation of OLT Campus software & Support / Services provided by the company.
Read the case study
The software is the smaller part of the work
Campus projects rarely fail on features. They fail on migration that was underestimated, integrations nobody scoped, and training given once to everybody. Implementation is planned in eight stages, and you can prepare for the first conversation with a printable migration checklist.
Discovery and configuration
Your regulations, structures and workflows are established, and the modules set up to match.
Migration and integration
Existing records are brought across from agreed sources, and connections to other systems are set up.
Testing and training
Each department checks its own processes and is trained on the modules it will use.
Go-live and support
The system goes into use, with support under the terms of your agreement.
Asked before a demonstration
Do we have to take every module?
No. Institutions take the modules that address their current problem and add others later. Which modules are included is set out in your proposal; nothing on this site should be read as meaning every module is part of every deployment.
What does the software cover?
Admissions; academics and student administration, including electives, examinations, grading and transcripts; fees and finance; HR and payroll; institutional operations such as stores, hostel and transport; and placement and executive education. Each area is described on its own solution page.
What happens to our existing data?
Migration is scoped with you during discovery: which records come across, from which sources, and from what cut-off date. Student, course and faculty data can be imported from spreadsheets. We do not commit to a migration scope before we have seen the source data. The migration checklist helps you prepare.
Is it hosted, or installed on our own servers?
Both models exist. Institutions can use a hosted service in which each institution's data is kept separate from every other institution's, or a standalone deployment for a single institution. The right model depends on your procurement route and your data policy, and is agreed in the proposal.
Can several institutions in a group run on one platform?
Yes. The hosted applications are built to serve multiple institutions, each with its own configuration, users and data.
What happens after we request a demonstration?
We reply to arrange a time, and ask which offices and workflows matter most so the demonstration covers those. You do not need to prepare anything. If you have used the requirements builder, you can attach its summary to the request.
What does it cost?
It depends on the number of students or participants, the modules you take and the deployment model. Tell us those three and we will give you a figure.
See it with your own workflow
Tell us which offices are under the most pressure and the demonstration will cover those. Or set out your requirements first.