Report for January 2017

AP67-024

eInvoicing for medium suppliers

Planning - tbc

Delivery - tbc

 RAG Status : GREEN

AP67-025

Fraud protection for Accounts Payable

Planning - tbc

Delivery - tbc

 RAG Status : GREEN

FIN108 (AP56-042)

Essential enhancements (FIS)

Category: Discretionary

Milestones

tbc - dependent on the Supplier's delivery of a successful fix.  Milestones to be re-planned

RAG Status : SUSPENDED

Report by Nikki Stuart 

Project has been suspended awaiting an FPM patch being applied and signed off in DEV. 

Testing is currently underway in Finance for the latest patch which was released and applied to DEV. Initial testing was positive and if the patch is signed off in DEV then the project will be reopened.

Next Steps

• obtain business sign-off to progress latest patch to Test
• Re-plan the project's remaining milestones

FIN111 (AP56-036)

eExpenses enhancements

Category: Discretionary

Milestones

 RAG Status : BLUE (suspended)

Report by Nikki Stuart

This project is now suspended until the April

FIN115 (AP67-026)

FInancial systems user de-provisioning

Category: Compliance

Milestones - WP1

RAG Status : AMBER

Report by Nikki Hackett-Reed for January 2017

Achievements this period

WP1

Acceptance

• UAT completed
• ASOR

Deployment

• Alert drafted
• GO/NO GO - due to resource conflicts GO LIVE delayed until 09/02

WP2

System Design

• Complete/sign off SDS
• Complete/sign off TAD

Build

• Build commence

Risks/Issues

WP1/WP2

NONE

Next Steps

WP1

Deployment

• Deploy

WP2

Build

• Build completed

Integration

• integration commenced

FIN116 (AP67-022)

eTime - guaranteed hours

Category: Compliance

Milestones

Indicative revised milestones - to be approved by Project Team and Sponsor

 RAG Status : AMBER

Report by Nikki Stuart for January 2017

Achievements in last period

• Business Analysis stage complete
• Revised resource requests submitted

Issues

• The project Designer's start date has been delayed due to the demands of other projects.  
• New Project Manager to be assigned due to an extended period on unplanned absence

Next Steps

• Agree revised milestones
• Start design

RAG Status

AMBER to reflects need to replan the project with a new PM and to accommodate impact from develop conflict.

FIN117 (AP56-054)

Finance BI Improvement

Category: Discretionary

Milestones

RAG Status: Amber

Reported by Duncan Stewart for January 2017

Achievements this period

• Issue identified with reports required for analysis.  Service Management working with BI supplier to resolve.  An updated report with new objects has been produced, currently under review by Service Management
• JIRA Dev work underway

Risks

• Key project resource may be unavailable at critical times due to higher priority work
• The remaining BI development activity may take longer to complete than initially estimated if not conducted by specialist

Issues

• Issue identified with BI reports required for analysis.  Service Management working with BI supplier to resolve. 

Next steps

• Resolve BI report issues
• Continue BI report analysis
• Hold 'security workshop' once report analysis complete
• Continue development analysis/solutions for JIRAs
• Agree release approach/schedule for JIRAs

Amber RAG status reflects slippage against planned start date of Finance team's review of existing BI reports, which is due to the issues encountered with the BI reports required for the analysis. Status should revert to Green once report issues have been resolved by Service Management.

FIN118 (AP56-016)

eFinancials upgrade

Core funded

Milestones: November go-live now considered unlikely. Revised milestones to be discussed 13 February with Project Sponsor.

Target Date	Title
No date available	End of Analysis / Design
No date available	Readiness / Approval to Go-Live
10-Feb-2017	Project Brief
20-Nov-2017	Go-Live
31-Jan-2018	Deployment Sign-off
28-Feb-2018	Project Closure

RAG Status: AMBER

Report by Chris Orrell for January 2016

Achievements in Last Period

• Project Brief, including detailed estimation but excluding key milestones (due to Advanced not advising their availability) agreed by key stakeholders.
• Detailed plan prepared and initially reviewed by project team to understand what would be required in order to achieve a November go-live if Advanced are not available, as they have suggested, until end May / June (see issue below). Achieving a November go-live is considered unlikely and a review has been scheduled with the Project Sponsor 13 February to consider high level milestones.
• Interface document has been initially reviewed by Project Team, additional work is still required to amalgamate various sources of information. This is then to form the basis of an Interface test plan.
• Initial resource requests have been submitted through Asta and this work is to be completed.

Issues

• Advanced have advised that they will not be able to support this project until end May / June. The risk that they will be unable to support the requested project timescales (a preferred go-live in November) is considered to have materialised and without a clear understanding of project milestones this is the reason why the Project Brief has not yet been submitted to WIS. This issue has been escalated by Finance and despite Advanced being on site 23rd January and this situation being reviewed internally by them 25th January there has been no change in their position. High level project planning options to be discussed with Project Sponsor 13 February. Advanced have so far failed to answer any of the technical questions tabled 9 January (and discussed again 23rd January) commenting they need to first appoint a project manager.
• Project Brief was not submitted to 20 January WIS, a PICCL has been raised and approved by WIS and a submission is targeted 17 February.
• Initially proposed project budget was 400 days. Project estimation is proposed at 537 and this is the figure shown within Asta.  

Next Steps

• Confirm high level project milestones and submit Project Brief to WIS 17 February.
• Confirm dates when Advanced can support project and number of days they will need to support the project.
• Hold initial meeting with Chief Information Security Officer and Information Security Manager and begin to define security requirements for project and potential changes to architecture that may be needed.
• Complete resource submission on Asta.
• Complete detailed project plan, specifically interface document and test planning.

AP67-023

eCash

Core funded

FIN112 (AP56-921)

Finance strategic review

Category : discretionary / funded

Project Manager - Dawn Holmes

Project closed 2nd August 2016

Link to completion report

AP45-020

Estates & Buildings - Finance interface requirements

Category: Discretionary

FIN114 (AP56-039)

Financial documents revitalisation (Version One)

Category: Discretionary

Project Manager - Nikki Hackett Reed

Project closed 2nd September 2016

Link to Completion report