1. Program Guides System: Transition Process Presentation to VETLink: Friday 17 April 2009

2. VETLink: 17 April 2009 2 Project Objectives Provide a single authoritative source of information for TAFE and HE programs Support the HE program approval process Enable the automatic generation and publication of: – Program Guides – Enrolment Program Structures

3. VETLink: 17 April 2009 3 Overview of System HE Program Approval Documents Program Guides (Handbook) Enrolment Program Structures Program Guides System AMS/Peoplesoft Student System

4. VETLink: 17 April 2009 4 Enrolment Program Structures Went “live” in September, 2008 Automates the production of the former Enrolment Program Summaries Provide an extract of the program structure from PeopleSoft Includes class numbers, access to course guides and other information to assist students enrolling online

5. VETLink: 17 April 2009 5 Program Guides Official, historical record – version control Will assist with AQTF compliance (Element 2.2) One for each program/plan/campus One for each program within “nested” programs Scheduled to go-live in April/May

6. VETLink: 17 April 2009 6 Transition – TAFE A program guide currently not required as part of program approval/amendment process No published program guides currently exist for TAFE programs TAFE program approval/amendment process will shortly be amended to require a program guide for each program

7. VETLink: 17 April 2009 7 Process to Publish TAFE Guides School will create new draft and enter data in the program guides system College to “endorse” program guide using internal college approval processes ARG will then “publish” program guide Schools have two years to create guides for all TAFE programs

8. VETLink: 17 April 2009 8 New Programs for 2010 - TAFE Program guides will be developed as part of approval process Program guide will be created in PGS once ARG have created a new record [after approval from Deputy Director (TAFE)]

9. VETLink: 17 April 2009 9 Next Steps Program guides system scheduled to go live in late May System training will be spread over June / July / August Processes to support transition will be documented and distributed