Report for June 2017

Report Date

June 2017

• Achievements this period:

  • Agreement reached on the approach re data protection and encryption for the Interim Service.

  • Coding contractor has joined the team.
  • All designs approved (does not include encryption).
  • Interim Service lined up to go-live on 12th July.
  • Equipment orders placed for one of the two DCs  
• Next Steps
  • Equipment orders placed for the second DC (carried over from last period).
  • Cloud provision option identified and agreed order placed (carried over from last period).  
• Risks - Full Service Solution:

  • 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 it is currently unknown what the impact will be on the time line from accommodating this.

  • .We do not yet have an agreed approach for dealing with personal or other sensitive data or the use of encryption on the Full Service Solution.
  • Our new coding contractor is not making the initial progress that was expected. We do not yet know what impact this will have on our overall time line.
  • A full decision on a cloud service provider has not yet been reached. Oracle is the preferred supplier within the project team but a formal selection process needs to be gone through.  We are progressing with coding work on the assumption that Oracle will be selected.   It is currently assumed this delay will not affect our overall time line.
  • There have been further delays with the purchase of storage infrastructure equipment within the Backup Infrastructure Upgrade project.   We do not yet now what the impact will be on out time line yet.
  • 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.

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.