This section of the user manual provides an overview of the statistics subsystem and its use for the production of government statistical returns.
This is a highly specialised part of Callista, intended for the use of statistics specialists only.
Statistics reference data is maintained in other subsystems. Refer to the Statistics subsystem Table of Contents for details.
Topics covered here include:
The production of government statistics is a job for the specialist statistics officer. It requires an intimate knowledge of both the requirements of AVETMISS statistical reporting and the data sources within Callista. Users of this subsystem need to be familiar with the contents of the AVETMISS manual. It is the basis upon which this subsystem is designed. They need a broad understanding of system wide functionality and a detailed understanding of load calendars and load apportionment as well as operation of the Enrolments and Job Control and Scheduling subsystems. This manual provides the necessary information in the System Overview, Enrolments Subsystem and Job Control and Scheduling Subsystem chapters. Help for a specific topic can be found using the Index.
Setting up the Statistics subsystem prior to its first use requires some programmer/analyst activity. This is detailed in Statistics Subsystem Data Pre-requisites.
The entry of data used by the Statistics subsystem is distributed throughout other subsystems. For instance, course and unit information originates in the Course Structure and Planning subsystem and is used in the Enrolments subsystem. Users entering this data do not require detailed knowledge of the Statistics subsystem.
For the Statistics subsystem to function, specific reference data must be created and maintained in other subsystems (e.g. specific calendar instances and date alias instances must be created in the Calendar subsystem). These pre-requisites are detailed below. This data is usually created by a system administrator or by the specialist responsible for the subsystem concerned.
Government codes, as specified in the AVETMISS manual, are recorded throughout the system. In most cases one or more institution defined codes map to a government code and it is the institution defined code which is used by the majority of users. Institution and government codes are usually created and maintained by a system administrator or by the specialist responsible for the subsystem concerned.
Specific data must be created in other subsystems in order for the Statistics subsystem to function correctly. This data is detailed in Statistics Subsystem Data Pre-requisites and must be established prior to running data 'snapshots'.
Two reference data/control forms related to statistics snapshots exist in the Statistics subsystem:
The Maintain Government Snapshot Control form must be used to set up control details for a particular submission prior to the government submission snapshot process (STAJ8005) for that submission being run.
The broad processes involved in preparing a government statistics submission are described here. Where more detailed explanations are required, refer to How the Government Statistics process works.
Government reportable data is maintained routinely in Callista. For example, student addresses and course and unit details are maintained as part of the business of the institution. A set of specific codes used for government reporting is also maintained in the system. Examples include, government citizenship codes and government attendance types.
Note: After any of the Statistics jobs have been run, the Job Run Log should be checked. It will identify both the reasons for a job failing, and missing and incorrect data.
Enrolment Statistics Snapshots
Preparations for government statistics submissions 1 and 2 commence with the creation of an Enrolment Statistics Snapshot. (Submission 3 does not require the creation of an enrolment snapshot.) These snapshots are produced as frequently as the institution requires (by running STAJ8000 in the Job Control and Scheduling subsystem) and can be used for pre-submission data checking (by utilising the Government Statistics Process to identify DESTPAC validation errors) or other institution purposes such as enrolment analysis. The snapshots record course and unit data for all students except those with unit attempt status UNCONFIRM, INVALID or DUPLICATE at the point in time at which the capture process takes place. Each record is broken down to the level of teaching responsibility and discipline group within a student unit attempt within a student course attempt. Precise information about the data included in the Enrolment Snapshot is contained in How the Government Statistics process works.
The enrolment snapshots also derive a government reportable indicator for each record which flags 'Y' those records to be considered for inclusion in a government submission and flags 'N' those records which are not government reportable. The government reportable indicator may also be set to 'W' (Warning) for some records. This indicates that manual checking of these records should be performed. The Reset Government Reportable Indicator form (STAF1250) is used to view Warning records. Where required, the statistics officer can use the same form to set the government reportable indicator to 'X' (exclude - not government reportable) It is not necessary to change the indicator (for Warnings which are deemed reportable) to 'Y', as records which remain 'W' are reported in the submission by default. The Government Reportable indicatorfor each record is re-evaluated when the Government Submission Snapshot is run, with the exception of those previously changed to 'X'.
An exception report (STAR0100) is produced which lists those records not included in the snapshot, as errors. A reason is provided for each exception, permitting identification and resolution of problems.
Unwanted enrolment snapshots should be deleted using the Delete Enrolment Statistics Snapshots process (STAJ8002) on a regular basis, due to the large amount of storage space they consume.
Government Submission Snapshots
A government submission snapshot is the snapshot used to create the extract files used in DESTPAC . These snapshots can be created as required and used in DESTPAC to check data at any time prior to the actual submission being produced. (Note: For a particular submission year and number only one government snapshot is retained in the system. Running the government snapshot process again, overwrites the existing version.) The data to be included in a snapshot is determined by the parameters specified in the Maintain Government Snapshot Control form (STAF8005), the parameters specified when job STAJ8005 is run and by database routines which extract and derive data in accordance with the file specifications detailed in the AVETMISS manual. The documentation for STAF8005 provides some general information on data selection but the AVETMISS manual should be referred to for specific detail. Precise information about the data included in the Government Snapshot is contained in How the Government Statistics process works.
Production of the AVETMISS submission involves determining that a particular enrolment snapshot reflects the enrolment situation at the census date. This enrolment snapshot may by necessity have been created after the census date, to allow for processing of retrospective enrolment/discontinuation transactions (by staff with Override Variation Cut-off Date authority). The Government Submission Snapshot process (STAJ8005) is run via Job Scheduler. It uses the chosen enrolment snapshot to identify which records to consider for reporting in the government submission (via the government reportable indicator), and as a source of some data. The remaining required data is extracted or derived from other parts of the system. Other checks are performed by the system to determine if records should be included in the government submission (for example, 'Is unit enrolled as at the census date?). These are detailed in the AVETMISS manual.
Creating the Government Extract Files
Having created the government submission snapshot, the following jobs are run in Job Scheduler (regardless of the submission number) to create the extract files required for DESTPAC.
(Note: Not all files are created for each submission. Refer to the documentation for each file and the AVETMISS manual - Section 6: File Specifications, for a list of those files included in each submission.)
JOB NAME |
DESCRIPTION |
DETAILS |
STAJ0020 |
Create Academic Organisational Unit file |
|
STAJ0040 |
Create Course file |
|
STAJ0050 |
Create HECS Due file |
|
STAJ0060 |
Create HECS Liability Status file |
|
STAJ0070 |
Create Past Course Completions file |
|
STAJ0080 |
Create Student Load file |
|
STAJ0090 |
Create Student Enrolment file |
The extract files are output to a secure directory specified by the 'KEEP' environment variable. Files in the 'KEEP' directory cannot be accessed by users. The files can be copied from this secure directory, to a user directory in which they can be accessed, using the Copy Extract Files From Secure Area process (STAJ0120). The user directory is specified by the 'USER' environment variable (refer to your system administrator).
Use of extract files in DESTPAC is covered by Section 5, 'Steps in Preparing and Sending Returns to AVETMISS and the ATO', of the AVETMISS manual.
Errors produced in DESTPAC should be fixed by amending data in the 'live' database and repeating the process above.
Finalising the Submission
The final step in Callista, following the forwarding of a submission to AVETMISS is to 'close off update access' to the submission. This is done by setting the Completion Date for the submission in the Government Snapshot Control form (STAF8005). A logical date to use would be the date the submission was forwarded to AVETMISS.
Last Modified on 31 January 2002