Last update: October 26, 2018

OAMS

CWL login

The Project

OAMS was built for UBC on the foundation of CRM software. Software development is scheduled to continue until Spring 2014.

 

SITP Context and Vision

The OAMS Project is part of the Student Interaction Transformation Program (SITP), a group of projects and initiatives including Early Alert, Learning Plan, Broad-Based Admissions, and many others. SITP's vision aligns with the Student Learning component of UBC's Strategic Plan, and is:

We will transform our interactions with students to ensure they support, enhance, and facilitate a transformative student learning environment.  We will do this in partnership with and in service to students and faculties.

OAMS supports the SITP vision by helping advising units create a transformative learning environment.

 

OAMS Project Objectives

The OAMS Project is responsible for the following objectives:

Sustainability

Making OAMS more operationally supportable, scalable, and sustainable, by implementing technical upgrades recommended by UBC-IT Enterprise Architecture.

Student Success

Sharing

Enabling advisors to share information about students’ goals, challenges, and opportunities more efficiently within, and between, advising units .

Broad Support for UBC Advising Offices

Supporting a broader range of advising activities in UBC’s faculties, departments, and service units, through a redesign of OAMS workflows and user interface elements.

Efficiency

Increasing advisors’ ability to efficiently store and retrieve students’ advising information, through improvements to the OAMS user experience and associated business processes.

 

Key Software Development Areas

The OAMS Project is responsible to the university community through the OAMS Stakeholder Working Group (OAMS SWG). The OAMS SWG has identified four key development areas:

OAMS (Sugar CRM CE) Technical Upgrades

Note: OAMS is built on the foundation of SugarCRM software.

  • Moving customizations out of SugarCRM modules
  • Moving customizations out of SugarCRM framework, and building an initial series of unit tests
  • Replacing Talend middleware with a standardized UBC SIS integration

Vital Scalability and Usability Improvements

  • Functional improvements essential for the successful deployment of OAMS on a larger scale (i.e. beyond the four initial pilot groups).

Privacy and Access

  • Functional changes to support the new advising Privacy and Access model, so that advisors can more readily share information with others outside their advising unit.

Further Business Scalability and User Experience Improvements

  • Another set of functional improvements to improve OAMS’s usability, and its ability to support advising practices across the University.

 

Project Timeline