Report for April 2017

Report Date
April 2017

IS Applications Infrastructure Programme Report for Programme Owner Stefan Keampf

Section One: Programme Commentary, RAG and Resources Update

 

Section Two: Projects Not Started Section Three: Projects In Progress Section Four: Closed or Withdrawn Projects

Section One: Programme Commentary, RAG and Resources Update

Overall Programme RAG: AMBER

All projects for 16/17 have now started.  

The programme status is set as AMBER as our priority project INF121 has significant overspend on first phase and high estimates for second phase. Other projects all good.

 

 

 

 

Section Two: Projects Not Started  

Project Info Programme Manager's Commentary
  all projects started
   

 

Section Three: Projects in Progress

 

Project Info Project Manager's Commentary

INF119 (AP56-047)

Service Resilience Capability

Category: Discretionary

 

Milestones

10/05/2017

Priority Service (1) Live Failover complete

10/05/2017

Delivery

 17/05/2017

Closure

 

RAG Status / RAG change during last month

GREEN

Report by Karen Stirling for April 2017

Achievements in Last Period

  • IDM MyEd connector updated
  • Dev database failover completed and tested successfully
  • Database Switchover tasks documented and available on wiki page
  • Agreed with Technology Management team for their resource to complete Test and Live failovers
  • Test database failover completed and tested successfully

Issues

  • Review remaining effort and raise PICCL to return 25 unspent days to INF Programme
  • Moved test failover activities out by 1 week to allow Tech Man resource to complete failover for test
  • Ensure project activities are not impacting tasks within COM034 Annual Wiki Update project, Project Manager is in contact with COM034 project manager

Next Steps

  • Prep for Live database failover
  • Complete Live database failover
  • Complete closure report and agree sign off
  • Close project

The project status now GREEN.

RAG Commentary

n/a

 

INF121

Migrate Core Databases to Oracle 12c

Category: Compliance

 

Milestones

05-May-2017 Oracle 12.2 GO/NO GO
12-May-2017 Upgrade Oracle 12 GEN DEV/TEST/LIVE instances to Oracle 12.2
15-May-2017 Migrate GEN to Oracle 12.2
19-May-2017 NewsLive Deployment sign off
22-May-2017 GENDEV Post-migration Checks
16-Jun-2017 GenTEST integration sign off
16-Jun-2017 Live environment build for GenLive complete
30-Jun-2017 GenTEST Acceptance sign off

RAG Status / RAG change during last month

RED

Report by Chris Konczak for April 2017  

Achievements in Last Period

  • Pre migration testing on DEV, TEST and LIVE completed
  • Project plan and estimate reviewed and agreed.
  • Error in upgrade from Oracle 12.1 to 12.2 now resolved and upgrade for RMADDEV can begin

Issues and Risks

  • There is an issue with the 12.2 database template scripts which are being prevented from running. Investigation is on-going.
  • Duration to complete the 12.2 upgrade is taking longer than anticipated. No issue with effort required, but more the duration will need extended.

Next Steps

  • Continue with GEN environment build
  • Begin DEV, TEST and LIVE Pre migration testing
  • Review of project plans and estimates for 16/17 and 17/18 will be carried out in April.

RAG Commentary

  • Change. Resolved. Scope change to migrate to Oracle 12.2 to avoid future downtime and extended end of life. Agreed by project team and sponsor.

 

INF123

16-17 Provisioning of Python environment

Compliance

Milestones

Target Date

Title

22-Feb-2017

Iteration 1 Release

01-May-2017

Start of iteration 1A

08-May-2017

Start of iteration 2

12-May-2017

End of iteration 1A

18-May-2017

Start migration of IDM dashboard

05-Jun-2017

Start of iteration 3

07-Jun-2017

End of iteration 2

07-Jul-2017

End of iteration 3

14-Jul-2017

Delivery

28-Jul-2017

Closure

 

RAG Status

Green

Report by Chris Orrell for April 2017

Achievements in Last Period

  • Requested an additional 22 days which was approved by WIS. A developer resource has been secured so that additional value may be delivered by the 16/17 Python project and this is being progressed through Iteration 1A.
  • Python packaging repository work has been completed to allow Edgel Innovation work from API126 to be released (D1.1).

Issues

  • A new risk has been raised that preliminary work necessary to allow Iteration 3 to progress containerisation development work may not be completed to allow iteration 3 to start as planned. Risk owner and mitigation to be agreed.
  • A release date for Edgel Innovation deliverable D1.1 is required.  

Next Steps

  • Plan the work necessary in order to release iteration 1.
  • Agree actions that will allow Iteration 3 containerisation development to start on time.
  • Iteration 2 planning meeting scheduled for 5 May in advanced of iteration start date 8 May. 
  • Schedule the next key stakeholder meeting.
 

RAG Commentary

Project is rated green, scope rated amber. Iteration 3, Containerisation, is scheduled to start 5 June. However, the University has yet to agree a Strategy or Roadmap for containerisation and so without these items in place these user stories may not be completed, see risk 10.

 

INF124

Bamboo Upgrade 2016

Milestones

07-Apr-2017 Sign Off Test Bamboo Environment
20-Apr-2017 Delivery (Bamboo and Nexus)
21-Apr-2017 Sign Off Live Nexus Environment
21-Apr-2017 Sign Off Live Bamboo Environment
28-Apr-2017 Closure

 

RAG Status

GREEN

Report by Gillian Henderson for March 2016

Achievements in Last Period

  • Test Nexus Environment Built
  • Test Nexus Environment Tested
  • Test Nexus Environment Signed Off
  • Test Bamboo Environment Built
  • Test Bamboo Environment Tested
  • Test Bamboo Environment Signed Off
  • Live Nexus Environment Built
  • Live Nexus Environment Tested
  • Live Nexus Environment Delivered
  • Live Bamboo Environment Built
  • Live Bamboo Environment Tested
  • Live Bamboo Environment Delivered

Issues and Risks

  • no amber or red risks

Next Steps

Complete Bamboo Environment tasks for Deployment Sign off

  • Final TAD updates to be made including new diagram showing outgoing connections through Nexus and firewall change to block outgoing connections.
  • Updated TAD circulated to Stakeholders and ITI.
  • Deployment Checklist to be completed (Tech Man to confirm if require additional handover)
  • CMDB to be updated with new server names.
  • Agree date to decommission old Bamboo Servers.  Production to raise call with ITI to remove on agreed date (Current servers powered down and unavailable but may be required for reference over coming months)

Complete Nexus Environment tasks for Deployment Sign off

  • Final TAD updates to be made following feedback.
  • Updated TAD circulated to Stakeholders and ITI for sign off.
  • Deployment Checklist to be completed Tech Man (Tech Man to confirm if require additional handover.
  • CMDB entry to be added for Nexus Service.
  • Agree date to decommission old Nexus Environment. In meantime agree when can shut this server down. Production to raise call with ITI to remove on agreed date.
  • Determine if tasks to update all plans to reference new Nexus URL is part of INF124 (if easy global update with 1-2 days effort) or if plans would be updated out with this INF124 on a project by project basis. – confirmation required by Stefan/Bill/Iain
 

INF125

System Monitoring Pilot 2

Discretionary

Milestones

To be replanned

 

RAG Status

AMBER

 

Report by Maurice Franceschi for April 2016

Achievements in Last Period

  • complete requirements gathering - not achieved - need team to complete MoSCoW
  • workshop with AppDynamics  -achieved
  • TEST implementation - achieved but issues to resolve

Issues and Risks

  • no amber or red risks

Next Steps

  • complete requirements gathering
  • set plan and resource folk for completion of TEST, LIVE once we have fed back to AppDynamics
  • hold workshop to identify business processes to be monitored and how to configure these in the system
  • start using AppDynamics to monitor EUCLID, LEARN and UWS

 

 

RAG Commentary

The AppDynamic consulting who was on-site 27/4 is preparing the planning for implementation document, with feedback from the team by 5/5. Once plan is completed, we can then set the project plan for build, test and delivery.

 

Section Four: Closed or Withdrawn Projects

 

Project Info Project Managers Commentary
INF115 Python Development Platform Implementation Closure Approved August 2016

INF113 (AP45-067)

System Monitoring Pilot

Closure Approved 16 September 2016

INF111 (AP56-006)

New SQL Server Database Tier Replacement

Closure Approved 30 September 2016

INF118

JIRA upagrade 2016

Closure  Approved 30 September 2016

INF120

Disaster Recovery for Priority Services

Closure Approved 3 March 2017

INF116

ASTA Upgrade 2016

Closure Approved 3 March 2017

INF122

Infrastructure Rationalisation

Closure Approved 1 May 2017

 

 

 

Programme Info

Not available.

Documentation

Not available.