Impact

Priority and Funding

This project is a Priority 1 due to the hard milestone for completion of the database migration by December 2014 so as to not impact the HR & Payroll Annual Maintenance (Tax Year End) Project and to reduce the risk to the database caused by the current database infrastructure approaching end of life and support arrangements. The project will focus on the migration of the database by early December 2014 with the implementation of DataGuard to be carried out asap at later date. 

The project is Core Funded due to this being a compliance project.

Impact and Dependencies

As noted above, the database migration must be completed by earlyDecember 2014 or this will impact the 14/15 HR & Payroll Annual Maintenance (Tax Year End) Project. The Annual Maintenance Project is undertaken each year with clones and pre-requisite patching usually required to start mid-November to ensure sufficient testing periods as well as contingency for progressing bugs or issues with the supplier Oracle. The Tax Year End patches are then started during February to again allow sufficient contingency for testing and supplier input. Failure to complete the LIVE migration by early December may result in the University being unable to complete all tax year end technical and business activities by the legislative deadline mid April. We have agreement with all stakeholders to start the annual maintenance project a bit later this year to try and ensure the migration is complete in the first week of December.

The migration of the Oracle HR & Payroll database will impact the following work during the periods when each environment is unavailable for migration or while testing is underway; 

• Automate Maternity, Paternity and Adoption Pay
• Online Payslips and P60s
• Implement the Recommendations of the Enhancing Employment project

A full business diary showing the three environments and the planned work on each is available here.