Organisation

Work/Task Breakdown

Work carried forward from HR HESA Staff Return 12/13 project (HRS071):

• Changes that were applied direct to the data (as it was not possible to rerun the extract without impacted HR manual updates) have been retrospectively updated in the extract code on DEV. At the deployment sign off meeting it was discussed whether this should be applied to TEST and LIVE but agreed that, although there was low risk, the changes should only be applied to DEV and TEST so that these are not lost or forgotten before changes are made for 13/14. The code was checked in to SVN and should be used for the DEV Do-It (Build) for this project
• return LOCLEAVE for casual staff
  • business requirement to be specified

The carry over points below require the business rules to be reviewed, and if required, the code updated for the 13/14 submission; (some items will already have been covered by updating the XML, or covered within the HESA tables)

• APEX - There is a change required on the APEX system created in 12/13 for HESA. The issue encountered resulted in a person being both typical and atypical in the same year resulting in the same assignment qualifying for inclusion in the HESA return under two different categories in the same year. This should be reviewed to confirm if this situation needs to be coded or can be manually handled. (Deliverable) 

• LOCLEAVE - this was not collected for casual staff for 12/13 but there is a requirement to return this field.The business requirements will specify this year's changes to enablerule for how this should be returned needs to be agreed. 

• Current Academic Discipline not updating for all records (see JIRA https://www.jira.is.ed.ac.uk/jira/browse/HRS071-125)
• The following fields resulted in errors and the data was updated directly in the HESA code. The business HESA requirements will specify which of the fields require to be amended for; 

1. PREVHEI
2. REGBODY
3. ENDCON
4. STARTCON

• Review the Open JIRAs in HRS071 to see if they can now be closed or are needed for this years return:
  • HRS071-145 Apply code changes to HRDEV and HRTEST after clone (discuss) JIRA transferred to HRS082-3
  • HRS071-143 Request to apply data changes to HRTEST (please agree to close)
  • HRS071-141 Run script to generate hesa_ids for new starts  (please agree to close)
  • HRS071-125 Current Academic Discipline Missing (mentioned above as not updating) JIRA transferred to HRS082-5
  • HRS-71-126 NHSCON not being updated JIRA transferred to HRS082-4
  • HRS071- 68 HR will Clarify REF requirements with James Toon. This was covered last year, so can be closed JIRA transferred to HRS082-2
• The HR HESA project will adopt an iterative implementation approach moving to LIVE iteratively as soon as possible.
  • Initially it will follow the traditional waterfall approach until the first LIVE install
  • Thereafter further iterations to LIVE will enable proper thorough testing on LIVE data. This results in minimal testing in DEV and TEST to ensure that the application does not break before moving to LIVE.

Resources Skills and Cost

 This project will include resources from HR, Dev Tech, CSG CSG, Projects

60 days effort in HR HESA Staff Return Proposal with 2013-14 (30-40 days) and carry over to 2014-15 (20 days)

2013-14

2014-15

Further information

HR HESA Website

http://www.hesa.ac.uk/index.php?option=com_studrec&Itemid=232&mnl=13025

Project to be -re-estimated based on the Completed Brief