Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

Objective

...

Overview

In preparation for the production launch of TCSI reporting, a number of configuration changes must take place before a site is able to successfully start reporting data via TCSI. This article should be used as a checklist to ensure that your Paradigm site is TCSI ready and compliant.

This article outlines a series of configuration steps that must take place to prepare a Paradigm site for successfully reporting TCSI data.

Complexity:

Status
colourRed
titleExpert

Page Contents

Table of Contents
maxLevel1
excludePage Contents

Introduction

There are potentially two rounds of Paradigm code updates that our providers will need to complete prior to entering TCSI Read-Only mode. Providers who have been long time users of Paradigm are likely to be running on an older version of our code-base and these Provider systems will need to be upgraded to the latest version of our code-base before further TCSI migration work can begin. Silverband continues to work with the providers who are in this group to schedule the upgrade work and then assist the relevant users to migrate their workflows to the new software version.

Once the TCSI update has been deployed, the system will show fields for both HEPCAT and TCSI. This will remain the case until after the system has entered into TCSI Write Mode, at which time Silverband will start deploying patches to mark HEIMS fields as hidden.

TCSI System Preparation

Info

Note

With the scope of the TCSI solution, there are two status fields that are required to be reported. Rather than creating new fields for these elements, we linked them to our status item table. Click here to find more: https://silverband.atlassian.net/wiki/spaces/PKB/pages/985126/Search%2C+Add+and+Edit+a+Status+Items?atlOrigin=eyJpIjoiMjY3Y2JiMzRlOTQwNDlmMDk2YmJhZjdiMjk2MzA4MDUiLCJwIjoiY29uZmx1ZW5jZS1jaGF0cy1pbnQifQ

  • Providers are required to open the System tab from the side menu, click on Search Status Type button. In the search box type in ‘Enrolment’, and click on Search Status Types. If more than one row of data is returned, choose the row for ‘ENROLMENT_STATUS’ by clicking the blue hyperlink at the left side of the screen. For each listed status item, click on its pencil icon to edit the record. Each enrolment status item must have matching entries for the HEIMS Unit of Study Status Identifier and HEIMS Course Outcome Identifier. Only status items that have this correct mapping will be sent to TCSI. Once each status item has matching values, click the Save Status Item button and proceed to edit the next status item in the list.

  • Complete entering data for the courses provided by your institution. This will need to be completed before you can enter any course admission records.

  • Complete the set-up tasks including campus records. This will need to be entered and completed before you can enter courses on campus records and this data will not be imported from HEIMS.

  • Complete the set-up tasks for units on campus. This will need to be completed before you can add any unit enrolment records.

Data Conversion From HEIMS to TCSI

The following points outline a series of updates that will need to be applied to convert historical data to a format that is ready and appropriate for submission via TCSI.

 

  • Courses Of Study Group

    • Match UID3

  • Courses Group

    • Match UID5

    • Update field E596 from TCSI where the value is null in Paradigm

    • Update field E609 from TCSI where the value is null in Paradigm

    • Update field E610 from TCSI where the value is null in Paradigm

    • Course fields of education

      • Import all sub-packets

    • Special interest course extension

      • Import all sub-packets

  • Students Group

    • Match UID8

    • Update field E572 from TCSI where the value is null in Paradigm

    • Update field E573 from TCSI where the value is null in Paradigm

    • Update field E574 from TCSI where the value is null in Paradigm

    • Update field E612 from TCSI where the value is null in Paradigm

    • Disability Extension

      • Import all sub-packets

    • Citizenship extension

      • Import all sub-packets

    • Scholarship Extension

      • Import all sub-packets

  • Course Admissions Group

    • Match UID15

    • Update field E620 from TCSI where the value is null in Paradigm

    • Basis for admission extension

      • Import all sub-packets

    • Course prior credit extension

      • Import all sub-packets

    • Specialisation extension

      • Import all sub-packets

    • Scholarship extension

      • Import all sub-packets

    • RTP stipend amount extension

      • Import all sub-packets

Recommended Post Migration Data Update

The following list outlines various separate updates that Silverband will implement on each Provider database to ensure that historical data is converted, and where necessary, uses the newly introduced TCSI elements.

  • Convert year long indicator - e622

  • Convert basis for admission new packet element e358 only for new records ?

  • Convert basis for admission new packet element e327 only for new records ?

  • Convert disability into new packet element e615 - only for new records ?

  • Copy e572 from course enrolment to student - only for new records

  • Copy e573 from course enrolment to student - only for new records

  • Copy e574 from course enrolment to student - only for new records

  • Convert e493 to e620 - only for new records

Further reading

TCSI Packets (Higher Education Providers)

TCSI Packets (VET Student Loans)

TCSI Push Rules

TCSI Remapped Elements

TCSI Elements with changed options

We highly recommended that all users who will be performing data entry read the following documents so that they gain a strong understanding of the elements that are required to be reported.

FINAL 2020 Data element specifications (24 September 2019)

FINAL HE Data framework and element list (24 September 2019)

HE 2020 reporting requirements v1.0 (24 September 2019)

...

TCSI Configuration Checklist:

Place a checkmark (☑) on the following list if they have already been configured in your business or institution. Refer to the Workflow section below for more details and the instructions for the configuration.

Workflow

Expand
titleProvider Configuration

Provider

Primary accredited Higher Education Provider (HEP) record

All Paradigm sites that are required to report data via TCSI will need to include a provider record that represents the primary reporting HEP. This provider record must be assigned ONE of the following provider roles:

  • TCSI VET

  • TCSI PIR

  • TCSI Higher Education

Parent Reporting Provider

Note

BE ADVISED:

The “Parent reporting provider” field for the primary HEP provider record in Paradigm must be set to the primary HEP provider. In this way the primary record is a parent of itself.

NOTE:

The following workflow needs to be completed for ALL providers that are connected to one or more of the following data types that are linked to Higher Education accredited courses or programs:

  • Base course

  • Base unit

  • Scheduled unit

  • Course enrolment

One of the triggers used to identify TCSI data within Paradigm is whether a specific record is associated with an accredited Higher Education Provider (HEP). This is achieved using the field “Parent Reporting Provider” found on the Provider Edit screen.

Dual sector providers

Providers who operate within both Higher Education and VET sectors will need to have 2 primary provider records within Paradigm: one for Higher Education and one for VET.

New required fields for TCSI providers

Implications

  • Silverband uses the abbreviation field of the primary accredited Higher Education Provider (HEP) record within Paradigm to authenticate with PRODA. This means the abbrev field must not be changed without first notifying the Silverband support team.

  • This workflow applies to provider records that are not accredited HEPs, including providers that reflect a delivery location, campus or subset of the overall reporting HEP

  • Paradigm only supports provider nesting that is one layer deep as reflected in the examples below:

    • Status
      colourGreen
      titleSUPPORTED
      Provider as a campus of an accredited HEP

    • Status
      colourGreen
      titleSUPPORTED
      Provider as a delivery location of an accredited HEP

    • Status
      colourGreen
      titleSUPPORTED
      Provider as a (department/school/faculty) of an accredited HEP

    • Status
      colourRed
      titleNOT SUPPORTED
      Provider as a faculty of a campus of an accredited HEP

Workflow

1. Choose Providers > Search menus on the side.

2. Use the search fields to load the primary HEP of your Paradigm site

3. Scroll down the page and locate the field labelled “Parent Reporting Provider

Image Added

4. Select the primary HEP from the available option(s)

5. Update any missing required fields from the list defined above

6. Click the “Save Details” button to save the changes

back to top: TCSI Configuration Checklist

Expand
titleBase Course Configuration

Base course

The Base Course Edit Details screen has been updated to contain the new TCSI elements. The historical HEIMS fields have been permanently moved to the new Program HEIMS Edit screen. This change ensures that Paradigm as a system can be simultaneously compliant with both the HEIMS and TCSI reporting standards.

Base Course Edit Screen

This screen has been updated to include the TCSI fields. The standard is higher for producing a valid base course under TCSI, compared with HEPCAT.

The following fields are compulsory to form a valid TCSI Course record:

In addition to the above fields, the following sections must also be completed:

Program HEIMS Edit screen

The Program HEIMS Edit screen offers a simplified view of the base course together with the relevant legacy HEIMS reporting fields. This screen is intended to support providers who have not yet fully reported all of their 2020 student-related data.

back to top: TCSI Configuration Checklist

Expand
titleElement 329 - Mode of attendance code

Element 329 - Mode of attendance code

NOTE:

The following workflow needs to be completed for ALL method of delivery options that are connected to students studying Higher Education accredited courses or unit

The TCSI element 329 will be derived from the existing Paradigm field “Method of Delivery” found on the Base Unit and Scheduled Unit screens. Each provider will need to configure their own mapping between the Paradigm field and the equivalent element 329 option.

Implications

  • Scheduled unit must not contain a mix of different delivery methods. A new scheduled unit is therefore required when ANY of the following scheduled unit fields change:

    • Unit Code

    • Unit Name

    • Start Date

    • End Date

    • Census Date

    • Mode of Delivery

    • Home Institution

Workflow

1. Choose System > Search Code Type menus on the side

2. Enter “METHOD_OF_DELIVERY” as the search criteria

3. Click the “SEARCH CODE TYPES” button

4. Use the blue pencil icon to edit a data record

5. Click on the field labelled “HEIMS Code” and select the appropriate element 329 option

Image Added

6. Click the “SAVE CODE ITEM” button to save the changes

Further reading

back to top: TCSI Configuration Checklist

Expand
titleElement 355 - Unit of study status code

Element 355 - Unit of study status code

Note

BE ADVISED:

New unit enrolments are normally created with a default status such as applied or enrolled. This can be configured on a per Paradigm site basis. Users should be aware that if this default status is associated with a value for element 355 then the unit enrolment will be reported to the government as part of the unit enrolment creation event.

NOTE:

Paradigm will only send a unit enrolment record to TSCI when the unit enrolment status has been associated with a valid E355 option.

The TCSI element 355 will be derived from the existing Paradigm field “Unit Enrolment Status”. This means providers may still use their own internal enrolment status values while still conforming to the requirements of TCSI reporting. Each provider will need to configure their own mapping between the Paradigm field and the equivalent element 355 option.

Video tutorial

Widget Connector
overlayyoutube
_templatecom/atlassian/confluence/extra/widgetconnector/templates/youtube.vm
width400px
urlhttps://www.youtube.com/watch?v=OwcMc5Qnr-Q
height300px

Workflow

Refer to the instructions on this workflow: How to Map a Status Item in Paradigm to TCSI Allowable Values

back to top: TCSI Configuration Checklist

Expand
titleElement 599 - Course outcome code

Element 599 - Course outcome code

The TCSI element 599 will be derived from the existing Paradigm field “Course Enrolment Status”. Each provider will need to configure their own mapping between the Paradigm field and the equivalent element 599 option.

Workflow

Refer to the instructions on this workflow: How to Map a Status Item in Paradigm to TCSI Allowable Values

back to top: TCSI Configuration Checklist

Next Steps

Once the above steps have been completed the next step is to begin data matching and performing the TCSI ready tests to bring the remainder of your data into a TCSI compliant state: TCSI Reporting

Filter by label (Content by label)
showLabelsfalse
max10
sortcreation
showSpacefalse
cqllabel = "tcsi_ready"

...

Next Page

TCSI PIR New Reporting Elements