Home > Data & statistics > Funding and monitoring data > Latest statistics > 2010-11 overview
This page contains information regarding funding and monitoring data activities based on 2010-11 HESA and ILR data. These are the 2010-11 web facility and 2010-11 funding and monitoring data exercise.
The HEFCE web facility assists institutions and colleges in returning accurate data to HESA or the Data Service. The 2010-11 HESA web facility was released on the 11 August 2011 and ILR web facility was released on 20 September 2011.
The funding and monitoring data exercise takes place after finalised data have been submitted to HESA and the Data Service. We perform funding data reconciliations, and also produce indicative funding summaries which are used to inform funding allocations. The 2010-11 funding and monitoring data reconciliation exercise is expected to be released in Spring 2012-13.
We also provide additional activities based on 2010-11 HESA and ILR data.
| HEIs | FECs | |
|---|---|---|
| Indicative funding summaries |
||
| 2012-13 widening participation (WP) allocations | ||
| 2012-13 teaching enhancement and student success (TESS) allocation |
Download the ilr_indicative_2012-13_TESS as PDF (274 KB) Download the ilr_indicative_2012-13_TESS as MS Word (167 KB) |
|
| 2013-14 national scholarship programme (NSP) allocation | ||
| 2012-13 research degree programme (RDP) supervision fund allocation | n/a | |
| Funding data reconciliations |
||
| HESES10 re-creation | n/a | |
| HEIFES10 re-creation | n/a | |
| HESES10 re-creation based on cost centre sector norms | n/a | |
| RAS10 re-creation | n/a | |
| CFEE10 re-creation | ||
| Other funding and monitoring data | ||
| Summaries of students' entry qualifications and grades | n/a | |
| 2010-11 HEFCE-fundable student FTEs for TRAC(T) | n/a | |
| National student survey (NSS) targets | n/a | |
| Destinations of leavers from higher education (DLHE) | n/a | |
| Unistats summaries | n/a | |
| Derived statistics that may inform HESES10 data audits | n/a | |
| Derived statistics used for publication and to inform policy | n/a | |
| Date | Action |
|---|---|
| 15 September 2011 | C10051 HESA student record return deadline |
| 21 November 2011 | 2010-11 Learner Responsive data return (LR05) |
| 4 May 2012 | Deadline for receipt of action plans for HEIs or FECs wishing to make amendments for funding purposes |
| 18 May 2012 | Deadline for sign-off for HEIs or FECs wishing to make amendments for funding purposes |
| 29 June 2012 | Deadline for receipt of final action plans produced by each HEI required to respond for reconciliation purposes |
| 6 July 2012 | Deadline for receipt of final action plans produced by each FEC required to respond for reconciliation purposes |
| 13 July 2012 | Deadline for submitting amendments and overrides to primary derived fields for each HEI required to respond for reconciliation purposes |
| 20 July 2012 | Deadline for submitting amendments and overrides to primary derived fields for each FEC required to respond for reconciliation purposes |
Action plans are available via the HEFCE extranet (see How to access outputs for details about accessing the extranet). The following guides for completing the action plans are available:
There are no exercises currently running where we would expect institutions or colleges to respond. When a response is required to an exercise, example action plans will be made available.
These can be downloaded from the HEFCE extranet by navigating to the ‘HEFCE resources’ page, then under ‘Folders’ click on the ‘2010-11 data amendments’ link. Then for the general HESA amendments action plan click on ‘APHESA10 data collection’; for the general ILR amendments action plan click on ‘APILR10 data collection’.
On the HEFCE extranet navigate to the 'HEFCE resources' page, then under 'Folders' click on 'HESA FAMD data 2010-11: funding data reconciliations', then for:
On the HEFCE extranet navigate to the 'HEFCE resources' page, then under 'Folders' click on 'ILR FAMD data 2010-11: funding data reconciliations', then for:
Once the action plan has been completed, you can upload by navigating back to the same page that the action plan was downloaded from. Next select 'Upload', browse to the location where the action plan is saved and select 'Upload'.
The guide to action plans provides descriptions about the different types of data correction. We will invite institutions to submit an override or amendment file to us on approval of a valid action plan.
An override or amendment file may be uploaded via the HEFCE extranet by navigating to the 'HEFCE resources' page, then under 'Applications' click on the 'FAMD General upload area (GUA)' link. This will take you to the upload page where override and amendment files may be submitted. To upload, select the 'Upload' button and then, on the subsequent page, select the 'Browse' button to find the file you wish to submit. Once you have selected this file and the pathname has appeared in the entry field, select 'Upload File' to complete the upload.
To amend HESA student data, post-collection amendments must be made to the HESA return (Fixed database). If amendments are required after the closing date of the Fixed database, it may be possible to submit an Historic data error file to us.
Where there are problems of fit with our algorithms overrides to primary derived fields may also be submitted to us.
FECs may submit either ILR amendment files or overrides for primary derived fields depending on the type of data correction required.
| Override files | |
|---|---|
Example HDE file |
This is an HDE file to correct the primary derived field RDPEXCL. This example will change 2 students to be included in the RDP population who were previously not included, and exclude 2 students from the RDP population who were previously included. |
Example override file for primary derived fields for HEIs |
This is an override to the primary derived field HESFEELV. This example will change the fee level of 4 students to either FULL or HALF. |
Example override file for primary derived fields for FECs |
This is an override to the primary derived field HEFFEELV. This example will change the fee level of (hypothetical) learner aim 00012345 to FULL and aim 00023456 to HALF. Note the use of RECNO to create a suitable field to allow the check sum to be computed. |
Example override for LAD fields |
This is an override to the LAD field AWARD_BO. This example will change the awarding body of (hypothetical) learning aim references ABCDE001, ABCDE002 and ABCDE003. Note the use of RECNO to create a suitable field to allow the check sum to be computed. |
| ILR amendment files | |
|---|---|
| CHANGE FILES | |
Example HE data set change file |
This example changes fields Type of instance year (H13), Mode of study (H14), Level applicable to funding council HESES (H15) and Student instance FTE (H17) for students identified by Provider number (H01), Learner reference number (H03), Learning aim data set sequence (H05) and Student instance identifier (H09). |
Example learning aim data set change file |
This example changes the Programme type (A15) identified by the combination of Provider number (A01), Learner reference number (A03), Learning aim data set sequence (A05) and Provider specified learning aim data (A48a, A48b). |
Example learner data set change file |
This example changes the Country of domicile (L24) for students identified by the combination of Provider number (L01), Contract/allocation type (L02), Learner reference number (L03) and Provider specified learner data (L42a, L42b). |
| DELETION FILES | |
Example HE data set deletion file |
This example removes learner data incorrectly returned from the HE data set identified by the combination of Provider number (H01), Learner reference number (H03), Learning aim data set sequence (H05) and Student instance identifier (H09). |
Example learning aim data set deletion file |
This example removes learning aim data incorrectly returned. The records are identified by the combination of Provider number (A01), Learner reference number (A03), Learning aim data set sequence (A05) and Provider specified learning aim data (A48a, A48b). |
Example learner data set deletion file |
This example removes learners incorrectly returned. The records are identified by the combination of Provider number (L01), Contract/allocation type (L02), Learner reference number (L03) and Provider specified learner data (L42a, L42b). |
| ADDITION FILES | |
Example HE data set addition file |
This example adds HE data to three existing learning aims. |
Example learning aim data set addition file |
This example adds learner data to the learning aim data set. |
Example learner data set addition file |
This example adds three students to the learner data set. |
Page last updated 25 June 2012
Vacancies | Copyright | Disclaimer | Tenders |