Text only

skip University | BUCS/MIS  | Registry | SAMIS  

-
Sulis head logo SAMIS - Student and Applicant Management Information System - Link to SAMIS index and log-in page University of Bath logo - link to University home page
 

Why SAMIS? - and what it covers

Some history - why we decided to change | What SAMIS covers

Some history - why we decided to change This is a non-current, archived file. Press here for more information.

The main change takes the University from a "student" system known as stusys or OES (Oracle Education System) to one we call SAMIS, the Student & Applicant Management Information System. The company which has developed this system is called Strategic Information Technology Services Limited, so the system is often referred to in other institutions as "SITS".

SAMIS is an "off-the-shelf" package for the University in most senses. We have to work out how to model some University processes and business within it, but most of all, it is a functioning system which continues to be developed by its owning company. Around forty other universities in the UK are SITS-users. This is a major contrast with stusys or OES, which was originally developed by Oracle in conjunction with twenty-four universities but had come to be used only in a very small number of institutions.

In 2000, it became clear that, to continue using stusys, the University would have to upgrade the database on which it ran, and that this would entail upgrading all of the screens of the system into a new software environment. Estimates of the time that this operation would take suggested that most of the staff resources available in BUCS/MIS would be fully occupied on it for at least six months. Moreover, beyond that, the University would still be left in an exposed position as one of the few users of the system, and would have to continue to support and develop it entirely in-house. Any changing external requirements (such as those of the Higher Education Funding Council for England (HEFCE) or of the Higher Education Statistics Agency (HESA)) might stretch our resources well beyond their capacity, and any internal developments we wanted to make might be very slow to be implemented.

The underlying database was reckoned to be fundamentally sound, and we had seen it used to great effect, most recently and most notably through the implementation of Registration On-Line. This proved a remarkable success at its first use in autumn 2000, with over 6,500 students using the facilities to enter/check/update their data. However, it was also clear that the resources available were insufficient to implement stusys as a common tool throughout the University as originally envisaged. The combination of needing to manage upgrades, of wanting to make steps forward in our processes, and of wanting to widen significantly the community of users, was judged to be too much.

The balance of the arguments, therefore, led to the conclusion that the University would do better to implement and work with an "off-the-shelf" package, accepting minimal if any customisation, such that it will be able to continue to develop in conjunction with its chosen software-supplier partner.

 

Top of page

What SAMIS covers This is a non-current, archived file. Press here for more information.

In this section, we describe in general terms what the SAMIS covers. At this stage, some of this naturally comes in terms of the project to implement SAMIS. We mention again the name of the system, and cover the scope of the system and of the project, and give a brief outline of the timescale for implementation.

The system and its name This is a non-current, archived file. Press here for more information.

The University has purchased a new "student" system. We are calling it SAMIS, which stands for Student & Applicant Management Information System. The supplying company is called Strategic Information Technology Services Limited, so this system is often referred to in other institutions as "SITS".

The scope of the system and of the project This is a non-current, archived file. Press here for more information.

SAMIS will take us all the way from enquiries and applications through to assessment and graduation.

We have split the project into four main strands of development. Each of these is autonomous to a certain extent, and work is progressing on all simultaneously.

Admissions: Work started on UCAS Admissions, which has now gone live, and is being used across the University. Some areas remain outstanding - particularly relating to Clearing and Confirmation in August 2002 which will be addressed closer to the time. Direct Admissions and Enquiry Management is currently in development. Future areas might cover prospectus management and on-line admission handling.

Scheme and Assessments: The "Scheme Definition" was one of the first areas looked at, and provides a structure within which the University's programmes and units can be modelled. The main aims in designing this have been to make it easy to report on, and easy to extend. The bulk of this work has now been completed, and the group working on this are now considering assessments. In SAMIS, assessment management is tied very closely to the way in which the scheme is defined, so this is a direct progression.

Student Lifecycle: This covers the day-to-day management of student records, starting with registration, going through changes of circumstances, to end-of-year progression (though this area will be covered more and more by the assessments group mentioned previously). It also covers statutory returns such as HESA and HESES. One of the larger areas covered here is widespread interaction with SAMIS via the web, for both students and staff.

Student Finance: Student Finance starts with the allocation and generation of fees for all students held in SAMIS, and goes through invoicing to fee collection, debt management, and reconciliation. It also covers predicting tuition fee income, and communication with the Student Loans Company. Further areas might cover grant- and loan-tracking, and sponsorship & bursary management.

The aim is to implant SAMIS much more widely within the University than has been possible with the previous system, stusys. We always planned to have many more people use stusys, and through Registration On-Line we were very successful in getting thousands of student users to enter/check/update their own data in the system. There was also wide staff use of the web-based Student Enquiry Screen. However, much more distributed use of the system is planned in the SAMIS context.

The timescale for implementation This is a non-current, archived file. Press here for more information.

The outline plan envisaged having undergraduate admissions in operation for Autumn 2001, and this has already been achieved. Other student data was to be migrated into the new system around March 2002, such that the 2001/02 academic year would start in the existing system, stusys, and finish in SAMIS. Registration 2002 was planned to be done completely in SAMIS. Details of the progress made can be found in the news archive section of this site.

Top of page

SAMIS index and log-in page | SAMIS Info/Help

-

 University | BUCS/MIS  | Registry | SAMIS