...

Assumptions

...

The user has an understanding of the Australian Tertiary Education System.

...

The user is familiar with the previous HEPCAT / HEIMS reporting

...

Introduction

2020 Reporting Requirements

...

In implementing the new TCSI requirements Silverband analysed the two methods on sending data to the government. These two main methods include TCSI Data Upload (known as Portal method) and B2G real time solution (known as real time solution). In the intial initial specification we considered the TCSI Data Upload as this matches closely to the existing HEIMS reporting with different file formats. However the government required that updates be sent weekly at a minumum minimum which Silverband thought was to erroneous of work effort to place on providers. Additionally the government recommended that TCSI Data Upload method was only suitable for very small providers ( approx. 20 students) where the data is not changing often.

...

According to the government the TCSI web interfaces are meant to be resposonsive responsive near in real time. This allowed the implemention implementation our solution that is known as single touch. The single touch soultion solution allows data to be sent to the government as it saved in Paradigm and return to the interface the response from the web interfaces for the submitted piece of data.

See TCSI Migration 2020Summary for further notes on the development and how data packets are created.

...

• All the unit enrolments will be deleted from TCSI 1 at a time.

• Then the minimum required fields will be send to TCSI to create the unit enrolment.

• Then a an update will be sent to TCSI to completed the record as it stands in Paradigm.

...

• The elements E572, E573, E574 have been moved from the course enrolment screen to the student screen

TCSI RemappedFieldsRemapped Fields

The introduction of TCSI has presented us with an opportunity to remap some internal fields to TCSI fields as the TCSI implementation has deuplicated duplicated the meaning of a field into a single field.

• E319 - Previously this field had a dual value either a post code or country and hence a separate field in Paradigm. In TCSI this elment element purely represents the Term Address Postal Code and element E661 has been added to capture the Term Address country code. These address fields have been now mapped to the Semester Address fields for the student and hence removed from the application.

• E320 - Previously this field had a dual value either a post code or country and hence a separate field in Paradigm. In TCSI this elment element purely represents the Term Address Postal Code and element E658 has been added to capture the Residential Address country code. These addresses has been now mapped to the Billing Address fields for the student and hence removed from the application.

• E330 - This field has been mapped to the Full/Part Time field in Paradigm. It used to be a calculated based on the eftsl EFTSL being submitted in the LL file. No action is required to makethis make this work.

• E329 - This field used to be located on the course enrolment screen and has now been remapped to the scheduled unit screen and the field Mode of Delivery. This field relies that the code items for this field have the new HEIMS value filled in. Please see video below.

...

• E599 - This field is located on the course enrolment screen and has been mapped to the course enrolment status field. The enrolment status field needs a HEIMS a value mapped to it in the status edit screen. Paradigm will only send values to TSCI where there a status mapped to the field. This means you can still have your own internal enrolment status values and only when you set a status where the value is ampped mapped with to send a change to TSCI.

...

In the development of TCSI you need setup a primary provider record where the abbrviation abbreviation of the provider record matches the abbreviation of we map in Nexus for your PRODA authentication record. This means that if you are a dual sector provider then you will need 2 primary provider records one for Higher Education and one for VET Provider.

The primary provider record for botht both the higher education and primary vet provider must have the role: HEIMS Higher Education Provider.

In addition to the the above role being assigned providers are also required to set a new field: Parent Reporting Provider. Eventhough Even though this is the primary record this field must be set to itself. Apart of submitting records to TCSI Paradigm will only submit records where the primary provider is directly or indirectly associated with the primary provider.

Due to the statement above all records associated with the primary provider must also be have a relationship assigned back to the primary provider. If your instiutiion institution has numerous unit and program providers submmiting submitting data on behalf of the primary provider they also must have the Parent Reporting Provider field set. Only records that are associated to the primary provider will be submitted to TCSI. Knowing this additional provider records can be created that do not have a relationship to the primary provider for internal use.

...

Paradigm has implemented the Course of Study Packet and the Courses Group packet on the same screen. This makes the screen a complex to use as data editing must be completed in the correct order.

...

Paradigm has implemented the Course of Study Packet and the Courses Group packet on the same screen. This makes the screen a complex to use as data editing must be completed in the correct order. You must ensure the fields to get a Dest UID 3 are filled in before you can get a Dest UID5. This means you are required to complete the fields of the Course of Study Packet first. It is important to note without a UID for this record you cannot submit a course enrolment.

...

Courses On Campus Record

...

It is important in Paradigm that data packets are now completed in the correct in order for the system to push data packets to TCSI. This is important because we will not attempt to push packets where a required id is not completed. This means if a depenedent dependent UID is later required all the depenedent dependent records will need to saved independently so they get pushed to the TCSI system.eg

If you do not have a UID5 on the Courses Group packet then no course enrolments will be submitted to TCSI and therefore no uniy unit enrolments. So this means all these records will need to be save individually this also means that if these packets have sub packets they will also need to saved to they are pushed as well. Therefore it is vitally important for saving time that data packets are entered in the correct order.

One of the advanages advantages of TCSI reporting over HEPCAT is you only report sub packets if you have data for that sub packet. eg If your student does not have a disability you do not enter that sub packet.

There are some new sub records which can have one or more records, be time depenedent dependent and both have one or values and be time depenedentdependent.

The table below outline those dependencies

...

Course Of Study Packet

The table below outines outlines the editing rules you need to follow when using the screens to get a TCSI data packet to completed successfully.

...

The Paradigm implementation of the TCSI web interfaces

Some HEIMS TCSI response as examples listed below:

Workflow

Where to get more details about element numbers

...