If you still have questions or prefer to get help directly from an agent, please submit a request.
We’ll get back to you as soon as possible.
Note: This is a part of master data objects that will be created and maintained by admin users for a program plan.
Plan Requirement is an EDA object. We have extended it with record types (Group and Course) and additional fields to track information required in RIO Education.
A Group Plan Requirement is used to group Courses together for a Program Plan of an Academic Program. A Program Plan is allowed to have multiple groups with different group criteria. In a Group Plan Requirement record, admin can specify:
Credits = The total credits that needs to be gained by a student in order to complete the group.
Required = A student must complete the courses listed in the group depending on the Credits defined.
Optional = A student may choose to/not to complete the Courses listed in the group. The completion is still depending on the Credits earned. This type of Plan Requirement won’t affect the completion of a Program Enrollment.
The Credits field can be used to cater for different scenarios that you might have:
With the options above, admins can utilize Group Plan Requirement to specify which Courses are mandatory (core) and optional (elective).
Please bear in mind that Group Plan Requirement is a template. The data will be cloned to PE Group when a new Program Enrollment is created. The actual completion status of groups for each student will then be tracked in PE Group instead (individually for each enrollment).
|Plan Requirement Name||Name of the Plan Requirement (Group), i.e Core, Specialization, Elective.|
|Program Plan||The Program Plan that this Plan Requirement belongs to.|
|Category||"Required" or "Optional".|
|Credits||Total amount of credits from all the Courses under this Plan Requirement (Group).|
|Max Credits||Set the maximum amount of credits that a student can take from the Courses in this Group.|
A Course Plan Requirement is a junction object between Program Plan and Course object. It is used to represent a Course (unit of study or subject) that is being offered in a particular version of an Academic Program. As it is a junction object, admin is allowed to link the same Course record to multiple Program Plan as part of the offering.
In Course Plan Requirement, admins can define the requirements before students can enroll in a Course. The requirement logic is defined in a field name “Requirement Logic”. The requirement logic will use the “Requirement ID” defined in Program Course Requirement as the unique identifier for each requirement and perform the comparison. The logic can support simple and complex grouping. For example:
A AND B.
A OR (B AND C).
A OR (B AND (C OR D)).
(A OR B) AND (C OR D).
Please bear in mind that Course Plan Requirement is a template. The data will be cloned over to Course Connection when a new Program Enrollment is created. The actual completion status of Courses for each student will then be tracked in Course Connection instead for each individual enrollment.
|Plan Requirement Name||Name of the Course under the parent Plan Requirement (Group).
||The Program Plan that this Plan Requirement belongs to.
|Parent Plan Requirement||The parent Plan Requirement (Group) that this Plan Requirement (Course) belongs to.|
|Course||Name of the Course under the parent Plan Requirement (Group).
||"Required" or "Optional".
||Total amount of credits from all the Courses under this Plan Requirement (Group).
||In v3.3, "Placeholder" field is added on the Plan Requirement for system administrator to indicate that the Plan Requirement is a placeholder. The placeholder Plan Requirement will be skipped in the credit transfer engine and Program Enrollment creation for now.|
Note: When a Course requirement is created and if the Course is used in a Program Plan Requirement, it would create the Program Course Requirement record against that Plan Requirement, using new Course requirement information.
When creating a Plan Requirement (Group), you can use the “Shared Group” lookup field to lookup to a Plan Requirement (Group) from the Elective Program Plan. Students who enroll will see the shared group and its related Courses as if it had been set up for their Program Plan.
Please note that setting up a Group type of Plan Requirement by pointing to another Plan Requirement (Group) will bring Program Course Requirements across (i.e. pre-requisites, co-requisites, etc.).
A precautionary check should be performed to avoid any conflict. These Program Course Requirements must be attainable in the origin Program Plan (e.g. a Plan Requirement in the destination Program Plan that has a pre-requisite that is not available for enrollment in the origin Program Plan).
This is to prevent conflict for the student enrolled in the Program Plan that has a Plan Requirement (Group) created as a 'Shared Group'. This would be the case if some Course in the original Program Plan had a requisite that is not available for enrollment in the student's Program Plan.
Example Shared Group Hierarchy:
What the Admin sets up
What the Student sees
(Program Plan) Electives Program Plan
(Program Plan) Bachelor of IT
Bachelor of IT
This is a conceptual diagram of the intended function of shared groups.
Implementation of the shared groups is as such:
Create a new Program Plan to store the Elective Courses under its own Plan Requirement Group, called Shared Plan Requirement Group for example.
And when a different Program Plan's Requirement Group shares the same elective Courses, you must manually link both Program Plan Requirement Groups to the Shared Plan Requirement Group. The Shared Group link is as displayed in the screenshot below.