| Monash home | About Monash | Faculties | Campuses | Contact Monash |
| Staff directory | A-Z index | Site map |
|
|
Quality Assurance in Off Campus Learning and Open Learning Programs PolicyPlease note that this policy has not yet been revised or converted to the new format. This policy area is being re-formulated into the new Academic Policy Bank format. The following is the original Policy and Procedures for Quality Assurance in Distance Education and Open Learning Programs approved by Academic Board at its meeting 3/1997. Contents
1. IntroductionThe delivery of programs in off campus learning or open learning mode is a more complex activity than on-campus delivery. It requires the integration of a large number of separate activities, responsibility for which rests with various academic and administrative units within the University. As one of Australia's leading providers of off campus learning and open learning programs, Monash University is committed to maintaining high standards of quality in the content and pedagogy of these programs as well as in learning support and administrative support for students undertaking them. This requires the existence of an appropriate University-wide policy framework, together with a commitment, by each of the organisational units involved, to quality assurance in all of the services it provides to the University's off campus learning and open learning programs. In 1996, the Distance Education and Open Learning Committee established a Quality Assurance Working Party to bring together information about the quality assurance criteria and monitoring procedures being followed by all relevant units of the University. The Committee agreed that this information should be presented in conjunction with an outline of the policy framework within which off campus learning and open learning currently operate in Monash University. This report is the outcome of the work of the Quality Assurance Working Party. The cooperation of the organisational units concerned is gratefully acknowledged. In presenting the report, the Working Party wishes to stress that its work should be regarded only the beginning of an ongoing process. Important matters such as policy and processes for benchmarking and quality improvement (as distinct from quality assurance), and for auditing of quality assurance procedures have yet to be considered and documented. These should be a priority for the Committee in 1997. Quality Assurance Working Party M. Crowley
2. Policy Framework and Objectives for Quality Assurance in Off Campus Learning and Open Learning2.1 PreambleThe University's Off Campus Learning (OCL) programs currently involve 7500 students (3200 EFTSU) in 70 award courses. In addition, some 6000 students (1400 EFTSU) (December 1995 data) annually are undertaking Open Learning (OL) studies through Monash University. Given the more limited opportunities for OCL and OL students to communicate with staff and fellow students, compared to their on-campus counterparts, it is vitally important that a high level of quality assurance is ensured by the University in all aspects of OCL and OL programs. Quality assurance is becoming even more important as off campus learning and open learning enter a period of major change. As Sir John Daniel, Vice-Chancellor of the UK Open University (UKOU) expresses it "All institutions offering any form of distance education now face a further wave of technological change. The coming together of telecommunications, television and computing is producing a media environment for distance education that is more than the sum of its component elements." For a university such as Monash there are substantial opportunities for the use of this new media environment to enhance both the quality of learning within its programs and the ease of access to these programs from around the world. At the same time the University must recognise and accept the challenges which accompany the new technological and educational tools available to it. In the words of Georges Van der Perre, President of EuroPACE 2000, a consortium of 45 universities together with private and public companies and organisations, "Whether the academic world will succeed in realising the potential of these tools will not depend on technological conditions in the first place: technology is available and access to it is growing spectacularly (eg Internet). Key success factors are the development of effective pedagogic models for integrated utilisation of technology tools in mainstream education, and effective networking on a local as well as a European scale." Monash University must meet these challenges if it is to compete successfully with organisations such as EuroPACE and the UKOU. The role of the Off Campus Learning and Open Learning Committee is to guide and facilitate the development within Monash of effective pedagogical models and the integration of new technologies into mainstream education. Quality assurance policies and procedures are critical to the success of this process. This paper summarises the policy framework within which quality assurance procedures for OCL and OL programs operate. It also lists key quality assurance objectives arising from this policy framework. A series of complementary papers will detail the quality assurance criteria and monitoring procedures applicable to each of the academic units and academic support units involved in the development and delivery of Off Campus Learning and Open Learning programs for the University. 2.2 Framework for Quality Assurance in Off Campus Learning and Open Learning2.2.1 The University's responsibility"When teaching programs are conducted without regular face-to-face contact between academic staff and students, effectiveness depends on the provision of properly designed and appropriate alternative technologies, and/or distance education methodologies, resources and support services, under appropriate academic direction." Education Policy, Section 1.2, para 1 2.2.2 Operational Responsibility2.2.2.1 Off Campus Learning"The Centre for Learning and Teaching Support has responsibility for the operational side of distance education within Monash University, and should have clearly developed and recorded policies for these operational arrangements. (Policies relating to distance course approval and development, study materials preparation and supplementary tuition were developed in 1990 and approved by the then Distance Education Advisory Committee but have never been presented to Academic Board.) These responsibilities include:
To the extent that an arrangement is made whereby the teaching unit, or a third party, undertakes any of these responsibilities for a unit or course in place of CeLTS, CeLTS has responsibilities for ensuring that these arrangements are adequate, and for monitoring their implementation for quality." Distance Education Policy, p2, para 1 2.2.2.2 Open Learning"For the purposes of this policy, the offering of undergraduate or graduate units or courses by a teaching unit through Open Learning is subject to substantially the same conditions and arrangements as for that teaching unit offering such units or courses through off campus learning at Monash University. In particular this includes the role of CeLTS, and the need for a teaching unit tendering for, or providing, units or courses to consult with CeLTS and to meet the requirements for the provision of off campus learning units laid down in this policy and by CeLTS." Distance Education Policy, p5, section (iii), paras 1 and 2 "The production quality of study materials will be that considered acceptable for standard distance education materials provided by Australian Distance Education Centres". OLAA Agreement on Offering Higher Education Units, Clause 27 2.2.3 Responsibilities of Teaching Units2.2.3.1 Teaching and Learning Support"1.3.4 The appointment of Associate Deans (Teaching) to take responsibility for the enhancement of teaching and Learning in their faculties. These Associate Deans will liaise with the Professional Development Centre and, where appropriate, the Monash Centre for Learning and Teaching Support, on a formal and regular basis, and will have responsibility for establishing faculty staff development programs focused on teaching. They will meet regularly with the Deputy Vice-Chancellor responsible for Academic Projects.' Education Policy, para 1.3.4 2.2.3.2 Quality of content in Open Learning, Units"The content of study materials will be that considered acceptable for standard distance education materials in the relevant subject area provided by Australian Distance Education Centres." OLAA Agreement on Offering Higher Education Units, Clause 25 2.2.3.3 Quality of content in Off Campus Learning programs"Course and subject content is solely the responsibility of the teaching unit concerned...." Distance Education Policy, p.2 para 4 2.2.4 Responsibilities shared between Teaching Units and CeLTS"The particular aspects of development for which CeLTS has responsibility are those aspects of course and instructional design whereby the content, and requirements of the courses and any skills to be developed within the course, can be made accessible to students through the distance mode of learning. Course and subject content is solely the responsibility of the teaching unit concerned; effective teaching and learning (as defined in the University's Education Policy) is a shared responsibility of the teaching unit and CeLTS." Distance Education Policy, p2, para 4 "The instructional design of study materials will be that considered acceptable for standard distance education materials provided by Australian Distance Education Centres." OLAA Agreement on Offering Higher Education Units, Clause 26 2.3 Objectives for the Quality Assurance in Off Campus Learning and Open Learning2.3.1 Objectives for the University
2.3.2 Objectives for the Centre for Learning and Teaching Support
2.3.3 Objectives for Faculties
2.3.4 Objectives for Teaching Units2.3.4.1 Content
2.3.4.2 Academic Support
2.3.4.3 Assessment and Marking
2.3.4.4 Administrative functions
2.3.4.5 Liaison
2.4 References1. Daniel, JAS., "The Mega-Universities and the Knowledge Media: Implications of new technologies for large distance teaching universities", Thesis for the Degree of MA (Educational Technology), Concordia University, Montreal, Quebec, Canada, November 1995, p 11. 2. Van der Perre, Georges, "A virtual university for Europe'" Abstracts, Online Educa Berlin: International Conference on Distance Education, Berlin, Germany, November 24-25, 1995, p36.
3. Monash University Centre for Learning and Teaching Support: Services, Quality Assurance Criteria and Monitoring Procedures
4. Services provided by Teaching Units for Off Campus Learning and Open Learning Programs
5. Monash University Library: Quality Assurance for Off-Campus Library Services
6. Student Records and Admissions Branch: Services to the Centre for Learning and Teaching Support
|
||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Service | Quality Criterion | Monitoring Procedure |
|
1. Applications |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
2. New Students |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
3. Current Students |
||
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
4. Database Management |
||
|
|
|
|
|
|
|
|
|
| Service Provided | Performance Indicator/s | Monitoring mechanism/remedial action |
|
1. Timetabling |
||
| Timetabling of examinations for OLAA and OCL students in order to produce few if any clashes, minimal proximities of examinations for individual students, and provide adequate time for both student revision and for assessment | Number of individual clashes and proximities.
Length of 'swot vac.' Number of days between last day of examinations and deadline for submission of results by examiners. |
Feedback from clients.
Publication of relevant performance indicators with the examination timetable. Information sessions/meetings with student representatives and academic and general staff. |
| The timetabling process should also seek to accommodate special timetabling requests from examiners where possible. | Numbers of special timetabling requests received and met.
Numbers of complaints as a percentage of the number of students timetabled. |
Comparison of performance indicator data with previous examination periods to determine, measure, and explain improvement or otherwise. |
|
2. Examination Papers |
||
| Advice to subject advisers on examination paper preparation so that quality papers are provided to candidates. | Advice/instructions are communicated in written format in a timely and suitable medium.
Number of errors. Uniformity of format. |
Papers are proofread by departments and cross-checked against timetabling data. Errors corrected by departments prior to printing wherever possible.
Examinations staff to maintain data on errors and report to CeLTS and Heads of Departments. |
|
3. Venues |
||
| The provision across Australia and internationally of examination venues that enable candidates to perform optimally | Candidates should not have so far to travel to a venue that they are unable to perform optimally.
Numbers of complaints about travel, lighting, noise, signage, ventilation, and furniture |
Reasonable travel distance policy formulated/revised in consultation with CeLTS, Monash International, student bodies, etc.
Investigation of alternative modes of delivery of examination papers, eg can the Internet be used? Examinations staff to investigate and resolve problems with venue ventilation, noise, etc. |
|
4. Invigilators |
||
| The provision across Australia and internationally of invigilators who implement well-publicised procedures designed to deter and detect cheating but do not do so in a way that would impact unreasonably on a candidate's performance. | The instructions for invigilators and candidates are documented and communicated in a timely and appropriate medium.
Number of incidences of cheating detected each examination period. Numbers of complaints about invigilators. |
Examinations staff to investigate alleged cheating. Discipline Statute may have to be invoked.
Examinations staff to investigate complaints about invigilators. |
|
5. Communicating Information |
||
| The provision of timely, complete, and accurate examination information to OLAA and OCL students. | Number of times candidates sent variations to original information.
Number of complaints from candidates and exam centres/invigilators about inadequate, incorrect, and/or late information. |
Examinations staff to investigate using new technologies such as IVR and the Internet to disseminate information in a more timely manner.
Examinations staff to maintain data on errors necessitating communicating to candidates variations to information previously sent. |
|
6. Disabled Students |
||
| In conjunction with academic departments and the Disability Liaison Office, organise and conduct examinations for those candidates requiring alternative arrangements for assessment in accord with the University's equity policies. | Number of complaints from disabled students and/or the DLO about discrimination and/or poor service in relation to examinations conducted by the Branch. | Examinations staff to meet regularly with DLO, CeLTS, and academic departmental staff to monitor and review assessment practices in relation to disabled students. |
A&MIS will provide software and programming support to distance education and open learning operations as commensurate with the objective of providing timely quality teaching services. Service and quality objectives may be assumed to embrace high standards of efficiency and effectiveness (ie quality), and it may also be assumed that modern database management techniques and standards will be employed. (Note. Provision of the actual physical resources is a responsibility of the Computer Centre.)
Special Note. The General Manager has recently directed that development "work that could not demonstrably produce saving is not to be entertained".
Design scope and factors negotiated between primary client and AMIS, test procedures devised and agreed upon, and priorities and schedules determined. Pre-implementation test procedures will normally involve both parties and secondary users.
Monitoring will include overall system availability, stability and response times - particularly during key periods - and disk space availability and allocations. This will not normally involve users but agreed procedures for reporting of anomalies and malfunctions by the primary client is (to be) a key element of the monitoring processes.
An electronic job lodging and logging, and automatic acknowledgement system exists for initial recording, and progress reporting of routine job requests and malfunctions alike. (Although this has been virtually only used for the main student system to date, it has recently been decided to extend the facility to all systems and clients will be notified shortly.) Emergencies although still to be logged in the system, will be considered immediately upon receipt of a phone request from the primary client. Pre-emptive priority will be given to keeping systems running and programming resources will be dedicated to emergency matters until resolved. Normally this will be a matter of hours, rather than days, and any downtime will be included in system performance evaluation processes.
Determination of priorities for allocation of resources to problem resolution in the event of competing emergency demands will have regard to factors such as the number of customers affected and the nature of the problems - that is, the magnitude of the problems and implications of errors or down-time including costs to the wider University as well as to the immediate users. (It may be feasible to prioritise systems, but a particular problem in a low priority system may have more significant service implications than a higher priority system at times so some flexibility is appropriate.)
In essence, any developments embrace a further pass through the design and testing phase. However, any specific proposals which are proposed or in train for a particular service can be included under this heading. It perhaps also needs to be appreciated that detailed blueprints do not exist for design, maintenance and problem resolution in relation to the various systems, and that although there are traditional accepted practices, future development should include full documentation of service provisions and support procedures.
Note. As This is very much a first draft, some services or systems components may nor appear at all, or could be presented in a different/better manner, and no effort has been made to collect and development items currently being dreamed about or actively worked on. Perhaps more intensive examination of the various services will reduce the extensive use of "Standard" clauses, or result in additional comments being appended to some entries.
| Service Purpose and Quality Objective | Monitoring Processes |
| COURSE INQUIRIES CENTRE SYSTEM (OCL only)
Primary Client: Distance Education Centre (CeLTS) Objective. To provide and maintain an efficient and effective on-line marketing database for the recording and analysis of OCL enquiries - such database to be capable of producing mailing labels and mailing address data files according to on-line customer definition. |
Design & Testing. Standard.
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development. Provision for access to self-defining reports and statistical analyses facilities to be extended to faculties. (Ready but not released.) |
| STUDENT DATA SYSTEM (OCL,OL & Gippsland Campus)
Primary Client: Student Admissions and Records Branch Objective: To provide and support a comprehensive student system for the recording of applications, production of offer letters etc, and the management of student enrolments and fee payments. Note: Although system modules, components and functions may be handled within MUFIN and MUSIS in the future, the need for the OCL/OL services will remain and must feature in the University's unified corporate systems. |
Design and Testing. Standard
Performance Evaluation and Maintenance. Standard. Problem response and Resolution. Standard. Continuing and Future Development. System is to be interfaced with MUFIN in the short term, and much of it incorporated within MUSIS in the medium term. Therefore only essential development is being performed. System changes are made for DEETYA at least annually. |
Primary Client: SARB Objective: To provide for recording and coding of applications for admission. Includes provision for separately identifying applications by student category (local OCL, offshore courses, OL etc) and semester or other study period. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard. Problem Response and Resolution. Standard. Continuing and Future Development There is an applicants module within MUSIS which is being evaluated for adoption for OCL/OL use. Handling of multiple applications is a feature of the MUSIS system and such facility is increasingly becoming necessary. |
Primary Client: SARB Objective: To produce multiple page offer letters and duplicates etc automatically in overnight computer runs. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development . Production methods and quality of presentation require continuous review and improvements to help encourage applicants whom lodge multiple applications with a number of universities to choose a Monash course. |
Primary Client: SARB Objective To rapidly load OL registrations received from OLA in accordance with contract specifications. Registrations are FTP'd (electronically transferred) to the Gippsland campus but need to be loaded into the student system - and matched with any previous records for the students. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development.None other than that a different target computer may need to be determined for the FTP files. |
Primary Client: SARB Objective: To capture and store photo-images created directly from students standing in front of a camera connected to a PC, in person, or via an image captured (scanned) from a passport size photo supplied by students through the mail. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development. At the present time the Gippsland cards are different from those of other campuses in that they bear a second barcode from microlab access. Efforts are being made within the University to do away with the need for the second barcode, and to use a single system only when SDS and MUSIS are merged. |
Primary Client: SARB (for Budget and Statistics Branch) Objective: To record all fee payments and HECS calculations in coded form, capable of analysis by transaction type and for accounting/bank reconciliation and budget distribution purposes. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development. Changes for 1997 have been made. Adoption for MUFIN. |
Primary Client: SARB Objective: To provide an application and file location and tracking system for Student Admissions and Records Branch (Gippsland) from the time. The use of barcodes and wands makes this a facile method of file movement control - assisted by the ability to produce reports of non-returned files, or other analyses such as average return time. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development Although extremely useful, this system does not readily lend itself to integration into MUSIS. The facility is to be extended to include movement within Schools at Gippsland, and faculties saw a wider value in it, this would make it a more attractive proposition for inclusion. |
Primary Client: SARB Objective: To provide computer programs for processing assessments and producing result notices for students. Note: Data for notices of intent to exclude, commendation, probation etc for are produced relatively automatically at the same time for Word merge letters. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development Nil |
Primary Client: SARB Objective: To provide facility for overlay printing of personalised re-enrolment forms. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development Nil |
Objective: To provide facility for overlay printing of personalised graduation application forms |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development Nil |
Primary Client: SARB (for Budget and Statistics Branch) Objective: To provide timely statistical data for internal enrolment monitoring and budget purposes and to satisfy DEETYA requirements. Note: DEETYA requirements include Austudy/BENCON reporting. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development Provision for DEETYA changes for 1997 has been made. Statistical reporting will be a function of the single corporate database from 1998. |
Primary Client: Various: SARB, CeLTS, Schools & Depts. Objective: To provide a suite of standard reports for the line printer plus an array of screen-based reports which can also be directed to a local slave/network printer. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development Minor |
Primary Client: SARB Objective: To provide programs for producing lists of students whose (paper) files are to be culled for archiving purposes. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development Computer record management review. (Question is whether culled records should be held in a separate database as in the past years, or be held in a single database as is the case on the Alpha4). |
Primary Client:: SARB Objective: To program and produce timely personalised payment advice/request notices for appropriate student enrolment categories. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development Minor. (Will possibly be a MUFIN function from 1998, but most likely not for 1997 even though MUFIN will be introduced early in the year. Fine detail of the MUFIN, SDS, and MUSIS relationships is not yet known to the author). |
Primary Client: SARB?? Objective: Unspecified for time being. Note: Not sure of current practice, or planned post MUFIN practice. |
Design & Testing.??
Performance Evaluation and Maintenance. ?? Problem Response and Resolution. ?? Continuing and Future Development?? |
Primary Client: SARB To program and produce timely personalised HECS Liability Notices to all enrolled students. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development Minor. Will be handled by corporate systems for 1998. |
- Change of Assessment - Change of Study Program Primary Client: SARB Objective: To program and produce timely personalised change letters and duplicates to students. (Duplicates include information on area/persons performing the updates. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. This is a complex matter and problems do arise. Continuing and future Development. Minor |
(& uncertified course records) Primary client: SARB Objective: To provide batch and individual records program facilities for producing course records, and formal certified statements of academic record. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development To include majors? Note: Automatic production of transcripts is anticipated to be a feature of MUSIS by the time records are merged. |
| EXAMINATIONS DATABASE (all students)
Primary Client: SARB Objective: To provide an examinations system which draws data from the SDS and enables registration forms to be produced for all (relevant) students plus management of despatch of question papers, candidates rolls etc to over 200 examination centres within Australia and overseas. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development Minor. Additional functionality will, however, need to be incorporated within MUSIS (or alternative process/separate module agreed upon) for 1998 once systems are integrated |
| ASSIGNMENT TRACKING SYSTEM (OCL & OL only)
Primary Client: CeLTS Objective. To provide a facility for assignment movements to and from students to be recorded. (students are mailed cover sheets with barcodes at some point of time: details are wanded when assignments are received). |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. Continuing and Future Development Minimal, however CeLTS is experimenting with electronic assignment submission (already used in some form by one Gippsland School). This system will presumably need to be interfaced with MUSIS for 1998. |
| DESPATCH SYSTEM (OCL and OL Study Materials)
Objective: To provide a facility for despatch of study materials and other information to students. The system includes batch and packing control provisions and considerable print output from the Alpha4 is involved. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard Problem Response and Resolution. Standard. It should be appreciated, however that this is an extremely complex system involving at least 22 despatch events and as many catchup events (eg for students who enrol after the first batch of study materials for a particular subject has been despatched). It is a high volume ongoing user-interactive system and problems do occur. Continuing and future Development. Will most likely need to be retained as a separate system and interfaced with MUSIS for 1998. Data transfers would be one-way only. |
| PRODUCTION ADMIN SYSTEM (OCL & OL at Least)
This is a new system which has not yet been signed off to A&MIS to maintain. |
Design & Testing. Not completed but at least one phase is in operational trial mode
Performance Evaluation and Maintenance. Not an AMIS responsibility so far. Problem Response and Resolution. Not AMIS. Continuing and Future Development Unknown to Author |
| PRODUCTION ADMIN SYSTEM OCL and OL at least)
This is a new system which has not yet been signed off to A&MIS to maintain. |
Design & Testing. Not completed but at least one phase is in operational trial mode
Performance Evaluation and Maintenance. Not an AMIS responsibility so far. Problem Response and Resolution. Not AMIS. Continuing and Future Development Unknown to Author. |
| GRADUATION SYSTEM
Primary Client: Campus Academic Services Objective To provide facilities for recording of graduates and management of ceremonial attendance processes, including extraction of data (in electronic form) for production of testamurs at Clayton Campus. |
Design & Testing. Standard
Performance Evaluation and Maintenance. Standard. Problem Response and Resolution. Standard Continuing and Future Development Has been prepared to interface with MUSIS if need be (as the functionality is not currently incorporated within MUSIS). |
Notes: (Some of which have since been references within the table).
1. Excluded Processes
Processes which do not involve distance education or open learning have not been included: eg routines relating to VTAC selection, offer and enrolment processes, and recruitment of on-campus international students.
2. Other Exclusions
Some aspects of VCE Enhancement Studies enrolments require additional attention but this has bot been detailed as it was not specifically referenced in the brief. Generally speaking, the differences would be more a matter for the Student Admissions and Records Branch and Monash Centre for Learning and Teaching Support to be concerned with in any event, than A&MIS. Offshore course offerings also entail variations to the basis system, particularly to encompass different teaching time-frames, but these are not separately detailed either. Facilities which allow SARB (G) to invoke programs for individual or batch recovery of letters which have not been produced or are unusable for some reason, or data needs to be corrected, are not mentioned within service entries.
Note: Inclusion of scheduling information has not been considered as yet, but much of this information can be obtained from the OCL processes calendar produced separately by the Student Systems Monitoring Group (SSMG) at Gippsland, and currently being updated.
3. Monitoring
To assist in ensuring that monitoring processes are efficient and effective, A&MIS accepts job requests from clients in electronic form and maintains an electronic database of such requests for job control and progress advice purposes.
4. Systems Integration
Many of the processes will be components of an integrated University student system as from the beginning of the next distance education enrolment period, say from August 1997. Some processes may be affected by the introduction of an integrated Finance system, MUFIN, before then. These could include production of debtor notices, payments and refunds processing and reconciliation. In both instances, the methods of monitoring processes and managing/prioritising jobs could change as integration occurs, and involve different lead and response times for various processes although the net outcome may be much the same overall.
5. Future Developments
If the (Gippsland) Student Data System were to continue, items such as facility for directing electronic notices to e-mail addresses or fax numbers, in preference to producing and mailing paper notices would have been considered for introduction from 1998. Similarly, it is becoming feasible to not only accept re-enrolment via IVR or electronic forms, but to extend this to direct applications (notwithstanding the need for certifying of documents). Regardless of what the eventual structure of the corporate student system is, these sorts of things have considerable value for improving services to applicants and students, and in containing costs to the University, and probably still deserve attention during 1997 if Monash is not to fall behind. We believe that the electronic enrolment details two-way data exchange arrangements for offshore course agents/partners will be a first once implemented. Program will be tested shortly.
6. Clients
Although not specified for each service item, the primary client in most cases is SARB(G) of CeLTS. Future versions of this document will include the primary client before the "Objective" for each service.
(Bruce Bremner)
Co-ordinator, Systems Integration and Projects
A&MIS (Gippsland)
14 October 1996
Note:
1. This document reflects the arrangements in place until the end of 1996. Changes in services are anticipated in 1997.
2. Many services normally operate 24 hours a day. Support for services is normally only provided during business hours. As on-call arrangement with the Centre's technical support staff operates after hours and weekends for first level support during published times. Normally vendors will only respond to calls on the next business day.
| Service | Quality Criterion | Monitoring Procedure |
|
||
| a) Provide reliable wide area links of sufficient capacity for acceptable performance of normal higher level services | a) The operation of wide area links, in the delivery of higher level services, remain unnoticed by users of the links. | a) Wide area links are monitored by SPECTRUM (a network monitoring tool) and alarm messages are sent to the Helpdesk and network administrators immediately performance thresholds are reached or problems occur.
Note: Each wide area link is backed up by a slower ISDN link which takes over if the main link fails. |
| b) Install local area links to campus buildings of sufficient capacity for acceptable performance
Note: The Centre will assist faculties and departments if difficulties arise in the operation and/or management of that part of the network which is their responsibility |
b) The operation of local area links, in the delivery of higher level services, remain unnoticed by users of the links. | b) Local area links are monitored by SPECTRUM and alarms are sent to the Helpdesk and network administrators immediately performance thresholds are reached and problems occur. |
|
||
| The provision of remote access services is currently under review. Until policy directions are established by the yet to be formed IT Policy and Advisory Committee, criteria cannot be agreed | ||
|
||
| a) Email Services. | ||
| i) Provide a reliable, secure, scalable and flexible email system | i) Email can reliably be sent and delivered within Monash in an acceptable time frame.
Note: Email addressed outside of Monash will be promptly sent. Email received from outside will be promptly delivered. No criteria can be set for the delivery of mail when it leaves the Monash domain. |
i) Monitored by the Computer Centre through its automated service monitoring tools and CeLTS. Bi-annual staff and student survey. |
| 3. Internet Services (continued) | ||
| b) WWW Services
In cooperation with our partners, provide, i) a reliable and secure WWW server to host the University's official home pages. ii) a reliable and secure WWW proxy service of sufficient capacity and performance to provide good response consistent with minimising Internet traffic costs. iii) Publish monthly and quarterly reports on Internet usage and associated charges. |
i) & ii) WWW pages and files stored on the server and proxy can be retrieved in an appropriate time for the type of information being sought. iii) Reports to be published on Computer Centre's home pages monthly and quarterly. |
i),ii) Monitored by the Computer Centre through its automated service monitoring tools and CeLTS. iii) Monitored by the Computer Centre and CeLTS. |
|
||
| a) Software
i) Establish the core set of licensed application software to be provided on it's file servers. ii) Provide a mechanism for faculty staff to install licensed software belonging to the faculty onto centrally managed file servers. |
i) Consult with departments on licensed software to be provided on centrally managed servers in September each year. List is published in October each year. ii) Mechanism is published on the Computer Centre's home pages. |
i) Monitored by the Computer Centre and CeLTS. ii) Monitored by the Computer Centre and CeLTS. |
| b) Printing
i) Provide a reliable, chargeable laser quality printing service for students using the Centre's labs and host systems. |
i) Feedback from students is positive. |
i) Enquiries answered on the Helpdesk related to printing. computer Centre to conduct bi-annual survey of staff and students. |
| c) File Servers | ||
| i) Provide reliable centrally managed file servers of sufficient capacity to give good response times for machines in laboratories, for uses agreed to with the Computer Centre. | i) Continuous operation of labs during scheduled class times. Lab machines provide appropriate levels of performance for the type of machine and the software being used. | i) Servers and network are monitored by the Computer Centre.
Computer Centre to conduct bi-annual survey of staff and students using labs. |
| For labs managed by the Centre,
ii) maintain a booking facility for staff wishing to use the lab for classes, iii) publish lab bookings and hours of operation |
ii) mechanism for booking labs is published on the Centre's home pages. iii) lab bookings and hours of operation are published on the Centre's home pages and in the labs. |
ii),iii),iv) Monitored by the Computer Centre and CeLTS. Computer Centre to conduct bi-annual survey of staff and students using labs. |
|
||
| a) DITS
i) Consult with faculties and departments to establish standard software packages. ii) Annually review and publish the minimum DITS standard hardware configuration. iii) Annually review and publish the approved list of DITS hardware suppliers and negotiate the price of the hardware for Monash. iv) Provide centrally managed DITS file servers of sufficient capacity, security and performance of each campus for all staff. v) Provide each DITS file server with the ability to be expanded for faculty specific applications. vi) Provide a means to recover data stored on DITS file servers in the event of disk failure. |
i) Consultation takes place prior to deciding on the standards. ii iii) Materials are published on the Computer Centre's home pages. iv) Login to server within 15 seconds and sufficient disk capacity for basic operations. v) Negotiated the upgrade of file server capacity with faculty and departments. vi) Successful recovery of files. |
i),ii),iii), Monitored by the Computer Centre and CeLTS
iv) Conduct bi-annual survey of staff v) Monitored by the Computer Centre and CeLTS. vi) Monitored by the Computer Centre and CeLTS. |
|
||
| i) Provide a range of reliable and secure centrally managed host system of sufficient capacity for teaching, research, library and administrative operations.
ii) Publish list of software available on teaching and research systems . iii) Publish system usage statistics. iv) Provide a means to recover data stored on host systems in the event of disk failure. |
i) Continuous operation of systems during normal business hours.
ii),iii) List of software and system usage statistics published on the Centre's home pages. iv) Successful recovery of files. |
i) Monitored by the Computer Centre through its automated service monitoring service monitoring tools and CeLTS. Computer Centre to conduct bi-annual survey of staff and students.
ii),iii),iv) Monitored by the Computer Centre and CeLTS. |
|
||
| i) Operate a Helpdesk at each major campus for reporting faults, providing information on the Computer Centre's services and submitting of requests for changes or enhancements to services. | i) helpdesk is appropriately staffed and open during the advertised hours. | i) Monitored by the Computer Centre and CeLTS. Computer Centre to conduct bi-annual survey of staff and students. |
| ii) The Computer Centre helpdesk will co-operate with faculty and departmental Helpdesks. | ii) Positive feedback from helpdesks on level of co-operation.. | ii),iii),iv) Monitored by the Computer Centre and CeLTS. |
| iii) Publish information on the services provided by the Computer Centre. | iii) Information is published on the Computer Centre's home pages. | |
| iv) Provide sufficient notice, where possible, of impending changes to services. | iv) Notice messages are published on the Centre's home pages, and emailed to appropriate lists with sufficient notice where possible. | |
|
||
|
This service will change when the recommendations of the TACI review are implemented and therefore no criteria can be agreed to. |
||
| Policy Information | ||||
| Title of Policy | Quality Assurance in Off Campus Learning and Open Learning Programs | |||
| Policy Reference | acad15 | |||
| Central Registry File No. | ||||
| Approval Process | ||||
| Authorising Person | University Council | Academic Board | ||
| Meeting No. | 03/97 | Meeting No. | 03/97 | |
| Meeting Date | 12/05/97 | Meeting Date | 16/04/97 | |
| Agenda Item | inc in proc. of Academic Board | Agenda Item | ||
| Policy approved on | 16/04/97 | |||
| Policy effective on | 16/04/97 | |||
| Policy expires on | ||||
| Policy next reviewed on | ||||
| Related statutes | ||||
| Related regulations | ||||
| Comments | See also Education Committee Meeting Minutes 2/97 | |||