The Credential Eligibility Calculator is the component of the Transcript Processor that is responsible for determining if a student has satisfied the requirements and is eligible for a credential.

In order to determine when a Credential Requirement has been met by a student there are two Student Credential Requirement attributes that need to be considered:

• Achievement
• Exemption

The following table outlines when a credential requirement should be considered met based on the two Student Credential Requirement attributes.

Note: The services Get Student Credentials and Get Student Academic Profile do not return a Met / Not Met indicator. It will be the responsibility of the PASI Client to implement the above table in order to interpret if the requirement has been met by the student.

The following details outline the pieces of data that need to be updated based on outcomes determined by the calculator.

Note: Credential Requirement Statuses are calculated by PASI, as needed and are not stored within the database.

Each credential requirement may relate to one or more credential requirement sets. The relationship between the credential requirement and credential requirement set identifies if the credential requirement is a trigger requirement for that credential requirement set. When a student has achieved all trigger credential requirements for a specific credential requirement set the credential eligibility calculator creates a credential requirement set record for the student. This reflects that they are working towards the achievement of that credential requirement set.

The following details outline the pieces of data that need to be updated based on outcomes determined by the calculator.

The following table lists the security roles that are used by the Credential Eligibility Calculator

Please refer to the PASI Security overview for more information.

Please see the individual Credential Requirements documentation on the roles that can manage a requirement achievement. Multiple roles can be defined to manage the achievement¹⁾. For example, the following indicates users with 18A, 18B and 18C can manage the achievement for the requirement:

Please see the individual Credential Requirement Exemption Reasonss documentation on the roles that can submit or approve a requirement exemption Multiple roles can be defined to submit or approve an exemption ²⁾. For example, the following indicates users with 18A, 18B and 18C can submit the exemption, while 18B and 18C user can approve the exemption.

If there is no Approval permission specified for the Credential Requirement Exemption, it is 'auto-approved' - i.e. when it is Requested, the system automatically moves it to an Approved status.

• Awarded credentials from both the primary and secondary ASN should be returned for the primary ASN.
• The following should be observed on the secondary ASN after linking:
  • If prior to linking the secondary ASN has a “Not Awarded” credential, the credential should no longer be returned after linking.
  • If prior to linking the secondary ASN has an “Awarded” credential, the credential should still be “Awarded” after linking.

Note: Where ASN's are linked and the Secondary ASN has one or more awarded credentials, this will be handled manually by re-issuing the credential on the Primary ASN once the Secondary ASN has been successfully linked.

• Only credential requirement sets directly related to the primary ASN should be returned for the primary ASN.
• The following credential requirement achievement statuses should be returned on the secondary ASN:
  • If prior to linking the secondary ASN has an “Achieved” and “Not Awarded” credential, the credential requirement set should have an achievement status of “Not Assessing.”
  • If prior to linking the secondary ASN has an “Achieved” and “Awarded” credential, the credential requirement set should have an achievement status of “Not Achieved.”

• The most current Student Credential Requirement record between the Primary ASN and Secondary ASN should appear for the Primary ASN
• Deleted Achievements on the Secondary ASN will be ignored and will not appear on the Primary ASN
• Editing the exemption on the Primary ASN only affects the Primary ASN
• The Secondary ASN should reflect the most current exemption for the Secondary ASN prior to linking of ASNs
• The exemption on the Secondary ASN cannot be edited

• Same as Exemptions above

• Credentials from the primary ASN should be returned for the primary ASN.
• The following should be observed on the secondary ASN after unlinking:
  • Credentials from the secondary ASN should be returned for the secondary ASN.
  • “Not Awarded” credentials may be returned after unlinking depending on if the secondary ASN now has “Achieved” an associated requirement set.

• The credential requirement sets should recalculate for the formerly primary and secondary ASNs after unlinking.

• The most current exemption added to the Primary ASN should appear on the formerly Primary ASN
• The most current exemption added to the Secondary ASN prior to linking should appear on the formerly Primary ASN

• Same as Exemptions above

The credential eligibility calculator has only been designed to assess detailed credential requirements from 2010 onward. A user needs to assess a student’s information in order to determine the student’s achieved status for credential requirement sets that existed prior to 2010.

credeligcalc_oleobject4.vsd

Credential requirement sets that have a credential requirement where the IsSystemUpdateable flag is set to 1 are considered manually assessed credential requirement sets.

The IsSystemUpdateable flag indicates that the requirement is a requirement that is set by a user and can be reset by PASI.

There are two purposes for the IsSystemUpdateable flag:

• Allow the user to record their assessment of the student’s records in relation to a particular credential requirement set, e.g. “Achieved.”
• Allow PASI to communicate that new information has been received for the student and that the original assessment is no longer valid and requires reconsideration, i.e. “Not Assessed.”

The processor starter version is used to capture the version of the student’s record that triggered the transcript processor to run. When updates are made to any of the following records associated to a student, the version recorded on the record that was updated will also be recorded as a processor starter version:

• Student³⁾
• School Enrolment
• Course Enrolment
• Evaluated Mark
• Exam Mark
• Manual Credential Requirement⁴⁾
• Credential Requirement Exemption⁵⁾

Even though credential Awarding is a processor starter the version of the awarded credential is not recorded as a processor starter version. The processor starter version is then compared against the version of the student requirement that ‘Is System Updateable’ in order to determine if the last action was the update of the ‘Is System Updateable’ student requirement or some other record. The result of this comparison will determine if the student requirement that ‘Is System Updateable’ should be updated by PASI.

Upon restart of PASI Core, a process is initiated to handle management of manually assessed credentials.

awardingcred_diagram1.vsd

PASI Core reset will initiate a task to update a manually assessed credential only when all of the following conditions have been met:

• The manually assessed credential is “Not Awarded” to the student
• A higher order or equivalent credential has not been awarded to the student – this includes non-deleted Credential. Refer to Credential Order logic.
• The manually assessed credential requirement (IsSystemUpdateable=1) has an achievement status of “Not Achieved”,
• The manual credential requirement does not have an approved exemption,
• The version of the manual credential requirement is less than the Processor Starter Version.

For all manually assessed credentials that meet the above conditions, the following information will be created or updated:

• Update the manual (IsSystemUpdateable) credential requirement for the student to an achievement status of “Not Assessed”.

Create a record in the Transcript Trigger for students who had their manual credential requirement updated. When the Transcript Processor processes the student, the Credential Requirement Set achievement status will be set to “To Be Assessed” based on the manual credential requirement being “Not Assessed”.

A PASI system user should be recorded as the audit user to show that the system updated the credential and the credential requirement.

A known, but acceptable reporting deficiency will exist when a higher order credential is awarded. After a higher order credential⁶⁾ has been awarded the lower order manually assessed credential will never return to “To Be Assessed.” This means after a higher order credential has been awarded the lower order manually assessed will be reported for re-assessment. It was determined that this scenario, i.e. lower order awarded, higher order awarded then lower order requiring deletion, would have a low probability of occur and this behavior would be acceptable.