Report for August 2017

Report Date

August 2017

• Achievements this period:
  • Phased approach for full service delivery agreed to support key functionality going live asap.
  • Encryption approach agreed.
  • Edina engaged re provision of coding resources.  
• Issues
  • Delay with coding work – We are several weeks behind the re-plan put together in June.   Edina are lined up to provide resources once we have completed the function and technical reqs.

  • Delay with provision of tape infrastructure in DCs (being delivered by the Backup Infrastructure Project).  We have a target date of end of Sept. for this now. Coding contractor has not worked out as hoped and has now left the Uni with little progress made.

  • Delay with provision of the cloud service. Target date of end of Sept. for this now.  

• Risks - Full Service Solution:

  • No confirmed resource to document\design how encryption and key management will be applied, and potentially to deploy this as well.   It is un-clear how much effort this will take, and what impact it will have on the time-line.

  • Change in PM – Steve Taylor’s IoT programme needs more of his time and he needs to step back from the DataVault project.  Maurice Franceschi is working with Apps team to identify a new PM.

  • Kenton D’Mellow has been assigned to a key new project which may impact his availability for DataVault.

  • The policy for the Interim Service is that no personal data should be stored on the system.  We are relying on depositors adhering to this policy, but there is a Risk that personal data may make it on to the system.  
  • Next Steps
    • Confirm resource for encryption design (and implementation?) work.
    • Completed functional and technical requirement docs.
    • Document functionality questions that the project team need the Board to advise on, and present these to the Board for feedback.

    • Re-planning and confirm new expected go-live date for phase 1 of the full service solution.

Note re budgets:   This project has a mix of capital and revenue budgets, and core funding on this project.  The revenue budget is a fixed cost for RSS effort and the other teams are core funded, so there is not effort tracking against budget on this project.