Session 9: Government Reporting
Overview
The session focuses on the following government reporting requirements: AVETMISS, AVETMISS VIC, PIR, and TCSI. Depending on your business or institution’s needs, we will cover all the necessary details to set you up properly for you to be in compliance with all the mandated reports.
Â
Learning outcomes
Discuss the relationships and the file structure of all the AVETMISS NAT files (NAT00010 - NAT00130); and generate NAT00010-130 Files in Paradigm.
Describe the reporting scope and file structure for the Course of Study Report, PLE Report in Paradigm, PIR past course completions report, and the Student (PSD) ReportRun PIR Reports in Paradigm (PCS, PLE, PPS, and PSD); and generate these PIR Reports in Paradigm.
Identify and recall all the Unique Identifiers (UIDs) related to TCSI Reporting
Summarise and recognise the TCSI Push Rules
Identify elements that have been remapped, and have been migrated from HEIMS to TCSI
Â
1. AVETMISS
Duration: 60 minutes
Complexity: MEDIUM
This section will provide an overview of AVETMISS, the national standard for the collection of VET data. We will also give you the relationships and the file structure of all the AVETMISS NAT files (NAT00010 - NAT00130). At the end of this section, we will outline the workflow on how to use Paradigm SMS to generate each reporting file and submit it to NCVER's AVETMISS Validation Software for validation.
Â
Topics:
NAT00010 - Training Organisation File
Workflow from NAT00010 - Training Organisation File | Workflow[hardBreak]
NAT00020 - Training Organisation Delivery Location File: File Relationships and Training Organisation Delivery Location File Structure
Workflow from NAT00020 - Training Organisation Delivery Location file | [hardBreak]Workflow
NAT00030 - Program File: File Relationships and Program File Structure
Workflow from NAT00030 - Program file | Workflow
NAT00060 - Unit of Competency/Subject File: File Relationships and Subject File Structure
Workflow from NAT00060 - Unit of Competency/Subject File | Workflow
NAT00080 - Client File Structure
Workflow from NAT00080 - Client file | Workflow
NAT00090 - Disability File Structure
Workflow from NAT00090 - Disability file | [hardBreak]Workflow
NAT00100 - Prior Educational Achievement File Structure
Workflow from NAT00100 - Prior educational achievement file | Workflow
NAT00120 - Training Activity File: Relationships and Structure
Workflow from NAT00120 - Training activity file | Workflow
NAT00130 - Qualification Completed File: Relationships and Structure
Workflow from NAT00130 - Qualification Completed file | Workflow
Â
Resource Links:
Â
2. AVETMISS VIC
Duration: 60 minutes
Complexity: MEDIUM
This section will provide an overview of AVETMISS, the Victorian state standard for the collection of VET data. We will also outline the file structure under each AVETMISS NAT File for you to understand where the field draws from. This section will end with a demonstration of the workflow on how to use ParadigmSMS – generate each reporting file so you can submit the file to Victorian AVETMISS Validation Software (Skills Victoria Training System) for validation.
Â
Topics:
VICVET NAT00010 - Training Organisation File: Relationships and Structure
Workflow from VICVET NAT00010 - Training Organisation File | Workflow[hardBreak]
VSR/VSN Reports
Workflow from VSR/VSN Reports | Workflow
 External Excel Query, and External Excel Query via API for Office 365
Workflow from External Excel Query via API (Office 365 and Other Supported Excel Versions) | Workflow
Unit Assessment Results
Workflows 1-2 from https://silverband.atlassian.net/wiki/spaces/PKB/pages/15597569/Unit+Assessment+Results#Workflow
QILT SES Reporting
Workflow from https://silverband.atlassian.net/wiki/spaces/PKB/pages/1309704427/QILT+SES+Reporting#Workflow
Â
Resource Links:
Â
3. PIR
Duration: 60 minutes
Complexity: MEDIUM
This section will provide guidelines on how to generate the Provider Information Request (PIR) report from Paradigm, the reporting scope and file structure for the Course of Study Report, PLE Report in Paradigm, PIR past course completions report, and the Student (PSD) Report. At the end of this section, we will provide the workflows on how to run all these reports in Paradigm.
Â
Topics:
List of PIR Reports you can generate in Paradigm
Workflows 1-5 from https://silverband.atlassian.net/wiki/spaces/PKB/pages/984745/PIR+reporting#Workflow
How to Troubleshoot (Run a Report to Audit the Census Date are Correct): https://silverband.atlassian.net/wiki/spaces/PKB/pages/984745/PIR+reporting#Workflow
PIR Course of Study (PCO) Report: Reporting Scope and File Structure
Workflows 1-2 from https://silverband.atlassian.net/wiki/spaces/PKB/pages/984841/PIR%2BCourse%2Bof%2BStudy%2BPCO%2BReport#Workflow
PIR Half Year Load Estimate(PLE) Report: Reporting Scope and File Structure
Workflow from https://silverband.atlassian.net/wiki/spaces/PKB/pages/984836/PIR%2BHalf%2BYear%2BLoad%2BEstimate%2BPLE%2BReport#Workflow
PIR Past Course Completions (PPS) Report: Reporting Scope and File Structure
Workflow from https://silverband.atlassian.net/wiki/spaces/PKB/pages/984831/PIR%2BPast%2BCourse%2BCompletions%2BPPS%2BReport#Workflow
PIR Student (PSD) Report: Reporting Scope and File Structure
Workflow from https://silverband.atlassian.net/wiki/spaces/PKB/pages/984827/PIR%2BStudent%2BPSD%2BReport#Workflow
Â
Resource Links:
https://heimshelp.education.gov.au/pir/scope/pir-half-year-load-estimates
https://heimshelp.education.gov.au/pir/scope/pir-past-course-completions
Â
4. TCSI
Duration: 60 minutes
Complexity: MEDIUM
This section will give you all the must-know information related to TCSI Reporting – depending on your institution, this section will cover the following: all the packets and sub-packets of TCSI Reporting for Higher Education Providers, for VET Student Loans, Push Rules, Remapped Elements, and an outline of all the elements that have been migrated from HEIMS to TCSI with one or more options defined or changed otherwise.
Â
Topics:
TCSI for Higher Education Providers: Course of Study Group (UID3), Course Group (UID5), Courses on Campuses Group (UID4), Student Group (UID8), Course Admissions Group (UID15), and Unit Enrolments Group (UID16)
TCSI for VET Student Loans: Course Group (UID5), Campuses Group (UID2), Student Group (UID8), Course Admissions Group (UID15), and Unit Enrolments Group (UID16)
TCSI Push Rules – outlines the logic used to push certain data packets to the B2G API.
TCSI Remapped Elements – outlines a number of elements that have been remapped after TCSI implementation
TCSI Elements with Changed Options – outlines the elements that have been migrated from HEIMS to TCSI with one or more options defined or otherwise changed
Â
Resource Links:
https://silverband.atlassian.net/wiki/spaces/PKB/pages/14385161
https://silverband.atlassian.net/wiki/spaces/PKB/pages/14974985
https://silverband.atlassian.net/wiki/spaces/PKB/pages/16580785
https://silverband.atlassian.net/wiki/spaces/PKB/pages/19267818
https://silverband.atlassian.net/wiki/spaces/PKB/pages/19300415
https://silverband.atlassian.net/wiki/spaces/PKB/pages/19496980
Â
5. Review
Duration: 10 minutes
Complexity: MEDIUM
After delivering the main topics, there will be some spare time for open discussion. You can ask any questions you have during the training. We will discuss and confirm a date and time for the next training session.
Â
Topics:
Open discussion including Q&A
Confirm schedule for next training session
Outline outcomes of next session
Â
6. Extension
Duration: 90 minutes
The following tasks are recommended for users to complete at the conclusion of each training session to ensure that the content is understood and to establish familiarity with Paradigm terminology and its user interface.
Any records created during this section may be raised for review at the beginning of the next session to ensure that the data has been entered correctly, for example, meeting the relevant government reporting standard.
Â
Tasks:
Run NAT00010-130 Files in Paradigm
Run PIR Reports in Paradigm (PCS, PLE, PPS, and PSD)
Identify and recall the UIDs related to TCSI Reporting
Summarise and recognise the TCSI Push Rules
Identify elements that have been remapped, and have been migrated from HEIMS to TCSI
Â
Â
Â
Â
Â