Skip to main content
ExLibris Dev

Overview of campusM

campusM has been implemented by a third of all Universities in the UK, with further installations in Europe, USA, Australia and South Africa, with a growing global base. campusM is provided by the Mobile Campus Solutions Business Unit of Ex Libris.
campusM is a powerful mobile app solution designed to give students personalized access to University services and information. Using the app, students have access to a range of standard services including their timetable, email and calendar, Library account and resources, Learning Management System (LMS) resources and elements of their Student Records such as grades. Other services can also be incorporated into the app to bring value to the overall app experience. The services are accessed via menu options, or tiles, as can be seen from the screenshot on the right.
The app is designed for maximum flexibility to capture whatever services and information the University wants to provide, based on their current available data and services.
The mobile app is available as an app store download for Apple and Android products. To ensure that the solution is fully inclusive for those users who do not have access to a smart device, the campusM product includes a responsive web app that is desktop and mobile ready. The web app can be used as a student portal, to replace the more traditional in-house web-only systems utilized in the past.
Web app screenshot
campusM web app screenshot
A campusM implementation aims to produce a customized and seamless app for students offering access to a number of integrated services and static information resources.
campusM Implementation Flow
campusM Implementation Flow
Phase 1 of the project, Getting Started, commences with the kickoff meeting to identify key stakeholders and roles; review all project stages, roles and responsibilities; identify key milestones and agree a date for the Discovery Workshop (see Appendix 1).
The Design phase, Phase 2, is about defining what will be delivered and setting out how the platform will be integrated and implemented.
In Phase 3 of the project, the Build phase, the campusM Connect layer is configured and the integrations are built. During this phase, the authentication methods, permissions, roles and profiles are implemented, along with branding, maps and locations and static content. Administration training is carried out concurrently throughout this phase of the project to enable the institution to configure their elements for the app and for ongoing administration.
Phase 4 of the project, Deploy, hands the app over to the customers and ends after implementation project handover and sign-off, with the platform fully operational.
This guide is intended to support the administration training during this phase and provide a comprehensive set of support documents for the ongoing development, configuration and daily administration of the product.
The guide commences with a discussion of the key concepts that underpin a thorough understanding of the product followed by a detailed description of the administrative tools within the product. Although the guide works through each section in order, there are some functions that are managed in more than one area of App Manager and are treated as a section in their own right.
  • Was this article helpful?
// feedback widged