Report for March 2019

Report Date
March 2019

Resource Position 

 

 

 

Forward Look

 

 

 

Section 2: Projects Not Started

Project Info

Programme Managers Commentary

FIN126 - Making Tax Digital & Essential Financial System Compliance Updates

Planning - April 12th, 2019

Delivery - July 31st,  2019

 RAG Status : GREEN

FIN126 Project Brief due to be reviewed by WIS on April 12th.

FIN129 - PCI DSS Audit

Initiation - TBC

Planning - TBC

Delivery - TBC

RAG Status: AMBER

Planned revision to start date for FIN129 to be discussed with Portfolio Manager during w/c April 8th, 2019.

 

AMBER RAG Status:

CSG team still awaiting response from ITI representatives, as ITI is better placed than Production Services to respond to PCI DSS audit questions from Finance team.

 

 

Section 3: Projects in Progress

 

Project Info

Project Managers Commentary

 

FIN119 (AP67-024)

eInvoicing

Core Funded

Agreed at WIS 25-Jan-2019:

Target Date Title  
01-Mar-2019   Development & Deployment of the API / XML Handler  
26-Mar-2019 On-board the First 3 Suppliers  
23-Apr-2019 On-board the Second 5 Suppliers  
10-May-2019 Phase 2 – Deployment sign off  
17-May-2019 Project closure  

 

RAG Status : RED

 

 

Report By Richard Bailey for March 2019

For reference:  SG = Scottish Government,  SGS = Scottish Government Solution

Achievements in Last Period

  • Work packages / development of the API / XML Handler (all original 'Must Have' Jira) almost complete (please see Issues below)
  • Acceptance testing started, though end to end testing not completed

Issues

  • Risk #12:  Application is not available for acceptance / testing - RED

    • Though Acceptance Testing has now started, its availability has been limited. A number of functional bugs have been discovered with an Invoice as it passes through its journey that have meant that an end to end test has still not been completed. Risk raised to RED as this has an impact both on Resource - Risk #5 "Securing Software Development Resource" and Risk #7 "Project Slippage Sees its Deadline Move Closer Towards the Regulatory Deadline"

  • Risk #14:  Additional Requirements / Issues After User Acceptance Testing, That If Not Put In Place Could Have Implications on Application Support - RED

    • It has been raised that a number of other requirements are coming to light as acceptance is prepared for / gets underway.  The issue is that these have budgetary implications and budget, or resource, may not be available in order to meet these.  If all of the possible requirements / possible invoice 'failure scenarios' are not developed then there is the risk that IS Applications Support might be engaged in order to help resolve / or clear any issues.

  • Risk #5:  Securing Software Development Resource - RED

    • As per Risk #14 above it is looking increasingly likely that Finance will require additional requirements / functionality within the eInvoicing solution, particularly within the User Interface in order to reduce risk of Application Support needing to be involved in resolving any issues with handling unmatched or failed invoices that are able to pass the SG Solution (as described / covered by Risk #14 Additional Requirements / Issues After User Acceptance Testing, That If Not Put In Place Could Have Implications on Application Support). This will need to be monitored going forwards and the Resource Manager / Project Manager of other projects awaiting resource are being kept informed, conflict maybe required. 

  • Risk #7:  Project Slippage Sees its Deadline Move Closer Towards the Regulatory Deadline - AMBER

    • Directly related to Risk #12 above, the ability to complete UAT and its potential slippage might see the Project deployment slip back.

  • Risk 13:  PO's can be issued by multiple systems to Suppliers by the University - AMBER

    • There are five University systems which generate order numbers (SciQuest, eFinancials, EBIS, ALMA and Saffron).  The three systems that have been highlighted during this project are the systems other than eFin/SciQuest (EBIS, ALMA and SAFFRON) as these three systems generate order numbers which do not interface to eFinancials and as such would not be recognised by the eInvoicing solution.  Due to the fact that it has come to light that potentially Suppliers could send in Invoices from systems that are not compatible with eInvoicing it has led to a possible scenario that these situations now need to be considered. Risk #14, above, has been raised to handle this.  

  • Risk #10:  Availability of Finance Staff Resource - AMBER

    • Though Finance Staff Resource has been maintained throughout this risk remains AMBER while Acceptance Testing is still required / continues to go on.

Next Steps

  • Complete work packages / development of the API / XML Handler (all original 'Must Have' Jira)
  • Complete acceptance testing
  • Agree / secure Resource / Budget to complete any recognised / agreed show stopper Jira 
  • Agree a new 'LIVE' SR with the SG, forms have been received are being processed
  • Agree new milestones and agree a plan / date to Go live, in coordination with the SG

 

 

FIN125

Media Production for Annual Report and Accounts                                              

Sponsor Funded

Milestones

  Milestone Due Date
  Closure Review 31-Jul-2019

 

RAG Status: GREEN

 

 

 

Report By Tim Gray for March 2019

 

Achievements in Last Period

  • No production activity this month
  • Meeting scheduled for early April to plan content production for the coming months

Issues

  • None

Next Steps

  • Confirm and plan future content production.

 

 

 

FIN126

Core Funded

Essential Finance System Compliance Updates and Document Revitalisation

 

Milestones:

To Be Agreed

 

RAG Status: GREEN

Report By Ken Miller for March 2019

 

Achievements in Last Period

  • Project Initiation raised and approved by WIS on 15/03/2019.
  • Assisted Procurement and Finance to sign off letter of engagement for proof of concept phase.
  • Meeting held with Finance to confirm present position and discuss how they see project progressing post proof of concept phase.

Issues

  • None

Next Steps

  • Project planning approved
  • Agree objectives and deliverables with Finance for both the MTD and BAU components of the project.

 

FIN127

Finance General Data Protection Regulation (GDPR)

Core Funded

Milestones

Milestone Due Date
Planning 01-Feb-2019
Analysis 03-May-2019
Solution Options 07-Jun-2019
Implementation Plan 28-Jun-2019
Delivery 30-Sep-2019
Closure 28-Oct-2019

 

RAG Status : GREEN

 

Report By Ken Miller for March 2019

 

Achievements in Last Period

  • GDPR patch installed on eFin Dev in prep for Advanced on site.
  • Review of GDPR patch for eFinancials with Finance and Advanced on site at Argyle House.
  • Meeting agreed to discuss implementation of GDPR patch and remaining scope of project.

Issues

  • Possible Business Analysis resource has been identified for IS Applications but has yet to be fully confirmed.

Next Steps

  • Agree sign of schedule for GDPR patch installed on eFin Dev.

  • Re-schedule GDPR patch installation on Test and Live.

  • Confirm scope of implementation of GDPR patch and remaining scope of project for 2018/19.

  • Kick off analysis of data across Finance systems for GDPR compliance.

 

FIN128

FPM Upgrade

Core Funded

Milestones

Milestone Due Date
Planning 08-03-2019
Delivery 03-05-2019
Closure 17-06-2019

 

 RAG Status : GREEN

Acheivements in Last Period:

  • Approval of FIN128 PICCL

    PICCL

    , to reflect revised Finance Process Management (FPM) testing approach, by WIS on March 1st
  • Initial  UAT review of FPM v2.4.0.15 by Finance in Dev environment
  • Advanced (FPM supplier) provided final confirmation of release date for FPM v2.4.0.16 (target release package for FIN128)

Issues:

  • None to report

Next Steps:

  • Release and deployment of FPM v2.4.0.16 in Dev and then Test environment
  • Initial Finance-team UAT testing activities in Dev environment

Section 4: Closed or Withdrawn Projects

 

Project Info Project Managers Commentary

FIN118 (AP56-016)

eFinancials upgrade

 

Closure Report

FIN123 (AP56-016)

Annual Finance Document Revitalisation 17/18

Closure Report