Progression - Special Topics

Progression — Special Topic

In this section:

Calculation of Grade Point Average / Weighted Average Mark
Grade Point Average
- Example
- Storing GPA values
Weighted Average Mark
- Example
- Storing WAM values
Derivation of Show Cause / Appeal Expiry Dates
- Example
Derivation of Progression Outcome and Encumbrance Expiry Date
- Examples

Calculation of Grade Point Average/Weighted Average Mark

The GPA and WAM values can be calculated for a Student Course Attempt, in three ways:

At the time of evaluating a student's progress against a rule that measures one of these values. For example, an institution may have a rule that states that each student must have a Course GPA >= 3.
In this institution, the progress of every student is measured against this rule, at the end of a defined Progression Period. As this evaluation is done, the Course GPA for each student is calculated and used by the rule to determine whether the student has passed or failed the rule. This GPA value is not necessarily displayed or stored (see 2); instead a Student's Progression Status reflects the 'pass/fail' result of the rule evaluation.
Where the Progression configuration settings that apply to this Student Course Attempt have either of the Calculate GPA/WAM Indicator parameters set, the calculation and storage of both a course and a Progression Period GPA/WAM value is done as part of the process of applying Progression Rules. (Refer to the documentation for the job PRGJ6100 for a full explanation of this process). The Progression configuration applicable may be a System, Organisational Unit or Course Version level configuration. (Multi-level configuration is explained in Specialist Functions.) The calculation is executed regardless of whether a rule using GPA or WAM as a measurement tool is checked for this Student Course Attempt or not. The resulting values are displayed on PRGF6600.
An institution may also wish to be able to view (through ENRF3000, ENRR08M0 or INQF1200) a student's current course GPA and/or WAM. The calculations are performed, at the time of the inquiry, and the student's current GPA and WAM values are displayed. These would not have any impact on the Student's Progression Status, as they are not part of the evaluation of any Progression Rule. This 'as-required' calculation of either GPA or WAM can only be done if the Calculate GPA/WAM Indicator parameter is set at the Progression Configuration Level applicable to this Student Course Attempt. Display in ENRF3000 is also dependent on the Enrolment Category including the PROGRESS System Enrolment Step Type (ENRF0192) and configuration that permits the user to 'perform' the step (ENRF01H0).

Calculation of Grade Point Average

Where a Grade Point Average value is calculated for a student, the calculation uses the following data:

Achievable Credit Points: Every unit in a Student's Course Attempt has an Achievable Credit Points value (as defined in form CRSF2210). The calculation of a GPA value requires the total value of a student's Achievable Credit Points. Where an override credit point value is set for a Student Unit Attempt, the Override Value is used

Grade GPA Value: When defining a Grading Schema for use at an institution (in ASSF5110), each Grade can have a corresponding GPA Value nominated. Where this has been recorded, the grades recorded against the units a student has studied have an equivalent GPA Value.

The standard formula for calculating a student's GPA is:

GPA = Total (Achievable Credit Points * Grade GPA value) / Total (Achievable Credit Points)

Example

A student has the following grades recorded against six units:

Unit	Achievable Credit Points Value	Student's Grade	Grade GPA Value
1	1	D	6.00
2	1	C	5.00
3	2	N	2.00
4	1	N	2.00
5	1	P	4.00
6	2	PC	3.00
Total:	8

Using these values the calculated GPA

=(6+5+4+2+4+6) / 8
= 27 / 8
= 3.3

The inclusion/exclusion of Student Unit Attempt Grades or the substitution of Grade Point Average values for use in the calculation is determined by the 'type' of GPA calculation. For the available types of Grade Point Average calculations refer to Progression Rules Overview or the syntax of Progression Rules. The inclusion/exclusion of discontinued Student Unit Attempts is determined by the associated Administrative Unit Status. A discontinued unit is only included in the calculation where that is a status with the 'Effectively Enrolled for Progression' check box set. (See ENRF0110.)

Storing GPA Values

Some GPA values, calculated as part of the process of applying Progression Rules, can be stored. This is only possible where the configuration parameter 'Calculate GPA check box' is set at the configuration level applicable to the Student Course Attempt (either System, Organisational Unit or Course Version configuration).

The GPA value is stored along with data that identifies the Progression Period in which it was calculated. Only Course GPA and Progression Period GPA values calculated using finalised results, can be stored.

Calculation of Weighted Average Mark

Where a Weighted Average Mark value is calculated for a student, the calculation uses the following data:

Achievable Credit Points: Every unit in a Student's Course Attempt has an Achievable Credit Points value (as defined in form CRSF2210). The calculation of a WAM value requires the total value of a Student's Achievable Credit Points. Where an Override Credit Point value is set for a Student Unit Attempt, the override value is used.

Numeric Mark Value: This is the numeric mark recorded as the assessment outcome for each unit a student has studied.

WAM Weighting Value: This is derived from one of two values.

The WAM Weighting value assigned to a unit. Where a Unit Level is recorded for a unit (in CRSF2210), it has a WAM weighting value assigned to it (in CRSF2140). Institutions can 'weight' different level units. For example a unit designed as part of the first year of an undergraduate degree course would generally have a lower weighting value than a unit designed to be studied in the final year of the same course.
The Course Unit Level recorded in CRSF2240 (accessed from CRSF2210 via Other Unit Details). Institutions can allocate a course level value to a unit, which 'weights' the unit based on the course level at which the unit is designed to be studied. For example a standard first year undergraduate unit may have a Course Unit Level of 1. When that unit is undertaken by a student enrolled in a Master's by Research course, this low Unit Internal Course Level value results in a lower WAM value, for that student than when it is undertaken by a first year undergraduate student.

The Course Unit Level value is used where it exists. If not, the Unit Level WAM weighting value is used. If neither exist, a WAM Weighting value of 1 is used.

The standard formula for calculating a student's WAM is:

WAM = Total WAM Achieved / Total Achievable WAM

The Total WAM Achieved is calculated from the results recorded against each unit in a Student's Course Attempt.
For each unit:

WAM Achieved = Achievable Credit Points * WAM Weighting * Numeric Mark.

The Total Achievable WAM is calculated from the basic unit details recorded against each of those units.
For each unit:

Achievable WAM = Achievable Credit Points * WAM Weighting.

Example using the Unit Level WAM Weighting:

Three Units have the following Unit Level WAM Weighting values:

Unit	Achievable Credit Points Value	Unit Level WAM Weight Value
ABG271	2	2.00
ASC238	1	2.00
HD0101	4	9.00

Using these values for a student with the given marks, the WAM for that student would be calculated as shown:

Unit	Achievable WAM (Achievable CP * WAM Weighting)	Student's Mark	WAM Achieved (Achievable CP * WAM Weight * Mark)
ABG271	4	71	284
ASC238	2	85	170
HD0101	36	80	2880
Total:	42		3,334

Using these values the calculated WAM = 3,334 / 42 = 79.381

For the available types of Weighted Average Mark rules refer to Progression Rules Overview or the syntax of Progression Rules. The inclusion/exclusion of discontinued Student Unit Attempts is determined by the associated Administrative Unit Status. A discontinued unit is only included in the calculation where that is a status with the 'Effectively Enrolled for Progression' indicator set. (See ENRF0110.)

Storing WAM Values

Some WAM values, calculated as part of the process of applying Progression Rules, can be stored. This is only possible where the configuration parameter 'Calculate WAM check box' is set at the configuration level applicable to the Student Course Attempt (either System, Organisational Unit or Course Version configuration).

The WAM value is stored along with data that identifies the Progression Period in which it was calculated. Only Course WAM and Progression Period WAM values can be stored. This means the resulting value from those calculations that include Recommended marks cannot be stored.

Derivation of Show Cause/Appeal Expiry Date

When Progression Rules are applied, under a configuration that allows a student to show cause or appeal, the date by which that student must show cause or lodge an appeal is calculated. This calculation uses:

The Show Cause/Appeal Length value (from the configuration level that applies to this student)
The Show Cause/Appeal Cut Off Date Alias Instance (from the applicable Progression Calendar)
The date on which the Progression outcome was approved.

A Student's calculated Show Cause / Appeal
Expiry Date = Outcome Approval Date + Show Cause / Appeal Length value.

If this resulting date is later than the Show Cause / Appeal Cut Off Date Alias Instance, the Expiry Date is set to the Cut Off Date Alias Instance (where it is still a future date). This is the case for Student B in the example below.
If the Cut Off Date Alias Instance has passed, the Expiry Date for this student is set to the current date. This is the case for Student C in the example below.

This system derivation gives all students an equal number of days in which to show cause or appeal, providing the derived date is before the Cut Off Date. A user with the required level of security can override the derived date.

Example

	Applicable Show Cause Cut Off Date Alias Value	Applicable Show Cause Length	Outcome Approval Date	Expiry Date (by which Student must have shown cause)
Student A	31/07/03	14	25/06/03	9/07/03
Student B	31/07/03	14	20/07/03	31/07/03
Student C	31/07/03	14	3/08/03	3/08/03

Derivation of Progression Outcome and Encumbrance Expiry Date

Derived Expiry Dates:

These dates can only derived be where the Duration and Duration Type are defined as part of the Student Progression Outcome. Only outcomes with the System Progression Rule Outcome Types of SUSPENSION, PROBATION or MANUAL can have a duration/duration type and therefore derived Expiry Dates (for both the Outcome and the associated Encumbrance).

Note: For a list of all System Progression Rule Outcome Types, see PRGF1100.

The derivation depends on the existence of instances of the future Progression Calendars of the same Stream Number as the Progression Calendar in which the outcome was applied. The number of instances that must exist is the number entered for the Duration of the Progression Outcome. The instance (for the identified Progression Calendar) of the Encumb End Date Alias (set in the system-wide configuration) is recorded as the Expiry Date. (If there is no instance of this Date Alias in the existing Progression Calendar, the End Date of that Progression Calendar is used instead.)

Where the Duration Type = NORMAL, the Expiry Date is the Encumb End Date Alias instance for the nth future Progression Calendar instance, where n = Duration.
Where the Duration Type = EFFECTIVE, the Expiry Date is the Encumb End Date Alias instance for the nth future Progression Calendar instance in which the student had a Student Unit Attempt with the status of ENROLLED, COMPLETED or DISCONTIN recorded in a subordinate Teaching Period.
Where the required Calendars do not yet exist, Expiry Dates are not recorded and the batch maintenance process (PRGJ6450) derives the dates as soon as it is possible (because the Calendar Instance has been created).

Manually Set Expiry Dates:

Some Progression Outcomes (and their associated Encumbrances) cannot have a Duration/Duration Type specified and therefore cannot have a derived Expiry Date. These are outcomes with a System Progression Rule Outcome Type of EXCLUSION, EXPULSION or NOPENALTY. These types of student Progression outcomes must be manually ended in one of the following ways.

A Decision Status of CANCELLED can be entered for the outcome. When this change to decision status is applied (through running job PRGJ6800) the System Date is entered as the Expiry Date for both the Student Progression Outcome and associated Encumbrance/Encumbrance effects.
An Outcome could have the Expiry Date manually set to enable the ending of an Outcome without changing the decision status. This can be done to end one of the Outcome Types that cannot have duration details recorded. It can also be used to expire a current Outcome to allow the application of another incompatible outcome. For example where a student who currently has an applied PROBATION outcome is to have an EXCLUSION outcome added. This incompatible Outcome cannot be added until the existing probation is expired.

Note: An Expiry Date that was manually applied to an Outcome (in PRGF6610) can subsequently be deleted (ie. set to NULL), for example, if you want to make the Encumbrance ACTIVE.

For all System Progression Rule Outcome Types (i.e. Outcomes with a derived Expiry Date and those with a manually entered Expiry Date):

If required, an Expiry Date can be manually back-dated (in PRGF6610) to a date that is greater than or equal to the Encumbrance Start Date and less than or equal to the current date.

Examples

Scenario One:

A suspension of a NORMAL duration type and duration length of 2 is applied to Student1 on 25/6/2003. The Progression Periods in this scenario are semester length with a Stream Number of 1, so the student is suspended for Semester 2 2003 and Semester 1 2004. The Outcome Expiry Date = the Encumb End Date Alias Instance for the Semester 1, 2004 Progression Calendar.

Outcome Duration Type

Duration

Stream Number (of Progression Calendar Instance)

Required Conditions to Derive Expiry Date

Applied On

Outcome / Encumbrance Expiry Date

NORMAL

2 active future Progression Calendars with Stream Number = 1

For example, Semester 2, 2003
and Semester 1, 2004

25/06/2003

Encumb End Date Alias Instance from 2^nd identified Calendar
= 1/6/2004

Scenario Two:

A suspension of a NORMAL duration type and duration length of 2 is applied to Student2 on 25/11/2003. The Progression Periods in this scenario are year long with a Stream Number of 2, so the student is suspended for the academic years of 2004 and 2005. The Outcome Expiry Date = the Encumb End Date Alias Instance for the year 2005 Progression Calendar.

Outcome Duration Type

Duration

Stream Number (of Progression Calendar Instance)

Required Conditions to Derive Expiry Date

Applied On

Outcome / Encumbrance Expiry Date

NORMAL

2 active future Progression Calendars with Stream Number = 2

For example, Year 2004
and Year 2005

25/11/2003

Encumb End Date Alias Instance from 2^nd identified Calendar
= 1/12/2005

Scenario Three:

Student3 has a probation outcome applied that has an associated encumbrance type restricting this student to part-time enrolment. This outcome has the duration values of two EFFECTIVE periods. The Expiry Dates cannot be derived until the student has been effectively enrolled for two Progression Periods. When the second period in which the student is effectively enrolled is identified (through running of the batch maintenance job PRGJ6450) the Expiry Dates are derived.

Outcome Duration Type

Duration

Stream Number (of Progression Calendar Instance)

Required Conditions to Derive Expiry Date

Applied On

Outcome / Encumbrance Expiry Date

EFFECTIVE

Active future Progression Calendars with Stream Number = 1
For example, Semester 2, 2003
Semester 1, 2004
and Semester 2, 2004

Student must have at least 1 Student Unit Attempt with status of ENROLLED, COMPLETED or DISCONTIN recorded in a Teaching Period subordinate to each of the Progression Calendars.

25/06/2003

Completed Student Unit Attempt in Semester 2, 2003 Teaching Period.

No Student Unit Attempt in Semester 1, 2004 Teaching Period.

Enrolled Student Unit Attempt in Semester 2, 2004 Teaching Period.

Encumb End Date Alias Instance from 2^nd identified Calendar
= 1/12/2004

Note: Where the unit status is DISCONTIN, the associated Administrative Unit Status must be one that considers this unit 'effectively enrolled for Progression' (see ENRF0110).

Last modified on 11 November, 2013 11:51 AM

History Information

Release Version	Project	Change to Document
13.0.0.2	calipso 28954	Changed details relating to WAM calculation
12.1.0.3, 12.1.1.2, 13.0.0.2	1408 - PC140 Calipso 26870	Added note about manually back-dating Expiry date