| Project Info |
Project Managers Commentary |
|
FIN118 (AP56-016)
eFinancials upgrade
Core funded
RAG Status: RED
|
Report by Chris Orrell
Achievements in Last Period
- A strategic options paper detailing the various upgrade options that in theory may be available has been prepared and reviewed by the University. At the time of preparing this report option 1 appears likely to be the recommended option though additional detail and senior management review is required. This option paper included costs to date, costs directly attributable to the issue and estimated costs to complete for the supplier recommended approach.
- DEV has been upgraded to Oracle 12.1 eFinv5 using Data Guard and as expected no issues have been encountered and this confirms with the supplier that this method of data export / import can be performed with eFinancial upgrades.
- A revised draft plan for November go-live with Oracle 12.1 has been prepared but this needs to be reviewed in light of agreed update dates for TEST and Pre-LIVE of 9th and 24th May respectively.
- Security Pen Testing completed for eFin except for Supplier Self Service (SSS) and an interim report has been issued. Security Pen Test Supplier will complete the pen testing of SSS once a defect has been fixed.
- All JIRAs have been reviewed to identify those which should be resolved now rather than waiting for a repeat of UAT.
- Resources have been booked to complete eExpenses JIRAs and repeat UAT.
- Finance (FIS) have agreed that if eFin upgrade takes place in November 2018 the upgrades to FPM and eExpenses can wait until then.
Issues
- There is currently only one option available to the University to progress the upgrade of eFinancials this calendar year. This would mean TEST & Pre-LIVE being rebuilt to Oracle 12.1, interface testing being repeated for DEV & TEST and Finance repeating all of UAT. Earliest go-live is indicated at November 2018. However, the University must decide upon the favoured option and agree a route forward with the supplier.
- All project milestones currently void until the project has been re-planned.
- Asta requires a complete update to reflect whatever proves to be the agreed approach.
- The estimate to complete should be complete within this report should be completely ignored as it will be approximately 318 IS days.
Next Steps
- Finalise a project plan for the agreed approach to resolve the sequencing / Oracle 12.1 issue, then book resources against this, update projects web site and submit new milestones to WIS.
- All JIRAs not to be fixed now to be closed.
- Fix the SSS defect and complete security pen testing.
RAG Commentary
Issue: The project cannot go-live with Oracle 12.2 and so must be re-planned. An options paper has been prepared and reviewed and the approach to be taken by the University needs to be agreed both internally and with the supplier. This has been escalated to IS senior management. |
|
FIN119 (AP67-024)
eInvoicing
RAG Status : AMBER
|
Report by Richard Bailey
- Report Date
- April 2018
Achievements this Period
- Software Development Resource is booked against the project (see the Issues section below)
- A PICCL was submitted to WIS 27/04/2018 to reset the milestones / extend the project into the 2018/19 financial year.
- Progress has been made with the Applications and Data Architecture (ADA) Document.
- The Senior Analyst Developer has been secured to plan subsequent WPs (based on the decisions made / the Project Proposal & ADA Documents) in May.
Issues
- RISK: Securing Software Development Resource - Amber. PM has worked closely with the Resourcing Manager (Software Development). It was apparent that it would not be possible to secure Software Development Resource to complete all of the tasks required in the 17-18 financial year. Therefore Resource has been booked / secured to complete the required works at the first available opportunity, which runs the project into the 18-19 financial year.
- RISK: Securing Budget In 2018/19 Financial Year - Amber. At this stage the budgets for 2018/19 are yet to be secured / agreed and there is a risk that the budget to secure the remainder of the works will not be made available in the 2018/19 year.
Next Steps
- Submit a PICCL to WIS 04/05/2018 to raise the Project Priority from Normal to Higher in order to protect resource bookings / working alongside SG Team.
- Plan the subsequent WPs (based on the decisions made / the Project Proposal & ADA Documents) with the Senior Analyst Developer.
- Complete the Applications and Data Architecture (ADA) Document and achieve sign off.
- Get the SR document agreed and sign off / engage with the SG
-
RAG Commentary
Change: The change to the project timescales and moving a proportion of the development to the 2018-19 Financial Year creates a risk around securing budget to complete the tasks required in that year as budgets for 2018-19 are not yet agreed / set.
|
|
FIN123 (AP56-016)
Annual Finance Document Revitalisation 17/18
Planning - tbc
Delivery - tbc
Core funded
RAG Status : GREEN
|
Report by Lee-Ann Simpson
- Report Date
- April 2018
Achievements
- Kick off meeting with Finance undertaken to obtain commitment of Finance resource;
- Reached out to additional key finance stakeholders, setting up initial meeting in order to identify the documents which will be in scope for this project (meeting scheduled for 01/05/2018).
- Discussed project with Service Excellence whom advised they do not need to be sighted in this project currently as it does not impact upon the Core System Procurement. This will be reviewed throughout the duration of the project.
Issues
- There is a current potential issue regarding IS Service Development resource. This is being reviewed and discussed as part of the planning stage.
Next Steps
- Complete planning for the project.
- Project brief to be signed off.
- System Design to be commenced.
|
finapril2.png
