Background to types of changes and a how to change them

Skills required to meet the HESA Staff return

Looking to provide more detail to give the person more background into what skills are required and where to look.

We should include it into a document help on the Website

E.G.

HESA Extract

Although we may be able to identify the HESA field to be populated (from the HESA 17/18 Staff link), how do we identify which University HESA fields are used and from what table?

(This it to ensure we take the data from the correct place)

HESA BI Universes

Who can estimate and complete any Universe changes?

(I spoke to Andrew before our meeting and he said that if they are only changes to existing layouts and there are no new structures then he would not expect to be involved)

HESA APEX screens

Who can estimate and complete any Apex changes?

(I know last year there was confusion where JIRAs were raised and implied that the change was Apex, but in fact it was relating to Oracle)

Oracle Change

Who can add or amend fields?

I know some notes were made last year and some handover took place from Manoj. Can we make these available and I will put them on this year’s website please?

Looking to provide more detail to give the person more background into what is required and where to look?

Also any useful links - eg HESA

Project Info

Project
HR HESA Staff Return 17/18
Code
HRS094
Programme
Human Resources (HRS)
Management Office
ISG PMO
Project Manager
Anne Mathison
Project Sponsor
Susan McLaren
Current Stage
Close
Status
Closed
Start Date
22-Nov-2017
Planning Date
20-Apr-2018
Delivery Date
28-Sep-2018
Close Date
23-Nov-2018
Overall Priority
Higher
Category
Compliance