Top of ENR

Index

Table of Contents

Feedback

Student Load Structure and Management

This section describes:

• Load Calendar Structure
• Load and Discontinued Unit Attempts
• Relationships Between Load and Attendance Type

  Note: Many of the procedures described here are likely to be performed only by a specialist user.

Load Calendar Structure

A number of Calendar Categories exist in the System. One of these categories is LOAD. The Calendars in this category specify the periods of time against which student load is calculated. They are used in:

• Determining a student's EFTSL at any point in time
• Determining a Student's Attendance Type at any point in time
• Calculating Fees, including Student Contribution Amount

A Load Calendar belongs (in a parent/child relationship) to one Academic Calendar only, and normally each Load Calendar spans only one Government Census Date. Conversely, Teaching Calendars (and therefore Study Units) may span one or more Load Calendars.

The diagram below outlines a typical configuration of Academic, Load and Teaching Calendars. It is the basis for the explanations which follow. Of course, institutions will set up these relationships to reflect the pattern of their own Teaching Periods. Moreover, different configurations can be made available concurrently to cater for a variety of Teaching Delivery Patterns which might run at the same time (for example, Award Courses and courses offered for commercial clients).

This diagram assumes three Teaching Calendars, all starting at the same time, but running for:

• A Semester (SEM-1)
• A Year (YR-LONG)
• Three Semesters, starting in Semester 1 of one year, and ending at the end of Semester 1 in the following year (S1-E1).

This is a simplified view, for in reality Teaching Calendars of the same length will probably start at various points in the Academic Year. To extrapolate from the example, Teaching Periods named SEM-2, YR-LONG-2, and S2-E2 might all start mid-year in 2003, while another instance of S1-E1 starting in Semester 1 2004, will be beginning as the instance shown in the diagram ends (they will overlap during one Semester). Additionally, the start and end of Teaching Periods need not dovetail exactly with the start and/or end of a Load Calendar Instance, unless, the Load Calendar starts before the earliest load-incurring Discontinuation Date Alias.

Aggregate Load Calendars

Aggregate load Calendars are Calendars whose specific purpose is to group together two or more standard Load Calendars so that load can be considered for the combined Calendars rather than for each individual Calendar.

This allows standard Load Calendars to be created to measure student load in non-traditional Teaching Periods. Standard load Calendars linked to an aggregate load Calendar are still used for purposes such as fee assessment within a corresponding fee period and determination of load contribution of discontinued Unit Attempts. Standard load Calendars not linked to Aggregate Calendars may be used for all load calculation purposes.

Aggregate Load Calendars can be used to group two or more Standard Load Calendars for purposes such as:

• Fee assessment - based on aggregate load in a Fee Period corresponding to the Aggregate Load Calendar;
• Derivation of Attendance Type - considering all of a Student's Unit Attempts related to the aggregate period, and
• Enrolment checks and Encumbrance checking at Enrolment - where an Aggregate Load Calendar has been linked to an Enrolment Period

This diagram illustrates how an Aggregate Load Calendar (AUTMCENSUS) can be used to group a number of Standard Load Calendars (LD-CAL1A, LD-CAL1B, LOAD-CAL1) to provide an aggregated view of load. Using the Aggregate Load Calendar, Attendance Type, for example, can be determined at the Autumn Census Date (31 March). Load under all three Standard Load Calendars is summed and the total compared to the Attendance Type Load ranges for AUTMCENSUS.

Aggregate Load Calendars are discussed further in Load Calendars - Special Topic

.

'Point in time' Calculations

Student load is always calculated for a Single Load Period (a Load Calendar Instance) whenever required (this may be an Aggregate Load Calendar Period). This means that a student's load as at a particular date within an instance can be anticipated or determined at any time both during and after the instance. Load predictions can be calculated for future load periods as soon as the Calendar structures are in place and students have enrolled.

Apportioning load

Study units represent a certain number of credit points or EFTSL towards a student's load, as specified in the Maintain Basic Unit Details form (CRSF2210) in the Course Structure and Planning Subsystem. But for units with Teaching Periods which span more than one load period, the load which the unit represents must be split across two or more load periods. This is so for the YR-LONG and S1-E1 examples above. Here, load is distributed evenly between two load periods for YR-LONG, and between three for S1-E1.

However, load for a Teaching Period can also be distributed unevenly across the span of two Academic Calendars (but not more than two). In our example, this means that for YR-LONG, load could be split between LD-CAL1 and LD-CAL2 in proportions such as 60%-40%, 20%-80% or any other ratio totalling 100%. Similarly, for S1-E1, load could be split across LD-CAL1 (2003), LD-CAL2 (2003) and LD-CAL1 (2004) in any desired proportion, for example 50%-30%-20%. The distribution of Teaching Calendar load between load periods is recorded in the form Maintain Load Calendar Structure (ENRF01K0).

This load apportionment holds good for all enrolled and completed Student Unit Attempts. For students who have discontinued a Unit Attempt, the System must decide whether or not they should incur load in a particular load period. This is described below.

Note: Load apportionment is not recorded for Aggregate Load Calendars. They 'collect' load from their subordinate Standard load Calendars.

Note: For DIISRTE purposes, load for a student unit attempt is reported in association with the teaching period for which the unit is studied, and does not consider the load calculation described above.

Load and Discontinued Unit Attempts

This explanation relies on an understanding of the discontinuation mechanism explained in Managing Unit Discontinuation, and follows through the example given there.

For simplicity, this mechanism was demonstrated using one Teaching Period, SEM-1. But because the Administrative Unit Statuses shown there also carry implications for load, we now need to consider them in relation to Teaching Periods of different lengths. The diagram below reflects this more complex scenario.

Once again this diagram assumes a simple data structure where one set of Administrative Unit Statuses is used in three different Teaching Calendars. If required, different sets could be applied to different Teaching Calendars.

Recall that when a student discontinues a Unit Attempt, the System finds the most recent Discontinuation Date Alias Instance in that Teaching Calendar on or before the Student's Discontinuation Date. These Discontinuation Date Aliases are matched to Administrative Unit Statuses except where the Unit Attempt is deleted (typically a very early withdrawal). The table below summarises this matching for the data used in our example.

Setting Up the Load Mechanism

Setting up the mechanism to handle load for discontinued Student Unit Attempts involves setting a check box for each Administrative Unit Status to show whether it does or does not carry load. This is done in the form Maintain Load Calendar Structure (ENRF01K0).

The Logic

Once the load mechanism is set up, this is the logic used to calculate whether a discontinued Unit Attempt contributes to a student's load in any load period:

• From the Date given for discontinuing the unit, the System looks back to the last Discontinuation Date Alias Instance in the Teaching Period of the study unit.
• The Load Incurred check box for student's Administrative Unit Status determines whether load is, or is not, incurred.

Where load is incurred, it is added in the proportion already specified as this Teaching Period's contribution to the particular load period.

Example Scenarios - Determining Load

These scenarios apply the logic above, and are based on the previous diagram. They use an equal apportioning of load across Load Calendars.

For LD-CAL1, 2003

• Scenario 1: A student studying in SEM-1 withdrew on 9/6/03. The prior Discontinuation Date Alias fell on 8/6/03. The Student's Administrative Unit Status is WD-FAIL, which incurs load. Load (100%) is attributed to the student for this unit within the load period.
• Scenario 2: Studying in YR-LONG, a student withdrew on 25/5/03. The prior Discontinuation Date Alias fell on 31/3/03. The Student's Administrative Unit Status is WD-LATE1, and WD-LATE incurs load. Because load is incurred, 50% of the unit attempt's load is attributed to the student for this unit within load-cal1. Because the withdrawal is before WDN-LATE, there will be no load incurred for load-cal2.
• Scenario 3: Studying in S1-E1, a student withdrew on 5/3/03, making the date of the prior Discontinuation Date Alias 2/3/03. Her Administrative Unit Status is WD-EARLY, which does not incur load. No load is attributed to the student for this unit.

For LD-CAL2, 2003

• Scenario 4: A student studying in YR-LONG withdrew on 2/7/03. The prior Discontinuation Date Alias, associated with a status of WD-LATE (which, in ENRF01K0, has the Load incurred checkbox set for LOAD-CAL1 and LOAD-CAL2) fell on 31/3/03. Even though this is prior to the start date of the LD-CAL2, the student will incur load for both LD-CAL1 and LD-CAL2.
• Scenario 5: Studying in S1-E1, a student withdrew on 21/10/03 with an administrative status of WD-LATE (which in ENRF01K0 incurs load for LOAD-CAL1 and LOAD-CAL2 for 2006, but not for LOAD-CAL1 in 2007. Therefore load is not attributed to the student for this unit in LOAD-CAL1 in 2007.

For LD-CAL1, 2004

• Scenario 6: Studying in S1-E1, this student withdrew on 2/4/04. The prior Discontinuation Date Alias 31/3/04, associated with a status of WD-LATE (which incurs load for LOAD-CAL1 and LOAD-CAL2 in in 2006 and also LOAD-CAL1 in 2007).
• Scenario 7: Studying in S1-E1, this student withdrew on 10/6/04 receiving a status of WD-FAIL. The prior Discontinuation Date Alias is on 7/6/04, and WD-FAIL incurs load. As with WD-LATE, this student administrative status incurs 33.33% of load in each of the related load calendars.

Relationship Between Load and Attendance Type

There is a direct relationship between the load incurred by a student and their Attendance Type. Students enrol in a Course Offering Option which is of a particular Attendance Type. They then enrol in units, each of which attracts a specified amount of load. The System calculates the load for a student in two ways for two distinct purposes.

1. To report an Attendance Type, for each student, to Government.

This Attendance Type is determined by comparing the student's calculated load (for a particular reporting period, load is calculated for all of a Student's Course Attempts across all relevant Teaching Periods using the relevant apportionment factors) to the load ranges defining Attendance Types for the Academic Period.

2. To determine the Attendance Type of a course for a particular Academic Period:

For comparison with the Student's Enrolled Course Attempt Attendance Type (for checking against 'forced' Course Attempt attributes) . The System makes validation checks to see whether the total load for all load incurring units in which the student enrolled is within the acceptable load range for the Attendance Type of the Course Attempt. The units considered are those in Teaching Periods linked to Load Calendars which are Subordinate to the Student's Course Enrolment Period.

3. To determine the Attendance Type of a course for a particular Load Period:

For display of a derived Attendance Type in various Callista forms and for Attendance Type related administrative purposes, such as internal Fees and charges and library borrowing privileges.

This Attendance Type is determined by comparing the student's calculated load for a Course Attempt to the load ranges defining Attendance Type for a particular load Calendar Period.

For example, a student has enrolled in a full-time course. The acceptable load range for full-time Enrolment in this course is 0.750 - 2.000 EFTSL. The student elects to study units with a total load of 0.750 EFTSL in this Academic Period (this year). This student is reported to Government as a full-time student.

The same student may be enrolled in units totaling 0.250 EFTSL in Semester 1 and 0.500 EFTSL in Semester 2. The acceptable load range for full-time Enrolment in each of two Load Calendars corresponding to these Semesters is 0.375 - 1.000 while the part-time load range is 0.001 - 0.374. The institution uses Attendance Type (full or part-time) to determine a Service Fee. The student's load for first Semester is within the part-time load range so the student is liable for the part-time Service Fee rate in Semester 1. The student's load for second Semester is within the full-time load range so the student is liable for the full-time Service Fee Rate in Semester 2.

Further information:

• The concept of Load Calendars is fully detailed above.
• The load ranges for both Academic Periods and Load Calendar periods is maintained using the Maintain Attendance Types form (CRSF1170).
• The credit point value applicable to a unit is recorded and maintained in the Maintain Basic Unit Details form (CRSF2210).

Last Modified on 18 December, 2006