Closure Report

Project Summary

Research Information Management changes frequently, with changes to Research Excellence Framework, Open Access requirements and increasing demand from Research Funders and our own researchers.  

PURE and the service that it offers needs to be kept up to date. This can be achieved by taking the major version releases of PURE each year.

Additionally, PURE will only support redundant features for one year following their deprecation. It is vital that the University’s installation of PURE is kept up to date to avoid major step changes.

PURE is a supported service with both IS Applications Production Management Support and the support of the Research Information Systems team.

If PURE does not continue to be upgraded, this will result in the application falling behind the latest version, eventually falling out of vendor support and potentially failing to deliver on any new compliance features, such as the new form of REF return in 2021.

This project (RIS007) was initiated to continue the upgrade of PURE from versions 5.13 through to 5.15. The links on each release are included below:

Scope

The scope of this project was defined as the following:

  • To upgrade Tomcat (v8.5) and Java (Open JDK - OpenJDK jdk8u212-b04. See:https://doc.pure.elsevier.com/pages/viewpage.action?spaceKey=PureClient&title=Supported+Platforms ) to the latest versions for Pure v5.13 within all environments
  • Upgrade three versions of the University’s installation of Pure from v5.13 through to v5.15 
  • Resolve bug fixes identified during RIS003 and RES069 (Relating to the application version)
  • Resolution of carried forward actions from RIS003
  • Testing of the Pure processes adopted by the University
  • Testing of the Interfaces presenting data to Pure from Finance, HR, IDM and Student Systems
  • Testing of the outgoing interfaces to the downstream Web Services and Pure widget
  • Testing that the data within the new UPM works as expected
  • Decommissioning of redundant data and code from previous data model
  • Decommissioning of Web Services that have become redundant

 

Items Agreed Out of Scope

  • Upgrade to dev, test and live for Pure 5.14 not progressed as it was a business decision not to take this version and provided an opportunity to regain time lost when project was suspended due to RES069 activities which was priority at that time
  • Database work required for GDPR compliance; specifically the resetting of the 'Gender' field entries to 'Unknown'. This work will be carried out either as part of Core Systems project (HR and eFinance replacement) or a future post-REF future project in late 2021. The business team have identified functionality within next upgrade version 5.16 which may be able to update this information going forward.
  • The provision of a new Elsevier cloud (Pure) portal necessitating portal interface tailoring to UoE standards, i.e. Look & Feel with appropriate branding moved to RIS011 however initial consultation and requirements have been reviewed with Elsevier under this project.

Analysis of Resource Usage:

Staff Usage Estimate: 125 days

Staff Usage Actual: 75 days

% Usage : 60%

 

Outcome

The RIS007 Pure Upgrade v5.13 to v5.15 project has successfully delivered its requirements, whereby the Pure application is now running on the latest available components and the continuing plan will ensure the momentum built up over the last 2.5 years continues through to the point of REF2021 submission and beyond. 

Specifically, the underlying database is on Oracle 12c (RES062), Tomcat has been upgraded to v8.5 (RIS007), Java has been upgraded to OpenJDK v8.0 (RIS007) – all recommended by the supplier to support its latest releases – and the application has, since 2017, been upgraded through several major versions from v5.6 to v5.15 (see RIS001, RIS003, RIS007). The latest version in LIVE – v5.15.2-1 – was released September 2019.

The Pure upgrades delivered via this project has resulted in 30 REF Units of assessments managed by the RIS team due to the changes for REF 2021, in essence the users of the application are now seeing functionality for REF2021 instead of REF2014.” to read “The Pure upgrades delivered via this project, specifically the upgrade to 5.15, introduced the first substantially different piece of REF2021 functionality from what was previously used for REF2014 (namely a complete rewrite of the REF2 framework to enable the decoupling of staff and outputs). Engagement from the RIS team, who met with colleagues from around 30 Units of Assessment (UoA), was absolutely fundamental in ensuring that this change in functionality was well understood and gave the UoAs time to incorporate these changes into their local processes ahead of the upgrade itself.”

Objectives & Deliverables

 No.

 Description

 Priority       

Achieved

 O1

 To upgrade all Pure environments to v5.13

 MUST

 

          D1.1 Upgrade Tomcat (v8.5) and JAVA (Open JDK)to the latest version    Partial TOMCAT Upgraded (Java moved to v5.15 upgrade activity)

          D1.2

 Upgrade Development environment to Pure v5.13 and complete satisfactory testing

 

 Yes

          D1.3

 Upgrade Test environment to Pure v5.13 and complete satisfactory User Acceptance Testing

 

 Yes

          D1.4

 Complete performance / load testing to ensure no impact on current application performance         

 

 Yes

          D1.5

 Integration feeds are working as expected

 

 Yes

          D1.6

 Upgrade Live environment to Pure 5.13 and complete business testing

 

 Yes

 

 

 

 

O2

 To upgrade all Pure environment to v5.14 

MUST

 Descoped

          D2.1

 Upgrade Development environment to Pure v5.14 and complete satisfactory testing

 

N/A

          D2.2

 Upgrade Test environment to Pure v5.14 and complete satisfactory User Acceptance Testing

 

N/A

          D2.3

 Complete performance / load testing to ensure no impact on current application performance

 

N/A

          D2.4

 Integration feeds are working as expected

 

N/A

          D2.5

 Upgrade Live environment to Pure 5.14 and complete business testing

 

N/A

          D2.6  Decommission redundant data and code from previous data model   N/A
          D2.6  Decommission redundant web services   N/A
          D2.7  Communication with User groups for Web Services migration   N/A

 

 

 

 

O3

 To upgrade all Pure environments to v5.15

MUST

 

          D3.1

 Upgrade Development environment to Pure v5.15 and complete satisfactory testing

 

Yes (including Java Open JDK Upgrade)

          D3.2

 Upgrade Test environment to Pure v5.15 and complete satisfactory User Acceptance Testing

 

Yes

          D3.3

 Complete performance / load testing to ensure no impact on current application performance

 

Yes

          D3.4

 Integration feeds are working as expected

 

Yes

          D3.5

 Upgrade Live environment to Pure v5.15 and complete business testing

 

Yes

          D3.6 Decommission redundant data and code from previous data model   Yes
          D3.7 Decommission redundant web services   Yes
          D3.8 Communication with User groups for Web Services migration   Yes

Benefits and Success Criteria

Benefits
Achieved
Success Criteria
Achieved
All system upgrades will keep UoE on track for the REF2021 submission Yes Tomcat and JAVA will be upgraded with no impact to the application Yes
Additional functionality within each release will provide benefits to the business in addition to resolving bug fixes. Yes  Upgrades are undertaken with minimal impact to the production service Yes
Pure support communication of the University’s current research to a global audience, underpins open access compliance and our REF return and contributes to continued research income Yes  No impact to the current performance of the application following upgrade Yes
Continued support of the Pure application by Elsevier Yes

Web services will continue to work as expected once the redundant services are decommissioned

Yes

 

Explanation for variance

  • The project was impacted in the early stages due to the impact from RES069 project and was suspended for 2 months until April 2019 when RES069 was deployed to live.
  • Upgrade to dev, test and live for Pure 5.14 not progressed due to the number of bugs identified in the software prior to upgrade
  • Database work required for GDPR compliance; specifically the resetting of the 'Gender' field entries to 'Unknown'. This work will be carried out either as part of Core Systems project (HR and eFinance replacement) or a future post-REF future project in late 2021.
  • The provision of a new Elsevier cloud (Pure) portal necessitating portal interface tailoring to UoE standards, i.e. Look & Feel with appropriate branding moved to RIS011
  • Original budget estimated at planning 
    • FY 18/19 = 41 days
    • FY 19/20 = 84 days
    • Total = 125 days
    • This was revised downwards to 115 days when GDPR activity removed, revising 19/20 to 70 days
  • Actual Days at closure
    • FY 18/19 = 46 days
    • FY 19/20 = 29 days
  • As 5.15.2-1 was a standard upgrade, reduced Project management time required to manage activity
  • At project closure 40 days will be transferred back to RIS Programme 

Key Learning Points

  • Due to the tight timescales on the lead up to REF 2021 submission it may be necessary to take earlier versions of the software .2 releases instead of .4 version. This may result in identifying more bugs in the software than would normally be evidenced in later versions. 
  • By taking .1 release of version into development the business team can view new functionality earlier but may mean that deployment of 2 point releases into development before progressing through the environments.
  • When upgrading middleware components e.g. JAVA it is best to test upgrade of component and then upgrade Pure and retest to ensure no impact during Live upgrade.
  • Consideration for next project upgrades whether a data refresh is required or not and also level of review with business areas will be dependent on functionality and data changes contained within each release - this is unknown until releases notes are made available by the supplier which may result in changes to plan, milestones and activities within next project RIS011.
  • Elsevier have started to improve their forward planning documentation so the 5.17+ development plan – https://doc.pure.elsevier.com/pages/viewpage.action?pageId=77966797. We will be reviewing this regularly as this could give early indications of what’s coming when, but until we get the release notes we won’t know exactly will be delivered.

  • As with previous projects for PURE, the project team consisting of RIS Team, IS Application Management, IS Development Technology and IS Project Services have worked well together to complete deliverables for the project.

Outstanding Issues

  • Any JIRAs raised within this project but which could not be fixed until a later version of Pure is available e.g. resolution in 5.16 have been transferred to RIS011
  • Review of deployment and start up scripts will be required 

 

 

 

Project Info

Project
PURE Upgrades v5.13 to v5.15
Code
RIS007
Programme
Research Information Systems (RIS)
Management Office
ISG PMO
Project Manager
Karen Stirling
Project Sponsor
Dominic Tate
Current Stage
Close
Status
Closed
Project Classification
Run
Start Date
02-Nov-2018
Planning Date
31-Jan-2019
Delivery Date
19-Nov-2019
Close Date
10-Dec-2019
Programme Priority
4
Overall Priority
Higher
Category
Compliance

Documentation

Close