Report for May 2017

Report Date

May 2017

• Achievements this period:

  • Proposed s/w design for interim solution completed, with assumptions.

  • Start full service software build.

  • New live date for Interim service identified.

  • Lead time for DC infrastructure identified.  

• Risks

  • The project has been asked to ensure that the solution can accommodate non-research data.   Non-research data is more tightly controlled than research data from a data protection perspective, and the impact on the time line from accommodating this is currently unknown.

  • We do not yet have an agreed approach for dealing with personal or other sensitive data.

  • We expect encryption will be required but do not yet know what the solution is for this.

  • User stories, functional requirements and s/w design not yet signed off.    

• Next Steps
  • Process for addressing data protection requirements identified.
  • Sign off main solution user stories, functional requirements, and s/w designs (carried over from last period)
  • UAT for interim service under way.
  • Equipment orders placed (carried over from last period)
  • Cloud provision option identified and agreed placed (carried over from last period)

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.